idnits 2.17.1 draft-ietf-sasl-saslprep-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: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 208 has weird spacing: '...for the purpo...' == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- 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 (24 February 2003) is 7726 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) == Missing Reference: 'RFC2119' is mentioned on line 72, but not defined == Missing Reference: 'Section 6' is mentioned on line 127, but not defined == Unused Reference: 'Keywords' is defined on line 154, but no explicit reference was found in the text == Unused Reference: 'CRAM-MD5' is defined on line 179, but no explicit reference was found in the text == Unused Reference: 'DIGEST-MD5' is defined on line 185, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3454 (ref. 'StringPrep') (Obsoleted by RFC 7564) -- No information found for draft-myers-saslrev-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'SASL' -- No information found for draft-nerenberg-sasl-crammd5-xx - is the name correct? -- No information found for draft-ietf-sasl-plain-xx - is the name correct? -- No information found for draft-ietf-sasl-rfc2831bis-xx - is the name correct? Summary: 6 errors (**), 0 flaws (~~), 7 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Editor: Kurt D. Zeilenga 3 Intended Category: Standards Track OpenLDAP Foundation 4 Expires in six months 24 February 2003 6 SASLprep: Stringprep profile for user names and passwords 7 9 Status of Memo 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. 14 This document is intended to be, after appropriate review and 15 revision, submitted to the RFC Editor as a Standards Track document. 16 Distribution of this memo is unlimited. Technical discussion of this 17 document will take place on the IETF SASL mailing list 18 . Please send editorial comments directly to the 19 document editor . 21 Internet-Drafts are working documents of the Internet Engineering Task 22 Force (IETF), its areas, and its working groups. Note that other 23 groups may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as ``work in progress.'' 29 The list of current Internet-Drafts can be accessed at 30 . The list of 31 Internet-Draft Shadow Directories can be accessed at 32 . 34 Copyright 2003, The Internet Society. All Rights Reserved. 36 Please see the Copyright section near the end of this document for 37 more information. 39 Abstract 41 This document describes how to prepare Unicode strings representing 42 user names and passwords for comparison. The document defines the 43 "SASLprep" "stringprep" profile to be used for both user names and 44 passwords. This profile is intended to be used by Simple 45 Authentication and Security Layer (SASL) mechanisms (such as PLAIN, 46 CRAM-MD5, and DIGEST-MD5) as well as other protocols exchanging user 47 names and/or passwords. 49 1. Introduction 51 The use of simple user names and passwords in authentication and 52 authorization is pervasive on the Internet. To increase the 53 likelyhood that user name and password input and comparsion work in 54 ways that make sense for typical users throughout the world, this 55 document defines rules for preparing internationalized user names and 56 passwords for comparison. For simplicity and implementation ease, a 57 single algorithm is defined for both user names and passwords. 59 This document defines the "SASLprep" profile of the "stringprep" 60 protocol [StringPrep]. 62 The profile is designed for use in Simple Authentication and Security 63 Layer ([SASL]) mechanisms such as [PLAIN]. It may be applicable 64 elsewhere user names and passwords are used. This profile is not 65 intended to be used for arbitrary text. 67 1.1. Conventions 69 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 70 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 71 document are to be interpreted as described in BCP 14 [RFC2119]. 73 Character names in this document use the notation for code points and 74 names from the Unicode Standard [Unicode]. For example, the letter 75 "a" may be represented as either or . 76 In the lists of mappings and the prohibited characters, the "U+" is 77 left off to make the lists easier to read. The comments for character 78 ranges are shown in square brackets (such as "[CONTROL CHARACTERS]") 79 and do not come from the standard. 81 Note: a glossary of terms used in Unicode can be found in [Glossary]. 82 Information on the Unicode character encoding model can be found in 83 [CharModel]. 85 2. The SASLprep profile 87 This section defines the "SASLprep" profile. This profile is intended 88 to be used to prepare strings representing user names and passwords. 90 2.1. Character Repertoire 91 This profile uses Unicode 3.2, as defined in [StringPrep, A.1]. 93 2.2. Mapping 95 This profile specifies: 96 - non-ASCII space characters [StringPrep, C.1.2] are to be mapped to 97 SPACE (U+0020), and 99 - the "commonly mapped to nothing" characters [StringPrep, B.1] are 100 to be mapped to nothing. 102 2.3. Normalization 104 This profile specifies using Unicode normalization form KC, as 105 described in Section 4 of [StringPrep]. 107 2.4. Prohibited Output 109 This profile specifies the following characters: 111 - Non-ASCII space characters [StringPrep, C.1.2], 112 - ASCII control charcters [StringPrep, C.2.1], 113 - Non-ASCII control characters [StringPrep, C.2.2], 114 - Private Use [StringPrep, C.3], 115 - Non-character code points [StringPrep, C.4], 116 - Surrogate code points [StringPrep, C.5], 117 - Inappropriate for plain text [StringPrep, C.6], 118 - Inappropriate for canonical representation [StringPrep, C.7], 119 - Change display properties or are deprecated [StringPrep, C.8], and 120 - Tagging characters [StringPrep, C.9]. 122 are prohibited output. 124 2.5. Bidirectional characters 126 This profile specifies checking bidirectional strings as described in 127 [StringPrep, Section 6]. 129 2.6. Unassigned Code Points 131 This profile specifies [StringPrep, A.1] table as its list of 132 unassigned code points. 134 3. IANA Considerations 136 This document details the "SASLprep" profile of [StringPrep] protocol. 137 Upon Standards Action, it should be registered in the stringprep 138 profile registry. 140 Name of this profile: SASLprep 141 RFC in which the profile is defined: This RFC 142 Indicator whether or not this is the newest version of the 143 profile: This is the first version of the User Name profile. 145 5. Acknowledgement 147 This document borrows text from "Preparation of Internationalized 148 Strings ('stringprep')" and "Nameprep: A Stringprep Profile for 149 Internationalized Domain Names", both by Paul Hoffman and Marc 150 Blanchet. 152 6. Normative References 154 [Keywords] S. Bradner, "Key words for use in RFCs to Indicate 155 Requirement Levels", BCP 14 (also RFC 2119), March 1997. 157 [StringPrep] P. Hoffman, M. Blanchet, "Preparation of 158 Internationalized Strings ("stringprep")", RFC 3454, 159 December 2002. 161 [SASL] J. Myers, "Simple Authentication and Security Layer 162 (SASL)", draft-myers-saslrev-xx.txt (a work in progress). 164 7. Informative References 166 [Unicode] The Unicode Consortium. The Unicode Standard, Version 167 3.2.0 is defined by The Unicode Standard, Version 3.0 168 (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), 169 as amended by the Unicode Standard Annex #27: Unicode 3.1 170 (http://www.unicode.org/reports/tr27/) and by the Unicode 171 Standard Annex #28: Unicode 3.2 172 (http://www.unicode.org/reports/tr28/). 174 [Glossary] Unicode Glossary, . 176 [CharModel] Unicode Technical Report;17, Character Encoding Model. 177 . 179 [CRAM-MD5] L. Nerenberg, "The CRAM-MD5 SASL Mechanism", 180 draft-nerenberg-sasl-crammd5-xx.txt (a work in progress). 182 [PLAIN] K. Zeilenga, "The Plain SASL Mechanism", 183 draft-ietf-sasl-plain-xx.txt (a work in progress). 185 [DIGEST-MD5] P. Leach, C. Newman, A. Melnikov, "Using Digest 186 Authentication as a SASL Mechanism", 187 draft-ietf-sasl-rfc2831bis-xx.txt (a work in progress). 189 8. Editor's Address 191 Kurt Zeilenga 192 OpenLDAP Foundation 194 Email: kurt@OpenLDAP.org 196 Full Copyright Statement 198 Copyright 2003, The Internet Society. All Rights Reserved. 200 This document and translations of it may be copied and furnished to 201 others, and derivative works that comment on or otherwise explain it 202 or assist in its implementation may be prepared, copied, published and 203 distributed, in whole or in part, without restriction of any kind, 204 provided that the above copyright notice and this paragraph are 205 included on all such copies and derivative works. However, this 206 document itself may not be modified in any way, such as by removing 207 the copyright notice or references to the Internet Society or other 208 Internet organizations, except as needed for the purpose of 209 developing Internet standards in which case the procedures for 210 copyrights defined in the Internet Standards process must be followed, 211 or as required to translate it into languages other than English. 213 The limited permissions granted above are perpetual and will not be 214 revoked by the Internet Society or its successors or assigns. 216 This document and the information contained herein is provided on an 217 "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET 218 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, 219 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 220 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 221 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.