Re: [Tools-discuss] Draft email aliases aren't forever

Bob Hinden <bob.hinden@gmail.com> Wed, 11 May 2022 16:46 UTC

Return-Path: <bob.hinden@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 1E316C15E6D4 for <tools-discuss@ietfa.amsl.com>; Wed, 11 May 2022 09:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 oVmTmu2baCMq for <tools-discuss@ietfa.amsl.com>; Wed, 11 May 2022 09:46:49 -0700 (PDT)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 849A2C15E6CE for <tools-discuss@ietf.org>; Wed, 11 May 2022 09:46:49 -0700 (PDT)
Received: by mail-wm1-x331.google.com with SMTP id o12-20020a1c4d0c000000b00393fbe2973dso3613933wmh.2 for <tools-discuss@ietf.org>; Wed, 11 May 2022 09:46:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=4bxMx3F191un1eHNoVxJBe70sQs2Op7cvHftMOcPSUI=; b=WPs2cFKlQ56UwFwckGyNMHs3zf45N5nPpAZjExctjJVV46Fjqxq7OwliF6IZU3kZQ5 oF0fq8dFXvrpQGKk4HBemVQ7nkh8Q3lyiH/mZgqXCknsSgrmXW+JijFuWphtd5DQ4Qa1 DvpgEMd0odhj2fj0rxQCbRweApIHyXsVa63AB/Zrel8+Q18VyYQhxNs2cSGBQAb44qbq bS/frQ3BjGoXQrei3fE+BnkgeqrIcJfrg24QOkypU/DDv+WbzVG4G0l9c7HNcZI2c4sy n6GFauVxI+r1C9Lkj0EU963fJh+mFX4jOzMQsnE8LY8gzC3eMba289oR6U2xniQt+bfe j8MQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=4bxMx3F191un1eHNoVxJBe70sQs2Op7cvHftMOcPSUI=; b=YBfCMyxjbQwIQGAOrIrF+jcyuEYVwcPidJU+yMSLzm1vO2aHJZ9Vrd3w8fnH2rwSp7 jk5mtknEesTvmd/EPjf+eDw5N0Idh2V36+RFIk/F+VhEXqk7OZfk0BZXip7pnGUtEUON h371UZsnGDaML+Lp3UYucXJDO9TGTlACoXE9qc0825yPu3ciHrwhejQ/eufLcuB6PPpn FiqlAd6HkoQzSim7F16qco7bNgOS4u2pUEj2K2eL2yMyPW9LYWz+W1Oh2SssbaEiBDUf 6AUo1BlY7CUyAUk0mhk3TtPxLleExyJp8mFGpsFHTStDbB+ytg09F1q3sE0Mo05wOOMr J47w==
X-Gm-Message-State: AOAM530tRaAvrah/u8+y5xr8TjpOVRAdemv9Kqp2n9EjtP/21rySDswO D2YCY/0CD+LqZ3bWPsNTWoyfDv/hQnI=
X-Google-Smtp-Source: ABdhPJwXFo0T+L/lxYwFGYAdQCkCTBwkLuvW9ijI8ozRSurknluYRpaJX4XsJJ1w4ivvO8d/8Uk3nw==
X-Received: by 2002:a05:600c:4f15:b0:394:8ea0:bb45 with SMTP id l21-20020a05600c4f1500b003948ea0bb45mr5732448wmq.206.1652287607297; Wed, 11 May 2022 09:46:47 -0700 (PDT)
Received: from smtpclient.apple ([2600:1700:4383:c05f:c92d:bbd2:c0d2:ba32]) by smtp.gmail.com with ESMTPSA id q22-20020a7bce96000000b003942a244ebfsm308702wmj.4.2022.05.11.09.46.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 May 2022 09:46:46 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_92D8DFB9-08F8-45D8-A849-1FF648A62B49"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <573cb4e3-f80f-3d6c-b935-13599e9c5ae6@nostrum.com>
Date: Wed, 11 May 2022 09:46:43 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, Robert Sparks <rjsparks@nostrum.com>
Message-Id: <89281238-831A-492D-9636-FBDA50B5BA24@gmail.com>
References: <61077a2a-ab86-41c8-bef1-db339bc3623d@beta.fastmail.com> <0EC9C228-C6E4-40C5-A063-869314A50A76@tzi.org> <b1966fa9-fdd9-27b9-6faa-e88f6311e35f@sit.fraunhofer.de> <573cb4e3-f80f-3d6c-b935-13599e9c5ae6@nostrum.com>
To: tools-discuss <tools-discuss@ietf.org>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/qEac5hyDc3CMb60PxKtQOnt9WvM>
Subject: Re: [Tools-discuss] Draft email aliases aren't forever
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.34
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, 11 May 2022 16:46:50 -0000

On this topic, I am not sure it makes sense to keep these aliases going forever.   Something like a year after the draft expires should be fine.   The likely hood that the email addresses are still valid goes down over time, people change jobs, stop participating in the IETF, retire, etc.

How hard is it to hand copy the addresses from the authors section for old expired drafts, or do some Internet searches?

Bob


> On May 11, 2022, at 9:39 AM, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> 
> On 5/11/22 1:57 AM, Henk Birkholz wrote:
>> On 11.05.22 08:11, Carsten Bormann wrote:
>>> One thing that probably should be done is to record the datatracker IDs behind the authors’ addresses at the time of submission, and replacing the original addresses by current ones recorded under that datatracker ID, when the alias is being used.  (If there is a datatracker ID, that is.)
>> 
>> That is a great idea.
> I'm pretty sure that already happens.
>> 
>> 
>> On 11.05.22 08:11, Carsten Bormann also wrote:
>>> On 11. May 2022, at 04:40, Martin Thomson <mt@lowentropy.net> wrote:
>>>> 
>>>> I just tried mailing the authors of an expired draft using the draft-...@ietf.org alias.  The mail bounced.
>>>> 
>>>> What sort of guarantees exist for these email aliases?  The name of a draft is forever, so I'd suggest that it makes sense for the aliases to be kept indefinitely also.
>>> 
>>> We had this discussion a couple of years ago and I was very surprised to learn that these aliases time out.
>>> 
>>>> Or is this an important part of maintaining the fiction that drafts expire?
>>> 
>>> I don’t remember what the rationale was, but it still doesn’t make any sense to me either.
> The list of aliases for the mailserver to handle becomes _very_ long and the processing time becomes noticeable.
>>> 
>>> One thing that probably should be done is to record the datatracker IDs behind the authors’ addresses at the time of submission, and replacing the original addresses by current ones recorded under that datatracker ID, when the alias is being used.  (If there is a datatracker ID, that is.)
>>> People often publish their drafts proudly exposing the newest startup they are in (or whoever is sponsoring their IETF work), and that email address may not live very long.
>>> 
>>> Grüße, Carsten
>>> 
>>> ___________________________________________________________
>>> Tools-discuss mailing list - Tools-discuss@ietf.org
>>> This list is for discussion, not for action requests or bug reports.
>>> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org
>>> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
>>> * Report all other bugs or issues to: ietf-action@ietf.org
>>> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss
>> 
>> ___________________________________________________________
>> Tools-discuss mailing list - Tools-discuss@ietf.org
>> This list is for discussion, not for action requests or bug reports.
>> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org
>> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
>> * Report all other bugs or issues to: ietf-action@ietf.org
>> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org
> This list is for discussion, not for action requests or bug reports.
> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org
> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
> * Report all other bugs or issues to: ietf-action@ietf.org
> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss