Re: HTTP/2 Header Encoding Status Update
"Poul-Henning Kamp" <phk@phk.freebsd.dk> Mon, 04 March 2013 14:23 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 5BBEB21F8AB0 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 4 Mar 2013 06:23:20 -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 KrSdk89Bfe82 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 4 Mar 2013 06:23:19 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id D7CCB21F89CE for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 4 Mar 2013 06:23:19 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UCWGt-0003ou-AF for ietf-http-wg-dist@listhub.w3.org; Mon, 04 Mar 2013 14:21:43 +0000
Resent-Date: Mon, 04 Mar 2013 14:21:43 +0000
Resent-Message-Id: <E1UCWGt-0003ou-AF@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 1UCWGi-0003nk-IM for ietf-http-wg@listhub.w3.org; Mon, 04 Mar 2013 14:21:32 +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 1UCWGh-0000Y6-MX for ietf-http-wg@w3.org; Mon, 04 Mar 2013 14:21:32 +0000
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 59A9E89EAF; Mon, 4 Mar 2013 14:21:10 +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 r24EL9tw025457; Mon, 4 Mar 2013 14:21:10 GMT (envelope-from phk@phk.freebsd.dk)
To: Nicolas Mailhot <nicolas.mailhot@laposte.net>
cc: ietf-http-wg@w3.org
In-reply-to: <loom.20130304T122610-306@post.gmane.org>
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>
Date: Mon, 04 Mar 2013 14:21:09 +0000
Message-ID: <25456.1362406869@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.179, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.627
X-W3C-Scan-Sig: lisa.w3.org 1UCWGh-0000Y6-MX 71d70d88a53b97c34a0e6a73c06effd7
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2 Header Encoding Status Update
Archived-At: <http://www.w3.org/mid/25456.1362406869@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16965
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>
Content-Type: text/plain; charset=ISO-8859-1 -------- In message <loom.20130304T122610-306@post.gmane.org>, Nicolas Mailhot writes: >Also would if be possible to ask one of the IETF workgroups that worked on time >subjects to propose a time format safe wrt leap seconds and such? At present there are no relevant time formats which are leap-second safe. To my knowledge nobody is seriously working on a remedy for that, expecting leap-seconds to be killed in the next 10 years or so. I think trying to fix it in HTTP/2 would be ill-advised if not downright stupid, and we should just stick with POSIX, rather than invent yet another time-format[1]. Poul-Henning [1] The only standardized actually used format I can point to, which can deal correctly with leap-seconds is the "MJD" used by astronomers. MJD counts in days + fractional days, and therefore isolates the impact of leap-seconds to be non-accumulative, at the cost of noon being X.4999942130299418 rather than X.5 on days which insert leap seconds. Using MJD, with a 32 bit fraction, we get 20 microsecond resolution. A 16 bit day-number would give us only 9180 days, 25 years, before roll-over, but we could instigate a different epoch to buy us some time there. Conversions to/from POSIX/timeval/timespec would be mostly trivial, but not without pitfalls. -- 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.
- Re: HTTP/2 Header Encoding Status Update James Cloos
- HTTP/2 Header Encoding Status Update James M Snell
- Re: HTTP/2 Header Encoding Status Update Julian Reschke
- Re: HTTP/2 Header Encoding Status Update Martin Thomson
- Re: HTTP/2 Header Encoding Status Update Mark Nottingham
- Re: HTTP/2 Header Encoding Status Update James M Snell
- Re: HTTP/2 Header Encoding Status Update James M Snell
- Re: HTTP/2 Header Encoding Status Update Mark Nottingham
- Re: HTTP/2 Header Encoding Status Update James M Snell
- Re: HTTP/2 Header Encoding Status Update Amos Jeffries
- Re: HTTP/2 Header Encoding Status Update Julian Reschke
- Re: HTTP/2 Header Encoding Status Update Martin J. Dürst
- Re: HTTP/2 Header Encoding Status Update Julian Reschke
- Re: HTTP/2 Header Encoding Status Update Mark Nottingham
- Re: HTTP/2 Header Encoding Status Update Julian Reschke
- Re: HTTP/2 Header Encoding Status Update Nicolas Mailhot
- Re: HTTP/2 Header Encoding Status Update James M Snell
- Re: HTTP/2 Header Encoding Status Update Scott Schmit
- Re: HTTP/2 Header Encoding Status Update James M Snell
- Re: HTTP/2 Header Encoding Status Update Scott Schmit
- Re: HTTP/2 Header Encoding Status Update Scott Schmit
- Re: HTTP/2 Header Encoding Status Update James M Snell
- Re: HTTP/2 Header Encoding Status Update Nicolas Mailhot
- Re: HTTP/2 Header Encoding Status Update Yoav Nir
- Re: HTTP/2 Header Encoding Status Update Eliot Lear
- Re: HTTP/2 Header Encoding Status Update James Cloos
- Re: HTTP/2 Header Encoding Status Update Adrien W. de Croy
- Re: HTTP/2 Header Encoding Status Update James M Snell
- Re: HTTP/2 Header Encoding Status Update Nicolas Mailhot
- Re: HTTP/2 Header Encoding Status Update Nicolas Mailhot
- Re: HTTP/2 Header Encoding Status Update Poul-Henning Kamp
- Re: HTTP/2 Header Encoding Status Update Eliot Lear
- Re: HTTP/2 Header Encoding Status Update Poul-Henning Kamp