Re: Call for Adoption: Extensible Prioritization Scheme for HTTP

Ryan Hamilton <rch@google.com> Thu, 21 November 2019 17:46 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 8ADFB120821 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 21 Nov 2019 09:46:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.251
X-Spam-Level:
X-Spam-Status: No, score=-10.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 xLMpRu6H7nGP for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 21 Nov 2019 09:46:00 -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 AD96A1208E7 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 21 Nov 2019 09:45:45 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1iXqU0-00012K-At for ietf-http-wg-dist@listhub.w3.org; Thu, 21 Nov 2019 17:43:08 +0000
Resent-Date: Thu, 21 Nov 2019 17:43:08 +0000
Resent-Message-Id: <E1iXqU0-00012K-At@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 <rch@google.com>) id 1iXqTy-00011h-7E for ietf-http-wg@listhub.w3.org; Thu, 21 Nov 2019 17:43:06 +0000
Received: from mail-wr1-x435.google.com ([2a00:1450:4864:20::435]) by titan.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <rch@google.com>) id 1iXqTw-0007kB-RV for ietf-http-wg@w3.org; Thu, 21 Nov 2019 17:43:06 +0000
Received: by mail-wr1-x435.google.com with SMTP id s5so5525264wrw.2 for <ietf-http-wg@w3.org>; Thu, 21 Nov 2019 09:43:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=At2FYKPLxRv4TSrJXqv+kIh9oMcqOwCK7v21EOkO3Oc=; b=OQgFGT4dm4ujYCOqH7yEVRhby1N7DRg2x7zhyd0CW4ywxMnpmYGhwWOXWxXk/HSzTx u6EAsdF8TVcxOx+kdL3NuQyy68atUcfuGO89q9uVUQbW0AwvqDnW93zCp7BcU1bsj9xa ocy8MdJUeuLK24tSDmSZHmmrh69zobInyPEf+6kcQJuneGw3sDoqhz3lpUQf9/gLhYNu jZGNXqNl/TFaSt229bOwxKv/R557Dstd5RgIIlKj7hPG0myVuDF7PsWAr13J/leMaqep 2Y5rHEAhX9nLaOdplbw3A1i8CVFX/XoVa9fLQzFGZ2SEWgcnA7lQ0ilDRRPDROFBZBxg seZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=At2FYKPLxRv4TSrJXqv+kIh9oMcqOwCK7v21EOkO3Oc=; b=O/oonVuIBYjJoSh62Ry8WOu4xb4vlEcnX6W2CRm4QZ2RSstg77sUyf+VK/CJTp+tTd P+S79LUECC8IIDyV2G+NBfjeYDhe4rFymNts5gTMahANlNxpd+4KVR5XoHYBSDkQIx+a oIGWnTuLXgL48rumrJvg69q8IbxcBPTOafw9ynF5tXOaZIXo9CkTsWcLHQq3tYMLGqpk ac2m0f8DpLfWenu2H+BFHcXcsHiOADzmRzxgurhFl1OAF7M54frq7eGY7hc1OUWrkUNW G9NbQkBcxcCxu2hChHsPC6sbV2c+d0a/zIPklvGa95uk1uuds/Q0+bSVt+cUnmw35vxG xGug==
X-Gm-Message-State: APjAAAWVEd6zN4hIklaHFTErU9chfyEYUBWi9/tdapVPHw5muz42M6ro gVyvu3kne1vy2H5Yjx6iw8sfsTv9xGL2zvo64L96ug==
X-Google-Smtp-Source: APXvYqz/nAaiKAtOhlxkWM8jNrtYGdGc35qTpTn28w/diCfHGStO8SG3JzOQFmYe1NBU0KDNhi5/djT/lW7sGJw2b18=
X-Received: by 2002:adf:fe81:: with SMTP id l1mr12419533wrr.207.1574358182310; Thu, 21 Nov 2019 09:43:02 -0800 (PST)
MIME-Version: 1.0
References: <9F1A17D3-C801-42E3-B020-1447E5D172CC@apple.com>
In-Reply-To: <9F1A17D3-C801-42E3-B020-1447E5D172CC@apple.com>
From: Ryan Hamilton <rch@google.com>
Date: Thu, 21 Nov 2019 09:42:50 -0800
Message-ID: <CAJ_4DfTgcQFU5jNDBKCjC3vF-nWA5y_gZXBOvc_B5zQzNsSMSw@mail.gmail.com>
To: Tommy Pauly <tpauly@apple.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="0000000000003538d90597ded4f6"
Received-SPF: pass client-ip=2a00:1450:4864:20::435; envelope-from=rch@google.com; helo=mail-wr1-x435.google.com
X-W3C-Hub-Spam-Status: No, score=-19.6
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1iXqTw-0007kB-RV fb06ce7901f020aa24d8cbdc31115c2d
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/CAJ_4DfTgcQFU5jNDBKCjC3vF-nWA5y_gZXBOvc_B5zQzNsSMSw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37165
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>

I strongly support the adoption of this work. (I'm skeptical of the
header-based mechanism for conveying this information, but as you said,
this discussion can continue in the WG).

On Wed, Nov 20, 2019 at 11:31 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
>
> 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
>