[ieee-ietf-coord] RFC Editor Model - Virtual Interim Meeting Announcement and Invitation

Russ Housley <housley@vigilsec.com> Wed, 04 September 2019 19:34 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1DE120D11 for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 4 Sep 2019 12:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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 3M_n1ouOIq4y for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 4 Sep 2019 12:34:18 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C73F120CF3 for <ieee-ietf-coord@ietf.org>; Wed, 4 Sep 2019 12:34:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id D165C300AAB for <ieee-ietf-coord@ietf.org>; Wed, 4 Sep 2019 15:34:16 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id S_dLinIylTsq for <ieee-ietf-coord@ietf.org>; Wed, 4 Sep 2019 15:34:14 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 748173005DF for <ieee-ietf-coord@ietf.org>; Wed, 4 Sep 2019 15:34:14 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_163C944A-7349-4E20-9CC0-227491693A25"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <8CDDD66B-3B1B-4883-8CEF-4CC1953B783D@vigilsec.com>
References: <564B3001-8BFE-4BF0-890C-4B98516C0AD9@rfc-editor.org>
To: "<ieee-ietf-coord@ietf.org>" <ieee-ietf-coord@ietf.org>
Date: Wed, 4 Sep 2019 15:34:15 -0400
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/9-0GoMjIh9vGWhSsUY74MfexVFA>
Subject: [ieee-ietf-coord] RFC Editor Model - Virtual Interim Meeting Announcement and Invitation
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Sep 2019 19:34:21 -0000

This topic may be of interest to some people on this list.

Russ


> From: Heather Flanagan <rse@rfc-editor.org <mailto:rse@rfc-editor.org>>
> Subject: [rfc-i] RFC Editor Model - Virtual Interim Meeting Announcement and Invitation
> Date: September 4, 2019 at 10:56:35 AM PDT
> To: ietf-announce@ietf.org <mailto:ietf-announce@ietf.org>
> Cc: wgchairs@ietf.org <mailto:wgchairs@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org <mailto:rfc-interest@rfc-editor.org>>
> 
> 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, 1 October 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?
> 
> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org <mailto:rfc-interest@rfc-editor.org>
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest

_______________________________________________
Ietf-liaisons mailing list
Ietf-liaisons@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-liaisons