s-o-1036 June 1994

[TOC] [ Next >]
            News Article Format and Transmission

                       Henry Spencer



Status of this Memo

This  document  is  intended  to  become  an Internet Draft.
Internet Drafts are working documents of the Internet  Engi-
neering  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.  Internet Drafts may be  updated,  replaced,  or
obsoleted  by other documents at any time.  It is not appro-
priate to use Internet Drafts as reference  material  or  to
cite  them  other  than  as  a  "working  draft" or "work in
progress".

Please check the I-D  abstract  listing  contained  in  each
Internet Draft directory to learn the current status of this
or any other Internet Draft.  (Actually, this  draft  is  at
too early a stage to even be listed there yet.)

It is hoped that a later version of this Draft will obsolete
RFC 1036 and will become an Internet standard.

References to the "successor to this  Draft"  refer  not  to
later  versions  of this draft, but to a hypothetical future
rewrite of this Draft (in the same way that this Draft is  a
rewrite of RFC 1036).

Distribution of this memo is unlimited.


Abstract

This Draft defines the format and procedures for interchange
of network news articles.  It is hoped that a later  version
of this Draft will obsolete RFC 1036, reflecting more recent
experience and accommodating future directions.

Network news articles resemble mail messages but are  broad-
cast  to potentially-large audiences, using a flooding algo-
rithm that propagates one copy to each interested  host  (or
group thereof), typically stores only one copy per host, and
does not require any central  administration  or  systematic
registration  of  interested users.  Network news originated
as the medium  of  communication  for  Usenet,  circa  1980.

INTERNET DRAFT to be        NEWS                      sec. -


Since  then  Usenet has grown explosively, and many Internet
sites participate in it.  In addition, the  news  technology
is now in widespread use for other purposes, on the Internet
and elsewhere.

This Draft primarily codifies and organizes  existing  prac-
tice.   A few small extensions have been added in an attempt
to solve problems that are considered serious.  Major exten-
sions (e.g. cryptographic authentication) that need signifi-
cant development effort are left to be undertaken  as  inde-
pendent efforts.


Table of Contents

TBW
1. Introduction
2. Definitions, Notations, and Conventions
2.1. Textual Notations
2.2. Syntax Notation
2.3. Definitions
2.4. End Of Line
2.5. Case-Sensitivity
2.6. Language
3. Relation To MAIL (RFC 822 etc.)
4. Basic Format
4.1. Overall Syntax
4.2. Headers
4.2.1. Names and Contents
4.2.2. Undesirable Headers
4.2.3. White Space and Continuations
4.3. Body
4.3.1. Body Format Issues
4.3.2. Body Conventions
4.4. Characters And Character Sets
4.5. Non-ASCII Characters In Headers
76 octets long, not counting the EOL.
4.6. Size Limits
4.7. Example
5. Mandatory Headers
5.1. Date
5.2. From
5.3. Message-ID
5.4. Subject
5.5. Newsgroups
5.6. Path
6. Optional Headers
6.1. Followup-To
6.2. Expires
6.3. Reply-To
6.4. Sender
6.5. References
6.6. Control
6.7. Distribution
6.8. Keywords
6.9. Summary
6.10. Approved
6.11. Lines
6.12. Xref
6.13. Organization
6.14. Supersedes
6.15. Also-Control
6.16. See-Also
6.17. Article-Names
6.18. Article-Updates
7. Control Messages
7.1. cancel
7.2. ihave, sendme
7.3. newgroup
7.4. rmgroup
7.5. sendsys, version, whogets
7.6. checkgroups
8. Transmission Formats
8.1. Batches
8.2. Encoded Batches
8.3. News Within Mail
8.4. Partial Batches
9. Propagation and Processing
9.1. Relayer General Issues
9.2. Article Acceptance And Propagation
9.3. Administrator Contact
10. Gatewaying
10.1. General Gatewaying Issues
10.2. Header Synthesis
10.3. Message ID Mapping
10.4. Mail to and from News
10.5. Gateway Administration
11. Security And Related Issues
11.1. Leakage
11.2. Attacks
11.3. Anarchy
11.4. Liability
[TOC] [ Next >]
#Diff to first older
NewerOlder
usefor-usepro February 2005
usefor-usepro December 2004
usefor-usepro September 2004
usefor-usepro August 2004
usefor-usefor May 2005
usefor-usefor April 2005
usefor-usefor November 2004
usefor-usefor September 2004
News Article Format and Transmission May 2004
News Article Format and Transmission November 2003
News Article Format June 2003
News Article Format April 2003
News Article Format February 2003
News Article Format August 2002
News Article Format May 2002
News Article Format November 2001
News Article Format July 2001
News Article Format April 2001
News Article Format February 2000
RFC 2822 April 2001
RFC 1036 December 1987

