#1028 USEFOR 3.1.2 Date: Resolved, I think.

[Harald Tveit Alvestrand <harald@xxxxxxxxxxxxx>]

Based on comments to Ken Murchison's text, I currently have the following 
as resolution:

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" as a time zone (part of <obs-
zone>), although deprecated, is widespread in news articles today.
Therefore, agents MUST accept <date-time> constructs which use the
"GMT" zone.

NOTE: this specification does not change [RFC2822], which says
 that agents MUST NOT generate <date-time> constructs which
 include any zone names defined by <obs-zone>.

 Software that accepts dates with unknown timezones SHOULD treat such
 timezones as equivalent to "-0000" when comparing dates, as specified
 in [RFC2822] section 4.3.

The main change is deleting the ABNF (unneccesary) and doing the import of 
unknown timezones in a NOTE rather than in normative text.

(Since we're quoting requirements from 2822, I think it makes sense to put 
the uppercase MUST and SHOULD in a NOTE - usually, it doesn't).

Makes sense?

                    Harald