idnits 2.17.1 draft-mayrhofer-enum-xmpp-00.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 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 241. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 252. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 259. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 265. ** 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 issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. 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 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 (September 29, 2006) is 6412 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3761 (ref. '1') (Obsoleted by RFC 6116, RFC 6117) ** Obsolete normative reference: RFC 4622 (ref. '5') (Obsoleted by RFC 5122) ** Obsolete normative reference: RFC 3920 (ref. '6') (Obsoleted by RFC 6120) Summary: 6 errors (**), 0 flaws (~~), 1 warning (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ENUM -- Telephone Number Mapping A. Mayrhofer 3 Working Group enum.at 4 Internet-Draft September 29, 2006 5 Intended status: Informational 6 Expires: April 2, 2007 8 IANA Registration for Enumservice 'XMPP' 9 draft-mayrhofer-enum-xmpp-00 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on April 2, 2007. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This document requests IANA registration of an Enumservice for 43 Extensible Messaging and Presence Protocol (XMPP) Uniform Resource 44 Identifiers (URIs) according to the registration procedure outlined 45 in RFC 3761. 47 Table of Contents 49 1. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 3. ENUM-specific XMPP considerations . . . . . . . . . . . . . . . 3 55 4. ENUM Service Registration - XMPP . . . . . . . . . . . . . . . 4 57 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6. Security & Privacy Considerations . . . . . . . . . . . . . . . 4 61 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 63 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 65 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 9.1. Normative References . . . . . . . . . . . . . . . . . . . 5 67 9.2. Informative References . . . . . . . . . . . . . . . . . . 5 69 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 Intellectual Property and Copyright Statements . . . . . . . . . . 7 72 1. Change Log 74 [Note to editors: This section is to be removed before publication - 75 XML source available on request] 77 draft-mayrhofer-enum-xmpp-00 78 initial draft 80 2. Introduction 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 84 document are to be interpreted as described in RFC 2119 [3]. 86 E.164 Number Mapping (ENUM) [1] uses the Domain Name System (DNS) [7] 87 to refer from E.164 numbers [2] to Uniform Resource Identifiers 88 (URIs) [4]. The registration process for Enumservices is described 89 in section 3 of RFC 3761. 91 The Extensible Messaging and Presence Protocol (XMPP) [6] provides 92 means for streaming Extensible Markup Language (XML) [8] elements 93 between endpoints in close to real time. The XMPP framework is 94 mainly used to provide instant messaging, presence and streaming 95 media services. 97 RFC 4622 [5] registers an Internationalized Resource Identifier (IRI) 98 and URI scheme for identifying XMPP entities. The Enumservice 99 specified in this document allows the use of such "xmpp" IRIs/URIs in 100 the context of ENUM. 102 3. ENUM-specific XMPP considerations 104 XMPP IRIs/URIs optionally contain an "Authority Component" (see 105 section 2.3 of RFC 4622). The presence of such an Authority 106 Component in an IRI/URI signals the processing application to 107 authenticate as the user indicated in the URI/IRI rather than using 108 the preconfigured identity. 110 In the context of this Enumservice, random clients may discover and 111 use the XMPP URIs/IRIs associated to an E.164 number, hence in most 112 cases those clients will not be able to authenticate as requested in 113 the Authority Component. 115 Therefore, URIs/IRIs results from processing an XMPP Enumservice 116 records SHOULD NOT contain an Authority Component. 118 4. ENUM Service Registration - XMPP 120 Enumservice Name: "XMPP" 122 Enumservice Type: "xmpp" 124 Enumservice Subtype: n/a 126 URI Schemes: "xmpp" 128 Functional Specification: 129 This Enumservice indicates that the resource identified is an XMPP 130 IRI/URI. 132 Security Considerations: see Section 6 134 Intended Usage: COMMON 136 Author: Alexander Mayrhofer 138 5. Example 140 An example ENUM entry referencing to a XMPP URI could look like: 142 $ORIGIN 6.4.9.0.6.4.9.7.0.2.4.4.e164.arpa. 143 @ IN NAPTR 100 10 "u" "E2U+xmpp" 144 "!^.*$!xmpp:some-user@example.com!" . 146 (Note: Due to line length constraints, the example record above is 147 split in two lines) 149 6. Security & Privacy Considerations 151 Since ENUM uses DNS - a publicly available database - any information 152 contained in records provisioned in ENUM domains must be considered 153 public as well. Even after revoking the DNS entry and removing the 154 refered resource, copies of the information could still be available. 156 Information published in ENUM records could reveal associations 157 between E.164 numbers and their owners - especially if IRIs/URIs 158 contain personal identifiers or domain names for which ownership 159 information can be obtained easily. 161 However, it is important to note that the ENUM record itself does not 162 need to contain any personal information. It just points to a 163 location where access to personal information could be granted. 165 ENUM records pointing to third party resources can easily be 166 provisioned on purpose by the ENUM domain owner - so any assumption 167 about the association between a number and an entity could therefore 168 be completely bogus unless some kind of identity verification is in 169 place. This verification is out of scope for this memo. 171 7. IANA Considerations 173 This memo requests registration of the "XMPP" Enumservice according 174 to the definitions in this document and RFC 3761 [1]. 176 8. Acknowledgements 178 Some text from RFC 4622 was used in the Introduction section of this 179 document. 181 9. References 183 9.1. Normative References 185 [1] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource 186 Identifiers (URI) Dynamic Delegation Discovery System (DDDS) 187 Application (ENUM)", RFC 3761, April 2004. 189 [2] ITU-T, "The international public telecommunication numbering 190 plan", Recommendation E.164 (02/05), Feb 2005. 192 [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement 193 Levels", BCP 14, RFC 2119, March 1997. 195 [4] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 196 Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, 197 January 2005. 199 [5] Saint-Andre, P., "Internationalized Resource Identifiers (IRIs) 200 and Uniform Resource Identifiers (URIs) for the Extensible 201 Messaging and Presence Protocol (XMPP)", RFC 4622, August 2006. 203 [6] Saint-Andre, P., Ed., "Extensible Messaging and Presence 204 Protocol (XMPP): Core", RFC 3920, October 2004. 206 9.2. Informative References 208 [7] Mockapetris, P., "Domain names - Implementation and 209 Specification", STD 13, RFC 1035, November 1987. 211 [8] Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T., and E. 212 Maler, "Extensible Markup Language (XML) 1.0 (Third Edition)", 213 W3C REC REC-xml-20040204, February 2004. 215 Author's Address 217 Alexander Mayrhofer 218 enum.at GmbH 219 Karlsplatz 1/9 220 Wien A-1010 221 Austria 223 Phone: +43 1 5056416 34 224 Email: alexander.mayrhofer@enum.at 225 URI: http://www.enum.at/ 227 Full Copyright Statement 229 Copyright (C) The Internet Society (2006). 231 This document is subject to the rights, licenses and restrictions 232 contained in BCP 78, and except as set forth therein, the authors 233 retain all their rights. 235 This document and the information contained herein are provided on an 236 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 237 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 238 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 239 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 240 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 241 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 243 Intellectual Property 245 The IETF takes no position regarding the validity or scope of any 246 Intellectual Property Rights or other rights that might be claimed to 247 pertain to the implementation or use of the technology described in 248 this document or the extent to which any license under such rights 249 might or might not be available; nor does it represent that it has 250 made any independent effort to identify any such rights. Information 251 on the procedures with respect to rights in RFC documents can be 252 found in BCP 78 and BCP 79. 254 Copies of IPR disclosures made to the IETF Secretariat and any 255 assurances of licenses to be made available, or the result of an 256 attempt made to obtain a general license or permission for the use of 257 such proprietary rights by implementers or users of this 258 specification can be obtained from the IETF on-line IPR repository at 259 http://www.ietf.org/ipr. 261 The IETF invites any interested party to bring to its attention any 262 copyrights, patents or patent applications, or other proprietary 263 rights that may cover technology that may be required to implement 264 this standard. Please address the information to the IETF at 265 ietf-ipr@ietf.org. 267 Acknowledgment 269 Funding for the RFC Editor function is provided by the IETF 270 Administrative Support Activity (IASA).