Re: [Rfced-future] Thank you and closure of the RFC Future Program
Peter Saint-Andre <stpeter@stpeter.im> Fri, 08 July 2022 19:30 UTC
Return-Path: <stpeter@stpeter.im>
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 A4BC5C159487 for <rfced-future@ietfa.amsl.com>; Fri, 8 Jul 2022 12:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.982
X-Spam-Level:
X-Spam-Status: No, score=-3.982 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, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=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=stpeter.im header.b=k/1/0R1U; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=zV4DpsbQ
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 zZXW00YAYkU3 for <rfced-future@ietfa.amsl.com>; Fri, 8 Jul 2022 12:30:37 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B17AC14CF0E for <rfced-future@iab.org>; Fri, 8 Jul 2022 12:30:37 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 1C2F43200930; Fri, 8 Jul 2022 15:30:31 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 08 Jul 2022 15:30:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1657308630; x= 1657395030; bh=ZSiaD2L6EPV0WNYJ3ahf84T491YnJTWh6XVn+K6lGzk=; b=k /1/0R1UPEXy2YAX5iA9drr/qBZNCFtueG9lf9zE2cExeB9lxMdumzHaKXGjN9Vfk SRhgwOxb6DdfcsU5aaDFCCnUFZ/B1a8IUaZPa3PP3sjBnC7T0taFRyMdkiH9W21t mh/IPHsGLC2IlrIrYhRkF+lnFFNNsvQgKT/zjOqkDb0Aj87K73y/eUPAu5yrwI6J w5UROsj0D6srz/1RLilqVzwcRwy4FrAbJBIgrB5uC0Jh+Kvm8L/JaT3Wt+Q9g26D DJnxOag/Gz4OK58kfegr4sJ3WBZu94mKaneeEsTZNN54B7zGEi/T2DSHeRe/O0RT uhAfyX1npJ2IexFDqMBcQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1657308630; x= 1657395030; bh=ZSiaD2L6EPV0WNYJ3ahf84T491YnJTWh6XVn+K6lGzk=; b=z V4DpsbQz4x7engLbInb87Qg3yX4VnEACdo/nicviDMATJ9g6wXPMEsi0DSg/ziwm wdUdcW4dvUbef8FN5WgZZCvtQufOHNy48g6up2LOZ14PDydzp6sKCkwkTwxS4xgc 2ml151Vz68MZpR1NsMp49rb0FVRacCB524QkAqDlazTh1TQ3ebBVVoXe5O9JFD8a HjC5h2lyFMpsLhI6vLOX7/q87Qx6Gu+n6lcrcOyY5oL2mifUt3VAGR0+NGDtzYug e7qopsNd3zsHUiGeoVpZJFgCLXezF51X5sTfMKp8wVeO596QLQpE7WO3nvLez73O ikRMflHil8p6cHhWqCuLA==
X-ME-Sender: <xms:1oXIYsjzIBsQW7k-GkgqIBcmet-ybScAemiBsHBAaCHSgHjEvVP0jQ> <xme:1oXIYlCYY5z5ADyAV4h90da0oQGPkWbJe7YC8g2NnR6p3AXFhC0IhPF5v7nW8-7O9 lqdCydzTFWhOSr4SQ>
X-ME-Received: <xmr:1oXIYkESYNIsRJ0b_lEJmRJeulRQPI8vbWfjrYWr6Gimp2N5mOgHfrwYNW4n>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudeijedgudefkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthekredttdefjeenucfhrhhomheprfgv thgvrhcuufgrihhnthdqtehnughrvgcuoehsthhpvghtvghrsehsthhpvghtvghrrdhimh eqnecuggftrfgrthhtvghrnhepleejueffjeeltefhhfdvveffveefueelgeefudfhtdek udeuvedvheevieekgefgnecuffhomhgrihhnpehivghtfhdrohhrghdpihgrsgdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehsthhp vghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:1oXIYtSXHVp0usKJBCGcyxOpXTgLuHpn5-Y0RTeUVbxho5ApDjCtmQ> <xmx:1oXIYpzhtQDp4mjG7IpU0Fwiyf4dvT7LTNEW5wgnzGjChRHtcd6Z2g> <xmx:1oXIYr7T2XrfVqWG1W8SR0MbRV3jdBlkhW3ZcfHxOEoKFDse-GYWzA> <xmx:1oXIYru9cmGwSKVsW1oKbvYzJrsVLoArFvpWQNhe7Fg4ydAuXdD81Q>
Feedback-ID: i24394279:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 8 Jul 2022 15:30:29 -0400 (EDT)
Message-ID: <1301db01-9dbf-8b2f-7fda-a71715b34c09@stpeter.im>
Date: Fri, 08 Jul 2022 13:30:28 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: Brian Rosen <br@brianrosen.net>
Cc: John C Klensin <john-ietf@jck.com>, Wes Hardaker <hardaker@isi.edu>, Mark Nottingham <mnot@mnot.net>, rfced-future@iab.org
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> <4E5BAC15-24A0-4897-9C30-92E45FED42DE@brianrosen.net>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <4E5BAC15-24A0-4897-9C30-92E45FED42DE@brianrosen.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/XSurS39Jj7lp5IhOAOeYJef2unE>
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:30:41 -0000
Overtaken by events. :-) See you all on the RSWG list: https://datatracker.ietf.org/group/rswg/about/ On 7/8/22 1:03 PM, Brian Rosen wrote: > <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 >> <mailto: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 <mailto: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> >
- [Rfced-future] Thank you and closure of the RFC F… Wes Hardaker
- Re: [Rfced-future] Thank you and closure of the R… Mark Nottingham
- Re: [Rfced-future] Thank you and closure of the R… Wes Hardaker
- Re: [Rfced-future] Thank you and closure of the R… Peter Saint-Andre
- Re: [Rfced-future] Thank you and closure of the R… John C Klensin
- Re: [Rfced-future] Thank you and closure of the R… Peter Saint-Andre
- Re: [Rfced-future] Thank you and closure of the R… Brian Rosen
- Re: [Rfced-future] Thank you and closure of the R… Peter Saint-Andre
- Re: [Rfced-future] Thank you and closure of the R… Lars Eggert