Re: [Tools-discuss] datatracker, I-Ds, and email addresses

Jay Daley <exec-director@ietf.org> Wed, 31 May 2023 09:49 UTC

Return-Path: <jay@staff.ietf.org>
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 995CCC1519AB for <tools-discuss@ietfa.amsl.com>; Wed, 31 May 2023 02:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.895
X-Spam-Level:
X-Spam-Status: No, score=-6.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=ietf-org.20221208.gappssmtp.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 oh9L2Pjvqww0 for <tools-discuss@ietfa.amsl.com>; Wed, 31 May 2023 02:49:19 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E2FFC15108B for <tools-discuss@ietf.org>; Wed, 31 May 2023 02:49:19 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-4f3b9e54338so6605390e87.0 for <tools-discuss@ietf.org>; Wed, 31 May 2023 02:49:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-org.20221208.gappssmtp.com; s=20221208; t=1685526558; x=1688118558; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=0peQyFvRq2P4b7kg276IZ8U++CrliApOWHwiBNEJ2So=; b=ViO2LBnTRrMdAFxnOuHm/1APWELjfoeEqh6Afsrq3CgzNClz3fmNpnV1m4eGFqwoex byogHgF9+QKoVa26FtVjdhi7uCJ8vlBcJQxfyaKKOjk+Ly7SpS5XqSEJxwkMt9Q8SWVo 1DQhmLjn/f60WMqjxTwAAmvlSt06oD+GdrMfkblmiLlVK5buDWfhNQrTQR2IskKIjjSI A1aI3JYEsSRMM7GxiGRCoLhL4+zSAUMVZtcvUlePtcxujQgl3CIUEoHDjbqm1+JmAV1U ly9fNSJvwXHQRHCARYCK11Nvu3PvmOEA3tc/++Md8Dk5ROnhWoI+oKdOWDUQHCCS2fAj p1qQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685526558; x=1688118558; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=0peQyFvRq2P4b7kg276IZ8U++CrliApOWHwiBNEJ2So=; b=jMYuoudQDmFPbMGQk39YySGi3hXomuRc7tI4qZrCJJISrHEslQelRUOUrWIA7M4kXx 2hkAtwsN4w815QeI02t4OLUBpwiLmemm6cdUk4UrOtTrfxlGXug5gbHpNZNNUvhOtkAM Qsa1DdDPQQLM4GaULWrlSzzkPNNY3vwcJItxPaXJ+SMuqudWT39yG+C7Z70gpPZrN6sG QAUy8xD3ookux2A93vFIcLW8a8iZQyQpELagYrPyH+fPZUrwg/YiJJsIBxhrk2nY2iMj ifO/KCXg6qGMenQNGpa+LsoAXxDLHsbBg4MMbcfZQxjreif3ZvXY5TpwCmsSc2IuTaBC jwVQ==
X-Gm-Message-State: AC+VfDw7U3ZxKs39hm9xrWVGnh7IU3mMw7Kbban/XVpuQxjeiPfkWd20 Hgs6UQay+2zdX0MspLRwwUKPCLqiABBkl6f56fZCmSbP
X-Google-Smtp-Source: ACHHUZ5Yqx/tQ994CK8eKErEHDFTtuloJdgq6v7z2R65oM6tteNL0ZacVieqXi8tXxLDlcGv26ha9w==
X-Received: by 2002:a19:7402:0:b0:4f3:789c:8bcf with SMTP id v2-20020a197402000000b004f3789c8bcfmr2279446lfe.4.1685526557592; Wed, 31 May 2023 02:49:17 -0700 (PDT)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id r15-20020adfda4f000000b0030789698eebsm6083057wrl.89.2023.05.31.02.49.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 May 2023 02:49:17 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Message-Id: <8742D52A-A3C7-42FB-98E8-B83BC930DB6D@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2601510F-3044-41FA-A343-3E61989EE8EB"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Date: Wed, 31 May 2023 10:48:35 +0100
In-Reply-To: <a6ba4484-e3b6-613c-69b0-e570cb339b4b@gmail.com>
Cc: John C Klensin <john-ietf@jck.com>, Tools Team Discussion <tools-discuss@ietf.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <CF14A35ABED1122EC614AF81@PSB> <0298e627-b433-4ecb-0c29-cd395079de6e@gmail.com> <D94D78B548161F0ECFD69111@PSB> <17FA35AD-F786-48B0-8EC5-46A8EFAD90E0@ietf.org> <a6ba4484-e3b6-613c-69b0-e570cb339b4b@gmail.com>
X-Mailer: Apple Mail (2.3731.500.231)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/rf8EtHfTcMexZ0VBQ6fMeiewD9g>
Subject: Re: [Tools-discuss] datatracker, I-Ds, and email addresses
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 May 2023 09:49:21 -0000


