IETF Logo Mail Archive

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

ianswett <notifications@github.com> Sat, 24 November 2018 01:43 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 0AC9F128CF3 for <quic-issues@ietfa.amsl.com>; Fri, 23 Nov 2018 17:43:28 -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 Q6hZnsmKUSB2 for <quic-issues@ietfa.amsl.com>; Fri, 23 Nov 2018 17:43:26 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CC6A130E89 for <quic-issues@ietf.org>; Fri, 23 Nov 2018 17:43:26 -0800 (PST)
Date: Fri, 23 Nov 2018 17:43:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543023805; bh=Vikzm1Kd4aaFZjVBA1Uuqmf5cCB7EYkUI9aPWVyEW3s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ImLPCZx3F7Ktg1Hx9XNzouF0HwfONQqwzpcIpy3gFLbBCK4HaZ1okigDLzrF8pHm1 FT1sVlS6YbEdpJoinBaoy3lFOh+1nfvYCk3YG0RafwLZ0tz5e5Fkm1233LJd5ciMgG DvCZ+fSd/k+Yd8m30rJhoFugOI2H4+Chaz3acpho=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab59c855f3d8f7e3a5ddcb8c939bb51f12cb474aef92cf0000000118106ebd92a169ce16a20dde@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/441336338@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_5bf8acbddf95_218e3fb1eaad45b8169186"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/3dy9Vuv04UPd4O4W4d1LlDJs4Uo>
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: Sat, 24 Nov 2018 01:43:28 -0000

One idea: In an effort to enforce the principles, but not be overly strict or complex, maybe allow the connection to be closed with an error if a NEW_CONNECTION_ID frame is received with an ID that's more than the max_connection_ids from the largest retired connection id(or 0 if no ids have been retired)?

-- 
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-441336338

v2.23.0 | Report a Bug | By Email