Re: [quicwg/base-drafts] Mandate using a new connection ID on migration (#2413)

erickinnear <> Mon, 04 February 2019 23:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EDE79129AB8 for <>; Mon, 4 Feb 2019 15:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Status: No, score=-12.553 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 ovYYkKkRpuob for <>; Mon, 4 Feb 2019 15:39:47 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 11CF5129508 for <>; Mon, 4 Feb 2019 15:39:47 -0800 (PST)
Date: Mon, 04 Feb 2019 15:39:45 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549323585; bh=8g7qOGIldaN02Jlhl88WpRkCZnrC7hZFg6r803WTkK8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KTRAPkhNgE6B69Wpce0v/K+wJa1XAtzZ+leXm1wJBtXUgCw2ERisgsknSzwcDJ0aM 4OTkfA3opns+PhKQRvivvT77AbRwsKqtKVP8J9W1131B0vqPDBhfWIL6YEtR8fGljO MwsbRQT+MupcRCRMGT13JYyjkQuUJWMo/66RU14U=
From: erickinnear <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2413/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Mandate using a new connection ID on migration (#2413)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c58cd41afa9f_5d7a3fa3504d45bc31714"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
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: Mon, 04 Feb 2019 23:39:49 -0000

It looks like it’s been moved around a lot, but 5.1.2 says

> As discussed in Section 9.5, each connection ID MUST be used on packets sent from only one local address. An endpoint that migrates away from a local address SHOULD retire all connection IDs used on that address once it no longer plans to use that address.

Historically, that’s been under the CID sections, not the migration sections, which made it kind of hard for me to dig up. 

Re the proposed diff: 
>An endpoint that exhausts available connection IDs can only
migrate if the peer chooses to use receive packets with zero-length connection

Does that conflict at all with the below text in 5.1?

> An endpoint whose peer has selected a zero-length connection ID MUST continue to use a zero-length connection ID for the lifetime of the connection and MUST NOT send packets from any other local address.

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