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

Peter Saint-Andre <stpeter@stpeter.im> Thu, 10 March 2022 22:31 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 D005B3A1C82; Thu, 10 Mar 2022 14:31:19 -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=KsR28ujC; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=UvnS+SJt
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 PGgAPbF3PMf3; Thu, 10 Mar 2022 14:31:15 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 492653A1C39; Thu, 10 Mar 2022 14:31:15 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 315DF3200933; Thu, 10 Mar 2022 17:31:10 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 10 Mar 2022 17:31:10 -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=A/wlJaSImFjyMG xZCz7Me+T6W50y0qKxiuYFrMNKVH4=; b=KsR28ujC65XUExZmKWWDRVOYUOpnnB 5tyMFtoZqX3iDmfazG0wvY1GIp8SKwmhM/YZSBvtFAtmRN3iC3OHQQXqi8p/U6KD LPShpmf3pwEmDmUFTgW8SYVnOIcJAwn9uNlJlV5JKhBjMR8nUlejtgKzSf+d1pbI UXSlPc1N/QSxYTM3z1wyxp9iXRWf6Ll2D/fhe/i3MAVJ+MK85AWk1m4v4D/zoUrL ItukdeZV5ukaspwv3NXDvE9EFQIyCAmoZDXFlKVNRNalZxJMTIHkYSv/caaFhXp6 uJL9E5UGY05jeOZ7a093sfxwNMogzIsZ1hsFxB+W5A+2oPApOnhsZL7g==
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=A/wlJaSImFjyMGxZCz7Me+T6W50y0qKxiuYFrMNKV H4=; b=UvnS+SJtRxAN6QruQDnD0xGDzRdF8wTfr5otGJmYmfK+qwMwBXd370xog Y0R7NpR6nf2ehsHNtJLdcUV+9IEn/ToDuvDBXCnEN04kSuFYp9dx8MngbuaLIusd IgdxggE33qlbO/PkbvcLcN/dR2yBTOF5mx/6dSToF4XN55ZxOgsUjexOg1QZzpKJ 2fL9o+FT3VsrsKNk6D4YMqIVhEiTQxSAVPBuODd3gRNzdzyuxgU+HWEDpHrvLwbV 1nbopufnIl+5EOMxyA90BEbADEjAum0cOi7T2FiT7yDIAi9S9eXRJE/dSavVAMHa 5MnxZGumVS4GnAg8OgtPfw2IEo5Qg==
X-ME-Sender: <xms:LXwqYm8LlZH8dRl3t1VErsf00yOEZryF17VUSxizkPBB2xjeM1Rw-w> <xme:LXwqYmu0BfmylISRcZBd5UE0D3knObnaocfLxHvbMS4sb6zcciI4iHZSENGjnL5Fv k2CyKu7dV8xB-Td1w>
X-ME-Received: <xmr:LXwqYsBLijsuf3n1x3PoszSgG5PxHoClf29m8piRfnbEIF8KvUAftsTbAU9KK3TMiHFS-Lbf1sJeE8Rn8pGxLezK1fzkS2X49OKXYgo>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvtddgudeifecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeevfedvgeeuueehueetfefhhfduhfevheejudfhleeiudff ueekleetjefgteelgeenucffohhmrghinhepghhithhhuhgsrdgtohhmnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepshhtphgvthgvrhesshht phgvthgvrhdrihhm
X-ME-Proxy: <xmx:LXwqYucs1DMMp8Mx9DFJQ9jVJS6WQSGxFIHQ263eHAiks8crZgcNMA> <xmx:LXwqYrNs5qS2fh4sHdl3cz7DNECZILGhIdMLmFVNkRu6sMj-mMa70g> <xmx:LXwqYom2rysylj7x7zowXGCwEmQd2k9SdQ-2QY5LiiwL74awTFwE1g> <xmx:LXwqYgrvBi3e6GRnK9MAb_38U6AXb4e78X4U8tUXUruYth_gQfcAvQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 10 Mar 2022 17:31:08 -0500 (EST)
Message-ID: <f8ffca71-03a0-7ec0-5843-e6176e2bc16e@stpeter.im>
Date: Thu, 10 Mar 2022 15:31:07 -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: Benjamin Kaduk <kaduk@mit.edu>
Cc: Eliot Lear <lear@lear.ch>, "rfced-future@iab.org" <rfced-future@iab.org>, IAB <iab@iab.org>, The IESG <iesg@ietf.org>
References: <20220310060016.GV22457@mit.edu> <1e5d1934-806d-2689-4483-c3296e334e69@lear.ch> <20220310071251.GZ22457@mit.edu> <18a9ed03-1be6-5993-750a-5dccf7f21bdb@lear.ch> <0eaf0a63-91c2-9480-b361-e5d1554aaf3e@stpeter.im> <20220310214041.GD22457@mit.edu> <97b387f0-20a1-d658-1286-d61d6bac34ce@stpeter.im> <20220310222501.GG22457@mit.edu>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <20220310222501.GG22457@mit.edu>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/CpqNIEvRXTFRJ7YMSwL9LBqtIqg>
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 22:31:20 -0000

