Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model-12
Benjamin Kaduk <kaduk@mit.edu> Thu, 10 March 2022 22:25 UTC
Return-Path: <kaduk@mit.edu>
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 053E13A0D0B; Thu, 10 Mar 2022 14:25:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.722
X-Spam-Level:
X-Spam-Status: No, score=-1.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.186, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 JEgvczMv4huW; Thu, 10 Mar 2022 14:25:09 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 60AB93A088C; Thu, 10 Mar 2022 14:25:08 -0800 (PST)
Received: from mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 22AMP17Q011464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 10 Mar 2022 17:25:06 -0500
Date: Thu, 10 Mar 2022 14:25:01 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Peter Saint-Andre <stpeter@stpeter.im>
Cc: Eliot Lear <lear@lear.ch>, "rfced-future@iab.org" <rfced-future@iab.org>, IAB <iab@iab.org>, The IESG <iesg@ietf.org>
Message-ID: <20220310222501.GG22457@mit.edu>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <97b387f0-20a1-d658-1286-d61d6bac34ce@stpeter.im>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ceXWydx4-CylNnpbenIxueLywFo>
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:25:11 -0000
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. -Ben
- [Rfced-future] Comments on draft-iab-rfcefdp-rfce… Benjamin Kaduk
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Eliot Lear
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Benjamin Kaduk
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Eliot Lear
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Peter Saint-Andre
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Benjamin Kaduk
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Peter Saint-Andre
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Benjamin Kaduk
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Peter Saint-Andre
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Peter Saint-Andre
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… John C Klensin
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Peter Saint-Andre
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… John C Klensin
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Benjamin Kaduk
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Peter Saint-Andre