RFC Editor Model - Virtual Interim Meeting Announcement and Invitation

Heather Flanagan <rse@rfc-editor.org> Wed, 04 September 2019 17:56 UTC

Return-Path: <rse@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A694120B35; Wed, 4 Sep 2019 10:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 Xgu7z3WSUk5h; Wed, 4 Sep 2019 10:56:37 -0700 (PDT)
Received: from mail.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 0B7CA120B36; Wed, 4 Sep 2019 10:56:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 4DF92202196; Wed, 4 Sep 2019 10:56:06 -0700 (PDT)
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 liwu0KtZkEBS; Wed, 4 Sep 2019 10:56:06 -0700 (PDT)
Received: from [10.198.42.38] (c-71-231-216-10.hsd1.wa.comcast.net [71.231.216.10]) by c8a.amsl.com (Postfix) with ESMTPSA id DD3A4202194; Wed, 4 Sep 2019 10:56:05 -0700 (PDT)
From: Heather Flanagan <rse@rfc-editor.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EA680FA8-9F82-4F12-AAB1-1CEF33A7FA69"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: RFC Editor Model - Virtual Interim Meeting Announcement and Invitation
Message-Id: <564B3001-8BFE-4BF0-890C-4B98516C0AD9@rfc-editor.org>
Date: Wed, 04 Sep 2019 10:56:35 -0700
Cc: RFC Interest <rfc-interest@rfc-editor.org>, wgchairs@ietf.org
To: ietf-announce@ietf.org
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/9ag2ss7RvvAd6wTQhdOS444D-vY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Sep 2019 17:56:40 -0000

Hello,

The RFC Series has come to a crossroads where questions must be answered regarding how the Series should be managed, the role of the RFC Series Editor, and the oversight of the RFC Editor function. The RFC Editor publishes RFCs for the IETF, the IRTF, the IAB, and the Independent Submissions stream. Those RFCs are referred to by other Standards Development Organizations (SDOs), by organizations and governments in their procurement processes, by academics, and more. Decisions on the future of the RFC Editor and the RFC Series needs to include input from both the producers and the consumers of RFCs.

I am reaching out to different groups and organizations so that they may be a part of figuring out how to answer those questions. It is worth noting that I am not trying to get to a final answer on what the future of the RFC Editor and the RFC Series should be; I’m trying to reach consensus on who should be making those decisions.  So, with that in mind, this is an invitation to attend one of three virtual interim meetings, and/or the face-to-face meeting (with remote participation supported) at IETF 106 in Singapore. 

This is not an IETF or IRTF activity, but we are holding this discussion under the IETF and IRTF policies described in the Note Well (https://www.ietf.org/about/note-well/ <https://www.ietf.org/about/note-well/>).  This is to ensure consistent and well-understood policies, particularly relating to appropriate behavior, privacy, etc.  To the extent that topics of discussion might comprise input to IETF or IRTF and involve regular participants in each, this ensures that these discussions are covered under the rules of those bodies.

The virtual meetings will be held in various time-zone sensitive windows to enable as much participation as possible:

Friday, 13 September 2019 at 16:00 UTC
Monday, 30 September 2019 at 13:00 UTC
Friday, 18 October 2019 at 02:00 UTC

The WebEx information, a copy of the agenda [1], and (eventually) all future proceedings are on the RSE wiki: https://www.rfc-editor.org/rse/wiki/doku.php?id=interim <https://www.rfc-editor.org/rse/wiki/doku.php?id=interim>

Required reading list: 
https://www.rfc-editor.org/info/rfc4844 <https://www.rfc-editor.org/info/rfc4844>
https://www.rfc-editor.org/info/rfc6635 <https://www.rfc-editor.org/info/rfc6635>
https://datatracker.ietf.org/doc/draft-carpenter-request-for-comments/ <https://datatracker.ietf.org/doc/draft-carpenter-request-for-comments/>
https://datatracker.ietf.org/doc/draft-iab-fiftyyears/ <https://datatracker.ietf.org/doc/draft-iab-fiftyyears/>
https://www.ietf.org/about/note-well/ <https://www.ietf.org/about/note-well/>

This announcement and invitation is being extended to:
* IETF, IRTF, IAB, and Independent Submission authors and participants via various mailing lists, including the rfc-interest, ietf-announce, and wgchairs mailing lists
* Regional NOGs
* IAB liaison contacts (see https://www.ietf.org/about/liaisons/ <https://www.ietf.org/about/liaisons/>)
* ISOC chapter heads
* REFEDS

Email-based discussion on this topic should happen on the rfc-interest mailing list (https://www.rfc-editor.org/mailman/listinfo/rfc-interest <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>).

Additional participants are welcome; feel free to forward to anyone you think would be interested and willing to contribute to the discussion. 

Thank you for your time,
Heather Flanagan
RFC Series Editor

—

[1] Agenda

Administrivia
Meeting will be recorded
Note Well (https://www.ietf.org/about/note-well/ <https://www.ietf.org/about/note-well/>)

Acknowledging possible models
The RFC Editor as a wholly independent entity
The RFC Editor as an IAB/RSOC managed function
The RFC Editor as an IETF LLC managed function

Identifying how to handle next steps:
Who manages the community discussion?
Who needs to be invited to the table?
Who calls consensus?