IETF Logo Mail Archive

Re: [Tools-discuss] tooling: Change of address Q.

Robert Sparks <rjsparks@nostrum.com> Thu, 27 May 2021 20:48 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 96D2F3A1004 for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 13:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 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, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2HAByMN8ULW for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 13:48:34 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCDDE3A0FFA for <tools-discuss@ietf.org>; Thu, 27 May 2021 13:48:34 -0700 (PDT)
Received: from unformal.localdomain ([47.186.9.176]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 14RKmVSv063925 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 27 May 2021 15:48:31 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1622148512; bh=H61fMDrlcSYebwmL9GyZpamWHizjrDjBckuClwtExEo=; h=To:Cc:References:From:Subject:Date:In-Reply-To; b=nIa0odOxBbNi6DE8vYCznyG0Ks8+iZno21KB2Vn8whabBp4fCHmOkXZxSoE8fS/hE bCmA1cgDABo3F38zv4EQxlPCjsyQVx43kCnNHvluj2TRNmi3t8EzLz9sV5B5OaNnz7 rlwYMo3a+uaECiMORQluU//GZ8SMtiLEMzl+UJRo=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.9.176] claimed to be unformal.localdomain
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: tools-discuss@ietf.org
References: <20210526175001.GK3909@faui48e.informatik.uni-erlangen.de> <059250c6-cc20-63c4-ca83-6b1d85998f94@nostrum.com> <12878.1622118335@localhost>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <0f77465d-a73a-a145-5329-03570e7b92ed@nostrum.com>
Date: Thu, 27 May 2021 15:48:26 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.2
MIME-Version: 1.0
In-Reply-To: <12878.1622118335@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Ctw-tm8fDC_Pcj-mho0slGaJAAI>
Subject: Re: [Tools-discuss] tooling: Change of address Q.
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 May 2021 20:48:40 -0000

On 5/27/21 7:25 AM, Michael Richardson wrote:
> Robert Sparks <rjsparks@nostrum.com> wrote:
>      > The draft-<foo>*@ietf.org and <acronym>-chairs@ietf.org aliases are
>      > regenerated on-demand, or with a high refresh rate (hourly).
>
>      > If the collaborator changes their preferred email address in the
>      > datatracker, it will be used in all of those aliases after the next
>      > generation.
>
> So, the emails are generated from the DT, not from the drafts themselves?
>
> 1) draft emails -> DT identity (according to whole set of emails)
> 2) DT identity -> aliases using "primary" email.
>
> A downside seems to be that I think that I can't have drafts with different
> email addresses (representing wearing different hats), concurrently being used.
> I don't have this requirement, but I just wanted to be clear about how it works.
> It might be surprising to some.

Well, things are always more complicated than they first seem, and this 
post made me go look more closely, and I'll backtrack a little, changing 
what I've said earlier.

The code for generating the aliases is here:

https://trac.ietf.org/trac/ietfdb/browser/trunk/ietf/doc/management/commands/generate_draft_aliases.py

The salient part for the draft-<name>@ alias (as opposed to the 
draft-<name>-[ad|shepherd|notify|all]@ aliases) is at

https://trac.ietf.org/trac/ietfdb/browser/trunk/ietf/doc/management/commands/generate_draft_aliases.py#L129

and in particular

https://trac.ietf.org/trac/ietfdb/browser/trunk/ietf/doc/management/commands/generate_draft_aliases.py#L54

Which takes its data from the addresses taken from the drafts:

https://trac.ietf.org/trac/ietfdb/browser/trunk/ietf/doc/models.py#L605

Note that the DocumentAuthor object only allows for a single address. It 
would be a big change for it to allow multiples.

So - your draft specific emails will still be used for the various 
aliases (but only one address will be used from the draft).

What I've said about the addresses that get used (only using the 
Preferred address) is true for mail the datatracker sends though.

Greg - apologies that I wasn't completely correct in my earlier responses.

RjS





>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>             Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>

v2.23.0 | Report a Bug | By Email