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

Igor Lubashev <> Tue, 05 February 2019 00:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D2121130DD6 for <>; Mon, 4 Feb 2019 16:38:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.552
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3_hCqpvjIGAw for <>; Mon, 4 Feb 2019 16:38:34 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C5E1F130DE3 for <>; Mon, 4 Feb 2019 16:38:33 -0800 (PST)
Date: Mon, 04 Feb 2019 16:38:32 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549327112; bh=+TL5zUJPZr1ubGkknBu2ud3yZyYxkOEtWa38wnydNrM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qkUp3MSRhkHqa9jtk3MoUnBpZWr7YPz9Pu1PmCyrBsfDV6eZVdpc53cD6E6R5ZyZP mDc58ZsXE8C3hOdbuip0GDwlhvryB0qQj7/hK+b2BxhVaMUSv23+RqTnatgY2B/ZwJ Li7kK28DPe5AOAjmwE38X3yxrwKbInefA5yA9ovU=
From: Igor Lubashev <>
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_5c58db08e7578_357e3fc3b6ed45b810790"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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: Tue, 05 Feb 2019 00:38:36 -0000

> allowing a peer to exhaust connection IDs to maintain linkability across migrations is an attack that I'd rather we not have.

I'd not worry about the peer. But I would, indeed, worry about a man-on-a-side exhausting your reserve of connection IDs by pretending to initiate peer migration events.  So this is a valid concern.

Of course, a violation of this MUST is indistinguishable from NAT rebinding/tethering migration and thus is not detectable by the peer.  So this MUST is really just a recommendation.  It is a fine recommendation.

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