Re: [quicwg/base-drafts] The method of identifying "the same server" (#3155)

Igor Lubashev <> Mon, 04 November 2019 13:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CA715120274 for <>; Mon, 4 Nov 2019 05:28:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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, 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 v2PcF1f6gO6V for <>; Mon, 4 Nov 2019 05:27:59 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 08C18120144 for <>; Mon, 4 Nov 2019 05:27:59 -0800 (PST)
Date: Mon, 04 Nov 2019 05:27:57 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572874078; bh=FfrZF28tuScFvd4DqTCvyZzp8X4rU+dK6pIIJaHBHiU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ml9LvMo9vKgQYr7Bgu6/4hfy6RtxKVqb1XJQDA9tdbJOV1CYaeooX7S34vuK6j/Hx bzjpF60tbDSYR3ebGxNFBtrUL1PpLv6KVYl6znaFzC+cB4Pfoy8sgD0zuzKZu+D6x5 Jgfp22xj/Qc9znA0hat60OSBrxi/n9CJ6U+214h0=
From: Igor Lubashev <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3155/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] The method of identifying "the same server" (#3155)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc0275dea4e6_38463fcae40cd96c2682de"; 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, 04 Nov 2019 13:28:01 -0000

@kazuho So why is the answer to my question of whether the scheme above gives out extra information only in case of multiple users behind a NAT: no?

If there is only a single user behind an IP, a party that can observe all traffic to load balancer "a" can know who is connecting to "c" and "b" just by matching on the src ip and seeing that they are the same.

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