ietf-822
[Top] [All Lists]

Re: Angle brackets surrounding Content-ID

2004-10-08 03:08:49

Bruce Lilly <blilly(_at_)erols(_dot_)com> writes:

But you have not answered the question. We were discussing the <id-right>
in <msg-id>s. Have you heard of any case where this esoteric change of
semantics actually caused a problem?

I have indeed answered exactly that question, in detail.
For example:
Interpreting a msg-id RHS as RFC 2822 id-right means that one
cannot determine whether <foo(_at_)bar(_dot_)com> matches 
<foo(_at_)Bar(_dot_)COM>
because RFC 2822 doesn't specify whether or not id-right is
a domain name. It might be or it might not be.  In the event
that it is not, RFC 2822 is silent on whether or not case
matters.  Under RFC 822, the RHS of a msg-id was always a
domain, and as domain names are always case-insensitive, the
two msg-ids above would match under RFC 822. Under RFC 2822,
one cannot tell whether or not they match.

Standards wise that is probably true.
But pragmatically whatever generates the message-id isn't 
likely to change how it cases the strings it builds.
So if case differs message was presumably generated by 
at last a different instance of the thing - so it is a different 
message.

Only the bit after the '@' is a domain in any case, so 
transport shouldn't mess with case.



There are other, related issues as well.