usefor-article-03 February 2000

6.17.1.  Syntax

   The following headers, as defined within [RFC 2045] and its
   extensions, may be used within articles conforming to this standard.

        MIME-Version:
        Content-Type:
        Content-Transfer-Encoding:
        Content-ID:
        Content-Description:
        Content-Disposition:
        Content-MD5:

   Insofar as the syntax for these headers, as given in [RFC 2045], does
   not specify precisely where whitespace and comments may occur
   (whether in the form of WSP, FWS or CFWS), the usage defined in this
   standard, and failing that in [MESSFOR], and failing that in [RFC
   822] MUST be followed. In particular, there MUST NOT be any WSP
   between a header-name and the following colon and there MUST be a SP
   following that colon.

   The meaning of the various MIME headers is as defined in [RFC 2045]
   and [RFC 2046], and in extensions registered in accordance with [RFC
   2048].  However, their usage is curtailed as described in the
   following sections.

--- ../rfc2822/Syntax.out          April 2001
+++ ../usefor-article-03/Syntax.out          February 2000
@@ -1,2 +1,26 @@
-3. Syntax
+6.17.1.  Syntax
+
+   The following headers, as defined within [RFC 2045] and its
+   extensions, may be used within articles conforming to this standard.
+
+        MIME-Version:
+        Content-Type:
+        Content-Transfer-Encoding:
+        Content-ID:
+        Content-Description:
+        Content-Disposition:
+        Content-MD5:
+
+   Insofar as the syntax for these headers, as given in [RFC 2045], does
+   not specify precisely where whitespace and comments may occur
+   (whether in the form of WSP, FWS or CFWS), the usage defined in this
+   standard, and failing that in [MESSFOR], and failing that in [RFC
+   822] MUST be followed. In particular, there MUST NOT be any WSP
+   between a header-name and the following colon and there MUST be a SP
+   following that colon.
+
+   The meaning of the various MIME headers is as defined in [RFC 2045]
+   and [RFC 2046], and in extensions registered in accordance with [RFC
+   2048].  However, their usage is curtailed as described in the
+   following sections.