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

Paul Wouters <paul.wouters@aiven.io> Fri, 29 November 2024 15:29 UTC

Return-Path: <paul.wouters@aiven.io>
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 E2E79C169424 for <saag@ietfa.amsl.com>; Fri, 29 Nov 2024 07:29:39 -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 (1024-bit key) header.d=aiven.io
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 eeoNhPaKzU3F for <saag@ietfa.amsl.com>; Fri, 29 Nov 2024 07:29:35 -0800 (PST)
Received: from mail-ej1-x642.google.com (mail-ej1-x642.google.com [IPv6:2a00:1450:4864:20::642]) (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 CF174C14F6B7 for <saag@ietf.org>; Fri, 29 Nov 2024 07:29:35 -0800 (PST)
Received: by mail-ej1-x642.google.com with SMTP id a640c23a62f3a-aa5b0d8bd41so94124466b.2 for <saag@ietf.org>; Fri, 29 Nov 2024 07:29:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aiven.io; s=google; t=1732894174; x=1733498974; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=2L2QnNK/rQsewtl15ncfGIkk+nohnZvnAVxY+7l8I+k=; b=YQLbCxLkvU68OG+21U73Kv8XxHKpKKmhes1qwLHzlldy/t0Trz2l29U9D3rzeiNo30 E4PNoj6tiMPaICg7ZR5CaRdOxeIbQb7Ud7lBvYR00/pC7YB65fcBepq0KT6sy2llvpT9 RukXYOwqSxXuycpgUH3pY13Lo7TN0kBs+PVk0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732894174; x=1733498974; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=2L2QnNK/rQsewtl15ncfGIkk+nohnZvnAVxY+7l8I+k=; b=g6KlITU2sPRPt3rqZEgop92yHVmjxgXaf2CYT8zrbzKJU/xitWt3ik48u/p37n8Ntv GyCH44Nbr/cGJ3M3Fk2T9KEuC+4n7ksYVLrpCxQLgTDmASdWLBfPItvQMnFY7Inv559A Aag2455IKUnR7O8d7U9qX9Y1YtgGMCUYR5xlR9Xih+7AICUFhlNYDDo5SOay9Q/IDQj0 tvlXAt6QrjnpevMr8KQJUWU56UmXIPqMr1P6vJArz/2ZTGCwo/k74WSGqluPdRJdMS9q dXU9sTnbuHA+HP2sFQm0VwoyiB2fEzLOmNXv5g0nmmbOCTLRhKJUX94iYKraDvxVmooa 3j2Q==
X-Gm-Message-State: AOJu0YxdUPqbvMJYTHvZsLWBQRX0KAjGz/BVxoMTbj9Hw1sEj5JueTeq Gu+qODyxxgk/BzCdRJQINqNZMeNgRDnG81xsy4XMb1PouynYcxpqQ+Q9PZDt+oKWBBI/2ZbULuh +4tOA9Q==
X-Gm-Gg: ASbGnctBnystFE6ETlMCS06rzmrcO5gqe0NdX4sXvl8Df0VRddM8QxBNmhWySG/ymU9 kIoWi+DTYMOFdZhoEiqeTVUYingTgpYG79tlWYigI5Qg2MY9fi2AHyfD6j1ih8X7qzIpirRQRvM /J3NoEAUgH4SsFvdi8k6K0DMfXxThSuQQa3dsh3bMwniYEmrh5LbS2P1UjrqE9k1e3IKZmxh7Rt HCS8y66g2FecLmh1Wd81LftmS22bWTumHV9y9clhU9i265FnaEroTgMGFZ9/8SuZm0=
X-Google-Smtp-Source: AGHT+IFn+0TQ9bVxARwGeQHjRAaHseRHC6vjOVjhMErj+XP4jheaptBHWxX5rQAeRxOsJ1ob4UKxhg==
X-Received: by 2002:a17:906:9c1:b0:aa5:3b94:78e9 with SMTP id a640c23a62f3a-aa580f57517mr850525966b.33.1732894174363; Fri, 29 Nov 2024 07:29:34 -0800 (PST)
Received: from smtpclient.apple ([74.122.52.94]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-aa5998e6d8bsm185240266b.107.2024.11.29.07.29.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 Nov 2024 07:29:33 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
From: Paul Wouters <paul.wouters@aiven.io>
Mime-Version: 1.0 (1.0)
Date: Fri, 29 Nov 2024 10:29:20 -0500
Message-Id: <5BABAD65-5F55-4D0B-B3FC-5DDE677C949B@aiven.io>
References: <20241129144655.1089022.qmail@cr.yp.to>
In-Reply-To: <20241129144655.1089022.qmail@cr.yp.to>
To: "D. J. Bernstein" <djb@cr.yp.to>
X-Mailer: iPhone Mail (21H16)
Message-ID-Hash: 4MSC55TQUSZ3R473LW247PBN64GLUBAL
X-Message-ID-Hash: 4MSC55TQUSZ3R473LW247PBN64GLUBAL
X-MailFrom: paul.wouters@aiven.io
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
CC: saag@ietf.org, jay@staff.ietf.org, ombudsteam@ietf.org
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/voBrfB4O5RKH2tt011KKbLt-jNE>
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>


> On Nov 29, 2024, at 09:47, D. J. Bernstein <djb@cr.yp.to> wrote:
> 
> 
>    * an AD, after indisputably being informed that a WG has adopted an
>      NTRU Prime document, issuing false claims of IETF consensus "that
>      there is no appetite for NTRUprime".

Please stop willfully misinterpreting what I say. As i explained a few times now, i am talking IETF wide. not just SSH.

These type of personal attacks in why a lot of people refuse to engage with you at all publicly. Continuing to do so will add me to that list.

> Very similar fraud

i am CC:ing the ombudsman to notify them that you are publicly accusing me of fraud. This is unacceptable behaviour and violates the IETF code of conduct.

>>> Instead the ADs seem to be _encouraging_ having Kyber as
>>> the only post-quantum encryption option.
>> That is willful misrepresentation.
> 
> 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 and on top of that equating "dropping candidate X" with "no candidates whatsoever". Again, willfully misrepresenting what I said.

> The
> only PQ encryption mechanism that NIST has standardized is Kyber, so
> this do-only-what-NIST-does position is encouraging Kyber as the only PQ
> encryption option for IETF too.

i never said "only do what nist does". please cite with link (not scary quote!) where i said we should only do kyber.

> You're also on record responding to the Kyber patent mess by claiming,
> e.g., that the "process for deciding on cryptography is a separate
> process" somehow exempting cryptography from BCP 79. You didn't back
> down on this claim even after
> 
>    https://mailarchive.ietf.org/arch/msg/saag/pKLdOqJpiyZDIrqJjrFuD65tWUc/
> 
> gave a quote from Scott Bradner to the contrary. Ultimately what matters
> is that you seem to be letting Kyber specs sail through while throwing
> obstacles in the way of other options.

"I" am not doing any of these claims unless your claim is "disagreeing with someone is the same as throwing obstacles in someone's way". Your indirect claim of me abusing a leadership role is reprehensible. If you have an actual case of abuse, you should file your case with the IESG or the IAB.

Note I am technically one of the moderators of the saag list. If you had written this email targeting someone else, I would have taken moderation actions based on the abusive and misleading content of this email. I am not taking such action to avoid any appearance of a conflict of interest (but adding IESG and ombudsman to CC: for visibility)

Paul