[Tools-discuss] Finding authors [was: sob@harvard.edu is not long for the world]
Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 15 August 2024 05:13 UTC
Return-Path: <brian.e.carpenter@gmail.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 088E5C18DB8E; Wed, 14 Aug 2024 22:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, FREEMAIL_FROM=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_BLOCKED=0.001, 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 (2048-bit key) header.d=gmail.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 5E_D3D6eZOsD; Wed, 14 Aug 2024 22:12:58 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 30B0BC180B51; Wed, 14 Aug 2024 22:12:58 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id d9443c01a7336-1fc611a0f8cso5071235ad.2; Wed, 14 Aug 2024 22:12:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723698777; x=1724303577; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=mfRLqkCaHAGP79+W+wvOHvlMIN2H7xqGHC3vqMMsXA4=; b=dZ5/2b5n8t37uu7ESjzniUalqInzCiZjigGU2ccZGUtR63EyFrdqsfVi0zb49DoO3n Gma1mAkRiw/vHqaIVbm01e2O/g4LYOewtVuQ/N5I/byV0bwXotWlRWS5LMhIkWWRkj/h IuOWN6SVO8IztbKcaAHBNRgTk3ZA+5iVPV9iiVIoZ5HCx03ufhnTOKH+s4NHep5OwQGS HeIXuINPSK8XpAljcH28PWfC8/U+BodrlucVuwZPmDIygeqWK5VktozZCfQKwfdaEXW2 HX3hf3g+EVeNRmOABjKk9wt64iyfDf+B8OGtgr3pyflVh+b7r6O7aI4e1vtknO4OvnrM 9zOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723698777; x=1724303577; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mfRLqkCaHAGP79+W+wvOHvlMIN2H7xqGHC3vqMMsXA4=; b=FUZNauIm9z25d8y/TYaZFvb53bDzjipCOTuilRaYqQwkpKdRbfMnan+r+SowiBElKO Wa4Ssdo4G0p3VUp9leYv0fqiUEhcd6RxiF0I6DRYvvE662qKlKGU1vxlxZtrCDYA7kbP WYsZk/O1WfLXCjb6c/5r/31G5ampYPuKZyoc2yz/HlawStdtm2V71fYo4OZnZznWjRgI 7z/HX9POcKEIOUpnTOZc3ASn0ZT1yrMI0LE+NdM1m3KTbE+wY01tBeC0lHZeE0wr7fa+ 8SC3TZfhHvfK2ncwhqdwOqtr2HQjRD+zlQwIKR6GdFWuZXQbW4vtEFucHyyI/J36FDEJ CAxg==
X-Forwarded-Encrypted: i=1; AJvYcCXQi3aUVMbZFCUWtn2gJruydwFr8YHJWQhp5Oxn7eArzunFQNT220+7p+aeZkQ0eyUeF0DFMJCJYNSHloi/
X-Gm-Message-State: AOJu0YxIoz5x6rUE0q2qSM42mI/cP764er8lMHU4Ncno2X21xiCMU2N6 6IOsjd7QIr6u+sID6cMZAKZCFYsoQxVpP4tC7E949O48VBwhuw6jpGkANw==
X-Google-Smtp-Source: AGHT+IE7e3/QXQ7uGdHp//Ia/SD1u85x9CQkoW6O4Fi11Xzl4xPZHrMLqsVLRL//Qxz5qEkitPAMOw==
X-Received: by 2002:a17:902:d2cc:b0:200:7d10:b889 with SMTP id d9443c01a7336-201d6588eaemr70319905ad.57.1723698776989; Wed, 14 Aug 2024 22:12:56 -0700 (PDT)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-201f03a4c28sm4266855ad.287.2024.08.14.22.12.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 14 Aug 2024 22:12:56 -0700 (PDT)
Message-ID: <edcfd4dd-fab7-48c2-9905-336d33c763d8@gmail.com>
Date: Thu, 15 Aug 2024 17:12:52 +1200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: George Michaelson <ggm@algebras.org>, Terry Manderson <terry@terrym.net>
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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CAKr6gn0frE0YqpC2KtKS90H1Cvs_AmZzzQzzYAj4oW+d_HOd_A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Message-ID-Hash: WAFPKJIJPXA36IJDIO3TURQILUHT5RLJ
X-Message-ID-Hash: WAFPKJIJPXA36IJDIO3TURQILUHT5RLJ
X-MailFrom: brian.e.carpenter@gmail.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
CC: Tools Team Discussion <tools-discuss@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] 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/BRIkL_MQDk36AUhrMrFpl_SEiKI>
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>
[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") 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] Finding authors [was: sob@harvard… Brian E Carpenter
- [Tools-discuss] Re: Finding authors [was: sob@har… George Michaelson
- [Tools-discuss] Re: Finding authors [was: sob@har… Robert Sparks
- [Tools-discuss] Re: Finding authors [was: sob@har… Toerless Eckert
- [Tools-discuss] Re: Finding authors [was: sob@har… Brian E Carpenter
- [Tools-discuss] Re: Finding authors [was: sob@har… Jean Mahoney