Re: Changes to the way we manage RFPs

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 26 February 2020 13:08 UTC

Return-Path: <mcr+ietf@sandelman.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 5E23F3A09F9 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 05:08:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, 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 J7O-NCQCZlrE for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 05:08:14 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 973D63A09F4 for <ietf@ietf.org>; Wed, 26 Feb 2020 05:08:14 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7FC4F38982 for <ietf@ietf.org>; Wed, 26 Feb 2020 08:07:12 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 91E1768B for <ietf@ietf.org>; Wed, 26 Feb 2020 08:08:13 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF <ietf@ietf.org>
Subject: Re: Changes to the way we manage RFPs
In-Reply-To: <07BE2FB4-286D-4A35-B17F-629D3FBB7308@ietf.org>
References: <E6815976BDDAFB2B06809DEC@PSB> <07BE2FB4-286D-4A35-B17F-629D3FBB7308@ietf.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 26 Feb 2020 08:08:13 -0500
Message-ID: <18478.1582722493@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/itw3t39HBlbz8j8NtTZCeeq1PTk>
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: Wed, 26 Feb 2020 13:08:18 -0000

Jay Daley <jay@ietf.org> wrote:
    > It’s also a wider problem than announcements/reports - I only realised
    > last week that there was an active mtgvenue list, one of many “admin”
    > lists, and also a tools-discuss list, one of many “devops(?)” lists.

Yes, so it might be that for the set of non-WG related lists (mtgvenue is a
WG though) that we should have a policy of periodically (1-2/year) of posting
something (even if it is just the terms of reference for the list) to ietf@
or ietf-announce@ with appropriate Reply-To:

--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-