Re: [Rfced-future] Document for IAB consideration: draft-iab-rfcefdp-rfc-model-11

Cindy Morgan <cmorgan@amsl.com> Wed, 02 February 2022 20:16 UTC

Return-Path: <cmorgan@amsl.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 A73843A1E77 for <rfced-future@ietfa.amsl.com>; Wed, 2 Feb 2022 12:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 uMABZ6gh5UbB for <rfced-future@ietfa.amsl.com>; Wed, 2 Feb 2022 12:16:48 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30E873A1E7C for <rfced-future@iab.org>; Wed, 2 Feb 2022 12:16:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 0C47D425C152 for <rfced-future@iab.org>; Wed, 2 Feb 2022 12:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQiVmwgYAx2e for <rfced-future@iab.org>; Wed, 2 Feb 2022 12:16:48 -0800 (PST)
Received: from [10.0.1.8] (c-24-6-24-199.hsd1.ca.comcast.net [24.6.24.199]) by c8a.amsl.com (Postfix) with ESMTPSA id E9D31425A346 for <rfced-future@iab.org>; Wed, 2 Feb 2022 12:16:47 -0800 (PST)
From: Cindy Morgan <cmorgan@amsl.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Wed, 02 Feb 2022 12:16:47 -0800
References: <mailman.5139.1643831712.6626.rfced-future@iab.org>
To: rfced-future@iab.org
In-Reply-To: <mailman.5139.1643831712.6626.rfced-future@iab.org>
Message-Id: <D996B49E-3EA0-442F-8BB3-BDA762CF97C7@amsl.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/X0z4xP5gAw0VUFDqhwXRTB8EP-Y>
Subject: Re: [Rfced-future] Document for IAB consideration: draft-iab-rfcefdp-rfc-model-11
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: Wed, 02 Feb 2022 20:16:53 -0000

At their meeting earlier today, the IAB agreed to send a Call for Comments (IAB version of IETF Last Call) on draft-iab-rfcefdp-rfc-model. This will have a wider-than-normal distribution that includes IETF-Announce, IRTF-Announce and RFC-interest.

The IAB also noted that this Call for Comments should go out at the same time as the IETF Last Calls on draft-carpenter-rfced-iab-charter, draft-rosen-rfcefdp-update-2026, and draft-rsalz-2028bis. Lars (as AD sponsor for those docs) and I (as the Secretariat person who will be pushing the appropriate buttons in the Datatracker for all 4 of these docs) are coordinating.

Thanks,
Cindy

> From: Eliot Lear <lear@lear.ch>
> Subject: Re: [Rfced-future] Document for IAB consideration: draft-iab-rfcefdp-rfc-model-11
> Date: February 2, 2022 at 11:34:08 AM PST
> To: Michael StJohns <msj@nthpermutation.com>, rfced-future@iab.org
> 
> 
> Hi Mike,
> 
> I presented the process that I expect to have happen back in the Fall (you may recall a detailed timeline slide - it's in the materials).  This is an IAB stream document.  That means that RFC 4845 governs, and as I mentioned in the Fall, it's up to the board, not the program, to decide in the end how to weigh community input.  It has been my consistent advice that the board broadly consult, including the IETF, IRTF, and others, because, in my view, this program believes that's the right thing to do (I don't disagree).  The IESG will have to approve changes to the IAB charter, 2028, and a slight tweak to 2026.
> 
> Eliot
> 
> 
> 
> On 02.02.22 19:01, Michael StJohns wrote:
>> On 2/2/2022 3:51 AM, Eliot Lear wrote:
>>> Dear Board Members,
>>> 
>>> The chairs of the RFC Editor Future Development Program believe that draft-iab-rfcefdp-rfc-model-11[1] is ready for you to progress.  Given the nature of this work, we suggest that during the community comment period you seek broad review.  We await any comments or questions you or the community might have for us.
>>> 
>>> As a reminder, the final version of this draft should be published concurrently with draft-carpenter-rfced-iab-charter, draft-rosen-rfcefdp-update-2026-01, and draft-rsalz-2028bis-03.txt.  These updates are scoped to reflect the change of structure.
>>> 
>>> Brian & Eliot
>>> 
>>> [1] https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model-11
>>> 
>>> 
>>> 
>> Deleting the IAB for a minute.  Shouldn't this note also be directed to the IESG and the LLC Board?  I believe we were in agreement that it will require approval of all three groups to go forward with the approval of this document.
>> 
>> Mike