Re: Stray thoughts on ' Update of IESG statement "Last Call Guidance to the Community"'

Keith Moore <> Thu, 22 April 2021 23:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D59FD3A184E for <>; Thu, 22 Apr 2021 16:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HMtRdAr6qOIG for <>; Thu, 22 Apr 2021 16:20:45 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6545B3A184C for <>; Thu, 22 Apr 2021 16:20:45 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id E4FE01AD8; Thu, 22 Apr 2021 19:20:41 -0400 (EDT)
Received: from mailfrontend1 ([]) by compute3.internal (MEProxy); Thu, 22 Apr 2021 19:20:42 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=oyYnReF4+nYidBr2HselD66Y54ukdScEzzW7fxzgs EM=; b=LLUEX5vcr16UfbkVOGFjtEtr5d2LllcJTCfT4Ox1xPM6jqUY1V0YEDHte XktySyD4s+d2M6/eJ0vOna/xXK9dEW03cghQaP60DMKfTIbeu+kHeQjjRCgpOzli zzbUV0VcGY+H1p9UERKqlaPlW+OPoQzAWJf6uFfn0oLp++CosCf9LphB8gb44VuU epGaeYZJ6qfxucK1+DEbSz/vn4Q34AmMqILByCM+KXC+pie59+lEcCwIbV0ET7xG A/Y4Dsy+LPcaDfiiRBupWVyLetEsP2WorV4XxGD+nX6VOHQePhYINgmnPfaFYo1c XTkNHnc8JTBttHIlRgW5bLOfQONwA==
X-ME-Sender: <xms:yASCYM548S3Ul_hDme0PT20NiEc8WiUBWnk8XGub4A35FaE4g4FK7Q> <xme:yASCYN6fN8wp6SHZnOI82sdMAHgoLFbBciI5aJCSvcSgqWDCh3AyAFADZDx4aHadf he6AZNTkaZo-Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdduuddgudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvihht hhcuofhoohhrvgcuoehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh eqnecuggftrfgrthhtvghrnhephefhuedtheefgfefgffhkeehgfeugfeiudeugeejkeef leelueeiffetfeeuudeunecukfhppeejfedruddufedrudeiledriedunecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:yASCYLfdWMlEfYG72UrW-OBznqw3KcWIpFU2KDB0Zeh61G3DskgPng> <xmx:yASCYBI9oO1yZDf4sqUtUfWAnA60FrnXZYDuCAcFx9jkXI88n-9vmA> <xmx:yASCYALx80ivOXPLHcopGMFH-Gy39rZjZqhPzGCrU5b5VP4aHcy-4w> <xmx:yQSCYFXvPtp-d74GBLSiP6HgIXKc_HWD3DFevUX0zeESjwuDGSETtA>
Received: from [] ( []) by (Postfix) with ESMTPA id 2284A240057; Thu, 22 Apr 2021 19:20:40 -0400 (EDT)
Subject: Re: Stray thoughts on ' Update of IESG statement "Last Call Guidance to the Community"'
To: Adam Roach <>,
References: <> <> <> <> <> <>
From: Keith Moore <>
Message-ID: <>
Date: Thu, 22 Apr 2021 19:20:39 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 22 Apr 2021 23:20:50 -0000

On 4/22/21 6:42 PM, Adam Roach wrote:

>>> More pointedly -- it lets folks see discussions of IETF work product 
>>> without them getting lost among (checks notes) 150 messages about a 
>>> New York Times article, 132 posts about QUIC and DNSSEC, and 234 
>>> messages about inclusiveness.
>>> I'm not necessarily saying these topics aren't worth discussing; but 
>>> it's important to get broad consensus on the documents we publish as 
>>> RFCs, and we can't afford to lose those conversations under the 
>>> crush of high-volume topics. The risk of documents in last call 
>>> getting lost in the noise is far more of a barrier to being 
>>> "available to the community" than the use of a dedicated mailing list.
>> One can credibly make the opposite argument also: that it's hard to 
>> find the time/patience to scan all of the Last Call discussions that 
>> happen, just so you can be "in the loop" for the relatively rare Last 
>> Call discussions that seem important to you. 
> That's the same argument on a smaller scale: I asserted that we needed 
> (and then benefited from) a smaller haystack for the needles of 
> interest, and you're saying that the new, much smaller haystack may 
> still be too large for effective needle finding.

Actually, no, though perhaps I didn't make myself sufficiently clear.   
Let me try to describe it differently:

Everybody has their own idea of which messages are relevant and which 
are not relevant.

If the list you're reading has a high percentage of relevant (to you) 
messages, you may find it worth your time/energy/patience to deal with 
the relatively rare irrelevant message, enough that you will peruse the 
entire list.  By doing so, you also have the opportunity to discover 
discussions which are valuable to you (and some of less value to  you) 
that you would not have specifically looked for.

But if everybody reads only from very narrowly focused lists, those 
opportunities will be lost, and nearly everyone will be working from 
within a narrow silo.

So I specifically don't advocate "even finer grained breakdown".   But 
I'm trying to brainstorm ways in which people can still at least be 
aware of more diverse conversations, without getting drowned in the flood.

Or from another angle: I doubt that the last-call@ list is actually a 
high signal-to-noise ratio for many, because I suspect that few people 
outside of IESG really want to read about every Last Call.   (Feel free 
to tell me if I'm assumed incorrectly.) So I'm wondering if lists that 
are organized along different dimensions would work better, say one list 
per area with all of the announcements (BOF, WG discussion, LC 
discussions, etc.) pertaining to that area included on the list.   But 
why should we limit ourselves to statically configured lists, if we can 
instead each specify what areas/topics/WGs we're interested in?