IETF Logo Mail Archive

Re: Proposal: an "important-news" IETF announcement list

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 29 September 2021 21:14 UTC

Return-Path: <brian.e.carpenter@gmail.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 412253A08AC; Wed, 29 Sep 2021 14:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-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 wyOu3OCDiS0V; Wed, 29 Sep 2021 14:13:56 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 558093A0863; Wed, 29 Sep 2021 14:13:52 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id w11so2412303plz.13; Wed, 29 Sep 2021 14:13:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=KHZm7OgoT2mwusC7TQEqRqEqfuGYh90WeMLnhtVn65I=; b=nu7zoDFsyEJkpbQTIs4Y/84cYX4rRjeNvD1apDewYyKtsPgjwLLCo6+6TPEIW6HcZR odNFNQJJntd7kiDVACJPo9T6bQgchOkCwl8F/1Qs4AWH9XZEoh3Ithw+shgtbntux8k0 QY9qz7lsoBXbqoP464ZZgfsT7Na5DxdRTRjDtjHO6srOgVswzOY2WFQOIztKWFV+opAi 4I11BSEO7Valwp7pExCuEKa6h9vN5uKGMdKAIibyo12pvmfmAy9v+8PliTC3bHBFgxwq z0ejqA6vKL+YWKWfuMEy50aKkg266OIGLdDYEhZyO/+W6lb1bCG1W+GyGOdE39Bo7V+O EllA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=KHZm7OgoT2mwusC7TQEqRqEqfuGYh90WeMLnhtVn65I=; b=P9xkmrXw2Fcn3L2xYyTnby2Nz6k7w0yfYHRRpP1xoXv7AaYFcFDnTaVO2rGI9+Zq9b UjxYHTfVKvHkhgz+Ev2qI/+L2/0bzR2p4TbLEC+yUSQVtBOhBpmQ2YKo+HenB/SbhstP W1yzcCozcMxScPA0CbKbhzG9BaECKsbP7UVkVU1MX3O+5ojakqYySuVojwkG13UA5fwM HrwwgSSEQPPknm8c/pTK2Z4J1c83ZzhPtgiusWWZjwM6aYBE3kxCfKr4HyVjR8Oc4pmS v7CRLBTDnfMeoB4zh5vf63951i2wm+CJRRFgCLLR2YzrcQYPgazx9KESncj4mgayrVcs ocPg==
X-Gm-Message-State: AOAM531ZHTl7BOCe6jRHecOgzAjJ8mJkBulniupkQPMan2LYZPFxtAGC rfTGQBjlAovJuzzfp94nZ2QfA/NW4SGmPA==
X-Google-Smtp-Source: ABdhPJz1uzIITG/pGBz2qpg10XhI0UAT5dQnfYLCEEIiENwIpnbC64eVq0ScvepxcnX2UeXOL+d+xQ==
X-Received: by 2002:a17:90a:de16:: with SMTP id m22mr2225907pjv.54.1632950031623; Wed, 29 Sep 2021 14:13:51 -0700 (PDT)
Received: from ?IPv6:2406:e003:11aa:d701:80b2:5c79:2266:e431? ([2406:e003:11aa:d701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id s34sm794563pjd.36.2021.09.29.14.13.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 29 Sep 2021 14:13:51 -0700 (PDT)
Subject: Re: Proposal: an "important-news" IETF announcement list
To: "STARK, BARBARA H" <bs7652@att.com>, 'Alexey Melnikov' <alexey.melnikov@isode.com>, 'Barry Leiba' <barryleiba@computer.org>, 'Lars Eggert' <lars@eggert.org>
Cc: 'Working Chairs' <wgchairs@ietf.org>, 'IETF' <ietf@ietf.org>
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> <29d2a637-f629-b494-1cb5-75510e6149dc@isode.com> <DM6PR02MB6924C37148A63E27218142B3C3A99@DM6PR02MB6924.namprd02.prod.outlook.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7c882dc9-6cce-d3dc-f098-71049da44c1a@gmail.com>
Date: Thu, 30 Sep 2021 10:13:45 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <DM6PR02MB6924C37148A63E27218142B3C3A99@DM6PR02MB6924.namprd02.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/0AOUTstnwXcCTw1M3-EgcE4s3Jg>
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: Wed, 29 Sep 2021 21:14:07 -0000

On 30-Sep-21 04:14, STARK, BARBARA H wrote:
>>>> 1.  Announcements sent manually by <various roles> = 284
>>>> 2.  Announcements of new and updated WG charters & WG closures = 44
>>>> 3.  (included in above 44)
>>>> 4.  Announcements of new non-WG mailing lists = 13
>>>> 5.  Announcements of new RFCs = 275
>>>> 6.  IESG and LLC telechat announcements = 39
>>>> 7.  Announcements of document actions = 175
>>>> 8.  Announcements of IESG conflict-review results = 14
>>>> 9.  Last call announcements for I-Ds = 174 (+ 4 for other actions)
>>>> 10. Interim WG meeting announcements = 256
>>>>
>>>> The "important-news" proposal would only retain those under (1) above.
>>> I think that 1, 4, and 6 should all be retained as is (and in the new
>>> list, if it's created).
>>>
>>> I think that 2, 5, 7, 8, 9, and 10 should be in a weekly summary, one
>>> single message per week.
>>
>> I have a slight problem with this proposal because if it is implemented
>> it would not be possible to find last call announcements by draft name.
>> I think this is a rather important feature when searching archive.
>>
>> Unfortunately I don't have a solution for this problem.
> 
> I thought we were discussing changes to ietf-announce and not last-call. All these emails already exist on the last-call list and don't need to be repeated in their entirety on ietf-announce. A summary email to ietf-announce should be sufficient. Anybody wanting to subscribe to last-call has the ability to do so. 

Unfortunately that doesn't compute. If someone sees the Last Call announcement on announce @ietf, they can simply reply and it will go where it needs to go. The whole point of last calls is they go to *everybody* so that *anybody* can reply. This is why I believe that Last Calls are possibly the most important content on announce@ and should definitely not be dropped.

I'm not against weekly summaries for most of the categories Lars listed, but I suggest that the model should be, for category X, that the raw messages go to X-announce@ietf.org, and the summary comes labelled "X-announce messages for the week ending $DATE".

(And yes, I know there would be complaints about too many summary messages. Or too few.)

   Brian

v2.23.0 | Report a Bug | By Email