> On 30 May 2023, at 22:42, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 30-May-23 21:35, Jay Daley wrote:
>> John
>> Are you suggesting that when an I-D is submitted, the email addresses of the authors are automagically added to their Datatracker profiles, even if they themselves omitted to do that?
> 
> Looking at my own profile, my primary address is listed as
> 
> "brian.e.carpenter@gmail.com 	author: draft-ietf-6man-rfc6874bis"
> 
> which strongly suggests that the DT actively tracks submissions, since that
> is the draft that's been (re)submitted most recently.

So you haven’t provided that any other way, say when registering for a meeting?

Jay

> 
> But the *primary* address is presumably user-choice?
> 
>   Brian
> 
>> Jay
>>> On 28 May 2023, at 01:36, John C Klensin <john-ietf@jck.com> wrote:
>>> 
>>> Brian,
>>> 
>>> Yes, typo.  Sorry.
>>> 
>>> And, yes, I can imagine such a heuristic.  At the same time, if
>>> that most recent RFCs is decades old and the (new) I-D is fully
>>> posted, it seems to be that a competent heuristic would either
>>> go with the information in the I-D or point the inconsistency
>>> out and ask for human assistance.   (FWIW, I am not able to
>>> figure out what it would mean to identify an I-D as less than
>>> fully posted when the announcement had bee sent to
>>> IETF-announce, the datatracker page was up, and the document was
>>> online in the places that both specified, all of which are the
>>> case here.)
>>> 
>>> best,
>>>   john
>>> 
>>> 
>>> --On Sunday, May 28, 2023 11:53 +1200 Brian E Carpenter
>>> <brian.e.carpenter@gmail.com> wrote:
>>> 
>>>> To avoid confusion, I think you mean RFC 2693.
>>>> 
>>>> I'd guess that we are dealing with a heuristic for the case
>>>> where
>>>> the DT profile is incomplete. "Use the most recent RFC" might
>>>> appear safer than "use the most recent I-D" in some lights.
>>>> Or maybe "use the most recent I-D" won't work before the I-D
>>>> has been fully posted.
>>>> 
>>>> Regards
>>>>    Brian
>>>> 
>>>> On 28-May-23 11:24, John C Klensin wrote:
>>>>> Hi,
>>>>> 
>>>>> Until very recently, I assumed that the email addresses shown
>>>>> in the Datatracker, particularly those shown on the home
>>>>> pages for various I-Ds, would be the most up-to-date ones we
>>>>> had except, possibly, for old I-Ds where they might reflect
>>>>> the addresses shown as Author Address information in those
>>>>> I-Ds.
>>>>> 
>>>>> That does not appear to be the case.   If one examines
>>>>> https://datatracker.ietf.org/doc/draft-rivest-sexp/
>>>>> an address is shown for the first author, Ronald L. Rivest, of
>>>>> rivest@theory.lcs.mit.edu.  His datatracker page does not show
>>>>> any email addresses at all.  RFC 1186 (October 1990) shows
>>>>> that address under Author's Addresses as does RFC 2593
>>>>> (September 1999).  But that address has been dead, or at least
>>>>> not-preferred, since at least July 2003 when LCS was merged
>>>>> into CSAIL and MIT, IIR, was already strongly preferring
>>>>> user@mit.edu styles of email addresses over
>>>>> user@department-or-lab.mit.edu ones before I left about a
>>>>> decade earlier.
>>>>> 
>>>>> In any event, the Authors' Addresses section of
>>>>> draft-rivest-sexp-00 shows the correct current email address,
>>>>> rivest@mit.edu.  Why is the datatracker picking up, and
>>>>> showing on that I-D page, a two decade-old address rather
>>>>> than the one in an I-D posted a couple of days ago?  And,
>>>>> especially assuming that there might be other instances of
>>>>> similar relationships, can this be fixed and fixed more
>>>>> generally than patching that particular page (although that
>>>>> would be good too)?
>>>>> 
>>>>>       thanks
>>>>>        john
>>>>> 
>>>>> 
>>>>> ___________________________________________________________
>>>>> Tools-discuss mailing list - Tools-discuss@ietf.org -
>>>>> https://www.ietf.org/mailman/listinfo/tools-discuss
>>> 
>>> 
>>> ___________________________________________________________
>>> Tools-discuss mailing list - Tools-discuss@ietf.org - https://www.ietf.org/mailman/listinfo/tools-discuss
>> -- 
>> Jay Daley
>> IETF Executive Director
>> exec-director@ietf.org

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org