I am becoming more and more confused. I thought we were (at this
point0 only rtrying to decide exactly how to identify (what label to
use to identify) the character set that is (was) specified in the
original RFC822.
OK, we kinda got off on the content-type tangent.
Howabout calling it "822ASCII" since that is exactly what we mean.
Now, did RFC822 really nail down what character set it meant to be
used? I have heard of something called "NVT-ASCII" whatever that is.
Yes it did! Here's the relevant rules:
CHAR = <any ASCII character> ; ( 0-177, 0.-127.)
text = <any CHAR, including bare ; => atoms, specials,
CR & bare LF, but NOT ; comments and
including CRLF> ; quoted-strings are
; NOT recognized.
message = fields *( CRLF *text ) ; Everything after
I am beginning to wonder how we have managed for all these
years to not get messed up on this question of what the original
character set was (is)!
Also from RFC822, this is Crocker, et al.'s reference for ASCII.
ANSI. "USA Standard Code for Information Interchange," X3.4.
American National Standards Institute: New York (1968). Also
in: Feinler, E. and J. Postel, eds., "ARPANET Protocol Hand-
book", NIC 7104.
When I say "ASCII", this is the ASCII I mean. But, I'm with Stef. This
discussion is getting silly. I really don't care what the label is.
Nathaniel, this is your RFC, you name the label, just pick something! :-)
I promise not to say another word...at least for a while :-)
-jwn2