Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

The Use of Non-ASCII Characters in RFCs (RFC7997)

IP.com Disclosure Number: IPCOM000248558D
Original Publication Date: 2016-Dec-01
Included in the Prior Art Database: 2016-Dec-17
Document File: 30 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Flanagan: AUTHOR [+2]

Abstract

Please review the PDF version of this draft.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

Internet Architecture Board (IAB)                       H. Flanagan, Ed. Request for Comments: 7997                                    RFC Editor Updates: 7322                                              December 2016 Category: Informational ISSN: 2070-1721

                 The Use of Non-ASCII Characters in RFCs

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 gives guidance regarding the use of non-ASCII    characters in RFCs.

   This document updates RFC 7322.  Please view this document in PDF    form to see the full text.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Architecture Board (IAB)    and represents information that the IAB has deemed valuable to    provide for permanent record.  It represents the consensus of the    Internet Architecture Board (IAB).  Documents approved for    publication by the IAB are not a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7997.

Flanagan                      Informational                     [Page 1]
 RFC 7997                    Non-ASCII in RFCs              December 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3

   2.  Basic Requirements  . . . . . . . . . . . . . . . . . . . . .   3

   3.  Rules for the Use of Non-ASCII Characters . . . . . . . . . .   4

     3.1.  General Usage throughout a Document . . . . . . . . . . .   4

     3.2.  Person Names  . . . . . . . . . . . . . . . . . . . . . .   5

     3.3.  Company Names . . . . . . . . . . . . . . . . . . . ....