draft-ietf-precis-7613bis-10.txt   draft-ietf-precis-7613bis-11.txt 
Network Working Group P. Saint-Andre Network Working Group P. Saint-Andre
Internet-Draft Filament Internet-Draft Filament
Obsoletes: 7613 (if approved) A. Melnikov Obsoletes: 7613 (if approved) A. Melnikov
Intended status: Standards Track Isode Ltd Intended status: Standards Track Isode Ltd
Expires: January 25, 2018 July 24, 2017 Expires: January 26, 2018 July 25, 2017
Preparation, Enforcement, and Comparison of Internationalized Strings Preparation, Enforcement, and Comparison of Internationalized Strings
Representing Usernames and Passwords Representing Usernames and Passwords
draft-ietf-precis-7613bis-10 draft-ietf-precis-7613bis-11
Abstract Abstract
This document describes updated methods for handling Unicode strings This document describes updated methods for handling Unicode strings
representing usernames and passwords. The previous approach was representing usernames and passwords. The previous approach was
known as SASLprep (RFC 4013) and was based on stringprep (RFC 3454). known as SASLprep (RFC 4013) and was based on stringprep (RFC 3454).
The methods specified in this document provide a more sustainable The methods specified in this document provide a more sustainable
approach to the handling of internationalized usernames and approach to the handling of internationalized usernames and
passwords. This document obsoletes RFC 7613. passwords. This document obsoletes RFC 7613.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on January 25, 2018. This Internet-Draft will expire on January 26, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 17, line 46 skipping to change at page 17, line 46
application-layer constructs (see Section 3.5), and related matters. application-layer constructs (see Section 3.5), and related matters.
Some PRECIS profile definitions encourage entities that enforce the Some PRECIS profile definitions encourage entities that enforce the
rules to be liberal in what they accept. However, for usernames and rules to be liberal in what they accept. However, for usernames and
passwords such a policy can be problematic, because it can lead to passwords such a policy can be problematic, because it can lead to
false accepts. An in-depth discussion can be found in [RFC6943]. false accepts. An in-depth discussion can be found in [RFC6943].
Applying the rules for any given PRECIS profile is not necessarily an Applying the rules for any given PRECIS profile is not necessarily an
idempotent procedure for all code points. Therefore, an idempotent procedure for all code points. Therefore, an
implementation SHOULD apply the rules repeatedly until the output implementation SHOULD apply the rules repeatedly until the output
string is stable; if the output string does not stabilize within a string is stable; if the output string does not stabilize after
reasonable number of iterations, the implementation SHOULD terminate reapplying the rules three (3) additional times, the implementation
application of the rules and reject the input string as invalid. SHOULD terminate application of the rules and reject the input string
as invalid.
6. Migration 6. Migration
The rules defined in this specification differ slightly from those The rules defined in this specification differ slightly from those
defined by the SASLprep specification [RFC4013] (but not from defined by the SASLprep specification [RFC4013] (but not from
[RFC7613]). In order to smooth the process of migrating from [RFC7613]). In order to smooth the process of migrating from
SASLprep to the approach defined herein, the following sections SASLprep to the approach defined herein, the following sections
describe these differences, along with their implications for describe these differences, along with their implications for
migration, in more detail. migration, in more detail.
skipping to change at page 23, line 31 skipping to change at page 23, line 31
Unicode code points in usernames and passwords. Unicode code points in usernames and passwords.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-precis-7564bis] [I-D.ietf-precis-7564bis]
Saint-Andre, P. and M. Blanchet, "PRECIS Framework: Saint-Andre, P. and M. Blanchet, "PRECIS Framework:
Preparation, Enforcement, and Comparison of Preparation, Enforcement, and Comparison of
Internationalized Strings in Application Protocols", Internationalized Strings in Application Protocols",
draft-ietf-precis-7564bis-09 (work in progress), July draft-ietf-precis-7564bis-10 (work in progress), July
2017. 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
2003, <http://www.rfc-editor.org/info/rfc3629>. 2003, <http://www.rfc-editor.org/info/rfc3629>.
 End of changes. 5 change blocks. 
7 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/