--- ../rfc1036/TOC.out          December 1987
+++ ../s-o-1036/TOC.out          June 1994
@@ -1,20 +1,72 @@
-Network Working Group                                          M. Horton
-Request for Comments:  1036                       AT&T Bell Laboratories
-Obsoletes: RFC-850                                              R. Adams
-                                    Center for Seismic Studies
-                                                 December 1987
+            News Article Format and Transmission
 
-
-    Standard for Interchange of USENET Messages
+                       Henry Spencer
 
 
 
 STATUS OF THIS MEMO
 
-    This document defines the standard format for the interchange of
-    network News messages among USENET hosts.  It updates and replaces
-    RFC-850, reflecting version B2.11 of the News program.  This memo is
-    disributed as an RFC to make this information easily accessible to
-    the Internet community.  It does not specify an Internet standard.
+This  document  is  intended  to  become  an Internet Draft.
+Internet Drafts are working documents of the Internet  Engi-
+neering  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.  Internet Drafts may be  updated,  replaced,  or
+obsoleted  by other documents at any time.  It is not appro-
+priate to use Internet Drafts as reference  material  or  to
+cite  them  other  than  as  a  "working  draft" or "work in
+progress".
+
+Please check the I-D  abstract  listing  contained  in  each
+Internet Draft directory to learn the current status of this
+or any other Internet Draft.  (Actually, this  draft  is  at
+too early a stage to even be listed there yet.)
+
+It is hoped that a later version of this Draft will obsolete
+RFC 1036 and will become an Internet standard.
+
+References to the "successor to this  Draft"  refer  not  to
+later  versions  of this draft, but to a hypothetical future
+rewrite of this Draft (in the same way that this Draft is  a
+rewrite of RFC 1036).
+
     Distribution of this memo is unlimited.
+
+
+Abstract
+
+This Draft defines the format and procedures for interchange
+of network news articles.  It is hoped that a later  version
+of this Draft will obsolete RFC 1036, reflecting more recent
+experience and accommodating future directions.
+
+Network news articles resemble mail messages but are  broad-
+cast  to potentially-large audiences, using a flooding algo-
+rithm that propagates one copy to each interested  host  (or
+group thereof), typically stores only one copy per host, and
+does not require any central  administration  or  systematic
+registration  of  interested users.  Network news originated
+as the medium  of  communication  for  Usenet,  circa  1980.
+
+INTERNET DRAFT to be        NEWS                      sec. -
+
+
+Since  then  Usenet has grown explosively, and many Internet
+sites participate in it.  In addition, the  news  technology
+is now in widespread use for other purposes, on the Internet
+and elsewhere.
+
+This Draft primarily codifies and organizes  existing  prac-
+tice.   A few small extensions have been added in an attempt
+to solve problems that are considered serious.  Major exten-
+sions (e.g. cryptographic authentication) that need signifi-
+cant development effort are left to be undertaken  as  inde-
+pendent efforts.
+
+
+Table of Contents
+
+TBW
 

Documents were processed to this format by Forrest J. Cavalier III