idnits 2.17.1 draft-ietf-sasl-saslprep-02.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 243 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 (26 May 2003) is 7638 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 192, but no explicit reference was found in the text == Unused Reference: 'DIGEST-MD5' is defined on line 195, 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' -- Possible downref: Non-RFC (?) normative reference: ref. 'Unicode' -- No information found for draft-nerenberg-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: 5 errors (**), 0 flaws (~~), 5 warnings (==), 8 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 in six months 26 May 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 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 (2003). 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" "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 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 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 simple user names and passwords are used. This profile is 65 not intended to be used for arbitrary text. This profile is also not 66 intended to be used to prepare identity strings which are not simple 67 user names (e.g., e-mail addresses, domain names, distinguished 68 names). 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 for comparison. It is not intended to be used for to 134 prepare identities which are not simple user names (e.g., 135 distinguished names and domain names). Nor is the profile intended to 136 be used for simple user names which require different handling. 137 Protocols (or applications of those protocols) which have 138 application-specific identity forms and/or comparison algorithms 139 should use mechanisms specifically designed for these forms and 140 algorithms. 142 User names and passwords should be protected from eavesdropping. 144 General "stringprep" and Unicode security considerations apply. Both 145 are discused in [StringPrep]. 147 4. IANA Considerations 149 This document details the "SASLprep" profile of [StringPrep] protocol. 150 Upon Standards Action the profile should be registered in the 151 stringprep profile registry. 153 Name of this profile: SASLprep 154 RFC in which the profile is defined: This RFC 155 Indicator whether or not this is the newest version of the 156 profile: This is the first version of the SASPprep profile. 158 5. Acknowledgment 160 This document borrows text from "Preparation of Internationalized 161 Strings ('stringprep')" and "Nameprep: A Stringprep Profile for 162 Internationalized Domain Names", both by Paul Hoffman and Marc 163 Blanchet. 165 6. Normative References 167 [StringPrep] Hoffman P. and M. Blanchet, "Preparation of 168 Internationalized Strings ('stringprep')", RFC 3454, 169 December 2002. 171 [SASL] Myers, J., "Simple Authentication and Security Layer 172 (SASL)", draft-myers-saslrev-xx.txt, a work in progress. 174 [Unicode] The Unicode Consortium, "The Unicode Standard, Version 175 3.2.0" is defined by "The Unicode Standard, Version 3.0" 176 (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), 177 as amended by the "Unicode Standard Annex #27: Unicode 178 3.1" (http://www.unicode.org/reports/tr27/) and by the 179 "Unicode Standard Annex #28: Unicode 3.2" 180 (http://www.unicode.org/reports/tr28/). 182 7. Informative References 184 [Glossary] The Unicode Consortium, "Unicode Glossary", 185 . 187 [CharModel] Whistler, K. and M. Davis, "Unicode Technical Report 188 #17, Character Encoding Model", UTR17, 189 , August 190 2000. 192 [CRAM-MD5] Nerenberg, L., "The CRAM-MD5 SASL Mechanism", 193 draft-nerenberg-sasl-crammd5-xx.txt, a work in progress. 195 [DIGEST-MD5] Leach, P., C. Newman, and A. Melnikov, "Using Digest 196 Authentication as a SASL Mechanism", 197 draft-ietf-sasl-rfc2831bis-xx.txt, a work in progress. 199 [PLAIN] Zeilenga, K., "The Plain SASL Mechanism", 200 draft-ietf-sasl-plain-xx.txt, a work in progress. 202 8. Editor's Address 204 Kurt Zeilenga 205 OpenLDAP Foundation 207 Email: kurt@OpenLDAP.org 209 Intellectual Property Rights 211 The IETF takes no position regarding the validity or scope of any 212 intellectual property or other rights that might be claimed to pertain 213 to the implementation or use of the technology described in this 214 document or the extent to which any license under such rights might or 215 might not be available; neither does it represent that it has made any 216 effort to identify any such rights. Information on the IETF's 217 procedures with respect to rights in standards-track and 218 standards-related documentation can be found in BCP-11. Copies of 219 claims of rights made available for publication and any assurances of 220 licenses to be made available, or the result of an attempt made to 221 obtain a general license or permission for the use of such proprietary 222 rights by implementors or users of this specification can be obtained 223 from the IETF Secretariat. 225 The IETF invites any interested party to bring to its attention any 226 copyrights, patents or patent applications, or other proprietary 227 rights which may cover technology that may be required to practice 228 this standard. Please address the information to the IETF Executive 229 Director. 231 Full Copyright 233 Copyright (C) The Internet Society (2003). All Rights Reserved. 235 This document and translations of it may be copied and furnished to 236 others, and derivative works that comment on or otherwise explain it 237 or assist in its implmentation may be prepared, copied, published and 238 distributed, in whole or in part, without restriction of any kind, 239 provided that the above copyright notice and this paragraph are 240 included on all such copies and derivative works. However, this 241 document itself may not be modified in any way, such as by removing 242 the copyright notice or references to the Internet Society or other 243 Internet organizations, except as needed for the purpose of 244 developing Internet standards in which case the procedures for 245 copyrights defined in the Internet Standards process must be followed, 246 or as required to translate it into languages other than English.