idnits 2.17.1 draft-ietf-xmpp-resourceprep-01.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 21, 2003) is 7728 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) ** Obsolete normative reference: RFC 3454 (ref. '1') (Obsoleted by RFC 7564) == Outdated reference: A later version (-24) exists of draft-ietf-xmpp-core-03 -- Possible downref: Non-RFC (?) normative reference: ref. '4' Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 3 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 22, 2003 J. Hildebrand 5 Jabber, Inc. 6 February 21, 2003 8 Resourceprep: A Stringprep Profile for Resource Identifiers in XMPP 9 draft-ietf-xmpp-resourceprep-01 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 22, 2003. 34 Copyright Notice 36 Copyright (C) The Internet Society (2003). All Rights Reserved. 38 Abstract 40 This document defines a stringprep profile for resource identifiers 41 in 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 A. Revision History . . . . . . . . . . . . . . . . . . . . . . . 13 59 A.1 Changes from draft-ietf-xmpp-resourceprep-00 . . . . . . . . . 13 60 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 14 62 1. Introduction 64 This document, which defines a profile of stringprep (RFC 3454 [1]), 65 specifies processing rules that will enable users to enter 66 internationalized resource identifiers in XMPP (see XMPP Core [2]) 67 and have the highest chance of getting the content of the strings 68 correct. These processing rules are intended for XMPP resource 69 identifiers only, and not for arbitrary text. 71 This profile defines the following, as required by RFC 3454 [1]: 73 o The intended applicability of the profile: internationalized 74 resource identifiers within XMPP 76 o The character repertoire that is the input and output to 77 stringprep: Unicode 3.2, specified in section 2 79 o The mappings used: specified in section 3 81 o The Unicode normalization used: specified in section 4 83 o The characters that are prohibited as output: specified in section 84 5 86 o Bidirectional character handling: specified in section 6 88 1.1 Terminology 90 This document inherits the terminology defined in XMPP Core [2]. 92 The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 93 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 94 "OPTIONAL" in this document are to be interpreted as described in RFC 95 2119 [3]. 97 1.2 Discussion Venue 99 The authors welcome discussion and comments related to the topics 100 presented in this document. The preferred forum is the 101 mailing list, for which archives and subscription 102 information are available at . 105 1.3 Intellectual Property Notice 107 This document is in full compliance with all provisions of Section 10 108 of RFC 2026. Parts of this specification use the term "jabber" for 109 identifying namespaces and other protocol syntax. Jabber[tm] is a 110 registered trademark of Jabber, Inc. Jabber, Inc. grants permission 111 to the IETF for use of the Jabber trademark in association with this 112 specification and its successors, if any. 114 2. Character Repertoire 116 This profile uses Unicode 3.2 with the list of unassigned code points 117 being Table A.1, both defined in Appendix A of RFC 3454 [1]. 119 3. Mapping 121 This profile specifies mapping using the following tables from RFC 122 3454 [1]: 124 Table B.1 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.2 138 Table C.2.1 140 Table C.2.2 142 Table C.3 144 Table C.4 146 Table C.5 148 Table C.6 150 Table C.7 152 Table C.8 154 Table C.9 156 6. Bidirectional Characters 158 This profile specifies checking bidirectional strings as described in 159 section 6 of RFC 3454 [1]. 161 7. Security Considerations 163 The Unicode and ISO/IEC 10646 repertoires have many characters that 164 look similar. In many cases, users of security protocols might do 165 visual matching, such as when comparing the names of trusted third 166 parties. Because it is impossible to map similar-looking characters 167 without a great deal of context such as knowing the fonts used, 168 stringprep does nothing to map similar-looking characters together 169 nor to prohibit some characters because they look like others. 171 Resource identifiers are commonly employed as session names for users 172 who connect to XMPP servers for instant messaging and presence 173 services. The usability of such services could be compromised if a 174 user entering a single internationalized resource identifier could 175 attempt to initiate multiple sessions with the same name based on 176 different interpretations of the internationalized resource 177 identifier; however, it is unlikely that such a confusion would 178 compromise security. 180 8. IANA Considerations 182 This is a profile of stringprep. If and when it becomes an RFC, it 183 should be registered in the stringprep profile registry maintained by 184 the IANA [4]. 186 Name of this profile: 188 Resourceprep 190 RFC in which the profile is defined: 192 This document 194 Indicator whether or not this is the newest version of the profile: 196 This is the first version of Resourceprep 198 References 200 [1] Hoffman, P. and M. Blanchet, "Preparation of Internationalized 201 Strings ("stringprep")", RFC 3454, December 2002. 203 [2] Saint-Andre, P. and J. Miller, "XMPP Core (draft-ietf-xmpp-core- 204 03, work in progress)", February 2003. 206 [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement 207 Levels", BCP 14, RFC 2119, March 1997. 209 [4] Internet Assigned Numbers Authority, "Internet Assigned Numbers 210 Authority", January 1998, . 212 Authors' Addresses 214 Peter Saint-Andre 215 Jabber Software Foundation 217 EMail: stpeter@jabber.org 218 URI: http://www.jabber.org/people/stpeter.php 220 Joe Hildebrand 221 Jabber, Inc. 223 EMail: jhildebrand@jabber.com 224 URI: http://www.jabber.org/people/hildjj.php 226 Appendix A. Revision History 228 Note to RFC editor: please remove this entire appendix, and the 229 corresponding entries in the table of contents, prior to publication. 231 A.1 Changes from draft-ietf-xmpp-resourceprep-00 233 o Clarified references to Unicode 3.2 and unassigned code points. 235 o Corrected normalization routine. 237 o Removed reference to section B.2 of RFC 3454 (no case folding 238 required). 240 Full Copyright Statement 242 Copyright (C) The Internet Society (2003). All Rights Reserved. 244 This document and translations of it may be copied and furnished to 245 others, and derivative works that comment on or otherwise explain it 246 or assist in its implementation may be prepared, copied, published 247 and distributed, in whole or in part, without restriction of any 248 kind, provided that the above copyright notice and this paragraph are 249 included on all such copies and derivative works. However, this 250 document itself may not be modified in any way, such as by removing 251 the copyright notice or references to the Internet Society or other 252 Internet organizations, except as needed for the purpose of 253 developing Internet standards in which case the procedures for 254 copyrights defined in the Internet Standards process must be 255 followed, or as required to translate it into languages other than 256 English. 258 The limited permissions granted above are perpetual and will not be 259 revoked by the Internet Society or its successors or assigns. 261 This document and the information contained herein is provided on an 262 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 263 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 264 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 265 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 266 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 268 Acknowledgement 270 Funding for the RFC Editor function is currently provided by the 271 Internet Society.