Re: [quicwg/base-drafts] endpoints don't know how many connection IDs the peer is willing to store (#1994)

ekr <notifications@github.com> Fri, 23 November 2018 19:09 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 0D1C4130DEE for <quic-issues@ietfa.amsl.com>; Fri, 23 Nov 2018 11:09:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 UgTj57Dec_Li for <quic-issues@ietfa.amsl.com>; Fri, 23 Nov 2018 11:09:17 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5912612DD85 for <quic-issues@ietf.org>; Fri, 23 Nov 2018 11:09:17 -0800 (PST)
Date: Fri, 23 Nov 2018 11:09:16 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543000156; bh=cwMTNdz/Q0glSpjHDzmxVC6fBGPhv9VKYgnkBNIb2nc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HkZ5EDqttDU6JLGh+HmPbvsR8ZEaIerB4QNSAL4SW/HA4cx4SXYqED2O6aYWvgLqm iP2VAWSdmvLxa7jxvvSDEoqA0+ATt4ISS60LVTEDaW451LBiq+NPFrbi5uctDlG0dB g+O4DO2zDRR/lacvJE5OF5OEtOCCCaXq5lJ3RpFw=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd185a299def3b871bb3133b615261b23e7006cda92cf000000011810125c92a169ce16a20dde@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1994/441305154@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1994@github.com>
References: <quicwg/base-drafts/issues/1994@github.com>
Subject: Re: [quicwg/base-drafts] endpoints don't know how many connection IDs the peer is willing to store (#1994)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf8505c7fa2d_25873fbd29ed45c42487a0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/VrOr3ZeztHa8F0Bwo7_GJjvS_KA>
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, 23 Nov 2018 19:09:19 -0000

I'm not sure we need this, but if we are going to bother to have it, then it should be a target. I.e., the other side should be required to keep you full, not just not to send you any more than this.

I'm also concerned by the semantics of having exceeding the max be an error, because it introduces pressure to increase max. The issue is that what you want to have is spare CIDs, and right now the only real way to elicit new CIDs is to RETIRE, but while that's in flight, if the other side is at max it can't send more, so this makes things more brittle.

-- 
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/1994#issuecomment-441305154