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

Lucas Pardue <notifications@github.com> Mon, 22 July 2019 20:40 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 37F891200DE for <quic-issues@ietfa.amsl.com>; Mon, 22 Jul 2019 13:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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_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 HRusdmhhfaFq for <quic-issues@ietfa.amsl.com>; Mon, 22 Jul 2019 13:40:48 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4834C1200A3 for <quic-issues@ietf.org>; Mon, 22 Jul 2019 13:40:48 -0700 (PDT)
Date: Mon, 22 Jul 2019 13:40:47 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1563828047; bh=ZzgzGfqCOnkvln8ncrkB9ZGIIZkOHzsurbl33a2Qb9g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NR6BpozUtNdWsE+od3gkuK+6wLe6l3k2ZEf661PztW/TFMFhVuxwv3Pxdl36iSUcI vRReydLQihsMGWFwAAfJ6AMyxppzar3T2sBLmsKREERDGHL4gDQ+kgnqfZ5WG+TMmT Jl/wGGc/W7iNK2hd+tv9WNt3VTYfU/fuTKGr8O5Y=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZLECTFCCV5M6DRMH53INI47EVBNHHBYFV37I@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/review/265037706@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_5d361f4f48c66_3ef43fe2b16cd968597756"; 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/mc4pyReHnRu5K7ItAxPT-dQ96ak>
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:40:50 -0000

LPardue commented on this pull request.

I think this is in general a positive move. It closes some things out. However, I do wonder if it might make us revisit other things that were previously put to bed. For example, we might want to follow up the discussion about separate unidirectional streams [1], because the space is now smaller. 

[1] https://github.com/quicwg/base-drafts/issues/2678

> @@ -139,8 +139,8 @@ Alternative Services; this process is described in greater detail in
 Within each stream, the basic unit of HTTP/3 communication is a frame
 ({{frames}}).  Each frame type serves a different purpose.  For example, HEADERS
 and DATA frames form the basis of HTTP requests and responses
-({{request-response}}).  Other frame types like SETTINGS, PRIORITY, and GOAWAY
-are used to manage the overall connection and relationships between streams.
+({{request-response}}).  Other frame types like SETTINGS and GOAWAY are used to
+manage the overall connection and relationships between streams.

A minor contention: IMO SETTINGS or GOAWAY don't exemplify "relationships between streams". In fact, removing tree depencies helps makes request streams way more independent.

-- 
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#pullrequestreview-265037706