Re: A structured format for dates?

Mark Nottingham <mnot@mnot.net> Mon, 22 August 2022 02:32 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4A6C1522BB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 21 Aug 2022 19:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.06
X-Spam-Level:
X-Spam-Status: No, score=-5.06 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=E7PvQ7Fm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=4ZUVyy6M
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oRkGyFFw3Ra for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 21 Aug 2022 19:32:47 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E012C14CE3E for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 21 Aug 2022 19:32:47 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1oPxC8-003D8M-95 for ietf-http-wg-dist@listhub.w3.org; Mon, 22 Aug 2022 02:29:40 +0000
Resent-Date: Mon, 22 Aug 2022 02:29:40 +0000
Resent-Message-Id: <E1oPxC8-003D8M-95@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mnot@mnot.net>) id 1oPxC7-003D7G-1B for ietf-http-wg@listhub.w3.org; Mon, 22 Aug 2022 02:29:39 +0000
Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by titan.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mnot@mnot.net>) id 1oPxC4-002nEP-Qr for ietf-http-wg@w3.org; Mon, 22 Aug 2022 02:29:38 +0000
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 1905B5C0158; Sun, 21 Aug 2022 22:29:24 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sun, 21 Aug 2022 22:29:24 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1661135364; x= 1661221764; bh=DM9ZRuJJ4cbYTzdeS+3lK8bekXZjH+ptFTx9UesaX3o=; b=E 7PvQ7FmL3J8BKRfZ9JEe7E3cNEDteatuunQwgOEHV4oeJC2QhOFWw3TuKgBNCcBG dWg77mhMJ7o258PWfZZitJpA74VZia7uilB+/GmjHDYkJ3vDRULjSPXdfulG30Pv 1/xBxqd+SCEvodAmd7bsFNQYTbvcoDEDYfJ/VZs2GXfl6WmlXcEHT2gr78hAlAEN 6SWnvtlCPpa2q+Ba/soUOutx6IrnteFLsLJng6WG4gTSVgiHbi7fOOZAPdQ3IhyK wcMrM0tQO96Vd6te8kPlYDlAAaktlPJaZMeCn0O5wH1ZBMx2yahz5ctUcQahNq/c llSD8P3iO/XlUDUkGBLsw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1661135364; x= 1661221764; bh=DM9ZRuJJ4cbYTzdeS+3lK8bekXZjH+ptFTx9UesaX3o=; b=4 ZUVyy6MdwP8+fhCErV/3Z0ztNUXk9RajJrZZzQuTZi2rmFdbpbtESF63q4fe8xWw fIv3i3g4CzmWZ9doELtIMUmr619g6Te0u1OJg/DdC0fxEg/krOjqQrp/cGIWEcCd Xbn7BFfWE1xhX5/PgTRZi90iEs7F07IGWhVRuSAXnPRhJAf8pD+X/8GdeXVNW6bU u4V+RWFQyNgdl9BPwFS4nAnYaWsfybhdd9z2EVU/IrqB5FmXvwmohdnyTiwxDYo4 VwU3pSHOQLmia4JHVJFY+olMLONVQRRuo9+mLPbCfOwIjcRIrGYNSiintjtZM/ST 00pq7IcbfPe9tsvwhg8lA==
X-ME-Sender: <xms:A-oCY2SxQQsoBc69M_r38V3aeLAfDqrLbBfTPL_qlUiD5HBfZCu9Xg> <xme:A-oCY7x7fliNwJlMV33gmqGJtqE77ndr2_XhmofmrNL02_65W7lcs_Xhs7R_kr8j3 vOmH0Ck2eRTsCMBKg>
X-ME-Received: <xmr:A-oCYz3vtWGsRtN6I2yxq0atfOiNFs5xdcZ90DCFCstpxoqSxarI0jngO56P04P-CU8n5PWMUVAPG_LS6QtenVZeKA0yehctMri3TH6o_C5EHztr9Vnd7eT6>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdeiiedgieduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffvefgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrth htvghrnhepffekieelgeejleduffetfeelteeufeevgfektddvgfetudejvdfftdejgfff teeinecuffhomhgrihhnpehgihhthhhusgdrtghomhdphhhtthhpfihgrdhorhhgpdhmnh hothdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:BOoCYyAXh8ZBRg2UXJEv6K82k5EIgotO95R4B7xTk5A-XpkgT5wreg> <xmx:BOoCY_hcDzTaZ14T1si5W4_7YXrb4RPyNwhPWwHTY7lYNvtXbC-_ng> <xmx:BOoCY-oBmD20JHUgwz0IWbiCxXh8hn_atMJ-AfAfadIcnuCp0kEEFw> <xmx:BOoCY_LWKDcR14V2Kq2Umfq5eQ_YVVOWSC0OdFiTa5h_gZGCkOdfZw>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 21 Aug 2022 22:29:22 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <A94FB409-7D37-4B5E-894C-33E8CC4986D4@mnot.net>
Date: Mon, 22 Aug 2022 12:29:20 +1000
Cc: Roberto Polli <robipolli@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <502151A9-050A-4A46-AA1E-FC54751EBDC1@mnot.net>
References: <8C9C4A5C-45DB-43C0-9769-2A7510854AB1@mnot.net> <5CE5343D-EECB-4F25-A3DB-F300E7708656@mnot.net> <A94FB409-7D37-4B5E-894C-33E8CC4986D4@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Received-SPF: pass client-ip=66.111.4.29; envelope-from=mnot@mnot.net; helo=out5-smtp.messagingengine.com
X-W3C-Hub-DKIM-Status: validation passed: (address=mnot@mnot.net domain=mnot.net), signature is good
X-W3C-Hub-DKIM-Status: validation passed: (address=mnot@mnot.net domain=messagingengine.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-9.8
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1oPxC4-002nEP-Qr 555c50b5c2935403538ae1d055d55a91
X-Original-To: ietf-http-wg@w3.org
Subject: Re: A structured format for dates?
Archived-At: <https://www.w3.org/mid/502151A9-050A-4A46-AA1E-FC54751EBDC1@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40336
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

<editor hat>

So far, I've seen pretty strong support for the updated format (e.g., `Date: @1659073897`). The only pushback I've seen is from Roberto (CC:ed), here:
  https://github.com/httpwg/http-extensions/issues/2162#issuecomment-1209439005

Roberto, as discussed before the merit of approach (3) over just an integer is that it is possible for software that isn't aware of a specific header's semantics to recognise the type of the date in the textual format. For example, logging, tracing, analysis tools and the like. While personally I think I'd slightly prefer a profile of ISO dates (approach 2), my perception is that there's much stronger support for (3).

Any further discussion about this? If not, I'll go ahead and incorporate the PR so we can see if it sticks.

Cheers,


> On 4 Aug 2022, at 12:25 pm, Mark Nottingham <mnot@mnot.net> wrote:
> 
> Based on discussion at 114, I've updated the PR. See:
>  https://httpwg.org/http-extensions/mnot/2162/draft-ietf-httpbis-retrofit.html#name-the-date-structured-type
> 
> Thoughts? 
> 
> Also, I see that Martin is wondering whether this should be a separate document. Any opinions there? It's very short...
> 
> Cheers,
> 
> 
> 
>> On 21 Jun 2022, at 4:44 pm, Mark Nottingham <mnot@mnot.net> wrote:
>> 
>> Just a heads-up:
>> 
>> I've linked a PR from the issue, to give people an idea of one way this might look.
>> 
>> Cheers,
>> 
>> 
>>> On 16 Jun 2022, at 11:54 am, Mark Nottingham <mnot@mnot.net> wrote:
>>> 
>>> I'd love to hear what people think about this issue:
>>> https://github.com/httpwg/http-extensions/issues/2162
>>> 
>>> In a nutshell, the idea is to define a new structured type for dates, so that instead of e.g.,
>>> 
>>> SF-Date: 784072177
>>> 
>>> we'd have:
>>> 
>>> SF-Date: @1994-11-06T08:49:37Z 
>>> 
>>> ...as the textual representation. Obviously, if we ever do binary structured fields, its representation there could be more efficient.
>>> 
>>> Thoughts?
>> 
>> --
>> Mark Nottingham   https://www.mnot.net/
>> 
>> 
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 
> 

--
Mark Nottingham   https://www.mnot.net/