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

Peter Saint-Andre <stpeter@stpeter.im> Sat, 12 March 2022 19:07 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 495863A09CF; Sat, 12 Mar 2022 11:07:35 -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=oQxfNWVO; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Jx2ZtF49
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 z42nUlfDLSQU; Sat, 12 Mar 2022 11:07:29 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B0AE3A09B5; Sat, 12 Mar 2022 11:07:29 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 8D6055C0151; Sat, 12 Mar 2022 14:07:28 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sat, 12 Mar 2022 14:07:28 -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=M/1pefQ3G6TY6J ZOFUhxDV+UF4//7SIVLYP80VGnDu8=; b=oQxfNWVOit/S8ZngCJRG94GvR9e22i aYczohrJJLCQixhtwzNsL1jz3+liE/V5iH+3/stPe8wJf8wHjfF85BnT29/xqqcA CwrDZhZ9tR9kGLB6rbZA2Fej2X4GNErA0ngVJ8AXtvgdu1BHO9S2MCKXcfH7bXpb aLVdKNSNDqt+B+yHOymPSZt9QMHZ+AnHaUCMFg3Ah40H6P8UYJMjrBWOvRnqDkzQ UzuOKBwk8s6yb0tRB8pvMJWK5G5R3tqIK/7MmVaynUdxsbHjv56h+fW9AyZOQB+g 7uBww+3T9PGiHpR3f/Hj/UTSGB9u00EjoJYXs6NoOa9MsXyTHFvskTDA==
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=M/1pefQ3G6TY6JZOFUhxDV+UF4//7SIVLYP80VGnD u8=; b=Jx2ZtF49LEBX3V03MU5YtwKLxxzylm8QtB8go61G1ygkzn4xqtpUNgt+7 8Ti0vvLXtd/tpp33ImglyWLhAVAsHv2NXoaAMj2CJZUIVXYhnmEMEVGXF6+PIzVy kIhsZgvYjLwDNt22wOiWTtqLvXDxKu9O3bn8mWTi+LueAlyJ0O8edVZM5tIucKZc MA6VUJK9bG5znEC9qhaAiysO+T249h5sWtXSYZLlgIXHbSi/iApuwUqf9HQQD4z/ ylo9T5s8bbnq/Ee2FfgR0773tki2E/njsWgGtv3OZigS1Y1o3YAORMq3OK8ojxNR yWcnIwiSz5C6GRtOBUszIF19xE20A==
X-ME-Sender: <xms:b-8sYjARdCOtE9Glgx2AQzuJA-mcjFIvbN7PvgcL-33C9TKbgLfPKw> <xme:b-8sYpiNEiCH3FOIWw2QGL4qZ3NeWvTbo13nolGuLknHVMMntletx328wj2F9ee1W AMqXcEu1-guLWCYow>
X-ME-Received: <xmr:b-8sYukxnaJgZZysmYKM7LhlZfoh3-R6VUCbCWotiH1_O_JeCQVZoM0SR9zFxIIOtEpaLqp8b7UejMTzcCwTX6gxREiQfAGIjGNcewE>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvgedguddvtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeehtefhvdejvdfhgeetgefhfeeuudefkeetvdfhkeelleeu heefleekkeekieffudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:b-8sYlwCdc0DvzUZlX7jjxdBvXuP6CYdTcc5nwireUYLAyJ42vfbWQ> <xmx:b-8sYoRtBMx7PaSCa7GlvXx1OuE5wDEYJwxgfx4MC2sOIlX3AB_B2A> <xmx:b-8sYobV3caXMxOEpLB1IZwGDiR6-mhpGfm73-Acg_ehlUHx5Lz-2w> <xmx:cO8sYtKkBwO-lqhUZhpZkzqB0KCgNmiqIWzO49rdvkoWC2nT0P3LfA>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 12 Mar 2022 14:07:27 -0500 (EST)
Message-ID: <b18b5bae-0539-5512-33b5-d8976df64eb2@stpeter.im>
Date: Sat, 12 Mar 2022 12:07:22 -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: John C Klensin <john-ietf@jck.com>, Benjamin Kaduk <kaduk@mit.edu>
Cc: rfced-future@iab.org, IAB <iab@iab.org>, The IESG <iesg@ietf.org>, Eliot Lear <lear@lear.ch>
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> <D205B42CD433DB5510492CA8@PSB>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <D205B42CD433DB5510492CA8@PSB>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/awpeCZcAcw3_uXS89EPGrwpVIx8>
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: Sat, 12 Mar 2022 19:07:36 -0000

On 3/11/22 7:19 PM, John C Klensin wrote:
> 
> 
> --On Thursday, March 10, 2022 13:40 -0800 Benjamin Kaduk
> <kaduk@mit.edu> wrote:
> 
>>>> "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.)
> 
> In practice, it has always been a two-way flow, even when the
> RFC Editor and IANA held discussions by looking into a mirror.
> And even with that level of coordination, it has often been a
> bit of a dance because of the long-standing principle that RFCs
> do not direct IANA to assign, or even request, particular code
> points.  So please try to write the text along the lines Ben
> suggests, e.g., as something more like "Coordinate with IANA as
> necessary to ensure that any registry value assignments that
> actually appear RFCs are consistent with the registries."

What I suggested most recently was:

14. Coordinating with IANA to ensure that RFCs accurately document
     registration processes and assigned values for IANA registries.

Note that this mentions registration processes in addition to assigned 
values, because many RFCs establish registries and the processes for 
registering values in those registries need to be correct, too.

Peter