Re: Adoption call for draft-schwartz-httpbis-optimistic-upgrade
Martin Thomson <mt@lowentropy.net> Thu, 25 January 2024 22:40 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=ietf.org@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 CAB37C14F61C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 25 Jan 2024 14:40:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.755
X-Spam-Level:
X-Spam-Status: No, score=-2.755 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.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b="BdGO+LE4"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="bSU3uhgw"
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 k_eGLeeo03tn for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 25 Jan 2024 14:40:55 -0800 (PST)
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 9F07DC14F5E8 for <httpbisa-archive-bis2Juki@ietf.org>; Thu, 25 Jan 2024 14:40:55 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1rT8Or-00Acv6-66 for ietf-http-wg-dist@listhub.w3.org; Thu, 25 Jan 2024 22:40:45 +0000
Resent-Date: Thu, 25 Jan 2024 22:40:45 +0000
Resent-Message-Id: <E1rT8Or-00Acv6-66@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mt@lowentropy.net>) id 1rT8Op-00Acu5-2R for ietf-http-wg@listhub.w3.org; Thu, 25 Jan 2024 22:40:43 +0000
Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by mimas.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mt@lowentropy.net>) id 1rT8Om-004rkT-RP for ietf-http-wg@w3.org; Thu, 25 Jan 2024 22:40:42 +0000
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 58D055C0114; Thu, 25 Jan 2024 17:40:36 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute6.internal (MEProxy); Thu, 25 Jan 2024 17:40:36 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1706222436; x=1706308836; bh=z7E+kKbpo9kDJ101vKBE1nia3P3r+xFheRJx1FxtBO0=; b= BdGO+LE4PjtoV/mvY5JX7gBuLuzfW2n2d1GejwhgYy9NJrNVRFDWzBw3GQS5bN7S /BO25md9s8TAcDnh367bGh8ueNvw8nYklNhdKQ9WL7CkmQrfTXXxWOZzvXRm4paO UW/khmOQRkbJDu5jEXHpW8CkQwGn0suAZJe+YHMCHVQURv/f0RCc0OMh4aInfXPQ V0TF/0XT0Yr5MKmF02ThAe+fjMuEBm7LcLHrei6Xahi4b+sMmrgN6Tev0c2IIH+F Nh1nleyw7trtXbot9sH0Deh/3npCp+N+oYfKLLfltEt8OMN6I5gWFMKt03SuuOtd mRZ7N1Q0OPdw1AhrSeKTUQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1706222436; x= 1706308836; bh=z7E+kKbpo9kDJ101vKBE1nia3P3r+xFheRJx1FxtBO0=; b=b SU3uhgwmuDVzc6AlwgmdAb74i5WZvyK8F2OTdKbh4k9YSlbw/bY6Y/KKP+wbpok2 7r+CUAE+SBM4u9axrtk+03hD4IaY8mDBHBm+zZgMbn1ZpOFcuSC/3jo6rFd9+J9p zanRs3EztYzM7Gcmt/Ayy2BeRin3Uiczv3zUHHjGhWRio9e1HT7JBSlG5vf2T/L/ gi5P4n8CRrIdpUnnDZCWRNj1i7QbEA/mV3sBWqY1dToOgA0MXI5uZt8JzOBmPAFN T6QV2/k98UCrXgo7sAkW5AGP9UQJucCHRkuwlIyauQJKudE7du0XL16h+HYU/qBk kzeqNJ2Ur5MtzQeQBXWLA==
X-ME-Sender: <xms:ZOOyZc12spi9KzDP574-d_YVhJqbINkZmYx8ROlieJjQ0UDI5ztxmQ> <xme:ZOOyZXHfqu0IlSroFIUgYIBdPO6A3-W62I5ghoPVSfM9WSsTlM79Ue6so1wMC7TIS P8-ETc6diEbT1uUqDE>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdeliecutefuodetggdotefrodftvfcurf hrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdforghrthhi nhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecuggftrf grthhtvghrnhepffetgfevvdfhtdffheejudefhffhveehudefhffgleelteeifeegfefg gfelhefgnecuffhomhgrihhnpehivghtfhdrohhrghenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:ZOOyZU4BDahwnNEDqOM9LpDyWHVq-qXp6BUPianY2mEH0xoCuGl2mg> <xmx:ZOOyZV0OgVkNWL68jlCOaxVshGs42ZcZ7F83JJ2LDhoJEE-nVxlkhg> <xmx:ZOOyZfFv2i5MyhUWuU367vM96uSVai73r2amebeuW73ga6l9ZksIPw> <xmx:ZOOyZWwv560JXbVwFgnH173Jlj7MjyOF8-qcfCWNRQ98Llqjl9iBfw>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 207A02340080; Thu, 25 Jan 2024 17:40:36 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.11.0-alpha0-119-ga8b98d1bd8-fm-20240108.001-ga8b98d1b
MIME-Version: 1.0
Message-Id: <0b8b50a1-8a65-413b-af4b-34abb4f5718c@betaapp.fastmail.com>
In-Reply-To: <DC01619C-3B1C-4AE8-B331-56B1CE3E7120@apple.com>
References: <DC01619C-3B1C-4AE8-B331-56B1CE3E7120@apple.com>
Date: Fri, 26 Jan 2024 09:40:15 +1100
From: Martin Thomson <mt@lowentropy.net>
To: Tommy Pauly <tpauly@apple.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=66.111.4.29; envelope-from=mt@lowentropy.net; helo=out5-smtp.messagingengine.com
X-W3C-Hub-DKIM-Status: validation passed: (address=mt@lowentropy.net domain=lowentropy.net), signature is good
X-W3C-Hub-DKIM-Status: validation passed: (address=mt@lowentropy.net domain=messagingengine.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-9.8
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1rT8Om-004rkT-RP 9f36966efa8ee72b0ec1cd877ba1d39c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Adoption call for draft-schwartz-httpbis-optimistic-upgrade
Archived-At: <https://www.w3.org/mid/0b8b50a1-8a65-413b-af4b-34abb4f5718c@betaapp.fastmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/51738
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/email/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Yes, we should adopt it. Maybe the first thing we should do is add a clear description of what a client OR server can do to avoid the problems. The server treating Upgrade as implying Connection: close might be a good start, counter to what Section 4 currently says. We should not be recommending mitigations that only one affected party can deploy. On Wed, Jan 24, 2024, at 04:41, Tommy Pauly wrote: > Hello HTTP, > > This email starts a working group adoption call for "Security > Considerations for Optimistic Use of HTTP Upgrade”, > draft-schwartz-httpbis-optimistic-upgrade. Notably, this updates RFC > 9298 (connect-udp, which was produced by the MASQUE WG) on how to > handle HTTP Upgrade, including to disallow optimistic data sending for > HTTP/1.1. > > The document can be found here: > > https://datatracker.ietf.org/doc/draft-schwartz-httpbis-optimistic-upgrade/ > https://www.ietf.org/archive/id/draft-schwartz-httpbis-optimistic-upgrade-00.html > > This adoption call will last for 3 weeks, until *Tuesday, February 13*. > Please reply to this email with your reviews and comments, and whether > or not you think HTTPBIS should adopt this draft. > > Thanks, > Tommy
- Adoption call for draft-schwartz-httpbis-optimist… Tommy Pauly
- Re: Adoption call for draft-schwartz-httpbis-opti… Lucas Pardue
- Re: Adoption call for draft-schwartz-httpbis-opti… David Schinazi
- Re: Adoption call for draft-schwartz-httpbis-opti… Glenn Strauss
- Re: Adoption call for draft-schwartz-httpbis-opti… Ben Schwartz
- Re: Adoption call for draft-schwartz-httpbis-opti… Glenn Strauss
- Re: Adoption call for draft-schwartz-httpbis-opti… Willy Tarreau
- Re: Adoption call for draft-schwartz-httpbis-opti… Martin Thomson
- Re: Adoption call for draft-schwartz-httpbis-opti… Willy Tarreau
- Re: Adoption call for draft-schwartz-httpbis-opti… Tommy Pauly
- Upgrade failure and Connection: close request hea… Kazuho Oku