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

Versions: 00 01 02 03

Network Working Group                                     P. Saint-Andre
Internet-Draft                                Jabber Software Foundation
Expires: August 6, 2004                                 February 6, 2004


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

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   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 August 6, 2004.

Copyright Notice

   Copyright (C) The Internet Society (2004). All Rights Reserved.

Abstract

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












Saint-Andre              Expires August 6, 2004                 [Page 1]


Internet-Draft               PIDF Over XMPP                February 2004


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   1.1 Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   1.2 Discussion Venue . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  4
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
       Normative References . . . . . . . . . . . . . . . . . . . . .  5
       Informative References . . . . . . . . . . . . . . . . . . . .  5
       Author's Address . . . . . . . . . . . . . . . . . . . . . . .  6
       Intellectual Property and Copyright Statements . . . . . . . .  7







































Saint-Andre              Expires August 6, 2004                 [Page 2]


Internet-Draft               PIDF Over XMPP                February 2004


1. Introduction

   The Presence Information Data Format ([PIDF]) defines a common
   presence 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 security and performance.
   Because the syntax for PIDF is XML [XML], it should be
   straightforward to send PIDF data over the Extensible Messaging and
   Presence Protocol [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.1 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].

1.2 Discussion Venue

   The author welcomes discussion and comments related to the topics
   presented in this document.  The preferred forum is the
   <xmppwg@jabber.org> mailing list, for which archives and subscription
   information are available at <http://www.jabber.org/cgi-bin/mailman/
   listinfo/xmppwg/>.

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, and
   the <presence/> element may contain any number of <tuple/> child
   elements specying information about an 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 August 6, 2004                 [Page 3]


Internet-Draft               PIDF Over XMPP                February 2004


   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 extensions thereto,
   such as the rich presence formats described in [RPID] and the
   geographical location formats described in [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;
   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. IANA Considerations

   This document requires no action on the part of the IANA.

4. Security Considerations

   Detailed security considerations for XMPP are given in XMPP Core
   [XMPP-CORE].

Normative References



Saint-Andre              Expires August 6, 2004                 [Page 4]


Internet-Draft               PIDF Over XMPP                February 2004


   [CPP]      Peterson, J., "Common Profile for Presence (CPP)",
              draft-ietf-impp-pres-04 (work in progress), August 2003.

   [PIDF]     Fujimoto, S., Sugano, H., Klyne, G., Bateman, A., Carr, W.
              and J. Peterson, "Presence Information Data Format
              (PIDF)", draft-ietf-impp-cpim-pidf-08 (work in progress),
              May 2003.

   [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", draft-ietf-xmpp-core-22 (work in
              progress), January 2004.

   [XMPP-E2E]
              Saint-Andre, P., "End-to-End Object Encryption in the
              Extensible Messaging and Presence Protocol (XMPP)",
              draft-ietf-xmpp-e2e-07 (work in progress), December 2003.

   [XMPP-IM]  Saint-Andre, P., "Extensible Messaging and Presence
              Protocol (XMPP): Instant Messaging and Presence",
              draft-ietf-xmpp-im-21 (work in progress), January 2004.

Informative References

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

   [RPID]    Schulzrinne, H., "RPID -- Rich Presence Information Data
             Format", draft-ietf-simple-rpid-00 (work in progress), July
             2003.








Saint-Andre              Expires August 6, 2004                 [Page 5]


Internet-Draft               PIDF Over XMPP                February 2004


Author's Address

   Peter Saint-Andre
   Jabber Software Foundation

   EMail: stpeter@jabber.org













































Saint-Andre              Expires August 6, 2004                 [Page 6]


Internet-Draft               PIDF Over XMPP                February 2004


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property 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; neither does it represent that it
   has made any effort to identify any such rights. Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11. Copies of
   claims of rights made available for publication 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 implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard. Please address the information to the IETF Executive
   Director.


Full Copyright Statement

   Copyright (C) The Internet Society (2004). All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assignees.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION



Saint-Andre              Expires August 6, 2004                 [Page 7]


Internet-Draft               PIDF Over XMPP                February 2004


   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Acknowledgment

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











































Saint-Andre              Expires August 6, 2004                 [Page 8]


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