[Tools-discuss] Re: Finding authors [was: sob@harvard.edu is not long for the world]

Robert Sparks <rjsparks@nostrum.com> Thu, 15 August 2024 13:43 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13D05C14F706 for <tools-discuss@ietfa.amsl.com>; Thu, 15 Aug 2024 06:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=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=nostrum.com
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 FSbjSKUvEN7h for <tools-discuss@ietfa.amsl.com>; Thu, 15 Aug 2024 06:43:54 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 66CBEC14F70C for <tools-discuss@ietf.org>; Thu, 15 Aug 2024 06:43:54 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.18.1/8.18.1) with ESMTPSA id 47FDhqMI057426 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <tools-discuss@ietf.org>; Thu, 15 Aug 2024 08:43:52 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1723729432; bh=AOV3pqTuiqTOJ5Tw/9ScQQeqkaenA8Mu8DC8TEhFLsA=; h=Date:Subject:To:References:From:In-Reply-To; b=P3//iiddZ/l/krK3bJmK0CHkTwhALwP6sv66TRrjFbPvPKxS/67F/WkATi2FpVkRo AvEkuNAAP5N1RR9i7KxgGLYd4lgiLP1cf8RdaNCzz8O1SIOoc7y4gPLl64Z4p/AK9M OuqXpTAWyyiEfPhesDtMBQdGiRa1oT9N/fgwUiKM=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Message-ID: <a27c3ebe-bf81-49ee-9405-9bb4f4b52277@nostrum.com>
Date: Thu, 15 Aug 2024 08:43:47 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: tools-discuss@ietf.org
References: <9EAE17CA-418D-48AB-9BAB-5E8F2ABF6D88@sobco.com> <a045de6c-8f09-4616-8e3a-032cab31569f@cs.tcd.ie> <8E5ECB74-746B-47DC-BC50-70CEEF3B9633@strayalpha.com> <A45F9A94-AA41-45B2-8457-0F52D0ADEAF4@terrym.net> <a27a369e-b484-4c46-88b3-af2d712b7b10@gmail.com> <CAKr6gn0frE0YqpC2KtKS90H1Cvs_AmZzzQzzYAj4oW+d_HOd_A@mail.gmail.com> <edcfd4dd-fab7-48c2-9905-336d33c763d8@gmail.com>
Content-Language: en-US
From: Robert Sparks <rjsparks@nostrum.com>
Autocrypt: addr=rjsparks@nostrum.com; keydata= xsDNBFx4PQwBDADIIJqFKIeYNmVR3iH8YnNqwApV+ci83VqFaPg0UXZAZ1utH/2O2LOLJKmV Ol11+lOSfH4OJgpARt37PWbqfG2TzzGfEucRBPMAV8TEDmzKL+7/OUMLEoPeexgxz6ADxK2Q ACKKzHhF30y4fx2fn9rYZrCvYHV9HDKcfFotNLna0U6P6wu70L0mT2hcjQgZ7+8HSZCpK2XG PTya1mEiMklH6+UHfcTLoAxd3chQiseRi19/TQZZCD3LuuaGFWyTIeF9ZNWV9yL0HQeb/XMs tmZnObSSHSUbZwn5PR9Uf+3iW7jdG5JuXBvNbDpAHfLyPXRqxErM/nCLrbwGB6AgNSKFCwkL lb3uxsGFWcOt6sedrjixoVUO2k4zQWVnCUCwFHGrgIxUK24dI8oqydGPctXAKj5VqoCVJBv6 4JxSpiR+V8fl3A8gksBUnuIMLNlRjB5RAgZaSUpaOkXsWUBA8Z75wQWoIzkJIeMm29w2l1kB B9kGMdyiXGr2JV8VQZ4lAscAEQEAAc0kUm9iZXJ0IFNwYXJrcyA8cmpzcGFya3NAbm9zdHJ1 bS5jb20+wsEUBBMBCAA+FiEEGNywdGDCHUYBwWN3bipqV3X5ExgFAmXhDnYCGwMFCQ0rmNQF CwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQbipqV3X5ExiEpwwAknrYjNHDI2l50IC1lpQB SnmCLvuu4pEESpRaBx1Te7vZBHr740dMbKQv/ZYYekw/NfFfoq2Ptguz5BXHwtyx3hKKjBUA U/rP62bl+x77yTJ0+I5k2hJ1p1DWNqXHWK3SEM0IUvjWpMGlfXPu7iVYCBGPKBDglQ4GWpzU HmSAX/8Zww6+ZbrXM0VgA+hLSHivyHextX4mJwoLRcuY99ecvkdWwFnKoDlEsKozdv9NW+QT h1rFvAtXf2ZCGwIveAMJPbHbRY3uFVp+oMvBbP7m5teffB8Ki5kuO1Y1Wqd9UPhiVDZmUuyC PXymQErskbOB6DcNSSFH7ZHuLM4V+zyziYWTT6foBv0ynA+a3Ofxo+rKPVHLybZlO9bQcI0Q TIE8yT0oqd3kWMaMIyrKZURVUpzcDgRnx6ujckLLyAC1H8L0tuntPwZOo5PAq3P7SUiWlc0L 5HbA0L//BE6eeWn6U3xOgaJNF2+YRVICNtWpXcR3Mr4k1uXW4JkE7lyoufbnzsDNBFx4PQwB DAC03e1kk41e9Z9FuVW8UKWIkVUBeH3gfJMsb94d/c0cqBMRw5rulSY7+U76rw4AXo792LZn ydjDfoL0GQxGqkrZh397Sn9P/sLCb5I+wC14251nkmh5tmU2sQqCk+g9nykcE/NJft/zFkeb HHCKAosK6glO+W0YPHc/k7nXt/fLz7dMRpFpmqFXWjeN2VtwKr9znMg9+iX6XfgAJPMdDNH8 fn30Cp5TIsn5WCI70+JztgvfjFhD15Eb3rtDdOfOydjGCV2ZVxfM8ECmc8Z3DrThyiC2M3uo 2Y50rs6MH+TmVCtpHkISnH7B+80Vy2SC60K9l2xgCaezN1SlkQy3ZpprzcDrNTI8FcJa/UUM ayMGvSDGEGuHZRaNUyXP3jQ8oss+067axmNr5vgjpf01kmE1RJtiGEDWmCr8u1SbVQjdax6C pDqq3RKoX2ZVGLtkdDYZbsqSq4TgmFukoijWRbLxsFBdeEgruTViWRw4PKZav0piLxrhHUGI m6F6JFngapUAEQEAAcLA/AQYAQgAJhYhBBjcsHRgwh1GAcFjd24qald1+RMYBQJl4Q52AhsM BQkNK5jUAAoJEG4qald1+RMYaCML/jp+3W9OedMRVk5XQ3Urxu7g09qaeAfBAArLlE7F13Xt WuGUN7JwZ8hZt8Rsx1+Uz/Zq2TIPjl8PmgIqCSkuvZrxacr+drYARtO00Af71qHVoh4gZTae iOwEuOGhhtCVI3vvKLMDv1ex0scvD4rJTsIk/zqEDCJNDVOf09Szj0CW0vJOYxrIV0sG/UoM 7Ui5/eB4tlN5AFIXuTJzo6BzaUAJVut74Ss2i93qwtwjGw44iEqPVhqKMCDYuB9+bm13ft+H Vr7viRZobd+60NTWrfZhkpmzhb4Qiib9qXhrUoa2EXqVOIy+LMQoiwjF9/iK+5FSA18c52FP ODkDgkica826W9AnBasS6gXQr0bO1BCJu84Fp2RQcjB4IFP+sKVoN3EZTByyUKK4NnSLF3lJ /G+vQhisnuJS+e+emZ8UxZBOK8upAhrhHJj0Wju2W0uTQTxlBME0/uNsvA/KaudLNhlQiUYN 7Fl3rswvQk/iD+utnQdWJbRgIsqesNXbQCOimQ==
In-Reply-To: <edcfd4dd-fab7-48c2-9905-336d33c763d8@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: PIQTHK5AGQ7ZLGQYXDHRE4OQGOEDWKCZ
X-Message-ID-Hash: PIQTHK5AGQ7ZLGQYXDHRE4OQGOEDWKCZ
X-MailFrom: rjsparks@nostrum.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Re: Finding authors [was: sob@harvard.edu is not long for the world]
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/YEXR1ehT50yfWIJtlFn13-P_uG0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

