Re: [arch-d] IAB Statement on Encryption and Mandatory Client-side Scanning of Content
Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 16 December 2023 22:42 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 F12A6C14F5F4 for <architecture-discuss@ietfa.amsl.com>; Sat, 16 Dec 2023 14:42:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.199
X-Spam-Level:
X-Spam-Status: No, score=-7.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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham 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 dy84as7C4WfX for <architecture-discuss@ietfa.amsl.com>; Sat, 16 Dec 2023 14:41:56 -0800 (PST)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 92C12C14F5EC for <architecture-discuss@ietf.org>; Sat, 16 Dec 2023 14:41:56 -0800 (PST)
Received: by mail-pg1-x531.google.com with SMTP id 41be03b00d2f7-517ab9a4a13so1536628a12.1 for <architecture-discuss@ietf.org>; Sat, 16 Dec 2023 14:41:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702766515; x=1703371315; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=sA2RtIyfW3O9Kj19YsIRU7jgGyg8jvCO8qzM0mlbn7g=; b=i/GgzRCsekL+UXS2nMVFiWcxHr0fp9PHV/K8UDDA+69z61QeM9ez5OwTaaemKAckcP YJsuF0Q2Z9A1OBc2oJnfTwvoMtMDtqgJraLSheFTTTxMS22zKfWErnZEnilLXgOZ4675 PmY98ANVLdxvDWXz6ruJOsK8aB9zTEflHt6eJXyUGs0CWg2nR+hzakKi3y5Nb4COBRzP GcNDJWaMp9yXXAZrMyDdfOMLCwurRtLJEWZglVjLn1FZxMWJJsWH8Pi0Pwb6RchMAuDn HG0VK+06z+TlxFTYDlZq1OKiND0BD+IRcB4XpuAvfRhfMoWEc7scUXC+AQzera2GWCTf erIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702766515; x=1703371315; h=content-transfer-encoding:in-reply-to:from:references: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=sA2RtIyfW3O9Kj19YsIRU7jgGyg8jvCO8qzM0mlbn7g=; b=Tqcc0s2s1yzTCCx5QrlaF9Sf55qtkLp7ADRWRCSwwjw58efgacWYZPZSzzUTu2Gi62 kkvhgAOVUlzXWDf2Jri3f4cxYOcTZlngfbBj3UAA1PsEOAH9XjQDwxJZDKe/dnkG3eGt 7ETKUqQ1OhWiDM5cH75cBmCBlEN7MsNd2OXLo7naFMVgoO1Lr+jyjtF//XtFK48J+yKc VZkPSsnItgr8IdU5MMMetu3KpLMvlCs8Q9q6sguCzyu04cNJpZsYv3NQtBekr5Nh4lFJ NzfFVBg+ttVbOznvrJPh3KFh9H4+0bPKEtGCMWIR9thqR/2UsgttfKtt4ng2J9JcsQ4P lgMg==
X-Gm-Message-State: AOJu0YwLYJhe/awL4SHQv7R4p5coLLMlaqXNxbKpLmHRqWuZ9dndrpsk UfCjLWkRevXoAp520TITbKsU1m4jT0dP9A==
X-Google-Smtp-Source: AGHT+IEQMS2PTdCHv41hOBhPB+W2zl6sH2TvWwh9WrB/xSwOSKsT02V+IbvdwpHhRekbj5tCTlBXcQ==
X-Received: by 2002:a05:6a21:a588:b0:194:38e8:6ec7 with SMTP id gd8-20020a056a21a58800b0019438e86ec7mr293902pzc.69.1702766515602; Sat, 16 Dec 2023 14:41:55 -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 12-20020a17090a198c00b00286d905535bsm18733475pji.0.2023.12.16.14.41.54 for <architecture-discuss@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 16 Dec 2023 14:41:55 -0800 (PST)
Message-ID: <52e423e7-5787-d56a-b197-61fabe623505@gmail.com>
Date: Sun, 17 Dec 2023 11:41:50 +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: architecture-discuss@ietf.org
References: <170266952162.33107.14325064798861197261@ietfa.amsl.com> <6.2.5.6.2.20231216110256.18d0acd0@elandnews.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <6.2.5.6.2.20231216110256.18d0acd0@elandnews.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/fNxZ_PNK7oK1vy7d6HPRUZRYcbE>
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: Sat, 16 Dec 2023 22:42:02 -0000
On 17-Dec-23 09:07, S Moonesamy wrote:
> I am at a loss on how mandatory use of client-side scanning could
> restrict the use of open-source software as the statement does not
> explain that.
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.
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.
Brian
- 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)