IETF Logo Mail Archive

[TLS] Re: FATT process update

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Thu, 07 November 2024 20:10 UTC

Return-Path: <muhammad_usama.sardar@tu-dresden.de>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CCB3C180B46 for <tls@ietfa.amsl.com>; Thu, 7 Nov 2024 12:10:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tu-dresden.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2XC9fLJU9cx3 for <tls@ietfa.amsl.com>; Thu, 7 Nov 2024 12:10:02 -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 ietfa.amsl.com (Postfix) with ESMTPS id 49598C1654EF for <tls@ietf.org>; Thu, 7 Nov 2024 12:10:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tu-dresden.de; s=dkim2022; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:CC:References:To:Subject:MIME-Version:Date:Message-ID:Sender :Reply-To: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=VGa3/3IkSW3WpQk90pjDGeslLrjLaoWsWDilJ5QEHOE=; b=RvT8ugu5ursEtCh1hRC/MMZ+NS PgGV7jXgk9YE7Unj5nTsCf8fUo89e7V2mpTyGJUGt1NieJKDIAW6wraSwoGx1d1BVmqqy6/vWItdz J+WAEE3cy+0Yzq5Pyj+6pQFITKFhI63fp/VbBMq8EoNvqMiLJhsWpu/qPjQ991omXYYczxFW5QKp8 BqCV+pQPE/FIqBu3mHTqbu8JgK5eZiEHUcbq1pjXIeITqynL+lBp8kQy5ojtWe77JLkqhNPvOgeDM 0+Tw+l6Yb0BN0/KFQdFkCl7Gx0D884nDlnMHdzLTsB/cdVtvmaw3kGIQelpAZ4QLvxkfJTPapB9Kl 9ZAFBjvg==;
Received: from [172.26.35.112] (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 1t98pK-006sbL-Rj; Thu, 07 Nov 2024 21:09:59 +0100
Received: from msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139) by MSX-T312.msx.ad.zih.tu-dresden.de (172.26.35.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 7 Nov 2024 21:09:37 +0100
Received: from [31.133.130.163] (31.133.130.163) 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.1544.11; Thu, 7 Nov 2024 21:09:36 +0100
Message-ID: <125b89c9-4981-4e35-a9fd-8888998df431@tu-dresden.de>
Date: Thu, 07 Nov 2024 20:09:36 +0000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: tls@ietf.org
References: <CAOgPGoDAm=thO6O3xsm_HTJ+K8=mWkqVgYXZbm5Cw6K_pO1Tew@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CAOgPGoDAm=thO6O3xsm_HTJ+K8=mWkqVgYXZbm5Cw6K_pO1Tew@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: MSX-L314.msx.ad.zih.tu-dresden.de (172.26.34.114) 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: 227T4IYCYWO4SUSEFR6ESBM6PHJ6YM7L
X-Message-ID-Hash: 227T4IYCYWO4SUSEFR6ESBM6PHJ6YM7L
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 update
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/63rMRcRwUNFQWcSs6h3GnSQJTMI>
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>

Thank you for clearly writing down the process and continuing to improve 
it. I particularly like the "understood" part, which is IMO a key 
benefit of formal methods.

Also, thanks for clearly mentioning the current members in FATT process. 
I do notice that current FATT is slightly different from the initial 
announcement, and the change was never announced to the WG. Anyway, its 
good to have it in a repo now.

I would recommend putting the liaison/focal person for each document 
also in the repo. For example, I don't know who is the focal person for 
8773bis.

I would also suggest adding more onsite participants in FATT. This will 
help a lot and remove some communication latencies.

Thanks,

Usama

On 05.11.24 15:34, Joseph Salowey wrote:
> There is an updated FATT available here:
> https://github.com/tlswg/tls-fatt
>
> This has taken a lot of the feedback we have received so far, but is 
> still a work in progress. There will be a little time to discuss in 
> the meeting Friday.
>
> Joe
>
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org

v2.35.0 | Report a Bug | By Email | System Status