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

S Moonesamy <sm+ietf@elandsys.com> Sun, 17 December 2023 01:05 UTC

Return-Path: <sm@elandsys.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 6B9B7C14F5F8 for <architecture-discuss@ietfa.amsl.com>; Sat, 16 Dec 2023 17:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.704
X-Spam-Level:
X-Spam-Status: No, score=-1.704 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QwaAp2EhmeF0 for <architecture-discuss@ietfa.amsl.com>; Sat, 16 Dec 2023 17:05:45 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 47648C14F5F6 for <architecture-discuss@ietf.org>; Sat, 16 Dec 2023 17:05:45 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.129.76]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 3BH15RFS016615 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Dec 2023 17:05:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1702775139; x=1702861539; i=@elandsys.com; bh=WQLSFWGq7lzVUPPJrU9Gn1rpMhilnDKudI2VEmJApdc=; h=Date:To:From:Subject:In-Reply-To:References; b=oJZz9DPE/0Sy9xjg4K+VOe7aLJgtVLjxNf9NrzNqjWv6p6wODMTXKN00SJOptvKUH BpeDis3tDmyTriIbUp2z+aCOzaZdZnYf38x7Dkhyj/bpP3xVybmJqbZeg8gxl1Eyy4 C6J8s82Clm5shLe8wb+u4iksyTkL147oFd2xs0C8=
Message-Id: <6.2.5.6.2.20231216162324.10bb7800@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 16 Dec 2023 17:00:44 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, architecture-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <52e423e7-5787-d56a-b197-61fabe623505@gmail.com>
References: <170266952162.33107.14325064798861197261@ietfa.amsl.com> <6.2.5.6.2.20231216110256.18d0acd0@elandnews.com> <52e423e7-5787-d56a-b197-61fabe623505@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/2FHxZylOKmOgPrtf7A6WwY3ljLk>
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: Sun, 17 Dec 2023 01:05:49 -0000

Hi Brian,
At 02:41 PM 16-12-2023, Brian E Carpenter wrote:
>That seems fairly clear to me. If open-source software does not allow,
>or actively prevents, mandatory scanning it would be illegal to use it.

https://www.pinsentmasons.com/out-law/guides/guide-digital-services-act-for-online-intermediaries 
states that the law affects "platforms" with a monthly active 
recipients which is equal to 45 million or higher.  If I am not 
mistaken, the other details (please see 
https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022R2065&from=EN 
) do not seem to target open-source software as such.

>In general, it's clear that the argument against standardising in-host
>scanning is almost identical to the argument against standardising
>wiretapping (i.e. RFC 2804). However, it's not a protocol issue, so
>the IETF would never standardise it anyway. Any scanning that happens
>before material enters the host is already covered by RFC 2804. Whether
>one agrees with the IAB or not (I do), IETF policy is already set.

The topic reminds me of OPES instead of wiretapping.  It sounds more 
like a matter for civil society.  There are civil society 
organizations which do advocacy on such matters.

Regards,
S. Moonesamy