IETF Logo Mail Archive

Re: [quicwg/base-drafts] Remove PRIORITY (#2922)

Lucas Pardue <notifications@github.com> Mon, 22 July 2019 20:53 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 D7DC812008C for <quic-issues@ietfa.amsl.com>; Mon, 22 Jul 2019 13:53:40 -0700 (PDT)
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 L37bMv2ZoEnt for <quic-issues@ietfa.amsl.com>; Mon, 22 Jul 2019 13:53:38 -0700 (PDT)
Received: from out-17.smtp.github.com (out-17.smtp.github.com [192.30.252.200]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00EE2120120 for <quic-issues@ietf.org>; Mon, 22 Jul 2019 13:53:37 -0700 (PDT)
Date: Mon, 22 Jul 2019 13:53:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1563828816; bh=yqczICSulA6VJsQQXwG+wyAYZSxuGzFqQf3lJtAg5JM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OxDKpH7s2CEB5t55TVjxW73kWHYFYdJQ4KdCEwp30Hw7so/eeYTjh5y6TaB8uwuBW sLraDbzkvUSRg2tsnvktU9yk8XiLc9w7y5l+J4XqV7u8qp12ugTM4FMt/eEU/rmx5Y GWuFuwcRSL2pSQpeEArzek5bgYQMiHPn6XD+xdT8=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK24FCXR356ILHBEF4F3INKNBEVBNHHBYFV37I@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2922/c513950016@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2922@github.com>
References: <quicwg/base-drafts/pull/2922@github.com>
Subject: Re: [quicwg/base-drafts] Remove PRIORITY (#2922)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d362250d4495_7fd33fcdf86cd968526499"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/PPlDbFJ70oePk-TN90NUjVuX9s4>
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: Mon, 22 Jul 2019 20:53:41 -0000

I'm also a little nervy that the removal of text makes it appear that the first user of streams (HTTP/3) quietly ignores the transport's recommendation in section 2.3 

> A QUIC implementation SHOULD provide ways in which an application can
   indicate the relative priority of streams.  When deciding which
   streams to dedicate resources to, the implementation SHOULD use the
   information provided by the application.

-- 
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/pull/2922#issuecomment-513950016

v2.23.0 | Report a Bug | By Email