IETF Logo Mail Archive

[TLS] Re: Fwd: I-D Action: draft-ietf-tls-extended-key-update-10.txt

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Mon, 02 March 2026 13:00 UTC

Return-Path: <muhammad_usama.sardar@tu-dresden.de>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8FB89C1E25C4 for <tls@mail2.ietf.org>; Mon, 2 Mar 2026 05:00:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=tu-dresden.de
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fywg9UEPzaDl for <tls@mail2.ietf.org>; Mon, 2 Mar 2026 05:00:42 -0800 (PST)
Received: from mailout7.zih.tu-dresden.de (mailout7.zih.tu-dresden.de [141.76.32.220]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id AB536C1E25BA for <tls@ietf.org>; Mon, 2 Mar 2026 05:00:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tu-dresden.de; s=dkim2022; h=Content-Type:In-Reply-To:From:References:To: Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Y1CA31XBvxNY2UykYEKN4APRNRDnuldUKFvoJX+/iWs=; b=XQDtGEym+q17N07ExG5JfDpjyb f+eWc/rzlz/gJd2n1LZx3OzqIwUBefxceF8Vli9/e84kpaM5bhHYSRCQQx2AvOeZ1Zk4LGSpMQLGT YF3uWnV/KSY7NuH06nwWMXfsj1aTi2jXl91WlZARO+mvAdaUjp6sOXQs3txBbhGuGZr3JbEznkTtz dc8w37+HSit46ftTl+BLdEkqsDe6AjDhgB5K5oOBCWbHzP/Sif+y0R0UVsKOQ1mlsIN/881fX6k7i v0j84Y8EKBBW5fHs+BdLDr2poQxDzW9AZYuhsS+vpBkJzGQkXoQaj2UONq7JE6RWayhzT/9YfeZLG UsuJPozw==;
Received: from msx-t422.msx.ad.zih.tu-dresden.de ([172.26.35.139] helo=msx.tu-dresden.de) by mailout7.zih.tu-dresden.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1vx2t1-005h7H-1z; Mon, 02 Mar 2026 14:00:41 +0100
Received: from [10.12.5.228] (141.76.13.165) by msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.37; Mon, 2 Mar 2026 14:00:29 +0100
Message-ID: <05aeb8db-52ac-4cab-b59c-bcd7c23e8d4b@tu-dresden.de>
Date: Mon, 02 Mar 2026 14:00:16 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: tirumal reddy <kondtir@gmail.com>, tls@ietf.org
References: <177245334761.3494122.16417546920214555219@dt-datatracker-6ff7c68975-7k42g> <CAFpG3gdR3omguE1-A-SFhgq+JukDer3Uk9kk58TvrBa+ZFO6fA@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CAFpG3gdR3omguE1-A-SFhgq+JukDer3Uk9kk58TvrBa+ZFO6fA@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms090102000300090609080105"
X-ClientProxiedBy: msx-t421.msx.ad.zih.tu-dresden.de (172.26.35.138) To msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139)
X-TUD-Virus-Scanned: mailout7.zih.tu-dresden.de
Message-ID-Hash: 2J52DEYRYXRMVKRH7C65GIID6BG4VGP7
X-Message-ID-Hash: 2J52DEYRYXRMVKRH7C65GIID6BG4VGP7
X-MailFrom: muhammad_usama.sardar@tu-dresden.de
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.9rc6
Precedence: list
Subject: [TLS] Re: Fwd: I-D Action: draft-ietf-tls-extended-key-update-10.txt
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/21eAWKjMBRCgKZQBIGOx9QWauVE>
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 02.03.26 13:18, tirumal reddy wrote:

> The main changes in 
> https://datatracker.ietf.org/doc/draft-ietf-tls-extended-key-update/ addresses 
> the session resumption threat identified by the FATT team.

FWIW, the FATT process does not seem to be followed in spirit in this 
case, too. ISTM that the following from the process [0] have not 
occurred for this draft (I did check the archives [1,2] but did not find 
anything relevant to the two processes below):

     1. The working group chairs will inform the working group of this
        decision.
     2. The output of the FATT is posted to the working group by the
        FATT point person.

Did I miss something? #1 is non-controversial (still following the 
process is good) but #2 would have been useful to send on the list.

What kind of analysis is required by FATT for this draft? Is a 
combination of symbolic security analysis (ProVerif) and standard model 
checking (SPIN model checker) deemed sufficient?

Thanks,

-Usama

[0] https://github.com/tlswg/tls-fatt?tab=readme-ov-file#document-adoption

[1] 
https://mailarchive.ietf.org/arch/browse/tls/?q=%22draft-ietf-tls-extended-key-update%22%20%22formal%22

[2] 
https://mailarchive.ietf.org/arch/browse/tls/?q=%22draft-ietf-tls-extended-key-update%22%20%22FATT%22

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