draft-ietf-sasl-saslprep-06.txt   draft-ietf-sasl-saslprep-07.txt 
INTERNET-DRAFT Kurt D. Zeilenga INTERNET-DRAFT Kurt D. Zeilenga
Intended Category: Standards Track OpenLDAP Foundation Intended Category: Standards Track OpenLDAP Foundation
Expires: September 2004 10 March 2004 Expires: September 2004 22 March 2004
SASLprep: Stringprep profile for user names and passwords SASLprep: Stringprep profile for user names and passwords
<draft-ietf-sasl-saslprep-06.txt> <draft-ietf-sasl-saslprep-07.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 RFC 2026. provisions of Section 10 of RFC 2026.
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 2, line 4 skipping to change at page 2, line 4
for 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" profile of the "stringprep" algorithm to be used for both "SASLprep" profile of the "stringprep" algorithm to be used for both
user names and passwords. This profile is intended to be used by user names and passwords. This profile is intended to be used by
Simple Authentication and Security Layer (SASL) mechanisms (such as Simple Authentication and Security Layer (SASL) mechanisms (such as
PLAIN, CRAM-MD5, and DIGEST-MD5) as well as other protocols exchanging PLAIN, CRAM-MD5, and DIGEST-MD5) as well as other protocols exchanging
user names and/or passwords. simple user 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
likelihood that user name and password input and comparison 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.
skipping to change at page 4, line 6 skipping to change at page 4, line 6
[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. Security Considerations 3. Security Considerations
This profile is intended to used to prepare simple user names and This profile is intended to used to prepare simple user names and
passwords strings for comparison or use in cryptographic functions passwords strings for comparison or use in cryptographic functions
(e.g., message digests). (e.g., message digests). The preparation algorithm is specifically
designed such that its output is canonical.
It is not intended to be used for to prepare identity strings which It is not intended to be used for to prepare identity strings which
are not simple user names (e.g., distinguished names and domain are not simple user names (e.g., distinguished names and domain
names). Nor is the profile intended to be used for simple user names names). Nor is the profile intended to be used for simple user names
which require different handling. Protocols (or applications of those which require different handling. Protocols (or applications of those
protocols) which have application-specific identity forms and/or protocols) which have application-specific identity forms and/or
comparison algorithms should use mechanisms specifically designed for comparison algorithms should use mechanisms specifically designed for
these forms and algorithms. these forms and algorithms.
Application of string preparation may have an impact upon the Application of string preparation may have an impact upon the
feasibility of brute force and dictionary attacks. While the number feasibility of brute force and dictionary attacks. While the number
of possible prepared strings is less than the number of possible of possible prepared strings is less than the number of possible
Unicode strings, the number of usable names and passwords is hoped to Unicode strings, the number of usable names and passwords is greater
be greater. than if only ASCII was used. Though SASLprep eliminates some of
Unicode code point sequences as possible prepared strings, that
elimination generally makes the (canonical) output forms practicable
and prohibits nonsensical inputs.
User names and passwords should be protected from eavesdropping. User names and passwords should be protected from eavesdropping.
General "stringprep" and Unicode security considerations apply. Both General "stringprep" and Unicode security considerations apply. Both
are discussed in [StringPrep]. are discussed in [StringPrep].
4. IANA Considerations 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
skipping to change at page 6, line 4 skipping to change at page 6, line 6
draft-ietf-sasl-plain-xx.txt, a work in progress. draft-ietf-sasl-plain-xx.txt, a work in progress.
8. Editor's Address 8. Editor's Address
Kurt D. Zeilenga Kurt D. Zeilenga
OpenLDAP Foundation OpenLDAP Foundation
Email: Kurt@OpenLDAP.org Email: Kurt@OpenLDAP.org
Intellectual Property Rights Intellectual Property Rights
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain Intellectual Property Rights or other rights that might be claimed to
to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might or this document or the extent to which any license under such rights
might not be available; neither does it represent that it has made any might or might not be available; nor does it represent that it has
effort to identify any such rights. Information on the IETF's made any independent effort to identify any such rights. Information
procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be found
standards-related documentation can be found in BCP-11. Copies of in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such proprietary assurances of licenses to be made available, or the result of an
rights by implementors or users of this specification can be obtained attempt made to obtain a general license or permission for the use of
from the IETF Secretariat. such proprietary rights by implementers or users of this specification
can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf-
Director. ipr@ietf.org.
Full Copyright Full Copyright
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78 and
except as set forth therein, the authors retain all their rights.
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published and OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
distributed, in whole or in part, without restriction of any kind, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be followed,
or as required to translate it into languages other than English.
 End of changes. 

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