[rfc-i] [IAB Trac] #269: Discussion of UTF-8 in RFCs (Section 3.3)
stpeter at stpeter.im
Thu Feb 28 17:43:25 PST 2013
-----BEGIN PGP SIGNED MESSAGE-----
On 2/28/13 4:25 PM, SM wrote:
> Hi Heather, Nevil, At 15:54 26-02-2013, IAB issue tracker wrote:
>> The official language of the RFC Series is English. ASCII is
>> required for all "normative" text, i.e., text that must be read
>> to understand or implement the technology described in the RFC.
>> UTF-8/Unicode text will be
> My guess is that the above requirement would be an edge case.
> Someone (in the IETF) might have to explain why the text must be
> read to understand or implement the technology. Anyway, after
> reading http://www.ietf.org/iesg/appeal.html I think that the
> above requirement can end up being a headache.
Only an übergeek such as yourself would be so naïve as to think that
all (modern) English words can be represented only in ASCII. If you
prove me wrong, I will promise you a delightful road trip to the Good
Thyme Café in Cañon City, Colorado whenever the IETF meets in Denver.
I've heard that their apple pie à la mode is especially delicious.
There are plenty of reasons why some text might need to use Unicode
code points outside the ASCII range. That does not change the fact
that the official language of the RFC Series is English.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the rfc-interest