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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 13 March 2020 21:47 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 0E3743A1086 for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 14:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 uuUj35KoEOft for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 14:47:53 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99C173A1081 for <ietf@ietf.org>; Fri, 13 Mar 2020 14:47:53 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id 39so4160619pjo.1 for <ietf@ietf.org>; Fri, 13 Mar 2020 14:47:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=uIb12HsKIdhb/z5vN8nHcI9zFlC4QnVak2lkrihlGzA=; b=X2XQJcRxyxD7i5tNGM1ocYFuos5LTPFiIFMTERV+Lq8mKoDG22mZ3Qpx1755OYgKom RC9cbAtYiQw7RXZzvMZz3ow7CAx6Fl92qlYkT8lUlCtHiwI+8Vyu4cQTmpG5z1vRZe24 x9pHG2HPwU5lRysbRFRDPM+jt+AzWvB41QLRXlEHCcuyBuYKgRi8nDhqEKHah1lM7B3i wDdf82Mm6ETsUssRiQLRXgwUh8ZUqtNYke3noaQK0Y2h5zbiIBov0C0YnouFteJumvUo aYav6daPGiBxT85cjrGwRf2NajXRCqfgvqu53h8T2jHfryYjJpCtBLV16/NjGdzNSW2d TT7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=uIb12HsKIdhb/z5vN8nHcI9zFlC4QnVak2lkrihlGzA=; b=aQgD07oDyywAEw4zT1H43BeXk50qp9RAlgP+1h/SSzy9atAtmTRs1eOMPNFblZSg5L oHRjUMx2Pu0BVdZB5EybLPC2tx4pQBpO7iI0sRIiZBHtyHocGKgD9T+LHiEUABvLZT46 Yi7bEmoIEeuVQ+03tdP8XMPatBDX38MX4BCTdl2BmMngI6yUELCAxdZO9UXrsl2eXEDo BTjSvW9bDo6XlZAGn2Cylahnaw+jPhcXAS+XEeoM8ZbQdD1Nv1nzVQU3jWXn+VQJbioa LTkCrW2q7svgE1SuymSvSTW+S6YzgCvouO30uHqpVowMHoNbCJqdiisNsaHfa2XsYJOr eneg==
X-Gm-Message-State: ANhLgQ3Ia8FKcRS2nbaBl7PX4ewNDfGVDs7+ITnAKFwW5vms1FZMYDnl DTqBl1gndZqGGOoFjMhYTLiz9LSr
X-Google-Smtp-Source: ADFU+vsolLZ1VwZVl9kj99BpsEFVumZrso475qk9TM+CdY1r5u8PQGv74mfaCyjBNBUHcy6G2IAm7A==
X-Received: by 2002:a17:90a:9416:: with SMTP id r22mr12259518pjo.2.1584136072567; Fri, 13 Mar 2020 14:47:52 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id a24sm9614832pfl.115.2020.03.13.14.47.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Mar 2020 14:47:50 -0700 (PDT)
Subject: Re: Planned experiment: A new mailing list for last-call discussions
To: Benjamin Kaduk <kaduk@mit.edu>, 7riw77@gmail.com
Cc: ietf@ietf.org
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> <20200313213351.GY98042@kduck.mit.edu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <315a5ede-98cb-c8c2-b94f-793cc4251c11@gmail.com>
Date: Sat, 14 Mar 2020 10:47:47 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20200313213351.GY98042@kduck.mit.edu>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y_AIOCGOTizWFxzbs-RRcB9zgVA>
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:47:56 -0000

On 14-Mar-20 10:33, Benjamin Kaduk wrote:
> 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...

I don't understand this discussion. For many years, I've had messages with "last call" in their subject header sorted into an inbox named, strangely enough, "lastcallsin". I had to slightly augment my filters when the new list was created, but otherwise... nothing changed.

i-d-announce is indeed challenging, especially around I-D cutoff dates. But frankly, if your MUA can't filter or sort adequately, you either need a new MUA or you need to abandon hope of following IETF work.

   Brian