Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model

Peter Saint-Andre <stpeter@stpeter.im> Tue, 01 March 2022 21:05 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 602483A0E71; Tue, 1 Mar 2022 13:05:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 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=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=cXtOPGVQ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Ki1VloLF
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 sYTS_qLzcsus; Tue, 1 Mar 2022 13:04:56 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BDFE3A0E7A; Tue, 1 Mar 2022 13:04:56 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 0F3D93200BD2; Tue, 1 Mar 2022 16:04:52 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 01 Mar 2022 16:04:53 -0500
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=fm2; bh=4vPR079KSxPvgA 5Q4TWCkC4oyScFHjLtj5Mft4Gl2LQ=; b=cXtOPGVQ5Lq6VcBnKnmTh68TdFqyaG hGL2X1YuqlG7YI3fA8IjOzEcty8RlYQT3maktf+IvqWoCoArCFzJDqYa3G3tWTjp +V9XcBp0eev5xUqfPqjxvV22Oxtnj3Aa+QDjjLSagtitH4qukSw/awG1YJuGoRm6 0EjfT1PgafugMpMb1cNFbH8NZkPAR5PeaSfg7eishdgteedDjDMHtLjMBE1HwuAB eghRTI+D4D1L/eNQtSyNqjH3zZKMSCcy2hkAdq7NxH+E0sSK2gbQmdJhl2LyccRE sQykRZux0f8FrpgBi2EOKSifOs4bIvUU6f4gLJDwoev9bJrxePwjUx+w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; 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:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=4vPR079KSxPvgA5Q4TWCkC4oyScFHjLtj5Mft4Gl2 LQ=; b=Ki1VloLFdOI0RPV9ngETxokajReHLo53Z51P1y3AiknG6wr8+Bq329cRP 6rRH5i+DiuuAmm0COFOnA1fz5fotK/1LNZHwwpf/ImmxZjmDtTzsf0ey82zF+MIP v/PgIyyqegXeWbkjf5OiZAHuUjhBvrWojgcIxM0wi2allkI3YVuku0tgS5r32kg6 7ugcUFj8HKfpOAptr9sOkTtKJc261Ba2SHIe7IkVqwhC30eF81j4BBE2ngKOSXdL KzY3YCax9OiEbZw0kai6Nw2KxmjQ9ytQDKLdi4yxzX8OFg1YCqBifH0sxO2MVGZ8 zoiT+DikrU56ya4rCl861+tWXZh3g==
X-ME-Sender: <xms:dIoeYlDhl-FXsohNLEQbIhzvwWQJhU47qWr4Y3pkZQ-dxXWUTbtkxw> <xme:dIoeYjjrzt8Q4guTXIlfh4H3U0btqAWF8U9FPkTywO0XhMOYPKU_R1vCtqxcwlCC9 VyuXEQEnUrfOCZF6g>
X-ME-Received: <xmr:dIoeYgnPbpGbv795YfnJcOu7rQU8sUGl0xmtjUIkV4s68gFJqn26WkSZ3cdZBjHV6s5VR2J--OT_kPIVxdpwEXrITvZ6ds8T2F5u5KY>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddtvddgudegvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeevtdfgteetgfffveehtedvudegudfgleevfedtleevtefg feeggffgfeeludekheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:dIoeYvyoX2lFSljSSHgMWJnpMpwFl36fr53SigLorxlLXlqalJdh9A> <xmx:dIoeYqQfIVzxEK3h4mgYy6BHHPGwEWrqpBHNikXSq9RIRne5qO_xJA> <xmx:dIoeYiZtnuBZFyFGZhKgukrX-TkoJqDxK1ESHuUFNt3Hxhj3QMN_Bw> <xmx:dIoeYnKJU_X-F38aKRjuTooU_yNd2lGGpXIn-Z71vIIhySQSepioYQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 1 Mar 2022 16:04:51 -0500 (EST)
Message-ID: <c75a8f66-3170-986d-7973-ff8758b4996b@stpeter.im>
Date: Tue, 01 Mar 2022 14:04:50 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Eric Rescorla <ekr@rtfm.com>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Paul Hoffman <paul.hoffman@icann.org>, "iab@iab.org" <iab@iab.org>, Eliot Lear <lear@lear.ch>
References: <74AF211B-741E-46FC-9E35-8015D5254515@icann.org> <f55fba34-c449-8566-0423-147fc1fa3363@lear.ch> <0c1711fe-bc05-e6b0-2f94-eb1c24ae3766@stpeter.im> <CABcZeBPqGHt0KD4tjQZFd7SVRwQHVa7fj7wJ_LYCn-3XQKjfjg@mail.gmail.com> <de6c4153-ebed-47e2-7657-3ad7f917dd73@stpeter.im> <2b400d58-5985-016f-e722-2b61df64e146@gmail.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <2b400d58-5985-016f-e722-2b61df64e146@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/oNMr1D8RU1BAS1gKxU2GpgyjJis>
Subject: Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 21:05:02 -0000

