[quicwg/base-drafts] HTTP/3 is lacking priorities (#3198)
Ryan Hamilton <notifications@github.com> Wed, 06 November 2019 20:55 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA48E1200A4 for <quic-issues@ietfa.amsl.com>; Wed, 6 Nov 2019 12:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 b8t_s2yqJHor for <quic-issues@ietfa.amsl.com>; Wed, 6 Nov 2019 12:55:48 -0800 (PST)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA83C120072 for <quic-issues@ietf.org>; Wed, 6 Nov 2019 12:55:47 -0800 (PST)
Received: from github-lowworker-292e294.va3-iad.github.net (github-lowworker-292e294.va3-iad.github.net [10.48.102.70]) by smtp.github.com (Postfix) with ESMTP id E3020660C4E for <quic-issues@ietf.org>; Wed, 6 Nov 2019 12:55:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573073746; bh=+bKb6heeHtB5rWPPX2w0GagwNvcTYtYH3uWg8xU+YTk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=SxSGKIat30hQRoq5xz3KTNYhnjJ7IanYPbK2QmC4bsS3iiAcrBP2KOU7f+k2viCdZ mX0oB4C9acRRjzO5YrE7SI0H0ofYFUOC9u0lgsJmeM7iGBQmwElhLYZkdpDv2ncQaG iw0eXgcq5CsJL9QhqE/o3j0yM4CfmESyhKKKgRLw=
Date: Wed, 06 Nov 2019 12:55:46 -0800
From: Ryan Hamilton <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6MTXXCSDU2V4EIWAV32BS5FEVBNHHB524Q44@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3198@github.com>
Subject: [quicwg/base-drafts] HTTP/3 is lacking priorities (#3198)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc33352d2b76_252b3f9bd70cd96c1126ed"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/mnoiMA3_7yNZmyLPpwI-1EViqXY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2019 20:55:50 -0000
Since HTTP/3 is a multiplexed protocol (just as HTTP/2 was) a sender which is servicing multiple requests needs some way to decide which request to send data on. HTTP/2 used a ... baroque ... prioritization scheme that this working groups has decided (rightly, IMO) is a poor fit for HTTP/3. Before shipping HTTP/3 we should settle on some prioritization mechanism for HTTP/3. (Possible a very simple scheme with the opportunity for extensions to provide more sophisticated schemes.) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/3198
- [quicwg/base-drafts] HTTP/3 is lacking priorities… Ryan Hamilton
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Martin Thomson
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Ryan Hamilton
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Lars Eggert
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Mike Bishop
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Lars Eggert
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Lars Eggert
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Mike Bishop
- Re: [quicwg/base-drafts] HTTP/3 is lacking priori… Mike Bishop