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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 10 February 2022 19:52 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 EDA773A060D; Thu, 10 Feb 2022 11:52:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 d2LbqzaGMLuS; Thu, 10 Feb 2022 11:52:50 -0800 (PST)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B6C53A08B5; Thu, 10 Feb 2022 11:52:49 -0800 (PST)
Received: by mail-pf1-x429.google.com with SMTP id 9so9264697pfx.12; Thu, 10 Feb 2022 11:52:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=dl03wSNANHSg5oStMPlBT2GRC6BFVLaxfjN7vdqtWVc=; b=fDW0gtX6j0vhEW5FJM8sWvaoKQJqBm0WnSV5kihE0Zt6w0Xoo8aPF5dNWltB3hkfOg +rHxcyjaX8PWJoc/UECBMdHyfoNyR+nOxmRp4VU6DLLTfWg/VPOK/InmowIbRxl09FPq H5O12O9V85yjoYNz0f7ykA1ceHr6jnOf6Y3uJpwZahZ+hxdlg7LfV8RwOtxQMSkBn+/K 2fuQFrCGWTEWKsU0WvTUQxdXdDM2dWAWjsiZrqiLqMW94tjr5Wz1jIB8UELqr/43ymoL eU+Oh7OS9Scuj1uA9bhc8qfcHK58g3czEaEwb2MrD4wWSuaFfDgN2qnHp0OT4gCMcf4c wLcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=dl03wSNANHSg5oStMPlBT2GRC6BFVLaxfjN7vdqtWVc=; b=Qi5cMlAjMKzc2PuUW68ApRjUvfUAUlKC6Ysau7I/VWq0gm67u9wjre4fegq7kf6jOj 2rlgGWBQ211Q4tbYlphhCB8Ydi3ALS3ngd3W+WoOcKRIHPFHyud2JDHi872Zu1L6aA52 VO2V07kx1HQLCvOpf7b2KLqm012aFpWzFKGbDDQDvWEX6DC6n4Mq2LsnopKqvlAMqPN6 gksiHaLpud4kCSc6QOd9vIQI9IKEfCInEEODFfdDvMHKk6I63mPBjXd30/oH9dzv4b9z sj9x7+UH9WFyz83LnZUULwju58/SsMS2MbVaawwTaXrGb3QXDJbNCfJtPs2cxJhNuIeP CNWg==
X-Gm-Message-State: AOAM532dU54Rg5AmRr7J6p8flYfwmbburkRC1WQmRgTkGlmBbbI/fW5k wGMY3DQqUDjH7BEOOkK4JPLs0KIPWPv2Qg==
X-Google-Smtp-Source: ABdhPJzzoAgiLLYV4tZUuocrxNMRvG3jyuaXDg5rWqeWPh70CmrDdSakZoF4TnNJnWCcQQN3SUSaOA==
X-Received: by 2002:a05:6a00:228c:: with SMTP id f12mr9162550pfe.34.1644522766074; Thu, 10 Feb 2022 11:52:46 -0800 (PST)
Received: from ?IPv6:2406:e003:1180:7001:80b2:5c79:2266:e431? ([2406:e003:1180:7001:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id l12sm3081692pjq.57.2022.02.10.11.52.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Feb 2022 11:52:45 -0800 (PST)
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: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e41f63f4-7d59-3498-80e5-abae354c4281@gmail.com>
Date: Fri, 11 Feb 2022 08:52:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <f55fba34-c449-8566-0423-147fc1fa3363@lear.ch>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/VVnN6G89w6tv7uaMRGpFk2NtlCE>
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 19:52:52 -0000

On 11-Feb-22 03:42, 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.

There's a slightly wider operational question of which new mailing lists will be needed and which existing ones need to be tweaked or closed. IMHO 
that doesn't really belong in the founding document.
  
> 
>>
>> 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.”

Make it "communication, decision processes and policies" and that also covers mailing lists and conferencing tools.

      Brian

> 
> ?
> 
> Eliot
> 
>