Re: Proposal: an "important-news" IETF announcement list

John C Klensin <john-ietf@jck.com> Wed, 29 September 2021 16:06 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B5433A00E1; Wed, 29 Sep 2021 09:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 AKWoe6WkNds6; Wed, 29 Sep 2021 09:05:58 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6C1E3A0783; Wed, 29 Sep 2021 09:05:52 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1mVc5e-0003em-4D; Wed, 29 Sep 2021 12:05:50 -0400
Date: Wed, 29 Sep 2021 12:05:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Lars Eggert <lars@eggert.org>
cc: Working Chairs <wgchairs@ietf.org>, IETF <ietf@ietf.org>
Subject: Re: Proposal: an "important-news" IETF announcement list
Message-ID: <752027E351A479CDF4CE8CA3@PSB>
In-Reply-To: <CALaySJLseu4Ci_=-OZDN1NKLimnfLSjnPFyv2bwOnOxL6q4RGg@mail.gmail.com>
References: <f22d22ea-80da-e595-d91f-c577461766a3@huitema.net> <44B61547-1B28-4D1C-88C1-4AD7BA7F9639@lear.ch> <69E7C755-D09C-447B-B327-4F13C19A3EED@eggert.org> <475d7515-f71a-c3f0-e455-03336226cc47@lear.ch> <04F3603A-514B-49DF-81C5-36023CBBB69E@eggert.org> <CALaySJLseu4Ci_=-OZDN1NKLimnfLSjnPFyv2bwOnOxL6q4RGg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/f5QThlLR1iAmKN5XjbeRfIGzTzc>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2021 16:06:10 -0000


--On Wednesday, September 29, 2021 10:08 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>> 1.  Announcements sent manually by <various roles> = 284
>> 2.  Announcements of new and updated WG charters & WG
>> closures = 44
>> 3.  (included in above 44)
>> 4.  Announcements of new non-WG mailing lists = 13
>> 5.  Announcements of new RFCs = 275
>> 6.  IESG and LLC telechat announcements = 39
>> 7.  Announcements of document actions = 175
>> 8.  Announcements of IESG conflict-review results = 14
>> 9.  Last call announcements for I-Ds = 174 (+ 4 for other
>> actions)
>> 10. Interim WG meeting announcements = 256
>> 
>> The "important-news" proposal would only retain those under
>> (1) above.
> 
> I think that 1, 4, and 6 should all be retained as is (and in
> the new list, if it's created).
> 
> I think that 2, 5, 7, 8, 9, and 10 should be in a weekly
> summary, one single message per week.
> 
> I think that when those under 10 are in a pattern (first
> Tuesdays, every second Wednesday) there should be one message
> that says that, and those messages should be immediately
> posted to the relevant working group lists and not wait for
> the weekly summary.
> 
> If we do that, there's probably no need for a new list, but I
> don't object to the new list.

Barry, 

I generally agree, but wonder about 6 and 9 because...

6.  IESG and LLC telechats (especially the former) occur on a
fixed schedule (as much or more so than the subset of 10 you
mention) so, while links and exceptions may be important, the
announcements ought to be routine and part of a summary (and, as
others have suggested, an available and downloadable calendar).

9. There are problems with pushing Last Call announcements for
I-Ds, especially I-Ds proposed for standards track or BCP
action, into a weekly summary. We would, I think, like to
encourage people to watch those things and step in on ones on
which they might have informed opinions, even if, for a given
participant, such Last Calls are only a few percent of the total
and all of the others will be deleted after skimming the subject
line.  However, consider the timing.  If the Last Call is for a
WG document and announced to the WG list on, say, a Monday, the
digest does not appear until Friday, and first announcement
starts the clock, we've cut the time that interested participant
has to read the document and comment by almost half.  Different
permutations of dates just affect different people and documents
badly unless we make other changes.  I can think about ways
around that but most involve tinkering with timing of LC
announcements or which ones count -- these are not just matters
of creating new lists or shuffling content distribution.  Of
course, Alexey's concern about searching by draft name is a
different aspect of much the same problem.

That brings me close to Eliot's consolidation suggestion but is
also a reminder of what others have said -- that, inevitably,
different people are going to find different things important
and hence that efforts beyond a certain point to really
fine-tune things may be doomed.  I'm also confident we could
come up with a different list of categories of announcements:
probably not much better than the one Lars posted, but probably
not much worse either.  

If we can concentrate on improving the S/N ratio on the
Announcement list --selective digests, avoiding four separate
interim meeting postings at the same time for the same WG,
encouraging calendar subscriptions, etc.-- then I think we
address the real problem while splitting up lists even more just
create distractions.

best,
   john