idnits 2.17.1 draft-ietf-xmpp-nodeprep-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. 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 (February 03, 2003) is 7752 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3454 (ref. '1') (Obsoleted by RFC 7564) == Outdated reference: A later version (-24) exists of draft-ietf-xmpp-core-02 -- Possible downref: Non-RFC (?) normative reference: ref. '4' Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 4 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 Jabber Software Foundation 4 Expires: August 4, 2003 J. Hildebrand 5 Jabber, Inc. 6 February 03, 2003 8 Nodeprep: A Stringprep Profile for Node Identifiers in XMPP 9 draft-ietf-xmpp-nodeprep-00 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at http:// 27 www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on August 4, 2003. 34 Copyright Notice 36 Copyright (C) The Internet Society (2003). All Rights Reserved. 38 Abstract 40 This document defines a stringprep profile for node identifiers in 41 the eXtensible Messaging and Presence Protocol (XMPP). 43 Table of Contents 45 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 46 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 1.2 Discussion Venue . . . . . . . . . . . . . . . . . . . . . . . 3 48 1.3 Intellectual Property Notice . . . . . . . . . . . . . . . . . 3 49 2. Character Repertoire . . . . . . . . . . . . . . . . . . . . . 5 50 3. Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 51 4. Normalization . . . . . . . . . . . . . . . . . . . . . . . . 7 52 5. Prohibited Output . . . . . . . . . . . . . . . . . . . . . . 8 53 6. Bidirectional Characters . . . . . . . . . . . . . . . . . . . 9 54 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 55 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 56 References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12 58 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 13 60 1. Introduction 62 This document, which defines a profile of stringprep (RFC 3454 [1]), 63 specifies processing rules that will enable users to enter 64 internationalized node identifiers in XMPP (see XMPP Core [2]) and 65 have the highest chance of getting the content of the strings 66 correct. These processing rules are intended for XMPP node 67 identifiers only, and not for arbitrary text. 69 This profile defines the following, as required by RFC 3454 [1]: 71 o The intended applicability of the profile: internationalized node 72 identifiers within XMPP 74 o The character repertoire that is the input and output to 75 stringprep: Unicode 3.2, specified in section 2 77 o The mappings used: specified in section 3 79 o The Unicode normalization used: specified in section 4 81 o The characters that are prohibited as output: specified in section 82 5 84 o Bidirectional character handling: specified in section 6 86 1.1 Terminology 88 This document inherits the terminology defined in XMPP Core [2]. 90 The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 91 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 92 "OPTIONAL" in this document are to be interpreted as described in RFC 93 2119 [3]. 95 1.2 Discussion Venue 97 The authors welcome discussion and comments related to the topics 98 presented in this document. The preferred forum is the 99 mailing list, for which archives and subscription 100 information are available at . 103 1.3 Intellectual Property Notice 105 This document is in full compliance with all provisions of Section 10 106 of RFC 2026. Parts of this specification use the term "jabber" for 107 identifying namespaces and other protocol syntax. Jabber[tm] is a 108 registered trademark of Jabber, Inc. Jabber, Inc. grants permission 109 to the IETF for use of the Jabber trademark in association with this 110 specification and its successors, if any. 112 2. Character Repertoire 114 This profile uses Unicode 3.2, as defined in Appendix A.1 of RFC 3454 115 [1]. 117 3. Mapping 119 This profile specifies mapping using the following tables from RFC 120 3454 [1]: 122 Table B.1 124 Table B.2 126 4. Normalization 128 This profile specifies using Unicode normalization form KC, as 129 described in RFC 3454 [1]. 131 5. Prohibited Output 133 This profile specifies prohibiting use of the following tables from 134 RFC 3454 [1]. 136 Table C.1.1 138 Table C.1.2 140 Table C.2.1 142 Table C.2.2 144 Table C.3 146 Table C.4 148 Table C.5 150 Table C.6 152 Table C.7 154 Table C.8 156 Table C.9 158 In addition, the following Unicode characters are also prohibited: 160 #x22 (") 162 #x26 (&) 164 #x27 (') 166 #x2F (/) 168 #x3A (:) 170 #x3C (<) 172 #x3E (>) 174 #x40 (@) 176 6. Bidirectional Characters 178 This profile specifies checking bidirectional strings as described in 179 section 6 of RFC 3454 [1]. 181 7. Security Considerations 183 The Unicode and ISO/IEC 10646 repertoires have many characters that 184 look similar. In many cases, users of security protocols might do 185 visual matching, such as when comparing the names of trusted third 186 parties. Because it is impossible to map similar-looking characters 187 without a great deal of context such as knowing the fonts used, 188 stringprep does nothing to map similar-looking characters together 189 nor to prohibit some characters because they look like others. 191 Node identifiers are commonly employed as the username of users who 192 connect to XMPP servers for instant messaging and presence services. 193 The security of such services could be compromised if a user entering 194 a single internationalized node identifier could access another 195 user's account information based on different interpretations of the 196 internationalized node identifier. 198 8. IANA Considerations 200 This is a profile of stringprep. If and when it becomes an RFC, it 201 should be registered in the stringprep profile registry maintained by 202 the IANA [4]. 204 Name of this profile: 206 Nodeprep 208 RFC in which the profile is defined: 210 This document 212 Indicator whether or not this is the newest version of the profile: 214 This is the first version of Nodeprep 216 References 218 [1] Hoffman, P. and M. Blanchet, "Preparation of Internationalized 219 Strings ("stringprep")", RFC 3454, December 2002. 221 [2] Saint-Andre, P. and J. Miller, "XMPP Core (draft-ietf-xmpp-core- 222 02, work in progress)", February 2003. 224 [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement 225 Levels", BCP 14, RFC 2119, March 1997. 227 [4] Internet Assigned Numbers Authority, "Internet Assigned Numbers 228 Authority", January 1998, . 230 Authors' Addresses 232 Peter Saint-Andre 233 Jabber Software Foundation 235 EMail: stpeter@jabber.org 236 URI: http://www.jabber.org/people/stpeter.php 238 Joe Hildebrand 239 Jabber, Inc. 241 EMail: jhildebrand@jabber.com 242 URI: http://www.jabber.org/people/hildjj.php 244 Full Copyright Statement 246 Copyright (C) The Internet Society (2003). All Rights Reserved. 248 This document and translations of it may be copied and furnished to 249 others, and derivative works that comment on or otherwise explain it 250 or assist in its implementation may be prepared, copied, published 251 and distributed, in whole or in part, without restriction of any 252 kind, provided that the above copyright notice and this paragraph are 253 included on all such copies and derivative works. However, this 254 document itself may not be modified in any way, such as by removing 255 the copyright notice or references to the Internet Society or other 256 Internet organizations, except as needed for the purpose of 257 developing Internet standards in which case the procedures for 258 copyrights defined in the Internet Standards process must be 259 followed, or as required to translate it into languages other than 260 English. 262 The limited permissions granted above are perpetual and will not be 263 revoked by the Internet Society or its successors or assigns. 265 This document and the information contained herein is provided on an 266 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 267 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 268 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 269 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 270 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 272 Acknowledgement 274 Funding for the RFC Editor function is currently provided by the 275 Internet Society.