idnits 2.17.1 draft-saintandre-xmpp-pidf-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 243. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 220. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 227. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 233. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 31, 2006) is 6653 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' -- Possible downref: Non-RFC (?) normative reference: ref. 'XML-NAMES' ** Obsolete normative reference: RFC 3920 (ref. 'XMPP-CORE') (Obsoleted by RFC 6120) ** Obsolete normative reference: RFC 3921 (ref. 'XMPP-IM') (Obsoleted by RFC 6121) == Outdated reference: A later version (-10) exists of draft-saintandre-xmpp-simple-05 Summary: 6 errors (**), 0 flaws (~~), 4 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Saint-Andre 3 Internet-Draft JSF 4 Expires: August 4, 2006 January 31, 2006 6 Transporting Presence Information Data Format (PIDF) over the Extensible 7 Messaging and Presence Protocol (XMPP) 8 draft-saintandre-xmpp-pidf-03 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on August 4, 2006. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 This document defines how to send information encoded in the Presence 42 Information Data Format (PIDF) over the Extensible Messaging and 43 Presence Protocol (XMPP). 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 2. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 50 4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 51 4.1 Normative References . . . . . . . . . . . . . . . . . . . 5 52 4.2 Informative References . . . . . . . . . . . . . . . . . . 5 53 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6 54 Intellectual Property and Copyright Statements . . . . . . . . 7 56 1. Introduction 58 1.1 Overview 60 The Presence Information Data Format ([PIDF]) defines a common data 61 format for presence protocols that conform to the Common Profile for 62 Presence ([CPP]), enabling presence information to be transferred 63 across CPP-compliant protocol boundaries without modification, with 64 attendant benefits for end-to-end encryption and performance. 65 Because the syntax for PIDF is Extensible Markup Language [XML], it 66 should be straightforward to send PIDF data over the Extensible 67 Messaging and Presence Protocol (XMPP) [XMPP-CORE], since XMPP is 68 simply an XML streaming protocol. This memo defines a mechanism for 69 encapsulating PIDF data within an "extended namespace" contained in 70 an XMPP presence stanza. 72 1.2 Terminology 74 This document inherits terminology defined in [PIDF], [XMPP-CORE], 75 and [XMPP-IM]. 77 The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 78 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 79 "OPTIONAL" in this document are to be interpreted as described in RFC 80 2119 [TERMS]. 82 2. Protocol 84 The PIDF format is defined in [PIDF]. Briefly, the XML namespace 85 name is 'urn:ietf:params:xml:ns:pidf', the root element is 86 , the element must possess an 'entity' 87 attribute that specifies the pres: URI (see [CPP]) that identifies 88 the presentity (see [RFC2778]) to which the PIDF data relates, and 89 the element may contain any number of child 90 elements specifying information about the entity. 92 The recommended method for encapsulating PIDF data within an XMPP 93 presence stanza is by including the PIDF element as a 94 child of the XMPP stanza. Although it may appear that 95 this is potentially confusing, the inclusion of the 96 'urn:ietf:params:xml:ns:pidf' namespace ensures that PIDF data is 97 kept separate from XMPP presence data (in accordance with [XML- 98 NAMES]). The following is a simple example of encapsulating PIDF 99 data within an "extended namespace" in XMPP: 101 A basic example of PIDF over XMPP: 103 104 dnd 105 Wooing Juliet 106 108 109 110 open 111 112 113 114 116 Because base PIDF data does not encapsulate any additional 117 information over and above XMPP presence stanzas, there is little 118 point to including it in native XMPP systems when it is not encrypted 119 (obviously, encrypting PIDF data can help to ensure end-to-end 120 encryption of presence information, as described in [XMPP-E2E], 121 especially across boundaries between CPP-compliant systems such as 122 those described in [XMPP-SIMPLE]). The power of PIDF in the context 123 of XMPP derives from PIDF extensions, such as those for rich presence 124 (see [RPID]) and geographical location (see [GEOLOC]). Any such 125 extension to PIDF can be included in an XMPP presence stanza, since, 126 according to the definition of "extended namespaces" in [XMPP-IM], 127 the format of such extended data is defined by the extension rather 128 than by the base XMPP specification itself. Thus the ability to 129 include PIDF data and PIDF data extensions in XMPP enables XMPP-aware 130 applications to include any PIDF-compatible data that is currently 131 defined or that may be defined in the future. Naturally, there is no 132 guarantee that all XMPP entities will be able to understand such PIDF 133 data, and entities that do not understand the data MUST ignore it (in 134 accordance with [XMPP-CORE]). However, this memo at least defines a 135 mechanism for including PIDF data, which XMPP applications are 136 encouraged to implement if they desire to make use of PIDF data 137 extensions for rich presence, geographical location, and other kinds 138 of presence-related information. 140 3. Security Considerations 142 This memo introduces no new security considerations above and beyond 143 those provided for PIDF in [PIDF] and for XMPP in [XMPP-CORE]. 145 4. References 146 4.1 Normative References 148 [CPP] Peterson, J., "Common Profile for Presence (CPP)", 149 RFC 3859, August 2004. 151 [PIDF] Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, 152 W., and J. Peterson, "Presence Information Data Format 153 (PIDF)", RFC 3863, August 2004. 155 [TERMS] Bradner, S., "Key words for use in RFCs to Indicate 156 Requirement Levels", BCP 14, RFC 2119, March 1997. 158 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler, 159 "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC- 160 xml, October 2000, . 162 [XML-NAMES] 163 Bray, T., Hollander, D., and A. Layman, "Namespaces in 164 XML", W3C REC-xml-names, January 1999, 165 . 167 [XMPP-CORE] 168 Saint-Andre, P., "Extensible Messaging and Presence 169 Protocol (XMPP): Core", RFC 3920, October 2004. 171 [XMPP-E2E] 172 Saint-Andre, P., "End-to-End Signing and Object Encryption 173 for the Extensible Messaging and Presence Protocol 174 (XMPP)", RFC 3923, October 2004. 176 [XMPP-IM] Saint-Andre, P., "Extensible Messaging and Presence 177 Protocol (XMPP): Instant Messaging and Presence", 178 RFC 3921, October 2004. 180 4.2 Informative References 182 [GEOLOC] Peterson, J., "A Presence-based GEOPRIV Location Object 183 Format", RFC 4119, December 2005. 185 [RFC2778] Day, M., Rosenberg, J., and H. Sugano, "A Model for 186 Presence and Instant Messaging", RFC 2778, February 2000. 188 [RPID] Schulzrinne, H., "RPID: Rich Presence Extensions to the 189 Presence Information Data Format (PIDF)", 190 draft-ietf-simple-rpid-10 (work in progress), 191 December 2005. 193 [XMPP-SIMPLE] 194 Saint-Andre, P., "Basic Messaging and Presence 195 Interoperability between the Extensible Messaging and 196 Presence Protocol (XMPP) and Session Initiation Protocol 197 (SIP) for Instant Messaging and Presence Leveraging 198 Extensions (SIMPLE)", draft-saintandre-xmpp-simple-05 199 (work in progress), August 2005. 201 Author's Address 203 Peter Saint-Andre 204 Jabber Software Foundation 205 P.O. Box 1641 206 Denver, CO 80201 207 US 209 Email: stpeter@jabber.org 211 Intellectual Property Statement 213 The IETF takes no position regarding the validity or scope of any 214 Intellectual Property Rights or other rights that might be claimed to 215 pertain to the implementation or use of the technology described in 216 this document or the extent to which any license under such rights 217 might or might not be available; nor does it represent that it has 218 made any independent effort to identify any such rights. Information 219 on the procedures with respect to rights in RFC documents can be 220 found in BCP 78 and BCP 79. 222 Copies of IPR disclosures made to the IETF Secretariat and any 223 assurances of licenses to be made available, or the result of an 224 attempt made to obtain a general license or permission for the use of 225 such proprietary rights by implementers or users of this 226 specification can be obtained from the IETF on-line IPR repository at 227 http://www.ietf.org/ipr. 229 The IETF invites any interested party to bring to its attention any 230 copyrights, patents or patent applications, or other proprietary 231 rights that may cover technology that may be required to implement 232 this standard. Please address the information to the IETF at 233 ietf-ipr@ietf.org. 235 Disclaimer of Validity 237 This document and the information contained herein are provided on an 238 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 239 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 240 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 241 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 242 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 243 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 245 Copyright Statement 247 Copyright (C) The Internet Society (2006). This document is subject 248 to the rights, licenses and restrictions contained in BCP 78, and 249 except as set forth therein, the authors retain all their rights. 251 Acknowledgment 253 Funding for the RFC Editor function is currently provided by the 254 Internet Society.