Re: [ietf-privacy] Accurate history

S Moonesamy <sm+ietf@elandsys.com> Sat, 06 November 2021 07:41 UTC

Return-Path: <sm@elandsys.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 AC27C3A1498 for <ietf-privacy@ietfa.amsl.com>; Sat, 6 Nov 2021 00:41:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 OvG2nZrjhcSr for <ietf-privacy@ietfa.amsl.com>; Sat, 6 Nov 2021 00:41:52 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E28D3A1496 for <ietf-privacy@ietf.org>; Sat, 6 Nov 2021 00:41:52 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.97.39]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 1A67fCXP027728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 Nov 2021 00:41:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1636184484; x=1636270884; i=@elandsys.com; bh=h2dnncsQPXGk6BvFCOEKQqHx/5WRcGchpdSi2vbjKG8=; h=Date:To:From:Subject:In-Reply-To:References; b=HJ2sJf9nwYpk9ieP17ALQ5TVcYdcpGnJiUWLkRIUFpls7EsuNsP0x0OM4vMmRfcjC r0t4Y/J/WkukJaBvKFl7HAJFphFmNOoLz8x24c/oG+9a6omEFjii+tA1IP72N/h+Zy YQotcs/ENJRYtkE1Sg1yuSIWU3A3OFFUb4f3SBjM=
Message-Id: <6.2.5.6.2.20211105234600.094db288@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 06 Nov 2021 00:40:45 -0700
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>, ietf-privacy@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <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> <ef39c3fdba804c15bcaacdd1616160ea@huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/LHkBL7IO3yFr1iJ_ZFTBxwysyjY>
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: Sat, 06 Nov 2021 07:41:57 -0000

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.