usefor-usefor-02 November 2004

3.1.2  Date

   The Date header is the same as that specified in Sections 3.3 and
   3.6.1 of [RFC2822] with the added restrictions detailed in Section
   2.2.  However, the use of "UT" and "GMT" as time zones (part of
   <obs-zone>), although deprecated, is widespread in news articles
   today.  Therefore, agents MUST accept <date-time> constructs which
   include the updated <zone> construct below.

   orig-date       =  "Date:" SP date-time CRLF
   zone            =  (( "+" / "-" ) 4DIGIT) / "UT" / "GMT"

   Note that agents SHOULD NOT generate <date-time> constructs which
   include either "UT" or "GMT" and MUST NOT generate <date-time>
   constructs which include any other zone names defined by <obs-zone>,
   some of which have ambiguous interpretations and would have adverse
   effects on Netnews protocols.

   Also note that these requirements apply wherever <date-time> is used,
   including Injection-Date and Expires in Section 3.1.7 and Section
   3.2.3 respectively.

--- ../usefor-usefor-01/Date.out          September 2004
+++ ../usefor-usefor-02/Date.out          November 2004
@@ -1,13 +1,22 @@
-3.1.3  Date
+3.1.2  Date
 
    The Date header is the same as that specified in Sections 3.3 and
    3.6.1 of [RFC2822] with the added restrictions detailed in Section
-   2.2.  However, the use of "GMT" and "UT" as time zones, which are
-   part of <obs-zone>, is widespread in news articles today.  Therefore,
-   agents MUST accept, but MUST NOT generate, <date-time> constructs
-   which include <obs-zone>.  As stated in Section 2.1, support for
-   <obs-zone> would otherwise have been SHOULD accept, MUST NOT
-   generate.  Note that these requirements apply wherever <date-time> is
-   used, including Injection-Date and Expires in Section 3.1.7 and
-   Section 3.2.3 respectively.
+   2.2.  However, the use of "UT" and "GMT" as time zones (part of
+   <obs-zone>), although deprecated, is widespread in news articles
+   today.  Therefore, agents MUST accept <date-time> constructs which
+   include the updated <zone> construct below.
+
+   orig-date       =  "Date:" SP date-time CRLF
+   zone            =  (( "+" / "-" ) 4DIGIT) / "UT" / "GMT"
+
+   Note that agents SHOULD NOT generate <date-time> constructs which
+   include either "UT" or "GMT" and MUST NOT generate <date-time>
+   constructs which include any other zone names defined by <obs-zone>,
+   some of which have ambiguous interpretations and would have adverse
+   effects on Netnews protocols.
+
+   Also note that these requirements apply wherever <date-time> is used,
+   including Injection-Date and Expires in Section 3.1.7 and Section
+   3.2.3 respectively.