W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

obs-date, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 28 Oct 2013 15:00:20 +0100
Message-ID: <526E6DF4.4030509@gmx.de>
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
CC: iesg@ietf.org, ietf-http-wg@w3.org, ietf@ietf.org
On 2013-10-28 09:07, S Moonesamy wrote:
> ...
> In Section 7.1.1:
>
>    "The preferred format is a fixed-length and single-zone subset of
>     the date and time specification used by the Internet Message Format
>     [RFC5322]"
>
> The ABNF imports obs-date from RFC 5322.  "GMT" is defined in "obs-zone"
> (see RFC 5322).  There is the following in the section:
>
>    "For example, messages are occasionally forwarded over HTTP from a
>     non-HTTP source that might generate any of the date and time
>     specifications defined by the Internet Message Format."
>
> I listed this as a minor issue.  I am not suggesting any change as "GMT"
> is used in other header fields.  I'll defer to the HTTPbis Working Group
> as to whether there should be a note about "GMT" with an explanation
> that although "GMT" is deprecated the use is widespread.
> ...

Actually, HTTPbis has its own obs-date:

	obs-date     = rfc850-date / asctime-date

<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-24.html#rfc.section.7.1.1.1>

So there doesn't seem to be an issue here.

Best regards, Julian
Received on Monday, 28 October 2013 14:00:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:18 UTC