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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 18 December 2023 03:44 UTC

Return-Path: <brian.e.carpenter@gmail.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 BB272C14F5FD for <architecture-discuss@ietfa.amsl.com>; Sun, 17 Dec 2023 19:44:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 kk7kVtO3k5xb for <architecture-discuss@ietfa.amsl.com>; Sun, 17 Dec 2023 19:44:16 -0800 (PST)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 7D8C3C14F5F3 for <architecture-discuss@ietf.org>; Sun, 17 Dec 2023 19:44:16 -0800 (PST)
Received: by mail-pl1-x634.google.com with SMTP id d9443c01a7336-1d3ac28ae81so7222925ad.0 for <architecture-discuss@ietf.org>; Sun, 17 Dec 2023 19:44:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702871056; x=1703475856; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=aW/Tb2x8GdEEzuFUL1i6HpnII6qA6V5F6QgoyDRDle8=; b=PqprzcgXElYcC6wBa3gnl7lyPj36DS3VMy8gbu3Ebd6ZXCzVLhwX+VD3P2GeAOKs4x xhoiY0Cxe4WrfFE00bv0LNMkuuXgvrb8JtqGtNXSTd0UNMG5m7aSjZcBRn2GIagV6n8p 7CRXqM9RbHKmDvKhhme7lvKz2+rS35yRiF3RjDsDIgUr5ltT19Uuhfe75ARXYyFMhc74 NJ3JP6zJWj205fuwO8TYtE+rPKg9xsFZeImYmz37huZPNsfxGYaNViZhsBwWIg7FOiHu 6hb0owBn7O3WhFXCZTWmvHETPWr8ywWh5IUT9v2XPfe2UwoaD5rfEqtALzFo+oARtNH4 UO+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702871056; x=1703475856; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=aW/Tb2x8GdEEzuFUL1i6HpnII6qA6V5F6QgoyDRDle8=; b=Zh6ns4ctbj/cdFIece8fQ5KUTaHJTJsNpTpInqRbGmnqoIl/jvSB8LSDO/iM2RlE9H d1nHTxCWakXnFjkYRr/JRTRY87vVr8+NTtTY3SpZJDhN6ExiODuCXgWNCqeML23JS57V Nvx925TzT3+fePbmIFHcytIXbDwS9Rc9Tl5aLtXfoQfcJiu5Eq+EdR/wndnB2i4lDYrm qoFRpq8a3zjDR6lep62xNVcdaGI2pbvTWzDvryNVFkzH/OR8V5wZKlT1LSMgrbZLVeZs okNsTjpTpRI2l+5G6CQAn+zcKZR5XL9Ok/JWnLpVIkfiAX/+JZjimGIk2rjqgoWPkSsV frqA==
X-Gm-Message-State: AOJu0YzVeVypgn8HNHqE2lwsU/+1Vj8DTG0e2izwxzm7j0c9T+fs70PD 14wINU6VuKR1AsNTAughBebP0/4zqQ57cw==
X-Google-Smtp-Source: AGHT+IEAaHoL+IB9Ha5xv2HKlrEGh/aJ2EHBKeE+VJOjkG9ApNkHoq2yAn6tiXtvHUG65dudmvhy7Q==
X-Received: by 2002:a17:902:da8b:b0:1d0:6ffd:e2b6 with SMTP id j11-20020a170902da8b00b001d06ffde2b6mr17928504plx.80.1702871055827; Sun, 17 Dec 2023 19:44:15 -0800 (PST)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id h10-20020a170902704a00b001d35223d0besm4869292plt.251.2023.12.17.19.44.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 17 Dec 2023 19:44:15 -0800 (PST)
Message-ID: <f8c307e0-51af-7636-b582-beb9d3f22213@gmail.com>
Date: Mon, 18 Dec 2023 16:44:09 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Andrew Campling <andrew.campling@419.consulting>, "iab@iab.org" <iab@iab.org>
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, S Moonesamy <sm+ietf@elandsys.com>
References: <170266952162.33107.14325064798861197261@ietfa.amsl.com> <6.2.5.6.2.20231216110256.18d0acd0@elandnews.com> <CWXP265MB5153610FBB98A7B06AF81040C290A@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CWXP265MB5153610FBB98A7B06AF81040C290A@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/NglgxZ3L7aiAz2N-FtGeloCcQJc>
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 03:44:20 -0000

Andrew,

On 18-Dec-23 13:44, Andrew Campling wrote:
> At 8:08 PM 16-12-2023, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
>> I would like to commend the members of the IAB for acknowledging the concern about societal harms.
> 
> The document states that "The IAB shares concerns about societal harms through the distribution of illegal content and criminal action on the Internet and recognizes the need to protect Internet users from such threats".  Whilst the document rules out the use of client-side scanning (a definition of which could usefully be added), it does not go on to indicate how the IAB recommends Internet users should be protected from such threats; is there a plan to produce a separate document that addresses this important issue?

The IAB has a specific role in the IETF/IRTF/RFC Editor universe, and the relevant part of its charter seems to be this:

~~~
    The IAB, both collectively
    and on an individual basis, is expected to pay attention to important
    long-term issues in the Internet, and to make sure that these issues
    are brought to the attention of the group(s) that are in a position
    to address them.  It is also expected to play a role in assuring that
    the people responsible for evolving the Internet and its technology
    are aware of the essential elements of the Internet architecture."
~~~

It seems to me that the recent IAB statement precisely fits that. It isn't the IAB's role to propose how to address the societal and legal problems of illegal content. As others have pointed out, these are not technical issues with network protocols, from which I conclude that they cannot be solved by changing or extending network protocols. And really, that is what the IAB statement boils down to: you can't stop illegal content by making the Internet less secure.

     Brian