Re: [quicwg/base-drafts] The method of identifying "the same server" (#3155)
Igor Lubashev <notifications@github.com> Mon, 04 November 2019 12:01 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA10C1200BA for <quic-issues@ietfa.amsl.com>; Mon, 4 Nov 2019 04:01:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9vrd5_IcFtas for <quic-issues@ietfa.amsl.com>; Mon, 4 Nov 2019 04:01:00 -0800 (PST)
Received: from out-17.smtp.github.com (out-17.smtp.github.com [192.30.252.200]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5459D12004C for <quic-issues@ietf.org>; Mon, 4 Nov 2019 04:01:00 -0800 (PST)
Received: from github-lowworker-ca5950c.va3-iad.github.net (github-lowworker-ca5950c.va3-iad.github.net [10.48.17.57]) by smtp.github.com (Postfix) with ESMTP id 75E846E008E for <quic-issues@ietf.org>; Mon, 4 Nov 2019 04:00:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1572868859; bh=mBdR9R7DMz9B6gfn2TrKjeG5uLANskIPGDjq7PzMztY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eA+/wfuIh4Mo5ipWCzcUlMUYvPf+ndHF7T0XIAKuzLY0TqKzhgjvdduM5x8yF4ui/ lybVZ1jFVi65c57SCmaYvYdcInX42QiAftwyuMXMt9RxAuZ5Us4ua6tKbeAk07ajdp DlnRDslEF0O+FnJejJTMTQq6qi8k6Lp/aa/MufRI=
Date: Mon, 04 Nov 2019 04:00:59 -0800
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5K44AZLQBLRQNENJV3ZVCXXEVBNHHB5FITQM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3155/549323704@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3155@github.com>
References: <quicwg/base-drafts/issues/3155@github.com>
Subject: Re: [quicwg/base-drafts] The method of identifying "the same server" (#3155)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc012fb67966_22d23f9e5d2cd964126068"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8QLKmTKXhfO9j24SRNzG4fGsAQY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 12:01:02 -0000
@kazuho I did see this but am confused where the risk is. If a party can see all traffic going to a specific IP, is the concern that it is giving them some extra information when there are multiple clients behind a NAT? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/3155#issuecomment-549323704
- [quicwg/base-drafts] The method of identifying "t… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Nick Harper
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Nick Harper
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Martin Thomson
- Re: [quicwg/base-drafts] The method of identifyin… MikkelFJ
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Igor Lubashev
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Igor Lubashev
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Igor Lubashev
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Igor Lubashev
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Igor Lubashev
- Re: [quicwg/base-drafts] The method of identifyin… Kazuho Oku
- Re: [quicwg/base-drafts] The method of identifyin… Martin Thomson
- Re: [quicwg/base-drafts] The method of identifyin… MikkelFJ
- Re: [quicwg/base-drafts] The method of identifyin… Igor Lubashev
- Re: [quicwg/base-drafts] The method of identifyin… Martin Thomson