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

The information below is for an old version of the document
Document Type Active Internet-Draft (precis WG)
Last updated 2012-08-01
Replaces draft-blanchet-precis-framework
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document (wg milestone: Nov 2010 - Accept framework doc... )
Document shepherd None
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Pete Resnick
Send notices to precis-chairs@tools.ietf.org, draft-ietf-precis-framework@tools.ietf.org
Network Working Group                                     P. Saint-Andre
Internet-Draft                                       Cisco Systems, Inc.
Obsoletes: 3454 (if approved)                                M. Blanchet
Intended status: Standards Track                                Viagenie
Expires: February 2, 2013                                 August 1, 2012

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

Abstract

   Application protocols using Unicode code points in protocol strings
   need to prepare such strings in order to perform comparison
   operations (e.g., for purposes of authentication or authorization).
   This document defines a framework enabling application protocols to
   handle various classes of strings in a way that depends on the
   properties of Unicode code points and that 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).  A
   specification that reuses this framework can either directly use the
   base string classes or subclass the base string classes as needed.
   This framework takes an approach similar to the revised
   internationalized domain names in applications (IDNA) technology (RFC
   5890, RFC 5891, RFC 5892, RFC 5893, RFC 5894) and thus adheres to the
   high-level design goals described in RFC 4690, albeit for application
   technologies other than the Domain Name System (DNS).  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 February 2, 2013.

Saint-Andre & Blanchet  Expires February 2, 2013                [Page 1]
Internet-Draft              PRECIS Framework                 August 2012

Copyright Notice

   Copyright (c) 2012 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  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  String Classes . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.2.  NameClass  . . . . . . . . . . . . . . . . . . . . . . . .  7
       3.2.1.  Valid  . . . . . . . . . . . . . . . . . . . . . . . .  7
       3.2.2.  Disallowed . . . . . . . . . . . . . . . . . . . . . .  7
       3.2.3.  Unassigned . . . . . . . . . . . . . . . . . . . . . .  8
       3.2.4.  Directionality . . . . . . . . . . . . . . . . . . . .  8
       3.2.5.  Case Mapping . . . . . . . . . . . . . . . . . . . . .  8
       3.2.6.  Normalization  . . . . . . . . . . . . . . . . . . . .  8
     3.3.  FreeClass  . . . . . . . . . . . . . . . . . . . . . . . .  8
       3.3.1.  Valid  . . . . . . . . . . . . . . . . . . . . . . . .  9
       3.3.2.  Disallowed . . . . . . . . . . . . . . . . . . . . . .  9
       3.3.3.  Unassigned . . . . . . . . . . . . . . . . . . . . . .  9
       3.3.4.  Directionality . . . . . . . . . . . . . . . . . . . .  9
       3.3.5.  Case Mapping . . . . . . . . . . . . . . . . . . . . .  9
       3.3.6.  Normalization  . . . . . . . . . . . . . . . . . . . . 10
   4.  Use of PRECIS String Classes . . . . . . . . . . . . . . . . . 10
     4.1.  Principles . . . . . . . . . . . . . . . . . . . . . . . . 10
     4.2.  Subclassing  . . . . . . . . . . . . . . . . . . . . . . . 10
     4.3.  A Note about Spaces  . . . . . . . . . . . . . . . . . . . 11
   5.  Code Point Properties  . . . . . . . . . . . . . . . . . . . . 12
   6.  Category Definitions Used to Calculate Derived Property
Show full document text