Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
draft-ietf-precis-saslprepbis-15

The information below is for an old version of the document
Document Type Active Internet-Draft (precis WG)
Last updated 2015-04-28 (latest revision 2015-04-14)
Replaces draft-melnikov-precis-saslprepbis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html 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 Waiting for AD Go-Ahead
Consensus Boilerplate Unknown
Telechat date
Responsible AD Barry Leiba
Send notices to draft-ietf-precis-saslprepbis@ietf.org, draft-ietf-precis-saslprepbis.ad@ietf.org, mamille2@cisco.com, precis-chairs@ietf.org, draft-ietf-precis-saslprepbis.shepherd@ietf.org
IANA IANA review state IANA - Not OK
IANA action state None
PRECIS                                                    P. Saint-Andre
Internet-Draft                                                      &yet
Obsoletes: 4013 (if approved)                                A. Melnikov
Intended status: Standards Track                               Isode Ltd
Expires: October 16, 2015                                 April 14, 2015

 Preparation, Enforcement, and Comparison of Internationalized Strings
                  Representing Usernames and Passwords
                    draft-ietf-precis-saslprepbis-15

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 PRECIS framework, RFC YYYY, obsoletes RFC 3454, and
   this document obsoletes RFC 4013.

   [[ NOTE TO RFC EDITOR: please replace "YYYY" in the previous
   paragraph with the RFC number assigned to draft-ietf-precis-
   framework. ]]

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 16, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Saint-Andre & Melnikov  Expires October 16, 2015                [Page 1]
Internet-Draft       PRECIS: Usernames and Passwords          April 2015

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Usernames . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Definition  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  UsernameCaseMapped Profile  . . . . . . . . . . . . . . .   5
       3.2.1.  Preparation . . . . . . . . . . . . . . . . . . . . .   6
       3.2.2.  Enforcement . . . . . . . . . . . . . . . . . . . . .   6
       3.2.3.  Comparison  . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  UsernameCasePreserved Profile . . . . . . . . . . . . . .   6
       3.3.1.  Preparation . . . . . . . . . . . . . . . . . . . . .   7
       3.3.2.  Enforcement . . . . . . . . . . . . . . . . . . . . .   7
       3.3.3.  Comparison  . . . . . . . . . . . . . . . . . . . . .   7
     3.4.  Case Mapping vs. Case Preservation  . . . . . . . . . . .   7
     3.5.  Application-Layer Constructs  . . . . . . . . . . . . . .   9
     3.6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Passwords . . . . . . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  Definition  . . . . . . . . . . . . . . . . . . . . . . .  11
     4.2.  OpaqueString Profile  . . . . . . . . . . . . . . . . . .  12
       4.2.1.  Preparation . . . . . . . . . . . . . . . . . . . . .  12
       4.2.2.  Enforcement . . . . . . . . . . . . . . . . . . . . .  12
       4.2.3.  Comparison  . . . . . . . . . . . . . . . . . . . . .  13
     4.3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .  13
   5.  Use in Application Protocols  . . . . . . . . . . . . . . . .  14
   6.  Migration . . . . . . . . . . . . . . . . . . . . . . . . . .  15
     6.1.  Usernames . . . . . . . . . . . . . . . . . . . . . . . .  15
     6.2.  Passwords . . . . . . . . . . . . . . . . . . . . . . . .  16
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     7.1.  UsernameCaseMapped Profile  . . . . . . . . . . . . . . .  17
     7.2.  UsernameCasePreserved Profile . . . . . . . . . . . . . .  18
     7.3.  OpaqueString Profile  . . . . . . . . . . . . . . . . . .  18
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
Show full document text