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

Eliot Lear <lear@lear.ch> Thu, 10 February 2022 14:42 UTC

Return-Path: <lear@lear.ch>
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 6463A3A0D2F; Thu, 10 Feb 2022 06:42:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.603
X-Spam-Level:
X-Spam-Status: No, score=-1.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 Mm33e1S4jLNE; Thu, 10 Feb 2022 06:42:53 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 623B33A094E; Thu, 10 Feb 2022 06:42:51 -0800 (PST)
Received: from [192.168.0.227] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 21AEgmpE731001 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 10 Feb 2022 15:42:49 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1644504169; bh=BRoCaY1YcHUtD5ITr/sFC/L0iLZW6/OUHw3gS1Oe8V8=; h=Date:Subject:To:References:From:In-Reply-To:From; b=OVMnGLadeHXiqIoSAL5rqlMVqzJcYCJ8xAHpE9NPgyk+Mh0GPSaZF4Q++bJbL+SQH X87ReT8e8nTLE0cWdG3zIX8Kx4qGOsHTyMzaoier7lbYSFkbf0pIAXSy6z0kowRL7Q KNEO9sK5RL7rt76otzfV3YLY69CVlW95DV/bAtqU=
Message-ID: <f55fba34-c449-8566-0423-147fc1fa3363@lear.ch>
Date: Thu, 10 Feb 2022 15:42:48 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1
Content-Language: en-US
To: 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>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <74AF211B-741E-46FC-9E35-8015D5254515@icann.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------jqeEf7AsKN3F0By38mCdiKSt"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/FGtCjDrorxOF4y5i_a846QyvW_Q>
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: Thu, 10 Feb 2022 14:43:07 -0000

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.

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

?

Eliot