[rfc-i] Fwd: I-D ACTION:draft-hoffman-utf8-rfcs-03.txt

Joe Touch touch at ISI.EDU
Mon Oct 20 09:16:28 PDT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Julian Reschke wrote:
> Joe Touch wrote:
>>> Nope.
>>>
>>> A text/plain document encoded in ASCII by *definition* is already
>>> encoded in UTF-8, so the document itself does not change at all.
>>
>> The draft allows UTF-8 in places that are not absolutely requires, which
>> affects new RFCs and IDs that are not intended to address protocol
>> internationalization issues.
>>
>> I.e., this affects all *new* RFCs and IDs. Agreed it doesn't affect old
>> ones.
> 
> It only affects those documents where non-ASCII characters are used.

It allows non-ASCII characters in all RFCs, even where not required to
express a protocol construct.

> So please do not claim it affects all new, when it only *potentially*
> affects them all.

   Upon publication of this document as an RFC, all existing RFCs and
   Internet Drafts will be considered to be encoded in UTF-8.

That seems to require that RFCs be served in UTF-8 format. That would be
ALL files (old and new) if a BOM is used.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkj8rtsACgkQE5f5cImnZrvPOQCglUr2PGfokXufRLB/xzmkF814
TDoAnir0D3Ss16T3z61lXkUZf1r40ZQZ
=6OQR
-----END PGP SIGNATURE-----


More information about the rfc-interest mailing list