Re: [ietf-privacy] Accurate history
Vasilenko Eduard <vasilenko.eduard@huawei.com> Sun, 07 November 2021 10:22 UTC
Return-Path: <vasilenko.eduard@huawei.com>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7533A11FF for <ietf-privacy@ietfa.amsl.com>; Sun, 7 Nov 2021 02:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 p25H-0bV8CZm for <ietf-privacy@ietfa.amsl.com>; Sun, 7 Nov 2021 02:22:18 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A6103A11FB for <ietf-privacy@ietf.org>; Sun, 7 Nov 2021 02:22:18 -0800 (PST)
Received: from fraeml744-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Hn9FD3nD2z67NNV for <ietf-privacy@ietf.org>; Sun, 7 Nov 2021 18:18:40 +0800 (CST)
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by fraeml744-chm.china.huawei.com (10.206.15.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Sun, 7 Nov 2021 11:22:10 +0100
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by mscpeml500001.china.huawei.com (7.188.26.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Sun, 7 Nov 2021 13:22:09 +0300
Received: from mscpeml500001.china.huawei.com ([7.188.26.142]) by mscpeml500001.china.huawei.com ([7.188.26.142]) with mapi id 15.01.2308.015; Sun, 7 Nov 2021 13:22:09 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: S Moonesamy <sm+ietf@elandsys.com>, "ietf-privacy@ietf.org" <ietf-privacy@ietf.org>
Thread-Topic: Accurate history
Thread-Index: AQHX0uHCPrC+Wp5o/k2YGGEyqEjaX6v32YVw
Date: Sun, 07 Nov 2021 10:22:09 +0000
Message-ID: <daefa555bccc4eb4b6e61e51d85bde3d@huawei.com>
References: <8F4B97EA-665F-4A59-B99D-791B4AB9F2F7@yahoo.co.uk> <c3e9fe1b-8e48-a364-9e25-4084dac70889@meetinghouse.net> <3a6bf8ad-5492-0942-a451-6317e8a93705@network-heretics.com> <3e685576-a230-a7c4-f371-d66a55aa820d@necom830.hpcl.titech.ac.jp> <7a087707-499f-e3bf-8701-1a58930a8a22@meetinghouse.net> <4ec32d7a-a17b-635b-91bc-4152313d6800@necom830.hpcl.titech.ac.jp> <885e62bf-7d6a-4501-a48a-e7c2cbf20382@joelhalpern.com> <e59adb61-a55c-7f5f-a60a-40bf186c139d@necom830.hpcl.titech.ac.jp> <CAC8QAceMSrfkqGTYcMNr3JargO3gxJqTaEyf02LGHd-KVeUDHw@mail.gmail.com> <6286da3e-2beb-9556-089a-2e1951573b1e@gmail.com> <59c80b60-438f-b10f-ad61-ba839f6e4f95@necom830.hpcl.titech.ac.jp> <e834916e85ea47ef94fce07c23928d2b@huawei.com> <37b299c8-e821-07e5-6240-68fb9d1ca137@gmail.com> <23b450fb11eb4a51bb4ee837b5c52657@huawei.com> <a805b50d-3ccd-dd2a-4931-6c6dc9a8ede3@necom830.hpcl.titech.ac.jp> <CAC8QAceY1gtK5v3WGMd4OB0z826jDiDDw_g1LbjWef7MKTnrcg@mail.gmail.com> <eae026b8fc7a42eeb2210dcb156d5f56@huawei.com> <8007ec69-628a-448a-28f3-090b6fdab999@network-heretics.com> <ef39c3fdba804c15bcaacdd1616160ea@huawei.com> <6.2.5.6.2.20211105234600.094db288@elandnews.com>
In-Reply-To: <6.2.5.6.2.20211105234600.094db288@elandnews.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.200.191]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/PNtxgQxl8Q2_PJwPvMVVpEuts9Q>
Subject: Re: [ietf-privacy] Accurate history
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-privacy/>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Nov 2021 10:22:23 -0000
Hi S. Moonesamy, The context was about IPv6 addressing only, not the privacy on the general scope. The second half of IPv6 address bits (64 from 128) are used only for privacy now. RFC 8981. IPv6 is 64-bit addressing architecture because of this, not 128 as many believe. The host generates different pseudo-random IIDs (64-bits) and uses them to create many temporary addresses for different sessions. Keith Moore mentioned that it is privacy. Hence, the good wastage of (2^64-1)/2^64 of IPv6 address space. I was arguing that it is fake privacy. Hence, not a justification to waste so huge address space. Eduard -----Original Message----- From: S Moonesamy [mailto:sm+ietf@elandsys.com] Sent: Saturday, November 6, 2021 10:41 AM To: Vasilenko Eduard <vasilenko.eduard@huawei.com>; ietf-privacy@ietf.org Subject: RE: Accurate history Hi Vasilenko, I moved the thread to another mailing list. At 12:55 AM 05-11-2021, Vasilenko Eduard wrote: >Privacy is a myth. > >OTTs deliver 70% of traffic. They could correlate users by 100 >parameters (including your browser window size). >Just changing IID would not impact their correlation. Not at all. > >Your carrier has to know all your sessions for Lawful Intercept. > >Whom you are trying to mislead by IID changes? > >It just creates a heavy load on logs collection for troubleshooting, >forensic, and legal intercept. The point which you made correlation is correct. Session-level information is sometimes collected for network management purposes. An external party can request access to it for investigating, for example, a crime [1]. I doubt that the external party would use information generated through correlation (using, for example, browser information) in their investigation. IIDs, as designed, did not address privacy concerns. It could be because the assumptions were incorrect. As a response to your comment about privacy, I noticed that some participants changed their identification information over the last few years. It may have been influenced about concerns about privacy. Are you trying to say that the IETF participants' expectation of privacy does not match reality? Regards, S. Moonesamy 1. It depends on the jurisdiction.
- Re: [ietf-privacy] Accurate history S Moonesamy
- Re: [ietf-privacy] Accurate history Vasilenko Eduard
- Re: [ietf-privacy] Accurate history S Moonesamy
- Re: [ietf-privacy] Accurate history Vasilenko Eduard