draft-ietf-sasl-saslprep-02.txt   draft-ietf-sasl-saslprep-03.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 26 May 2003 Expires in six months 30 June 2003
SASLprep: Stringprep profile for user names and passwords SASLprep: Stringprep profile for user names and passwords
<draft-ietf-sasl-saslprep-02.txt> <draft-ietf-sasl-saslprep-03.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 4, line 16 skipping to change at page 4, line 16
distinguished names and domain names). Nor is the profile intended to distinguished names and domain names). Nor is the profile intended to
be used for simple user names which require different handling. be used for simple user names which require different handling.
Protocols (or applications of those protocols) which have Protocols (or applications of those protocols) which have
application-specific identity forms and/or comparison algorithms application-specific identity forms and/or comparison algorithms
should use mechanisms specifically designed for these forms and should use mechanisms specifically designed for these forms and
algorithms. algorithms.
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 discused 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
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 SASPprep profile. profile: This is the first version of the SASPprep profile.
5. Acknowledgment 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.
This document is a product of the IETF SASL WG.
6. Normative References 6. Normative References
[StringPrep] Hoffman P. and M. Blanchet, "Preparation of [StringPrep] Hoffman P. and M. Blanchet, "Preparation of
Internationalized Strings ('stringprep')", RFC 3454, Internationalized Strings ('stringprep')", RFC 3454,
December 2002. December 2002.
[SASL] Myers, J., "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.
 End of changes. 

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