Re: [arch-d] Possible IAB Adoption of draft-kpw-iab-privacy-partitioning

Vittorio Bertola <vittorio.bertola@open-xchange.com> Wed, 23 November 2022 11:10 UTC

Return-Path: <vittorio.bertola@open-xchange.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65388C14CE4C for <architecture-discuss@ietfa.amsl.com>; Wed, 23 Nov 2022 03:10:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h4MOdmiVEscH for <architecture-discuss@ietfa.amsl.com>; Wed, 23 Nov 2022 03:10:02 -0800 (PST)
Received: from mx3.open-xchange.com (mx3.open-xchange.com [87.191.57.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AF59C14CE3B for <architecture-discuss@ietf.org>; Wed, 23 Nov 2022 03:10:01 -0800 (PST)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id A934F6A0DD; Wed, 23 Nov 2022 12:09:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1669201799; bh=8ld3HB+CLtIHXgEWfmx10T5Hwy8Bdb3TvuT6M86YLj0=; h=Date:From:To:In-Reply-To:References:Subject:From; b=UHCBphydSUqDb/rHiIDzJPpBj4XlZisdYlV4zmuIjIBFQ89MdadWwi9LACzB3m+A7 gsfmKy0VGWDQXHbWTHk69Y9E41oerzIIQEDsRA2Vd0Dq3R7Hol3AsiAuB16qdYF1KX PPwYGqVzHZLWAaEdnszWk0Ai+W5jUNxdOruXBV47ckqBMLjpdynvLJNolB9e0ilBZh cIn+shQMp7KPIGnU2qgo7Ui7YGBtpdDv037/lH9gULMieB5qlLa7Uk9ySMTXfJ2GbT 2mLg5FZVOEv3J8vXIVQALLd3W74NLxDe85n9SGO4aOY+Occ080RXgWDhai0XpXfotS +kA0oOOLcKABA==
Received: from appsuite-gw2.open-xchange.com ([10.20.28.82]) by imap.open-xchange.com with ESMTPSA id TqPRJ4f/fWORmAMA3c6Kzw (envelope-from <vittorio.bertola@open-xchange.com>); Wed, 23 Nov 2022 12:09:59 +0100
Date: Wed, 23 Nov 2022 12:09:59 +0100
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Martin Thomson <mt@lowentropy.net>, architecture-discuss@ietf.org
Message-ID: <969393466.92459.1669201799615@appsuite-gw2.open-xchange.com>
In-Reply-To: <6c471c16-2196-4e08-84a9-cc576ff1a66a@betaapp.fastmail.com>
References: <166862348898.27211.16338265887689375983@ietfa.amsl.com> <797875861.71155.1668701339665@appsuite-gw1.open-xchange.com> <6c471c16-2196-4e08-84a9-cc576ff1a66a@betaapp.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev30
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/CPd977gB__TjqQSzolvYbsBhutU>
Subject: Re: [arch-d] Possible IAB Adoption of draft-kpw-iab-privacy-partitioning
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2022 11:10:06 -0000


> Il 18/11/2022 05:35 CET Martin Thomson <mt@lowentropy.net> ha scritto:
> 
> However, by constructing - and then vigorously attacking - what is only one of many hypothetical outcomes, you don't do your cause any favours.  Unless your cause is disrupting this work, I guess, but why would you spend so much time writing emails if that were the case?

The outcome in which the user has no control over the choice of the intermediaries, which is entirely under the control of the device maker, is not "one of many hypothetical outcomes" - it is how the current main deployment of the oblivious transport model works, and unless I miss something, there is no effort in sight to change this.

> If I might suggest, a more constructive approach might be to look at those systemic problems and building consensus around improved solutions.

I think that there was a clear proposal in my message: don't just talk of doing things "for the end-users" but actually put end-users in control. The document should state very clearly that the net effect of these architectures on user privacy will be positive or negative depending on who is in control of the choice of where the traffic goes. Any protocol designs should make sure that users have a way to discover services and pick them for use within their applications. Indeed, this may also require regulation or antitrust enforcement for companies that will still try to use this as another self-preferencing mechanism, but the IAB should take a clear stance on how centralized it would like this kind of services to be.

-- 
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy