Re: [Rfced-future] Thank you and closure of the RFC Future Program

John C Klensin <john-ietf@jck.com> Fri, 08 July 2022 18:46 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32BACC15A72C for <rfced-future@ietfa.amsl.com>; Fri, 8 Jul 2022 11:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lhH-YmidApSm for <rfced-future@ietfa.amsl.com>; Fri, 8 Jul 2022 11:46:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C623EC1594AF for <rfced-future@iab.org>; Fri, 8 Jul 2022 11:46:05 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1o9szI-000GqP-Sq; Fri, 08 Jul 2022 14:46:00 -0400
Date: Fri, 08 Jul 2022 14:45:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Wes Hardaker <hardaker@isi.edu>, Mark Nottingham <mnot@mnot.net>
cc: rfced-future@iab.org
Message-ID: <A4FF92590881DBE388EE2DF6@PSB>
In-Reply-To: <a01dcd88-61ed-f85d-c493-ec75d4f9cb2b@stpeter.im>
References: <CANk3-NAb-Lb2ccAp3DgVSm7nf8a39H3Ws6Unf6dEuGsqfm_YPw@mail.gmail.com> <09341EEC-DB1B-4DA9-ADB1-14275067BA48@mnot.net> <CANk3-NAZ05jJ0vLBXyAtPyOg6FLNKRA_pmDe5-m03OUqNr=z3g@mail.gmail.com> <a01dcd88-61ed-f85d-c493-ec75d4f9cb2b@stpeter.im>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/8C2vcYPbiLB06QB9OjAT3auift8>
Subject: Re: [Rfced-future] Thank you and closure of the RFC Future Program
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2022 18:46:10 -0000


--On Friday, July 8, 2022 11:57 -0600 Peter Saint-Andre
<stpeter@stpeter.im> wrote:

> On 7/8/22 7:02 AM, Wes Hardaker wrote:
>> 
>>     Thanks, all. Will this e-mail list be deactivated?
>> 
>> 
>> We did not discuss that (and it's a good question).  As you
>> know the  IETF is very good at not closing lists if people
>> find them useful.   Considering there is a new list being set
>> up for the new WG, is this one  still useful for any
>> reason?  So how about this:
>> 
>> Does anyone think the list should remain open and useful for
>> some  purpose?  If so, ideally state why too and I can take
>> that feedback back  to the IAB.  Silence by everyone will
>> likely result in closing the list  (IMHO, not IAB-HO).
> 
> I see no reason to keep this list open - our work is done here
> and attention will now move to the RSWG (once that list is
> announced).

Agreed, but that is, IMO, the other piece of the answer, which
is that this list should not be shut down until the RSWG one is
created and announced.   If the RSWG is simply going to use
rfc-interest, than that should be said and it would be ok to
shut this list down as soon as convenient.  On the other hand,
if the RSWG is not going to use rfc-interest for its list, one
of its first activities should be defining, presumably in
consultation with the RPC, just exactly where the boundary
between its list and rfc-interest falls and update the
descriptions of both list to reflect that explanation.

    john