[TLS] Re: FATT Process Updates: Contacting FATT
Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Tue, 28 April 2026 00:03 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 E3367E44AE84 for <tls@mail2.ietf.org>; Mon, 27 Apr 2026 17:03:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777334623; bh=7YhZxjHu4cbYcYEXD1pabC6L6wz7ogoXf5Q4TCnIYEk=; h=Date:Subject:To:References:From:In-Reply-To; b=jflGEpuGGqVr0aBF/iBwvRjqth7E3nL175T2uTugpvlNVUD60NyOUDE4EwP4okpEw elmBZuRve9JEb9gjzngnaHIQJIN/i7rhtBPiqudcD7ElY33t4Z5K2QDRrtKfUXHm0s Nm+h0iylBu2tlIH7BywXSlviqR1/eiT7hcvnYmn4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.396
X-Spam-Level:
X-Spam-Status: No, score=-4.396 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_MSPIKE_H2=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 0tVYUvrgHwbH for <tls@mail2.ietf.org>; Mon, 27 Apr 2026 17:03:43 -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 DFAA5E44AE73 for <tls@ietf.org>; Mon, 27 Apr 2026 17:03:42 -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: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=2AnhjUOI8YUljgCqSvR0J0vxx+FI3rIJctNAfMiFRc8=; b=FWhFTJZ+Q4tE2LYZxr9oRTfiJu bfH5rrRhMeLW23Wt5OCkmfIM/0pwLwMgkkLzkzWQGJa1kOZOALAuznVHkiB+aFa+QMXZLd8hpJ8Bb BlSTkU93i4K9S439sKRlY2H+i1WZQrudI+i51OZ/WxEcomKTVxVSGqs8DjnlwiEsPK6n5zH7nB5dU JcyIfxv3+MwFcghj62E9BFEgjzUC7hx/UZbnfAruSPytHSNSwU/i7DWhzynmLIFSxbBxwzy8SdpcS P7j0LgVqrlioRPV3f0QN9PxZprKiohIGO/882Z2vmi05iSnnjVYbSvFqzGdy7NUPleEgMs4QVEFVL ckxSWJKQ==;
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.96) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1wHVvQ-00Fylk-2C for tls@ietf.org; Tue, 28 Apr 2026 02:03:41 +0200
Received: from [10.12.5.228] (141.76.13.149) 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; Tue, 28 Apr 2026 02:03:40 +0200
Message-ID: <306aec2b-935a-4d2f-8e1d-a80b11957fec@tu-dresden.de>
Date: Tue, 28 Apr 2026 02:03:39 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: TLS List <tls@ietf.org>
References: <143FA1BF-280A-4469-ADE0-7CAE3867DB88@sn3rd.com> <9759b289-15aa-4cae-a306-258873b90f07@tu-dresden.de> <80CE4119-79F9-40B2-82FF-2D6E2BFE967C@sn3rd.com> <b3d2495c-ca82-420c-9bb8-8f5766f1c94a@tu-dresden.de> <CABcZeBOnzwNnu=joUfzfD30T3PbTwbDJE_+70g8+mpJ1ZON6Aw@mail.gmail.com> <CAChr6SwVa+RK4sNTTCkBL+tKTohtzvSVkf7W9HJ3jbrJXDTdKQ@mail.gmail.com> <4ffb0756-1cfe-41a6-8f26-c0fb4daecaed@tu-dresden.de> <CAChr6SwmyLX6UJiq5bdoveDEVEsvY6r9Kzf5Zp3iXr6MhPRLyw@mail.gmail.com> <b6fc4367-0015-4538-aa6d-5a3816eb1c41@tu-dresden.de> <CAChr6SxJHG=iyNKsy47uimbqg-L1b9yZUy0JYHp=Dx6hy0-Mcg@mail.gmail.com> <f878a04f-f30f-4dfe-a113-a84f198ebf27@tu-dresden.de> <CAChr6Sz1tyjYsc7Stp3_KELm467sP2d7-p2-QMReAZN_aZmrrQ@mail.gmail.com> <eb7d6206-076f-47f4-ada4-47b00b6b1f76@tu-dresden.de> <MN2PR17MB403149D17EF6158950DA6C25CD362@MN2PR17MB4031.namprd17.prod.outlook.com> <3897d5de-e09b-4c07-bd3c-6c1b0b385f22@app.fastmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <3897d5de-e09b-4c07-bd3c-6c1b0b385f22@app.fastmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms000005000902010202040607"
X-ClientProxiedBy: msx-t420.msx.ad.zih.tu-dresden.de (172.26.35.137) 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: WA4QL2H43MHVU62VUJTRAHQEP6ZJS3F3
X-Message-ID-Hash: WA4QL2H43MHVU62VUJTRAHQEP6ZJS3F3
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: FATT Process Updates: Contacting FATT
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/HdMr4_K_UUd8f0i1VW-xSVVDMmQ>
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>
It will probably not change anything but just to share my last 2 cents on this without going into a debate: On 27.04.26 20:49, Filippo Valsorda wrote: > I’m opposed: it doesn’t sound like we heard from any FATT members > about this? The scarce resource here is their time, we should do > whatever works best for them That's a very fair point and I see this as a perfectly valid reason for opposition by /FATT/, but perhaps not by /WG members/. In my understanding, it would likely save FATT time, as I mention in the draft [0]. But if they oppose it, I'll just drop it, just like I dropped the openness point a couple of years ago. I believe chairs will seek their input directly, as they might not be fine with sharing their individual opinions. > (and secondarily try not to block things unnecessarily on them, which > means I am especially opposed to anything in > https://muhammad-usama-sardar.github.io/tls-fatt-extension/draft-usama-tls-fatt-extension.html that > would have made a trivial addition of a key exchange algorithm like > ML-KEM block on FATT). FWIW, this appears to be largely orthogonal to the mechanism for /contacting/ FATT, which was the topic of this sub-thread. FWIW, this "trivial" addition has an opposition of several WG members in my understanding. It is essentially blocked. It is not obvious to me how we are going to unblock that without formal analysis. I don't think calling it "trivial" will lead us anywhere. I am very surprised that a sincere effort to resolve the dispute and to offer a statement for security considerations is labelled as 'block'-ing draft by the WG members, especially given that the draft is already blocked by the opposition of several WG members. Instead of spending more time and energies on resolving issues of ML-KEM, I would rather let it remain blocked and do some useful work for other WGs. Thank you all for your time and energies on considering my proposals. I am grateful to all for the discussion. Sincerely, -Usama [0] https://www.ietf.org/archive/id/draft-usama-tls-fatt-extension-06.html#section-4.1.3-2.2.1
- [TLS] FATT Process Updates Sean Turner
- [TLS] Re: FATT Process Updates Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: FATT process for … Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: FATT process for … Bas Westerbaan
- [TLS] Re: FATT Process Updates: FATT process for … Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: FATT process for … Bas Westerbaan
- [TLS] Re: FATT Process Updates: FATT process for … Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: FATT process for … David Benjamin
- [TLS] Re: FATT Process Updates: FATT process for … Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates Sean Turner
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT Eric Rescorla
- [TLS] Re: FATT Process Updates: Contacting FATT Rob Sayre
- [TLS] Re: FATT Process Updates: Contacting FATT Eric Rescorla
- [TLS] Re: FATT Process Updates: Contacting FATT Rob Sayre
- [TLS] Re: FATT Process Updates: Contacting FATT Sean Turner
- [TLS] Re: FATT Process Updates: Contacting FATT Rob Sayre
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT Rob Sayre
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT Rob Sayre
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT Rob Sayre
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT Salz, Rich
- [TLS] Re: FATT Process Updates: Contacting FATT Filippo Valsorda
- [TLS] Re: FATT Process Updates: Contacting FATT David Benjamin
- [TLS] Re: FATT Process Updates: Contacting FATT Eric Rescorla
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT Nadim Kobeissi
- [TLS] Re: FATT Process Updates: Contacting FATT Felix Linker
- [TLS] Re: FATT Process Updates: Contacting FATT Nadim Kobeissi
- [TLS] Re: FATT Process Updates: Contacting FATT Salz, Rich
- [TLS] Re: FATT Process Updates: Contacting FATT Nadim Kobeissi
- [TLS] Re: FATT Process Updates: Contacting FATT Salz, Rich
- [TLS] Re: FATT Process Updates: Contacting FATT Nadim Kobeissi
- [TLS] Re: FATT Process Updates: Contacting FATT Salz, Rich
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT S Moonesamy
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT S Moonesamy
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT S Moonesamy
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT S Moonesamy
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar
- [TLS] Re: FATT Process Updates: Contacting FATT Rob Sayre
- [TLS] Re: FATT Process Updates: Contacting FATT S Moonesamy
- [TLS] Re: FATT Process Updates: Contacting FATT Muhammad Usama Sardar