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

Brian Rosen <br@brianrosen.net> Fri, 08 July 2022 19:04 UTC

Return-Path: <br@brianrosen.net>
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 1E61BC14CF16 for <rfced-future@ietfa.amsl.com>; Fri, 8 Jul 2022 12:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.com
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 9QB8TFr0L-gz for <rfced-future@ietfa.amsl.com>; Fri, 8 Jul 2022 12:04:55 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CC60C15A733 for <rfced-future@iab.org>; Fri, 8 Jul 2022 12:03:07 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id v185so20517839ioe.11 for <rfced-future@iab.org>; Fri, 08 Jul 2022 12:03:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=AAGDOQ7kSlrzq++pJVUvZhA7fN/giou0T86MRK/vvgI=; b=PzRs7PVCBHi+0gG0mUeAgyjdQvw7scEaDQJxlMw3ZAOVs/qhf3SKdJM4p2MiEn+9Qa zGg5jqBSdgSzO2dg87vGYhqoPmC7tV1XmUf6oTgSyumwXVWmp11lcoitL/bm9DF9ElJ6 DLaPYxGOSBVMJiNjAESn7GHdvGqasjzfJW+A2oeYPTkRNUT6Wq+fuNE+BSPwpCwOMm9U zxyrCczu2LoY7RXCGVv9jCAI+axpG2QY6018+uFCHqClgTortobKKqy7GazYzGvR4B8R vBnW3turmJufypmyzO2IfYBLFK2btbsEjRHiJ2VItH7PUXZhTMDzPcCxoXlwudeRbG/d eEEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=AAGDOQ7kSlrzq++pJVUvZhA7fN/giou0T86MRK/vvgI=; b=b8Bfdrl52PxrlGVUEnNToBZfytKeRLNNJykfJntHcVEM33yDYlRsO3vLvZSQjBApJF Zo5o/lUDGC5tkEESdLg7FFQAUQhGf+kNJwmzaQ1hneabeJN3EYM6P3Osu3HRiz1R/sfs lw0haUMTxBTVHGJ2aqKkkVt91bNOzaawnGA4yKo2iN6DGqKDBcb+YQ/6y3AvsjbEdMQ5 f42uVks+jv9Z2ugJoqshUr8ABHQnbxWCZ+HKKPoUys+7yP1CSzHE9Kyvb0c5wMIh0Kx5 /wgB8ozM7GQwGwQ88cxZ21sQ2zb46EtWuWvVOZ9onEFXHCH1mGbbE/ADcoTRThbENAY2 2Cqw==
X-Gm-Message-State: AJIora+Qzu6K+MXGlQmBPXJq+pu4nDU4bfPpwYE9SKTa2MvUUCZjOVUS qZWygAnJpSMgNZow74wIAAUTiw==
X-Google-Smtp-Source: AGRyM1vRPrDrxacikZJqETFIe0OJAA8P2LhYCGVuJUF8ZSjGsqA+9DUlIRzPTCDWrtaohUFQrVIalg==
X-Received: by 2002:a6b:3115:0:b0:660:d5f1:e3b6 with SMTP id j21-20020a6b3115000000b00660d5f1e3b6mr2641431ioa.99.1657306986603; Fri, 08 Jul 2022 12:03:06 -0700 (PDT)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id cs3-20020a056638470300b003314d7b59b0sm1764552jab.88.2022.07.08.12.03.05 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Jul 2022 12:03:06 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <4E5BAC15-24A0-4897-9C30-92E45FED42DE@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_30973697-3057-4492-8BE2-53C0456932C6"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Date: Fri, 08 Jul 2022 15:03:05 -0400
In-Reply-To: <18de26a3-3dff-2234-d675-50076f50bd23@stpeter.im>
Cc: John C Klensin <john-ietf@jck.com>, Wes Hardaker <hardaker@isi.edu>, Mark Nottingham <mnot@mnot.net>, rfced-future@iab.org
To: Peter Saint-Andre <stpeter@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> <A4FF92590881DBE388EE2DF6@PSB> <18de26a3-3dff-2234-d675-50076f50bd23@stpeter.im>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/EL0NyEgBG59-0MSDaBi8yQMkHXo>
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 19:04:59 -0000

<as individual>
I think it would be improper to have any substantive discussion of RSWG issues on this list.

That means there is no venue for RSWG issues until the new list is created and announced.  I think that’s fine.

I think this list should be shut down.  

Brian

> On Jul 8, 2022, at 2:53 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> 
> On 7/8/22 12:45 PM, John C Klensin wrote:
>> --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. 
> 
> Hopefully that will happen soon.
> 
> Given that the work of the Program is complete, discussing substantive matters on this list could be confusing, but I suppose there's no harm in doing so temporarily. I leave that to the Program chairs or IAB.
> 
>> 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.
> 
> I suppose that's all up to the new RSWG chairs, whomever they may be. I doubt we'll need to wait all that long in any case.
> 
> Peter
> 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org <mailto:Rfced-future@iab.org>
> https://www.iab.org/mailman/listinfo/rfced-future <https://www.iab.org/mailman/listinfo/rfced-future>