[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: #1003 Message-ID text: Resolving
In <F6FC8E6D93DDBC8F88C5F58B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> Harald Tveit Alvestrand <harald@xxxxxxxxxxxxx> writes:
>However, the text seems to have support as "better than what we have now".
Agreed.
> NEW:
> The Message-ID header contains a single unique message identifier.
> News is more dependent on msg-id uniqueness and fast comparision
>than
> email is, and some news software would have trouble with the full
>range
> of possible msg-ids permitted by RFC 2822;
I have already pointed out that it is more that "some" news software. It
is also the new NNTP standard-to-be.
> NEW:
> Some software will try to match the <id-right> of a msg-id in
> a case-insensitive fashion; some will match it in a case sensitive
> fashion. Implementations MUST NOT generate two message-IDs where
> the only difference is the case of characters in the <id-right> part.
> If domain literals are used, the syntax found in [RFC2821] section
> 4.1.3 is RECOMMENDED.
I think some people had a problem with that last sentence.
--
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@xxxxxxxxxxxxxxxx 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