Re: Comments on draft-richardson-in-memoriam-00

Michael Richardson <mcr@sandelman.ca> Wed, 25 June 2025 14:55 UTC

Return-Path: <mcr@sandelman.ca>
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 473313951E0D for <ietf@mail2.ietf.org>; Wed, 25 Jun 2025 07:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_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=sandelman.ca
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 VNxNHhG-a7rn for <ietf@mail2.ietf.org>; Wed, 25 Jun 2025 07:55:25 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 BA7A73951E01 for <ietf@ietf.org>; Wed, 25 Jun 2025 07:55:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 53D8B3898D; Wed, 25 Jun 2025 10:55:25 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id WIBL7Z0_XNnR; Wed, 25 Jun 2025 10:55:23 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1750863323; bh=+hP9ZRWOxSB7XoTyM4JJ4UX7SGcXgfVqN6li+Ap/veM=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=VWAnD9nEBpdmhyiDQncFJc4u66nyizpwiv+uJa9Kqonk1v/0Ce9j9g8EvP29S109E dl/D3AapV3XC6z6TpoE0GrvKh3S1ka4rfRdO6BWfkApfDL5+uuLDp9UNP6E0n1OLES 81uYkADICpVt7MwAZZeoR+droAiX1ErNSM6836GvgJKltoXsMOfvmW2dks9VsxhixU HkFDTz6JgyXVfTSLZkf0Gb5VO1gYVwUfV63oJWUVNX1P9utkGKVv0GP92WZImD0E9R 0QX466cyOfMF/ZTe3nBSaKxccIFs/a2Bshaa0qBwWgqnjy9WNy05bgXVe63X7hrWr7 MdmqU0wMIf9YA==
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:b241:6fff:fe09:a92b]) by tuna.sandelman.ca (Postfix) with ESMTP id C25DB3898C; Wed, 25 Jun 2025 10:55:23 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id BC6591C8; Wed, 25 Jun 2025 10:55:23 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "Dean H. Saxe" <dean@thesax.es>
Subject: Re: Comments on draft-richardson-in-memoriam-00
In-Reply-To: <CAPzg_Dfks56oD+aJ-GC-N9DXYFDDw5wnyD-CusG=CYbv4Km8bQ@mail.gmail.com>
References: <CAPzg_Dfks56oD+aJ-GC-N9DXYFDDw5wnyD-CusG=CYbv4Km8bQ@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 25 Jun 2025 10:55:23 -0400
Message-ID: <26918.1750863323@obiwan.sandelman.ca>
Message-ID-Hash: UPCJJIHZAHXMUUE7LIZX7NTOBTGZLG76
X-Message-ID-Hash: UPCJJIHZAHXMUUE7LIZX7NTOBTGZLG76
X-MailFrom: mcr@sandelman.ca
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: 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/MlF0BotGrSsn2E61d4F7yB8sodk>
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>

Dean H. Saxe <dean@thesax.es> wrote:
    > Brian Campbell forwarded me this thread following your comments,
    > Michael.  I co-chair the Death & The Digital Estate Community Group
    > <https://openid.net/cg/death-and-the-digital-estate/> at the OpenID
    > Foundation.  These kinds of issues are exactly what we’re trying to
    > tackle in DADE CG.  At the moment, we’re not chartered to work on
    > protocols, so we’re working to understand what a digital estate is, how
    > it can be managed (it turns out the answer is, “it depends”), and how
    > people think about their digital estates.  I hope a next step in our
    > evolution is to move on to thinking about protocols for digital estate
    > management.

openid.net, not OASIS or ORCID :-)
I knew someone else should do it.

    > You can find DADE CG meeting minutes and other data on our Wiki
    > <https://github.com/openid/death-and-the-digital-estate/wiki> and
    > GitHub repo <https://github.com/openid/death-and-the-digital-estate/>.

    > ​

    > I welcome the IETF community to join us at DADE CG.  If it makes sense
    > to share more information about DADE CG with the larger IETF community
    > at IETF123, let me know.  I’ll be in attendance in person and I’m happy
    > to speak about DADE CG to get others involved.

We used to do these IAB plenary tech talks.  This might be a good topic.
Three slides at SPICE with a summary would also be nice.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [