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

Russ Housley <housley@vigilsec.com> Wed, 02 February 2022 19:55 UTC

Return-Path: <housley@vigilsec.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 A6A053A1DDF for <rfced-future@ietfa.amsl.com>; Wed, 2 Feb 2022 11:55:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_NONE=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 Ctydvb5dXCQc for <rfced-future@ietfa.amsl.com>; Wed, 2 Feb 2022 11:55:06 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.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 238563A1DDB for <rfced-future@iab.org>; Wed, 2 Feb 2022 11:55:06 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 2010B13AFD7; Wed, 2 Feb 2022 14:55:05 -0500 (EST)
Received: from [192.168.1.161] (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 1333813AFD6; Wed, 2 Feb 2022 14:55:05 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <26953c41-db43-0c3f-4a5d-d95a99fe4844@nthpermutation.com>
Date: Wed, 02 Feb 2022 14:55:03 -0500
Cc: rfced-future@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AAC0A2A3-FE38-4D2F-9671-E60AD7BFF0AC@vigilsec.com>
References: <410918e0-1898-309f-3289-a02d30a112b3@lear.ch> <26953c41-db43-0c3f-4a5d-d95a99fe4844@nthpermutation.com>
To: Mike StJohns <msj@nthpermutation.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/hmlUPX5JuvP41Uz8e4D5-vxVqCM>
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 19:55:11 -0000


> On Feb 2, 2022, at 1:01 PM, Michael StJohns <msj@nthpermutation.com> 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.

When this group got started, I thought we said that the IAB would be responsible for the coordination with the IESG and LLC prior to document approval.  I did not go back to the archives to check my memory, but that is my recollection.

Russ