The Use of Non-ASCII Characters in RFCs
draft-flanagan-nonascii-06
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Author | Heather Flanagan | ||
| Last updated | 2015-11-18 | ||
| Replaced by | RFC 7997 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-iab-rfc-nonascii | |
| 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
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 guidance regarding the use of non-ASCII characters in RFCs. This document updates RFC 7322.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)