[TLS] Re: FATT Process
"Salz, Rich" <rsalz@akamai.com> Wed, 04 September 2024 20:11 UTC
Return-Path: <rsalz@akamai.com>
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 CDB1EC1516EB for <tls@ietfa.amsl.com>; Wed, 4 Sep 2024 13:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.252
X-Spam-Level:
X-Spam-Status: No, score=-2.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.148, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=akamai.com
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 4CBi8wX0AefU for <tls@ietfa.amsl.com>; Wed, 4 Sep 2024 13:11:35 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE45C1519B8 for <tls@ietf.org>; Wed, 4 Sep 2024 13:11:34 -0700 (PDT)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 484EZuCI009021; Wed, 4 Sep 2024 21:11:34 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=jan2016.eng; bh=CMhJvXRWL2EhF6TKAiL7nk X7aui3AyCvqjcqatT6Y6A=; b=KL15NON38+WgiFdoFRVc87NCWhkFb/SQf5xDaZ wYKembFy5zKuBfh2hPwDcdWvvjxr6RYjsxIyA2WsL6WPxQYgRB8gN1gl31iN6kZy uxI3ERNRoM17i7HLsExLBfAeH9YRYQo2p6B+WRamrCsB80eNlhWslLDskg/qvgmM LxZtQE7kBWXvnQLCRjXQglb06xvgLdgtPrw3UUVNX3AynJUTXWix/9vesnhjD/27 Fvd2kB0EF0i//xhK6Iu9i/hqRzspMcOudxadv8Ap48ZYXMNXb7pZ+UOW7EMfOao2 6LsNK/mb/L4jbpXskozHl9MqQO7b2z83xIvXuORBL+8ij3LQ==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by mx0b-00190b01.pphosted.com (PPS) with ESMTPS id 41btu089fp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 04 Sep 2024 21:11:33 +0100 (BST)
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.18.1.2/8.18.1.2) with ESMTP id 484IStrK024581; Wed, 4 Sep 2024 16:11:32 -0400
Received: from email.msg.corp.akamai.com ([172.27.91.22]) by prod-mail-ppoint1.akamai.com (PPS) with ESMTPS id 41bxh0763r-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 04 Sep 2024 16:11:32 -0400
Received: from usma1ex-dag4mb4.msg.corp.akamai.com (172.27.91.23) by usma1ex-dag4mb3.msg.corp.akamai.com (172.27.91.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Wed, 4 Sep 2024 16:11:32 -0400
Received: from usma1ex-dag4mb4.msg.corp.akamai.com ([172.27.91.23]) by usma1ex-dag4mb4.msg.corp.akamai.com ([172.27.91.23]) with mapi id 15.02.1544.011; Wed, 4 Sep 2024 16:11:32 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Joseph Salowey <joe@salowey.net>, "TLS@ietf.org" <tls@ietf.org>
Thread-Topic: FATT Process
Thread-Index: AQHa/ubVFdGn2MY5yUO/uxFEmf7j8rJID3WA
Date: Wed, 04 Sep 2024 20:11:32 +0000
Message-ID: <983F94FF-66B4-4F3C-BC94-34EBFF0E9640@akamai.com>
References: <1E84DBF8-CA48-4CA9-A435-9E61E981D8DF@akamai.com> <6284E288-4F8E-4E2A-8335-5054D9D7A6DF@obtuse.com> <CAFR824xAxfUFrXyo5PZckJPqoM3fU8ESNrDHUfOKNzDF_jJZQA@mail.gmail.com> <A5E3474B-E3D5-4DA2-BCAD-D443B2A02B5A@akamai.com> <CAFR824y=stSf28Lt=bDoM2yCOHMAEt2OsaFPAY7dxGjx+-DHug@mail.gmail.com> <B7872890-71F2-41BC-9ED9-F085CB18FA95@akamai.com> <CAOgPGoBPtTmoKQOy27XbDUGr20VDYy7qDGoZWePhZhf9vX6SEQ@mail.gmail.com>
In-Reply-To: <CAOgPGoBPtTmoKQOy27XbDUGr20VDYy7qDGoZWePhZhf9vX6SEQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.88.24082514
x-originating-ip: [172.27.118.139]
Content-Type: multipart/alternative; boundary="_000_983F94FF66B44F3CBC9434EBFF0E9640akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.60.29 definitions=2024-09-04_17,2024-09-04_01,2024-09-02_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 phishscore=0 bulkscore=0 mlxscore=0 malwarescore=0 adultscore=0 spamscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2407110000 definitions=main-2409040151
X-Proofpoint-GUID: 0y1rCwV2dO1OWv9tGZG6zIXrybOtDUmh
X-Proofpoint-ORIG-GUID: 0y1rCwV2dO1OWv9tGZG6zIXrybOtDUmh
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.60.29 definitions=2024-09-04_17,2024-09-04_01,2024-09-02_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 bulkscore=0 mlxlogscore=999 lowpriorityscore=0 suspectscore=0 phishscore=0 spamscore=0 adultscore=0 impostorscore=0 clxscore=1015 priorityscore=1501 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2407110000 definitions=main-2409040151
Message-ID-Hash: MEWJZKP7OZSXJD6E7JXSCLOBKOALE7SR
X-Message-ID-Hash: MEWJZKP7OZSXJD6E7JXSCLOBKOALE7SR
X-MailFrom: rsalz@akamai.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.9rc4
Precedence: list
Subject: [TLS] Re: FATT Process
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/7Z97sUWoOivUEgSWTQ_p7uKcwFE>
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>
* Starting a new subject to separate discussions on the FATT. That’s sensible, thanks for doing this. Let me try to answer your question this way. Here is how I view the timeline: 1. Chairs proposed a review panel 2. WG commented (my summary: consensus in favor of more analysis, disagreed with some of the specifics) 3. Chairs published panel, no acknowledgement of the feedback, no changes made 4. Summary report of analysis given If anyone disagrees with this, please let me know. Ideally with URLs pointing to messages/changes that I am forgetting. If we take the above outline as correct, then what must happen is what I’ve said before: start over. Make sure to listen and acknowledge the WG feedback and act on it. * Please understand that we are working though defining the process here. The current structure of the FATT does not allow for direct attribution of FATT feedback to specific individuals. Perhaps we may be able to adjust this in the future, but this is as it stands now. Sure. To me that means it must get thrown out. * it would be more helpful to have specifics about how we can improve and what is missing in the current process. In addition to the above… * How does the WG incent people to do analyses that the WG wants? * How long would the WG be willing to hold up an optional feature? * A core feature? * Will there be consensus calls on the final process document? If not, there really should be a good explanation of why not. * We owe the working group a revised definition of the current process which we will provide soon. Looking forward to it. Seriously. Hope this helps.
- [TLS]Consensus call for RFC8773bis Formal Analysi… Joseph Salowey
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Ben Smyth
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Salz, Rich
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Eric Rescorla
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Bob Beck
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Deirdre Connolly
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Deirdre Connolly
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Salz, Rich
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Deirdre Connolly
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Salz, Rich
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Muhammad Usama Sardar
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Stephen Farrell
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Christopher Patton
- [TLS] FATT Process Joseph Salowey
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Eric Rescorla
- [TLS] Re: FATT Process Stephen Farrell
- [TLS] Re: FATT Process Joseph Salowey
- [TLS] Re: FATT Process Salz, Rich
- [TLS] Re: FATT Process Stephen Farrell
- [TLS] Re: FATT Process Watson Ladd
- [TLS] Re: FATT Process Salz, Rich
- [TLS]Re: Consensus call for RFC8773bis Formal Ana… Salz, Rich
- [TLS] Re: Consensus call for RFC8773bis Formal An… Joseph Salowey
- [TLS] Re: Consensus call for RFC8773bis Formal An… Russ Housley
- [TLS] Re: Consensus call for RFC8773bis Formal An… Eric Rescorla
- [TLS] Re: Consensus call for RFC8773bis Formal An… John Mattsson
- [TLS] Re: Consensus call for RFC8773bis Formal An… John Mattsson
- [TLS] Re: [TLS]Consensus call for RFC8773bis Form… Muhammad Usama Sardar