Upcoming Community Consultations on Next Generation RFC Model

Eliot Lear <lear@lear.ch> Wed, 27 October 2021 12:13 UTC

Return-Path: <lear@lear.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4602A3A110F; Wed, 27 Oct 2021 05:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.889
X-Spam-Status: No, score=-0.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7KWMANoPQwXc; Wed, 27 Oct 2021 05:12:56 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com []) (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 EE0833A110A; Wed, 27 Oct 2021 05:12:51 -0700 (PDT)
Received: from [IPV6:2a02:aa15:4101:2a80:9916:9b8c:d136:30ae] ([IPv6:2a02:aa15:4101:2a80:9916:9b8c:d136:30ae]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 19RCCmDN1187221 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 27 Oct 2021 14:12:48 +0200
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1635336769; bh=KrQkn2JLd+HtJY/NWV7OEE4Wd9Wm2XCAiyYldowfatU=; h=Date:To:Cc:Reply-To:From:Subject:From; b=B/og3ZYCky2WK0rZ/6gfd1ckFqbeGG/2CLgA8+wxMCNPgv7cReEsBAn98AC2/al6z 6bxaOQMjrhXA2CzvI461xXw0a1vrDURlRtg5BwenocBKmpCwXhqSqSN2KL0ZKK3wI6 PPFlrDKb5gU5lHqGFDbn3PLeh/g+MZMBP/J4+EVI=
Message-ID: <0e0db0df-6e23-ed9a-2c6e-1d7dc57fac1b@lear.ch>
Date: Wed, 27 Oct 2021 14:12:47 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.1.2
Content-Language: en-US
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, gendispatch@ietf.org, The IETF List <ietf@ietf.org>, rfc-interest@ietf.org
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Brian Rosen <br@brianrosen.net>
Reply-To: "rfced-future@iab.org" <rfced-future@iab.org>
From: Eliot Lear <lear@lear.ch>
Subject: Upcoming Community Consultations on Next Generation RFC Model
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------jlh709raj4unRJuVAzy9bNuY"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QmjdV8FiE34L_MjsLyjPtf57FX8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2021 12:13:01 -0000

Dear colleagues,

In March of 2020 the IAB kicked off the RFC Series Editorial Future 
Development Program, a program opened to the entire community, with an 
eye toward reviewing the RFC Editor model found in 
draft-iab-rfcefdp-rfced-model-05[1]. We are now coming to the conclusion 
of our work, and the IAB will soon begin its formal consideration, which 
is governed by RFC 4845[2]. Part of that process includes solicitation 
of community input.

The program has developed an evolution of the RFC Editor Model and a 
small change to the charter of the IAB. You can find this evolution in 
draft-iab-rfcefdp-rfced-model-05 as well as two companion drafts[3,4,5]. 
This draft brings together many different points of view, as you can see 
from the mailing list archive[6].

Here are some of the proposed changes that you may wish to know:


    The community oversees the evolution of the series by means of an
    open working group. Proposed changes that reach rough consensus will
    be reviewed by an RFC Series Approval Board (RSAB) that consists of
    the RSCE and people representing the various streams.


    The RFC Editor role is changing to that of a consulting editor (RFC
    Series Consulting Editor or RSCE). In this model, an expert will
    provide guidance to the community, the streams, and to the RPC to
    evolve the series.


    The IAB will no longer manage or oversee the RFC series. The
    community and the streams will do that. The IAB will continue to be
    in the appeal path if there are disputes.

There are a lot of things that won't change. The RPC would continue to 
handle day-to-day functions of the RFC Editor function, and authors 
should not see any immediate change in terms of how RFCs are published. 
They continue to be managed through the LLC. We will continue to benefit 
from the expertise of a professional expert, now the RSCE.

Of course, there's a lot more detail that is specified in the drafts.

This is what will soon be put forth for your comments. In the meantime, 
even though the formal comment period is not yet open, we invite you to 
review the model now and bring whatever questions you might have to the 
program when we meet on Wednesday, November 10th, at 14.30 GMT at the 
IETF meeting. Of course you can also join the mailing list[7] and 
contribute your questions and comments there.

On behalf of the program,

Brian and Eliot

[2] https://www.rfc-editor.org/rfc/rfc4845.html
[3] https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model-05
[5] https://datatracker.ietf.org/doc/html/draft-rosen-rfcefdp-update-2026-01
[6] https://mailarchive.ietf.org/arch/browse/rfced-future/
[7] https://www.iab.org/mailman/listinfo/rfced-future