Re: [quicwg/base-drafts] Connection ID Length changes (#2473)

Kazuho Oku <> Sun, 17 February 2019 07:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6434E128B01 for <>; Sat, 16 Feb 2019 23:38:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Status: No, score=-8.001 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_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 zZErCr9VZLe2 for <>; Sat, 16 Feb 2019 23:38:10 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 88C93127AC2 for <>; Sat, 16 Feb 2019 23:38:10 -0800 (PST)
Date: Sat, 16 Feb 2019 23:38:08 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1550389088; bh=3k6zzN3H2fmFb4Xa3GlzX3+AG6TEJDktQy0D96WB5lQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XBvU/LSe5rJC8i+0Pv8gq1NpJEN1CZcz/iPes2C44h/MsNVMtCxbtm8TSnArnEQ4r V6ovaVatLksDuDKTmw60zeTLzFieD34XYYta+7rs1xBhs6Z/+mKg12sCey8DH5FLIY /xRijINa2qv7yrke45hMnQHvnNTGKKrue1vHNX8w=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2473/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Connection ID Length changes (#2473)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c690f60c954b_76ce3ff61eed45b421365b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: Sun, 17 Feb 2019 07:38:12 -0000

@martinduke IIUC, generally speaking, trial decryption becomes inevitable for a client when it coalesces multiple connections that uses the same server 2-tuple onto a single socket.

In the approach you describe, the client is not coalescing multiple connections in such a way on a single socket when it initiates the connection, because it is initially using zero-length CID. But it sounds like that the client will be using the socket in such a way on a socket it decides to migrate.

What I do not see is the rationale behind such a design.

If the client's preference is to minimize the network bandwidth (by using zero-length CIDs), shouldn't it use zero-length CIDs for subsequent paths that it migrates the connection to? That's possible, as long as it does not coalesce multiple connections that share the same server 2-tuple onto a single socket. The simplest way of doing that is to use a dedicated socket for each connection.

Or if the client's preference is to minimize the number of sockets it maintains, shouldn't it be always using non-zero-length CIDs from when it initiates a new connection?

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