#1003 Message-ID text: Resolving

[Harald Tveit Alvestrand <harald@xxxxxxxxxxxxx>]

Two significant issues seem to have been raised with the proposed 
resolution:

- What needs to be said in order to "play nice" with the $altz "control." 
convention (for instance, not to outlaw it)
- Whether, and if so where, the requirement not to go mess with other 
people's namespace needs to be documented

However, the text seems to have support as "better than what we have now".

So I'm declaring consensus and moving this to "Text accepted", for the 
following text (the change is deleting the last paragraph, which might 
interfere with the $altz convention):

OLD (start of section):

The Message-ID header contains a single unique message identifier.
This document updates the <msg-id> construct from Section 3.6.4 of
[RFC2822] so as to ensure that Internet Message Format Message-IDs
are usable in widely deployed news software. The global uniqueness
requirement for <msg-id> in [RFC2822] is to be understood as
applying
across all protocols using such message identifiers, and across
both
Email and Netnews in particular. A revised syntax for <msg-id> is
given below, but the requirements and descriptive text from Section
3.6.4 of [RFC2822] still apply.

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; this section therefore
restricts the syntax of <msg-id> compared to Section 3.6.4 of
[RFC2822].
The global uniqueness
requirement for <msg-id> in [RFC2822] is to be understood as
applying
across all protocols using such message identifiers, and across
both
Email and Netnews in particular.

OLD (ABNF):

no-fold-quote = DQUOTE
( "." mqtext /
*mqtext "." /
*mqtext mqspecial *mqtext )
DQUOTE

NEW:

no-fold-quote = DQUOTE
( "." *mqtext /
*mqtext "." /
*mqtext mqspecial *mqtext )
DQUOTE


OLD (end of section):

NOTE: It is RECOMMENDED in [RFC2822] that, for ensuring global
uniqueness, the <id-right> be some domain identifier within
whose
scope the uniqueness of the <id-left> can be guaranteed. When
following this recommendation, any <dot-atom-text> or <no-fold-
literal> used for the <id-right> are to be interpreted as
<domain>s as described in Section 3.4.1 of [RFC2822].

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.

NOTE: [RFC2822] section 3.6.4 recommends that the <id-right>
should be a domain name or a domain literal. Domain literals are
troublesome since many IP addresses are not globally unique;
domain names are
more likely to generate unique message-IDs.