usefor-usefor-01 September 2004

3.1.3  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.

--- ../usefor-article-13/Date.out          May 2004
+++ ../usefor-usefor-01/Date.out          September 2004
@@ -1,23 +1,13 @@
-5.1.  Date
+3.1.3  Date
 
-   The Date-header contains the date and time that the article was
-   prepared by the poster ready for transmission and SHOULD express the
-   poster's local time. The content syntax makes use of syntax defined
-   in [RFC 2822] (but see the revised definition of zone in section
-   2.4.3).
-
-      header              =/ Date-header
-      Date-header         = "Date" ":" SP Date-content
-      Date-content        = date-time
-
-   The date-time MUST be semantically valid as required by [RFC 2822].
-   Although folding white space is permitted throughout the date-time
-   syntax, it is RECOMMENDED that a single space be used in each place
-   that FWS appears (whether it is required or optional).
-
-   The date-time MUST NOT be more than 24 hours into the future
-   (injecting agents will reject such articles, possibly even when the
-   margin is less than 24 hours - see 8.2.2 - and MAY also reject them
-   if it is inordinately far into the past).  Relaying agents MUST NOT
-   modify the Date-header in transit.
+   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.