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

Ryan Hamilton <> Fri, 30 November 2018 23:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A902112D7F8 for <>; Fri, 30 Nov 2018 15:56:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.46
X-Spam-Status: No, score=-4.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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DWKyqRwJpGNv for <>; Fri, 30 Nov 2018 15:56:07 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6C4FA126F72 for <>; Fri, 30 Nov 2018 15:56:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=3gKssm0Q7AF8jOiw+xfQZyHCW2U=; b=kYsIqfUmeL6Nhz00 CYrgsYQHWe/gI5kW5fWWvbpjYZ+iefd82CIMu3BAQV3/wDuZ24O0x0eQ2t2O7OkB sqTAnkylj9xw1kN9gGY3ZyKo3VAfY30q175a4lPhcXUbkzCQmV9TRhhd9Go6jx80 WhoGjMK5/tjApGVnxbLm1bCBFDo=
Received: by with SMTP id filter0767p1las1-9544-5C01CE16-36 2018-11-30 23:56:06.756881115 +0000 UTC m=+1300801.211048886
Received: from (unknown []) by (SG) with ESMTP id VuNCMIjnQImqiWKaxI9f_w for <>; Fri, 30 Nov 2018 23:56:06.655 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 9CB03461471 for <>; Fri, 30 Nov 2018 15:56:06 -0800 (PST)
Date: Fri, 30 Nov 2018 23:56:06 +0000
From: Ryan Hamilton <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1994/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
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_5c01ce169b31a_17043f8071cd45c097794"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0MrNKonpKNgUko7ZlUQneJ/AvuqMIlbAPwXD 3N4BDZhir8VNEUdYzEUF4ino3eyM8JBzRgV37JO33qaW6hj9pFLOuOSkbBN8k0WszcfyQNiTuWzizo B91G/lFGjy4zysZQqzz4yHv+e5MTrigTgA1QhGtyMV+0DieyogPO8r6QCU/5ye2u583qtHKm978jPX I=
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: Fri, 30 Nov 2018 23:56:10 -0000

I agree with ianswett here. If there's a limit that an endpoint is allowed
to set on the number of connection IDs that it stores, it should
communicate that limit to the peer. Anything else seems like it sets us up
for subtle interop bugs down the road. (And if I have a limit which the
peer knows and exceeds, then closing the connection seems great.)

On Thu, Nov 29, 2018 at 12:25 PM ianswett <> wrote:

> The current default number of ids is 8, which I think is wrong. However,
> the design team thought it was reasonable.
> I think the fact my preferences are so different is an indication
> one-size-fits-all is wrong, so I favor adding this transport param.
> Re: closing the connection, I'm going to have to do something if I receive
> too many, and it's really easy to not send too many, and it's really
> obvious when the connection is closed, so I think it's the more
> straightforward way to implement this.
> But ask @ekr <> said, if a peer indicates a value,
> it should be the target, unless you can't supply that many.
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <>,
> or mute the thread
> <>
> .

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