usefor-article-11 June 2003

[< Prev] [TOC] [ Next >]
5.1.  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.2).

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

   In order to prevent the reinjection of expired articles into the news
   stream, relaying and serving agents MUST refuse "stale" articles
   whose Date-header predates the earliest articles of which they
   normally keep record, or which is more than 24 hours into the future
   (though they MAY use a margin less than that 24 hours). Relaying
   agents MUST NOT modify the Date-header in transit.
[< Prev] [TOC] [ Next >]
#Diff to first older
NewerOlder
usefor-usefor May 2005
usefor-usefor April 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 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-article-10/Date.out          April 2003
+++ ../usefor-article-11/Date.out          June 2003
@@ -3,27 +3,17 @@
    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], subject to the following revised definition of zone.
+   in [RFC 2822] (but see the revised definition of zone in section
+   2.4.2).
 
       header              =/ Date-header
       Date-header         = "Date" ":" SP Date-content
       Date-content        = date-time
-      zone                = (( "+" / "-" ) 4DIGIT) / "UT" / "GMT"
 
-   The forms "UT" and "GMT" (indicating universal time) are to be
-   regarded as obsolete synonyms for "+0000". They MUST be accepted, and
-   passed on unchanged, by all agents, but they MUST NOT be generated as
-   part of new articles by posting and injecting agents.  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).
-
-        NOTE: A convention that is sometimes followed is to add a
-        comment, after the date-time, containing the time zone in
-        human-readable form, but many of the abbreviations commonly used
-        for this purpose are ambiguous. The value given by the <zone> is
-        the only definitive form.
+   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).
 
    In order to prevent the reinjection of expired articles into the news
    stream, relaying and serving agents MUST refuse "stale" articles


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