Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
draft-ietf-precis-7613bis-09

Document Type Active Internet-Draft (precis WG)
Last updated 2017-07-16
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Jun 2016 - New version of RFC ... )
Document shepherd Marc Blanchet
Shepherd write-up Show (last changed 2017-05-30)
IESG IESG state Approved-announcement to be sent::AD Followup
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to Marc Blanchet <Marc.Blanchet@viagenie.ca>
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                     P. Saint-Andre
Internet-Draft                                                  Filament
Obsoletes: 7613 (if approved)                                A. Melnikov
Intended status: Standards Track                               Isode Ltd
Expires: January 17, 2018                                  July 16, 2017

 Preparation, Enforcement, and Comparison of Internationalized Strings
                  Representing Usernames and Passwords
                      draft-ietf-precis-7613bis-09

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.  This document obsoletes RFC 7613.

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 January 17, 2018.

Copyright Notice

   Copyright (c) 2017 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

Saint-Andre & Melnikov  Expires January 17, 2018                [Page 1]
Internet-Draft       PRECIS: Usernames and Passwords           July 2017

   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 . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Definition  . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Case Mapping vs. Case Preservation  . . . . . . . . . . .   6
     3.3.  UsernameCaseMapped Profile  . . . . . . . . . . . . . . .   7
       3.3.1.  Rules . . . . . . . . . . . . . . . . . . . . . . . .   7
       3.3.2.  Preparation . . . . . . . . . . . . . . . . . . . . .   8
       3.3.3.  Enforcement . . . . . . . . . . . . . . . . . . . . .   8
       3.3.4.  Comparison  . . . . . . . . . . . . . . . . . . . . .   9
     3.4.  UsernameCasePreserved Profile . . . . . . . . . . . . . .   9
       3.4.1.  Rules . . . . . . . . . . . . . . . . . . . . . . . .   9
       3.4.2.  Preparation . . . . . . . . . . . . . . . . . . . . .  10
       3.4.3.  Enforcement . . . . . . . . . . . . . . . . . . . . .  10
       3.4.4.  Comparison  . . . . . . . . . . . . . . . . . . . . .  10
     3.5.  Application-Layer Constructs  . . . . . . . . . . . . . .  11
     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 . . . . . . . . . . . . . . . . . . . . .  15
       4.2.3.  Comparison  . . . . . . . . . . . . . . . . . . . . .  16
     4.3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .  16
   5.  Use in Application Protocols  . . . . . . . . . . . . . . . .  17
   6.  Migration . . . . . . . . . . . . . . . . . . . . . . . . . .  18
     6.1.  Usernames . . . . . . . . . . . . . . . . . . . . . . . .  18
     6.2.  Passwords . . . . . . . . . . . . . . . . . . . . . . . .  19
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
     7.1.  UsernameCaseMapped Profile  . . . . . . . . . . . . . . .  20
     7.2.  UsernameCasePreserved Profile . . . . . . . . . . . . . .  21
     7.3.  OpaqueString Profile  . . . . . . . . . . . . . . . . . .  21
Show full document text