< Then, how do you define "ASCII characters"?
<
< Quoting RFC822, section 3.3:
< ------------------------------------------------------------
< 3.3. LEXICAL TOKENS
< The following rules are used to define an underlying lexical
< analyzer, which feeds tokens to higher level parsers. See the
< ANSI references, in the Bibliography.
< ; ( Octal, Decimal.)
< CHAR = <any ASCII character> ; ( 0-177, 0.-127.)
< ------------------------------------------------------------
< With this, I can read:
< >> The body is simply a sequence of lines containing ASCII characters.
< as:
< << The body is simply a sequence of lines containing characters
< << of the range 0-177 (Octal).
< and sending "A B C ESC $ B $ + $ s $ 8 ESC ( B" does not
< violate RFC822 (ESC = 033 (octal)). This is what
< ISO-2022-JP is doing.
So it would seem until you look at the references in the bibliography, which
you're explicitly told to look at and which you're so conveniently ignoring:
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.
Golly gee, what's the acronym for "USA Standard Code for Information
Interchange"? USASCII!
Tony Hansen
hansen(_at_)pegasus(_dot_)att(_dot_)com,
tony(_at_)attmail(_dot_)com
att!pegasus!hansen, attmail!tony