idnits 2.17.1 draft-ietf-sasl-saslprep-05.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 253 has weird spacing: '...for the purpo...' -- 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 (15 February 2004) is 7366 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: 'Section 6' is mentioned on line 123, but not defined == Unused Reference: 'CRAM-MD5' is defined on line 203, but no explicit reference was found in the text == Unused Reference: 'DIGEST-MD5' is defined on line 206, but no explicit reference was found in the text -- No information found for draft-hoffman-rfc3454bis-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'StringPrep' -- No information found for draft-ietf-sasl-rfc2222bis-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'SASL' -- Possible downref: Non-RFC (?) normative reference: ref. 'Unicode' -- No information found for draft-ietf-sasl-crammd5-xx - is the name correct? -- No information found for draft-ietf-sasl-rfc2831bis-xx - is the name correct? -- No information found for draft-ietf-sasl-plain-xx - is the name correct? Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Kurt D. Zeilenga 3 Intended Category: Standards Track OpenLDAP Foundation 4 Expires: August 2004 15 February 2004 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 RFC 2026. 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 (C) The Internet Society (2004). All Rights Reserved. 36 Please see the Full Copyright section near the end of this document 37 for 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" profile of the "stringprep" algorithm to be used for both 44 user names and passwords. This profile is intended to be used by 45 Simple Authentication and Security Layer (SASL) mechanisms (such as 46 PLAIN, CRAM-MD5, and DIGEST-MD5) as well as other protocols exchanging 47 user 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 likelihood that user name and password input and comparison 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 algorithm [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 simple user names and passwords are used. This profile is 65 not intended to be used to prepare identity strings which are not 66 simple user names (e.g., e-mail addresses, domain names, distinguished 67 names), or where identity or password strings which are not character 68 data. 70 2. The SASLprep profile 72 This section defines the "SASLprep" profile. This profile is intended 73 to be used to prepare strings representing simple user names and 74 passwords. 76 This profile uses Unicode 3.2, as defined in [StringPrep, A.1]. 78 Character names in this document use the notation for code points and 79 names from the Unicode Standard [Unicode]. For example, the letter 80 "a" may be represented as either or . 81 In the lists of mappings and the prohibited characters, the "U+" is 82 left off to make the lists easier to read. The comments for character 83 ranges are shown in square brackets (such as "[CONTROL CHARACTERS]") 84 and do not come from the standard. 86 Note: a glossary of terms used in Unicode can be found in [Glossary]. 87 Information on the Unicode character encoding model can be found in 88 [CharModel]. 90 2.1. Mapping 91 This profile specifies: 92 - non-ASCII space characters [StringPrep, C.1.2] be mapped to SPACE 93 (U+0020), and 95 - the "commonly mapped to nothing" characters [StringPrep, B.1] be 96 mapped to nothing. 98 2.2. Normalization 100 This profile specifies using Unicode normalization form KC, as 101 described in Section 4 of [StringPrep]. 103 2.3. Prohibited Output 105 This profile specifies the following characters: 107 - Non-ASCII space characters [StringPrep, C.1.2], 108 - ASCII control characters [StringPrep, C.2.1], 109 - Non-ASCII control characters [StringPrep, C.2.2], 110 - Private Use [StringPrep, C.3], 111 - Non-character code points [StringPrep, C.4], 112 - Surrogate code points [StringPrep, C.5], 113 - Inappropriate for plain text [StringPrep, C.6], 114 - Inappropriate for canonical representation [StringPrep, C.7], 115 - Change display properties or are deprecated [StringPrep, C.8], and 116 - Tagging characters [StringPrep, C.9]. 118 are prohibited output. 120 2.4. Bidirectional characters 122 This profile specifies checking bidirectional strings as described in 123 [StringPrep, Section 6]. 125 2.5. Unassigned Code Points 127 This profile specifies [StringPrep, A.1] table as its list of 128 unassigned code points. 130 3. Security Considerations 132 This profile is intended to used to prepare simple user names and 133 passwords strings for comparison or use in cryptographic functions 134 (e.g., message digests). 136 It is not intended to be used for to prepare identity strings which 137 are not simple user names (e.g., distinguished names and domain 138 names). Nor is the profile intended to be used for simple user names 139 which require different handling. Protocols (or applications of those 140 protocols) which have application-specific identity forms and/or 141 comparison algorithms should use mechanisms specifically designed for 142 these forms and algorithms. 144 Application of string preparation may have an impact upon the 145 feasibility of brute force and dictionary attacks. While the number 146 of possible prepared strings is less than the number of possible 147 Unicode strings, the number of usable names and passwords is hoped to 148 be greater. 150 User names and passwords should be protected from eavesdropping. 152 General "stringprep" and Unicode security considerations apply. Both 153 are discussed in [StringPrep]. 155 4. IANA Considerations 157 This document details the "SASLprep" profile of [StringPrep] protocol. 158 Upon Standards Action the profile should be registered in the 159 stringprep profile registry. 161 Name of this profile: SASLprep 162 RFC in which the profile is defined: This RFC 163 Indicator whether or not this is the newest version of the 164 profile: This is the first version of the SASPprep profile. 166 5. Acknowledgment 168 This document borrows text from "Preparation of Internationalized 169 Strings ('stringprep')" and "Nameprep: A Stringprep Profile for 170 Internationalized Domain Names", both by Paul Hoffman and Marc 171 Blanchet. 173 This document is a product of the IETF SASL WG. 175 6. Normative References 177 [StringPrep] Hoffman P. and M. Blanchet, "Preparation of 178 Internationalized Strings ('stringprep')", 179 draft-hoffman-rfc3454bis-xx.txt, a work in progress. 181 [SASL] Melnikov, A. (Editor), "Simple Authentication and 182 Security Layer (SASL)", 183 draft-ietf-sasl-rfc2222bis-xx.txt, a work in progress. 185 [Unicode] The Unicode Consortium, "The Unicode Standard, Version 186 3.2.0" is defined by "The Unicode Standard, Version 3.0" 187 (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), 188 as amended by the "Unicode Standard Annex #27: Unicode 189 3.1" (http://www.unicode.org/reports/tr27/) and by the 190 "Unicode Standard Annex #28: Unicode 3.2" 191 (http://www.unicode.org/reports/tr28/). 193 7. Informative References 195 [Glossary] The Unicode Consortium, "Unicode Glossary", 196 . 198 [CharModel] Whistler, K. and M. Davis, "Unicode Technical Report 199 #17, Character Encoding Model", UTR17, 200 , August 201 2000. 203 [CRAM-MD5] Nerenberg, L., "The CRAM-MD5 SASL Mechanism", 204 draft-ietf-sasl-crammd5-xx.txt, a work in progress. 206 [DIGEST-MD5] Leach, P., C. Newman, and A. Melnikov, "Using Digest 207 Authentication as a SASL Mechanism", 208 draft-ietf-sasl-rfc2831bis-xx.txt, a work in progress. 210 [PLAIN] Zeilenga, K. (Editor), "The Plain SASL Mechanism", 211 draft-ietf-sasl-plain-xx.txt, a work in progress. 213 8. Editor's Address 215 Kurt D. Zeilenga 216 OpenLDAP Foundation 218 Email: Kurt@OpenLDAP.org 220 Intellectual Property Rights 221 The IETF takes no position regarding the validity or scope of any 222 intellectual property or other rights that might be claimed to pertain 223 to the implementation or use of the technology described in this 224 document or the extent to which any license under such rights might or 225 might not be available; neither does it represent that it has made any 226 effort to identify any such rights. Information on the IETF's 227 procedures with respect to rights in standards-track and 228 standards-related documentation can be found in BCP-11. Copies of 229 claims of rights made available for publication and any assurances of 230 licenses to be made available, or the result of an attempt made to 231 obtain a general license or permission for the use of such proprietary 232 rights by implementors or users of this specification can be obtained 233 from the IETF Secretariat. 235 The IETF invites any interested party to bring to its attention any 236 copyrights, patents or patent applications, or other proprietary 237 rights which may cover technology that may be required to practice 238 this standard. Please address the information to the IETF Executive 239 Director. 241 Full Copyright 243 Copyright (C) The Internet Society (2004). All Rights Reserved. 245 This document and translations of it may be copied and furnished to 246 others, and derivative works that comment on or otherwise explain it 247 or assist in its implementation may be prepared, copied, published and 248 distributed, in whole or in part, without restriction of any kind, 249 provided that the above copyright notice and this paragraph are 250 included on all such copies and derivative works. However, this 251 document itself may not be modified in any way, such as by removing 252 the copyright notice or references to the Internet Society or other 253 Internet organizations, except as needed for the purpose of 254 developing Internet standards in which case the procedures for 255 copyrights defined in the Internet Standards process must be followed, 256 or as required to translate it into languages other than English.