Fwd: New Version Notification for draft-kazuho-httpbis-priority-03.txt

Lucas Pardue <lucaspardue.24.7@gmail.com> Tue, 05 November 2019 12:11 UTC

Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB1A1208ED for <quic@ietfa.amsl.com>; Tue, 5 Nov 2019 04:11:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_BOUND_DIGITS_15=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 9WbTD22oz2Uz for <quic@ietfa.amsl.com>; Tue, 5 Nov 2019 04:11:23 -0800 (PST)
Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF9391208A9 for <quic@ietf.org>; Tue, 5 Nov 2019 04:11:22 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id m6so6707680vsn.13 for <quic@ietf.org>; Tue, 05 Nov 2019 04:11:22 -0800 (PST)
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; bh=3+JtT7gqFn+WsOY0lm2UyHXF1SNRmCtAOmycreAn4mc=; b=VTixmARp+oeKmvG0joKRKxDcbN18msuH0F2M7Cw5b/4ato0C3C5gwJsNi6WzNGwfxz NWFj/kT/KjOAwHT9dR606Kj2mDl4LF/ggkpgOUjcgGlWjejAURaYk2Aa3D96ciUczcuZ V9mOv5kgU5JhSdLQMoxLqAHiLdLDNpwnKld4u/56RDBkQekDq9nWZPoph0VgGg0OwzoS PFwi50IiPLnTxuudl/cBjQEu1fmzxJ4aQ1Z54RxFR8r2TEJkWsu6voV/ehTYQwdaajsm 7vXN3KLDCdpfIkLNwKerNLyGvAgZBkeUadFfqBGZLgLwd++wakhxv5vRDBbpIOMjPH/W RUTg==
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; bh=3+JtT7gqFn+WsOY0lm2UyHXF1SNRmCtAOmycreAn4mc=; b=SiT+K4WpUQppfmudcecCGYcScNet1MAdaBzkmAXAYY0tx6KaqoZP3MwnmEorlT70uk IeZqx6UzX1hPgM1JjWd+2LEWBDZ+bj8CeXnLw7BXH2CvIfLiNXf9ZGXbSb6SA9erJDSR TpW4EqDmb6gQxsbpEC/1YOmsl7lYr5XDTRePoc4mjZQhzsyKGMFt4YNHTZb8UisUsr+W oAF84kGeVYDo9Gb8pOmT08E9K1duB/sSKp4OebOGErKILBfYZy9avWHCUu6jaRVb7dlC GQI2Y/+B60+GRtxnNwsJIQLJRZRCg84P4ueM+vv0vl6RSZ3ZhpdC+KOIiB5U0MpAho1s UTEw==
X-Gm-Message-State: APjAAAXaDLEiKpuo8zQk94M1J5yGz0ZEHMl+CZKo9R5ubFG3Qo1oI6Fn h/lL1acL0tUv7GFG2kBp7gvQuie7qPjY8J2HfyQNMsY3
X-Google-Smtp-Source: APXvYqxIvh0I+2tCo7rkEXTRdriW/k85SM/D0su11m+BojptRidYFzYTGuXs3dbeCh+H/9JD8V1aoKXin8DLb+8iPPc=
X-Received: by 2002:a05:6102:2041:: with SMTP id q1mr15236094vsr.15.1572955881626; Tue, 05 Nov 2019 04:11:21 -0800 (PST)
MIME-Version: 1.0
References: <157291052116.13928.17523145259269241429.idtracker@ietfa.amsl.com>
In-Reply-To: <157291052116.13928.17523145259269241429.idtracker@ietfa.amsl.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 5 Nov 2019 12:11:10 +0000
Message-ID: <CALGR9obHr8-iwVooru5BrrYuK4jQRkHEpVwsMMtjpDBj8eFZhQ@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-kazuho-httpbis-priority-03.txt
To: HTTP Working Group <ietf-http-wg@w3.org>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009260610596985454"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-JMjWsiZEMOjUMu1UBZKB9P1srI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2019 12:11:24 -0000

Greetings Gentlefolk,

During IETF 105 in Montreal it was decided to form an HTTP Design Team.
Since then the team has had some good discussion [1] and made some
progress, which was presented by the team lead Ian Sweet during the QUIC
Interim meeting in Cupertino [2]. To summarise, the design team believe
that draft-kazuho-httpbis-priority is a good starting point for a priority
scheme that offers an alternative to HTTP/2 priorities, that a negotiation
mechanism for selecting the desired priority scheme for use in an HTTP/2 or
HTTP/3 connection is useful, and that reprioritization is useful.

Kazuho and I have released draft-kazuho-httpbis-priority-03. For ease of
reference and review, draft 03 incorporates a negotiation mechanism based
on a design modification to draft-lassey-priority-setting-00 [3] along with
updates based on the design team and community's feedback so far. In future
we may split these facets back out of the document.

The major changes in draft 03 are:

* A motivation section that consolidates several problems statements
presented to the HTTP community [4] [5] [6]
* A fuller negotiation mechanism based on a new SETTINGS_PRIORITIES setting
for HTTP/2 and HTTP/3.
    * Endpoints send an size-bound ordered list of their preferred schemes,
if a compatible scheme is found the server's preference order prevails.
* Fully specify how reprioritization works using a new frame called
PRIORITY_UPDATE for HTTP/2 and HTTP/3.
* Expanded guidance for intermediaries, especially those that coalesce
client connections to an origin.

We would appreciate any comment from the HTTP, or wider, community either
on the lists or directly on the GitHub repository [7].

Thanks again to all the contributors so far.

Lucas

[1] https://groups.google.com/forum/#!forum/http-priorities-design-team
[2]
https://github.com/quicwg/wg-materials/blob/master/interim-19-10/HTTP%20Priorities%20Update.pdf
[3] https://tools.ietf.org/html/draft-lassey-priority-setting-00
[4] https://tools.ietf.org/html/draft-peon-httpbis-h2-priority-one-less-00
[5]
https://h3.edm.uhasselt.be/files/HTTP3_Prioritization_extended_3jul2019.pdf
[6]
https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md
[7] https://github.com/kazuho/draft-kazuho-httpbis-priority

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>;
Date: Mon, Nov 4, 2019 at 11:35 PM
Subject: New Version Notification for draft-kazuho-httpbis-priority-03.txt
To: Kazuho Oku <kazuhooku@gmail.com>;, Lucas Pardue <
lucaspardue.24.7@gmail.com>;



A new version of I-D, draft-kazuho-httpbis-priority-03.txt
has been successfully submitted by Kazuho Oku and posted to the
IETF repository.

Name:           draft-kazuho-httpbis-priority
Revision:       03
Title:          Extensible Prioritization Scheme for HTTP
Document date:  2019-11-05
Group:          Individual Submission
Pages:          19
URL:
https://www.ietf.org/internet-drafts/draft-kazuho-httpbis-priority-03.txt
Status:
https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority/
Htmlized:       https://tools.ietf.org/html/draft-kazuho-httpbis-priority-03
Htmlized:
https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-priority
Diff:
https://www.ietf.org/rfcdiff?url2=draft-kazuho-httpbis-priority-03

Abstract:
   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
   extensibility.




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