IETF Logo Mail Archive

Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)

"Martin Thomson" <mt@lowentropy.net> Thu, 21 November 2019 04:46 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB88120232 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 20:46:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=EXi6rIs5; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=wpqU+qBC
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 tKgdranrTAGU for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 20:46:02 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B419120133 for <quic@ietf.org>; Wed, 20 Nov 2019 20:46:02 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 474DB223E8; Wed, 20 Nov 2019 23:46:01 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 20 Nov 2019 23:46:01 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm3; bh=iCrzpVpW1ujJi5MjF3PeZvAuG7VI tL/n8Kp4A9u+YLk=; b=EXi6rIs5u/2DSDSpcKjioVUJeMGT95uOuxDZEd/Jf0Ml AiCo1oMRA4KNqNrmgz/AfJ40Mmrz8Pk2PUzGRJVriXYGA3wQ0/EgTDc8s+fwD1m2 eHvSr5wpJkM9UnBISBzNZokWfjnLEf+qx3VxJkM5ZXr0LwjJP/XywRWgbFDJyQu2 Y4K3ooAR7YhHWeygqkkqQV8Pjztl45ktrm1B6P5L1bXrGtKHAmrv22AMXVyQvJZE DzhrcrGOg4u0WHLQjH3mktU+N/Z+ZGHVzkTl5l4fMbKzrUX17k9maHgV91f0EWie St9zaQXveOUSyJYXzOAPPayv76L0wy3mjFm6ky8hHA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=iCrzpV pW1ujJi5MjF3PeZvAuG7VItL/n8Kp4A9u+YLk=; b=wpqU+qBCV5jgoY+lZOlF2d EsZ0XOGwnE5BActtTOJHLBdwjFDBVuDkHn11a8gUvdUHJuy/QAI37S4lzYF/RRAS G8ddbkoERrxcc1wlOw0Z8/rTX3ExUmpaHF7GWNzXRoFpNl7n0gxUyfNtzfO/UJ2q S54umeYSMLhYEYdbI9OSlYm0fHn/VVYF7vwgGyIAR6mffhZb+eEB9Z5clPhsfC0j RrSMksSyiuG6A/srYjNCHXswmsck5uqmxMwlLLu0SqoPBeKBTnc7Afe06EWk8Qam HS/nGJxRoh+pKj5quHhiYmubVi2MmZYgKwsZ516IsZpS0u2OJPoLLYdEEO4pxbkg ==
X-ME-Sender: <xms:iBbWXdbtPTOu2IO3_AZ0syFIx8XOpfQoNJVOpnUqYms307GRKeTK3g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehuddgjeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreerjeenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecuff homhgrihhnpehgihhthhhusgdrtghomhenucfrrghrrghmpehmrghilhhfrhhomhepmhht sehlohifvghnthhrohhphidrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:iBbWXZie-NMg6DOmMLeBTjFrXVVY_Ma1arHrwAKd4uohbW4xZBMMoA> <xmx:iBbWXXMgKfNhYDR-1RJwAV6Amft5tNykAhgJA8lbXhW48_BmsbX9dg> <xmx:iBbWXTMEXB1mZzvJnVsESxI6vg55PAKFA8Iuf1Df_CT4bP9adxIR3Q> <xmx:iRbWXUFyZgTNSdYscPqz87YtOfrBkRf7ns6BVhpi8AvTmkfKjpzKLg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 33183E00A3; Wed, 20 Nov 2019 23:46:00 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1
Mime-Version: 1.0
Message-Id: <fed8fbb4-69aa-4b8b-bde2-21b1eaeb6ff8@www.fastmail.com>
In-Reply-To: <CAC7UV9bqo=jFearFt-yTr5M6q7noywvicG-bW6k4UQGq7bikuQ@mail.gmail.com>
References: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com> <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com> <a8f57134-114e-4d56-9076-7d880897b842@www.fastmail.com> <CAC7UV9bqo=jFearFt-yTr5M6q7noywvicG-bW6k4UQGq7bikuQ@mail.gmail.com>
Date: Thu, 21 Nov 2019 12:45:39 +0800
From: Martin Thomson <mt@lowentropy.net>
To: Robin MARX <robin.marx@uhasselt.be>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7LJDmtkUDarDNbBQlCUc4XVz2LQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 04:46:05 -0000

Hi Robin,

On Thu, Nov 21, 2019, at 10:11, Robin MARX wrote:
>  > I understand that reprioritization was identified as being important 
> by the design team, but I don't recall seeing ever any evidence to 
> support that view. Can we split that piece out and maybe pursue it 
> separately? 
> 
> Could you expand on this statement a bit more? 
> In my view, reprioritization has two sides: reprioritization from the 
> client after sending an initial priority and server-side 
> reprioritization, overriding the client's initial priority.

I refer specifically to the frame.

> The first side comes into play when doing things like video/media 
> streaming when switching qualities (see e.g., 
> https://github.com/kazuho/draft-kazuho-httpbis-priority/issues/92) or 
> for the "switching tabs" use case that e.g., Ian keeps mentioning.

These seem fairly obvious, but I realized recently that a lot of our thinking hasn't been grounded in any data.  That is, we're intuiting things about the value of the signal, but we never got firm reasons.

v2.23.0 | Report a Bug | By Email