IETF Logo Mail Archive

Re: [quicwg/base-drafts] The number of Connection ID is unbounded to NEW_CONNECTION_ID sender (#2403)

Kazuho Oku <notifications@github.com> Wed, 06 February 2019 03:23 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 4A39512950A for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 19:23:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Level:
X-Spam-Status: No, score=-12.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_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 KT9-9gxZGTFg for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 19:23:06 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C51C1288BD for <quic-issues@ietf.org>; Tue, 5 Feb 2019 19:23:06 -0800 (PST)
Date: Tue, 05 Feb 2019 19:23:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549423385; bh=Joq0jHDuVD6TaRzFOlhUDfipkr+gXA6GSfZ0YD/ty/M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=S9OMxzoRcAqxB/xVVV6J+xa+lho4zMHsGuJlQ9NQYHtcsfS5DfWp/gUKLi6NshQQB 67eTBozI7Ex/7wJXKN2EtkoMmXeDinPO2rR1q/3uv9RxgvvnaNEzxCUn5xP2T5dECO om0DO/XDu5vOlLZLDQrGkbcmL9Vag2aD3UYIPAnM=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abec697ab130319f62b18cbe635e07441edf87c5bb92cf000000011872151992a169ce1833bfbd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2403/460888623@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2403@github.com>
References: <quicwg/base-drafts/issues/2403@github.com>
Subject: Re: [quicwg/base-drafts] The number of Connection ID is unbounded to NEW_CONNECTION_ID sender (#2403)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5a531948bb4_15073fbe930d45bc80694"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Eb-BWYBfvJL3BzykeIz58wHNaCU>
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 03:23:08 -0000

@erickinnear Thank you for the comment. I can understand the hesitation to having another requirement for the consumer of CIDs.

I think I agree to your conclusion that simply clarifying that the issuer might cap the limit the total number of CIDs it assigns for each connection would be sufficient (FWIW, I am considering of capping the total to 256 CIDs per connection).

My complaint is simply that the current text can be interpreted to assume that it is the issuer's fault when the client aggressively using new CIDs runs out of spares.

-- 
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/2403#issuecomment-460888623

v2.23.0 | Report a Bug | By Email