Re: Early Hints (103)

Julian Reschke <julian.reschke@gmx.de> Wed, 23 November 2016 09:13 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 D55291293D8 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Nov 2016 01:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Level:
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UECOAcOd7Mc9 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Nov 2016 01:13:07 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 481F812945B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 23 Nov 2016 01:13:07 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1c9TYU-00069J-41 for ietf-http-wg-dist@listhub.w3.org; Wed, 23 Nov 2016 09:09:26 +0000
Resent-Date: Wed, 23 Nov 2016 09:09:26 +0000
Resent-Message-Id: <E1c9TYU-00069J-41@frink.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1c9TYO-00068D-C1 for ietf-http-wg@listhub.w3.org; Wed, 23 Nov 2016 09:09:20 +0000
Received: from mout.gmx.net ([212.227.15.18]) by mimas.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <julian.reschke@gmx.de>) id 1c9TYH-0004OA-9J for ietf-http-wg@w3.org; Wed, 23 Nov 2016 09:09:15 +0000
Received: from [192.168.178.20] ([93.217.109.81]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MZkv0-1cSe3O2OKc-00LZAq; Wed, 23 Nov 2016 10:08:44 +0100
To: Patrick McManus <mcmanus@ducksong.com>, HTTP Working Group <ietf-http-wg@w3.org>
References: <CAOdDvNos+qXxi8K3HPtkuzkAuc1ctAmdt=Oz+vJy+oBgB7skQA@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <dfcc8c24-494e-204d-1e07-194bdc8e5b3b@gmx.de>
Date: Wed, 23 Nov 2016 10:08:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <CAOdDvNos+qXxi8K3HPtkuzkAuc1ctAmdt=Oz+vJy+oBgB7skQA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:eCfD3m6zjc7F+GzomS8ZiHYMM1MuIkX5skE0wsva/i0tlxAuJlI bq7XRlZ8o1gb3IQgJUlgn4QXGClpWfJKT5+KRzN0Idu0ZcC4Cg3ZTXCpsN2oAbgDQ7ny1VV 3fyGEvqTwxqNnWbErYGw3sTwCtbUJde7GRoyORGOvESuCV8a2Tou9/RpzM2buqmAxoZJ6jU Oryq/e4/OAfXLh1ECcS6Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:iiRdDpPhVz8=:1XTroEb8izneJGeIebqNja 8TfMzAp7Y1PhxAqxq7vgZeH/8rvrKGq8jM5Pws2NzNKWxGSYuC6ZwJhcjks0L/MV4fJYM8Yl/ /pY4zUp7MnwX+8wjpZt74DLpyfktgI2AvyBVHjbdVlUTzxkme5fWBiytJ9rker9/M5p13BrZB IHrLxDUfYlgcOIDlB2TjHWnplQ8soMC+Z8Xa4sJVWJdUzryQAuGqffAZb5yQc+MU3PDnw9KHc 4OPQvt7YK6cIymJXMuhQnpg0r66s7Te1IDoS9ZnShlrzlalplgGu4jgMcdbgjB+TLe86TgjNF 6ZsC254fvoyByciOGJqspkCQ4/qloG0Ur2K7FffitdsG4dtVOidXmoXFJs+ElUFc5AS6V3TeY Y+w2b7/4bC30JILLNLcAdMj4GhDIuUp1aGBCZt49qiNr1vtkcUCXcrqZuXO44I5TAQopJCP4d 7NeP373bZWTgOZsR4M9FS08tLY2fS2p9zfX0/HwqBcm1AsJpJXtxB5o0FebhSudKU5N4EB/fX 7xvvfRPNj0D9J4VkVdZoAiK0dm8R7u0ktEMSvX90Hw85hXryN4dOwW0G4D2mhNhHQNewVbaeP M2kaa0yxcBW3fqQDGp9BkHHXixucdf8AX1bhLmwSpn67gduxtoKD6O/Lt6XBlA58j42ET/fF4 G02G/xDns5Jk3gptr1VZiHSlF/mMAwj8sCY+nuh9yOyDhVDEfrgPezYLyoJEut2TpF2D2GrlH LncVtJ6USdF72mmuLbPTMdbSLpNRlMWUXv3JgTHfLv4kDoWN0QSxaNlJCEVC5WxyRk8OuHhTG Rkdcm6BE7SuZ+gcNzcGMS2LidTDcg==
Received-SPF: pass client-ip=212.227.15.18; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-6.6
X-W3C-Hub-Spam-Report: AWL=-0.025, BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1c9TYH-0004OA-9J 9052b2ca5e31f3140e0ae72ccb08579e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Early Hints (103)
Archived-At: <http://www.w3.org/mid/dfcc8c24-494e-204d-1e07-194bdc8e5b3b@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32969
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>

On 2016-11-22 23:26, Patrick McManus wrote:
> Dear Gentlefolk of HTTPbis,
>
> This is a followup to Kazuho's presentation in Seoul[*] where he
> discussed
> https://datatracker.ietf.org/doc/draft-kazuho-early-hints-status-code/
>
> The idea seemed to have acceptance (both in the room and on the list)
> with some concerns expressed about interoperability. Kazuho was kind
> enough to publish an endpoint so you can test if the client you
> implement has an unexpected failure in the face of 103.

...and the endpoint is <https://nghttp2.org/?103-eh>.

> However, the draft was published pretty close to meeting time and there
> wasn't much space for discussion in the room. So before we do a Call For
> Adoption, I would like to hear some more discussion so the chairs can be
> confident there is interest - even if that discussion is "I would like
> to implement that" or "what does that accomplish?". Please do chime in,
> your silence will be taken for disinterest otherwise :).

I would like to work on improving implementations so that they can 
actually use it.

I think it's great to work on 103, and while doing that also improve the 
situation for 1xx in general. I already saw somebody else saying that 
they're looking into using RFC 2518's 102 Processing status as well 
(different use case, but same protocol level).

Best regards, Julian