usefor-article-03 February 2000

[< Prev] [TOC] [ Next >]
6.  Optional Headers

   The headers appearing in this section have established meanings and
   MUST be interpreted according to the definitions given here. None of
   them is required to appear in every article but some of them are
   required in certain types of article, such as followups. Any header
   defined in this (or any other) standard MUST NOT appear more than
   once in an article unless specifically stated otherwise.
   Experimental headers (4.2.2.1) and headers defined by cooperating
   subnets are exempt from this requirement.  See section 8 "Duties of
   Various Agents" for the full picture.
[< Prev] [TOC] [ Next >]
#Diff to first older
NewerOlder
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
Son of 1036 June 1994
RFC 1036 December 1987

--- ../s-o-1036/Optional_Headers.out          June 1994
+++ ../usefor-article-03/Optional_Headers.out          February 2000
@@ -1,29 +1,12 @@
 6. Optional Headers
 
-Many  MAIL  headers,  and many of those specified in present
-and future MAIL extensions, are  potentially  applicable  to
-news.   Headers  specific to MAIL's point-to-point transmis-
-sion paradigm, e.g. To and Cc, SHOULD  not  appear  in  news
-articles.   (Gateways  wishing  to preserve such information
-
-INTERNET DRAFT to be        NEWS                      sec. 6
-
-
-for debugging probably SHOULD hide it under different names;
-prefixing  "X-"  to  the original headers, resulting in e.g.
-"X-To", is suggested.)
-
-The following optional headers are either specific  to  news
-or  of particular note in news articles; an article MAY con-
-tain some or all of them.  (Note that there are some circum-
-stances  in  which  some  of  them  are mandatory; these are
-explained under the individual headers.)   An  article  MUST
-not contain two or more headers with any one of these header
-names.
-
-     NOTE: The ban on duplicate header names  does  not
-     apply  to  headers  not specified in this Draft at
-     all, such as "X-" headers.   Software  should  not
-     assume  that  all  header names in a given article
-     are unique.
+   The headers appearing in this section have established meanings and
+   MUST be interpreted according to the definitions given here. None of
+   them is required to appear in every article but some of them are
+   required in certain types of article, such as followups. Any header
+   defined in this (or any other) standard MUST NOT appear more than
+   once in an article unless specifically stated otherwise.
+   Experimental headers (4.2.2.1) and headers defined by cooperating
+   subnets are exempt from this requirement.  See section 8 "Duties of
+   Various Agents" for the full picture.
 

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