On 3/1/22 12:53 PM, Brian E Carpenter wrote:
> 
> On 02-Mar-22 07:52, Peter Saint-Andre wrote:
>> On 3/1/22 11:45 AM, Eric Rescorla wrote:
>>>
>>>
>>> On Tue, Mar 1, 2022 at 10:36 AM Peter Saint-Andre <stpeter@stpeter.im
>>> <mailto:stpeter@stpeter.im>> wrote:
>>>
>>>      On 2/10/22 7:42 AM, Eliot Lear wrote:
>>>       > Hi Paul,
>>>       >
>>>       >
>>>       > On 09.02.22 17:46, Paul Hoffman wrote:
>>>       >> Greetings again. The structures proposed in this document seem
>>>      like a
>>>       >> very good way forward. The level of detail about the
>>>      expectations on
>>>       >> each group is a good balance in prescriptiveness.
>>>       >>
>>>       >> Two small thoughts on the current draft:
>>>       >>
>>>       >> The future status of the rfc-interest mailing list is 
>>> unclear; see
>>>       >> Section 3.2.3. Given it s current contents, I could see that it
>>>      would
>>>       >> easily become a parallel track for discussions that should be 
> on
>>>      the
>>>       >> RSWG mailing list. It might be good to close (and certainly
>>>      archive!)
>>>       >> rfc-interest unless it becomes more moderated by someone 
>>> pointing
>>>       >> discussions to the RSWG.
>>>       >
>>>       > I like the idea of at least having some RSWG participation to 
>>> point
>>>       > people to the right place, when necessary.
>>>
>>>      Keeping the rfc-interest list and starting a new list for the RSWG
>>>      might
>>>      indeed lead to confusion.
>>>
>>>      Here is a proposed change:
>>>
>>>      OLD
>>>
>>>           The RSAB seeks
>>>           such input by, at a minimum, sending a notice to the 
>>> rfc-interest
>>>           mailing list or to its successor or future equivalent.
>>>
>>>      NEW
>>>
>>>           The RSAB seeks
>>>           such input by, at a minimum, sending a notice to the mailing
>>>      list of
>>>           the RSWG (which should supersede the current rfc-interest 
>>> list).
>>>
>>>
>>> I actually don't agree with this. I think the WG should have a 
>>> separate list
>>> that is moderated by the chairs. The rfc-interest list can continue, but
>>> I think the new model deserves a new list.
>>
>> Can we specify (at a high level) what topics are appropriate for
>> rfc-interest as opposed to the RSWG list? Would we envision that rfc-i
>> is more for implementers? We already have a plethora of lists (rfc-i,
>> tools-discuss, xml2rfc-dev, etc.) and it's already unclear where certain
>> topics should be discussed.
> 
> Please not. I don't think we should cover such operational details at all.
> (Do you realise that RFC2026 refers to anonymous FTP and gopher?)
> 
> How about being *less* specific:
> 
>            The RSAB seeks
>            such input by, at a minimum, sending a notice to relevant
>            mailing lists.

IIRC folks wanted to know that there was one place such announcements 
were guaranteed to appear (kind of like the new-work list, I suppose).

Peter