[TLS]Re: Trust Expressions Update

Rob Sayre <sayrer@gmail.com> Mon, 22 July 2024 01:20 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77333C1840D3 for <tls@ietfa.amsl.com>; Sun, 21 Jul 2024 18:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=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] 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 e4AdXsEKwTrB for <tls@ietfa.amsl.com>; Sun, 21 Jul 2024 18:20:37 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 0C59BC151539 for <tls@ietf.org>; Sun, 21 Jul 2024 18:20:31 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a77e7420697so419875966b.1 for <tls@ietf.org>; Sun, 21 Jul 2024 18:20:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721611230; x=1722216030; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=f+DVszYFw4f7UF/YP2zKGy9ZqMmvsPiw3xmgPMPkfGo=; b=HpH+UE6nHbuXqd0+Iodcidw/EIEX5gYm3dkWSQDQnt4+w/HpiUThK0uYxqTqoweE/k tDEdKIhNsndgIpgKjimuF+7Sf62ABrKBwHNWqdDDqQzKOP1RswguPWSv8Re62Fufrtrs 32g0vjmCnQKYGl2WJJ+mF2GABq1RybdZLeqFK7pSD3gcA6S6M1q3YGCdL+/XzjgrBVnP GpMQcJpSCE7zDKoE6ctZVb/+JtFWOdppP3qLwx9JMK2LuKXDem3DQSKozXZ9dI2O1Pg4 NbjLKyYxn1GZeIQ/6o+vpC2NDPwc3JPj9HtSVuuDTWet5soQP6PpT5MII1jcZ5fB926k A9cQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721611230; x=1722216030; 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=f+DVszYFw4f7UF/YP2zKGy9ZqMmvsPiw3xmgPMPkfGo=; b=YX3wzSg1r+PO9mb1XgFsJRhXblw38UuRvc5glmwkbPoT6qeWbVFFGBAQAaQU4aIAiD tQaRBrdPE9hq3nCUVWXoxOQP53NWkJafEPH3E3UF2vbMJt36fMi7t9LGUIXn14OsKFRO 4btinQBTD65AfFsgyMOJ+7FdfgoKG8XAA2ZOBb+UXKhtb8zcR/9jCjYo/VShzcV6WNdZ bN47u3XxX/G9hE/272+CQg80cnZCn8ejtML5/jX3CaSTp/Bxd/JcE46M3JdHEyIOeilM HsfgsXghTr70Jk39X2sGM8H0k25bJZ8wJQzsZ7PEckH9V8uBeyu/iW2fkL8ZXl6xYlxI 8JnQ==
X-Forwarded-Encrypted: i=1; AJvYcCUsC1Wkemy/aJxedVVy7XIkthUKDcb1y3zmF3FivvmA7pMnlROc/Z2QVMyDSeMnxf9HuPJhuyLpIoCqqmY=
X-Gm-Message-State: AOJu0Yw3L5R239UPpCQJ7VLdLj0UiQ1dNp2gJo+KLnxVNkHMooU0cXip 9r1bhoVBgjFsyq4nXlcGjH3p1iAW0cjGuLbEakQB3ZlPq022PY9SOufmlxLCBppvRJ2n4zG8R9Y ObCQ5yQkIyTffUEuKKckoyZAJBKRp1lOe
X-Google-Smtp-Source: AGHT+IEnCaiROVpSgjUXQlanRkvwXqSjsx5jnE2S2BvAgXyTaDE4avms7Ka9av76XJa3iX7LY94houu5cmGTLGixKk0=
X-Received: by 2002:a17:907:7244:b0:a77:e55a:9e79 with SMTP id a640c23a62f3a-a7a4bfa19bbmr322092966b.4.1721611229744; Sun, 21 Jul 2024 18:20:29 -0700 (PDT)
MIME-Version: 1.0
References: <CAF8qwaAZ6QeyO9TcbmDgO5mkeixc11pzDgEF=7-KdLWzCp_qWA@mail.gmail.com> <51545883-30f5-4735-b237-e2c48df2b1dd@dennis-jackson.uk> <SJ2PR15MB567121783E3A9ADD2B1215ECB6A82@SJ2PR15MB5671.namprd15.prod.outlook.com>
In-Reply-To: <SJ2PR15MB567121783E3A9ADD2B1215ECB6A82@SJ2PR15MB5671.namprd15.prod.outlook.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Sun, 21 Jul 2024 18:20:18 -0700
Message-ID: <CAChr6SwKT91BV8JuVjqHFvyhkb7dD6Q2O2zCcz1hgvDe-S5pYg@mail.gmail.com>
To: Kyle Nekritz <knekritz=40meta.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ca5993061dcbd9dc"
Message-ID-Hash: VT5SPPMQ4IZQ4X7RE4OE7DWH4AXHYOMU
X-Message-ID-Hash: VT5SPPMQ4IZQ4X7RE4OE7DWH4AXHYOMU
X-MailFrom: sayrer@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Dennis Jackson <ietf=40dennis-jackson.uk@dmarc.ietf.org>, "tls@ietf.org" <tls@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [TLS]Re: Trust Expressions Update
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/WmcIHzGZbXRAG_SiARXvilJkOuA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

On Sun, Jul 21, 2024 at 6:10 PM Kyle Nekritz <knekritz=
40meta.com@dmarc.ietf.org> wrote:

> On the surveillance risks, what differentiates trust negotiations from
> other existing negotiation mechanisms? Any negotiation mechanism comes with
> risks that it will be used to negotiate something problematic. It's not
> clear to me why trust negotiation is significantly different in this regard
> to named group negotiation, which also has a lot of relevance when talking
> about mass surveillance risk.
>
> Do you see differences with trust negotiation, or in the specific
> negotiation mechanisms that are being proposed? Or would you have similar
> concerns if, say, we didn't already have named group negotiation, and were
> discussing adding that right now?
>

I'm not sure what the new problem is. Can someone explain that? I didn't
find the IoT explanation very convincing. Aren't these things all on IPv6
anyway?

thanks,
Rob