Re: [quicwg/base-drafts] Discuss requirement that connection IDs not be correlatable (#2084)

martinduke <> Tue, 23 July 2019 20:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B2900120932 for <>; Tue, 23 Jul 2019 13:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 bTH6H9Sff9aA for <>; Tue, 23 Jul 2019 13:15:07 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 37B8712036D for <>; Tue, 23 Jul 2019 13:15:07 -0700 (PDT)
Date: Tue, 23 Jul 2019 13:15:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1563912906; bh=RBLngm6+ksSzP6lRFbU9teau0uhnmAwo4KgRmmaHGVw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2UG7u8+6hn9V0MGDonkSvcjulUZfqxDpaFEC/8pJx4LyY9ZPjlZwwKI4PbBEqWCQ3 WwcrGzX+ST1F90pCtU1M0hqcQFo5HuWVubYYS4A2dMAmtozOkVBgDulORxBBQaZxae o0L5BX5LdnpQvELSMjlWYsUYCzcnm02L89MPBvJ8=
From: martinduke <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2084/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Discuss requirement that connection IDs not be correlatable (#2084)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d376aca45a09_b0a3fe115acd95c91606e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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, 23 Jul 2019 20:15:18 -0000

I believe this is an editorial issue, not design. We all know what we mean: it can encode information by use for itself and trusted intermediaries, but definitely is not correlatable. I agree that MUST is a little tricky unless we are mandating either true encryption or true randomness, which is a discussion I was hoping to defer until QUIC-LB is adopted.

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