Stringprep Revision Problem Statement
draft-ietf-precis-problem-statement-04

The information below is for an old version of the document
Document Type Active Internet-Draft (precis WG)
Last updated 2011-06-10 (latest revision 2011-03-31)
Replaces draft-blanchet-precis-problem-statement
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state WG Document Aug 2010
Document shepherd None
IESG IESG state AD is watching
Telechat date
Responsible AD Pete Resnick
Send notices to precis-chairs@tools.ietf.org, draft-ietf-precis-problem-statement@tools.ietf.org
Network Working Group                                        M. Blanchet
Internet-Draft                                                  Viagenie
Intended status: Informational                               A. Sullivan
Expires: July 16, 2012                                  January 13, 2012

                 Stringprep Revision Problem Statement
               draft-ietf-precis-problem-statement-04.txt

Abstract

   Using Unicode codepoints in protocol strings that expect comparison
   with other strings requires preparation of the string that contains
   the Unicode codepoints.  Internationalizing Domain Names in
   Applications (IDNA2003) defined and used Stringprep and Nameprep.
   Other protocols subsequently defined Stringprep profiles.  A new
   approach different from Stringprep and Nameprep is used for a
   revision of IDNA2003 (called IDNA2008).  Other Stringprep profiles
   need to be similarly updated or a replacement of Stringprep needs to
   be designed.  This document outlines the issues to be faced by those
   designing a Stringprep replacement.

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 July 16, 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

Blanchet & Sullivan       Expires July 16, 2012                 [Page 1]
Internet-Draft    Stringprep Revision Problem Statement     January 2012

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Blanchet & Sullivan       Expires July 16, 2012                 [Page 2]
Internet-Draft    Stringprep Revision Problem Statement     January 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Issues raised during newprep BOF . . . . . . . . . . . . . . .  5
   3.  Major Topics for Consideration . . . . . . . . . . . . . . . .  6
     3.1.  Comparison . . . . . . . . . . . . . . . . . . . . . . . .  6
       3.1.1.  Types of Identifiers . . . . . . . . . . . . . . . . .  6
       3.1.2.  Effect of comparison . . . . . . . . . . . . . . . . .  7
     3.2.  Dealing with characters  . . . . . . . . . . . . . . . . .  7
       3.2.1.  Case folding, case sensitivity, and case
               preservation . . . . . . . . . . . . . . . . . . . . .  7
       3.2.2.  Stringprep and NFKC  . . . . . . . . . . . . . . . . .  7
       3.2.3.  Character mapping  . . . . . . . . . . . . . . . . . .  8
       3.2.4.  Prohibited characters  . . . . . . . . . . . . . . . .  8
       3.2.5.  Internal structure, delimiters, and special
               characters . . . . . . . . . . . . . . . . . . . . . .  9
     3.3.  Where the data comes from and where it goes  . . . . . . .  9
       3.3.1.  User input and the source of protocol elements . . . .  9
       3.3.2.  User output  . . . . . . . . . . . . . . . . . . . . . 10
       3.3.3.  Operations . . . . . . . . . . . . . . . . . . . . . . 10
Show full document text