| TOC |
|
This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026.
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 October 12, 2004.
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document defines the initial IANA registration for permanent Netnews message header fields, per [[[RFC XXXX]]] [1].
Please send comments to <???@???>. To subscribe to this list, send a message with the body 'subscribe' to <???@???>.
| TOC |
| TOC |
This document defines IANA registration for a number of Netnews header fields, per Registration procedures for message header fields[1].
Section Registration templates 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 [3].
NOTE: indented comments like this provide additional nonessential information about the rationale behind this document.
[[[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.]]]
| TOC |
Header registry entries are summarized in tabular form for convenience of reference, and presented in full in the following sections.
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
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 _:n4132
- Description:
- Mailbox of article poster
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.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.
- Description:
- Article date and time
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.1)
- 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.
- Description:
- Newsgroups for posting
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.1)
- Related information:
- Specifies the list of newsgroups in which the article is intended to appear.
- Description:
- Topic of article
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.1)
- Related information:
- Contains a short string identifying the topic of the article.
- Description:
- Message identifier
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.1)
- 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.
- Description:
- Trace of path
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.1)
- Related information:
- Shows the path the article took to reach the current system
- Description:
- Mailbox for email replies to article
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- 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.
- Description:
- Mailbox of article sender
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Specifies the mailbox of the agent responsible for the actual posting of the article.
- Description:
- Newsgroups for followups
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Specifies the list of newsgroups in which followups are intended to appear.
- Description:
- Expiry date
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Specifies a suggested expiry date for the article.
- Description:
- Control message
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Specifies actions to be taken by host machines.
- Description:
- Distribution scope
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Specifies limits to the propagation of the article.
- Description:
- Poster's organization
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Describes the organization to which the poster belongs.
- Description:
- Keywords
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Contains a few well-selected keywords identifying the intent of the article.
- Description:
- Article summary
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Contains a brief summary of the article.
- Description:
- Mailbox of approving authority
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Indicates the authority approving the posting of a control message or moderated article.
- Description:
- Line count
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Contains a count of the lines in the body of the article.
- Description:
- _:n4132
- Applicable protocol:
- Netnews[2]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1036[2] (section 2.2)
- Related information:
- Indicates, for a particular server, the article's location within each newsgroup.
| TOC |
This specification provides initial registrations of Netnews header fields in the "Permanent Message Header Field Registry", defined by Registration procedures for message header fields[1].
| TOC |
No security considerations are introduced by this registration document beyond those already inherent in the use of Netnews message header fields referenced.
| TOC |
[[[???]]]
| TOC |
| [1] | Klyne, G., Nottingham, M. and J. Mogul, "Registration procedures for message headers", Oct 2003. |
| [2] | Horton, M. and R. Adams, "Standard for interchange of USENET messages", RFC 1036, December 1987. |
| [3] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997 (TXT, HTML, XML). |
| TOC |
| Charles Lindsey | |
| ??? | |
| UK | |
| EMail: | chl@clerew.man.ac.uk |
| TOC |
[[[Please remove this section on final publication]]]
- 00a 13-Apr-2004:
- Document initially created.
| TOC |
The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.
Funding for the RFC Editor function is currently provided by the Internet Society.