[TLS] Fwd: New Version Notification for draft-usama-tls-fatt-extension-03.txt

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Sun, 12 April 2026 15:47 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 D8097DAC5DED for <tls@mail2.ietf.org>; Sun, 12 Apr 2026 08:47:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776008851; bh=XHwJvGmKxelcp6iCtKQ5ljmKXtdWiUjw4kWYAznciJs=; h=Date:Subject:References:To:From:In-Reply-To; b=VzD8fm9irFSjx/E4XJ6zmNIUHb0Vvd9OaPmqqd1GpAxT/dJncABLfyugIbsCGJJKa ptvNmkLqxnqgHORGZ+HYkIwdOI61svIh3Toy/JvknsJUyxVEgi+PA3HVZo2LWu0/s+ lTV+fwq7ANVWBCAPr5wh1va1r+PBoMgajlmlfiYM=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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_DNSWL_MED=-2.3, 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 NaQX1O96PYBe for <tls@mail2.ietf.org>; Sun, 12 Apr 2026 08:47:31 -0700 (PDT)
Received: from mailout4.zih.tu-dresden.de (mailout4.zih.tu-dresden.de [141.30.67.75]) (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 C716CDAC5DE3 for <tls@ietf.org>; Sun, 12 Apr 2026 08:47:30 -0700 (PDT)
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:To:References: 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=KqQK078sFXzJryqBXsU0Xfwe5zxbKPQIo/ObNAdhCUY=; b=aeeLFl2kSghv/b+KUgGCtR9baH ZfD8uHZZYw9iVyE5Q/hGaOTUaVi5nj0y6KtvxBuYBTYunVnYBLzXr8xrBU9pCj5egJ+oq+9FGvwUI eTjyV9O9yQI4ZGtiOj5UOl9sT/O/sqHxxkk5+AHFeZmUGeKVr0WFNWTOS0Krp0a8JC7Zkkx1IUTjK t90dWC+O9DusEqt5CvYxhXlRMdplf0dPpv/Wl7BF4AbERCxwFQiJeZWz+qZXcvtxui98d7lE/GzOG fMtnym5tf2bC5uaekjaht57qcEAgHsMNBVLr2fchr1V23Dmq2OGZ7t7Y3mafdOw7UGZrpgMId2gg3 PDne2Y6g==;
Received: from msx-l415.msx.ad.zih.tu-dresden.de ([172.26.34.135] helo=msx.tu-dresden.de) by mailout4.zih.tu-dresden.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1wBx20-005LYs-CP for tls@ietf.org; Sun, 12 Apr 2026 17:47:29 +0200
Received: from [10.12.5.228] (141.76.13.149) by msx-l415.msx.ad.zih.tu-dresden.de (172.26.34.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.37; Sun, 12 Apr 2026 17:47:29 +0200
Message-ID: <a93eac37-34ed-46fc-90be-4fd0826ddb9b@tu-dresden.de>
Date: Sun, 12 Apr 2026 17:47:27 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
References: <177600701498.436747.15278208326116243713@dt-datatracker-647897bf7-7f2k5>
Content-Language: en-US
To: "TLS@ietf.org" <tls@ietf.org>
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <177600701498.436747.15278208326116243713@dt-datatracker-647897bf7-7f2k5>
X-Forwarded-Message-Id: <177600701498.436747.15278208326116243713@dt-datatracker-647897bf7-7f2k5>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms070704050605080307000301"
X-ClientProxiedBy: MSX-L414.msx.ad.zih.tu-dresden.de (172.26.34.134) To msx-l415.msx.ad.zih.tu-dresden.de (172.26.34.135)
X-TUD-Virus-Scanned: mailout4.zih.tu-dresden.de
Message-ID-Hash: G5ZJT6YOX5SS2XQBUQPBUIRXJRLMAG3Q
X-Message-ID-Hash: G5ZJT6YOX5SS2XQBUQPBUIRXJRLMAG3Q
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] Fwd: New Version Notification for draft-usama-tls-fatt-extension-03.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/hMPwzaPVB8NyYI3UuUbt-tTQhAs>
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>

Hi all,

This version addresses the following (format: feedback => action taken):

 1. Wei's request for guidance => added some details, examples and
    reference in Secs. 5.2 and 5.3 [0,1] (more on it in the
    corresponding thread later)
 2. Nate's request for guidance => same as above
 3. John's feedback on limitations of formal methods => added proposed
    phrasing in Sec. 8 [2]
 4. Ekr's concerns => addressed to a very small extent by removing a
    little bit of "litigation" and proposing solutions in Sec. 4 [3]. I
    know it will not make Ekr happy but the relevant issue (issue #3) is
    still open. Merging FATT PR#16 [4] will make more of it go away. I
    haven't seen anyone objecting to merging that but I prefer to wait
    for that to be merged first.

Thanks to John and Ekr for feedback on -02.

I welcome any further feedback, or what kind of guidance authors will 
find helpful. Thanks.

Best,
-Usama

[0] 
https://www.ietf.org/archive/id/draft-usama-tls-fatt-extension-03.html#section-5.2
[1] 
https://www.ietf.org/archive/id/draft-usama-tls-fatt-extension-03.html#section-5.3
[2] 
https://www.ietf.org/archive/id/draft-usama-tls-fatt-extension-03.html#section-8-2
[3] 
https://www.ietf.org/archive/id/draft-usama-tls-fatt-extension-03.html#section-4
[4] https://github.com/tlswg/tls-fatt/pull/16


-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-usama-tls-fatt-extension-03.txt
Date: 	Sun, 12 Apr 2026 08:16:54 -0700
From: 	internet-drafts@ietf.org
To: 	Muhammad Sardar <muhammad_usama.sardar@tu-dresden.de>, Muhammad 
Usama Sardar <muhammad_usama.sardar@tu-dresden.de>



A new version of Internet-Draft draft-usama-tls-fatt-extension-03.txt 
has been
successfully submitted by Muhammad Usama Sardar and posted to the
IETF repository.

Name: draft-usama-tls-fatt-extension
Revision: 03
Title: Extensions to TLS FATT Process
Date: 2026-04-12
Group: Individual Submission
Pages: 15
URL: https://www.ietf.org/archive/id/draft-usama-tls-fatt-extension-03.txt
Status: https://datatracker.ietf.org/doc/draft-usama-tls-fatt-extension/
HTML: https://www.ietf.org/archive/id/draft-usama-tls-fatt-extension-03.html
HTMLized: 
https://datatracker.ietf.org/doc/html/draft-usama-tls-fatt-extension
Diff: 
https://author-tools.ietf.org/iddiff?url2=draft-usama-tls-fatt-extension-03

Abstract:

This document applies only to non-trivial extensions of TLS, which
require formal analysis. It proposes the authors specify a threat
model and informal security goals in the Security Considerations
section, as well as motivation and a protocol diagram in the draft.
We also briefly present a few pain points of the team doing the
formal analysis which -- we believe -- require refining the process:

* Contacting FATT

* Understanding the opposing goals

* No response from some authors

* Slots at meeting

* Provide protection against FATT-bypass by other TLS-related WGs

* Process not being followed



The IETF Secretariat