One document matched: draft-flanagan-nonascii-02.txt

Differences from draft-flanagan-nonascii-01.txt

Internet Engineering Task Force                         H. Flanagan, Ed.
Internet-Draft                                                RFC Editor
Intended status: Informational                              July 4, 2014
Expires: January 5, 2015


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

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
   accepted language of the Series, the encoding of future RFCs will be
   in UTF-8.  This document describes the RFC Editor requirements and
   guidance regarding the use of non-ASCII characters in RFCs.

   This document updates the RFC Style Guide [I-D.iab-styleguide].

   Please review the PDF or HTML versions of this draft to see the full
   text, examples, and references.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 5, 2015.

Copyright Notice

   Copyright (c) 2014 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



Flanagan                 Expires January 5, 2015                [Page 1]

Internet-Draft              non-ASCII in RFCs                  July 2014


   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   2

1.  Introduction

   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
   accepted language of the Series, the encoding of future RFCs will be
   in UTF-8.  This document describes the RFC Editor requirements and
   guidance regarding the use of non-ASCII characters in RFCs.

   Please review the PDF or HTML versions of this draft to see the full
   text, examples, and references.

2.  References

   [I-D.iab-styleguide]
              Flanagan, H., "RFC Style Guide", draft-iab-styleguide-02
              (work in progress), April 2014.

Author's Address

   Heather Flanagan (editor)
   RFC Editor

   Email: rse@rfc-editor.org
   URI:   http://orcid.org/0000-0002-2647-2220













Flanagan                 Expires January 5, 2015                [Page 2]