Re: Planned experiment: A new mailing list for last-call discussions

Benjamin Kaduk <kaduk@mit.edu> Fri, 13 March 2020 21:34 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AAF3A1067 for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 14:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 g1m5k0Oqh1wn for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 14:34:02 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E21D3A093E for <ietf@ietf.org>; Fri, 13 Mar 2020 14:34:01 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 02DLXqHL030594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Mar 2020 17:33:54 -0400
Date: Fri, 13 Mar 2020 14:33:51 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: 7riw77@gmail.com
Cc: "'tom petch'" <daedulus@btconnect.com>, "'Robert Sparks'" <rjsparks@nostrum.com>, ietf@ietf.org
Subject: Re: Planned experiment: A new mailing list for last-call discussions
Message-ID: <20200313213351.GY98042@kduck.mit.edu>
References: <CALaySJKvdoy9MtzHMwq-Ew-EJoUs0V8t+y01FL-E5r3xdyRemQ@mail.gmail.com> <CAChr6Sw=yoTSzD4XUKEEojspW8=Bsfv9QzDqRz5S0fHR0Cda9w@mail.gmail.com> <alpine.LRH.2.21.2003131210440.17044@bofh.nohats.ca> <b4eaf545-16ac-d44f-34bf-8d3915773d51@nostrum.com> <1UW5qApRF0.3QvRUjjaoKI@pc8xp> <031901d5f97e$9d2598a0$d770c9e0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <031901d5f97e$9d2598a0$d770c9e0$@gmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WS7W2CwC1cYfp2bznXoS3KvY9I8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2020 21:34:03 -0000

On Fri, Mar 13, 2020 at 05:30:26PM -0400, 7riw77@gmail.com wrote:
> 
> > Now I am totally confused.  I miss Last Call announcements precisely because
> > there are hundreds and hundreds and hundreds of posts to ietf-announce at
> > times like last weekend when the submission window is about to close.
> 
> This is problem I face on a regular basis as well... I've tried to sort out the last calls based on the contents of the email, but it would be more convenient  if there were a separate list, I think (?).

It's entirely possible I have different calibration for email volume than
many people, but just to check: we're talking about the number of emails
being too much on ietf-announce@ietf.org, not i-d-announce@ietf.org?
I agree that the latter is indeed quite a lot...

-Ben