Re: A structured format for dates?

Ryan Hamilton <rch@google.com> Wed, 24 August 2022 13:55 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 38F49C1522D6 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 24 Aug 2022 06:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.562
X-Spam-Level:
X-Spam-Status: No, score=-12.562 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 lqQ7cWtJnBr6 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 24 Aug 2022 06:55:08 -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 21EF8C14CF06 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 24 Aug 2022 06:55:07 -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 1oQqny-00Be3U-QU for ietf-http-wg-dist@listhub.w3.org; Wed, 24 Aug 2022 13:52:26 +0000
Resent-Date: Wed, 24 Aug 2022 13:52:26 +0000
Resent-Message-Id: <E1oQqny-00Be3U-QU@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 <rch@google.com>) id 1oQqnw-00Be2e-UU for ietf-http-wg@listhub.w3.org; Wed, 24 Aug 2022 13:52:24 +0000
Received: from mail-yw1-x112a.google.com ([2607:f8b0:4864:20::112a]) by titan.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <rch@google.com>) id 1oQqnv-0044Jc-KM for ietf-http-wg@w3.org; Wed, 24 Aug 2022 13:52:24 +0000
Received: by mail-yw1-x112a.google.com with SMTP id 00721157ae682-33da3a391d8so48903907b3.2 for <ietf-http-wg@w3.org>; Wed, 24 Aug 2022 06:52:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=U9pVlxhxA8YC5VtFlEoNogNQVz79HLc7itJqhrEX120=; b=Qi/ACrsIcfxDsI+BaDupvi3pcIr8Wx8LDVeD4H0irh8SDXLybH/3OrEcq9/crhM0ar YvMTCsqekZ7v6fPDkbAwEoDU7tyYGhtdZhtOlqQ9CQHoUACZR4QSdxno+IXof9bE2uO4 6Cs4BIAyzfa09dO4elkfaAbHaYPwcTULZuG3pDHSyLPDZIM4THpg27QhtiZE7PE3wc5b 9OR0hp/Zoii9Jw+UjPGz+nH1Y48IQuc5a66o5BgdMlP4YOUuVYviVHqqSIMc1ofv4wvj 7EkLzahgRfwPSww3uCzXq0iFsTRupgrP9XOpFm7m43z+okN2zb8vuOtNqFTiKdfVsxGG e6Ww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=U9pVlxhxA8YC5VtFlEoNogNQVz79HLc7itJqhrEX120=; b=w803K+2+geULpv8a7jOW40InbFK1EqbhWV+KqqqRGXo6DwnWq7vdjnpz+zFtGpwWJl oW5tbg1tyaYALR2qAkmAWknpatnTZFEaYalBoZrop8dTphpNE2wxNAXp7LyjLfUMBy25 Q9wlqkkfWoc0wjSF87AVgSdTt18N9adFUkFMf4AluzOLUbClrUfDFVKDB8Xd5QKs2o54 7Mev01HUmdV2lAdav5ug1LwpRXFU5UrRXBXcWXaeMFq6mNxJOKKQpk2pwqTp/mZdziJz w1cdgK1mRHzFhmEItHBhnu+K8msjr8UCet693TVAnohnhSEr7Mt052x8Cl5k6wmthak/ VyFw==
X-Gm-Message-State: ACgBeo3xK7AVWYvKkMKjsKpzO19lHJSR7MTnCGXFsKWgyISS2dcD8sI/ SpVvm04zdaEDimomh+mwfY4SsHcbNh71E2KgJlMXmQ==
X-Google-Smtp-Source: AA6agR43zPVxInHLpizgXnxIiI0FonRxx3XKEC1U/fdEwwo7Xd4NrjuJu6MJl7WkKTcQIjXTamLJd1oQs9K69RgKInc=
X-Received: by 2002:a0d:c586:0:b0:334:3a54:1cb3 with SMTP id h128-20020a0dc586000000b003343a541cb3mr31740671ywd.420.1661349132787; Wed, 24 Aug 2022 06:52:12 -0700 (PDT)
MIME-Version: 1.0
References: <202208231056.27NAuWFY015133@critter.freebsd.dk> <7B9BFDFF-337E-4CB8-8550-3D38EFD52160@apple.com> <685890F9-9F68-41EF-AC8C-86ACAD074A38@mnot.net> <202208240838.27O8c6eE021749@critter.freebsd.dk>
In-Reply-To: <202208240838.27O8c6eE021749@critter.freebsd.dk>
From: Ryan Hamilton <rch@google.com>
Date: Wed, 24 Aug 2022 06:52:00 -0700
Message-ID: <CAJ_4DfRQJCj-fQnTKhdfqt58BWg=zDb_2cHtjERSF5YjzQpDdw@mail.gmail.com>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Mark Nottingham <mnot@mnot.net>, Tommy Pauly <tpauly@apple.com>, Roberto Polli <robipolli@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="000000000000e8c36c05e6fcfc84"
Received-SPF: pass client-ip=2607:f8b0:4864:20::112a; envelope-from=rch@google.com; helo=mail-yw1-x112a.google.com
X-W3C-Hub-DKIM-Status: validation passed: (address=rch@google.com domain=google.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-19.6
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1oQqnv-0044Jc-KM 7b71166cc495987eb017d2fa30d50c4c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: A structured format for dates?
Archived-At: <https://www.w3.org/mid/CAJ_4DfRQJCj-fQnTKhdfqt58BWg=zDb_2cHtjERSF5YjzQpDdw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40350
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>

I'm sold on the arguments that an integer format is the way to go.

On Wed, Aug 24, 2022 at 1:41 AM Poul-Henning Kamp <phk@phk.freebsd.dk>
wrote:

> --------
> Mark Nottingham writes:
>
> > IMO the only reason we'd choose an integer textual representation is if
> we
> > didn't believe that [binary structured fields are going to happen].
>
> I disagree.
>
> First, we are never going to get 100% penetration for a binary
> serialization,
> and it will take about five years for any significant uptake of it.
>
> Second, the efficiency arguments are invariant of the existence of
> binary serializations, because most of the actual HTTP header
> processing HTTP headers will not operate on the binary serialization
> in the first place.
>
> Third, there are many efficiency arguments for integer textural
> representation,
> even without considering binary serializations:
>
> * takes up less space in files and on the wire
> * compresses better.
> * is faster and uses less instructions/energy to produce and parse
> * is easier and less error-prone to produce and parse
>
> So I really dont see binary structured fields as particularly relevant for
> this
> decision, if anything, they just add one more efficiency argument:
>
> * is faster/uses less instructions/energy and easier to (de)serialize as
> binary.
>
> Poul-Henning
>
> --
> 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.
>
>