[quicwg/base-drafts] SHOULD for using PRIORITY (#2697)
Kazuho Oku <notifications@github.com> Mon, 13 May 2019 23:50 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 B264A12006D for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 16:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level:
X-Spam-Status: No, score=-1.392 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 QDuAppxkUq4Y for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 16:50:18 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 039AF120026 for <quic-issues@ietf.org>; Mon, 13 May 2019 16:50:17 -0700 (PDT)
Date: Mon, 13 May 2019 16:50:16 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557791416; bh=40ti+sVzryXVLq5UZLoiP4UqB0gb4TKy7Nh9p7B4dnA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=vgTUSP9tlRTMky2Ru8rn8kJHeBCdd/z23DPjqeVs0jHYXFdmKsqzvFt2FugT4B3N8 jmkQmpteAun8o/3eD912RKdTONfLbDtrifTFkx3VaAt6ROpcqimgArojnBp7lOQtgP LKTyuBYofgenpxAzOWKdiemGkI5GaNXprhZbUc0o=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYY7RXBDYNWSDMQ34N2442TREVBNHHBU4MN6E@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2697@github.com>
Subject: [quicwg/base-drafts] SHOULD for using PRIORITY (#2697)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cda02b8a988d_530e3fa4b86cd9685382f2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/tuRFDx2hsl_-HXVzKUcm86QZIgo>
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, 13 May 2019 23:50:20 -0000
In some client-server combinations using HTTP/2, we saw performance degradation from HTTP/1.1 due to either the client not specifying the priorities, or the server not processing the priorities in a correct manner. Considering that, I think it makes sense to clarify that endpoints are expected to support the prioritization scheme. Though it does not need to be a MUST because prioritization is only necessary when requests with different precedences are coalesced onto a single connection. Therefore I think something along the lines of SHOULD is the way to go. Also we might go one step further and consider making the use of the PRIORITY frame on the request stream a MUST. That would force implementors "how" they should support priorities. -- 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/issues/2697