The Use of Non-ASCII Characters in RFCs
RFC 7997, “The Use of Non-ASCII Characters in RFCs”, is an Informational document published in December 2016 by H. Flanagan. It updates RFC 7322. It has since been updated by RFC 9920. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7997 is hosted at rfc-editor.org. Available in TXT,PDF,HTML.
- RFC 7996 SVG Drawings for RFCs: SVG 1.2 RFC
- RFC 7998 "xml2rfc" Version 3 Preparation Tool Description
- RFC 7995 PDF Format for RFCs
- RFC 7999 BLACKHOLE Community
- RFC 7994 Requirements for Plain-Text RFCs
- RFC 8000 Requirements for NFSv4 Multi-Domain Namespace Deployment
- RFC 7993 Cascading Style Sheets Requirements for RFCs
- RFC 7992 HTML Format for RFCs