Preparation of Internationalized Strings ("stringprep")
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 91
- Abstract
- This document describes a framework for preparing Unicode text strings in order to increase the likelihood that string input and string comparison work in ways that make sense for typical users throughout the world. The stringprep protocol is useful for protocol identifier values, company and personal names, internationalized domain names, and other text strings. This document does not specify how protocols should prepare text strings. Protocols must create profiles of stringprep in order to fully specify the processing options. [STANDARDS-TRACK]
- Publication Date
- 2003-01-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3454- Link
- https://doi.org/10.17487/RFC3454
- Author(s)
- Paul E. HoffmanMarc Blanchet
- Keyword(s)
- Unicode, Internationalization
Latest version of IETF RFC 3454
Document Versions — IETF RFC 3454
-
▶ IETF RFC 3454 (2003-01-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
Bibliographic Reference(s)
- ISO 10646-1:2000 [Withdrawn]
- The Unicode Consortium. Unicode Standard Annex #9, The Bidirectional Algorithm, < http://www.unicode.org/unicode/reports/tr9/ >. EXTERNAL
- Unicode Technical Report;17, Character Encoding Model. < http://www.unicode.org/unicode/reports/tr17/ >. EXTERNAL
- Unicode Glossary, < http://www.unicode.org/glossary/ >. EXTERNAL
- Mark Davis. Case Mappings. Unicode Technical Report 21. < http://www.unicode.org/unicode/reports/tr21/ >. EXTERNAL
- IETF RFC 2434 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3454.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3454, Preparation of Internationalized Strings ("stringprep"). Available at https://doi.org/10.17487/RFC3454
Snippet:
IETF RFC 3454, Preparation of Internationalized Strings ("stringprep"). Available at https://doi.org/10.17487/RFC3454
HTML (ISO 690 compliant)
Preview:
IETF RFC 3454, Preparation of Internationalized Strings ("stringprep"). Available at https://doi.org/10.17487/RFC3454
Snippet:
<span class="citation"><cite>IETF RFC 3454</cite>, Preparation of Internationalized Strings ("stringprep"). Available at <a href="https://doi.org/10.17487/RFC3454" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3454</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3454, Preparation of Internationalized Strings ("stringprep")
doi: 10.17487/RFC3454
url: https://doi.org/10.17487/RFC3454
doi: 10.17487/RFC3454
url: https://doi.org/10.17487/RFC3454
Snippet:
<li> <cite id="bib-rfc3454">IETF RFC 3454</cite>, Preparation of Internationalized Strings ("stringprep") <span class="doi">10.17487/RFC3454</span> </li>
Referenced By
- IETF RFC 3467 [Active*]
- IETF RFC 3490 [Superseded*]
- IETF RFC 3491 [Superseded*]
- IETF RFC 3530 [Superseded*]
- IETF RFC 3553 [Active*]
- IETF RFC 3743 [Active*]
- IETF RFC 3748 [Active*]
- IETF RFC 3920 [Superseded*]
- IETF RFC 3922 [Active*]
- IETF RFC 4013 [Superseded*]
- IETF RFC 4185 [Active*]
- IETF RFC 4279 [Active*]
- IETF RFC 4343 [Active*]
- IETF RFC 4422 [Active*]
- IETF RFC 4505 [Active*]
- IETF RFC 4511 [Active*]
- IETF RFC 4513 [Active*]
- IETF RFC 4518 [Active*]
- IETF RFC 4616 [Active*]
- IETF RFC 4643 [Active*]
- IETF RFC 4690 [Active*]
- IETF RFC 4790 [Active*]
- IETF RFC 4954 [Active*]
- IETF RFC 5054 [Active*]
- IETF RFC 5122 [Active*]
- IETF RFC 5198 [Active*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5456 [Active*]
- IETF RFC 5890 [Active*]
- IETF RFC 5892 [Active*]
- IETF RFC 5893 [Active*]
- IETF RFC 5894 [Active*]
- IETF RFC 5931 [Active*]
- IETF RFC 6124 [Active*]
- IETF RFC 6365 [Active*]
- IETF RFC 6885 [Active*]
- IETF RFC 7564 [Superseded*]
- IETF RFC 7613 [Superseded*]