[TLS]Re: Consensus call for RFC8773bis Formal Analysis Requirement
Deirdre Connolly <durumcrustulum@gmail.com> Sun, 25 August 2024 21:21 UTC
Return-Path: <neried7@gmail.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 B354EC14F736 for <tls@ietfa.amsl.com>; Sun, 25 Aug 2024 14:21:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level:
X-Spam-Status: No, score=-1.855 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 KI_QI4EaA26g for <tls@ietfa.amsl.com>; Sun, 25 Aug 2024 14:21:55 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 ietfa.amsl.com (Postfix) with ESMTPS id C6954C14CEE4 for <tls@ietf.org>; Sun, 25 Aug 2024 14:21:55 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-5c0abaae174so306275a12.1 for <tls@ietf.org>; Sun, 25 Aug 2024 14:21:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724620914; x=1725225714; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3Rc3HYhSC750LpIunr/cCzlC9wYslJZkkAXwStsTJx4=; b=RGi5l8fuzh7f3uxI0rm/D8qcuvUf+GTypDoIhv6tllZaC/d4avt52n05E3kE1g+tjQ hb2gfeM85D/JEzfefb8c02FXhAT1Anz8ZrZOaozPmGOJljKESgPZ4crQU10+ddMPGPzM 8q/XS9rPaA98q7KcZR2513YPDyxPo584Xx21+vCV2jJkFV91KraSglg4uD6pS0cGE8Xd 2SWw1yYxvpv/FsRxgPtebej2V37PsJhw1nKDGVSR0cvbtR8Ms8cNG0aFh+ZQZ3eexsX8 IEOU5sC6hCAsUn26M62QW5Z0MS4g6EctqgljwKNnLOmt4C0Z2IdD3TdcyVdMgeojrJg7 sWsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724620914; x=1725225714; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3Rc3HYhSC750LpIunr/cCzlC9wYslJZkkAXwStsTJx4=; b=DSdol2ABe6vJ0JZRV8rtLFH0NhosQT4yx5nIMlXsbbGQ+1SCscqnHraF1e5gNbrVE0 73buQgOXUACzxY9PZN309u7geDib52046cROJ3iLffTUb/x5k1mRt2cpxvcdbE6bawYz mFx9LDGKggx4eIGRDXMjUFG/g3vljtmC2bcDsLNdVMlUHwfRoYoxeHSn7cvIyFiH4Sip aFRRJdeJrw2BD/AfXUIGB7ZWmZeFxIgrCiAVkSTV0CpGBWFYwaYv/qeLsn+6ruB8fb26 tUDkPk2GNLCnlF9KBz73a6wmVfWff/mNVgf9Im4lScSdy0tpCOwt6YvBdYx5FeRDgsTx fDFg==
X-Forwarded-Encrypted: i=1; AJvYcCWYjSpC8gs8l1ejBbeq3fK8JuxNNfNGB7AUg1RkV8VRzbnf+7EnPwjIClhEPzMCa9W/Nmo=@ietf.org
X-Gm-Message-State: AOJu0YyEYzxgj3L4rxOmMnTOJeV8MEqXaEQ51x1UBXMMvPHpCUTp2faS RRTirq1WvEmsO+N+BaFYKVDmhnf/kBuGWL5QrYWf/D3/+m9K/7Jfmh/E1Pnk9rmwHf8ndqNdVXa R+1CYaf1andwR2n0uIEfjloe+SOU9o+AP
X-Google-Smtp-Source: AGHT+IF72tMpNU7ymW1CPSf4SmCyxnn4ZGYBjHTvK4eFyCMsfWESposOFtIusrlsoeQ31UUEjkJnj+c/DS+9g3l7PgA=
X-Received: by 2002:a50:cb86:0:b0:5be:f1a7:c2cd with SMTP id 4fb4d7f45d1cf-5c0891afa15mr4554226a12.31.1724620913238; Sun, 25 Aug 2024 14:21:53 -0700 (PDT)
MIME-Version: 1.0
References: <1E84DBF8-CA48-4CA9-A435-9E61E981D8DF@akamai.com> <6284E288-4F8E-4E2A-8335-5054D9D7A6DF@obtuse.com>
In-Reply-To: <6284E288-4F8E-4E2A-8335-5054D9D7A6DF@obtuse.com>
From: Deirdre Connolly <durumcrustulum@gmail.com>
Date: Sun, 25 Aug 2024 17:21:15 -0400
Message-ID: <CAFR824xAxfUFrXyo5PZckJPqoM3fU8ESNrDHUfOKNzDF_jJZQA@mail.gmail.com>
To: Bob Beck <beck@obtuse.com>
Content-Type: multipart/alternative; boundary="000000000000e7e922062088986a"
Message-ID-Hash: NANLOYELX6U25IQXELNIPZ5XXYFK6XQJ
X-Message-ID-Hash: NANLOYELX6U25IQXELNIPZ5XXYFK6XQJ
X-MailFrom: neried7@gmail.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: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, tls@ietf.org
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/yEjZvN6WnqY-CFLoLil79pc2csA>
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>
> Anonymous reviewers have a number of problems The current triage panel is not anonymous, and the feedback they gave on RFC8773bis included the complete input from all current members. On Sun, Aug 25, 2024 at 4:51 PM Bob Beck <beck@obtuse.com> wrote: > > > On Aug 25, 2024, at 13:56, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> > wrote: > > > > I am opposed. Anonymous email recommendations are not how the IETF > operates. > > > I would also count myself as opposed. While I understand and am > sympathetic to a reviewer possibly not wanting to get deluged in email or > opinions unrelated to the task at hand, I think if this is truly a problem > it is symptomatic to participation in a working group as a whole and should > be addressed across the board for everyone. Anonymous reviewers have a > number of problems as Rich has pointed out. > > > > 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> > *Date: *Tuesday, July 30, 2024 at 1:49 PM > *To: *"tls-chairs@ietf.org" <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 mailing list -- tls@ietf.org > To unsubscribe send an email to tls-leave@ietf.org > > _______________________________________________ > TLS mailing list -- tls@ietf.org > To unsubscribe send an email to tls-leave@ietf.org >
- [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