Skip to main content

Stringprep Revision Problem Statement

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Marc Blanchet
Last updated 2010-10-27 (Latest revision 2010-07-05)
Replaced by RFC 6885
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-precis-problem-statement
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Using Unicode codepoints in protocol strings requires preparation of the string. Internationalized Domain Names(idn) initial work defined and used Stringprep and Nameprep. Other protocols have defined Stringprep profiles. A new approach different from Stringprep/ Nameprep is used for a revision of IDN. The Stringprep profiles need to be updated or a replacement of Stringprep need to be designed. This document summarizes the findings of the current usage of Stringprep and identifies directions for a new Stringprep replacement protocol.


Marc Blanchet

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)