[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
Fri Feb 15 16:07:08 PST 2013

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

Comment (by nico at cryptonector.com):

 But note that allowing non-ASCII UTF-8 would not require that any existing
 tools be updated on day one.  Instead the tool maintainers could update
 their tools as demand materializes.  I think this goes for other bits of
 desired evolution in the RFC formats, such as improved image support (that
 is, beyond ASCII art).

 I can live with that.

 Also, the RFC-Editor isn't responsible for any of the tools in question (a
 somewhat surprising fact, I think), so it seems a bit much to ask that the
 RFC-Editor have any degree of understanding of development/maintenance
 impact on any of the relevant existing tools.  That said, we should give
 the developers/maintainers of these tools a chance to comment on this and
 have their comments integrated into this I-D.

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

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

More information about the rfc-interest mailing list