Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
RFC 7613
Document | Type |
RFC - Proposed Standard
(August 2015; No errata)
Obsoleted by RFC 8265
Obsoletes RFC 4013
|
|
---|---|---|---|
Authors | Peter Saint-Andre , Alexey Melnikov | ||
Last updated | 2015-10-14 | ||
Replaces | draft-melnikov-precis-saslprepbis | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Matthew Miller | ||
Shepherd write-up | Show (last changed 2015-03-23) | ||
IESG | IESG state | RFC 7613 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Barry Leiba | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) P. Saint-Andre Request for Comments: 7613 &yet Obsoletes: 4013 A. Melnikov Category: Standards Track Isode Ltd ISSN: 2070-1721 August 2015 Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords Abstract This document describes updated methods for handling Unicode strings representing usernames and passwords. The previous approach was known as SASLprep (RFC 4013) and was based on stringprep (RFC 3454). The methods specified in this document provide a more sustainable approach to the handling of internationalized usernames and passwords. The preparation, enforcement, and comparison of internationalized strings (PRECIS) framework, RFC 7564, obsoletes RFC 3454, and this document obsoletes RFC 4013. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7613. Saint-Andre & Melnikov Standards Track [Page 1] RFC 7613 PRECIS: Usernames and Passwords August 2015 Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Saint-Andre & Melnikov Standards Track [Page 2] RFC 7613 PRECIS: Usernames and Passwords August 2015 Table of Contents 1. Introduction ....................................................4 2. Terminology .....................................................5 3. Usernames .......................................................6 3.1. Definition .................................................6 3.2. UsernameCaseMapped Profile .................................7 3.2.1. Preparation .........................................7 3.2.2. Enforcement .........................................7 3.2.3. Comparison ..........................................8 3.3. UsernameCasePreserved Profile ..............................8 3.3.1. Preparation .........................................8 3.3.2. Enforcement .........................................8 3.3.3. Comparison ..........................................9 3.4. Case Mapping vs. Case Preservation .........................9 3.5. Application-Layer Constructs ..............................10 3.6. Examples ..................................................11 4. Passwords ......................................................13 4.1. Definition ................................................13 4.2. OpaqueString Profile ......................................14 4.2.1. Preparation ........................................14 4.2.2. Enforcement ........................................14 4.2.3. Comparison .........................................15 4.3. Examples ..................................................15 5. Use in Application Protocols ...................................16 6. Migration ......................................................16 6.1. Usernames .................................................17 6.2. Passwords .................................................18 7. IANA Considerations ............................................19 7.1. UsernameCaseMapped Profile ................................19 7.2. UsernameCasePreserved Profile .............................20 7.3. OpaqueString Profile ......................................20 7.4. Stringprep Profile ........................................21 8. Security Considerations ........................................21Show full document text