Fwd: New Version Notification for draft-ietf-httpbis-priority-02.txt

Lucas Pardue <lucaspardue.24.7@gmail.com> Thu, 01 October 2020 12:06 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 4803E3A0D40 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 1 Oct 2020 05:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.748
X-Spam-Status: No, score=-2.748 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, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id NPweONzDTDsE for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 1 Oct 2020 05:06:17 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org []) (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 E89523A0EA5 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 1 Oct 2020 05:06:16 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1kNxJQ-0002RA-IH for ietf-http-wg-dist@listhub.w3.org; Thu, 01 Oct 2020 12:03:52 +0000
Resent-Date: Thu, 01 Oct 2020 12:03:52 +0000
Resent-Message-Id: <E1kNxJQ-0002RA-IH@lyra.w3.org>
Received: from mimas.w3.org ([]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <lucaspardue.24.7@gmail.com>) id 1kNxJN-0002Oh-R4 for ietf-http-wg@listhub.w3.org; Thu, 01 Oct 2020 12:03:50 +0000
Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <lucaspardue.24.7@gmail.com>) id 1kNxJL-0006o2-7M for ietf-http-wg@w3.org; Thu, 01 Oct 2020 12:03:49 +0000
Received: by mail-ej1-x62d.google.com with SMTP id a3so6860840ejy.11 for <ietf-http-wg@w3.org>; Thu, 01 Oct 2020 05:03:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=S54ZDEskX2amHWMP/HjNF4Pb17PWqZszVmbdgBYf5fY=; b=VbF9JCpQNK/jOPGSV9yRUdhVBusIvPe5t+61xDOIwT09zTSvMX0DDdaz6yNbuSTu10 VLZy90GW5zIun8ma06GwReo89fQEEsfxpFaAZjahuOid/vzSA6eNsdv9IMB/MceqWjVG jVhRM5iO4WU/uqmmpGqppLOZ6Ydl5ckBbhch1RfVX2A1pcAL51vaORKIDKZyL4T11PR1 2FOBOf+Tt0JkY1yEHtY2pRcR3lJOLLxMXs+flbO/4CP4TeeDUYbso1kL0Q5ML6lx9cA+ TjDMKhE7fQdsicNfEcFQ2CH08/bMy1S1Jt+5RV4ZqPbeTK2CtxPHhW6rZWF4SmyDoSWJ TsfA==
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=S54ZDEskX2amHWMP/HjNF4Pb17PWqZszVmbdgBYf5fY=; b=nGWKTunxmkymuKDtctNuppejSfv9UQV1BDrO0cqD84JjF+LvK6agAiqDmXkoq0m7Jn UM+mAO3lnjf9G6E0l7ZDkSXTCBZ5tAIUZBhszzmKrbnhbP2PHZ+9syHy7vXsroHZCMGZ Ijiy9rRd4uIEi1tERSG2Cxu+O3doSXn4YI96bzsKh82E89mS2JOPVrufbTlROs5TQ9L0 vU/VHx7Zafmjjxz/ZrPzjaRokhY0HmG9MWsrl24yyNaVAK69qUCKfrV4OS54IGdUzXw1 mrIrGm/JgxCWYISaM4uAPx5+Oab7gFWgvvf6Uwo6yUIVEgDUKDvYImEI/cgUlHjc5n8q fkZw==
X-Gm-Message-State: AOAM533hWYHXZdg0/9U2xOKpORxfzsHkydLj4hzq5g594gmXaBzaeVIt J4qJfSUI6LGOLhE+SBVJDuEg8EkxS20FmdoDVqI3vk4Xkqy5SA==
X-Google-Smtp-Source: ABdhPJxkro5xTwo1PVCO9dWGlyvxONe3vK8HwOxEbKJxlbMpcAURS6TQnnVw6GVc9LgwvjVz0eHnJv0Wg7tbCue+CFQ=
X-Received: by 2002:a17:906:3ac5:: with SMTP id z5mr7686408ejd.46.1601553815561; Thu, 01 Oct 2020 05:03:35 -0700 (PDT)
MIME-Version: 1.0
References: <160155102891.29050.18203576211471048544@ietfa.amsl.com>
In-Reply-To: <160155102891.29050.18203576211471048544@ietfa.amsl.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Thu, 1 Oct 2020 13:03:24 +0100
Message-ID: <CALGR9oYz8DN808i89MjVb4CQEnys0p+soCpVJSwjeLaLvF-t7w@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Cc: Kazuho Oku <kazuhooku@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000043ea2205b09acef9"
Received-SPF: pass client-ip=2a00:1450:4864:20::62d; envelope-from=lucaspardue.24.7@gmail.com; helo=mail-ej1-x62d.google.com
X-W3C-Hub-Spam-Status: No, score=-7.8
X-W3C-Scan-Sig: mimas.w3.org 1kNxJL-0006o2-7M c32ec77a6eeba26fa64166e3190f5f76
X-Original-To: ietf-http-wg@w3.org
Subject: Fwd: New Version Notification for draft-ietf-httpbis-priority-02.txt
Archived-At: <https://www.w3.org/mid/CALGR9oYz8DN808i89MjVb4CQEnys0p+soCpVJSwjeLaLvF-t7w@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/38070
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>

