[TLS] Re: FATT Process Updates: Contacting FATT

S Moonesamy <sm+ietf@elandsys.com> Fri, 24 April 2026 20:53 UTC

Return-Path: <sm@elandsys.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 62CC7E2AA2AC for <tls@mail2.ietf.org>; Fri, 24 Apr 2026 13:53:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777063999; bh=7ys031gOC1u479LyARGDtiutGlDsXWhNmjFRZEyqs9g=; h=Date:To:From:Subject:In-Reply-To:References; b=ghYN/+2+VMGxKac07+TCBK9VS1omeCfy2pa2efsHhpcaY5ldnSYw5z/cDGiEJGhUg 97jREfp3zXOm+lMsE6hufcBovesRIiFRW0csmVB8VF6fPs/xYqpW9zRlFd1c2iohfz Uk9RkEzs+L2/U9v1Ukfyc1nrT9hAnpS6aS6CCDjI=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 2H65Wsir9pzq for <tls@mail2.ietf.org>; Fri, 24 Apr 2026 13:53:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 1CE37E2AA2A9 for <tls@ietf.org>; Fri, 24 Apr 2026 13:53:16 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.64.26]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 63OKqVY3026013 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Apr 2026 13:53:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1777063988; x=1777150388; i=@elandsys.com; bh=7ys031gOC1u479LyARGDtiutGlDsXWhNmjFRZEyqs9g=; h=Date:To:From:Subject:In-Reply-To:References; b=Id116jnRjn4CBWijVYk+Ee1h42QeS3YbtdN86EunaQFtmmsmVLasl0n/GHYgfCZ9i 2YZIfK0GX04TCSBnxyWS2envK8N6KjrRI7YEp1RCkivsTgj/6seHyfjCR/K/cr4c7M uOcMLzth6dhRalqstml5Fl+n6W7oXDx8/3fB7Wng=
Message-Id: <6.2.5.6.2.20260424124250.0c41d0b0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 24 Apr 2026 13:35:46 -0700
To: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>, tls@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <38ca4094-51a8-46b8-9b6c-2a67e9508db5@tu-dresden.de>
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> <6.2.5.6.2.20260424093844.1132e398@elandnews.com> <38ca4094-51a8-46b8-9b6c-2a67e9508db5@tu-dresden.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: B5SAZFK6TUWRW636QM5PPZT6SFBR2BFW
X-Message-ID-Hash: B5SAZFK6TUWRW636QM5PPZT6SFBR2BFW
X-MailFrom: sm@elandsys.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
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/w2kEIH4AEgJEbJDxrOf6FHmS3K4>
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 Usama,
At 11:56 AM 24-04-2026, Muhammad Usama Sardar wrote:
>Correct. To be clear, my proposal is not suggesting to change any of 
>that. In my proposal, FATT membership remains closed and their own 
>discussions remain private (as currently). Best is to have that open 
>too, but as I said, better to have something than nothing.
>>The procedures are silent about whether a working group participant 
>>can contact a member of the sub-group.
>Right, that's also my reading and that seems to be an opportunity 
>for discussion here. This is exactly where my proposal falls. It 
>seems we can discuss and if folks agree, possibly make a publicly 
>archived mailing list for engagement with FATT. What do you think 
>about such a mailing list? In particular, I'd value your opinion on 
>whether my arguments for such a mailing list in the previous email 
>are reasonable.
>>   There isn't any requirement in BCP 11 for the member of the 
>> sub-group to respond, if he/she was contacted.
>
>Correct. I am not suggesting to change that. Aim is to provide a 
>mechanism for WG members to be able to contact them in a transparent 
>way. FATT may (or may not) join the list voluntarily and likewise 
>may (or may not) respond to emails on the list voluntarily.

There was an explanation given for having the direct contact (re. 
draft-usama-tls-fatt-extension-05).  I would describe it as 
miscommunication.  That could be addressed by having direct 
communication.  A mailing list, with a public archive, would allow 
any interested party to see whether the engagement worked on 
not.  What if the member of the sub-group did not respond to the 
query which was sent to the mailing list?

It is not possible to come up with an appropriate alternative without 
the feedback of the sub-group.  That's the missing part here.

Regards,
S. Moonesamy