[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03

Network Working Group                                     P. Saint-Andre
Internet-Draft                                                       JSF
Expires: February 9, 2006                                 August 8, 2005


Transporting Presence Information Data Format (PIDF) over the Extensible
                 Messaging and Presence Protocol (XMPP)
                     draft-saintandre-xmpp-pidf-02

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on February 9, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document defines how to send information encoded in the Presence
   Information Data Format (PIDF) over the Extensible Messaging and
   Presence Protocol (XMPP).








Saint-Andre             Expires February 9, 2006                [Page 1]


Internet-Draft               PIDF Over XMPP                  August 2005


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
   4.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     4.1   Normative References . . . . . . . . . . . . . . . . . . .  5
     4.2   Informative References . . . . . . . . . . . . . . . . . .  5
       Author's Address . . . . . . . . . . . . . . . . . . . . . . .  6
       Intellectual Property and Copyright Statements . . . . . . . .  7









































Saint-Andre             Expires February 9, 2006                [Page 2]


Internet-Draft               PIDF Over XMPP                  August 2005


1.  Introduction

1.1  Overview

   The Presence Information Data Format ([PIDF]) defines a common data
   format for presence protocols that conform to the Common Profile for
   Presence ([CPP]), enabling presence information to be transferred
   across CPP-compliant protocol boundaries without modification, with
   attendant benefits for end-to-end encryption and performance.
   Because the syntax for PIDF is Extensible Markup Language [XML], it
   should be straightforward to send PIDF data over the Extensible
   Messaging and Presence Protocol (XMPP) [XMPP-CORE], since XMPP is
   simply an XML streaming protocol.  This memo defines a mechanism for
   encapsulating PIDF data within an "extended namespace" contained in
   an XMPP presence stanza.

1.2  Terminology

   This document inherits terminology defined in [PIDF], [XMPP-CORE],
   and [XMPP-IM].

   The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
   "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in RFC
   2119 [TERMS].

2.  Protocol

   The PIDF format is defined in [PIDF].  Briefly, the XML namespace
   name is 'urn:ietf:params:xml:ns:pidf', the root element is
   <presence/>, the <presence/> element must possess an 'entity'
   attribute that specifies the pres: URI (see [CPP]) that identifies
   the presentity (see [RFC2778]) to which the PIDF data relates, and
   the <presence/> element may contain any number of <tuple/> child
   elements specifying information about the entity.

   The recommended method for encapsulating PIDF data within an XMPP
   presence stanza is by including the PIDF <presence/> element as a
   child of the XMPP <presence/> stanza.  Although it may appear that
   this is potentially confusing, the inclusion of the
   'urn:ietf:params:xml:ns:pidf' namespace ensures that PIDF data is
   kept separate from XMPP presence data (in accordance with [XML-
   NAMES]).  The following is a simple example of encapsulating PIDF
   data within an "extended namespace" in XMPP:







Saint-Andre             Expires February 9, 2006                [Page 3]


Internet-Draft               PIDF Over XMPP                  August 2005


   A basic example of PIDF over XMPP:

   <presence from='romeo@example.net/orchard' xml:lang='en'>
     <show>dnd</show>
     <status>Wooing Juliet</status>
     <presence xmlns='urn:ietf:params:xml:ns:pidf'
               entity='pres:romeo@example.net'>
       <tuple id='orchard'>
         <status>
           <basic>open</basic>
         </status>
       </tuple>
     </presence>
   </presence>

   Because base PIDF data does not encapsulate any additional
   information over and above XMPP presence stanzas, there is little
   point to including it in native XMPP systems when it is not encrypted
   (obviously, encrypting PIDF data can help to ensure end-to-end
   encryption of presence information, as described in [XMPP-E2E]).  The
   power of PIDF in the context of XMPP derives from PIDF extensions,
   such as those for rich presence (see [RPID]) and geographical
   location (see [GEOLOC]).  Any such extension to PIDF can be included
   in an XMPP presence stanza, since, according to the definition of
   "extended namespaces" in [XMPP-IM], the format of such extended data
   is defined by the extension rather than by the base XMPP
   specification itself.  Thus the ability to include PIDF data and PIDF
   data extensions in XMPP enables XMPP-aware applications to include
   any PIDF-compatible data that is currently defined or that may be
   defined in the future.  Naturally, there is no guarantee that all
   XMPP entities will be able to understand such PIDF data, and entities
   that do not understand the data MUST ignore it (in accordance with
   [XMPP-CORE]).  However, this memo at least defines a mechanism for
   including PIDF data, which XMPP applications are encouraged to
   implement if they desire to make use of PIDF data extensions for rich
   presence, geographical location, and other kinds of presence-related
   information.

3.  Security Considerations

   This memo introduces no new security considerations above and beyond
   those provided for PIDF in [PIDF] and for XMPP in [XMPP-CORE].

4.  References







Saint-Andre             Expires February 9, 2006                [Page 4]


Internet-Draft               PIDF Over XMPP                  August 2005


4.1  Normative References

   [CPP]      Peterson, J., "Common Profile for Presence (CPP)",
              RFC 3859, August 2004.

   [PIDF]     Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr,
              W., and J. Peterson, "Presence Information Data Format
              (PIDF)", RFC 3863, August 2004.

   [TERMS]    Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [XML]      Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler,
              "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-
              xml, October 2000, <http://www.w3.org/TR/REC-xml>.

   [XML-NAMES]
              Bray, T., Hollander, D., and A. Layman, "Namespaces in
              XML", W3C REC-xml-names, January 1999,
              <http://www.w3.org/TR/REC-xml-names>.

   [XMPP-CORE]
              Saint-Andre, P., "Extensible Messaging and Presence
              Protocol (XMPP): Core", RFC 3920, October 2004.

   [XMPP-E2E]
              Saint-Andre, P., "End-to-End Signing and Object Encryption
              for the Extensible Messaging and Presence Protocol
              (XMPP)", RFC 3923, October 2004.

   [XMPP-IM]  Saint-Andre, P., "Extensible Messaging and Presence
              Protocol (XMPP): Instant Messaging and Presence",
              RFC 3921, October 2004.

4.2  Informative References

   [GEOLOC]   Peterson, J., "A Presence-based GEOPRIV Location Object
              Format", draft-ietf-geopriv-pidf-lo-03 (work in progress),
              September 2004.

   [RFC2778]  Day, M., Rosenberg, J., and H. Sugano, "A Model for
              Presence and Instant Messaging", RFC 2778, February 2000.

   [RPID]     Schulzrinne, H., "RPID: Rich Presence Extensions to the
              Presence Information Data Format",
              draft-ietf-simple-rpid-08 (work in progress), July 2005.





Saint-Andre             Expires February 9, 2006                [Page 5]


Internet-Draft               PIDF Over XMPP                  August 2005


Author's Address

   Peter Saint-Andre
   Jabber Software Foundation
   P.O. Box 1641
   Denver, CO  80201
   US

   Email: stpeter@jabber.org










































Saint-Andre             Expires February 9, 2006                [Page 6]


Internet-Draft               PIDF Over XMPP                  August 2005


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Saint-Andre             Expires February 9, 2006                [Page 7]


Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/