Re: [arch-d] IAB Statement on Encryption and Mandatory Client-side Scanning of Content

Wes Hardaker <wjhns1@hardakers.net> Mon, 18 December 2023 20:51 UTC

Return-Path: <wjhns1@hardakers.net>
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 2503EC14E515 for <architecture-discuss@ietfa.amsl.com>; Mon, 18 Dec 2023 12:51:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hardakers.net
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 qP0v0DvNZE3w for <architecture-discuss@ietfa.amsl.com>; Mon, 18 Dec 2023 12:50:59 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6033AC14CF13 for <architecture-discuss@ietf.org>; Mon, 18 Dec 2023 12:50:59 -0800 (PST)
Received: from localhost (unknown [10.0.0.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id D57C125A9C; Mon, 18 Dec 2023 12:50:58 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net D57C125A9C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1702932658; bh=Azx+kdBRH3aV2SShEGWFShpexs4Wapf3Rqit7/+qgzA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=EjMcNA4+kBZCBOTKoFVR4g8IcM+la/3ytzAadkm4apqyZg+R1RDEXjZmKeBWUw0hc EDpBv8BrsrMO/zPc5U4bCklXrmHCJ0Hvy3tkAjUhF1SgEyHL2oCkSSbyQZnNO4UuWv 0+UFpJBETNuJxb4BypdLXRTdqOLsK2b/9+wRYT5k=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: 'Mallory Knodel' <mknodel=40cdt.org@dmarc.ietf.org>, 'Andrew Campling' <andrew.campling@419.consulting>, iab@iab.org, architecture-discuss@ietf.org
In-Reply-To: <02ae01da31f2$80580630$81081290$@olddog.co.uk> (Adrian Farrel's message of "Mon, 18 Dec 2023 20:40:55 -0000")
References: <170266952162.33107.14325064798861197261@ietfa.amsl.com> <6.2.5.6.2.20231216110256.18d0acd0@elandnews.com> <CWXP265MB5153610FBB98A7B06AF81040C290A@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM> <CAKr6gn2Hf4N+DgKHKyO+i3T3OJyYRBJhH1AdQf-uXZ0xKmJ4Eg@mail.gmail.com> <CWXP265MB515381523714FF99524410CFC290A@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM> <790032a6-24f6-60d1-fb60-4b44bd447bde@gmail.com> <fadd9250-4b31-4bf5-aa76-4f37d24fd650@cdt.org> <02ae01da31f2$80580630$81081290$@olddog.co.uk>
Date: Mon, 18 Dec 2023 12:50:58 -0800
Message-ID: <yblcyv3grpp.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/b5IUfNzRgvP1eveQ9-RRle8i0II>
Subject: Re: [arch-d] IAB Statement on Encryption and Mandatory Client-side Scanning of Content
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: Mon, 18 Dec 2023 20:51:04 -0000

"Adrian Farrel" <adrian@olddog.co.uk> writes:

> It might be helpful to provide a pointer to a definition that you find
> helpful and clear.

I recommend that interested parties read the proposed policies
themselves and come to conclusions about what is being proposed (in each
of the regions) and what the risks are.  They are not long, and the
language is not super complex (mostly).  I know that my reading of them
(and a layer's reading of them) differs from other people's reading of
them about what the impact and requirements will be.

-- 
Wes Hardaker
<no hats>