Re: [quicwg/base-drafts] HTTP/3 is lacking priorities (#3198)
Ryan Hamilton <notifications@github.com> Wed, 06 November 2019 21:52 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 6F51C120145 for <quic-issues@ietfa.amsl.com>; Wed, 6 Nov 2019 13:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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_24=1.618, 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 XBHXFYBMRRuQ for <quic-issues@ietfa.amsl.com>; Wed, 6 Nov 2019 13:52:12 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE86C12002F for <quic-issues@ietf.org>; Wed, 6 Nov 2019 13:52:11 -0800 (PST)
Received: from github-lowworker-6349a71.ac4-iad.github.net (github-lowworker-6349a71.ac4-iad.github.net [10.52.18.20]) by smtp.github.com (Postfix) with ESMTP id 12DF8C60EC2 for <quic-issues@ietf.org>; Wed, 6 Nov 2019 13:52:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573077131; bh=sJiQPLE9Ns2BXqWLH7HvnZxrwULvZpymNnT2sCPJMVA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TfoZ592WeZ5TV5pVfIyoPwOpGFVUdCJBnct6V6JO8nMVIsaxQuG3ibY0yNVuFWWoV R0KNX2+o/36Cb3ysFGV9duMeodDV3gRAdM45e8TOhr/GkeXswDfKPlOcffXg3hH8yz bWJklhY2bEmM+sCHbFKxnUm7XWWm2ETpz2f43bgo=
Date: Wed, 06 Nov 2019 13:52:11 -0800
From: Ryan Hamilton <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK574SCEP6UHYSXL5L532BZQXEVBNHHB524Q44@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/550516922@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3198@github.com>
References: <quicwg/base-drafts/issues/3198@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/3 is lacking priorities (#3198)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc3408b36b4_42fa3fa7d88cd95c49387"; 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/qWs1zJcjWfp1IKgjjG-e9yOu2hc>
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 21:52:14 -0000
Well, HTTP/3 the specification lack priorities in any form whatsoever :) But yes, you're totally right that an HTTP/3 endpoint implementation can do prioritization based on locally available information. What is lacking is a way for and endpoint to provide information to the peer to facilitate the prioritization. I'll be interested to see what sort of normative language we end up with for how an endpoint is required (or not) to act on this information. -- 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#issuecomment-550516922
- [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