IETF Logo Mail Archive

[TLS]Re: Adoption call for Extended Key Update for TLS 1.3

Russ Housley <housley@vigilsec.com> Thu, 25 July 2024 18:18 UTC

Return-Path: <housley@vigilsec.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 A5166C14F5F8 for <tls@ietfa.amsl.com>; Thu, 25 Jul 2024 11:18:46 -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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.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 rr9B7f4SJqzW for <tls@ietfa.amsl.com>; Thu, 25 Jul 2024 11:18:42 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 957D1C14F619 for <tls@ietf.org>; Thu, 25 Jul 2024 11:18:42 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id C8ADAD1CF1; Thu, 25 Jul 2024 14:18:41 -0400 (EDT)
Received: from smtpclient.apple (pfs.iad.rg.net [198.180.150.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 7F20DD0FF0; Thu, 25 Jul 2024 14:18:41 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C811F380-E386-485F-9B48-6BFDD61C0031"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.1\))
Date: Thu, 25 Jul 2024 14:18:29 -0400
References: <595B81B5-6E50-4809-AD56-8646F31C99CD@sn3rd.com>
To: Sean Turner <sean@sn3rd.com>, IETF TLS <tls@ietf.org>
In-Reply-To: <595B81B5-6E50-4809-AD56-8646F31C99CD@sn3rd.com>
Message-Id: <A0B6AC51-5D44-48FE-9DE0-44C110F6496F@vigilsec.com>
X-Mailer: Apple Mail (2.3731.700.6.1.1)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:content-type:mime-version:subject:date:references:to:in-reply-to:message-id; s=pair-202402141609; bh=p3TeFx7RT6Aq0wECpiE7ToxNKuHBTe+L6WNevDPhaTU=; b=UZPvUEaQUwsLUVa4juIxDXSuf/kuuTG6YEwlSxifgeNrfPMBq5X47vEx3F04h1d9f5FzmBUlBo1vT5NeJuv/bw6PIXKmo6TIYF8ITAnorpPiS4cxIB3eYMaaoCutFfzv5l3EnWcrTdVJ4rggbzh45NbmS6JR1yAMuzH73hhlxzWiE6JX76qEGE8gY4+yRTAF5Nv9FH+Wmvl/Mh6A0nlD9bF+atfVJUnE7xuKnLlDiT7nVsU7tT7iIMdP8qvmSBpdU00QQGntaeNyAS97JFdI3eYfhproWJ+jWyPcRxzN9Cvj0XEFP5LiPHY12IxzyyNDK0JnhNuO6AeHKGyddsPVfQ==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Message-ID-Hash: M3GKA5TRXYCMCOSUG5ENZEFJQOZ5EIWV
X-Message-ID-Hash: M3GKA5TRXYCMCOSUG5ENZEFJQOZ5EIWV
X-MailFrom: housley@vigilsec.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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [TLS]Re: Adoption call for Extended Key Update for TLS 1.3
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/Q3F6T31tPr_LEI4Dy9mvQYZmVVI>
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>

The FATT-related slides that were presented yesterday said:

~~~
Mechanism: triage, then maybe analyze

At document/change adoption call, chairs email the triage panel, bring
summarized analysis to the WG as part of the adoption discussion.
~~~

I now realize that this is ambiguous.  At what point in the call for adoption process, will the FATT triage assessment be shared with the WG?

Russ

v2.26.15 | Report a Bug | By Email | System Status