Re: Proposal: an "important-news" IETF announcement list
John C Klensin <john-ietf@jck.com> Fri, 01 October 2021 18:01 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 D64D13A0EF6; Fri, 1 Oct 2021 11:01:38 -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 uTbjTDKD-IV4; Fri, 1 Oct 2021 11:01:33 -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 719283A0ED6; Fri, 1 Oct 2021 11:01:31 -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 1mWMqb-0008y7-HD; Fri, 01 Oct 2021 14:01:25 -0400
Date: Fri, 01 Oct 2021 14:01:19 -0400
From: John C Klensin <john-ietf@jck.com>
To: Robert Sparks <rjsparks@nostrum.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
cc: Michael Richardson <mcr+ietf@sandelman.ca>, Working Chairs <wgchairs@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, tom petch <daedulus@btconnect.com>, IETF <ietf@ietf.org>
Subject: Re: Proposal: an "important-news" IETF announcement list
Message-ID: <5C75B025FE3E8C26AE4EBD50@PSB>
In-Reply-To: <ccb570db-3d68-87f2-1300-feb25093cd90@nostrum.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> <3627.1632928020@localhost> <6c6129eb-21b0-6bf1-86a8-f092fe78b3d4@gmail.com> <29954.1633025138@localhost> <b7101988-a26a-019a-bee8-7605b4a6d212@gmail.com> <6156C837.3020003@btconnect.com> <D9D2D7FF0974E6C3F00CCE65@PSB> <CAKKJt-dUNsnvVixd6ysaQ-s7feCgiA4sCm_52OV9xLj6YePX+A@mail.gmail.com> <ccb570db-3d68-87f2-1300-feb25093cd90@nostrum.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/Ya7J3ZIl-RIUjqbgbjHWfisZLkM>
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: Fri, 01 Oct 2021 18:01:39 -0000
--On Friday, October 1, 2021 10:32 -0500 Robert Sparks <rjsparks@nostrum.com> wrote: > Related but apart from discussion of what summaries might be > sent by email - > > There is a feed for last call documents at > https://datatracker.ietf.org/feed/last-call, and a page at > https://datatracker.ietf.org/doc/in-last-call. > > There are several feeds, fwiw. At one point there was a menu > for them, but pressure to declutter the menus some time back > took that away. There should at least be a summary page > somewhere. Robert, Thanks. Noting that a page the IETF participants don't know about or don't know how to find is of limited utility, your paragraph above exactly, if indirectly, summarizes part of the problem. I've just looked at https://www.ietf.org https://www.ietf.org/standards/process/ and even https://www.ietf.org/links/ (which only active participants who have been paying attention know how to find). And, if any of them contain the links you provided or even hints that they exist, I'm not looking hard enough. While, again, I don't think that page is a substitute for well-considered Last Call announcements (at least to the relevant WG, maybe Area, and a weekly summary as others have discussed), it suggests that we should be looking more broadly than tweaking or subdividing mailing lists. Some particular suggestions that I assume should be straightforward if others agree: (1) Add https://datatracker.ietf.org/doc/in-last-call to the "links" page under "IESG", "Internet-Drafts" or both. (2) Add a line to the bottom of the template for Last Call announcements that says something like "A listing of open IETF Last Calls is available at https://datatracker.ietf.org/doc/in-last-call Really a different topic, but I also think the "links" page should be more obviously available from the www.ietf.org home page and wonder whether the Last Calls should be identified there too. However, I've lost track of who the audience for that page is supposed to be and wonder if any evaluation is underway for whether that redesign is serving its intended purpose. best, john
- Proposal: an "important-news" IETF announcement l… IETF Chair
- Re: Proposal: an "important-news" IETF announceme… Melchior Aelmans
- IETF calendar (was: Re: Proposal: an "important-n… Toerless Eckert
- Re: Proposal: an "important-news" IETF announceme… Bob Hinden
- Re: Proposal: an "important-news" IETF announceme… Christian Huitema
- RE: Proposal: an "important-news" IETF announceme… Adrian Farrel
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Eliot Lear
- Re: Proposal: an "important-news" IETF announceme… Salz, Rich
- Re: Proposal: an "important-news" IETF announceme… David Noveck
- Re: Proposal: an "important-news" IETF announceme… Tim Wicinski
- Re: Proposal: an "important-news" IETF announceme… Lucas Pardue
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: [irsg] Proposal: an "important-news" IETF ann… Lars Eggert
- Re: Proposal: an "important-news" IETF announceme… Lars Eggert
- Re: [irsg] Proposal: an "important-news" IETF ann… Lars Eggert
- Re: Proposal: an "important-news" IETF announceme… Lars Eggert
- Re: Proposal: an "important-news" IETF announceme… Eliot Lear
- Re: Proposal: an "important-news" IETF announceme… Lars Eggert
- RE: Proposal: an "important-news" IETF announceme… MORTON JR., AL
- Re: Proposal: an "important-news" IETF announceme… Stephen Farrell
- RE: Proposal: an "important-news" IETF announceme… STARK, BARBARA H
- Re: Proposal: an "important-news" IETF announceme… Eliot Lear
- Re: Proposal: an "important-news" IETF announceme… Carsten Bormann
- Re: Proposal: an "important-news" IETF announceme… Marc Petit-Huguenin
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… Alexey Melnikov
- RE: Proposal: an "important-news" IETF announceme… MORTON JR., AL
- Re: Proposal: an "important-news" IETF announceme… Robert Sparks
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- RE: Proposal: an "important-news" IETF announceme… STARK, BARBARA H
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- making upcoming calendar more useful Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Jay Daley
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… Jay Daley
- Re: Proposal: an "important-news" IETF announceme… Martin Thomson
- Why last calls matter more than ever [Re: Proposa… Brian E Carpenter
- Re: making upcoming calendar more useful John C Klensin
- Re: making upcoming calendar more useful Warren Kumari
- Re: making upcoming calendar more useful Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… Spencer Dawkins at IETF
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… Robert Sparks
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- The links page [was: something else] Brian E Carpenter