[TLS] Re: Clarification on the FATT Process

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Sat, 28 February 2026 07:30 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 16FBDC040F6C for <tls@mail2.ietf.org>; Fri, 27 Feb 2026 23:30:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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, 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 XiWz67efAOui for <tls@mail2.ietf.org>; Fri, 27 Feb 2026 23:30:20 -0800 (PST)
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 40ECCC040F5F for <tls@ietf.org>; Fri, 27 Feb 2026 23:30:18 -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=rSQ5DQzjg+yk5c7OUWQ6vkS9Uix8fPB/Xj6Dw7Uyku0=; b=A3CZW6JfFAMPh/Qqw7E9NxpoMN jKu1BfcdB7WKWzmut66aliNj5aEgPk0kiqGx1z+hd7pnwe+8fG39dTh7WBcwxvWjgNIHnaGmGTgN/ m3SoeERrUTM/fGvxWF47vb9UxHWXqWjijT9mCHbcHkO2Feuae3ZMw9kxhf2K2VbsAvS/aFVSTPsRN TOOm6Ns/JgbriomgWwYImVDy9gssczGnPVfFeS0JN0G0ZvMoI7A5tyVUfgPuPgIM9DI133bRTkKEs ghAHOV6xbWli9mUpaMgKQQY9zaGf+Hahug6UYUW5Iwkvp4xFCI+P6buPzwiT49kh/5nlCJ9cfdM8g oco89+Og==;
Received: from msx-t422.msx.ad.zih.tu-dresden.de ([172.26.35.139] 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 1vwEmH-007JJI-H3; Sat, 28 Feb 2026 08:30:17 +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; Sat, 28 Feb 2026 08:30:16 +0100
Message-ID: <983b7f92-bfb2-4523-b19e-7a8ba26fec42@tu-dresden.de>
Date: Sat, 28 Feb 2026 08:30:15 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Joseph Salowey <joe@salowey.net>, tls@ietf.org
References: <CAOgPGoC_J5js5DNfQNm0yNr=D+U8BJiL+CO4wdD3btYgZJUgXw@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CAOgPGoC_J5js5DNfQNm0yNr=D+U8BJiL+CO4wdD3btYgZJUgXw@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms010602030303050006020601"
X-ClientProxiedBy: MSX-T416.msx.ad.zih.tu-dresden.de (172.26.35.136) To msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139)
X-TUD-Virus-Scanned: mailout4.zih.tu-dresden.de
Message-ID-Hash: R3ZXPF43AR6NWOT4QMXTDYLMMJTBAZS2
X-Message-ID-Hash: R3ZXPF43AR6NWOT4QMXTDYLMMJTBAZS2
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: Clarification on the FATT Process
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/13WCbz3IVLVfR2xLACnYBfX181s>
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>

Dear Joe,

On 28.02.26 02:03, Joseph Salowey wrote:
> Unfortunately, the chairs did not announce this decision on the list 
> (this is something that should be corrected in the process)

Thank you for acknowledging that the decision was not announced on the 
list. I would like to understand what "corrected in the process" 
entails. Does it entail moving the document from WGLC to WG document? 
Could you please explain in full detail?

Before I go point by point on your email (in the light of history of 
FATT process, namely RFC8773bis), I want to ask one process-related thing:

Is the chairs' "determination whether the change proposed by the 
document requires review by the FATT" considered as final or is the WG 
allowed to put its 2 cents after the decision is finally revealed? Also 
please note that at least three other participants of the WG have 
requested FATT review during WGLC. So it seems that I am not the only 
one who would have put trust in FATT for a controversial matter and if 
chairs allow, I would like to discuss it further on the list.

Thank you for your kind consideration,

-Usama