IETF Logo Mail Archive

Re: A structured format for dates?

Poul-Henning Kamp <phk@phk.freebsd.dk> Thu, 25 August 2022 11:00 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 4FDD1C152561 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 25 Aug 2022 04:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.662
X-Spam-Level:
X-Spam-Status: No, score=-7.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 4g2lG13R_Sxk for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 25 Aug 2022 04:00:25 -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 380B6C1524DD for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 25 Aug 2022 04:00:24 -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 1oRAY8-00EQoz-DH for ietf-http-wg-dist@listhub.w3.org; Thu, 25 Aug 2022 10:57:24 +0000
Resent-Date: Thu, 25 Aug 2022 10:57:24 +0000
Resent-Message-Id: <E1oRAY8-00EQoz-DH@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <phk@critter.freebsd.dk>) id 1oRAY7-00EQo2-8E for ietf-http-wg@listhub.w3.org; Thu, 25 Aug 2022 10:57:23 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by mimas.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <phk@critter.freebsd.dk>) id 1oRAY5-002obu-Gm for ietf-http-wg@w3.org; Thu, 25 Aug 2022 10:57:22 +0000
Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 66E30892AA; Thu, 25 Aug 2022 10:57:07 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.16.1/8.16.1) with ESMTPS id 27PAumtQ002435 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 25 Aug 2022 10:56:48 GMT (envelope-from phk@critter.freebsd.dk)
Received: (from phk@localhost) by critter.freebsd.dk (8.16.1/8.16.1/Submit) id 27PAukhx002434; Thu, 25 Aug 2022 10:56:46 GMT (envelope-from phk)
Message-Id: <202208251056.27PAukhx002434@critter.freebsd.dk>
To: iain hill <iainardernhill@gmail.com>
cc: ietf-http-wg@w3.org
In-reply-to: <535ee9c7-cb3a-0dad-f544-de97323f74db@gmail.com>
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <202208231056.27NAuWFY015133@critter.freebsd.dk> <7B9BFDFF-337E-4CB8-8550-3D38EFD52160@apple.com> <685890F9-9F68-41EF-AC8C-86ACAD074A38@mnot.net> <3CBE12DF-8229-43E0-A9D9-EAB306B9EFF8@mit.edu> <535ee9c7-cb3a-0dad-f544-de97323f74db@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2432.1661425006.1@critter.freebsd.dk>
Date: Thu, 25 Aug 2022 10:56:46 +0000
Received-SPF: pass client-ip=130.225.244.222; envelope-from=phk@critter.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-4.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1oRAY5-002obu-Gm ba4813635073ef26899f03741f058c8e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: A structured format for dates?
Archived-At: <https://www.w3.org/mid/202208251056.27PAukhx002434@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40354
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>

--------
iain hill writes:

> Is using a floating point number based upon a chosen format of Julian 
> Date (perhaps beginning at the start of UNIX time) really not worthy of 
> more consideration here?

Time-nut-PHK would vote for such a proposal, but programmer-PHK would
be firmly set against it.

When it comes to computers and timekeeping, "doing it right" has not
been an option for decades.

Given my painfully extensive experience with my own and other peoples
time-bugs, I am now firmly in the "Call time(2), use that number,
as a number, but dont modify it!" camp.

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

v2.23.0 | Report a Bug | By Email