Return-Path: <sean@sn3rd.com>
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 505C7E0C8362
	for <tls@mail2.ietf.org>; Wed, 22 Apr 2026 05:58:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1776862706; bh=d7JGIkBvF2Hw4UfcGjZWJlsKBvxW5U+LOulFxifi8JI=;
	h=From:Subject:Date:In-Reply-To:Cc:To:References;
	b=mb5MVmEqNsvVrt7L2nYX4icmFtmyKs7MUGRrI1Fp9SgC6OQ39/07dugg4fVatOAcl
	 N2npPOama8y2jXoJ9RTK5dadk30HoO8rPRa7f9sYnmbKlV6HlU4gC2jZnJwUH/EsOm
	 J+2nFZhKGGOh/0G0AK+y4mpY08fqCfjZLkQF2bBY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
	autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key)
	header.d=sn3rd.com
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 twCA2VrxzX6N for <tls@mail2.ietf.org>;
	Wed, 22 Apr 2026 05:58:24 -0700 (PDT)
Received: from mail-qv1-xf43.google.com (mail-qv1-xf43.google.com
 [IPv6:2607:f8b0:4864:20::f43])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256)
	(No client certificate requested)
	by mail2.ietf.org (Postfix) with ESMTPS id BADAEE0C82D3
	for <tls@ietf.org>; Wed, 22 Apr 2026 05:58:14 -0700 (PDT)
Received: by mail-qv1-xf43.google.com with SMTP id
 6a1803df08f44-89fc349b5ceso77710116d6.3
        for <tls@ietf.org>; Wed, 22 Apr 2026 05:58:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=sn3rd.com; s=google; t=1776862694; x=1777467494; darn=ietf.org;
        h=references:to:cc:in-reply-to:date:subject:mime-version:message-id
         :from:from:to:cc:subject:date:message-id:reply-to;
        bh=YuVdAn75tk6P0zJVPU/yTXWC14bRJi7vygw+hJG2mAQ=;
        b=hezBOux7u0wrLYUTwLADZpFzU4I89WxWOS0Q9cK6Jmv7fUBJwqX3HVp3fikMaYd4Y/
         STdBmS8+TiuhCJjLX4hT6TTX1i2E34mM4k+XQcfDigp97LmoUf9qj1blbFg5LS4vvdYY
         OybXSCzQPb59zZpwM5Ei2NA9hbqZKPIvEiDNc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20251104; t=1776862694; x=1777467494;
        h=references:to:cc:in-reply-to:date:subject:mime-version:message-id
         :from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id
         :reply-to;
        bh=YuVdAn75tk6P0zJVPU/yTXWC14bRJi7vygw+hJG2mAQ=;
        b=EMuQDbhpfSkxHm8rRULEAk9ttCZKjww39JlN3D2UZatdeLFbbO7kyYLF5FC+gnC+cR
         q4T0ngie4y5Ishu3u1GMVbWyXWCc1LqizpKXp7Lp3xTUxxTIEt8lf0WA/pNlnC5eC6qF
         meX5dMcxidffBBF1dZspQrcxZwqqdUChngHyfh2ZvobJkZW9H2I5AYTXbV3k4zOHdvOL
         8ayu4npppPxHPp/V6WG57nfPoCrYDdgO9sfxw4+oftTpscL6PnbKJ6LfMrIJwcs6UipW
         usmcn7q+J+ibDdsOiNKkrowhEfKI5p0X4U14aaoD+cN5NTr0WSRmc7pQQk5mSpw8C5IB
         1rKw==
X-Gm-Message-State: AOJu0YzuTVgFj85t+tFXGsNvMltOr3KbUrKMU+AUC9dFXHZRCacBJW5V
	2mN/dli9KyOWcxFnDSsuZUFAD7ZqhzWAdfR1GrXSlGfW2+u5/IhHggNwtBoABFWKhcDqmjhuDCC
	HOXw6530oOg==
