The Use of Non-ASCII Characters in RFCs
RFC 7997

Changed author "H. Flanagan": changed name from "Heather Flanagan" to "H. Flanagan", changed is_editor from "False" to "True", changed affiliation from "RFC" to "RFC Editor", changed order from "0" to "1"

Received changes through RFC Editor sync (changed abstract to '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.')

Received changes through RFC Editor sync (created alias RFC 7997, changed abstract to '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.', changed pages to 15, changed standardization level to Informational, changed state to RFC, added RFC published event at 2016-12-16, changed IAB state to Published RFC, created updates relation between draft-iab-rfc-nonascii and RFC 7322)