Status of the RFC Series Editor Transition project.

IAB Chair <iab-chair@iab.org> Mon, 14 February 2011 07:06 UTC

Return-Path: <iab-chair@iab.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C30E13A6A5A for <ietf-announce@core3.amsl.com>; Sun, 13 Feb 2011 23:06:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level:
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=0.930, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DN-6NJHO1zyK for <ietf-announce@core3.amsl.com>; Sun, 13 Feb 2011 23:06:24 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 8109C3A6AAE for <ietf-announce@ietf.org>; Sun, 13 Feb 2011 23:06:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 078E3E089C for <ietf-announce@ietf.org>; Sun, 13 Feb 2011 23:06:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nsAqB3drKJn8 for <ietf-announce@ietf.org>; Sun, 13 Feb 2011 23:06:45 -0800 (PST)
Received: from aagje.fritz.box (xs4all.dacht.net [82.95.132.144]) by c1a.amsl.com (Postfix) with ESMTPSA id 23F8CE0782 for <ietf-announce@ietf.org>; Sun, 13 Feb 2011 23:06:44 -0800 (PST)
From: IAB Chair <iab-chair@iab.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Status of the RFC Series Editor Transition project.
Date: Mon, 14 Feb 2011 08:06:28 +0100
Message-Id: <C7988572-52CF-4DD4-945F-2F5A3E5C881D@iab.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: RFC Interest <rfc-interest@rfc-editor.org>
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 14 Feb 2011 07:06:27 -0000

[apologies for the cross-post]

Colleagues,

This is to update you on the next steps of the RSE transition project.

As planned, the TRSE contract and Glenn Kowack's role as transitional RFC Series Editor wind up at the end of February.

It will be impossible to have hired a new RSE by then. So, we have worked out a plan to make sure most of the
pieces are in place so that the hiring process can start, preferably around the IETF in Prague.

Glenn has worked with the IAB to prioritize a number of tasks for the remainder of his engagement. In addition to continuing managerial oversight, he takes responsibility to:

1) Produce the Job Description and SOW

2) Document RSE experience gained during the project. The goal is
 to provide documentation for the next RSE to bridge the approaching gap.

3) Assist the process of developing the RFC of RFC Editor Model
 (Version 2). The focus will be on facilitating the ongoing process.

In parallel we have asked Joel Halpern to edit RFC5620bis. Both the job description and RFC5620bis are based on the consensus that has developed here and is documented in http://tools.ietf.org/html/draft-kolkman-rse-2011

Between the end of February and the time an RSE is appointed there will be a need for somebody to act as the 'point person' for escalation of issues that need cross-stream coordination or need escalation 'above' the production house. That
'point person' has a coordinating and mediating role and is not expected to be managing the day to day process
(that train runs). I have agreed with the IAB that I should temporarily take that role as a volunteer[*].

Glenn promised to remain available in a volunteering role (time and other commitments permitting). He will also be at the IETF80 in Prague so ongoing matters can be discussed face to face and past experiences can be shared.

Since the development of consensus around the RFC Editor is broader than the IETF the IAB has been using the rfc-interest@rfc-editor.org for the development of consensus. RFC5620bis, the SOW, the Job description and all other relevant documents will be reviewed there. 


--Olaf Kolkman


[*] I plan to not volunteer for the IAB chair position, which should give me the necessary cycles.


________
The Internet Architecture Board
www.iab.org
iab-chair@iab.org