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

Peter Saint-Andre <stpeter@stpeter.im> Thu, 10 March 2022 01:11 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 E35223A0831; Wed, 9 Mar 2022 17:11:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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_MSPIKE_H3=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=R0azHM0l; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=SbXQqUe4
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 kULm7TMmOc0M; Wed, 9 Mar 2022 17:11:03 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 385653A082D; Wed, 9 Mar 2022 17:11:03 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B9FBE5C01D6; Wed, 9 Mar 2022 20:02:40 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 09 Mar 2022 20:02:40 -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=Aymj9GSAvAirXJ t3kvg9WFH/WI37Y7kLZ+bfZIPwbKg=; b=R0azHM0lXf8TU9OstGMSMVtE1WRo8u 0HV/k3+qytMIGGQv4dzoESdjDYIRS8E3//Sc71KR1F1TV9Rse/3D64ujuNAL6ifJ 0qpeeM7ncKbbZOuzTXEjC35Nut752QK+FCHKJhEhe5d2WEm3vtKBVxYNV9Vqeu/b XvVstDpNWAMyksiF24BKwIFGhA9/bxzzGUysYYP0A7yUwzUyte2GvYbb5WgpsK7f w8eghKP7Z5Z+X2XF6HvI1rMf/fYDkA4kUo9AJ2sTMFuyXZWyM6m/b3Oh+wNgJRpM IeR/C6c0T9CAxzyjqwRxA+ya4XPm7tdy7jTFpeqrYJC3AhAXdnxiFzxA==
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=Aymj9GSAvAirXJt3kvg9WFH/WI37Y7kLZ+bfZIPwb Kg=; b=SbXQqUe47d7WCtF34eQFShbgZ8KvLT4uQK3XCTY3PNHRCD8cnJnpE9Qhh L9TW53JjoFO7xhUd8bjfQXEmE5nHZhpG/D1RkX/CbKJNQ6j63CaOSiSPXkA28NP8 BSbX76x7aFHoCqvTaEwWkyYjX4p7vRzOj15Cxi9s3Eam/omgF5fAm9FIk3XYskze IIgYGTLmK6Pw3F5ZkjbBOlu8yzdtsSzIgGmTmB075zhXy0O/XphHHuG5GyAKRDZp soP+k4dyDHwPjvEU+H+ojaK5HXY7x3XictkQyAoWi6vSW21BndWaDuDNgDTsVrmq 5IgaxRMf1FJbjeFwggGAnJMABmNfg==
X-ME-Sender: <xms:ME4pYuSDoS4i9wf7Nysmhqdz25Ym7xk9lBt3ZNYnRXzS6tP-f883ug> <xme:ME4pYjwcao3tKJRN8_6voisq-vxjats8mFyMYD4RcHS1KOqTtGlefTKlnwUkEf5Bg fxLeqqpj0Agak5m2Q>
X-ME-Received: <xmr:ME4pYr1FPJKaXJ6SFvTvightkAlmyq3JaKagO5KXRhF8aTv8PoiK_kLSyykYwDq79UJyVCiI0Jge5FwI1zPv6nT6fjO_CzfGCqqhPGc>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudduledgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomheprfgvthgv rhcuufgrihhnthdqtehnughrvgcuoehsthhpvghtvghrsehsthhpvghtvghrrdhimheqne cuggftrfgrthhtvghrnhepvedtgfettefgffevheetvddugedugfelveeftdelveetgfef gefggfefledukeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:ME4pYqDrcN8Cj-9bVz3ovMFGvLqwkEABgkeRFnS8QrcuvXOPlSm-uQ> <xmx:ME4pYnjXicpv4zbNPbLKtMX4Z5Efy8cmd-YZ-s271araEDT0FIX6rA> <xmx:ME4pYmoqzUdARfwLXhPp3Xq5AJwHZrzgGAXnLp80pRHdBRJ8NNfAug> <xmx:ME4pYndYjWdgZ7OrKXnC2fcBYUeIUm9QK2zuO11iyAMvLWIwNnXiaw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 9 Mar 2022 20:02:39 -0500 (EST)
Message-ID: <b8653f5b-3c29-9b51-8d19-58944904b278@stpeter.im>
Date: Wed, 09 Mar 2022 18:02:35 -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: Jay Daley <exec-director@ietf.org>, John Scudder <jgs=40juniper.net@dmarc.ietf.org>
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> <0158B5FF-15CC-4F32-AAD5-6ACC120559B8@ietf.org> <68DA3FCF-DBBE-41C6-8ADD-33F8424515B2@juniper.net> <64709CDF-1624-4A2D-9B6F-94083EB0F005@ietf.org>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <64709CDF-1624-4A2D-9B6F-94083EB0F005@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/PUmG5GqUv4bYYdzToKUCfiY0t4c>
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: Thu, 10 Mar 2022 01:11:09 -0000

On 3/9/22 5:44 PM, Jay Daley wrote:
> 
> 
>> On 10/03/2022, at 1:39 PM, John Scudder <jgs=40juniper.net@dmarc.ietf.org> wrote:
>>
>> Hi Jay,
>>
>>> On Mar 9, 2022, at 7:06 PM, Jay Daley <exec-director@ietf.org> wrote:
>>>
>>>> 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”.)
>>>
>>>  From memory, this was specifically decided against, on the basis that the RSWG is akin to IETF WGs, which do not receive staff support, while the RSAB is akin to RSOC, which does.  The reference to tooling is, from my reading, to ensure that the RSWG is added to Datatracker etc rather than specifying any form of special tools resourcing.
>>
>> Yes, I had crossed up the RSWG and the RSAB in my mind when I wrote that. Thanks for the clarification. However, when I look at §3.1.2.6, on the RSAB’s Mode of Operation, I see the same “tooling” language:
>>
>>    The IETF LLC is requested to provide necessary tooling to support
>>    RSAB communication, decision processes, and policies.
>>
>> So, I’m not immediately seeing “RSAB… which does”?
> 
> "staff support" could certainly be added there.

This seems right. I might have committed a copy-paste error here.

Peter