RFC 3454: Preparation of Internationalized Strings ("stringprep")
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7564.
Current document in this lineage: RFC 8264 — PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC3454
- Published
- January 2003
- Authors
- P. Hoffman; M. Blanchet
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 91
- Also known as
- —
- Obsoleted by:
- RFC 7564
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3454 (2003)
- RFC 7564 (2015)
- RFC 8264 (2017) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3467Role of the Domain Name System (DNS)Current
March 2003
- RFC 5137ASCII Escaping of Unicode CharactersCurrent
February 2008
- RFC 5721POP3 Support for UTF-8Obsoleted
February 2010
- RFC 5987Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field ParametersObsoleted
August 2010
- RFC 6409Message Submission for MailUpdated
November 2011
- RFC 6530Overview and Framework for Internationalized EmailCurrent
February 2012
- RFC 6531SMTP Extension for Internationalized EmailCurrent
February 2012
- RFC 6783Mailing Lists and Non-ASCII AddressesCurrent
November 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?