usefor-usefor-03 April 2005

[< Prev] [TOC] [ Next >]
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-core> construct defined in Section 3.1.3 MUST
      be used.

   o  Message identifiers MUST be separated with CFWS.

   o  Comments in CFWS between message identifiers can cause
      interoperability problems, so comments SHOULD NOT be generated,
      but MUST be accepted.


   references      =  "References:" SP 1*( [CFWS] msg-id-core) [CFWS]
            CRLF
[< Prev] [TOC] [ Next >]
#Diff to first older
NewerOlder
usefor-usefor May 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
Son of 1036 June 1994
RFC 1036 December 1987

--- ../usefor-usefor-02/References.out          November 2004
+++ ../usefor-usefor-03/References.out          April 2005
@@ -5,10 +5,13 @@
    those listed below:
    o  The updated <msg-id-core> construct defined in Section 3.1.3 MUST
       be used.
+
    o  Message identifiers MUST be separated with CFWS.
+
    o  Comments in CFWS between message identifiers can cause
       interoperability problems, so comments SHOULD NOT be generated,
       but MUST be accepted.
+
 
    references      =  "References:" SP 1*( [CFWS] msg-id-core) [CFWS]
             CRLF


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