Re: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)

Martin Thomson <notifications@github.com> Wed, 06 February 2019 04:14 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 BBC76126C7E for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 20:14:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Level:
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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: 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 CnPjxP5rB6u6 for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 20:14:28 -0800 (PST)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14A03123FFD for <quic-issues@ietf.org>; Tue, 5 Feb 2019 20:14:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; 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=vk9zbq0B5Kt3Ad73JejmupFDX5E=; b=KXCDpqaKVkMqjpHt 6ebUW8ydRtHyB9OW8YdFR3cCDilEoyamo6IXWatM5z/MQ36xiS0uxxrqrW4gWbtY 9HwQmD5OgG+94XKH00EmqWvhk3f/C2tO4RXb1BbUthMGd8ml6gm0SBvJYJAvGnmv 1bm8YsTS19+R1v1zGgf6LpWwJW4=
Received: by filter0580p1iad2.sendgrid.net with SMTP id filter0580p1iad2-26101-5C5A5F22-11 2019-02-06 04:14:26.472814426 +0000 UTC m=+28451.782665947
Received: from github-lowworker-3c598a3.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0012p1iad1.sendgrid.net (SG) with ESMTP id nYcUBhZXTVm7DprwhO37Uw for <quic-issues@ietf.org>; Wed, 06 Feb 2019 04:14:26.523 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-3c598a3.cp1-iad.github.net (Postfix) with ESMTP id 7E11BA80241 for <quic-issues@ietf.org>; Tue, 5 Feb 2019 20:14:26 -0800 (PST)
Date: Wed, 06 Feb 2019 04:14:26 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6dd937116b0160ec834bb72f97ce926a77ce93d092cf000000011872212292a169ce184361c4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2428/c460895656@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2428@github.com>
References: <quicwg/base-drafts/pull/2428@github.com>
Subject: Re: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5a5f227caaa_7cb53ff753cd45bc92335"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0ll7g/9PFr62qyuIXvbcKw07OGYEcy5rEzAe ej6blxQPCzN6QTEoc012xEzuCbb53oy9qDqaE0O6SFc1Xm7z22U58MKea2+FWPGKu/meTaPdYM7YM1 uf67tpadKk1vpi7bn2NOClpxumwtsIRbccdVJ2CVQrqC7YH2LC3s25D0g+Q0uS/eIuffUEltIYYe3Z M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/2cqV8bHMQVTehzC1axsXbWdaDdA>
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: Wed, 06 Feb 2019 04:14:30 -0000

I don't want to put this in the draft.  It tells endpoints not to change connection IDs based on some unspecified (scary!) constraints that may or may not be present in a peer.

I realize that there might be a limited supply in some implementations, but artificial constraints on the rate of use is not the way I would address the problem.  Refusing or slowing issuance of new connection IDs if someone retires too many is a better approach.  In other words, implementations should deal with this on their own.

-- 
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/pull/2428#issuecomment-460895656