Allow non-ASCII characters in Internet-Drafts
draft-luis140219-id-nonascii-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Luís Câmara | ||
| Last updated | 2017-12-20 (Latest revision 2017-06-18) | ||
| 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
RFC 7997 allowed non-ASCII characters in RFCs. This document updates RFC 2026, removing from it the requirement that Internet-Drafts be fully in ASCII. This document also updates RFC 5657 and RFC 7997 to note the allowance of non-ASCII characters in Internet-Drafts. [[RFC-Editor: please replace the second character of my surname by U+00E2 when publishing as RFC in the header and in all pages. Non-ASCII characters are allowed in RFCs as per RFC 7997.]]
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)