The Use of Non-ASCII Characters in RFCs
draft-flanagan-nonascii-06

Document Type Replaced Internet-Draft (individual)
Last updated 2015-11-18
Replaced by draft-iab-rfc-nonascii
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-iab-rfc-nonascii
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-flanagan-nonascii-06.txt

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

Heather Flanagan (rse@rfc-editor.org)

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