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

Peter Saint-Andre <stpeter@stpeter.im> Fri, 11 March 2022 15:57 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 C8EB13A12BF; Fri, 11 Mar 2022 07:57:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=dd5ExEHi; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=LBsZDDUZ
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 kg3LTHF2NoWe; Fri, 11 Mar 2022 07:56:57 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEC003A1722; Fri, 11 Mar 2022 07:56:57 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id CA3B55C00FE; Fri, 11 Mar 2022 10:56:56 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Fri, 11 Mar 2022 10:56:56 -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=e9SRlz8ks9WcjN B9xioLnlLCu1om9ymUYBz+y790w5E=; b=dd5ExEHi6jPEFDkzt3f9mdYrH3PlmS nAhGCswY+lYQ8k6BBEoVL+I/aQnuPDtGQ1sbmd4StpGvOqX5iMKuFS85G3icMtn5 0kb8yZUeykUdLcotEVCFKceFq7edw24LkjoK+ICmwyZq1WidP4Mj/IylqeSbSoDl yQZgGCZfrM+sWMG907944DjZbgRdjyfQPRreImA16PkV9TZ2DbzDLuAal0bhd9eK I8c8etvhemi9yxK1ap932VK10seJJ5rVPW3/5B1jz/wt85tutPZlW3iTDjjlKHKL sHsot93Yblf9++SS6sgoBd8GZPElZFWzAVyjp+8E02onkti/6dxlowIw==
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=e9SRlz8ks9WcjNB9xioLnlLCu1om9ymUYBz+y790w 5E=; b=LBsZDDUZGf3Dcd7Nygs6WyePboawgGsKr+yj/5FpKo7r7y071NeDVS/Nf tUNVVbAavoimF1Nln8j5dttL7P5t7586Sjp+2PEbljkM5wh2DW+4tZxq6UjM6fjE fbO5J/gSij2/NoXNgN4cExEjrHSR7zazXcoDOwc1eXfEU9AbN9zyJGuAWRleLvs9 DG5Lbf6k2ZOL2X27yIaOHzD5SMqV8RFECkPq/dTn8TlgS9NXldMO7DQoGDTP87Vz BrAxP9zXSdiwWCbS5vNOCNFyRw/qkqQsRGNQue1Vl3GeCwN24PNLN287MW2EJcTY W+yv2+Sf/dj+9M23hZyw5YPV7fbKQ==
X-ME-Sender: <xms:SHErYqmEVjjhoP2-QqNPFSHeioyQTxxgQ1Z4quZ6XAYjqH7G5hAnog> <xme:SHErYh1uyNmdhqwmxpv8pL-sxkvmrG8UOI9mLvjA2hbD7_rFmyffgvLrVwo7eWbtW AZUWxeY0jujfxy0eQ>
X-ME-Received: <xmr:SHErYopIYW0YHDDzImgRi0HKiWBQEPB7x3p8qq_bYyReHE-DTWBvGk3kliurcBhhiNeusdYVIHJOqgHYF84EpNILWFU9FTZfieBY3B8>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvvddgjeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfvfhfhffujggtgfesthekredttdefjeenucfhrhhomheprfgvthgv rhcuufgrihhnthdqtehnughrvgcuoehsthhpvghtvghrsehsthhpvghtvghrrdhimheqne cuggftrfgrthhtvghrnhepgfeugeefvdekteefgeekkeeggffgueetteehgedvgfffveeg kefgleehtdegteefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:SHErYulKs8ldUVoT1TfSM_9knTjK1bhh7bslEbiJI0MF12p3ikWyyQ> <xmx:SHErYo3_s0-PqqDAggCeVo7KVoPl5y2-foIRmFnfou65470pBIrIyQ> <xmx:SHErYlsZHwQwixPJKVSwdOCdiSP9dj0RL7hFm9Ez6GSP0qUn1Oo16Q> <xmx:SHErYlwvke3mjSLLoUA4FlnPMiuJTv_kOth22QAwgRWTjNZLaLPaWg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 11 Mar 2022 10:56:56 -0500 (EST)
Message-ID: <4c0e8ce9-000c-a508-5102-d226d99c395f@stpeter.im>
Date: Fri, 11 Mar 2022 08:56:52 -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: John Scudder <jgs@juniper.net>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, IAB <iab@iab.org>, The IESG <iesg@ietf.org>
References: <1B8B9928-6092-45FA-A58D-D55706013B50@juniper.net>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <1B8B9928-6092-45FA-A58D-D55706013B50@juniper.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/-ABbxkt085qS6165NSP8b-zOj5w>
Subject: Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model-12
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: Fri, 11 Mar 2022 15:57:04 -0000

Hi John, thanks for your review. Comments below.

On 3/9/22 5:02 PM, John Scudder wrote:
> I gave draft-iab-rfcefdp-rfced-model-12 a read through, LGTM. I have a few comments and nits:
> 
> 1. In 3.1.1.4 we have
> 
>     The IETF LLC is requested to provide necessary tooling to support
>     RSWG communication, decision processes, and policies.
> 
> Is the LLC also requested to provide for necessary staff support, as it does for, e.g., IESG meetings? If not, that implies the RSWG will have to manage its mandated minute-taking and publication on a volunteer basis, something I wouldn’t recommend. If so, it’s probably worth calling out the request for staffing explicitly, or maybe broaden “tooling” to “resources”. (Hopefully all will agree that staff are not “tooling”.)

Per Jay's reply, I've added "and staff" to the RSAB section (but not the 
RSWG section because we do not envision needing staff support for RSWG).

> 2. Section 3.2.2 #11 is “A proposal without any CONCERN positions is approved.” Is it deliberate that as written, a proposal with no YES position would be approved, as long as it had no CONCERNs? It seems to me that “A proposal with at least one YES position and without any CONCERN positions is approved” would be better, but maybe this has been considered and rejected.

This was deliberate, and discussed within the Program.

The RSAB is different from the IESG in that it's not expected that there 
will be a sponsoring RSAB member who necessarily ballots "YES" and 
advocates for advancement of a proposal. The impetus and primary 
consensus comes from the RSWG. I suppose we didn't see much difference 
between one YES without CONCERNS and no YESes without CONCERNS.

> 3. In §3.1.1.4, “The RSWG is empowered to hold in-person or online-only meetings” triggered my inner literalist to complain that it could be read as precluding (say) hybrid meetings. The last sentence in the paragraph is probably good enough to eliminate doubt, but re-wording the quoted sentence like “the RSWG may hold meetings in a variety of formats, including in-person, online-only, or hybrid” might work even better. (Throw “… but not limited to” in after “including” for extra pickiness points if wanted.)

I'll change that to "in-person, online-only, or hybrid meetings".

> Nits:

Fixed.

Peter