RFC 6885

Stringprep Revision and Problem Statement for the Preparation and Comparison of Internationalized Strings (PRECIS), March 2013

File formats:
icon for text file icon for PDF icon for HTML
M. Blanchet
A. Sullivan
precis (app)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC6885

Discuss this RFC: Send questions or comments to the mailing list precis@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 6885


If a protocol expects to compare two strings and is prepared only for those strings to be ASCII, then using Unicode code points in those strings requires they be prepared somehow. Internationalizing Domain Names in Applications (here called 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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search