Re: [quicwg/base-drafts] Placeholder limits make for awkward clients (#2734)

Lucas Pardue <> Tue, 21 May 2019 12:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DBCE11201CB for <>; Tue, 21 May 2019 05:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.392
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dWbypAMEw2wO for <>; Tue, 21 May 2019 05:17:50 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4B5BB120193 for <>; Tue, 21 May 2019 05:17:50 -0700 (PDT)
Date: Tue, 21 May 2019 05:17:49 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558441069; bh=UmPQTHySZOXMNvUmld3FqvlpJpR/JyVKqvxivPph1yc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=O3rMS9+fUhyH6wa98twkvsCEayidnJo/yMzOZXLMExBgi0jqZvk1CcZ/Re1kRrOQ/ 7fCGnLzE029jM6md1dcIK4inXtQvCEzRE2ysD8J1+ouR42jJxgf5TA+srNeGIY5dTX oSY1vrDygdZnHfIfDPMk2MyOnc7DaT6x+1A1pHmo=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2734/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Placeholder limits make for awkward clients (#2734)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce3ec6d4357b_3c8d3f89c42cd96c14868"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 21 May 2019 12:18:00 -0000

A server advertises a limit it should be able to fulfill that entire limit. For example, by reserving the capacity - even if the structures are not explicitly allocated. A naive implementation that advertises a large limit (like MAX_INT) and fails to reserve capacity shouldn't get surprised if things go bad when a client comes along and attempts to prioritise MAX_INT placeholders...   

This is mostly an implementation detail.

The real points that we should focus on are on understanding if the limit unilaterally set by the server is the right approach given the way people might want to use placeholders.

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