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

John C Klensin <john-ietf@jck.com> Sat, 12 March 2022 19:10 UTC

Return-Path: <john-ietf@jck.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 5C55B3A0A1A; Sat, 12 Mar 2022 11:10:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 GIgnaXwX_Koc; Sat, 12 Mar 2022 11:10:21 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EDCC3A0A16; Sat, 12 Mar 2022 11:10:20 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1nT783-000L5c-5L; Sat, 12 Mar 2022 14:10:15 -0500
Date: Sat, 12 Mar 2022 14:10:09 -0500
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Benjamin Kaduk <kaduk@mit.edu>
cc: rfced-future@iab.org, IAB <iab@iab.org>, The IESG <iesg@ietf.org>, Eliot Lear <lear@lear.ch>
Message-ID: <60B4F03CABAACA753C9DA3B0@PSB>
In-Reply-To: <b18b5bae-0539-5512-33b5-d8976df64eb2@stpeter.im>
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> <b18b5bae-0539-5512-33b5-d8976df64eb2@stpeter.im>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/pzQrhvFwCJOeazZ2oF0IUZe_5R4>
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:10:27 -0000


--On Saturday, March 12, 2022 12:07 -0700 Peter Saint-Andre
<stpeter@stpeter.im> wrote:

>...
>> 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.

Yes.  Entirely correct.  Sorry I did not see that suggestion
before writing my note.

thanks,
   john