On 8/15/24 12:12 AM, Brian E Carpenter wrote:
> [Attempting to switch lists...]
>
> The topic is finding current addresses for authors of older RFCs.
>
> George,
>
> We cannot change the RFC text; that's a rule. So the solution has to 
> be external to the RFC itself. (See my comments in line below.)
>
> The datatracker already has the information needed. Taking myself as 
> an example, it knows that brian@dxcoms.cern.ch, brian@hursley.ibm.com, 
> brian@icair.org, brc@zurich.ibm.com, and brian.e.carpenter@gmail.com 
> are all the same person. Also, my datatracker profile knows which 
> address is currently primary.
>
> Therefore, writing a function that delivers current addresses for the 
> authors of RFC N, in cases where the tracker has this information, is 
> entirely possible, for people who know how to access the datatracker's 
> database. authors_of_rfc(2119) would return ("sob@sobco.com") 
> authors_of_rfc(1671) would return ("brian.e.carpenter@gmail.com")

Fwiw, the datatracker _does_ this now when sending mail (at least in 
almost all of the places it sends mail). As part of the RPC tools 
modernization project, we will make it so that when the RPC sends email 
it does the same thing.

Remember that there may be no usable address, especially for deceased 
authors.

RjS

>
> So we could have an API and a web tool for this.
>
> Whether the effort for this is justified is for discussion.
>
> On 15-Aug-24 15:19, George Michaelson wrote:
>> I think I must misunderstand what you're trying to say, because this
>> reads as the other half, and does not address what  I think Terry
>> proposed: The embedded values in the RFCs are held to be immutable,
>> but these contact strings are anything but immutable, as we all know.
>> user@host is not a constant which alters the normative force or
>> semantics of a document, its a reference to the authors.
>
> It doesn't matter. Published RFCs are immutable. This can only be handled
> as metadata.
>
>>
>> If the author reference in an RFC was abstracted to a DOI or an ORCID
>> or similar, noting Phils comments to the need to make it trustable
>> through cryptography, then the document suffers no loss of
>> information, when the user@host has to change. That crytographic
>> management is btw completely outside the RFC process. It manages a
>> value expressed into an RFC.
>>
>> An abstracted contact ID could be external, or could be internal. I
>> prefer internal, managed inside IETF process, and amenable to an XML
>> definition so it can be tokenised properly in the web display and
>> datatracker.
>
> s/IETF process/RFC Editor process/
>
>>
>> Ie its not "listing the emails" its tying the identity information of
>> the author to something outside of the RFC which can itself remain
>> substantively immutable, when emails change.
>
> Certainly one could imagine this added to the metadata for an RFC,
> but that would be a complicated discussion over in RFC Editor land.
>
> Regards
>    Brian
>
>>
>> G
>>
>> On Thu, Aug 15, 2024 at 11:47 AM Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>>>
>>> Terry,
>>>
>>> We effectively have that already. Try these:
>>>
>>> https://datatracker.ietf.org/person/sob@harvard.edu
>>> https://datatracker.ietf.org/person/terry@terrym.net
>>> https://datatracker.ietf.org/person/brian@dxcoms.cern.ch
>>>
>>> The only issue I see is that if you have no formal role (lucky me!), 
>>> no current email address is listed. That could be an option in the 
>>> user's profile, or "author" could be added as a new role. (If you 
>>> like that, we could discuss it at tools-discuss@ietf.org)
>>>
>>> Regards
>>>      Brian Carpenter
>>>
>>> On 15-Aug-24 11:46, Terry Manderson wrote:
>>>>
>>>>
>>>>> On 15 Aug 2024, at 7:54 AM, touch@strayalpha.com wrote:
>>>>>
>>>>> Although I appreciate the impact this has to our RFCs, we all 
>>>>> experience this (touch@isi.edu is no more as well), though perhaps 
>>>>> not to the same degree.
>>>>>
>>>>> I’ll step in here to defend Harvard’s decision; having an email 
>>>>> available to someone who no longer holds an official position is a 
>>>>> significant legal risk.
>>>>>
>>>>> Emails, URLs, and even RFC numbers change (remember back when TCP 
>>>>> was “always” RFC793?). Search engines mitigate this problem, as 
>>>>> would (preferably) a bounce message from Harvard providing the 
>>>>> next known email, at least for a while.
>>>>>
>>>>> Joe
>>>>>
>>>>
>>>> I'm looking at this from the impact to the RFCs and the link 
>>>> between RFC authors and other inquisitive minds. Especially while 
>>>> the author is still interested in responding to email questions.
>>>>
>>>> I wonder if a level of abstraction can be created through an 
>>>> "author profile" that ties together all past author's address 
>>>> blocks and can provide the "latest known" address.
>>>>
>>>> Just a thought.
>>>>
>>>> Cheers,
>>>> Terry
> -----------------------------------------------
> Tools-discuss mailing list -- tools-discuss@ietf.org
> To unsubscribe send an email to tools-discuss-leave@ietf.org
> https://mailarchive.ietf.org/arch/browse/tools-discuss/