usefor-usefor-01 September 2004

2.2  Header Fields

   All headers fields in a news article are compliant with [RFC2822],
   however this specification is more restrictive in what can be
   generated and accepted by news agents.  The syntax allowed for news
   articles is a strict subset of the "Internet Message Format", making
   all messages compliant with this specification inherently compliant
   with [RFC2822].  Note however that the converse is not guaranteed to
   be true.

   General rules which apply to all headers (even those documented in
   [RFC2822] and [RFC2045]) are listed below and those that apply to
   specific headers are described in the relevent sections of this
   document.

   User agents MUST generate headers so that at least one space
   immediately follows the ':' separating the header name and the header
   contents.  As a result, an <unstructured> header as defined in
   Section 3.2.6 of [RFC2822] MUST NOT be empty (it will always contain
   at least a single space).  News agents MAY accept headers which do
   not contain the required space.

   Compliant software MUST support headers of at least 998 octets.  This
   is the only limit on the length of a header line prescribed by this
   standard.  However, specific rules to the contrary may apply in
   particular cases (for example, according to [RFC2047] header lines
   containing encoded-words are limited to 76 octets).

      NOTE: There is NO restriction on the number of lines into which a
      header may be split, and hence there is NO restriction on the
      total length of a header (in particular it may, by suitable
      folding, be made to exceed the 998 octets restriction pertaining
      to a single header line).

   The character set for headers is US-ASCII.  Where the use of
   non-ASCII characters is required, they MUST be encoded using the MIME
   mechanisms defined in [RFC2045] and [RFC2231].

--- ../rfc2822/Header_Fields.out          April 2001
+++ ../usefor-usefor-01/Header_Fields.out          September 2004
@@ -1,12 +1,38 @@
-2.2. Header Fields
+2.2  Header Fields
 
-   Header fields are lines composed of a field name, followed by a colon
-   (":"), followed by a field body, and terminated by CRLF.  A field
-   name MUST be composed of printable US-ASCII characters (i.e.,
-   characters that have values between 33 and 126, inclusive), except
-   colon.  A field body may be composed of any US-ASCII characters,
-   except for CR and LF.  However, a field body may contain CRLF when
-   used in header "folding" and  "unfolding" as described in section
-   2.2.3.  All field bodies MUST conform to the syntax described in
-   sections 3 and 4 of this standard.
+   All headers fields in a news article are compliant with [RFC2822],
+   however this specification is more restrictive in what can be
+   generated and accepted by news agents.  The syntax allowed for news
+   articles is a strict subset of the "Internet Message Format", making
+   all messages compliant with this specification inherently compliant
+   with [RFC2822].  Note however that the converse is not guaranteed to
+   be true.
+
+   General rules which apply to all headers (even those documented in
+   [RFC2822] and [RFC2045]) are listed below and those that apply to
+   specific headers are described in the relevent sections of this
+   document.
+
+   User agents MUST generate headers so that at least one space
+   immediately follows the ':' separating the header name and the header
+   contents.  As a result, an <unstructured> header as defined in
+   Section 3.2.6 of [RFC2822] MUST NOT be empty (it will always contain
+   at least a single space).  News agents MAY accept headers which do
+   not contain the required space.
+
+   Compliant software MUST support headers of at least 998 octets.  This
+   is the only limit on the length of a header line prescribed by this
+   standard.  However, specific rules to the contrary may apply in
+   particular cases (for example, according to [RFC2047] header lines
+   containing encoded-words are limited to 76 octets).
+
+      NOTE: There is NO restriction on the number of lines into which a
+      header may be split, and hence there is NO restriction on the
+      total length of a header (in particular it may, by suitable
+      folding, be made to exceed the 998 octets restriction pertaining
+      to a single header line).
+
+   The character set for headers is US-ASCII.  Where the use of
+   non-ASCII characters is required, they MUST be encoded using the MIME
+   mechanisms defined in [RFC2045] and [RFC2231].