IETF Logo Mail Archive

Re: [quicwg/base-drafts] HTTP/3 with strict priorities (#2700)

ianswett <notifications@github.com> Fri, 17 May 2019 20:44 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 C4B26120158 for <quic-issues@ietfa.amsl.com>; Fri, 17 May 2019 13:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.606
X-Spam-Level:
X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 yUgZpieSC2-9 for <quic-issues@ietfa.amsl.com>; Fri, 17 May 2019 13:44:15 -0700 (PDT)
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 E57E21200E5 for <quic-issues@ietf.org>; Fri, 17 May 2019 13:44:14 -0700 (PDT)
Date: Fri, 17 May 2019 13:44:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558125854; bh=+HSPRL8EEjiqtO5uJeIOUx1fwHyVszRhxVpXA7VV6t8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=R1qwlh1AQTV7k0NlCf6ceXJyDCJtK5KU9GOgQpKQmDc+lsSwdovSAqc/sp05mppNG TIpibJRP672038pdywCLhCE1CAKbQIe93HexIJEpzR3qMkIeUgXgHTFphg6fZIBKK0 aCu32cowXWXPVlCPYo6tSU9x9pBR/DdSwZ4283fQ=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZMYX66LVVKTNDNYIF25RHZ5EVBNHHBU6PCKA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2700/c493593668@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2700@github.com>
References: <quicwg/base-drafts/pull/2700@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/3 with strict priorities (#2700)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cdf1d1e29943_112c3f9fdcccd95c1064324"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/5mGVVC0U9y57RxKVC0lcTmlzzvc>
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: Fri, 17 May 2019 20:44:17 -0000

@dtikhonov "My point is mostly that one technology already works." - I'll specifically disagree with this point.  HTTP/2 has been an RFC for 4 years now and according to Patrick Meenan's surveys, a huge fraction of servers don't support HTTP/2 priorities and clients have somewhat odd usage patterns, with Chrome specifically trying to re-create strict priorities and Edge ignoring them entirely.

The complexity has also kept HTTP/2 priorities out of the web APIs, because it's clear the full functionality is far too complex for web developers and it's hard to agree upon what should be surfaced.

The target should be something the majority of implementations will implement, even if it's not their ideal solution.

-- 
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/2700#issuecomment-493593668

v2.19.0 | Report a Bug | By Email