Hi Folks,

Kazuho and I have just cut a new version of Extensible Priorities. We think
this is a good interop target and for visibility I'd like to highlight the
notable points.

Following the WG discussion (and consensus) about header and frame signals,
we have been able to make progress on changes that we had proposed during
the interim meeting in May 2020 [1]. There has been feedback in the
meantime, details are a little different but the HTTP/3 PRIORITY_UPDATE
frame has changed format, which is a breaking change. The change from ASCII
art to QUIC-style frame definition can make this hard to spot: we've
dropped the bit field and encoded the prioritization target in the frame
type codepoint. To avoid clashes with the old codepoint (and failures that
might cause, especially for any deployments in the wild), we've moved the
frame types to 0xF0700 and 0xF0701. A future draft could move these back.

Since PRIORITY_UPDATE can be used to signal initial priority, we've added
some text to explain how a server should treat that. There's a little bit
more work left there but we hope some implementation experience will help
us refine the recommendations.

We've also added more exposition and guidance about how servers should
treat the Extensible Priority signal. It's tempting to get very
prescriptive here but we've kept the ethos of HTTP/2's server scheduling
guidance: signals are hints. We've highlighted some pitfall edge-cases that
servers should consider avoiding, no doubt there are some more we might
discover during interop testing.

To summarise: the priority scheme remains the same, we've tweaked frame
signals a bit and added more requirements about how to handle them, and
we've added more text to help server implementers. We encourage people to
take a look and try this out.

Kind regards
Lucas on behalf of Extensible Priorities editors

[1] -

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Thu, Oct 1, 2020 at 12:17 PM
Subject: New Version Notification for draft-ietf-httpbis-priority-02.txt
To: Lucas Pardue <lucaspardue.24.7@gmail.com>om>, Kazuho Oku <

A new version of I-D, draft-ietf-httpbis-priority-02.txt
has been successfully submitted by Lucas Pardue and posted to the
IETF repository.

Name:           draft-ietf-httpbis-priority
Revision:       02
Title:          Extensible Prioritization Scheme for HTTP
Document date:  2020-10-01
Group:          httpbis
Pages:          22
URL:            https://www.ietf.org/id/draft-ietf-httpbis-priority-02.txt
Htmlized:       https://tools.ietf.org/html/draft-ietf-httpbis-priority-02

   This document describes a scheme for prioritizing HTTP responses.
   This scheme expresses the priority of each HTTP response using
   absolute values, rather than as a relative relationship between a
   group of HTTP responses.

   This document defines the Priority header field for communicating the
   initial priority in an HTTP version-independent manner, as well as
   HTTP/2 and HTTP/3 frames for reprioritizing the responses.  These
   share a common format structure that is designed to provide future

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat