Re: [quicwg/base-drafts] Authenticating connection IDs (#3439)

David Schinazi <> Thu, 05 March 2020 18:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DAA6A3A093B for <>; Thu, 5 Mar 2020 10:37:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Status: No, score=-3.098 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 UJ6gEY714ZV1 for <>; Thu, 5 Mar 2020 10:37:29 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 634453A091C for <>; Thu, 5 Mar 2020 10:37:29 -0800 (PST)
Date: Thu, 05 Mar 2020 10:37:28 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1583433448; bh=X9M1Bd+wfsRvEBMX7BbeIxyugU8vHt9HeRl9EPNQv7M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=veXeY+ZQJN/4VCuGxAIgk82W8fJbStZJSf+kMiWb5qk5ZvhK/EcLV0sjdY+xPzhzw KRhJ/hwxp/cNBm0BkKqW3Yqrv6vxH+0MiKKaYyV+yGchS/aszumM/GG6oefmQSpokP +GtCmvcuvjp451SlwzLoZvRN1lQQpDWnztZ1vC0c=
From: David Schinazi <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3439/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Authenticating connection IDs (#3439)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e6146e86a96f_34993fe747ecd95c128998"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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: Thu, 05 Mar 2020 18:37:31 -0000

Speaking in terms of design principles, [the triple handshake attack]( has taught us that pretty much anything that doesn't land in the key schedule can be abused by an attacker that makes each endpoint think it has a different value. Specifically to QUIC, everything going on in the CRYPTO stream lands in the transcript thanks to TLS 1.3, but there are QUIC-specific fields that don't: in particular the connection IDs and version from long headers. To protect the version, we have [draft-ietf-quic-version-negotiation](, but we don't have anything for the Source CID. Therefore I'm supportive of adding a transport parameter that makes sure that it lands in the transcript.

On the other hand, requiring the server to always replace the client-chosen initial destination CID does not provide any security benefits in and of itself. There's nothing preventing the server from determining its replacement CID deterministically from the client-chosen one, for example.

This change would be non-trivial for the Google deployment because, unlike migration, it needs to happen synchronously when establishing the connection. If your communication with load balancers is asynchronous, you can delay sending NEW_CONNECTION_ID frames for migration until you've received enough connection IDs from your load balancer, but delaying the response to a client's initial has a performance cost that we're not willing to pay.

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