Re: Call for Adoption: Extensible Prioritization Scheme for HTTP

Tommy Pauly <tpauly@apple.com> Fri, 13 December 2019 16:48 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 6477B1208E2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 13 Dec 2019 08:48:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.75
X-Spam-Level:
X-Spam-Status: No, score=-2.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 krSzXxIOaQXM for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 13 Dec 2019 08:48:20 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25D0C1208DE for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 13 Dec 2019 08:48:18 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ifo4K-0004CA-QP for ietf-http-wg-dist@listhub.w3.org; Fri, 13 Dec 2019 16:45:32 +0000
Resent-Date: Fri, 13 Dec 2019 16:45:32 +0000
Resent-Message-Id: <E1ifo4K-0004CA-QP@frink.w3.org>
Received: from titan.w3.org ([2603:400a:ffff:804:801e:34:0:4c]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <tpauly@apple.com>) id 1ifo4I-0004BP-6S for ietf-http-wg@listhub.w3.org; Fri, 13 Dec 2019 16:45:30 +0000
Received: from nwk-aaemail-lapp01.apple.com ([17.151.62.66]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <tpauly@apple.com>) id 1ifo4E-0005vF-3l for ietf-http-wg@w3.org; Fri, 13 Dec 2019 16:45:30 +0000
Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id xBDGhF9p060772 for <ietf-http-wg@w3.org>; Fri, 13 Dec 2019 08:45:24 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : from : content-type : mime-version : subject : date : references : to : in-reply-to : message-id; s=20180706; bh=FNj+WoUldDaVz5ynU8TN1S+AZLAToZKxHl5q40Z4YbQ=; b=ZDOjwUnrHOqD1Ia82LYjntVOz2b58cQWYw4PN6f10nme+M3prmx1sm2Bl0mC5/m9B2gR JCDaVPBRxstwSTbBzhdyNZC/xyXx3uNNiAsFjzJYRgjurrqR76xCbQXfnVx1opPECpA4 mBJBq+bxvjSoFfeApSg/siUIn5aSLkCKcesRti5tXoNCp6YSwUweK9avwWczTgCkhdwh dazjXgoZuQtN/eL3Lrs5LekonWXWRdNWD38H02g6OsH6G7z1llMHuTkUEq+fDxjqm9B3 q1rJvZP4CV72zG29EdVRdNBw5S5jKGAEXC7Ev6JGPZk8yp1jEdFsnPZDuQeomoWG4pAe qA==
Received: from ma1-mtap-s02.corp.apple.com (ma1-mtap-s02.corp.apple.com [17.40.76.6]) by nwk-aaemail-lapp01.apple.com with ESMTP id 2wrbw6pw2r-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <ietf-http-wg@w3.org>; Fri, 13 Dec 2019 08:45:23 -0800
Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by ma1-mtap-s02.corp.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPS id <0Q2G002ZRMJM7W90@ma1-mtap-s02.corp.apple.com> for ietf-http-wg@w3.org; Fri, 13 Dec 2019 08:45:23 -0800 (PST)
Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) id <0Q2G00A00M5PAK00@nwk-mmpp-sz09.apple.com> for ietf-http-wg@w3.org; Fri, 13 Dec 2019 08:45:22 -0800 (PST)
X-Va-A:
X-Va-T-CD:
X-Va-E-CD:
X-Va-R-CD:
X-Va-CD: 0
X-Va-ID: 292f8e2c-7f0c-4a0e-be69-629c2c3d10e0
X-V-A:
X-V-T-CD: 02d63d4ac31622f4425b5159c2960928
X-V-E-CD: c864ce26bea9e2ae3e736a69ac1884d9
X-V-R-CD: 49736cb74467b56b650ac23ec410388c
X-V-CD: 0
X-V-ID: 35df19f0-da8d-4423-923d-081545bea815
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-12-13_05:,, signatures=0
Received: from [17.234.113.212] by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPSA id <0Q2G00K2HMJL9P50@nwk-mmpp-sz09.apple.com> for ietf-http-wg@w3.org; Fri, 13 Dec 2019 08:45:21 -0800 (PST)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_AD0726A9-52B8-41FB-A7B4-64F67AF0F554"
MIME-version: 1.0 (Mac OS X Mail 13.0 \(3594.4.17\))
Date: Fri, 13 Dec 2019 08:45:18 -0800
References: <9F1A17D3-C801-42E3-B020-1447E5D172CC@apple.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
In-reply-to: <9F1A17D3-C801-42E3-B020-1447E5D172CC@apple.com>
Message-id: <49571133-55AE-4134-80AD-9F9F773CB13D@apple.com>
X-Mailer: Apple Mail (2.3594.4.17)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-12-13_05:, , signatures=0
Received-SPF: pass client-ip=17.151.62.66; envelope-from=tpauly@apple.com; helo=nwk-aaemail-lapp01.apple.com
X-W3C-Hub-Spam-Status: No, score=-5.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1ifo4E-0005vF-3l fe4f6e669efe11d740ae3f5129da300f
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Call for Adoption: Extensible Prioritization Scheme for HTTP
Archived-At: <https://www.w3.org/mid/49571133-55AE-4134-80AD-9F9F773CB13D@apple.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37217
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/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hello all,

Thanks for the feedback received in the call for adoption! We will be adopting this document into the working group. We have asked Lucas and Kazuho to continue as editors of the document.

Authors, please submit a draft-ietf-httpbis-priority-00 when ready; we'll also move this document into the WG GitHub.

As mentioned previously, this work is an important piece of deploying HTTP/3. As such, I would like to encourage that we try to converge on open design issues quickly (QUICly?). The adoption call did highlight that the main concern is around the use of headers or frames for signaling. If anyone has thoughts on this issue, please take them to the list and/or GitHub.

Best,
Tommy & Mark

> On Nov 20, 2019, at 11:28 PM, Tommy Pauly <tpauly@apple.com> wrote:
> 
> Hello HTTPbis,
> 
> During our IETF 106 meetings, we received updates from the design team for updating HTTP's priority hinting mechanism, with the goals of defining priorities for HTTP/3 and allowing this scheme to be backported to HTTP/2.
> 
> The output of the design team is documented in this draft: https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04 <https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04>
> 
> This draft defines:
> - A SETTINGS parameter to disable the HTTP/2 priority mechanism
> - Two priority values, urgency (0-7), and incremental (boolean)
> - Mechanisms to communicate these priority values using headers and frames
> 
> This email begins a call for Working Group adoption of this draft. Note that adoption indicates that we, as a working group, want to use draft-kazuho-httpbis-priority as a basis for the definition of priorities for HTTP/3. There is still ongoing discussion that will continue, specifically around the mechanism for end-to-end and hop-by-hop signaling.
> 
> This call will end on Friday, December 6. Please reply to this email and indicate whether or not you believe we should adopt this document!
> 
> Best,
> Tommy & Mark