[TLS]Re: Consensus call for RFC8773bis Formal Analysis Requirement
"Salz, Rich" <rsalz@akamai.com> Sun, 25 August 2024 19:55 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 F3D88C14F693 for <tls@ietfa.amsl.com>; Sun, 25 Aug 2024 12:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.249
X-Spam-Level:
X-Spam-Status: No, score=-7.249 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 Uj6nb3LUKh6G for <tls@ietfa.amsl.com>; Sun, 25 Aug 2024 12:55:00 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [67.231.149.131]) by ietfa.amsl.com (Postfix) with ESMTP id 2645BC14F614 for <tls@ietf.org>; Sun, 25 Aug 2024 12:54:59 -0700 (PDT)
Received: from pps.filterd (m0409409.ppops.net [127.0.0.1]) by m0409409.ppops.net-00190b01. (8.18.1.2/8.18.1.2) with ESMTP id 47PE0IBo020024 for <tls@ietf.org>; Sun, 25 Aug 2024 20:54:59 +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=gSqieItIVlDxuyX3B5qlFV t0jw9MYibAdgMsreBP6VU=; b=I+vz9LvfV/e3sGRxo8I8OvB1qnlU9C+rBY6XBn iZCT29vYtL86bDQSRLv18YAxq4iosMpy4IJEA7KvWPnSGyPzyLv8Orw0JQNJDMbH jpgmp9hP3dYveR7GTDquZnYTBCUAjfu/GUvyWrJlp4WgWKVxbqNEa+aquJlQ9EWK meXk8z4dQD0yYLFtKK0h8Pr6k4RTCiAUGq+lCZPteG/XXO547EFNXAJM1AePpO41 rzoRYtlRBCfBp+fCWOYxXs29To4iWJLt0MNuDeUtK5wHdaFBxznNuGxxjyXEOttr x0Q831XgbFWd65UrKn3BDFC0276vRhfvB4MkZOJSIwBh5PWA==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by m0409409.ppops.net-00190b01. (PPS) with ESMTPS id 417rusyx8v-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Sun, 25 Aug 2024 20:54:59 +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 47PF1hFN027208 for <tls@ietf.org>; Sun, 25 Aug 2024 15:54:57 -0400
Received: from email.msg.corp.akamai.com ([172.27.91.22]) by prod-mail-ppoint1.akamai.com (PPS) with ESMTPS id 417auywufv-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Sun, 25 Aug 2024 15:54:57 -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; Sun, 25 Aug 2024 15:54:57 -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; Sun, 25 Aug 2024 15:54:57 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "<tls@ietf.org>" <tls@ietf.org>
Thread-Topic: [TLS]Consensus call for RFC8773bis Formal Analysis Requirement
Thread-Index: AQHa9YJaWu9OLXOwrE2lBvHpjpQ1ubI4ZkuA
Date: Sun, 25 Aug 2024 19:54:56 +0000
Message-ID: <1E84DBF8-CA48-4CA9-A435-9E61E981D8DF@akamai.com>
References: <CAOgPGoBxoEhVkzb=WYFvNEhN0sKLDLir0qPVSqx_a=Co7dkXgA@mail.gmail.com>
In-Reply-To: <CAOgPGoBxoEhVkzb=WYFvNEhN0sKLDLir0qPVSqx_a=Co7dkXgA@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.24081116
x-originating-ip: [172.27.164.43]
Content-Type: multipart/alternative; boundary="_000_1E84DBF8CA484CA9A4359E61E981D8DFakamaicom_"
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.28.16 definitions=2024-08-25_16,2024-08-23_01,2024-05-17_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 malwarescore=0 phishscore=0 bulkscore=0 mlxscore=0 suspectscore=0 adultscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2407110000 definitions=main-2408250158
X-Proofpoint-GUID: dB0B8r2Zs7TtKZorECUxznxo41Yz8lzT
X-Proofpoint-ORIG-GUID: dB0B8r2Zs7TtKZorECUxznxo41Yz8lzT
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16 definitions=2024-08-25_16,2024-08-23_01,2024-05-17_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 adultscore=0 mlxlogscore=999 impostorscore=0 spamscore=0 malwarescore=0 bulkscore=0 suspectscore=0 phishscore=0 clxscore=1015 priorityscore=1501 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2407110000 definitions=main-2408250159
Message-ID-Hash: 3734PGWDTPDEQYQOT4YLKE2T3NIS72SE
X-Message-ID-Hash: 3734PGWDTPDEQYQOT4YLKE2T3NIS72SE
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: Consensus call for RFC8773bis Formal Analysis Requirement
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/dpCp3XEZPEfCWn39nNCWAbWrU64>
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>
I am opposed. Anonymous email recommendations are not how the IETF operates.
Attached below is a note I wrote a month ago to the Chairs. None of the points written there – and MOST of them were a summary of WG discussion – were addressed.
From: Rich Salz <rsalz@akamai.com<mailto:rsalz@akamai.com>>
Date: Tuesday, July 30, 2024 at 1:49 PM
To: "tls-chairs@ietf.org<mailto:tls-chairs@ietf.org>" <tls-chairs@ietf.org<mailto:tls-chairs@ietf.org>>
Subject: Rethinking the formal analysis triage
TLS Chairs,
I wasn’t sure whether to send this to you or the entire WG. I let another person read this and they suggested the Chairs. So here you go.
I re-read all the messages in the archive [1] and re-watched the 119 and 120 segments on the triage panel. I believe that, as currently set up, it is so flawed that it should be taken down and rebuilt from scratch.
After the idea was proposed in March, the two most common feedback suggestions were
• Collaborate with UFMRG
• Make all communications open and on the mailing list
Neither of these were done. In fact, there was no response from the Chairs on either point.
From the beginning, the stated intent was the that one thing the panel would provide is an estimate of how much work any suggested analysis would take. The one review that was done so far did not include that, other than “feasible.”
Many people have already commented that collating all responses is a bad idea. I want to add one point that I have not seen before: if a subset of the triage reviewers recommends analysis, the WG has no information about the qualifications of those making the recommendation and no way to evaluate how to accept it.
This brings up a related point. Anonymous evaluations are against the very nature of the IETF. How can we assess the value of someone’s contributions when we don’t know who they are? Will “Reviewer 1” always be the same person? If the entire panel did not do a review, are WG members expected to treat all members as equally competent and qualified?
The WG is strongly in favor of more formal analysis. The Chairs tried to do too much and failed. Start over, respond to the feedback you got from the WG, and pick something easier.
[1] https:/mailarchive.ietf.org/arch/browse/tls/?q=triage
- [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