idnits 2.17.1 draft-ietf-xmpp-resourceprep-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 7754 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-02 -- 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 4, 2003 J. Hildebrand 5 Jabber, Inc. 6 February 03, 2003 8 Resourceprep: A Stringprep Profile for Resource Identifiers in XMPP 9 draft-ietf-xmpp-resourceprep-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 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 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 resource identifiers in XMPP (see XMPP Core [2]) 65 and have the highest chance of getting the content of the strings 66 correct. These processing rules are intended for XMPP resource 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 72 resource 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 no normalization. 130 5. Prohibited Output 132 This profile specifies prohibiting use of the following tables from 133 RFC 3454 [1]. 135 Table C.1.2 137 Table C.2.1 139 Table C.2.2 141 Table C.3 143 Table C.4 145 Table C.5 147 Table C.6 149 Table C.7 151 Table C.8 153 Table C.9 155 6. Bidirectional Characters 157 This profile specifies checking bidirectional strings as described in 158 section 6 of RFC 3454 [1]. 160 7. Security Considerations 162 The Unicode and ISO/IEC 10646 repertoires have many characters that 163 look similar. In many cases, users of security protocols might do 164 visual matching, such as when comparing the names of trusted third 165 parties. Because it is impossible to map similar-looking characters 166 without a great deal of context such as knowing the fonts used, 167 stringprep does nothing to map similar-looking characters together 168 nor to prohibit some characters because they look like others. 170 Resource identifiers are commonly employed as session names for users 171 who connect to XMPP servers for instant messaging and presence 172 services. The usability of such services could be compromised if a 173 user entering a single internationalized resource identifier could 174 attempt to initiate multiple sessions with the same name based on 175 different interpretations of the internationalized resource 176 identifier; however, it is unlikely that such a confusion would 177 compromise security. 179 8. IANA Considerations 181 This is a profile of stringprep. If and when it becomes an RFC, it 182 should be registered in the stringprep profile registry maintained by 183 the IANA [4]. 185 Name of this profile: 187 Resourceprep 189 RFC in which the profile is defined: 191 This document 193 Indicator whether or not this is the newest version of the profile: 195 This is the first version of Resourceprep 197 References 199 [1] Hoffman, P. and M. Blanchet, "Preparation of Internationalized 200 Strings ("stringprep")", RFC 3454, December 2002. 202 [2] Saint-Andre, P. and J. Miller, "XMPP Core (draft-ietf-xmpp-core- 203 02, work in progress)", February 2003. 205 [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement 206 Levels", BCP 14, RFC 2119, March 1997. 208 [4] Internet Assigned Numbers Authority, "Internet Assigned Numbers 209 Authority", January 1998, . 211 Authors' Addresses 213 Peter Saint-Andre 214 Jabber Software Foundation 216 EMail: stpeter@jabber.org 217 URI: http://www.jabber.org/people/stpeter.php 219 Joe Hildebrand 220 Jabber, Inc. 222 EMail: jhildebrand@jabber.com 223 URI: http://www.jabber.org/people/hildjj.php 225 Full Copyright Statement 227 Copyright (C) The Internet Society (2003). All Rights Reserved. 229 This document and translations of it may be copied and furnished to 230 others, and derivative works that comment on or otherwise explain it 231 or assist in its implementation may be prepared, copied, published 232 and distributed, in whole or in part, without restriction of any 233 kind, provided that the above copyright notice and this paragraph are 234 included on all such copies and derivative works. However, this 235 document itself may not be modified in any way, such as by removing 236 the copyright notice or references to the Internet Society or other 237 Internet organizations, except as needed for the purpose of 238 developing Internet standards in which case the procedures for 239 copyrights defined in the Internet Standards process must be 240 followed, or as required to translate it into languages other than 241 English. 243 The limited permissions granted above are perpetual and will not be 244 revoked by the Internet Society or its successors or assigns. 246 This document and the information contained herein is provided on an 247 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 248 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 249 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 250 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 251 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 253 Acknowledgement 255 Funding for the RFC Editor function is currently provided by the 256 Internet Society.