Re: [arch-d] IAB Statement on Encryption and Mandatory Client-side Scanning of Content
Phillip Hallam-Baker <phill@hallambaker.com> Sun, 17 December 2023 02:36 UTC
Return-Path: <hallam@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 F2640C14F693 for <architecture-discuss@ietfa.amsl.com>; Sat, 16 Dec 2023 18:36:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.403
X-Spam-Level:
X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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
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 UUbdw7SW0fIY for <architecture-discuss@ietfa.amsl.com>; Sat, 16 Dec 2023 18:36:16 -0800 (PST)
Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) (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 F0510C14F68A for <architecture-discuss@ietf.org>; Sat, 16 Dec 2023 18:36:11 -0800 (PST)
Received: by mail-ot1-f52.google.com with SMTP id 46e09a7af769-6d9daa5207eso1603648a34.0 for <architecture-discuss@ietf.org>; Sat, 16 Dec 2023 18:36:11 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702780571; x=1703385371; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=aX9N3aNQT4w6bugqrvAN3ZaUq4igvfFbDEYxlsPCD1c=; b=rVQe/303HQXceWxq9Ta7C1kQm6WSyn3GaUJAvwzTznAl381UeM0m14FtiBekMJnkPU LmCGpAZGZfJsoGyKUzmJBT3Bv29+lBhupKqUQZCH+q9cl+TttIIBqXy2vs8qYdRy1drU 7V1y/gXK3FhrzFiUpHgjW7p1mqCRfIN8L4WaunWrVhBaQ8nRAjkIVcJ4eapFiMru7Vdu 4tC5TXozhj4pTgR2yAx2snuHYNixDNuEThmHN1Dbt8zrshNhBcsNfb9rEZvMkmH35WZe pOo6ZUMzG4UQWF/4F/hLKh2Z5jK+Vat3MAjx7erWCeJAnGIzD7TOJ5zDvU7DX9C1m2dz Wfqw==
X-Gm-Message-State: AOJu0YynKLtHYrbHhVSf0a0qE9JKr1HZoKv78FXR9WdpOJ2sBSG0P5Tr iTkzb9BrgHKKxVSqL/o5FvvIt1yH3iYmFm+pTc8=
X-Google-Smtp-Source: AGHT+IFfJTOmTzprksZe+VPuS+lKPFTxW3ECqi4/dRggu1chqcTYAlVv1OGOrxazpz4xe+wFnz2nxxqsi+DQkk3pqgc=
X-Received: by 2002:a9d:6b0c:0:b0:6d9:afd2:b8d0 with SMTP id g12-20020a9d6b0c000000b006d9afd2b8d0mr13926673otp.75.1702780571002; Sat, 16 Dec 2023 18:36:11 -0800 (PST)
MIME-Version: 1.0
References: <170266952162.33107.14325064798861197261@ietfa.amsl.com> <6.2.5.6.2.20231216110256.18d0acd0@elandnews.com> <52e423e7-5787-d56a-b197-61fabe623505@gmail.com> <6.2.5.6.2.20231216162324.10bb7800@elandnews.com>
In-Reply-To: <6.2.5.6.2.20231216162324.10bb7800@elandnews.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sat, 16 Dec 2023 21:35:59 -0500
Message-ID: <CAMm+LwjDWAt7J997=0Eg=ejSJTyx26qsHJBu4D+A+i3xWggQvQ@mail.gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="00000000000010ad4d060cab7fce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/k2EC8HG8jEmjgVznLSdWPtdVxKQ>
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 02:36:21 -0000
The history of the cryptowars is littered with bad faith proposals. There is a familiar two-step. First a proposal that has no practical effect is made to establish the precedent and once the principle has been conceded, a second proposal is made with effects that are very real. On Sat, Dec 16, 2023 at 8:05 PM S Moonesamy <sm+ietf@elandsys.com> wrote: > 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 > > _______________________________________________ > Architecture-discuss mailing list > Architecture-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/architecture-discuss >
- Re: [arch-d] IAB Statement on Encryption and Mand… S Moonesamy
- Re: [arch-d] IAB Statement on Encryption and Mand… Brian E Carpenter
- Re: [arch-d] IAB Statement on Encryption and Mand… S Moonesamy
- Re: [arch-d] IAB Statement on Encryption and Mand… S Moonesamy
- Re: [arch-d] IAB Statement on Encryption and Mand… George Michaelson
- Re: [arch-d] IAB Statement on Encryption and Mand… Brian E Carpenter
- Re: [arch-d] IAB Statement on Encryption and Mand… Vittorio Bertola
- Re: [arch-d] IAB Statement on Encryption and Mand… Christian Huitema
- Re: [arch-d] IAB Statement on Encryption and Mand… Eric Rescorla
- Re: [arch-d] IAB Statement on Encryption and Mand… Andrew Campling
- Re: [arch-d] IAB Statement on Encryption and Mand… Andrew Campling
- Re: [arch-d] IAB Statement on Encryption and Mand… S Moonesamy
- Re: [arch-d] IAB Statement on Encryption and Mand… Brian E Carpenter
- Re: [arch-d] IAB Statement on Encryption and Mand… Wes Hardaker
- Re: [arch-d] IAB Statement on Encryption and Mand… Hesham ElBakoury
- Re: [arch-d] IAB Statement on Encryption and Mand… S Moonesamy
- Re: [arch-d] IAB Statement on Encryption and Mand… S Moonesamy
- Re: [arch-d] IAB Statement on Encryption and Mand… Eliot Lear
- Re: [arch-d] IAB Statement on Encryption and Mand… Eric Rescorla
- [arch-d] Off topic [was: IAB Statement on Encrypt… Brian E Carpenter
- Re: [arch-d] IAB Statement on Encryption and Mand… Phillip Hallam-Baker
- Re: [arch-d] IAB Statement on Encryption and Mand… Eric Rescorla
- Re: [arch-d] IAB Statement on Encryption and Mand… Arnaud Taddei
- Re: [arch-d] Off topic [was: IAB Statement on Enc… Phillip Hallam-Baker
- Re: [arch-d] IAB Statement on Encryption and Mand… Phillip Hallam-Baker
- Re: [arch-d] [EXTERNAL] Re: IAB Statement on Encr… Tommy Jensen
- Re: [arch-d] Off topic [was: IAB Statement on Enc… Phillip Hallam-Baker
- Re: [arch-d] IAB Statement on Encryption and Mand… Eric Rescorla
- Re: [arch-d] IAB Statement on Encryption and Mand… Phillip Hallam-Baker
- Re: [arch-d] IAB Statement on Encryption and Mand… Phillip Hallam-Baker
- Re: [arch-d] IAB Statement on Encryption and Mand… Mallory Knodel
- Re: [arch-d] IAB Statement on Encryption and Mand… Mallory Knodel
- Re: [arch-d] IAB Statement on Encryption and Mand… Phillip Hallam-Baker
- Re: [arch-d] IAB Statement on Encryption and Mand… Mallory Knodel
- Re: [arch-d] IAB Statement on Encryption and Mand… Adrian Farrel
- Re: [arch-d] IAB Statement on Encryption and Mand… Mallory Knodel
- Re: [arch-d] Off topic [was: IAB Statement on Enc… Hesham ElBakoury
- Re: [arch-d] Off topic [was: IAB Statement on Enc… Brian E Carpenter
- Re: [arch-d] IAB Statement on Encryption and Mand… Vittorio Bertola
- Re: [arch-d] IAB Statement on Encryption and Mand… John Levine
- Re: [arch-d] IAB Statement on Encryption and Mand… Mirja Kuehlewind (IETF)
- Re: [arch-d] [IAB] IAB Statement on Encryption an… Mirja Kuehlewind (IETF)