Network Working Group C. Lindsey Internet-Draft University of Manchester Expires: January 3, 2005 G. Klyne Nine by Nine July 5, 2004 Registration of Netnews header fields draft-lindsey-hdrreg-netnews-01 Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on January 3, 2005. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This document defines the initial IANA registration for permanent Netnews message header fields, per [[[RFC XXXX/ draft-klyne-msghdr-registry-07]]]. Discussion of this document Please send comments to . For mailing list subscription and archive information, please see [5]. Lindsey & Klyne Expires January 3, 2005 [Page 1] Internet-Draft Netnews header field registration July 2004 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Structure of this document . . . . . . . . . . . . . . . . 3 1.2 Document terminology and conventions . . . . . . . . . . . 3 2. Registration templates . . . . . . . . . . . . . . . . . . . 3 2.1 Permanent Netnews field registrations . . . . . . . . . . 4 2.1.1 Header field: From . . . . . . . . . . . . . . . . . . 4 2.1.2 Header field: Date . . . . . . . . . . . . . . . . . . 5 2.1.3 Header field: Newsgroups . . . . . . . . . . . . . . . 5 2.1.4 Header field: Subject . . . . . . . . . . . . . . . . 5 2.1.5 Header field: Message-ID . . . . . . . . . . . . . . . 6 2.1.6 Header field: Path . . . . . . . . . . . . . . . . . . 6 2.1.7 Header field: Reply-To . . . . . . . . . . . . . . . . 7 2.1.8 Header field: Sender . . . . . . . . . . . . . . . . . 7 2.1.9 Header field: Followup-To . . . . . . . . . . . . . . 8 2.1.10 Header field: Expires . . . . . . . . . . . . . . . 8 2.1.11 Header field: References . . . . . . . . . . . . . . 9 2.1.12 Header field: Control . . . . . . . . . . . . . . . 9 2.1.13 Header field: Distribution . . . . . . . . . . . . . 10 2.1.14 Header field: Organization . . . . . . . . . . . . . 10 2.1.15 Header field: Keywords . . . . . . . . . . . . . . . 10 2.1.16 Header field: Summary . . . . . . . . . . . . . . . 11 2.1.17 Header field: Approved . . . . . . . . . . . . . . . 11 2.1.18 Header field: Lines . . . . . . . . . . . . . . . . 12 2.1.19 Header field: Xref . . . . . . . . . . . . . . . . . 12 3. IANA considerations . . . . . . . . . . . . . . . . . . . . 13 4. Security considerations . . . . . . . . . . . . . . . . . . 13 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.1 Normative references . . . . . . . . . . . . . . . . . . . . 13 5.2 Informative references . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 14 A. Revision history . . . . . . . . . . . . . . . . . . . . . . 14 A.1 draft-lindsey-hdrreg-netnews-01 . . . . . . . . . . . . . 14 A.2 draft-lindsey-hdrreg-netnews-00 . . . . . . . . . . . . . 15 Intellectual Property and Copyright Statements . . . . . . . 16 Lindsey & Klyne Expires January 3, 2005 [Page 2] Internet-Draft Netnews header field registration July 2004 1. Introduction This document defines IANA registration for a number of Netnews header fields, per Registration procedures for message header fields [3]. (See Registration of mail and MIME header fields [4] for the corresponding email and MIME header field registrations.) 1.1 Structure of this document Section Section 2 contains the submission for initial registration of Netnews related message header fields. 1.2 Document terminology and conventions 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 [2]. [[[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.]]] 2. Registration templates Header field registry entries are summarized in tabular form for convenience of reference, and presented in full in the following sections. Lindsey & Klyne Expires January 3, 2005 [Page 3] Internet-Draft Netnews header field registration July 2004 2.1 Permanent Netnews field registrations Header name Protocol ----------- -------- From Netnews Mailbox of article poster Date Netnews Article date and time Newsgroups Netnews Newsgroups for posting Subject Netnews Topic of article Message-ID Netnews Message identifier Path Netnews Trace of path Reply-To Netnews Mailbox for email replies to article Sender Netnews Mailbox of article sender Followup-To Netnews Newsgroups for followups Expires Netnews Expiry date References Netnews References Control Netnews Control message Distribution Netnews Distribution scope Organization Netnews Poster's organization Keywords Netnews Keywords Summary Netnews Article summary Approved Netnews Mailbox of approving authority Lines Netnews Line count Xref Netnews Article location 2.1.1 Header field: From Description: Mailbox of article poster Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.1.1) Related information: 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. Lindsey & Klyne Expires January 3, 2005 [Page 4] Internet-Draft Netnews header field registration July 2004 2.1.2 Header field: Date Description: Article date and time Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.1.2) Related information: 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. 2.1.3 Header field: Newsgroups Description: Newsgroups for posting Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.1.3) Related information: Specifies the list of newsgroups in which the article is intended to appear. 2.1.4 Header field: Subject Lindsey & Klyne Expires January 3, 2005 [Page 5] Internet-Draft Netnews header field registration July 2004 Description: Topic of article Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.1.4) Related information: Contains a short string identifying the topic of the article. 2.1.5 Header field: Message-ID Description: Message identifier Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.1.5) Related information: 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. 2.1.6 Header field: Path Description: Trace of path Lindsey & Klyne Expires January 3, 2005 [Page 6] Internet-Draft Netnews header field registration July 2004 Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.1.6) Related information: Shows the path the article took to reach the current system 2.1.7 Header field: Reply-To Description: Mailbox for email replies to article Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.1) Related information: When the "Reply-To:" field is present, it indicates the mailbox(es) to which the poster of the article suggests that replies be sent. 2.1.8 Header field: Sender Description: Mailbox of article sender Applicable protocol: Netnews [1] Status: informational Lindsey & Klyne Expires January 3, 2005 [Page 7] Internet-Draft Netnews header field registration July 2004 Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.2) Related information: Specifies the mailbox of the agent responsible for the actual posting of the article. 2.1.9 Header field: Followup-To Description: Newsgroups for followups Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.3) Related information: Specifies the list of newsgroups in which followups are intended to appear. 2.1.10 Header field: Expires Description: Expiry date Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Lindsey & Klyne Expires January 3, 2005 [Page 8] Internet-Draft Netnews header field registration July 2004 Specification document(s): RFC 1036 [1] (section 2.2.4) Related information: Specifies a suggested expiry date for the article. 2.1.11 Header field: References Description: References Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.5) Related information: Contains a list of precursors to the article. 2.1.12 Header field: Control Description: Control message Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.6) Related information: Specifies actions to be taken by host machines. Lindsey & Klyne Expires January 3, 2005 [Page 9] Internet-Draft Netnews header field registration July 2004 2.1.13 Header field: Distribution Description: Distribution scope Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.7) Related information: Specifies limits to the propagation of the article. 2.1.14 Header field: Organization Description: Poster's organization Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.8) Related information: Describes the organization to which the poster belongs. 2.1.15 Header field: Keywords Description: Keywords Applicable protocol: Netnews [1] Lindsey & Klyne Expires January 3, 2005 [Page 10] Internet-Draft Netnews header field registration July 2004 Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.9) Related information: Contains a few well-selected keywords identifying the intent of the article. 2.1.16 Header field: Summary Description: Article summary Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.10) Related information: Contains a brief summary of the article. 2.1.17 Header field: Approved Description: Mailbox of approving authority Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Lindsey & Klyne Expires January 3, 2005 [Page 11] Internet-Draft Netnews header field registration July 2004 Specification document(s): RFC 1036 [1] (section 2.2.11) Related information: Indicates the authority approving the posting of a control message or moderated article. 2.1.18 Header field: Lines Description: Line count Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.12) Related information: Contains a count of the lines in the body of the article. 2.1.19 Header field: Xref Description: Article location Applicable protocol: Netnews [1] Status: informational Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force Specification document(s): RFC 1036 [1] (section 2.2.13) Related information: Indicates, for a particular server, the article's location within each newsgroup. Lindsey & Klyne Expires January 3, 2005 [Page 12] Internet-Draft Netnews header field registration July 2004 3. IANA considerations This specification (Section 2) provides initial registrations of Netnews header fields in the "Permanent Message Header Field Registry", defined by Registration procedures for message header fields [3]. 4. Security considerations No security considerations are introduced by this registration document beyond those already inherent in the use of Netnews message header fields referenced. 5. References 5.1 Normative references [1] Horton, M. and R. Adams, "Standard for interchange of USENET messages", RFC 1036, December 1987. [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [3] Klyne, G., Nottingham, M. and J. Mogul, "Registration procedures for message headers", Oct 2003, . 5.2 Informative references [4] Klyne, G. and J. Palme, "Registration of mail and MIME header fields", Internet draft draft-klyne-hdrreg-mail-05, May 2004, . URIs [5] Lindsey & Klyne Expires January 3, 2005 [Page 13] Internet-Draft Netnews header field registration July 2004 Authors' Addresses Charles Lindsey University of Manchester 5 Clerewood Avenue Heald Green Cheadle, Cheshire SK8 3JU UK Phone: +44 161 436 6131 EMail: chl@clerew.man.ac.uk Graham Klyne Nine by Nine UK EMail: GK-IETF@ninebynine.org URI: http://www.ninebynine.net/ Appendix A. Revision history [[[Please remove this section on final publication]]] A.1 draft-lindsey-hdrreg-netnews-01 01c 05-Jul-2004: * Re-arranged revision history. * Updated draft-klyne-hdrreg-mail reference. * Fixed XML source to pass online XML2RFC validator in struct mode 01b 29-Jun-2004: * 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". Lindsey & Klyne Expires January 3, 2005 [Page 14] Internet-Draft Netnews header field registration July 2004 01a 01-Jun-2004: * 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). A.2 draft-lindsey-hdrreg-netnews-00 00b 19-Apr-2004: * 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. 00a 13-Apr-2004: * Document initially created. Lindsey & Klyne Expires January 3, 2005 [Page 15] Internet-Draft Netnews header field registration July 2004 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Lindsey & Klyne Expires January 3, 2005 [Page 16]