usefor-usepro-00 August 2004
[TOC] [ Next >]
INTERNET-DRAFT Charles H. Lindsey
Usenet Format Working Group University of Manchester
August 2004
News Article Architecture and Protocols
<draft-ietf-usefor-usepro-00.txt>
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 in February 2005.
Abstract
This Draft, together with its companion draft [USEFOR], are
intended as standards track documents, together obsoleting RFC
1036, which itself dates from 1987.
This Standard defines the architecture of Netnews systems and
specifies the requirements to be met by software which originates,
distributes, stores and displays Netnews articles.
Since the 1980s, Usenet has grown explosively, and many Internet and
non-Internet sites now participate. In addition, the Netnews
technology is now in widespread use for other purposes.
Backward compatibility has been a major goal of this endeavour, but
where this standard and earlier documents or practices conflict, this
standard should be followed. In most such cases, current practice is
already compatible with these changes.
A companion Current Best Practice document [USEAGE], addressing
requirements which are present for Social rather than Normative
reasons is in preparation.
[The use of the words "this standard" within this document when
referring to itself does not imply that this draft yet has pretensions
to be a standard, but rather indicates what will become the case if and
when it is accepted as an RFC with the status of a proposed or draft
standard.]
[Remarks enclosed in square brackets and aligned with the left margin,
such as this one, are not part of this draft, but are editorial notes to
explain matters amongst ourselves, or to point out alternatives, or to
assist the RFC Editor.]
[In this draft, references to [NNTP] are to be replaced by references to
the RFC arising from the series of drafts draft-ietf-nntpext-base-*.txt,
which has now passed its IETF last call.]
Table of Contents
1. Introduction .................................................. 0
1.1. Basic Concepts ............................................ 0
1.2. Objectives ................................................ 0
1.3. Historical Outline ........................................ 0
2. Definitions, Notations and Conventions ........................ 0
2.1. Definitions ............................................... 0
2.2. Defining the Architecture ................................. 0
2.3. Textual Notations ......................................... 0
3. Changes to the existing protocols ............................. 0
3.1. Principal Changes ......................................... 0
3.2. Transitional Arrangements ................................. 0
4. Transport ..................................................... 0
5. Definition of new Media Types ................................. 0
5.1. Application/news-transmission ............................. 0
5.2. Message/news obsoleted .................................... 0
5.3. Application/news-groupinfo ................................ 0
5.4. Application/news-checkgroups .............................. 0
6. Control Messages .............................................. 0
6.1. Digital Signature of Headers .............................. 0
6.2. Group Control Messages .................................... 0
6.2.1. The 'newgroup' Control Message ........................ 0
6.2.1.1. The Body of the 'newgroup' Control Message ........ 0
6.2.1.2. Initial Articles .................................. 0
6.2.1.3. Example ........................................... 0
6.2.2. The 'rmgroup' Control Message ......................... 0
6.2.2.1. Example ........................................... 0
6.2.3. The 'mvgroup' Control Message ......................... 0
6.2.3.1. Example ........................................... 0
6.2.4. The 'checkgroups' Control Message ..................... 0
6.3. Cancel .................................................... 0
6.4. Ihave, sendme ............................................. 0
6.5. Obsolete control messages. ............................... 0
7. Duties of Various Agents ...................................... 0
7.1. General principles to be followed ......................... 0
7.2. Duties of an Injecting Agent .............................. 0
7.2.1. Proto-articles ........................................ 0
7.2.2. Procedure to be followed by Injecting Agents .......... 0
7.3. Procedure for Forwarding to a Moderator ................... 0
7.4. Duties of a Relaying Agent ................................ 0
7.4.1. Example ............................................... 0
7.5. Duties of a Serving Agent ................................. 0
7.6. Duties of a Posting Agent ................................. 0
7.7. Duties of a Followup Agent ................................ 0
7.8. Duties of a Moderator ..................................... 0
7.9. Duties of a Gateway ....................................... 0
7.9.1. Duties of an Outgoing Gateway ......................... 0
7.9.2. Duties of an Incoming Gateway ......................... 0
7.9.3. Example ............................................... 0
8. Security and Related Considerations ........................... 0
8.1. Leakage ................................................... 0
8.2. Attacks ................................................... 0
8.2.1. Denial of Service ..................................... 0
8.2.2. Compromise of System Integrity ........................ 0
8.3. Liability ................................................. 0
9. IANA Considerations ........................................... 0
10. References ................................................... 0
11. Acknowledgements ............................................. 0
12. Contact Address .............................................. 0
Appendix A.1 - A-News Article Format .............................. 0
Appendix A.2 - Early B-News Article Format ........................ 0
Appendix A.3 - Obsolete Control Messages .......................... 0
Appendix B - Notices .............................................. 0
Appendix C - Change Log ........................................... 0
[This draft [USEPRO] and its partner [USEFOR] are an interim stage in
the splitting into two parts of the earlier draft [ARTICLE]. There is a
certain amount of material - basic concepts, definitions, etc - which
ultimately need occur in only one of the documents, and further such
material which may not be needed at all (e.g. terms currently defined
which in the event may not get used). For the moment, all such material
has been retained in the present draft (it being, in any case, easier to
take unwanted stuff out than to put new stuff in). It has also to be
decided, for such material which is needed by both documents, which one
(the "Primary") should contain it and which one should incorporate it by
reference (essentially, this draft is written so that it could be the
Primary).]
[Again, references in this document to sections which ultimately are
expected to be in [USEFOR] are still to the old sections in [ARTICLE],
since [USEFOR] is not stabilized enough to refer to specific sections in
it yet. These references can be recognized by being prefixed with "a-".
These references can be fixed up later as we find the proper places for
them to point to. In any case, there will doubtless be more toing and
froing of texts between the two documents before we are done.]
1. Introduction
1.1. Basic Concepts
1.2. Objectives
1.3. Historical Outline
2. Definitions, Notations and Conventions
2.1. Definitions
2.2. Defining the Architecture
2.3. Textual Notations
3. Changes to the existing protocols
3.1. Principal Changes
3.2. Transitional Arrangements
4. Transport
5. Definition of new Media Types
5.1. Application/news-transmission
5.2. Message/news obsoleted
5.3. Application/news-groupinfo
5.4. Application/news-checkgroups
6. Control Messages
6.1. Digital Signature of Headers
6.2. Group Control Messages
6.2.1.2. Initial Articles
6.2.1.3. Example
6.2.2.1. Example
6.2.3.1. Example
6.3. Cancel
6.4. Ihave, sendme
6.5. Obsolete control messages.
7. Duties of Various Agents
7.1. General principles to be followed
7.2. Duties of an Injecting Agent
7.2.1. Proto-articles
7.2.2. Procedure to be followed by Injecting Agents
7.3. Procedure for Forwarding to a Moderator
7.4. Duties of a Relaying Agent
7.4.1. Example
7.5. Duties of a Serving Agent
7.6. Duties of a Posting Agent
7.7. Duties of a Followup Agent
7.8. Duties of a Moderator
7.9. Duties of a Gateway
7.9.1. Duties of an Outgoing Gateway
7.9.2. Duties of an Incoming Gateway
7.9.3. Example
8. Security and Related Considerations
8.1. Leakage
8.2. Attacks
8.2.1. Denial of Service
8.2.2. Compromise of System Integrity
8.3. Liability
9. IANA Considerations
10. References
11. Acknowledgements
12. Contact Address
[TOC] [ Next >]
#Diff to first older
--- ../usefor-article-13/TOC.out May 2004
+++ ../usefor-usepro-00/TOC.out August 2004
@@ -1,14 +1,16 @@
INTERNET-DRAFT Charles H. Lindsey
Usenet Format Working Group University of Manchester
- May 2004
+ August 2004
- News Article Format and Transmission
- <draft-ietf-usefor-article-13.txt>
+ News Article Architecture and Protocols
+ <draft-ietf-usefor-usepro-00.txt>
Status of this Memo
- This document is an Internet-Draft and is in full conformance with
- all provisions of Section 10 of RFC 2026.
+ 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
@@ -27,14 +29,17 @@
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
-Abstract
+ This Internet-Draft will expire in February 2005.
- This Draft is intended as a standards track document, obsoleting
- RFC 1036, which itself dates from 1987.
+Abstract
- This Standard defines the format of Netnews articles and specifies
- the requirements to be met by software which originates, distributes,
- stores and displays them.
+ This Draft, together with its companion draft [USEFOR], are
+ intended as standards track documents, together obsoleting RFC
+ 1036, which itself dates from 1987.
+
+ This Standard defines the architecture of Netnews systems and
+ specifies the requirements to be met by software which originates,
+ distributes, stores and displays Netnews articles.
Since the 1980s, Usenet has grown explosively, and many Internet and
non-Internet sites now participate. In addition, the Netnews
@@ -45,18 +50,11 @@
standard should be followed. In most such cases, current practice is
already compatible with these changes.
-[Draft-10 removed all the Internationalization features (i.e. those
-involving the use of the UTF-8 charset in headers). This is being done
-so as to facilitate publishing those features, or similar ones, as an
-experimental protocol at a later stage.
-
A companion Current Best Practice document [USEAGE], addressing
-requirements which are present for Social rather than Normative reasons
-is in preparation.
+ requirements which are present for Social rather than Normative
+ reasons is in preparation.
+
-There may well be a further split of the present draft into a
-syntax/semantics part and a protocol part. Thus this present draft is
-but an intermediate stage in an ongoing development process.]
[The use of the words "this standard" within this document when
referring to itself does not imply that this draft yet has pretensions
@@ -69,12 +67,9 @@
explain matters amongst ourselves, or to point out alternatives, or to
assist the RFC Editor.]
-[In this draft, references to [NNTP] are to be replaced by [RFC 977], or
-else by references to the RFC arising from the series of drafts draft-
-ietf-nntpext-base-*.txt, in the event that such RFC has been accepted at
-the time this document is published.
-References to [KLYNE], which has now passed its IETF last call, are to
-be replaced by references to the eventual RFC.]
+[In this draft, references to [NNTP] are to be replaced by references to
+the RFC arising from the series of drafts draft-ietf-nntpext-base-*.txt,
+which has now passed its IETF last call.]
Table of Contents
@@ -83,143 +78,85 @@
1.1. Basic Concepts ............................................ 0
1.2. Objectives ................................................ 0
1.3. Historical Outline ........................................ 0
- 1.4. Transport ................................................. 0
2. Definitions, Notations and Conventions ........................ 0
2.1. Definitions ............................................... 0
- 2.2. Textual Notations ......................................... 0
- 2.3. Relation To Email and MIME ................................ 0
- 2.4. Syntax .................................................... 0
- 2.4.1. Syntax Notation ....................................... 0
- 2.4.2. Syntax copied from other standards .................... 0
- 2.4.3. Syntax adapted from Email and MIME .................... 0
- 2.5. Language .................................................. 0
+ 2.2. Defining the Architecture ................................. 0
+ 2.3. Textual Notations ......................................... 0
3. Changes to the existing protocols ............................. 0
3.1. Principal Changes ......................................... 0
3.2. Transitional Arrangements ................................. 0
-4. Basic Format .................................................. 0
- 4.1. Syntax of News Articles ................................... 0
- 4.2. Headers ................................................... 0
- 4.2.1. Naming of Headers ..................................... 0
- 4.2.2. MIME-style Parameters ................................. 0
- 4.2.3. White Space and Continuations ......................... 0
- 4.2.4. Comments .............................................. 0
- 4.2.5. Header Properties ..................................... 0
- 4.2.5.1. Experimental Headers .............................. 0
- 4.2.5.2. Inheritable Headers ............................... 0
- 4.2.5.3. Variant Headers ................................... 0
- 4.3. Body ...................................................... 0
- 4.4. Octets, Characters and Character Sets ..................... 0
- 4.4.1. Character Sets within Article Headers ................. 0
- 4.4.2. Character Sets within Article Bodies .................. 0
- 4.5. Size Limits ............................................... 0
- 4.6. Example ................................................... 0
-5. Mandatory Headers ............................................. 0
- 5.1. Date ...................................................... 0
- 5.1.1. Examples .............................................. 0
- 5.2. From ...................................................... 0
- 5.2.1. Examples: ............................................ 0
- 5.3. Message-ID ................................................ 0
- 5.4. Subject ................................................... 0
- 5.5. Newsgroups ................................................ 0
- 5.5.1. Forbidden newsgroup-names ............................. 0
- 5.6. Path ...................................................... 0
- 5.6.1. Format ................................................ 0
- 5.6.2. Adding a path-identity to the Path-header ............. 0
- 5.6.3. The tail-entry ........................................ 0
- 5.6.4. Path-Delimiter Summary ................................ 0
- 5.6.5. Example ............................................... 0
- 5.7. Injection-Date ............................................ 0
-6. Optional Headers .............................................. 0
- 6.1. Reply-To .................................................. 0
- 6.1.1. Examples .............................................. 0
- 6.2. Sender .................................................... 0
- 6.3. Organization .............................................. 0
- 6.4. Keywords .................................................. 0
- 6.5. Summary ................................................... 0
- 6.6. Distribution .............................................. 0
- 6.7. Followup-To ............................................... 0
- 6.8. Mail-Copies-To ............................................ 0
- 6.9. Posted-And-Mailed ......................................... 0
- 6.10. References ............................................... 0
- 6.10.1. Examples ............................................. 0
- 6.11. Expires .................................................. 0
- 6.12. Archive .................................................. 0
- 6.13. Control .................................................. 0
- 6.14. Approved ................................................. 0
- 6.15. Supersedes ............................................... 0
- 6.16. Xref ..................................................... 0
- 6.17. Lines .................................................... 0
- 6.18. User-Agent ............................................... 0
- 6.18.1. Examples ............................................. 0
- 6.19. Injection-Info ........................................... 0
- 6.19.1. Usage of Injection-Info-parameters ................... 0
- 6.19.1.1. The posting-host-parameter ....................... 0
- 6.19.1.2. The posting-account-parameter .................... 0
- 6.19.1.3. The posting-sender-parameter ..................... 0
- 6.19.1.4. The posting-logging-parameter .................... 0
- 6.19.2. Example .............................................. 0
- 6.20. Complaints-To ............................................ 0
- 6.21. MIME headers ............................................. 0
- 6.21.1. Syntax ............................................... 0
- 6.21.2. Content-Type ......................................... 0
- 6.21.3. Content-Transfer-Encoding ............................ 0
- 6.21.4. Definition of some new Content-Types ................. 0
- 6.21.4.1. Application/news-transmission .................... 0
- 6.21.4.2. Message/news obsoleted ........................... 0
- 6.22. Obsolete Headers ......................................... 0
-7. Control Messages .............................................. 0
- 7.1. Digital Signature of Headers .............................. 0
- 7.2. Group Control Messages .................................... 0
- 7.2.1. The 'newgroup' Control Message ........................ 0
- 7.2.1.1. The Body of the 'newgroup' Control Message ........ 0
- 7.2.1.2. Application/news-groupinfo ........................ 0
- 7.2.1.3. Initial Articles .................................. 0
- 7.2.1.4. Example ........................................... 0
- 7.2.2. The 'rmgroup' Control Message ......................... 0
- 7.2.2.1. Example ........................................... 0
- 7.2.3. The 'mvgroup' Control Message ......................... 0
- 7.2.3.1. Example ........................................... 0
- 7.2.4. The 'checkgroups' Control Message ..................... 0
- 7.2.4.1. Application/news-checkgroups ...................... 0
- 7.3. Cancel .................................................... 0
- 7.4. Ihave, sendme ............................................. 0
- 7.5. Obsolete control messages. ............................... 0
-8. Duties of Various Agents ...................................... 0
- 8.1. General principles to be followed ......................... 0
- 8.2. Duties of an Injecting Agent .............................. 0
- 8.2.1. Proto-articles ........................................ 0
- 8.2.2. Procedure to be followed by Injecting Agents .......... 0
- 8.3. Duties of a Relaying Agent ................................ 0
- 8.4. Duties of a Serving Agent ................................. 0
- 8.5. Duties of a Posting Agent ................................. 0
- 8.6. Duties of a Followup Agent ................................ 0
- 8.7. Duties of a Moderator ..................................... 0
- 8.8. Duties of a Gateway ....................................... 0
- 8.8.1. Duties of an Outgoing Gateway ......................... 0
- 8.8.2. Duties of an Incoming Gateway ......................... 0
- 8.8.3. Example ............................................... 0
-9. Security and Related Considerations ........................... 0
- 9.1. Leakage ................................................... 0
- 9.2. Attacks ................................................... 0
- 9.2.1. Denial of Service ..................................... 0
- 9.2.2. Compromise of System Integrity ........................ 0
- 9.3. Liability ................................................. 0
-10. IANA Considerations .......................................... 0
- 10.1. Media Types .............................................. 0
- 10.2. Header Field Registry .................................... 0
-11. References ................................................... 0
-12. Acknowledgements ............................................. 0
-13. Contact Address .............................................. 0
+4. Transport ..................................................... 0
+5. Definition of new Media Types ................................. 0
+ 5.1. Application/news-transmission ............................. 0
+ 5.2. Message/news obsoleted .................................... 0
+ 5.3. Application/news-groupinfo ................................ 0
+ 5.4. Application/news-checkgroups .............................. 0
+6. Control Messages .............................................. 0
+ 6.1. Digital Signature of Headers .............................. 0
+ 6.2. Group Control Messages .................................... 0
+ 6.2.1. The 'newgroup' Control Message ........................ 0
+ 6.2.1.1. The Body of the 'newgroup' Control Message ........ 0
+ 6.2.1.2. Initial Articles .................................. 0
+ 6.2.1.3. Example ........................................... 0
+ 6.2.2. The 'rmgroup' Control Message ......................... 0
+ 6.2.2.1. Example ........................................... 0
+ 6.2.3. The 'mvgroup' Control Message ......................... 0
+ 6.2.3.1. Example ........................................... 0
+ 6.2.4. The 'checkgroups' Control Message ..................... 0
+ 6.3. Cancel .................................................... 0
+ 6.4. Ihave, sendme ............................................. 0
+ 6.5. Obsolete control messages. ............................... 0
+7. Duties of Various Agents ...................................... 0
+ 7.1. General principles to be followed ......................... 0
+ 7.2. Duties of an Injecting Agent .............................. 0
+ 7.2.1. Proto-articles ........................................ 0
+ 7.2.2. Procedure to be followed by Injecting Agents .......... 0
+ 7.3. Procedure for Forwarding to a Moderator ................... 0
+ 7.4. Duties of a Relaying Agent ................................ 0
+ 7.4.1. Example ............................................... 0
+ 7.5. Duties of a Serving Agent ................................. 0
+ 7.6. Duties of a Posting Agent ................................. 0
+ 7.7. Duties of a Followup Agent ................................ 0
+ 7.8. Duties of a Moderator ..................................... 0
+ 7.9. Duties of a Gateway ....................................... 0
+ 7.9.1. Duties of an Outgoing Gateway ......................... 0
+ 7.9.2. Duties of an Incoming Gateway ......................... 0
+ 7.9.3. Example ............................................... 0
+8. Security and Related Considerations ........................... 0
+ 8.1. Leakage ................................................... 0
+ 8.2. Attacks ................................................... 0
+ 8.2.1. Denial of Service ..................................... 0
+ 8.2.2. Compromise of System Integrity ........................ 0
+ 8.3. Liability ................................................. 0
+9. IANA Considerations ........................................... 0
+10. References ................................................... 0
+11. Acknowledgements ............................................. 0
+12. Contact Address .............................................. 0
Appendix A.1 - A-News Article Format .............................. 0
Appendix A.2 - Early B-News Article Format ........................ 0
-Appendix A.3 - Obsolete Headers ................................... 0
-Appendix A.4 - Obsolete Control Messages .......................... 0
-Appendix B - Collected Syntax ..................................... 0
-Appendix B.1 - Characters, Atoms and Folding ...................... 0
-Appendix B.2 - Basic Forms ........................................ 0
-Appendix B.3 - Headers ............................................ 0
-Appendix B.3.1 - Header outlines .................................. 0
-Appendix B.3.2 - Control-message outlines ......................... 0
-Appendix B.3.3 - Other header rules ............................... 0
-Appendix C - Notices .............................................. 0
+Appendix A.3 - Obsolete Control Messages .......................... 0
+Appendix B - Notices .............................................. 0
+Appendix C - Change Log ........................................... 0
+
+
+[This draft [USEPRO] and its partner [USEFOR] are an interim stage in
+the splitting into two parts of the earlier draft [ARTICLE]. There is a
+certain amount of material - basic concepts, definitions, etc - which
+ultimately need occur in only one of the documents, and further such
+material which may not be needed at all (e.g. terms currently defined
+which in the event may not get used). For the moment, all such material
+has been retained in the present draft (it being, in any case, easier to
+take unwanted stuff out than to put new stuff in). It has also to be
+decided, for such material which is needed by both documents, which one
+(the "Primary") should contain it and which one should incorporate it by
+reference (essentially, this draft is written so that it could be the
+Primary).]
+
+[Again, references in this document to sections which ultimately are
+expected to be in [USEFOR] are still to the old sections in [ARTICLE],
+since [USEFOR] is not stabilized enough to refer to specific sections in
+it yet. These references can be recognized by being prefixed with "a-".
+These references can be fixed up later as we find the proper places for
+them to point to. In any case, there will doubtless be more toing and
+froing of texts between the two documents before we are done.]