Re: memorial RFC

"touch@strayalpha.com" <touch@strayalpha.com> Fri, 12 December 2025 17:59 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 93E6399C0E2A for <ietf@mail2.ietf.org>; Fri, 12 Dec 2025 09:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, 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=strayalpha.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 aGfHBmghsJ_p for <ietf@mail2.ietf.org>; Fri, 12 Dec 2025 09:59:47 -0800 (PST)
Received: from server217-4.web-hosting.com (server217-4.web-hosting.com [198.54.116.98]) (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 D2B2699C0E21 for <ietf@ietf.org>; Fri, 12 Dec 2025 09:59:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=GcYjIgiEPpYlfjrqJovm9yvmR6dQTsxKLZGOI/tUWPA=; b=dBbnjh1jqWM+Qk71JpSBwEQx0I 1Ff+WH8ON+4zBe1DanYdpVfIA9nJ6Vk0naX2dYSWkHeSRTIuPX48Kf7209RelSGeNTCs/8o5+Vp43 +nKDhssrebN3bHlReZjUOLwoFcyTC3XamLn0aW1W5kvbLO/3KKQxpJXM89MXDOlQ18BcGpKVUNFa5 kRKB9mjkc6SUxtwi/cARqQetX7Ddtm9O+0o/ukpiyInONosS0lOUsoeC0kyTIcKRemRw02c+0Xfkg CjY9KxwUwx4ogpRIYLpw5x7qkv5QpyEqs4iNrfxEkrXf71bClOhvGPFwzpfgrKwniMeZDUBjxKoAN 0FFX8+aQ==;
Received: from [172.58.213.52] (port=24866 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from <touch@strayalpha.com>) id 1vU7Qa-000000060Xn-01VF; Fri, 12 Dec 2025 12:59:39 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_B2784B9A-0E18-49A9-9C01-58E42ED876C1"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.200.81.1.6\))
Subject: Re: memorial RFC
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <974756CD-443E-48A3-855D-82106C3121C7@gmail.com>
Date: Fri, 12 Dec 2025 09:59:20 -0800
Message-Id: <1C9A4E6C-2B49-4331-9CA2-9CEBAFD0B856@strayalpha.com>
References: <CAMm+LwiETcVBjiJ0wtQdj9on947iCWFYSXkfwVPhzU4RdCC1tA@mail.gmail.com> <974756CD-443E-48A3-855D-82106C3121C7@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.3864.200.81.1.6)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
X-Rspamd-Queue-Id: 1vU7Qa-000000060Xn-01VF
Message-ID-Hash: 6F6TIHXWX4RR4BUSCUO62FRKGWRCB6W6
X-Message-ID-Hash: 6F6TIHXWX4RR4BUSCUO62FRKGWRCB6W6
X-MailFrom: touch@strayalpha.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Phillip Hallam-Baker <phill@hallambaker.com>, Theodore Tso <tytso@mit.edu>, John C Klensin <john-ietf@jck.com>, Lixia Zhang <lixia@cs.ucla.edu>, ietf@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Mt3fAF7O8lbDiRuclFqYWEVWCbo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

The IESG is chartered with technical oversight, not award leadership, AFAICT.

E.g., the ANRP is awarded by a separate committee. The Postel Award is decided by a committee at the ISOC level.

I am not aware of any award the IESG is chartered to bestow, so this seems outside their purview, IMO.

Joe

—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com

> On Dec 12, 2025, at 9:44 AM, Stewart Bryant <stewart.bryant@gmail.com> wrote:
> 
> The way we normally solve this type of problem is to delegate it to the IESG to decide on our behalf.
> 
> I think memorials need to be strictly reserved for those that have made an outstanding contribution to the work of the IETF.
> 
> Stewart
> 
>> On 3 Dec 2025, at 17:49, Phillip Hallam-Baker <phill@hallambaker.com> wrote:
>> 
>> 
>> If we go down this route, we are going to end up with the Wikipedia problem of determining significance. And then we will have the bike shedding over whether Igor Thrub made sufficiently important contributions to the WGAF protocol to deserve recognition.
>> 
>> I suggest that we reach out through our academic friends to see if there is a group of historians who are interested in picking up the subject while most of the principals are still alive. 
>> 
>> 
>> 
>> On Wed, Dec 3, 2025 at 12:13 PM Theodore Tso <tytso@mit.edu <mailto:tytso@mit.edu>> wrote:
>>> Stepping back a bit, we haven't formally stated what the requirements
>>> should be for the "In Memoriam" RFC/web page/whatever.
>>> 
>>> Perhaps as a result, when we've been discussing the idea, people also
>>> seem to have their own ideas of what might be contained in the "In
>>> Memoriam" document.  Is it just a list of names?  Names and photos,
>>> ala what is done with Oscar / Tony award shows?  List of RFC's,
>>> working groups, done by the person being remembered?  Paragraph-long
>>> rememberances of people who had fond memories of the deceased?
>>> Perhaps not-so-fond remembarances of people who are fond of launching
>>> IESG / IAB appeals?  Links to all of the appeals that someone has
>>> launched?  :-)   etc.
>>> 
>>> This is making discussions of whether this should be done at all to go
>>> round and around a bit, in my opinion.
>>> 
>>> If all we want to do is to state that someone is no longer around to
>>> answer questions, then something in the data tracker indicating that
>>> they have no valid e-mail addresses is sufficient.  If the requirement
>>> is more than that, then what needs to get done starts to get more
>>> complex, and I suspect, more controversial.
>>> 
>>>                                                         - Ted
>>>