RFC 7564: PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8264.
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
Application protocols using Unicode characters in protocol strings need to properly handle such strings in order to enforce internationalization rules for strings placed in various protocol slots (such as addresses and identifiers) and to perform valid comparison operations (e.g., for purposes of authentication or authorization). This document defines a framework enabling application protocols to perform the preparation, enforcement, and comparison of internationalized strings ("PRECIS") in a way that depends on the properties of Unicode characters and thus is agile with respect to versions of Unicode. As a result, this framework provides a more sustainable approach to the handling of internationalized strings than the previous framework, known as Stringprep (RFC 3454). This document obsoletes RFC 3454.
Document record
- Document ID
- RFC7564
- Published
- May 2015
- Authors
- P. Saint-Andre; M. Blanchet
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 40
- Also known as
- —
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 7613Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and PasswordsObsoleted
August 2015
- RFC 7622Extensible Messaging and Presence Protocol (XMPP): Address FormatUpdated
September 2015
- RFC 8265Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and PasswordsCurrent
October 2017
- RFC 8616Email Authentication for Internationalized MailCurrent
June 2019
- RFC 6365Terminology Used in Internationalization in the IETFCurrent
September 2011
- RFC 6783Mailing Lists and Non-ASCII AddressesCurrent
November 2012
- RFC 6531SMTP Extension for Internationalized EmailCurrent
February 2012
- RFC 6530Overview and Framework for Internationalized EmailCurrent
February 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?