[saag] Re: New Version Notification for draft-rsalz-crypto-registries-00.txt

"D. J. Bernstein" <djb@cr.yp.to> Fri, 29 November 2024 21:03 UTC

Return-Path: <djb-dsn2-1406711340.7506@cr.yp.to>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55641C1840F3 for <saag@ietfa.amsl.com>; Fri, 29 Nov 2024 13:03:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.203
X-Spam-Level:
X-Spam-Status: No, score=-0.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, THIS_AD=1.7, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 R4rQszD50nFC for <saag@ietfa.amsl.com>; Fri, 29 Nov 2024 13:03:13 -0800 (PST)
Received: from salsa.cs.uic.edu (salsa.cs.uic.edu [131.193.32.108]) by ietfa.amsl.com (Postfix) with SMTP id 51747C180B50 for <saag@ietf.org>; Fri, 29 Nov 2024 13:03:13 -0800 (PST)
Received: (qmail 9105 invoked by uid 1010); 29 Nov 2024 21:03:11 -0000
Received: from unknown (unknown) by unknown with QMTP; 29 Nov 2024 21:03:11 -0000
Received: (qmail 1108190 invoked by uid 1000); 29 Nov 2024 21:03:02 -0000
Date: Fri, 29 Nov 2024 21:03:02 -0000
Message-ID: <20241129210302.1108188.qmail@cr.yp.to>
From: "D. J. Bernstein" <djb@cr.yp.to>
To: saag@ietf.org, jay@staff.ietf.org, ombudsteam@ietf.org
Mail-Followup-To: saag@ietf.org, jay@staff.ietf.org, ombudsteam@ietf.org
In-Reply-To: <5BABAD65-5F55-4D0B-B3FC-5DDE677C949B@aiven.io>
Message-ID-Hash: F2Q53QHH7WTQLIGGQY3DQDDUFQ7EFJZ2
X-Message-ID-Hash: F2Q53QHH7WTQLIGGQY3DQDDUFQ7EFJZ2
X-MailFrom: djb-dsn2-1406711340.7506@cr.yp.to
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-saag.ietf.org-0; header-match-saag.ietf.org-1; 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: [saag] Re: New Version Notification for draft-rsalz-crypto-registries-00.txt
List-Id: Security Area Advisory Group <saag.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/kL12FZxPUpyrWItH_NsAwKq9i8o>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Owner: <mailto:saag-owner@ietf.org>
List-Post: <mailto:saag@ietf.org>
List-Subscribe: <mailto:saag-join@ietf.org>
List-Unsubscribe: <mailto:saag-leave@ietf.org>

Paul Wouters writes:
> personal attacks

No. ADs are official IETF roles. It is not a personal attack to state
that an AD, after indisputably being informed that a WG adopted an NTRU
Prime document, issued false claims of IETF consensus "that there is no
appetite for NTRUprime". It is not a personal attack to summarize this
AD action as fraud. These are complaints about official IETF actions
that the IETF corporation (ISOC etc.) is liable for under antitrust law.

I had tried simply pointing out the facts; Rich Salz also spoke up. The
AD response at that point should have been to issue an erratum. Instead
the AD response was to double down on the same fiction. Clear warning
labels seem necessary to prevent this AD disinformation from warping
subsequent SAAG discussions.

For comparison, here's an example of one of the personal attacks issued
earlier in the thread by the AD, in violation of BCP 54: "you seem to
want to have the benefits of the IETF process while skipping the IETF
process that yields that value to the community".

> > You're on record claiming, e.g., that "the cryptographic research
> > communities are focusing on NIST candidates ... Should the IETF really
> > recommend a dropped candidate at this stage? I do not think so".
> again, misquoting

https://mailarchive.ietf.org/arch/msg/saag/9e1QheO1L6SVBX3a8mFSij9AgHw/

The quote is perfectly accurate, and the surrounding message expresses
the same do-only-what-NIST-does position in more detail.

---D. J. Bernstein