Re: [Tools-discuss] Targeted email/chat group for reaching WG chairs.

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 14 April 2022 17:13 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 5B29B3A16F7 for <tools-discuss@ietfa.amsl.com>; Thu, 14 Apr 2022 10:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 Qz87EQioryBU for <tools-discuss@ietfa.amsl.com>; Thu, 14 Apr 2022 10:13:22 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D79F13A16ED for <tools-discuss@ietf.org>; Thu, 14 Apr 2022 10:13:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 8CDB238BAE; Thu, 14 Apr 2022 13:25:11 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kH9-0a2KJkpi; Thu, 14 Apr 2022 13:24:58 -0400 (EDT)
Received: from sandelman.ca (unknown [172.30.2.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0F90738BAC; Thu, 14 Apr 2022 13:24:58 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9064C38; Thu, 14 Apr 2022 13:13:04 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Rob Wilton \(rwilton\)" <rwilton=40cisco.com@dmarc.ietf.org>, tools-discuss <tools-discuss@ietf.org>
In-Reply-To: <BY5PR11MB419661EA3A466B06639C69D9B5EF9@BY5PR11MB4196.namprd11.prod.outlook.com>
References: <BY5PR11MB419661EA3A466B06639C69D9B5EF9@BY5PR11MB4196.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 14 Apr 2022 13:13:04 -0400
Message-ID: <1856.1649956384@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/PGPO9EuJs8rEJdvaeR-XYV6oViA>
Subject: Re: [Tools-discuss] Targeted email/chat group for reaching WG chairs.
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, 14 Apr 2022 17:13:27 -0000

Rob Wilton \(rwilton\) <rwilton=40cisco.com@dmarc.ietf.org> wrote:
    > The aim: Have a way of getting limited important information to the WG
    > chairs in a way that is likely to reach them (e.g., in-person meeting
    > announcements, or nomcom requests).  There was some brief discussion as
    > to whether an alias similar the <area>-chairs would be more effective
    > than a standard mailing list, but the conclusion was to seek your
    > expert opinions on this.

In order to increase reachability, you'll need to unicast, not relay through
DT as Robert says.  That could mean that the DT originates the emails.
I suggest intentionally omitting the List-Id:

    > the goal is a very cutdown lists with much more limited emails.  E.g.,
    > probably in the order of approx. 1 or 2 per week between meetings, and
    > a bit more in the run up to IETF.

So that's like 60 emails/year if I understood you correctly.
That's a lot really.   It seems like much of that ought to also be in an
archive and/or blog.

Probably IMAP access and mailarchive already provides this, we just don't
have a clear place, like a wgchairs-announce to which things could be archived.

    > In addition, there was also some discussion about having something
    > similar setup for Slack/Zulip.  I.e., a place to send announcements for
    > WG chairs to read.

I'm regularly connected to Jabber, Hallway and WGs to which I co-chair, and
I'd say that it would be completely ineffective in reaching me in a timely manner.

Carsten Bormann <cabo@tzi.org> wrote:
    > On 2022-04-14, at 17:02, Carsten Bormann <cabo@tzi.org> wrote:
    >>
    >> A wgchairs-announce to which you are force-subscribed by becoming WG
    >> chair would work if the message count stays low.

    > (I also have the mental image of a Totmann key, where datatracker
    > randomly sends out messages to which you need to reply within some time
    > or the train pulls the emergency brake.)

To me, this actually is a good idea.
Perhaps the specific email is an invitation from the AD to have a 3-times
yearly post-meeting debrief.    Failure to answer/schedule with your AD
raises quite a few questions.

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