Re: [Gendispatch] Making all RFCs UTF-8, with questions about RFC 20

John Levine <johnl@taugh.com> Mon, 13 March 2023 23:09 UTC

Date: Mon, 13 Mar 2023 18:09:14 -0500
Message-Id: <20230313230914.62378B0D49F0@ary.local>
From: John Levine <johnl@taugh.com>
To: gendispatch@ietf.org
Cc: sayrer@gmail.com
In-Reply-To: <CAChr6SxsD7k83ad2HLNcbOEDF7j_Rfit-zM+zsH_gHbUqeOyUg@mail.gmail.com>
Organization: Taughannock Networks
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/dG6xgQHk4cfqQP8OKS1kO6Slayo>
Subject: Re: [Gendispatch] Making all RFCs UTF-8, with questions about RFC 20
Precedence: list

It appears that Rob Sayre  <sayrer@gmail.com> said:
>-=-=-=-=-=-
>
>Hi,
>
>I was looking at making all RFCs UTF-8, which would be a brief document.
>The old ones are mostly ASCII, but that's kind of the point of UTF-8.

There's a lot of random non-ASCII junk in old RFCs, I think mostly
8859-1. I do not think that is a problem, nor should we try to change them,

>I think RFC 10000 should say "RFCs are now encoded in UTF-8"

Since RFC 7990 said that seven years ago, I don't see the point.

R's,
John

PS: here's some of the old random junk
rfc101.txt 753 b'      [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc1305.txt 2551 b'.01% or <F128M>\xe6<F255D>100 ppm. Its contents are designated y in the\n'
rfc1305.txt 3547 b'3, reachability okay (peer.reach <F128M>\xd6<F255D> 0)\n'
rfc1305.txt 4634 b'seconds, but varies about <F128M>\xe6<F255D>30 ms throughout the year due\n'
rfc1305.txt 5236 b'<F128M>\xe6<F255D>128 ms, called the aperture, which guarantees the seconds\n'
rfc1305.txt 5282 b'<F128M>\xe6<F255D>500 ppm. Even larger ranges may be required in the case\n'
rfc1305.txt 5299 b'the range <F128M>\xe6<F255D>100 ppm with an intrinsic oscillator frequency\n'
rfc1305.txt 5300 b'error as great as <F128M>\xe6<F255D>100 ppm. Figure 11<$&fig11> shows the\n'
rfc1305.txt 6018 b'(shown by the <F128>\xec<F255> symbol) and confidence interval shown for\n'
rfc177.txt 485 b'    [into the online RFC archives by Kelly Tardif, Viag\xe9nie 12/1999]\n'
rfc178.txt 607 b'        [into the online RFC archives by Kelly Tardif,Viag\xe9nie 11/99]\n'
rfc182.txt 52 b'     [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/1999]\n'
rfc2166.txt 641 b'   formats see the \x93Frame Formats\x94 section.\n'
rfc2166.txt 660 b'   the \x93Frame Formats\x94 section.\n'
rfc2166.txt 759 b'   which implement these multicast enhancements will carry a \x93Multicast\n'
rfc2166.txt 760 b'   Capabilities\x94 Control Vector in their capabilities exchange (see RFC\n'
rfc2166.txt 876 b'   generically refers to this process as \x93address resolution\x94.\n'
rfc2166.txt 1036 b'   and explorer retries.  Accordingly, the \x93Retry\x94 section in the table\n'
rfc2166.txt 1312 b'   indicated in the table above with an \x93Yes\x94 in the \x93Retry\x94 column.\n'
rfc2166.txt 1489 b'   implementations in the future can expect that the DLSw \x93Version\n'
rfc2166.txt 1490 b'   Number\x94 is found in byte one and that the following bytes describe\n'
rfc2166.txt 1501 b"   1) The \x93Version Number\x94 field is set to x'32' (ASCII '2') and now\n"
rfc227.txt 70 b'     [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc234.txt 53 b'      [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc235.txt 243 b'     [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc237.txt 50 b'     [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie 10/99]\n'
rfc243.txt 353 b'     [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/1999]\n'
rfc2497.txt 210 b'   [EUI64]   "64-Bit Global Identifier Format Tutorial", http://stan\xad\n'
rfc2557.txt 813 b'      E with acute accent becomes \xc9.<br>\n'
rfc270.txt 46 b'      [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc2708.txt 521 b'   assigned ID\xc6s, there is a limited amount of clear text information\n'
rfc282.txt 446 b'     [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc2875.txt 754 b'   TBS: the \xf4text\xf6 for computing the SHA-1 HMAC.\n'
rfc2875.txt 926 b'   Signature verification requires CA\xc6s private key, the CA certificate\n'
rfc288.txt 211 b'     [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc290.txt 828 b'     [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc292.txt 529 b'      [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc303.txt 607 b'     [into the online RFC archives by Kelly Tardif, Viag\xe9nie 10/99]\n'
rfc306.txt 189 b'     [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie 10/99]\n'
rfc307.txt 331 b'    [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie, 12/99]\n'
rfc310.txt 389 b'     [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie 10/99]\n'
rfc313.txt 440 b'     [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie 10/99]\n'
rfc315.txt 181 b'      [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie, 12/99]\n'
rfc316.txt 369 b'     [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie 10/99]\n'
rfc317.txt 51 b'     [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie 10/99]\n'
rfc323.txt 499 b'    [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie, 12/99]\n'
rfc327.txt 277 b'     [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie 10/99]\n'
rfc367.txt 184 b'    [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie, 12/99]\n'
rfc369.txt 602 b'     [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie 12/99]\n'
rfc441.txt 234 b'      U + 3 --> X\xa0\n'
rfc441.txt 389 b'      [into the online RFC archives by H\xe9l\xe8ne Morin, Viag\xe9nie, 12/99]\n'
rfc64.txt 65 b'message 4 bits to the left. This takes approximately 12 \xb5sec per double\n'

[Gendispatch] Making all RFCs UTF-8, with questio… Rob Sayre
Re: [Gendispatch] Making all RFCs UTF-8, with que… John Levine