W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2022

Re: A structured format for dates?

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Fri, 17 Jun 2022 06:53:59 +0000
Message-Id: <202206170653.25H6rxjP064848@critter.freebsd.dk>
To: Mark Nottingham <mnot@mnot.net>
cc: HTTP Working Group <ietf-http-wg@w3.org>
--------
Mark Nottingham writes:
> 
>
> > On 17 Jun 2022, at 4:20 pm, Poul-Henning Kamp <phk@phk.freebsd.dk> =
> wrote:
> >=20
> > Introducing ISO 8601 as yet another textual timestamp format,
> > offering no upside over the three already codified textual timestamp
> > formats, would be not only pointless, it would be a regression, for
> > instance in terms of HPACK efficiency.
>
> When it's textual, yes. If Binary Structured Fields happens, that's not
> an issue.

It will still be in log files, but that is of course "Somebody Elses Problem" :-)

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Friday, 17 June 2022 06:54:10 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:44:07 UTC