The Use of Non-ASCII Characters in RFCs, December 2016
Discuss this RFC: Send questions or comments to email@example.com
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.