[TLS] Re: FATT Process Updates: Contacting FATT
Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Mon, 27 April 2026 00:23 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 668E8E396C22 for <tls@mail2.ietf.org>; Sun, 26 Apr 2026 17:23:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777249385; bh=Fowtc+5DAnbJBcFtnpPWcq/BD83+vIRnoykQNjFtAuk=; h=Date:From:Subject:To:CC:References:In-Reply-To; b=yR/HzPZSjDtlsPvhURFHW86auK8O0febKEFuXk8jDbIqX9hY0RnHCIp7V5gpgXPrQ mHXVg00zAEYXvcaxmmFhsQ5mrJIJNT4xu06LrZydlijXZaxuWz8Jry3gIONRpCv8eo 3KyU1KTJMW8HgY+P2dl05bmZdcCHPia5VjQ2uqVw=
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 tv1HEFzVEWEq for <tls@mail2.ietf.org>; Sun, 26 Apr 2026 17:23:04 -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 DAE6FE396C18 for <tls@ietf.org>; Sun, 26 Apr 2026 17:23:03 -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:References:CC:To: Subject:From:MIME-Version:Date:Message-ID:Sender:Reply-To: 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=knDwfvzNUUQR2SH6xqrrVnaZ6xZ6kXpmG0YsZhCVSBk=; b=ReaJu/mFvn3H3zDGtoF+kqAham JREsEuCoX6TT6EUL1J/2Ekn9EAITj3qBwwImhGsdVkxILAlARPjkxOH/tVcTX8BpVvvzdKpKkIUBJ C2Ss8decaBoL69wd68u1iCK69bsBY/PNLYtgVu7va7h7HQsAk/VIFapythnUClmXdrBSUXbN8x/mx N5OHOBB84q+Sl6MoqvzZKjsjcl9cgdBBW6aJFJRCNaeCh7guB5xSmBkiXjO7yWwAbf4ztcD73QE5s kCsENCQD8JBcfegvT8GxdWEi72JMv/YZo9N1+1NCEfSVMVMvYxBUOEcbS7Kzgmne+hSnh28PrQWVt 9Vcdf3sQ==;
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 1wH9kb-002hpV-2B; Mon, 27 Apr 2026 02:23:02 +0200
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, 27 Apr 2026 02:22:38 +0200
Message-ID: <b6fc4367-0015-4538-aa6d-5a3816eb1c41@tu-dresden.de>
Date: Mon, 27 Apr 2026 02:22:18 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
To: Rob Sayre <sayrer@gmail.com>
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>
Content-Language: en-US
In-Reply-To: <CAChr6SwmyLX6UJiq5bdoveDEVEsvY6r9Kzf5Zp3iXr6MhPRLyw@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms080408050600040701040305"
X-ClientProxiedBy: msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139) 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: WRVPEG3MIFGIY76MSNWVQBDIF26YAHX6
X-Message-ID-Hash: WRVPEG3MIFGIY76MSNWVQBDIF26YAHX6
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
CC: TLS List <tls@ietf.org>
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/Q1jV7QJFnuEdKTygqu8ydEcFMaM>
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 Rob, Thank you for the clarification. Please feel free to clarify if I misunderstood something. On 26.04.26 03:34, Rob Sayre wrote: > > On Sat, Apr 25, 2026 at 6:24 PM Muhammad Usama Sardar > <muhammad_usama.sardar@tu-dresden.de> wrote: > > Hi Rob, > > On 23.04.26 02:07, Rob Sayre wrote: >> On Wed, Apr 22, 2026 at 4:34 PM Eric Rescorla <ekr@rtfm.com> wrote: >> >> >> As I said in the meeting, I think there are reasonable >> arguments to be >> made about how the FATT ought to engage with the WG, and ceteris >> paribus, I think it's better for things to be open. >> >> >> I agree with Ekr here, > > Mind clarifying which part you agree with: > > 1. "there are reasonable arguments to be made about how the FATT > ought to engage with the WG" > 2. "it's better for things to be open" > > 2 is fine and I think we are all in agreement. > > If 1, could you please clarify whether you are claiming that the > arguments I have made in the thread are /not/ reasonable? If so, > please clarify which of my arguments are lacking? Thank you. > > > I think #1 and #2 are a little more intertwined than your message > suggests. Sure, I agree. However, I'm still looking to better understand your /interpretation/ of #1 to which you said you agree? So, would you mind clarifying more explicitly: Are there specific parts of my arguments in this thread that you see differently or think could be improved? If so, it would be helpful to know which one, so that I can work on that in the next version of the draft. > I think perhaps the FATT deliberations could have some closer minutes. I may be misunderstanding what 'deliberations' mean here. Quick context: please note that formal models are abstract and we have to make reasonable choices to what to put in the model and what not. With that context in mind: For final FATT review: IMHO, 8773bis report [0] is quite extensive as minutes. For initial FATT review: IMHO, key-update email [1] and presentation [2] is more than sufficient as minutes. It would help to understand what you feel is missing from those. If we agree to form the new list, I can take the action item to update this list on a reasonable frequency (say once every 2 months) on the minutes of the discussions happening on the new list, if that is what you would like to see. The problem from my point of view really is that authors can approach the FATT (as happened in case of [1]) while rest of the WG cannot. FWIW, I don't find that justified. It would be beneficial if the discussion between authors and FATT happens transparently. > I don't need to participate. I would just like to read more detailed > rationales if I want to. Sure, work on that has already happened. See [3] which is a one-stop shop for hopefully everything you would like to see about any draft since FATT started. Happy to fill in gaps if there’s something missing. > The question is really about whether the FATT participants value > private communications or just not being interrupted by any TLS WG > participant. I guess that's an action item for chairs now. Best regards, -Usama [0] https://github.com/tlswg/rfc8773bis/blob/main/fatt-review/IETF%20FATT%20Report%20-%208773bis.pdf [1] https://mailarchive.ietf.org/arch/msg/tls/pYmjTTlYd11FnjdYoOL6RdGk0sk/ [2] https://datatracker.ietf.org/meeting/125/materials/slides-125-tls-sessa-fatt-report-on-eku-00 [3] https://github.com/tlswg/tls-fatt/blob/main/fatt-point-person.md
- [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