Registration of Netnews header fields University of Manchester
5 Clerewood Avenue Heald Green Cheadle Cheshire SK8 3JU UK +44 161 436 6131 chl@clerew.man.ac.uk
Nine by Nine
UK GK-IETF@ninebynine.org http://www.ninebynine.net/
Application message header fields Netnews headers registration IANA This document defines the initial IANA registration for permanent Netnews message header fields, per [[[RFC XXXX/draft-klyne-msghdr-registry-07]]]. Please send comments to <usenet-format@landfield.com>. For mailing list subscription and archive information, please see .
This document defines IANA registration for a number of Netnews header fields, per Registration procedures for message header fields. (See Registration of mail and MIME header fields for the corresponding email and MIME header field registrations.)
Section contains the submission for initial registration of Netnews related message header fields.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 . [[[Editorial comments and questions about outstanding issues are provided in triple brackets like this. These working comments should be resolved and removed prior to final publication.]]]
Header field registry entries are summarized in tabular form for convenience of reference, and presented in full in the following sections.
Mailbox of article poster Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.1.1) Specifies the poster(s) of the article, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the article.
Article date and time Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.1.2) Specifies the date and time at which the poster of the article indicated that the message was complete and ready to enter the netnews network.
Newsgroups for posting Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.1.3) Specifies the list of newsgroups in which the article is intended to appear.
Topic of article Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.1.4) Contains a short string identifying the topic of the article.
Message identifier Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.1.5) Contains a single unique message identifier that distinguishes a given article from all other articles ever posted. All copies of that article, wherever on the network they may be found, will have that same message identifier.
Trace of path Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.1.6) Shows the path the article took to reach the current system
Mailbox for email replies to article Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.1) When the "Reply-To:" field is present, it indicates the mailbox(es) to which the poster of the article suggests that replies be sent.
Mailbox of article sender Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.2) Specifies the mailbox of the agent responsible for the actual posting of the article.
Newsgroups for followups Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.3) Specifies the list of newsgroups in which followups are intended to appear.
Expiry date Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.4) Specifies a suggested expiry date for the article.
References Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.5) Contains a list of precursors to the article.
Control message Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.6) Specifies actions to be taken by host machines.
Distribution scope Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.7) Specifies limits to the propagation of the article.
Poster's organization Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.8) Describes the organization to which the poster belongs.
Keywords Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.9) Contains a few well-selected keywords identifying the intent of the article.
Article summary Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.10) Contains a brief summary of the article.
Mailbox of approving authority Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.11) Indicates the authority approving the posting of a control message or moderated article.
Line count Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.12) Contains a count of the lines in the body of the article.
Article location Netnews informational IETF (mailto:iesg@ietf.org) Internet Engineering Task Force RFC 1036 (section 2.2.13) Indicates, for a particular server, the article's location within each newsgroup.
This specification () provides initial registrations of Netnews header fields in the "Permanent Message Header Field Registry", defined by Registration procedures for message header fields.
No security considerations are introduced by this registration document beyond those already inherent in the use of Netnews message header fields referenced.
Registration procedures for message headers Nine by Nine
UK GK-IETF@ninebynine.org http://www.ninebynine.net/
BEA Systems
235 Montgomery St. Level 15 San Francisco CA 94104 USA mnot@pobox.com
Western Research Laboratory, Compaq Computer Corporation
250 University Avenue Palo Alto CA 94305 US JeffMogul@acm.org
Registration of mail and MIME header fields Nine by Nine Stockholm University/KTH
[[[Please remove this section on final publication]]]
Re-arranged revision history. Updated draft-klyne-hdrreg-mail reference. Fixed XML source to pass online XML2RFC validator in struct mode Updated document I-D revision to -01. In IANA considerations section, added cross-link to section containing the registration entries (following IANA feedback regarding the similar mail header field registration draft). Updated UPR declaration to "full3667". Status of RFC 1036 changed to "informational". Additional section reference for the Subject-header. Missing References-header added. All section references extended to 3 levels (e.g. section 2.1.2).
Editorial tweaks. Added GK as second editor. Indicated USEFOR list for discussion. Added informational reference to mail header fields registration draft. Fix up description for Xref header field. Document initially created.