IETF Logo Mail Archive

Re: [quicwg/base-drafts] rate-limiting of CID issuance needs to be allowed (#2436)

Kazuho Oku <notifications@github.com> Fri, 08 February 2019 19:32 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 CA390130F49 for <quic-issues@ietfa.amsl.com>; Fri, 8 Feb 2019 11:32:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level:
X-Spam-Status: No, score=-3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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 iUrAVP--LsI9 for <quic-issues@ietfa.amsl.com>; Fri, 8 Feb 2019 11:32:01 -0800 (PST)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 E1101130F4D for <quic-issues@ietf.org>; Fri, 8 Feb 2019 11:32:00 -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=+1L1KnOurtCs7lrWP+TXJDkQAXI=; b=bd4MrVDygYepeMQr tLyG1yf/zPc4S2V5QkW4ywIgKcbNUPhmedIoGaV+c9hgeb0WivszrkWHYQ7TgauD pyQ/7ZWatLU16u3lBpz9Xuws9sRi4gghCOvBb+R4V21YNedpIlMqS1qI6mjf+d/I HwQzUM57LoEtvQuRpG2GodUKqWk=
Received: by filter1551p1mdw1.sendgrid.net with SMTP id filter1551p1mdw1-21807-5C5DD92F-25 2019-02-08 19:31:59.99533741 +0000 UTC m=+254185.467604416
Received: from github-lowworker-f6df7df.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0043p1mdw1.sendgrid.net (SG) with ESMTP id 4PJp8qlBRCKCYD1CqVgMxw for <quic-issues@ietf.org>; Fri, 08 Feb 2019 19:31:59.906 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-f6df7df.cp1-iad.github.net (Postfix) with ESMTP id DFC453E0CA1 for <quic-issues@ietf.org>; Fri, 8 Feb 2019 11:31:59 -0800 (PST)
Date: Fri, 08 Feb 2019 19:32:00 +0000
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1d1e2f9790586ee6c6b3615c300f9daf95092cb592cf0000000118759b2f92a169ce184b1573@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2436/461919062@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2436@github.com>
References: <quicwg/base-drafts/issues/2436@github.com>
Subject: Re: [quicwg/base-drafts] rate-limiting of CID issuance needs to be allowed (#2436)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5dd92fddab1_1e553fa4666d45bc14872"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2IYjyedo9iPrWG/6Mt3sAjk3XxPsLZrwNk9s i4i98jGCsypJbaucDYnT9YpK8lwf1C367Wj0u1yMkqV8KZj8IczVZZjaCUx5+zBAZNeQVhdp2pl0fe 5ayKBuV48g4txR4Wx2UI5pKU/eXb4xzhwWOwb4auNoLT4C1Jg+Kd5G0kLbMjujPXWrmkG226wgZ+nM A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/lh0dNu7NUel8lZar-O5suzle3Is>
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, 08 Feb 2019 19:32:03 -0000

> if you are offered to start a new connection mid up-load of multiple Gigabytes, or hours of transaction processing,

That's an untypical scenario for HTTP.

Note also that even if the client runs out of spare CIDs, it can still continue using the connection. The only thing the client cannot do is initiate a voluntary migration. Considering the fact that migration is not a mandatory feature (both for client and server), I do not think there's a strong reason to argue against endpoints refusing to provide additional room for migration at certain moments.

-- 
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/2436#issuecomment-461919062

v2.23.0 | Report a Bug | By Email