From: Bruce Lilly (blilly@erols.com)
Date: Thu Apr 01 2004 - 21:36:34 CST
Charles Lindsey wrote:
> o those recognized by other IETF-established standards, notably the
> Email standard [RFC 2822] and its extensions, and included in the
RFC 2822's title is "Internet Message Format", not "Email standard".
The Internet Message Format is used by a number of applications in
addition to email.
> Experimental headers are those whose header-names begin with "X-".
> They are to be used for experimental Netnews features, or for
> enabling additional material to be propagated with an article. They
> are not (and will not be) defined by this, or any, standard.
Note that fields beginning with "X-" meet all of the requirements for
registration in the Permanent Registry; a claim that "[t]hey [...]
will not be [...] defined by [...] any [...] standard" promises more
than it can deliver.
> 10.2. Header Field Registry
>
> IANA is requested to register the following headers in the Permanent
> Message Header Field Repository, in accordance with the procedures
> set out in [KLYNE].
>
> Header field Applicable Status Author/Change Specification
> name protocol controller document
>
> Date netnews standard IETF [USEFOR] 5.1
> From netnews standard IETF [USEFOR] 5.2
> Message-ID netnews standard IETF [USEFOR] 5.3
> Subject netnews standard IETF [USEFOR] 5.4
No, the four above are specified in RFC 2822. As of this writing, the
document specified above defines different semantics for Date and
different syntax and semantics for Subject; both sets of differences
may cause interoperability problems for gateways, message access
protocols (e.g. IMAP), and news/mail user agents.
> Newsgroups mail standard IETF [USEFOR] 5.5
Nowhere is any protocol consideration for the mail application
specified for a "Newsgroups" field.
> Reply-To netnews standard IETF [USEFOR] 6.1
> Sender netnews standard IETF [USEFOR] 6.2
The defining document for the two fields above is RFC 2822.
> Keywords netnews standard IETF [USEFOR] 6.4
RFC 2822 is the specification document for the Keywords field. The
document specified above imposes restrictions on messages which may cause
interoperability problems with gateways, message access protocols (e.g.
IMAP), and news/mail user agents.
> References netnews standard IETF [USEFOR] 6.10
The specification document for the References field is RFC 2822.
> Supersedes netnews standard IETF [USEFOR] 6.15
N.B. the definition differs in syntax from Supersedes specified in RFC 2156,
and may cause interoperability problems with gateways, message access
protocols (e.g. IMAP), and mail/news user agents
> User-Agent mail standard IETF [USEFOR] 6.18
Nowhere is any protocol consideration for the mail application
specified for a "User-Agent" field.
> NNTP-Posting-Host netnews deprecated IETF [USEFOR] 6.19
> NNTP-Posting-Date netnews deprecated IETF [USEFOR] 6.19
There is no specification for either of the above two at the specified
place, in any RFC, or in any public de jure standard.
> Also-Control netnews obsoleted IETF [USEFOR] 6.22
> See-Also netnews obsoleted IETF [USEFOR] 6.22
> Article-Names netnews obsoleted IETF [USEFOR] 6.22
> Article-Updates netnews obsoleted IETF [USEFOR] 6.22
There are no specifications for any of the four fields above at the specified
place, in any RFC, or in any public de jure standard