Pete Resnick wrote:
On 1/15/04 at 9:59 PM +0000, Charles Lindsey wrote:
In <3FF7A5FC(_dot_)9080804(_at_)verizon(_dot_)net>
blilly(_at_)verizon(_dot_)net writes:
[N.B. RFC 822 ASCII NUL not permitted, even with obs- rules]
Bruce gives many examples of differences from RFC 822. I will leave
it to others to comment on the rights and wrongs, but some of them
certainly look like bugs in RFC 2822 to me.
I think Bruce is wrong on this one. I see ASCII NUL in 822's CHAR, and
that appears in ctext (minus a few characters).
But CHAR doesn't appear in 2822. ASCII NUL is excluded from NO_WS_CTL,
and so
cannot be in (2822's) ctext. The point is that some legal 822 messages
cannot be parsed
even with 2822's obs- rules. The specific instance of (unescaped) ASCII
NUL in a comment
is an example of that.