Skip to main content

The Use of Non-ASCII Characters in RFCs
draft-rswg-rfc7997bis-03

Document Type Expired Internet-Draft (rswg)
Expired & archived
Author Paul E. Hoffman
Last updated 2025-02-12 (Latest revision 2024-08-11)
RFC stream Editorial
Intended RFC status Informational
Formats
Additional resources Mailing list discussion
Stream Editorial state Active editorial stream document
Consensus boilerplate Unknown
Document shepherd (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

The RFC Series has evolved to allow for the use of non-ASCII characters in RFCs. While English remains the required language of the Series, the encoding of RFCs is now in UTF-8, allowing for a broader range of characters than typically used in the English language. This document describes requirements and guidelines for the RFC Editor regarding the use of non-ASCII characters in RFCs. This document obsoletes RFC 7997. The differences reflect changes in the practices of the RFC series since RFC 7997 was published, and makes further changes based on agreements in the IETF community about what characters are allowed in RFCs. [[ A repository for this draft can be found here (https://github.com/ paulehoffman/7997bis). ]]

Authors

Paul E. Hoffman

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)