Re: [quicwg/base-drafts] Which DCID do Handshake retransmissions use? (#3348)

Marten Seemann <> Wed, 15 January 2020 15:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0C92F1208A2 for <>; Wed, 15 Jan 2020 07:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 y1qu-Gt4L1li for <>; Wed, 15 Jan 2020 07:39:03 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 02AC6120025 for <>; Wed, 15 Jan 2020 07:39:03 -0800 (PST)
Date: Wed, 15 Jan 2020 07:39:02 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1579102742; bh=6SGjLms76Im3bL8YfVr35En49tJYBoM9qH9iextE8EA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ot8mj0893kM3kUZ2Nt8tjgkegPcf2UB+wNA+wXM1ruC1Z3mJchPhZfcx/INkY7ksW IVMIC2V6mMjEOGqqnUCwnNaoClAOU+RYuEiOr7UljLlMv9VUEcD72kQKjo2ZJ3safF 8efzBlv0zwavU2lNTcAIViWUtdcUYkYP4oehG3so=
From: Marten Seemann <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3348/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Which DCID do Handshake retransmissions use? (#3348)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e1f3216411bc_10373f90c72cd96c177342"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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: Wed, 15 Jan 2020 15:39:12 -0000

> * a) let the receiver of NCID to send Handshake packets using the new CIDs
> * b) require (or recommend) receiver of NCID to continue using the original DCID until the handshake is confirmed
> * c) require (or recommend) the sender to withhold the emission NCID (with a non-zero RTP) to until it sees an ACK for handshake confirmation

@kazuho There's a fourth option:
* d) require that the sender withholds the NCID frame until it has confirmed the handshake.

As soon as an endpoint confirms the handshake, it drops the Handshake keys (I'm assuming #3145 here). As a result, the endpoint obviously doesn't care about Handshake packets any longer (and especially doesn't care which DCID was used to send the packet).
Therefore, there's no problem if the receiver of the NCID frame immediately retires the connection ID used during the handshake, even if the the NCID and the HANDSHAKE_DONE frame were reordered.

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