draft-ietf-sasl-saslprep-01.txt   draft-ietf-sasl-saslprep-02.txt 
INTERNET-DRAFT Kurt D. Zeilenga INTERNET-DRAFT Kurt D. Zeilenga
Intended Category: Standards Track OpenLDAP Foundation Intended Category: Standards Track OpenLDAP Foundation
Expires in six months 4 May 2003 Expires in six months 26 May 2003
SASLprep: Stringprep profile for user names and passwords SASLprep: Stringprep profile for user names and passwords
<draft-ietf-sasl-saslprep-01.txt> <draft-ietf-sasl-saslprep-02.txt>
Status of Memo Status of Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
This document is intended to be, after appropriate review and This document is intended to be, after appropriate review and
revision, submitted to the RFC Editor as a Standards Track document. revision, submitted to the RFC Editor as a Standards Track document.
Distribution of this memo is unlimited. Technical discussion of this Distribution of this memo is unlimited. Technical discussion of this
document will take place on the IETF SASL mailing list document will take place on the IETF SASL mailing list
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
<http://www.ietf.org/ietf/1id-abstracts.txt>. The list of <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
Internet-Draft Shadow Directories can be accessed at Internet-Draft Shadow Directories can be accessed at
<http://www.ietf.org/shadow.html>. <http://www.ietf.org/shadow.html>.
Copyright 2003, The Internet Society. All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Please see the Copyright section near the end of this document for Please see the Full Copyright section near the end of this document
more information. for more information.
Abstract Abstract
This document describes how to prepare Unicode strings representing This document describes how to prepare Unicode strings representing
user names and passwords for comparison. The document defines the user names and passwords for comparison. The document defines the
"SASLprep" "stringprep" profile to be used for both user names and "SASLprep" "stringprep" profile to be used for both user names and
passwords. This profile is intended to be used by Simple passwords. This profile is intended to be used by Simple
Authentication and Security Layer (SASL) mechanisms (such as PLAIN, Authentication and Security Layer (SASL) mechanisms (such as PLAIN,
CRAM-MD5, and DIGEST-MD5) as well as other protocols exchanging user CRAM-MD5, and DIGEST-MD5) as well as other protocols exchanging user
names and/or passwords. names and/or passwords.
1. Introduction 1. Introduction
The use of simple user names and passwords in authentication and The use of simple user names and passwords in authentication and
authorization is pervasive on the Internet. To increase the authorization is pervasive on the Internet. To increase the
likelyhood that user name and password input and comparsion work in likelihood that user name and password input and comparison work in
ways that make sense for typical users throughout the world, this ways that make sense for typical users throughout the world, this
document defines rules for preparing internationalized user names and document defines rules for preparing internationalized user names and
passwords for comparison. For simplicity and implementation ease, a passwords for comparison. For simplicity and implementation ease, a
single algorithm is defined for both user names and passwords. single algorithm is defined for both user names and passwords.
This document defines the "SASLprep" profile of the "stringprep" This document defines the "SASLprep" profile of the "stringprep"
protocol [StringPrep]. protocol [StringPrep].
The profile is designed for use in Simple Authentication and Security The profile is designed for use in Simple Authentication and Security
Layer ([SASL]) mechanisms such as [PLAIN]. It may be applicable Layer ([SASL]) mechanisms such as [PLAIN]. It may be applicable
elsewhere simple user names and passwords are used. This profile is elsewhere simple user names and passwords are used. This profile is
not intended to be used for arbitrary text. This profile is also not not intended to be used for arbitrary text. This profile is also not
intended to be used to prepare identity strings which are not simple intended to be used to prepare identity strings which are not simple
user names (e.g., e-mail addresses, domain names, distinguished user names (e.g., e-mail addresses, domain names, distinguished
names). names).
1.1. Conventions 2. The SASLprep profile
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", This section defines the "SASLprep" profile. This profile is intended
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this to be used to prepare strings representing simple user names and
document are to be interpreted as described in BCP 14 [RFC2119]. passwords.
This profile uses Unicode 3.2, as defined in [StringPrep, A.1].
Character names in this document use the notation for code points and Character names in this document use the notation for code points and
names from the Unicode Standard [Unicode]. For example, the letter names from the Unicode Standard [Unicode]. For example, the letter
"a" may be represented as either <U+0061> or <LATIN SMALL LETTER A>. "a" may be represented as either <U+0061> or <LATIN SMALL LETTER A>.
In the lists of mappings and the prohibited characters, the "U+" is In the lists of mappings and the prohibited characters, the "U+" is
left off to make the lists easier to read. The comments for character left off to make the lists easier to read. The comments for character
ranges are shown in square brackets (such as "[CONTROL CHARACTERS]") ranges are shown in square brackets (such as "[CONTROL CHARACTERS]")
and do not come from the standard. and do not come from the standard.
Note: a glossary of terms used in Unicode can be found in [Glossary]. Note: a glossary of terms used in Unicode can be found in [Glossary].
Information on the Unicode character encoding model can be found in Information on the Unicode character encoding model can be found in
[CharModel]. [CharModel].
2. The SASLprep profile
This section defines the "SASLprep" profile. This profile is intended
to be used to prepare strings representing simple user names and
passwords.
This profile uses Unicode 3.2, as defined in [StringPrep, A.1].
2.1. Mapping 2.1. Mapping
This profile specifies: This profile specifies:
- non-ASCII space characters [StringPrep, C.1.2] be mapped to SPACE - non-ASCII space characters [StringPrep, C.1.2] be mapped to SPACE
(U+0020), and (U+0020), and
- the "commonly mapped to nothing" characters [StringPrep, B.1] be - the "commonly mapped to nothing" characters [StringPrep, B.1] be
mapped to nothing. mapped to nothing.
2.2. Normalization 2.2. Normalization
This profile specifies using Unicode normalization form KC, as This profile specifies using Unicode normalization form KC, as
skipping to change at page 3, line 27 skipping to change at page 3, line 21
2.2. Normalization 2.2. Normalization
This profile specifies using Unicode normalization form KC, as This profile specifies using Unicode normalization form KC, as
described in Section 4 of [StringPrep]. described in Section 4 of [StringPrep].
2.3. Prohibited Output 2.3. Prohibited Output
This profile specifies the following characters: This profile specifies the following characters:
- Non-ASCII space characters [StringPrep, C.1.2], - Non-ASCII space characters [StringPrep, C.1.2],
- ASCII control charcters [StringPrep, C.2.1], - ASCII control characters [StringPrep, C.2.1],
- Non-ASCII control characters [StringPrep, C.2.2], - Non-ASCII control characters [StringPrep, C.2.2],
- Private Use [StringPrep, C.3], - Private Use [StringPrep, C.3],
- Non-character code points [StringPrep, C.4], - Non-character code points [StringPrep, C.4],
- Surrogate code points [StringPrep, C.5], - Surrogate code points [StringPrep, C.5],
- Inappropriate for plain text [StringPrep, C.6], - Inappropriate for plain text [StringPrep, C.6],
- Inappropriate for canonical representation [StringPrep, C.7], - Inappropriate for canonical representation [StringPrep, C.7],
- Change display properties or are deprecated [StringPrep, C.8], and - Change display properties or are deprecated [StringPrep, C.8], and
- Tagging characters [StringPrep, C.9]. - Tagging characters [StringPrep, C.9].
are prohibited output. are prohibited output.
skipping to change at page 4, line 4 skipping to change at page 3, line 39
- Tagging characters [StringPrep, C.9]. - Tagging characters [StringPrep, C.9].
are prohibited output. are prohibited output.
2.4. Bidirectional characters 2.4. Bidirectional characters
This profile specifies checking bidirectional strings as described in This profile specifies checking bidirectional strings as described in
[StringPrep, Section 6]. [StringPrep, Section 6].
2.5. Unassigned Code Points 2.5. Unassigned Code Points
This profile specifies [StringPrep, A.1] table as its list of This profile specifies [StringPrep, A.1] table as its list of
unassigned code points. unassigned code points.
3. IANA Considerations 3. Security Considerations
This profile is intended to used to prepare simple user names and
passwords for comparison. It is not intended to be used for to
prepare identities which are not simple user names (e.g.,
distinguished names and domain names). Nor is the profile intended to
be used for simple user names which require different handling.
Protocols (or applications of those protocols) which have
application-specific identity forms and/or comparison algorithms
should use mechanisms specifically designed for these forms and
algorithms.
User names and passwords should be protected from eavesdropping.
General "stringprep" and Unicode security considerations apply. Both
are discused in [StringPrep].
4. IANA Considerations
This document details the "SASLprep" profile of [StringPrep] protocol. This document details the "SASLprep" profile of [StringPrep] protocol.
Upon Standards Action the profile should be registered in the Upon Standards Action the profile should be registered in the
stringprep profile registry. stringprep profile registry.
Name of this profile: SASLprep Name of this profile: SASLprep
RFC in which the profile is defined: This RFC RFC in which the profile is defined: This RFC
Indicator whether or not this is the newest version of the Indicator whether or not this is the newest version of the
profile: This is the first version of the User Name profile. profile: This is the first version of the SASPprep profile.
5. Acknowledgement 5. Acknowledgment
This document borrows text from "Preparation of Internationalized This document borrows text from "Preparation of Internationalized
Strings ('stringprep')" and "Nameprep: A Stringprep Profile for Strings ('stringprep')" and "Nameprep: A Stringprep Profile for
Internationalized Domain Names", both by Paul Hoffman and Marc Internationalized Domain Names", both by Paul Hoffman and Marc
Blanchet. Blanchet.
6. Normative References 6. Normative References
[Keywords] S. Bradner, "Key words for use in RFCs to Indicate [StringPrep] Hoffman P. and M. Blanchet, "Preparation of
Requirement Levels", BCP 14 (also RFC 2119), March 1997.
[StringPrep] P. Hoffman, M. Blanchet, "Preparation of
Internationalized Strings ('stringprep')", RFC 3454, Internationalized Strings ('stringprep')", RFC 3454,
December 2002. December 2002.
[SASL] J. Myers, "Simple Authentication and Security Layer [SASL] Myers, J., "Simple Authentication and Security Layer
(SASL)", draft-myers-saslrev-xx.txt (a work in progress). (SASL)", draft-myers-saslrev-xx.txt, a work in progress.
[Unicode] The Unicode Consortium. The Unicode Standard, Version [Unicode] The Unicode Consortium, "The Unicode Standard, Version
3.2.0 is defined by The Unicode Standard, Version 3.0 3.2.0" is defined by "The Unicode Standard, Version 3.0"
(Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5),
as amended by the Unicode Standard Annex #27: Unicode 3.1 as amended by the "Unicode Standard Annex #27: Unicode
(http://www.unicode.org/reports/tr27/) and by the Unicode 3.1" (http://www.unicode.org/reports/tr27/) and by the
Standard Annex #28: Unicode 3.2 "Unicode Standard Annex #28: Unicode 3.2"
(http://www.unicode.org/reports/tr28/). (http://www.unicode.org/reports/tr28/).
7. Informative References 7. Informative References
[Glossary] Unicode Glossary, <http://www.unicode.org/glossary/>. [Glossary] The Unicode Consortium, "Unicode Glossary",
<http://www.unicode.org/glossary/>.
[CharModel] Unicode Technical Report;17, Character Encoding Model.
<http://www.unicode.org/unicode/reports/tr17/>.
[CRAM-MD5] L. Nerenberg, "The CRAM-MD5 SASL Mechanism", [CharModel] Whistler, K. and M. Davis, "Unicode Technical Report
draft-nerenberg-sasl-crammd5-xx.txt (a work in progress). #17, Character Encoding Model", UTR17,
<http://www.unicode.org/unicode/reports/tr17/>, August
2000.
[PLAIN] K. Zeilenga, "The Plain SASL Mechanism", [CRAM-MD5] Nerenberg, L., "The CRAM-MD5 SASL Mechanism",
draft-ietf-sasl-plain-xx.txt (a work in progress). draft-nerenberg-sasl-crammd5-xx.txt, a work in progress.
[DIGEST-MD5] P. Leach, C. Newman, A. Melnikov, "Using Digest [DIGEST-MD5] Leach, P., C. Newman, and A. Melnikov, "Using Digest
Authentication as a SASL Mechanism", Authentication as a SASL Mechanism",
draft-ietf-sasl-rfc2831bis-xx.txt (a work in progress). draft-ietf-sasl-rfc2831bis-xx.txt, a work in progress.
[PLAIN] Zeilenga, K., "The Plain SASL Mechanism",
draft-ietf-sasl-plain-xx.txt, a work in progress.
8. Editor's Address 8. Editor's Address
Kurt Zeilenga Kurt Zeilenga
OpenLDAP Foundation OpenLDAP Foundation
Email: kurt@OpenLDAP.org Email: kurt@OpenLDAP.org
Full Copyright Statement Intellectual Property Rights
Copyright 2003, The Internet Society. All Rights Reserved. The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such proprietary
rights by implementors or users of this specification can be obtained
from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and or assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be followed, copyrights defined in the Internet Standards process must be followed,
or as required to translate it into languages other than English. or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/