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

Robert Sparks <rjsparks@nostrum.com> Thu, 27 May 2021 20:19 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 655A33A0DD3 for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 13:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level:
X-Spam-Status: No, score=-2.079 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, HTML_MESSAGE=0.001, 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 HRCy0GgwkGfg for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 13:19:15 -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 20AA13A0DD2 for <tools-discuss@ietf.org>; Thu, 27 May 2021 13:19:15 -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 14RKJ61Z053938 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 27 May 2021 15:19:07 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1622146747; bh=33uS3IVWBqqhY/YNhnBHySFd9ieGo6zwrCypXBK9hlU=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=eStsJKCyw/RYgYxie3ThAOs3YV6NIkvUt/tdMZuCgq8Z9uOOrvjYPoZZ076Z36i6g n6vH+odO3O8Caik5A27ASbs3pfjSBJksJf2MqJNj4e40hto/sKTfdSol/mnx/TNDOS T4A5uAw5F/UtxoIsRCqnX8lpx39oqQf1u5Gxka7U=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.9.176] claimed to be unformal.localdomain
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: Tools Team Discussion <tools-discuss@ietf.org>
References: <20210526175001.GK3909@faui48e.informatik.uni-erlangen.de> <059250c6-cc20-63c4-ca83-6b1d85998f94@nostrum.com> <CA+RyBmU45MoNKgJb8o_DE53aRbENfLczLAm-tCYsL9+pnPsmJA@mail.gmail.com> <30d455b5-5d0f-28c9-01a5-5a442bb3152f@nostrum.com> <CA+RyBmURT6dV6hyPmfHrS6+bc40LE1nhATumZxG5Ry0i2ruApQ@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <891b9316-36f7-b012-c6da-0775df49ec95@nostrum.com>
Date: Thu, 27 May 2021 15:19:01 -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: <CA+RyBmURT6dV6hyPmfHrS6+bc40LE1nhATumZxG5Ry0i2ruApQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------D4EE0B4553C7D0F14EB35B68"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/HTT0umI9hicT1EHeYcU7J6qsbDk>
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:19:20 -0000

On 5/27/21 2:52 PM, Greg Mirsky wrote:
> Hi Robert,
> thank you for suggesting the use of the "Send notices to" field. Can 
> it be automatically populated with all e-mail addresses listed in an 
> author's contact info? Or an author can add it manually?

At the moment, you would need to ask the secretariat (or an AD, or a wg 
chair if the document has been adopted by a wg) to add it for you.

RjS

>
> Regards,
> Greg
>
> On Thu, May 27, 2021 at 7:40 AM Robert Sparks <rjsparks@nostrum.com 
> <mailto:rjsparks@nostrum.com>> wrote:
>
>     No - we've had a lot of pressure from people that led to using the
>     marked primary email address.
>
>     We could consider adding an "always CC" flag to the email
>     configuration or something like it if there's enough demand, but
>     it would be a large change to do so.
>
>     What is your use case? Would it satisfy your needs to add the
>     addresses to the documents Notify field (on the document's main
>     page). Any addresses there will be copied in correspondence from
>     the datatracker, and will appear in the draft-<name>-notify and
>     draft-<name>-all aliases.
>
>     RjS
>
>
>     On 5/26/21 6:48 PM, Greg Mirsky wrote:
>>     Hi Robert,
>>     I've chosen to list two email addresses, the feature that is
>>     supported in XMLv3. I wanted the correspondence addressed to
>>     draft-<foo>@ietf.org <http://ietf.org> to be directed at both.
>>     But, as I see it, the datatracker uses only one, whichever is
>>     listed first. Do you of any plans to modify that behavior in the
>>     datatracker?
>>
>>     Regards,
>>     Greg
>>
>>     On Wed, May 26, 2021 at 1:12 PM Robert Sparks
>>     <rjsparks@nostrum.com <mailto:rjsparks@nostrum.com>> wrote:
>>
>>         The draft-<foo>*@ietf.org <http://ietf.org> and
>>         <acronym>-chairs@ietf.org <mailto: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.
>>
>>         RjS
>>
>>         On 5/26/21 12:50 PM, Toerless Eckert wrote:
>>         > So, i run repeatedly into the problem of co-authors or just
>>         > contributors to my WG changing association/email-address,
>>         and i am
>>         > right now not 100% sure about the BCP how they should deal
>>         with it.
>>         >
>>         > So, https://www.ietf.org/mailman/options/ietf/
>>         <https://www.ietf.org/mailman/options/ietf/><email address>
>>         > and global change is clearly part of the BCP.
>>         >
>>         > But in my past experience, it seems that this will not
>>         change the email
>>         > addresses of the collaborator on draft-ietf-wg-whatever.
>>         And i don't
>>         > even know if/how there is a way to change those email
>>         addresses. Is there
>>         > any tool for WG chairs or the contributor themselves to
>>         bulk change
>>         > the email adress on those draft aliases ? (even a single
>>         draft has
>>         > quite a few aliases created).
>>         >
>>         > Cheers
>>         >      Toerless
>>         >
>>         > ___________________________________________________________
>>         > Tools-discuss mailing list - Tools-discuss@ietf.org
>>         <mailto: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
>>         <mailto:datatracker-project@ietf.org>
>>         > * Report tools.ietf.org <http://tools.ietf.org> bugs to:
>>         webmaster@tools.ietf.org <mailto:webmaster@tools.ietf.org>
>>         > * Report all other bugs or issues to: ietf-action@ietf.org
>>         <mailto:ietf-action@ietf.org>
>>         > List info (including how to Unsubscribe):
>>         https://www.ietf.org/mailman/listinfo/tools-discuss
>>         <https://www.ietf.org/mailman/listinfo/tools-discuss>
>>
>>         ___________________________________________________________
>>         Tools-discuss mailing list - Tools-discuss@ietf.org
>>         <mailto: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
>>         <mailto:datatracker-project@ietf.org>
>>         * Report tools.ietf.org <http://tools.ietf.org> bugs to:
>>         webmaster@tools.ietf.org <mailto:webmaster@tools.ietf.org>
>>         * Report all other bugs or issues to: ietf-action@ietf.org
>>         <mailto:ietf-action@ietf.org>
>>         List info (including how to Unsubscribe):
>>         https://www.ietf.org/mailman/listinfo/tools-discuss
>>         <https://www.ietf.org/mailman/listinfo/tools-discuss>
>>
>>
>>     ___________________________________________________________
>>     Tools-discuss mailing list -Tools-discuss@ietf.org  <mailto: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  <mailto:datatracker-project@ietf.org>
>>     * Reporttools.ietf.org  <http://tools.ietf.org>  bugs to:webmaster@tools.ietf.org  <mailto:webmaster@tools.ietf.org>
>>     * Report all other bugs or issues to:ietf-action@ietf.org  <mailto:ietf-action@ietf.org>
>>     List info (including how to Unsubscribe):https://www.ietf.org/mailman/listinfo/tools-discuss  <https://www.ietf.org/mailman/listinfo/tools-discuss>
>