PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols
draft-ietf-precis-framework-23

 
Document
Type Active Internet-Draft (precis WG)
Last updated 2015-04-10 (latest revision 2015-02-19)
Replaces draft-blanchet-precis-framework
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html
Stream
WG state Submitted to IESG for Publication Nov 2010
Consensus Yes
Document shepherd Alexey Melnikov
Shepherd write-up Show (last changed 2014-02-10)
IESG
IESG state RFC Ed Queue
Telechat date
Responsible AD Pete Resnick
IESG note Please be aware of the note in the ballot, especially regarding the IAB Statement.
Send notices to precis-chairs@ietf.org, draft-ietf-precis-framework@ietf.org
IANA
IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor
RFC Editor state MISSREF

Email authors IPR References Referenced by Nits Search lists

PRECIS                                                    P. Saint-Andre
Internet-Draft                                                      &yet
Obsoletes: 3454 (if approved)                                M. Blanchet
Intended status: Standards Track                                Viagenie
Expires: August 23, 2015                               February 19, 2015

     PRECIS Framework: Preparation, Enforcement, and Comparison of
           Internationalized Strings in Application Protocols
                     draft-ietf-precis-framework-23

Abstract

   Application protocols using Unicode characters in protocol strings
   need to properly handle such strings in order to enforce
   internationalization rules for strings placed in various protocol
   slots (such as addresses and identifiers) and to perform valid
   comparison operations (e.g., for purposes of authentication or
   authorization).  This document defines a framework enabling
   application protocols to perform the preparation, enforcement, and
   comparison of internationalized strings ("PRECIS") in a way that
   depends on the properties of Unicode characters and thus is agile
   with respect to versions of Unicode.  As a result, this framework
   provides a more sustainable approach to the handling of
   internationalized strings than the previous framework, known as
   Stringprep (RFC 3454).  This document obsoletes RFC 3454.

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 August 23, 2015.

Saint-Andre & Blanchet   Expires August 23, 2015                [Page 1]
Internet-Draft              PRECIS Framework               February 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Preparation, Enforcement, and Comparison  . . . . . . . . . .   7
   4.  String Classes  . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  IdentifierClass . . . . . . . . . . . . . . . . . . . . .   9
       4.2.1.  Valid . . . . . . . . . . . . . . . . . . . . . . . .   9
       4.2.2.  Contextual Rule Required  . . . . . . . . . . . . . .   9
       4.2.3.  Disallowed  . . . . . . . . . . . . . . . . . . . . .  10
       4.2.4.  Unassigned  . . . . . . . . . . . . . . . . . . . . .  10
       4.2.5.  Examples  . . . . . . . . . . . . . . . . . . . . . .  10
     4.3.  FreeformClass . . . . . . . . . . . . . . . . . . . . . .  11
       4.3.1.  Valid . . . . . . . . . . . . . . . . . . . . . . . .  11
       4.3.2.  Contextual Rule Required  . . . . . . . . . . . . . .  11
       4.3.3.  Disallowed  . . . . . . . . . . . . . . . . . . . . .  12
       4.3.4.  Unassigned  . . . . . . . . . . . . . . . . . . . . .  12
       4.3.5.  Examples  . . . . . . . . . . . . . . . . . . . . . .  12
   5.  Profiles  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     5.1.  Profiles Must Not Be Multiplied Beyond Necessity  . . . .  13
     5.2.  Rules . . . . . . . . . . . . . . . . . . . . . . . . . .  13
       5.2.1.  Width Mapping Rule  . . . . . . . . . . . . . . . . .  13
       5.2.2.  Additional Mapping Rule . . . . . . . . . . . . . . .  14
       5.2.3.  Case Mapping Rule . . . . . . . . . . . . . . . . . .  14
       5.2.4.  Normalization Rule  . . . . . . . . . . . . . . . . .  15
       5.2.5.  Directionality Rule . . . . . . . . . . . . . . . . .  15
Show full document text