* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Precis Status Pages

Preparation and Comparison of Internationalized Strings (Concluded WG)
Art Area: Barry Leiba, Murray Kucherawy | 2010-Jun-11 — 2017-Nov-15 

2017-03-30 charter

Preparation and Comparison of Internationalized Strings (precis)


 Current Status: Active

     Marc Blanchet <Marc.Blanchet@viagenie.ca>

 Applications and Real-Time Area Directors:
     Ben Campbell <ben@nostrum.com>
     Alexey Melnikov <aamelnikov@fastmail.fm>
     Adam Roach <adam@nostrum.com>

 Applications and Real-Time Area Advisor:
     Alexey Melnikov <aamelnikov@fastmail.fm>

 Mailing Lists:
     General Discussion: precis@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/precis
     Archive:            https://mailarchive.ietf.org/arch/browse/precis/

Description of Working Group:

    Problem Statement

    The use of non-ASCII strings in Internet protocols requires additional
    processing to be handled properly. As part of the Internationalized
    Domain Names (idn) work in 2003, a method for preparation and comparison
    of internationalized strings was defined and generalized to be re-used
    by other protocols. This "stringprep" method [RFC 3454] defines the
    overall framework whereas specific protocols define their own profiles.
    Known existing IETF profiles are:

    - The Nameprep profile [RFC 3490] for use in Internationalized Domain
    Names in Applications (IDNA)
    - The iSCSI profile [RFC 3722] for use in Internet Small Computer
    Systems Interface (iSCSI) Names
    - The Nodeprep and Resourceprep profiles [RFC 3920] for use in the
    Extensible Messaging and Presence Protocol (XMPP)
    - The Policy MIB profile [RFC 4011] for use in the Simple Network
    Management Protocol (SNMP)
    - The SASLprep profile [RFC 4013] for use in the Simple Authentication
    and Security Layer (SASL)
    - The trace profile [RFC 4505] for use with the SASL ANONYMOUS mechanism
    - The LDAP profile (RFC 4518] for use with LDAP

    The IAB completed a review of IDN and made recommendations for change
    [RFC 4690], which triggered a new version of the IDNA protocol called
    IDNA2008. Whereas IDNA2003 was tied to Unicode 3.2 via stringprep,
    IDNA2008 does not use the stringprep method, but instead uses an
    algorithm based on the properties of Unicode characters, which makes it
    agile to the Unicode database version. The protocols using stringprep
    need Unicode version agility and therefore need to investigate whether
    and how to move away from the current stringprep approach, with the
    associated challenges of backward compatibility and migration.


    The goal of this group is to assess whether a new method based on the
    new IDNA2008 algorithmic approach is the appropriate path forward for
    existing stringprep protocols as well as for other application protocols
    requiring internationalized strings.

    The group will evaluate if a new generalized framework based on the
    algorithmic approach is appropriate and, if so, define it.

    The group will analyze existing stringprep profiles and will do one of
    the following with regard to each profile:

    1. Develop a replacement for the profile in close collaboration with the
    related protocol working group (if any).

    2. Collaborate with another active working group which will be
    developing the new profile as part of its charter.

    3. Advise the authors of profiles for which there is no active working
    group how to proceed.

    The group will also define a set of best current practices for
    preparation and comparison of internationalized strings.

    Because the framework, profile replacements, and guidelines are very
    much interrelated, work on them will proceed in parallel as much as

    Based on normal working group processes for achieving consensus, the
    group will attempt to gather input from, and may provide advice to,
    "customers" working on IETF technologies other than those listed above,
    including but not limited to Network Address Identifiers (RFC 4282) and
    Kerberos (RFC 4120). However, the group will prioritize work on the
    listed stringprep profiles higher than work on other technologies, and
    will formally accept additional tasks as official milestones only after

    In completing its tasks, the working group should collaborate with other
    teams involved in internationalized identifiers, such as the IETF's IRI
    and EAI working groups as well as other relevant standards development
    organizations (e.g., the Unicode Consortium).


    1. Problem statement / analysis of existing stringprep profiles

    2. Possible new framework to replace stringprep (Standards Track).

    3. Possible replacements for the existing IETF stringprep profiles as
    listed earlier in this charter (Standards Track).

    4. String preparation and comparison guidelines (BCP).

Goals and Milestones:
  Done     - Accept problem statement document as a WG item
  Done     - Accept framework document as a WG item
  Done     - Accept new profile documents as WG items
  Done     - Start Working Group Last Call on problem statement document
  Done     - Submit problem statement document to the IESG
  Done     - Start Working Group Last Call on framework document
  Done     - Start Working Group Last Call on new profile documents
  Dec 2013 - Submit new profile documents to the IESG
  Done     - Submit framework document to the IESG
  Apr 2014 - Accept guidelines document as a WG item
  Oct 2014 - Start Working Group Last Call on guidelines document
  Dec 2014 - Submit guidelines document to the IESG
  Jun 2016 - New version of RFC 7564
  Jun 2016 - New version of  RFC 7613
  Jun 2016 - New version of 7700

All charter page changes, including changes to draft-list, rfc-list and milestones:

Generated from PyHt script /wg/precis/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -