usefor-usefor-01 September 2004

3.2.1  References

   The References header is the same as that specified in Section 3.6.4
   of [RFC2822] with the added restrictions detailed in Section 2.2 and
   those listed below:

   o  The updated <msg-id> construct defined in Section 3.1.4 MUST be
      used.
   o  Message IDs MUST be separated with CFWS.
   o  Comments in CFWS between Message IDs can cause interoperability
      problems, so comments SHOULD NOT be generated, but MUST be
      accepted.

--- ../usefor-article-13/References.out          May 2004
+++ ../usefor-usefor-01/References.out          September 2004
@@ -1,19 +1,13 @@
-6.10.  References
+3.2.1  References
 
-   The References-header is an inheritable header (see 4.2.5.2) which
-   lists CFWS-separated message identifiers of the article's precursors,
-   as described in 8.6.  The content syntax makes use of syntax defined
-   in [RFC 2822] (but see the revised definition of msg-id in section
-   2.4.3).
+   The References header is the same as that specified in Section 3.6.4
+   of [RFC2822] with the added restrictions detailed in Section 2.2 and
+   those listed below:
 
-      header              =/ References-header
-      References-header   = "References" ":" SP References-content
-      References-content  = [CFWS] msg-id *( CFWS msg-id ) [CFWS]
-
-        NOTE: This differs from the syntax of [RFC 2822] by requiring at
-        least one CFWS between the msg-ids (a SP at this point was an
-        [RFC 1036] requirement).
-
-   A followup MUST have a References-header, and an article that is not
-   a followup MUST NOT have a References-header.
+   o  The updated <msg-id> construct defined in Section 3.1.4 MUST be
+      used.
+   o  Message IDs MUST be separated with CFWS.
+   o  Comments in CFWS between Message IDs can cause interoperability
+      problems, so comments SHOULD NOT be generated, but MUST be
+      accepted.