X-Gm-Gg: AeBDietMFroHrXnwU1J46i9JLhlJ8ES3zQkDBeADyv6IBE6eZ5/YW0Xu5r9Yt78hcRj
	Hkp08dRsh93G2LEyeoOG3dV31GrZLlvJajn2aE0Hobm0pXSfZejMdWRXmQIcM1a4ivTsrgRFQMY
	kkPWK04ppT+0OVxtR3khiyWkj5iTuFZgFCgvG7guK/dlPvzbhH38qo79mQa2dROSAwNivU/rrT5
	eitCDUhaptPCIb87bhbbFXgUGeX+/chFpkThDL3BlV9T0EUN7znHG9EQOwdU1aKXjSF33g+Uin4
	vamSBKKevy/fEmMPk72QlDTOwPgXFg9jQYK9Ox0Jklt/prC+DwjJ3TZPY2jNZR09hP8G/YuUKO4
	3ix02LYTyRgrCKWVfiyPYcf/VrusCvCcYdbSps3+Xu4Eq5jw+8Pdd6Pj1jvV3FS39mwFAb3eis4
	fjelPEdtcFb/st4VteA3y+J/SfafUOYpqrGmmxKd2cA0VyzBoXexIPmH9uCPEVfqcNTiSBVA==
X-Received: by 2002:a05:6214:c23:b0:8ac:7d13:d189 with SMTP id
 6a1803df08f44-8b028117675mr361890756d6.41.1776862694133;
        Wed, 22 Apr 2026 05:58:14 -0700 (PDT)
Received: from smtpclient.apple ([2600:4040:2555:6800:2445:7660:61c4:2904])
        by smtp.gmail.com with ESMTPSA id
 6a1803df08f44-8b02ae5ec2dsm134649046d6.29.2026.04.22.05.58.13
        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 22 Apr 2026 05:58:13 -0700 (PDT)
From: Sean Turner <sean@sn3rd.com>
Message-Id: <80CE4119-79F9-40B2-82FF-2D6E2BFE967C@sn3rd.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_FD155B45-D98C-4667-8FED-E2EE99C43EB2"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
Date: Wed, 22 Apr 2026 08:57:53 -0400
In-Reply-To: <9759b289-15aa-4cae-a306-258873b90f07@tu-dresden.de>
To: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
References: <143FA1BF-280A-4469-ADE0-7CAE3867DB88@sn3rd.com>
 <9759b289-15aa-4cae-a306-258873b90f07@tu-dresden.de>
X-Mailer: Apple Mail (2.3864.500.181)
Message-ID-Hash: WHAX6ETVIO6GS3Q7HGFHWXZDUD5KJR7N
X-Message-ID-Hash: WHAX6ETVIO6GS3Q7HGFHWXZDUD5KJR7N
X-MailFrom: sean@sn3rd.com
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: =?utf-8?q?=5BTLS=5D_Re=3A_FATT_Process_Updates?=
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/e7HZQhtX52SD5uX3Fh_qQGflCZ8>
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>


--Apple-Mail=_FD155B45-D98C-4667-8FED-E2EE99C43EB2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I=E2=80=99d bucket this in the transparency bucket. Merging.

spt

