The Use of Non-ASCII Characters in RFCs
draft-hoffman-rfc7997bis-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Paul E. Hoffman | ||
| Last updated | 2023-09-27 (Latest revision 2023-03-26) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (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 Production Center regarding the use of non-ASCII characters in RFCs. This document updates RFC 7997 to 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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)