IETF Logo Mail Archive

[saag] Re: Suggested Project

Randy Bush <randy@psg.com> Mon, 09 March 2026 17:27 UTC

Return-Path: <randy@psg.com>
X-Original-To: saag@mail2.ietf.org
Delivered-To: saag@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A1767C70889C for <saag@mail2.ietf.org>; Mon, 9 Mar 2026 10:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=psg.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vOqO7tyglXSP for <saag@mail2.ietf.org>; Mon, 9 Mar 2026 10:27:04 -0700 (PDT)
Received: from r.rg.net (r.rg.net [IPv6:2001:418:3807::18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D7525C70872F for <saag@ietf.org>; Mon, 9 Mar 2026 10:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=psg.com; s=rgnet-mail; t=1773077195; bh=Si7n5nnjQEC5E7V03gpkRxiwV/fkDEF6dOsKrHnWelY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=JiZaCK7ugy8GM9pziSq0BXybzHLNw4N02se9/ybPXck7+/JZKi4hGBmt8Z3c7iptL WU5vGazokbtRbNxqe0FIio50GiGXoQTXRHT/9mK+slOylrZV2zKiO5dBBQ4manW0LC 8TzqWVs+kbEMeVCmhy6Chm9vJGsJFTjYygwlNcCLnAev2nwFDciHaXlMcC69GPVDf7 gyfgO8dUKv+ZLPP/WCMxveI18StytZag5CbZaGpAkPrW9t7zf0SfiKKtR/azBIfYQ4 EKxVkVSJrY/Z80iQedNYWOiNCP/87fvPJJaDl8y4OpL35KUY7nrIIkPqucEYcOGceO O854+y+V4UNew==
Received: from ryuu.rg.net (localhost [127.0.0.1]) by r.rg.net (Postfix) with ESMTP id E04EF80566; Mon, 09 Mar 2026 17:26:34 +0000 (UTC)
Date: Mon, 09 Mar 2026 10:26:34 -0700
Message-ID: <m2zf4gx6b9.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Eric Rescorla <ekr@rtfm.com>
In-Reply-To: <CABcZeBPOUfHE+P7aFh3p-vWVEegYu8JBMjO6CApJnScJ+eWp6g@mail.gmail.com>
References: <000e01dcaf32$3910a510$ab31ef30$@JoeChiarella.com> <CABcZeBM5pfdDt0SzCu5d37PLDMxm0-OpKQcx9xYhrktmemrujA@mail.gmail.com> <42337cd7-ffbd-48c9-92dd-67ec08a1aaaf@nthpermutation.com> <CABcZeBPOUfHE+P7aFh3p-vWVEegYu8JBMjO6CApJnScJ+eWp6g@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Message-ID-Hash: E7WX7TWMLU53W7NTDADIJVCDVTQBWTWZ
X-Message-ID-Hash: E7WX7TWMLU53W7NTDADIJVCDVTQBWTWZ
X-MailFrom: randy@psg.com
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: Security Area Advisory Group <saag@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [saag] Re: Suggested Project
List-Id: Security Area Advisory Group <saag.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/MLoGSl6tyAdVSLdS_9WbXNxNXpw>
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>

> It seems like we'd want some evidence that either (1) manufacturers
> were interested in broadcasting such a signal or (2) regulators were
> interested in requiring it.

and here i thought standards were for users (those pesky critters) to
get vendor choice because of compatibility

perhaps the world is not only for vendors, regulators, and billionaires

randy

v2.46.0 | Report a Bug | By Email | System Status