IETF Logo Mail Archive

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

Peter Saint-Andre <stpeter@stpeter.im> Thu, 10 March 2022 20:20 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 52BCF3A1BA1; Thu, 10 Mar 2022 12:20:56 -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_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=MPjzJBsy; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=fhlJwL1m
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 vPhg2L_JccWy; Thu, 10 Mar 2022 12:20:51 -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 99FD93A1B9E; Thu, 10 Mar 2022 12:20:51 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 84F7A320046E; Thu, 10 Mar 2022 15:13:39 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 10 Mar 2022 15:13:39 -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=hyRk3zbHQaZsmI UADvN71/m8kvnCVVgaxgpiydfZ01g=; b=MPjzJBsyIv84xBnT84zu6LclXqDCES ht5ewmQbjRwuTreOAz1hFdDR4U9YC93zLlXa1u0pfo2oU3tW+bQdNl0v/xHCQMRX VkG3CQ3z3rt7ZgacezqN9x0QW7YdsuFJUz1bhpVOt82Tup6sPfHUvqJ99roueOcp jdKRsR8vgzvwdGZ4ZJaIlqX0eeTtad/iSPvgPeZoWZJdEQuluiV9fRLokNEr0g+f BivrJpe9uJq6cQRpU+VpjnEgW+jJ290TsS4mTlrpkZ3wqAAVatqfCd+urFnrxt9z yVPjcQNBtlu8bRk8x7Dr0bObLQE+2L4n1JvllEiulRoFcwJyzK3bL3sw==
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=hyRk3zbHQaZsmIUADvN71/m8kvnCVVgaxgpiydfZ0 1g=; b=fhlJwL1mn3K6EIevIHpp+m+jPqctJeQ7F8GvfgawRnqwvwNHOtq7j6aB5 OH2RVMOGeWRnUTjY1POi8VnFGdqgnSxsC5j4QUJ6HkzTf0rIQtihsqr+dEYbTzur AUPBhJNvLRa+NGloCjyPFkkLjaM7uJCGHzTHgCB+JHRoRp/K0lx2JYSge8r8f2qY ekxVZdb8aNZQ0MKeJQHbAXcpLOEDJtCnzq5ZWU64ybVdRTlPerBGp0PW5jmUdS8b KVCqz5OYHeYUT9uqJ6g8kINyg7Q47g4ryDP/3jme0NYtAOfWwDMJq6B/cXMNU1Gp eNgm0q1pz8rByG6wjnh8rvc/1CoCg==
X-ME-Sender: <xms:8lsqYtIny2nJMLxGnNGfKtxzF6eNhTfg2KkUyumkb4CYkjB0AkxMVQ> <xme:8lsqYpK81KpsXknSFEhYZ3fnb0I-BZpEdC3trab6H6sSt7iIdd_4KvyYwnWxPxmIQ 3XsT-1ruP52JT526A>
X-ME-Received: <xmr:8lsqYlvO90eghxJEtBukfonE2lb1A7rI5jP-vfRf-3zrsvvkjUb5neF_zYDhxhCNCdiLRXNF3b9NknBlCvRamEPJiL6uilMKqRm-eeU>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvtddgudefhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfvfhfhufgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeevgfehhfffvdejkeeukeehhfeilefgueejgfegteelkeei heffgfeltdekieegkeenucffohhmrghinhepihgrsgdqrhhftggvfhguphdqrhhftggvug dqmhhouggvlhdrihhtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:8lsqYuYKsLJ0TSzg-Vf443x1dAx1sEMjNQVq9Ry-i_nBjPVvKum0jA> <xmx:8lsqYkYMC_uxMGc0Gr9s8ltGLpnqYfmpbXTHk8jeOdUsN_BhBeHwkQ> <xmx:8lsqYiC6KVZe8XOkXAWHHa9fDheZbiO9wkCsg4aialGKw7fdXRWlqw> <xmx:81sqYsFDQ7JMz3z6N9RhM9jj9jqOmvZAho9WZ1FJa_oxNDZLH-yyGg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 10 Mar 2022 15:13:38 -0500 (EST)
Message-ID: <134294e0-5bd5-9b22-2d95-f6032e67f516@stpeter.im>
Date: Thu, 10 Mar 2022 13:13:32 -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: "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>, The IESG <iesg@ietf.org>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Internet Architecture Board <iab@iab.org>
References: <BY5PR11MB41963ABAE51BC46E205087BDB50B9@BY5PR11MB4196.namprd11.prod.outlook.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <BY5PR11MB41963ABAE51BC46E205087BDB50B9@BY5PR11MB4196.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/IpRdt86k0o_2VRKxngCwUpyzAAQ>
Subject: Re: [Rfced-future] Comment 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 20:20:57 -0000

On 3/10/22 3:41 AM, Rob Wilton (rwilton) wrote:
> Changing the title to help ensure that this comment is tracked against draft-iab-rfcefdp-rfced-model.
> 
> Still suffering from Covid, and I'm now way behind on email, so perhaps this has already been resolved, but I think that the issue below needs to be resolved before the document is published.
> 
> Regards,
> Rob
> 
> 
> -----Original Message-----
> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> Sent: 07 March 2022 19:40
> To: Rob Wilton (rwilton) <rwilton@cisco.com>; The IESG <iesg@ietf.org>
> Cc: draft-carpenter-rfced-iab-charter@ietf.org; rfced-future@iab.org
> Subject: Re: Robert Wilton's No Objection on draft-carpenter-rfced-iab-charter-06: (with COMMENT)
> 
> Rob,
> 
> On 07-Mar-22 23:58, Robert Wilton via Datatracker wrote:
> ...
>    
>> Hi,
>>
>>      Note that RFC 2850 states that the RFC Editor appoints a liaison
>>      member to the IAB.  This does not change, but refers to the RFC
>>      Editor function as described in [I-D.iab-rfcefdp-rfced-model].
>>
>> It isn't entirely clear to me exactly who (as in which person or body) is
>> actually responsible for appointing a liaison member to the IAB (given, as per
>> draft-iab-rfcefdp-rfced-model, the RFC editor function responsibilities are
>> split up into multiple entities).  My assumption is that this would be RSAB,
>> but perhaps I mistaken.  Would it be helpful to clarify this - perhaps in
>> draft-iab-rfcefdp-rfced-model?
> 
> Indeed, I don't think it belongs in the IAB charter. Hence I suggest that this
> is really a comment that the IAB Program (in Cc:) should look at.

This is a good question.

One key assumption underlying version 3 of the RFC Editor Model is that 
the process for policy definition and implementation is no longer under 
the purview of the IAB. Therefore, I question whether the IAB still 
needs a liaison from the RFC Editor Function (whose responsibilities are 
now spread across multiple entities) and I would defer to the IAB (cc'd) 
on whether they think this is needed. (If so, we'll need to figure out 
who does the appointing, but one step at a time.)

Peter

v2.23.0 | Report a Bug | By Email