In <200410222043(_dot_)22810(_dot_)blilly(_at_)erols(_dot_)com> Bruce Lilly
<blilly(_at_)erols(_dot_)com> writes:
On Fri October 22 2004 07:54, Charles Lindsey wrote:
But once the domain name has been copied into the id-right
There is no "copying" involved; RFC 2822 recommends that
id-right *be* a domain name, full stop.
(whether in
upper or lower case) it is no longer a domain name for any protocol
purpose.
Says who? Certainly not RFC 2822.
its only purpose is to be compared for identity
with other <id-right>s for the removal of duplicates, for threading, etc.
No, Charles; the original message in this discussion mentioned
content identifiers, which explicitly use RFC 822 syntax. There
was no mention of "removal of duplicates" or "threading" or
anything vaguely similar.
This thread has developed a long way since its original Subject was set.
You agreed that RFC 2822 had (intentionally or otherwise) changed the
semantics of <msg-id>s with regard to the case-sensitivity of whatever
came after the '@'. I said that I considered the change to be an
improvement, and you have been harranguing me ever since for being so
presumptious.
Whilst is is arguable whether RFC 2822 applies retrospectively to
Content-ID, there is no doubt that it applies to Message-ID, and that is
the more interesting case.
--
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl
Email: chl(_at_)clerew(_dot_)man(_dot_)ac(_dot_)uk Snail: 5 Clerewood Ave,
CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5