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

Peter Saint-Andre <stpeter@stpeter.im> Tue, 01 March 2022 18:36 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 D244D3A096E; Tue, 1 Mar 2022 10:36:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 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, RCVD_IN_DNSWL_BLOCKED=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=tY+SPecq; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=cgq4ggDC
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 7JzuB39I4kyD; Tue, 1 Mar 2022 10:36:27 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 836073A0965; Tue, 1 Mar 2022 10:36:27 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 6E58D3201DDB; Tue, 1 Mar 2022 13:36:24 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 01 Mar 2022 13:36:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=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=kowGV/Htgb9VMU 8iTWeoExWS53SvwmgsHxLNwLBTmnQ=; b=tY+SPecq2OrVfYLCOIOA3jRTKhB/i/ ppJ+kLNpZOEJLrxoymeqQe54SXERb6X0mO+9+zGZkYsn+tRjrMXS5Ev1HYCOYLZG MD8jeQ6IRA5GcqrGHj/jMZrNPMgB6RamC3ihui+OdKACn3VHTUkb9ZLUMMMMCmnL bJHNCZszdkvJXJgxFhwuBCHgUBzwsZchvmq5fIk67/mBLBlmWxUdrNa/i2D5lVwW ydeAO3Y998fgu+GH5oIbTzqxg75yhcQF6F2CiEMzQS2iF4CeWznNm1PoJivtSA1H rXFel6vPzJ1nAQrqfDCwmXQ9Qcus5KT5mXd2jC9ElpUA3zZx9QdMMeeg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=kowGV/Htgb9VMU8iTWeoExWS53SvwmgsHxLNwLBTmnQ=; b=cgq4ggDC 9qp/sWUUlNVKvz5Ts7SoKdXXjp04f2dul0mJ++bclujOuefgDujB4HaNtco0Qi4V hcDsBiM15EAejxWYDJIBZuXwJaNK6rcSWEP/ZkFIEzWsBnlLZltN+9QEx/oWlsAD 7vMPw3sLSmUrl8UP7YmoXA+BgFF+/IlhVyfImMcAW5nfXOoFciHzq1xeoPRUHWM/ btatFEXoF3mwFnTfY01eT5JZZ26iioph4R5tm0UmBRwWHVM2ofezLQMCurFzHyjm 8FVO5piZ3ZKLD/9LvftSDfhnaC5RoONqvhDxFJmygNzXtXzdchnEaXfMzJEFr33m V1s0NLoGn0S8dg==
X-ME-Sender: <xms:p2ceYsGRzv2MarSG5y1J_kywkY7zoSw83gA3oTM1FVcy-v69CDTv-Q> <xme:p2ceYlWRyav39vZ3ssUX0EiJ88YO-ZcvBqjmCkRf_42N8ZxNpzQDiCzRffbXXMbgq kl4_By8fHtubYVYNQ>
X-ME-Received: <xmr:p2ceYmKXIeWuXPoqvKn_sHFQ7hgE_6xHKZ4VaDNA-QdMp1GgHqN3KMbesU3VhYtqM9phVZ2XjpNLuslNYUQwYeujT592Wkh9-YQpQX8>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddtvddgudduvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfvfhfhufgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpefgueegfedvkeetfeegkeekgefggfeuteetheegvdfgffev geekgfelhedtgeetfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:p2ceYuHsiow9Yy8ZwlNL4iZ2pX3Rds99IyaFP9p6fdC6X82inD31Pg> <xmx:p2ceYiXGqGHYkYXpvH--o6YpKghNFI8yDLnPvpfOH8X44O-rRYfqkQ> <xmx:p2ceYhM45Hcm6AOMH2kLCiC0G83h5RrxNMcHv6P8244mZRiTe4-KuQ> <xmx:qGceYhRtpgDsASfBia8E6-C8DrQEoDpRgNAXjLthjGYqfbOcpUnEBg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 1 Mar 2022 13:36:23 -0500 (EST)
Message-ID: <0c1711fe-bc05-e6b0-2f94-eb1c24ae3766@stpeter.im>
Date: Tue, 01 Mar 2022 11:36:19 -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: Eliot Lear <lear@lear.ch>, Paul Hoffman <paul.hoffman@icann.org>, "rfced-future@iab.org" <rfced-future@iab.org>, "iab@iab.org" <iab@iab.org>
References: <74AF211B-741E-46FC-9E35-8015D5254515@icann.org> <f55fba34-c449-8566-0423-147fc1fa3363@lear.ch>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <f55fba34-c449-8566-0423-147fc1fa3363@lear.ch>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/BeDCSwncr6ix2dMqwfXlrcU6OSA>
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 18:36:33 -0000

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).

>> Someone is going to have to tool the tracking for RSWG documents after 
>> they leave the RSWG, given that this is a new process. That might be 
>> informal (but public) tracking, but I suspect that formally tracking 
>> the various rfc799*-bis documents will prevent later issues from 
>> arising based on missed cross-dependencies. Maybe adding a sentence or 
>> two about this to the current draft will keep it in our minds as we 
>> move forward.
> 
> Good idea.  Perhaps something along the lines, “The LLC is requested to 
> provide necessary tooling to support RSWG and RSAB decision processes 
> and policies.”

WFM, although editorially I'll split up the RSWG and RSAB requests, 
placing them in the respective "Mode of Operation" sections.

Peter