metasystema.org
UpdatedINFORMATIONALIAB stream

RFC 7997: The Use of Non-ASCII Characters in RFCs

Still current, but amended. Parts of this document are changed or extended by RFC 9920. Read both.

In plain English — editorial summary, not part of the RFC

In order to support the internationalization of protocols and a more diverse Internet community, the RFC Series must evolve to allow for the use of non-ASCII characters in RFCs. While English remains the required language of the Series, the encoding of future RFCs will be in UTF-8, allowing for a broader range of characters than typically used in the English language. This document describes the RFC Editor requirements and gives guidance regarding the use of non-ASCII characters in RFCs. This document updates RFC 7322. Please view this document in PDF form to see the full text.

Document record

Document ID
RFC7997
Published
December 2016
Authors
H. Flanagan
Status
INFORMATIONAL
Stream
IAB
Area
—
Pages
15
Also known as
—
Updates:
RFC 7322
Updated by:
RFC 9920

Topics

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.

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?

canonical URL: /rfc/7997-the-use-of-non-ascii-characters-in-rfcs