> On Apr 21, 2026, at 19:47, Muhammad Usama Sardar =
<muhammad_usama.sardar@tu-dresden.de> wrote:
>=20
> Dear Deirdre, Joe, and Sean,
>=20
> Following up with a new PR [0].
>=20
> On 10.04.26 16:00, Sean Turner wrote:
>> There were other suggestions at IETF 125, but I do not remember much =
support for them.
> I believe some things don't really need any support. Some things =
already have consensus and are already part of the process ([1] explains =
this one specifically; so won't repeat here), for which we have spent =
significant amount of time a couple of years ago in debating on list, in =
meetings and even in an interim. So this needs folks to stand up and say =
that they oppose it, rather than someone supporting it.
>=20
> TBH, I will be very surprised if there is even a single member of the =
WG who would like to get emails like [1] to be "informed" that a new =
FATT member has been added; and this is not the first time this has =
happened.
>=20
> I am not trying to be difficult, but it's unfortunate that I have to =
repeat the same thing every time new FATT is added. I am just trying to =
think of ways to make it easier for you not to forget it. For instance, =
when you add FATT member next time, the table in [0] will remind you =
that you might like to at least inform us instead of just adding FATT =
and approving PR.
>=20
> FATT addition is not frequent. IIRC we had two new in two years. So I =
am confident to say that it will not be much effort to maintain it in =
future. Nevertheless as the other PR, I am happy to volunteer to help =
maintain it in future.
>=20
> It may not be super important for others, but it is for me since I =
kind of directly work with them under their guidance. I need to know who =
is in FATT; who to contact for which draft etc.
>=20
> Thank you for your consideration in making it more transparent and =
keeping WG in the loop.
>=20
> Sincerely,
>=20
> -Usama
>=20
> [0] https://github.com/tlswg/tls-fatt/pull/20
>=20
> [1] =
https://mailarchive.ietf.org/arch/msg/tls/6usy24RJ3FQS-EwS79gd-3UEqak/
>=20


--Apple-Mail=_FD155B45-D98C-4667-8FED-E2EE99C43EB2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" =
content=3D"text/html; charset=3Dutf-8"></head><body =
style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;">I=E2=80=99d bucket this in the =
transparency bucket. Merging.<div><br></div><div>spt<br =
id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote =
type=3D"cite"><div>On Apr 21, 2026, at 19:47, Muhammad Usama Sardar =
&lt;muhammad_usama.sardar@tu-dresden.de&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div>

 =20
    <meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DUTF-8">
 =20
  <div><p>Dear Deirdre, Joe, and Sean,</p><p>Following up with a new PR =
[0].<br>
    </p>
    <div class=3D"moz-cite-prefix">On 10.04.26 16:00, Sean Turner =
wrote:<span style=3D"white-space: pre-wrap">
</span></div>
    <blockquote type=3D"cite" =
cite=3D"mid:143FA1BF-280A-4469-ADE0-7CAE3867DB88@sn3rd.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">There were other =
suggestions at IETF 125, but I do not remember much support for =
them.</pre>
    </blockquote><p>I believe some things don't really need any support. =
Some things
      already have consensus and are already part of the process ([1]
      explains this one specifically; so won't repeat here), for which
      we have spent significant amount of time a couple of years ago in
      debating on list, in meetings and even in an interim. So this
      needs folks to stand up and say that they oppose it, rather than
      someone supporting it.<br>
    </p><p>TBH, I will be very surprised if there is even a single =
member of
      the WG who would like to get emails like [1] to be "informed" that
      a new FATT member has been added; and this is not the first time
      this has happened.<br>
    </p><p>I am not trying to be difficult, but it's unfortunate that I =
have
      to repeat the same thing every time new FATT is added. I am just
      trying to think of ways to make it easier for you not to forget
      it. For instance, when you add FATT member next time, the table in
      [0] will remind you that you might like to at least inform us
      instead of just adding FATT and approving PR.</p><p>FATT addition =
is not frequent. IIRC we had two new in two years.
      So I am confident to say that it will not be much effort to
      maintain it in future. Nevertheless as the other PR, I am happy to
      volunteer to help maintain it in future.</p><p>It may not be super =
important for others, but it is for me since
      I kind of directly work with them under their guidance. I need to
      know who is in FATT; who to contact for which draft etc.<br>
    </p><p>Thank you for your consideration in making it more =
transparent
      and keeping WG in the loop.<br>
    </p><p>Sincerely,</p><p>-Usama<br>
    </p><p>[0] <a class=3D"moz-txt-link-freetext" =
href=3D"https://github.com/tlswg/tls-fatt/pull/20">https://github.com/tlsw=
g/tls-fatt/pull/20</a></p><p>[1]
      <a class=3D"moz-txt-link-freetext" =
href=3D"https://mailarchive.ietf.org/arch/msg/tls/6usy24RJ3FQS-EwS79gd-3UE=
qak/">https://mailarchive.ietf.org/arch/msg/tls/6usy24RJ3FQS-EwS79gd-3UEqa=
k/</a><br>
    </p>
  </div>

</div></blockquote></div><br></div></body></html>=

--Apple-Mail=_FD155B45-D98C-4667-8FED-E2EE99C43EB2--

