Re: [quicwg/base-drafts] Client connection IDs are broken (#2844)

Igor Lubashev <> Mon, 29 July 2019 17:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B2990120146 for <>; Mon, 29 Jul 2019 10:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Status: No, score=-6.383 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 q7R5ae5xSV59 for <>; Mon, 29 Jul 2019 10:56:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DA0E71203D5 for <>; Mon, 29 Jul 2019 10:56:15 -0700 (PDT)
Date: Mon, 29 Jul 2019 10:56:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1564422975; bh=Oxr1pzeROwqa9+KToV64V3xYbDyENe7BTcr5h/Pd9Tw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lUY4WZ7Z642RAzMdbMETTOLuiYqgY84wttCORFimhZPGmpqNN2jTEng0F5s7x3Ynh F+SSw/5HrszcVPImQHopj1kFhYpASVTcrrrE3+1CrQNzOeA/EPog4CYHZm6a1eOZ// 6adcvJwYryj+5mjo0o35uVOLLQbwv3H7s8DZAYSc=
From: Igor Lubashev <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2844/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Client connection IDs are broken (#2844)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d3f333eea44f_aa83faa630cd9683911d0"; 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: Mon, 29 Jul 2019 17:56:21 -0000


> But because the server cannot tell if the packet were to be identified by the 4-tuple or the CID (because you no longer have state!), the server needs to send two stateless reset packets, one generated using the 4-tuple as the key, and the other generated using the CID.

This is a good point that Stateless Reset must also be considered.  In case that the server can identify a certain population of clients ( as not needing migration, it can also identify which clients to send what kind of Stateless Reset.

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