IETF Logo Mail Archive

RE: Accurate history [Re: "professional" in an IETF context]

Vasilenko Eduard <vasilenko.eduard@huawei.com> Fri, 05 November 2021 07:55 UTC

Return-Path: <vasilenko.eduard@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10E473A0D66 for <ietf@ietfa.amsl.com>; Fri, 5 Nov 2021 00:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 XIba0Ol1GSDP for <ietf@ietfa.amsl.com>; Fri, 5 Nov 2021 00:55:23 -0700 (PDT)
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 969583A0D63 for <ietf@ietf.org>; Fri, 5 Nov 2021 00:55:23 -0700 (PDT)
Received: from fraeml709-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Hlt3T2vvzz67Pf9 for <ietf@ietf.org>; Fri, 5 Nov 2021 15:50:45 +0800 (CST)
Received: from mscpeml100001.china.huawei.com (7.188.26.227) by fraeml709-chm.china.huawei.com (10.206.15.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Fri, 5 Nov 2021 08:55:20 +0100
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by mscpeml100001.china.huawei.com (7.188.26.227) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Fri, 5 Nov 2021 10:55:19 +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; Fri, 5 Nov 2021 10:55:19 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Accurate history [Re: "professional" in an IETF context]
Thread-Topic: Accurate history [Re: "professional" in an IETF context]
Thread-Index: AQHX0CVovVGa7jvYXUCxunxuZ8u5Aqvxc5hQgAHV/ACAAA76AIAAN+JA///WFgCAASwFYA==
Date: Fri, 05 Nov 2021 07:55:19 +0000
Message-ID: <ef39c3fdba804c15bcaacdd1616160ea@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>
In-Reply-To: <8007ec69-628a-448a-28f3-090b6fdab999@network-heretics.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.207.155]
Content-Type: multipart/alternative; boundary="_000_ef39c3fdba804c15bcaacdd1616160eahuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Gfrsa0aLLTA0nt4XIlfRYTj6ztM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Nov 2021 07:55:28 -0000

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.

Eduard
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Keith Moore
Sent: Thursday, November 4, 2021 7:54 PM
To: ietf@ietf.org
Subject: Re: Accurate history [Re: "professional" in an IETF context]


On 11/4/21 12:26 PM, Vasilenko Eduard wrote:
Interface ID is still not used for something usefull, but ND creates a lot of problems.
It is still possible to return it to MAC and cancel the biggest part of the ND that creates a lot of problems.

For privacy reasons alone, I'd say that's a non-starter.

Keith

v2.23.0 | Report a Bug | By Email