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

Robert Sparks <rjsparks@nostrum.com> Thu, 27 May 2021 15:50 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 77AD93A141D for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 08:50:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.282
X-Spam-Level:
X-Spam-Status: No, score=-1.282 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.398, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 ap0y5G0ZylyC for <tools-discuss@ietfa.amsl.com>; Thu, 27 May 2021 08:49:55 -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 558BC3A141C for <tools-discuss@ietf.org>; Thu, 27 May 2021 08:49:55 -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 14RFnZbQ063321 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 27 May 2021 10:49:35 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1622130575; bh=RgDkHy8zMA6DK/cvLNPfBegSrdirinp9aHSbyhA36V8=; h=To:Cc:References:From:Subject:Date:In-Reply-To; b=ekZmVZL7e5fdXqpHx4yKy2TIeOgMm8Mg5RfjI3+qSSx+Ihn5KpjP0ARJSBUWPKCnq RfejVvtUTv1WBF0mRCeRy5gcr4js3fSY2Cs+JuSkLz08SEspBk1yz+qs3RBCdvW5bD dqzwLwhya+C02B/Xx2mCmIA0Ak9cvFiKlnrlh55w=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.9.176] claimed to be unformal.localdomain
To: Toerless Eckert <tte@cs.fau.de>
Cc: Greg Mirsky <gregimirsky@gmail.com>, 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> <20210527153542.GQ3909@faui48e.informatik.uni-erlangen.de>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <f7210553-7f07-b67e-5586-1bb1cda30b6d@nostrum.com>
Date: Thu, 27 May 2021 10:49:29 -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: <20210527153542.GQ3909@faui48e.informatik.uni-erlangen.de>
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/wH2hiXpXPoTvdAFy0CaaJMjGnJE>
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 15:50:01 -0000

On 5/27/21 10:35 AM, Toerless Eckert wrote:
> Cool!
>
> So, is changing email on https://www.ietf.org/mailman/options/ietf still necessary,
> or would all those subscriptions be also changed when changing datatracker preferred email ?

It's still necessary to manage mailman separately.

In the long run we're looking at more integration, but that isn't likely 
to happen until we move to mailman3 (which is still not looking to be a 
trivial move).

RjS

>
> Cheers
>      Toerless
>
> On Thu, May 27, 2021 at 09:40:18AM -0500, Robert Sparks 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
>>> 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