[quicwg/base-drafts] NUM_PLACEHOLDERS MUST NOT be zero (#2753)

Kazuho Oku <notifications@github.com> Thu, 23 May 2019 03:52 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 8772A12004A for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 20:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.606
X-Spam-Status: No, score=-1.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, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id bqMht8NPNGkq for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 20:52:09 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 496F1120152 for <quic-issues@ietf.org>; Wed, 22 May 2019 20:52:04 -0700 (PDT)
Date: Wed, 22 May 2019 20:52:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558583522; bh=aTN4+hRJA49IudmgDLNxNKBazee4gE0PT7RoUSPvVZw=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ap+cXvOwxZ0zBs7u57gwTSpb8Lo2oGUmiazrYGaJVB/wRARAe1dqjfabXXIeD47TV 5A5r1ZZ4MEZtTIsOTct+KDS4jIzUHxsLotA8P+rfzBXK6b/mZrz8uN1pMKsC4zeaCy mvzVUXo4ireDptJsg20SG5iMgyLcKEC8apKYTPXc=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYATQ3XNCH6UD5GQ2F26NFWFEVBNHHBVK26ZM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2753@github.com>
Subject: [quicwg/base-drafts] NUM_PLACEHOLDERS MUST NOT be zero (#2753)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce618e245710_68ae3ff0298cd96840405"; 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/Wix5yeU1exyCPdY5mBU8l8BgRk8>
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: Thu, 23 May 2019 03:52:12 -0000

Currently, the text says:
The default value is 0. However, this value SHOULD be set to a non-zero value by servers.

I think we should change the default to unlimited or to some sensible number, and also introduce a minimum permitted number.

Prioritization is not something a client can enforce, therefore servers that prefer to ignore or mishandle placeholders can just ignore / mishandle them, as well as other information for prioritization (e.g. weights and dependencies).

To rephrase, communicating the capability of handling just one of the features of prioritization has marginal benefit compared to the complexity it introduces to the client side (e.g., the need to use different prioritization approach depending on if the server supports placeholders).

Or, if it is the case that we do not expect browsers to no longer use placeholders but are keeping it for proxies, we should remove "SHOULD", because that is a minor use case that has not seen actual use in HTTP/2.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: