Re: New Version Notification for draft-kazuho-early-hints-status-code-00.txt

Kazuho Oku <> Sun, 13 November 2016 12:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 79D4812948C for <>; Sun, 13 Nov 2016 04:40:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.998
X-Spam-Status: No, score=-7.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mrtkSXqj0KiZ for <>; Sun, 13 Nov 2016 04:40:56 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 334DB1293DB for <>; Sun, 13 Nov 2016 04:40:55 -0800 (PST)
Received: from lists by with local (Exim 4.80) (envelope-from <>) id 1c5u22-0000cw-Qf for; Sun, 13 Nov 2016 12:37:10 +0000
Resent-Date: Sun, 13 Nov 2016 12:37:10 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1c5u1u-0007NN-C2 for; Sun, 13 Nov 2016 12:37:02 +0000
Received: from ([]) by with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <>) id 1c5u1o-0007M5-Ar for; Sun, 13 Nov 2016 12:36:57 +0000
Received: by with SMTP id a197so53977241wmd.0 for <>; Sun, 13 Nov 2016 04:36:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hQKNyyLRRkeEM8kDtRpBm7Dj5SVE8mpOuFtZ6N/Ruhg=; b=h1osbJFToD5QdlxtmUbGVX+0Ou5k298SU4VlijkWp55nIwnz/AjctMg8MNzXPswRQi AqGGXm1n5zk4hDeZH3GpX2HjcGiUvL4mekEmvxo1GTaC3zVQWj0lfOlzyiAwRZ0Saf+l Wfg8vgI65aa29rCyajaSi0r97g+XVLI8qSEC1aVp1X00mayTqXerVMSvd8pOk4j4NpnT jiHBuwR0qNJu8u18MLrMTz+HY7l3L1JFcROTV4nSax137ESGWPe0Epd8I7O2Py4UuDj8 YYaDz1HRpAL0U+GnE7T26Lfcr2LRIcfQiNYfXswezE9igPvFbnKaO7CfpGzVtrw2INQc CFPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hQKNyyLRRkeEM8kDtRpBm7Dj5SVE8mpOuFtZ6N/Ruhg=; b=LoHDSVd1pfMLYAuyhkD0jOf/U7Or263PFoKijIPUZG11BXn/+RPkVJo5P46GPJGYoP DewpivKcpKRKFNlBu0+YBzTNaBfiz3YWtcRErFVUlV9yoxn0zLNW4yyID0tZ1bR8vNTT vliv8M5NgCta0LuRp0RWsxnuDdTuap5cwt4KsUdHueYn4FfYHvR4mEB8jNHpH1eVd+q4 68H//hLr/kW1JaDq3tTEIumX9gKM694OG3hI7LI7CcDd3Z0rTQkC1BohmCzkDRiDfMTG r++tqETxUhyo/7x6Zrrw+4tngLJxjOYuNIX9voEsGRz+xe1UEfQcDN0YQzRcK3Whtg6d Y7+w==
X-Gm-Message-State: ABUngvdnrAACYRgdGIXihk4UPghfCrm46KteK6lurDUMw+2ahRWfMgVN942UWcw3nltfeqGmz+7HxB9ic03tFw==
X-Received: by with SMTP id ju2mr14261888wjb.223.1479040589753; Sun, 13 Nov 2016 04:36:29 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Sun, 13 Nov 2016 04:36:27 -0800 (PST)
In-Reply-To: <>
References: <> <> <> <> <> <> <>
From: Kazuho Oku <>
Date: Sun, 13 Nov 2016 21:36:27 +0900
Message-ID: <>
To: Alex Rousskov <>
Cc: HTTP Working Group <>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-4.5
X-W3C-Hub-Spam-Report: AWL=-0.984, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: 1c5u1o-0007M5-Ar 4d76fb1832ba91ab9609ce31e1f655de
Subject: Re: New Version Notification for draft-kazuho-early-hints-status-code-00.txt
Archived-At: <>
X-Mailing-List: <> archive/latest/32877
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

2016-11-12 9:00 GMT+09:00 Alex Rousskov <>:
> On 11/11/2016 12:49 AM, Julian Reschke wrote:
>> Q: maybe we should create a Wiki page, summarizing implementation status
>> and bug reports?
> FWIW, based on the results I had access to, most of the HTTP proxies
> using our HTTP compliance test suite mishandled 1xx messages one way or
> the other. Even today, after all the tests and bug fixes, there is an
> outstanding Squid bug where an unfortunate timing of 1xx and other
> events lead to a crash. 1xx is evidently tricky to get right.
> This data point is not meant to support or combat the "let the bad
> implementations surface/suffer" argument. I am just reporting that many,
> possibly most proxies mishandle 1xx messages.

Thank you for the info.

I do not have a strong preference on whether if we should try to
rescue the broken implementations, but to me your report is
interesting in the fact that it shows the bounds of using header-based
negotiation to work-around such implementations.

HTTP headers are end-to-end by default. Therefore a request header for
negotiating the use of 103 would go through an intermediary incapable
of handling 1xx correctly. We might consider designating the header
used for negotiation as a hop-by-hop header, but I'd be scared of
using a new token to the connection header (for interoperability

In other words, using header-based negotiation for Early Hints only
limitedly improves interoperability.

PS. sorry if my response resumes the combat.

> HTH,
> Alex.

Kazuho Oku