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

Paul Wouters <paul@nohats.ca> Fri, 13 March 2020 16:12 UTC

Return-Path: <paul@nohats.ca>
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 23A5D3A0D11 for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 09:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 P8w4vmhUjvdj for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 09:12:53 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 51AE33A0C5E for <ietf@ietf.org>; Fri, 13 Mar 2020 09:12:52 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 48f9hg0l9gzG71; Fri, 13 Mar 2020 17:12:51 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1584115971; bh=ToarWDZ8H1vgT9hzQW+Dl78z2h+du4lemom9rw3h/g8=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=VhPX+LTmixFIW71ZOd7jAPqLHTAWdaidD3O05T79kbc4VA48D4NqwG+b6LNIX8YX/ uxlh9c87OnArlG7VkmT+gY8bE3Yz45bcJM39YzXh9+f9+DqrveW7QGQZoybyOfQBv8 vArevZY516NJKR/lDFxxbj0ow7ibYBgVZx7eGMyc=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id JNlhOkJOyrGt; Fri, 13 Mar 2020 17:12:50 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 13 Mar 2020 17:12:50 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 1651B6029BA6; Fri, 13 Mar 2020 12:12:49 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 152D282C6C; Fri, 13 Mar 2020 12:12:49 -0400 (EDT)
Date: Fri, 13 Mar 2020 12:12:49 -0400
From: Paul Wouters <paul@nohats.ca>
To: Rob Sayre <sayrer@gmail.com>
cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: Planned experiment: A new mailing list for last-call discussions
In-Reply-To: <CAChr6Sw=yoTSzD4XUKEEojspW8=Bsfv9QzDqRz5S0fHR0Cda9w@mail.gmail.com>
Message-ID: <alpine.LRH.2.21.2003131210440.17044@bofh.nohats.ca>
References: <CALaySJKvdoy9MtzHMwq-Ew-EJoUs0V8t+y01FL-E5r3xdyRemQ@mail.gmail.com> <CAChr6Sw=yoTSzD4XUKEEojspW8=Bsfv9QzDqRz5S0fHR0Cda9w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rR05Yyn21bFgm8rn8-w9dDqFISI>
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 16:12:55 -0000

On Fri, 13 Mar 2020, Rob Sayre wrote:

> In my view, the experiment is a success.

Yes, but it could use improvements.

I would prefer a reply-to: the ietf@ietf.org list with the lastcall
list not getting any further CC:s. This helps me see last call for new
documents on this list without being drowned by a discussion on drafts
that are not in my area of expertise. Currently, I think I miss some
lastcall requests due to the high discussion volume on the list.

Paul