Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6885
Discuss this RFC: Send questions or comments to the mailing listprecis@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 forthose strings to be ASCII, then using Unicode code points in thosestrings requires they be prepared somehow. Internationalizing DomainNames in Applications (here called IDNA2003) defined and usedStringprep and Nameprep. Other protocols subsequently definedStringprep profiles. A new approach different from Stringprep andNameprep is used for a revision of IDNA2003 (called IDNA2008). OtherStringprep profiles need to be similarly updated, or a replacement ofStringprep needs to be designed. This document outlines the issuesto be faced by those designing a Stringprep replacement.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.