From: Charles Lindsey (chl@clerew.man.ac.uk)
Date: Tue Mar 30 2004 - 12:04:33 CST
Now that the Header Field Registrations
(draft-klyne-msghdr-registry-07.txt) is on its way to becoming an RFC,
we have to take account of it within USEFOR. The following are the
changes that appear to be required:
4.2.1. Naming of Headers
Despite the restrictions on header-name syntax imposed by the
grammar, relaying, serving and reading agents SHOULD tolerate
header-names containing any US-ASCII printable character other than
colon (":", US-ASCII 58).
Whilst relaying agents MUST accept, and pass on unaltered, any non-
variant header whose header-name is syntactically correct, and
reading agents MUST enable them to be displayed, at least optionally,
posting and injecting agents SHOULD NOT generate headers other than
o headers established by this standard or any extension to it;
o those recognized by other IETF-established standards, notably the
Email standard [RFC 2822] and its extensions, and included in the
Permanent Message Header Field Repository maintained by IANA in
accordance with [KLYNE], but excluding any header explicitly
deprecated for Netnews (e.g. see section 9.2.1 for the deprecated
Disposition-Notification-To-header);
o experimental headers beginning with "X-" (as defined in 4.2.5.1);
o on a provisional basis only, headers related to new protocols
under development which are listed in the Provisional Message
Header Field Repository maintained by IANA in accordance with
[KLYNE].
However, software SHOULD NOT attempt to interpret headers not
specifically intended to be meaningful in the Netnews environment.
Header-names are case-insensitive. There is a preferred case
convention set out in [USEAGE], and which is used in the various
rules defining headers in this standard. Relaying and reading agents
MUST, however, tolerate header-names in any case.
4.2.5.1. Experimental Headers
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: Experimental headers are suitable for situations where
they need only to be human readable. They are not intended to be
recognized by widely deployed Netnews software and, should such
a requirement be envisaged, it is preferable to arrange for a
suitable normal header to be included in the Provisional Message
Header Field Repository maintained by IANA in accordance with
[KLYNE].
10. IANA Considerations
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
Newsgroups netnews standard IETF [USEFOR] 5.5
Newsgroups mail standard IETF [USEFOR] 5.5
Path netnews standard IETF [USEFOR] 5.6
Reply-To netnews standard IETF [USEFOR] 6.1
Sender netnews standard IETF [USEFOR] 6.2
Organization netnews standard IETF [USEFOR] 6.3
Keywords netnews standard IETF [USEFOR] 6.4
Summary netnews standard IETF [USEFOR] 6.5
Distribution netnews standard IETF [USEFOR] 6.6
Followup-To netnews standard IETF [USEFOR] 6.7
Mail-Copies-To netnews standard IETF [USEFOR] 6.8
Posted-And-Mailed netnews standard IETF [USEFOR] 6.9
References netnews standard IETF [USEFOR] 6.10
Expires netnews standard IETF [USEFOR] 6.11
Archive netnews standard IETF [USEFOR] 6.12
Control netnews standard IETF [USEFOR] 6.13
Approved netnews standard IETF [USEFOR] 6.14
Supersedes netnews standard IETF [USEFOR] 6.15
Xref netnews standard IETF [USEFOR] 6.16
Lines netnews standard IETF [USEFOR] 6.17
User-Agent netnews standard IETF [USEFOR] 6.18
User-Agent mail standard IETF [USEFOR] 6.18
Injector-Info netnews standard IETF [USEFOR] 6.19
NNTP-Posting-Host netnews deprecated IETF [USEFOR] 6.19
NNTP-Posting-Date netnews deprecated IETF [USEFOR] 6.19
Complaints-To netnews standard IETF [USEFOR] 6.20
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
[KLYNE] G. Klyne and J. Mogul, "Registration procedures for message
header fields", draft-klyne-msghdr-registry-07.txt.
[RFC 2822] P. Resnick, "Internet Message Format", RFC 2822, April
2001.
[USEAGE] Draft in preparation.
[USEFOR] This Standard.
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@clerew.man.ac.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