[rfc-i] [IAB Trac] #270: Resources associated with allowing UTF-8 in RFCs (Section 3.3)

IAB issue tracker trac+iab at trac.tools.ietf.org
Thu Mar 7 12:52:31 PST 2013

#270: Resources associated with allowing UTF-8 in RFCs (Section 3.3)

Changes (by hlflanagan at gmail.com):

 * status:  new => closed
 * resolution:   => fixed


 The text for the ASCII requirement has been modified to:

       *  The official language of the RFC Series is English.  ASCII is
          required for all text that must be read to understand or
          implement the technology described in the RFC.  Use of non-
          ASCII characters, expressed in a standard Unicode Encoding Form
          (such as UTF-8), must receive explicit approval from the
          document stream manager and will be allowed after the rules for
          the common use cases are defined in the Style Guide.

 I have also started a document to capture some further details that must
 go in the Style Guide regarding when and where Unicode code points will be
 required in a document using the UTF-8 character set.  That level of
 detail does not belong in the Requirements document, however, so I
 consider the response to this particular ticket complete.

 Reporter:  john-        |       Owner:  draft-iab-
  ietf at jck.com           |  rfcformatreq at tools.ietf.org
     Type:  defect       |      Status:  closed
 Priority:  major        |   Milestone:  milestone1
Component:  draft-iab-   |     Version:  1.0
  rfcformatreq           |  Resolution:  fixed
 Severity:  In WG Last   |
  Call                   |
 Keywords:               |

Ticket URL: <http://trac.tools.ietf.org/group/iab/trac/ticket/270#comment:4>
IAB Trac <http://tools.ietf.org/group/iab/trac/>

More information about the rfc-interest mailing list