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

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2015-08-03 (latest revision 2015-01-30)
Replaced by rfc7997, draft-iab-rfc-nonascii
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-04.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.)