IETF Logo Mail Archive

Re: HTTP/2 Header Encoding Status Update

"Poul-Henning Kamp" <phk@phk.freebsd.dk> Mon, 04 March 2013 15:09 UTC

Return-Path: <ietf-http-wg-request@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 66FD521F88B6 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 4 Mar 2013 07:09:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSvPvUg+kBnb for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 4 Mar 2013 07:09:47 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 640DF21F8972 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 4 Mar 2013 07:09:47 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UCX0U-0007cR-HM for ietf-http-wg-dist@listhub.w3.org; Mon, 04 Mar 2013 15:08:50 +0000
Resent-Date: Mon, 04 Mar 2013 15:08:50 +0000
Resent-Message-Id: <E1UCX0U-0007cR-HM@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <phk@phk.freebsd.dk>) id 1UCX0G-0007ZZ-U1 for ietf-http-wg@listhub.w3.org; Mon, 04 Mar 2013 15:08:37 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <phk@phk.freebsd.dk>) id 1UCX0G-00033j-21 for ietf-http-wg@w3.org; Mon, 04 Mar 2013 15:08:36 +0000
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id DD3D989EAF; Mon, 4 Mar 2013 15:08:14 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id r24F8Emw025760; Mon, 4 Mar 2013 15:08:14 GMT (envelope-from phk@phk.freebsd.dk)
To: Eliot Lear <lear@cisco.com>
cc: Nicolas Mailhot <nicolas.mailhot@laposte.net>, ietf-http-wg@w3.org
In-reply-to: <5134B678.2010308@cisco.com>
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <CABP7RbfK9jT=-wXqv8wo6fJr8Wg0g9SYTZ3FeXHC=4yhihdsug@mail.gmail.com> <4D326297-42A8-487E-9450-7A971754C901@mnot.net> <loom.20130301T113152-432@post.gmane.org> <CABP7Rbc+QFQuEFocTsLZ68StriY+acqR0+DNLEnT-MXhr2MF-w@mail.gmail.com> <61cfe44be424129036f6bf68354e9c89.squirrel@arekh.dyndns.org> <6DB9F6DB-E351-46F0-B694-89EA33C15246@checkpoint.com> <loom.20130304T122610-306@post.gmane.org> <25456.1362406869@critter.freebsd.dk> <5134B678.2010308@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Mon, 04 Mar 2013 15:08:14 +0000
Message-ID: <25759.1362409694@critter.freebsd.dk>
Received-SPF: none client-ip=130.225.244.222; envelope-from=phk@phk.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-4.7
X-W3C-Hub-Spam-Report: AWL=-2.147, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.627
X-W3C-Scan-Sig: lisa.w3.org 1UCX0G-00033j-21 ab084b9276b282bc1b179245984e3dfc
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2 Header Encoding Status Update
Archived-At: <http://www.w3.org/mid/25759.1362409694@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16967
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: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

In message <5134B678.2010308@cisco.com>, Eliot Lear writes:

>> At present there are no relevant time formats which are leap-second safe.
>
>>From a *format* perspective, at least ISO-8601 and RFC-5322 (Message
>Format) are examples where leap-seconds are supported.

Both are standards for textual (aka: human readable) representation
of timestamps and involve a lot of text-processing to perform the
for HTTP usage necessary before/after comparisons on.

If HTTP/2 has any pretentions of being a high-performance protocol,
it must define an arithmetic time-representation, which allows
simple and cheap comparisons and the arithmetic operations necessary.

>When talking about seconds
>from an epoch, it seems to me that if the second occurred it should be
>counted, but I would suspect there already is a standard there as well,
>and we should follow it.  What would Linux do? ;-)

UNIX, POSIX, Linux and Windows all pretends that leapseconds don't exist.

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