usefor-usefor-02 November 2004
[TOC] [ Next >]
Usenet Format Working Group K. Murchison, Ed.
Internet-Draft Oceana Matrix Ltd.
Obsoletes: 1036 (if approved) C. Lindsey
Expires: May 24, 2005 University of Manchester
D. Kohn
Skymoon Ventures
November 23, 2004
News Article Format
draft-ietf-usefor-usefor-02.txt
Status of this Memo
This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of
which he or she 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 May 24, 2005.
Copyright Notice
Copyright (C) The Internet Society (2004).
Abstract
This document specifies the syntax of network news (Netnews) articles
in the context of the "Internet Message Format" (RFC 2822) and
"Multipurpose Internet Mail Extensions (MIME)" (RFC 2045). This
document supersedes RFC 1036, updating it to reflect current practice
and incorporating incremental changes specified in other documents.
Changes since draft-ietf-usefor-usefor-01
o Removed half-hearted discussion of internal format and 8-bit clean
transport.
o Added definitions of "proto-article", "posting agent", "followup",
"followup-agent", "user-agent", and "injecting agent".
o Removed discussion of message/partial MIME messages.
o Noted that the header contents in every line MUST NOT be empty.
o Merged MIME sections.
o Only allow "UT and "GMT" in Date header; disallow all other
<obs-zone>.
o Used Charles' ABNF for <msg-id> and <unstructured>.
o Removed restrictions on length and start character for Newsgroups.
o More verbose description of Path header.
o Disallowed comments in Control header.
o Specified that <control-message> is a verb optionally followed by
whitespace-separated arguments.
o Noted that Supersedes header is different from [Son-of-1036].
o More exact ABNF for Archive and Injection-Info parameters.
o Discussed meaning of "yes", "no", and "filename" in Archive
header.
o Added "Obsolete Headers" section.
o Miscellaneous editorial changes
Changes since draft-kohn-news-article-03
o Document is now a work product of USEFOR
o Added new co-authors
o Added some definitions from draft-ietf-usefor-article-13
o Removed discussion of message/partial MIME messages.
o Removed text that belongs in [USEPRO]
o Reorganized header sections
o Added Archive, User-Agent, Injection-Date, and Injection-Info
headers.
o Used Charles' ABNF for <msg-id> and <unstructured>.
o Removed restrictions on length and start character for Newsgroups.
o Added required SP to ABNF of header definitions.
o Disallowed comments in Control header.
o Xref header allows for non-digit "locations".
o Only allow for a single message-id in Supersedes header.
o Changes to the References header.
o Compatibility changes based on comments from Charles
Changes since draft-ietf-usefor-article-13
o The Mail-Copies-To, Posted-And-Mailed and Complaints-To headers
have been moved to other documents.
o Dropped MIME parameters, as there is no WG consensus (per Chair).
o More exact ABNF for Archive and Injection-Info parameters.
Issues to be addressed
o Decide which definitions should go in this document and in
[USEPRO].
o Decide how much (if any) discussion of Injection-Info content
belongs in this document vs. [USEPRO].
o Do we want to discuss message/partial?
o Add appendixes for changes from RFC 1036 and differences from RFC
2822.
o IANA considerations (the Klyne message header registry is now
official as RFC 3864).
o Collected Syntax.
o Merge more security issues?
o Merge acknowledgments?
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Basic Concepts . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Requirements Notation . . . . . . . . . . . . . . . . . . 5
1.4 Syntax Notation . . . . . . . . . . . . . . . . . . . . . 6
1.5 Definitions . . . . . . . . . . . . . . . . . . . . . . . 6
1.6 Structure of This Document . . . . . . . . . . . . . . . . 7
2. Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1 Base . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 Headers . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 MIME Conformance . . . . . . . . . . . . . . . . . . . . . 9
3. News Headers . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1 Mandatory Headers . . . . . . . . . . . . . . . . . . . . 10
3.1.1 From . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.2 Date . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.3 Message-ID . . . . . . . . . . . . . . . . . . . . . . 11
3.1.4 Subject . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.5 Newsgroups . . . . . . . . . . . . . . . . . . . . . . 13
3.1.6 Path . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.7 Injection-Date . . . . . . . . . . . . . . . . . . . . 14
3.2 Optional Headers . . . . . . . . . . . . . . . . . . . . . 15
3.2.1 References . . . . . . . . . . . . . . . . . . . . . . 15
3.2.2 Followup-To . . . . . . . . . . . . . . . . . . . . . 16
3.2.3 Expires . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.4 Control . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.5 Supersedes . . . . . . . . . . . . . . . . . . . . . . 17
3.2.6 Distribution . . . . . . . . . . . . . . . . . . . . . 17
3.2.7 Summary . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.8 Approved . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.9 Organization . . . . . . . . . . . . . . . . . . . . . 18
3.2.10 Xref . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.11 Archive . . . . . . . . . . . . . . . . . . . . . . 19
3.2.12 User-Agent . . . . . . . . . . . . . . . . . . . . . 19
3.2.13 Injection-Info . . . . . . . . . . . . . . . . . . . 20
3.3 Obsolete Headers . . . . . . . . . . . . . . . . . . . . . 21
3.3.1 Lines . . . . . . . . . . . . . . . . . . . . . . . . 22
4. Internationalization Considerations . . . . . . . . . . . . 23
5. Security Considerations . . . . . . . . . . . . . . . . . . 24
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1 Normative References . . . . . . . . . . . . . . . . . . . . 25
6.2 Informative References . . . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 26
A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
Intellectual Property and Copyright Statements . . . . . . . 29
1. Introduction
1.1 Basic Concepts
1.2 Scope
1.3 Requirements Notation
1.4 Syntax Notation
1.5 Definitions
1.6 Structure of This Document
2. Format
2.1 Base
2.2 Headers
2.3 MIME Conformance
3. News Headers
3.1 Mandatory Headers
3.1.1 From
3.1.2 Date
3.1.3 Message-ID
3.1.4 Subject
3.1.5 Newsgroups
3.1.6 Path
3.1.7 Injection-Date
3.2 Optional Headers
3.2.1 References
3.2.2 Followup-To
3.2.3 Expires
3.2.4 Control
3.2.5 Supersedes
3.2.6 Distribution
3.2.7 Summary
3.2.8 Approved
3.2.9 Organization
3.2.10 Xref
3.2.11 Archive
3.2.12 User-Agent
3.2.13 Injection-Info
3.3 Obsolete Headers
3.3.1 Lines
4. Internationalization Considerations
5. Security Considerations
6. References
6.1 Normative References
6.2 Informative References
[TOC] [ Next >]
#Diff to first older
--- ../usefor-usefor-01/TOC.out September 2004
+++ ../usefor-usefor-02/TOC.out November 2004
@@ -1,14 +1,14 @@
-Usenet Format Working Group C. Lindsey
-Internet-Draft University of Manchester
-Obsoletes: 1036 (if approved) K. Murchison
-Expires: March 15, 2005 Oceana Matrix Ltd.
+Usenet Format Working Group K. Murchison, Ed.
+Internet-Draft Oceana Matrix Ltd.
+Obsoletes: 1036 (if approved) C. Lindsey
+Expires: May 24, 2005 University of Manchester
D. Kohn
Skymoon Ventures
- September 14, 2004
+ November 23, 2004
News Article Format
- draft-ietf-usefor-usefor-01.txt
+ draft-ietf-usefor-usefor-02.txt
Status of this Memo
@@ -35,7 +35,7 @@
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
- This Internet-Draft will expire on March 15, 2005.
+ This Internet-Draft will expire on May 24, 2005.
Copyright Notice
@@ -43,25 +43,60 @@
Abstract
- This document specifies the syntax of network news articles in the
- context of the "Internet Message Format" (RFC 2822) and "Multipurpose
- Internet Mail Extensions (MIME)" (RFC 2045). This document
- supersedes RFC 1036, updating it to reflect current practice and
- incorporating incremental changes specified in other documents.
-
-Changes since draft-ietf-usefor-usefor-00
-
- o Rewrote/reorganized Abstract and Introduction.
+ This document specifies the syntax of network news (Netnews) articles
+ in the context of the "Internet Message Format" (RFC 2822) and
+ "Multipurpose Internet Mail Extensions (MIME)" (RFC 2045). This
+ document supersedes RFC 1036, updating it to reflect current practice
+ and incorporating incremental changes specified in other documents.
+
+Changes since draft-ietf-usefor-usefor-01
+
+ o Removed half-hearted discussion of internal format and 8-bit clean
+ transport.
+ o Added definitions of "proto-article", "posting agent", "followup",
+ "followup-agent", "user-agent", and "injecting agent".
+ o Removed discussion of message/partial MIME messages.
+ o Noted that the header contents in every line MUST NOT be empty.
+ o Merged MIME sections.
+ o Only allow "UT and "GMT" in Date header; disallow all other
+ <obs-zone>.
+ o Used Charles' ABNF for <msg-id> and <unstructured>.
+ o Removed restrictions on length and start character for Newsgroups.
+ o More verbose description of Path header.
+ o Disallowed comments in Control header.
+ o Specified that <control-message> is a verb optionally followed by
+ whitespace-separated arguments.
+ o Noted that Supersedes header is different from [Son-of-1036].
+ o More exact ABNF for Archive and Injection-Info parameters.
+ o Discussed meaning of "yes", "no", and "filename" in Archive
+ header.
+ o Added "Obsolete Headers" section.
+ o Miscellaneous editorial changes
+
+Changes since draft-kohn-news-article-03
+
+ o Document is now a work product of USEFOR
+ o Added new co-authors
+ o Added some definitions from draft-ietf-usefor-article-13
+ o Removed discussion of message/partial MIME messages.
+ o Removed text that belongs in [USEPRO]
+ o Reorganized header sections
+ o Added Archive, User-Agent, Injection-Date, and Injection-Info
+ headers.
+ o Used Charles' ABNF for <msg-id> and <unstructured>.
+ o Removed restrictions on length and start character for Newsgroups.
o Added required SP to ABNF of header definitions.
- o Reorganized header sections.
- o Compatibility changes based on comments from Charles.
- o Added Injection-Date and Injection-Info headers.
+ o Disallowed comments in Control header.
+ o Xref header allows for non-digit "locations".
+ o Only allow for a single message-id in Supersedes header.
+ o Changes to the References header.
+ o Compatibility changes based on comments from Charles
Changes since draft-ietf-usefor-article-13
-
o The Mail-Copies-To, Posted-And-Mailed and Complaints-To headers
have been moved to other documents.
o Dropped MIME parameters, as there is no WG consensus (per Chair).
+ o More exact ABNF for Archive and Injection-Info parameters.
Issues to be addressed
@@ -70,53 +105,57 @@
o Decide how much (if any) discussion of Injection-Info content
belongs in this document vs. [USEPRO].
o Do we want to discuss message/partial?
- o Add appendixes for obsolete headers, changes from RFC 1036 and
- differences from RFC 2822.
+ o Add appendixes for changes from RFC 1036 and differences from RFC
+ 2822.
+ o IANA considerations (the Klyne message header registry is now
+ official as RFC 3864).
+ o Collected Syntax.
o Merge more security issues?
o Merge acknowledgments?
Table of Contents
- 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
- 1.1 Basic Concepts . . . . . . . . . . . . . . . . . . . . . . 4
- 1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4
+ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
+ 1.1 Basic Concepts . . . . . . . . . . . . . . . . . . . . . . 5
+ 1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Requirements Notation . . . . . . . . . . . . . . . . . . 5
- 1.4 Syntax Notation . . . . . . . . . . . . . . . . . . . . . 5
- 1.5 Definitions . . . . . . . . . . . . . . . . . . . . . . . 5
- 1.6 Structure of This Document . . . . . . . . . . . . . . . . 5
- 2. Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
- 2.1 Base . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
- 2.2 Header Fields . . . . . . . . . . . . . . . . . . . . . . 7
- 2.3 MIME Conformance . . . . . . . . . . . . . . . . . . . . . 8
- 2.4 Additional MIME Support . . . . . . . . . . . . . . . . . 8
- 3. News Headers . . . . . . . . . . . . . . . . . . . . . . . . 9
- 3.1 Mandatory Headers . . . . . . . . . . . . . . . . . . . . 9
- 3.1.1 From . . . . . . . . . . . . . . . . . . . . . . . . . 9
- 3.1.2 Subject . . . . . . . . . . . . . . . . . . . . . . . 9
- 3.1.3 Date . . . . . . . . . . . . . . . . . . . . . . . . . 9
- 3.1.4 Message-ID . . . . . . . . . . . . . . . . . . . . . . 10
- 3.1.5 Newsgroups . . . . . . . . . . . . . . . . . . . . . . 11
- 3.1.6 Path . . . . . . . . . . . . . . . . . . . . . . . . . 11
- 3.1.7 Injection-Date . . . . . . . . . . . . . . . . . . . . 12
- 3.2 Optional Headers . . . . . . . . . . . . . . . . . . . . . 12
- 3.2.1 References . . . . . . . . . . . . . . . . . . . . . . 13
- 3.2.2 Followup-To . . . . . . . . . . . . . . . . . . . . . 13
- 3.2.3 Expires . . . . . . . . . . . . . . . . . . . . . . . 13
- 3.2.4 Control . . . . . . . . . . . . . . . . . . . . . . . 13
- 3.2.5 Supersedes . . . . . . . . . . . . . . . . . . . . . . 14
- 3.2.6 Distribution . . . . . . . . . . . . . . . . . . . . . 14
- 3.2.7 Summary . . . . . . . . . . . . . . . . . . . . . . . 14
- 3.2.8 Approved . . . . . . . . . . . . . . . . . . . . . . . 15
- 3.2.9 Organization . . . . . . . . . . . . . . . . . . . . . 15
- 3.2.10 Xref . . . . . . . . . . . . . . . . . . . . . . . . 15
- 3.2.11 Archive . . . . . . . . . . . . . . . . . . . . . . 15
- 3.2.12 User-Agent . . . . . . . . . . . . . . . . . . . . . 16
- 3.2.13 Injection-Info . . . . . . . . . . . . . . . . . . . 16
- 4. Internationalization Considerations . . . . . . . . . . . . 18
- 5. Security Considerations . . . . . . . . . . . . . . . . . . 19
- 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
- 6.1 Normative References . . . . . . . . . . . . . . . . . . . . 20
- 6.2 Informative References . . . . . . . . . . . . . . . . . . . 20
- Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 21
- A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23
- Intellectual Property and Copyright Statements . . . . . . . 24
+ 1.4 Syntax Notation . . . . . . . . . . . . . . . . . . . . . 6
+ 1.5 Definitions . . . . . . . . . . . . . . . . . . . . . . . 6
+ 1.6 Structure of This Document . . . . . . . . . . . . . . . . 7
+ 2. Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
+ 2.1 Base . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
+ 2.2 Headers . . . . . . . . . . . . . . . . . . . . . . . . . 8
+ 2.3 MIME Conformance . . . . . . . . . . . . . . . . . . . . . 9
+ 3. News Headers . . . . . . . . . . . . . . . . . . . . . . . . 10
+ 3.1 Mandatory Headers . . . . . . . . . . . . . . . . . . . . 10
+ 3.1.1 From . . . . . . . . . . . . . . . . . . . . . . . . . 10
+ 3.1.2 Date . . . . . . . . . . . . . . . . . . . . . . . . . 10
+ 3.1.3 Message-ID . . . . . . . . . . . . . . . . . . . . . . 11
+ 3.1.4 Subject . . . . . . . . . . . . . . . . . . . . . . . 13
+ 3.1.5 Newsgroups . . . . . . . . . . . . . . . . . . . . . . 13
+ 3.1.6 Path . . . . . . . . . . . . . . . . . . . . . . . . . 14
+ 3.1.7 Injection-Date . . . . . . . . . . . . . . . . . . . . 14
+ 3.2 Optional Headers . . . . . . . . . . . . . . . . . . . . . 15
+ 3.2.1 References . . . . . . . . . . . . . . . . . . . . . . 15
+ 3.2.2 Followup-To . . . . . . . . . . . . . . . . . . . . . 16
+ 3.2.3 Expires . . . . . . . . . . . . . . . . . . . . . . . 16
+ 3.2.4 Control . . . . . . . . . . . . . . . . . . . . . . . 16
+ 3.2.5 Supersedes . . . . . . . . . . . . . . . . . . . . . . 17
+ 3.2.6 Distribution . . . . . . . . . . . . . . . . . . . . . 17
+ 3.2.7 Summary . . . . . . . . . . . . . . . . . . . . . . . 18
+ 3.2.8 Approved . . . . . . . . . . . . . . . . . . . . . . . 18
+ 3.2.9 Organization . . . . . . . . . . . . . . . . . . . . . 18
+ 3.2.10 Xref . . . . . . . . . . . . . . . . . . . . . . . . 18
+ 3.2.11 Archive . . . . . . . . . . . . . . . . . . . . . . 19
+ 3.2.12 User-Agent . . . . . . . . . . . . . . . . . . . . . 19
+ 3.2.13 Injection-Info . . . . . . . . . . . . . . . . . . . 20
+ 3.3 Obsolete Headers . . . . . . . . . . . . . . . . . . . . . 21
+ 3.3.1 Lines . . . . . . . . . . . . . . . . . . . . . . . . 22
+ 4. Internationalization Considerations . . . . . . . . . . . . 23
+ 5. Security Considerations . . . . . . . . . . . . . . . . . . 24
+ 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
+ 6.1 Normative References . . . . . . . . . . . . . . . . . . . . 25
+ 6.2 Informative References . . . . . . . . . . . . . . . . . . . 25
+ Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 26
+ A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
+ Intellectual Property and Copyright Statements . . . . . . . 29