IETF Logo Mail Archive

Re: [quicwg/base-drafts] Define initial PRIORITY frame and remove exclusive dependencies (#2075)

Dmitri Tikhonov <notifications@github.com> Tue, 04 December 2018 20:33 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 C50D5130E3B for <quic-issues@ietfa.amsl.com>; Tue, 4 Dec 2018 12:33:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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_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 fiNML9pSKK7z for <quic-issues@ietfa.amsl.com>; Tue, 4 Dec 2018 12:33:51 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 851BF12D4E7 for <quic-issues@ietf.org>; Tue, 4 Dec 2018 12:33:51 -0800 (PST)
Date: Tue, 04 Dec 2018 12:33:50 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543955630; bh=LZT40DNHpEncqJ28eXKu0l95yLd742NzgMG8Pf/aE0c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bhz9Cx6X9aPMuKkiSStRS/qjKDD0Vm87fMif0Z2HS6gxkk5KueJVazjXjJgBoU4qR S9k3SoT4EWUm2qD+CYdYiGOvmMQG5aBl2ULLMaJxLuXIv7wbOBLA/Z9+Cmnk/YNE0A tui46CI0wIUScK4UwAvcPS2aNqxXqkXiO21G1KTw=
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb68f49cd73863185002af91b554aebef3cc5246792cf00000001181ea6ae92a169ce17019477@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2075/c444247799@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2075@github.com>
References: <quicwg/base-drafts/pull/2075@github.com>
Subject: Re: [quicwg/base-drafts] Define initial PRIORITY frame and remove exclusive dependencies (#2075)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c06e4ae19a14_21df3fea310d45c0834a5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dtikhonov
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/fYMISNoSNZaQrbqaJajW_dL277U>
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: Tue, 04 Dec 2018 20:33:54 -0000

I think a hard requirement is too expensive.  The only reason to duplicate the priority information from the request stream is if the priority changes, otherwise it's a waste.

Case 1: superfluous duplication

Request A: PRIORITY( A -> B )
Control: PRIORITY( A -> B )

Case 2: race possible

Request A: PRIORITY( A -> B )
Control: PRIORITY( A -> C )

Case 3: ensure eventual consistency

Request A: PRIORITY( A -> B )
Control: **PRIORITY(A - B)**; PRIORITY( A -> C )

My guess is that most clients will fall under Case 1.  If request priority changes, the client should use Case 3.


-- 
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/2075#issuecomment-444247799

v2.30.2 | Report a Bug | By Email | System Status