On 3/10/22 3:25 PM, Benjamin Kaduk wrote:
> On Thu, Mar 10, 2022 at 03:09:37PM -0700, Peter Saint-Andre wrote:
>> On 3/10/22 2:40 PM, Benjamin Kaduk wrote:
>>
>>> On Thu, Mar 10, 2022 at 02:35:58PM -0700, Peter Saint-Andre wrote:
>>>>
>>>> On 3/10/22 1:28 AM, Eliot Lear wrote:
>>>>>
>>>>> On 10.03.22 08:12, Benjamin Kaduk wrote
>>>>>> It's getting late here, so maybe I'm just missing things, but while this
>>>>>> does seem to be an improvement, it still seems to have somewhat of a
>>>>>> mismatch with §4.3's depiction.  If I understand correctly, the RPC only
>>>>>> cares about value assignments insamuch as the values being assigned get
>>>>>> recorded in the RFCs being produced, and your new proposal doesn't
>>>>>> mention
>>>>>> documents/RFCs (other than this one) at all.
>>>>>
>>>>> "This document requires that the RPC document registry value
>>>>> assignments made by IANA."
>>>>
>>>> That's pretty much what it said before, no? ;-)
>>>>
>>>> I suggest this in the "RPC Responsibilities" section:
>>>>
>>>> 14. Ensuring that RFCs accurately document registry value assignments
>>>>        made by IANA.
>>>>
>>>> For the avoidance of doubt, we could also say the same thing under the
>>>> IANA considerations.
>>>
>>> That does remove the bits I was confused about, but to me it also seems to
>>> change the semantics somewhat.  Namely, now the RPC is just consuming
>>> things produced by IANA, which could be seen as removing the possibility to
>>> coordinate on which allocations are actually to be made, from what
>>> range(s), etc., that the previous text seems to have implied.  I think I
>>> have seen the RPC notice things in editing that would affect what IANA
>>> does, and thus am not confident that describing this as a unidirectional
>>> flow would be entirely accurate.  (Whether such coordination could occur
>>> between RPC and IANA in an informal manner so as to get the right thing to
>>> happen anyway, is another question.)
>>
>> Ah, I see, you were originally concerned about the text in Section 11,
>> not the text in Section 4.3.
> 
> Ah, yes.  I guess that got lost as the thread evolved.
> 
>> I wonder if something like this would be more accurate in §11:
>>
>> "The RPC is responsible for coordinating with IANA to ensure that RFCs
>> accurately document registration processes and assigned values for IANA
>> registries."
> 
> That looks good to me on first read, thanks.

Great. This and other changes-in-progress can be tracked in the 
following pull request:

https://github.com/intarchboard/program-rfced-future/pull/158

Peter