6
Transitional RFC Series Editor Methods and Goals Glenn Kowack Transitional RFC Series Editor Wednesday, 24 March 2010 IETF 77, Anaheim, CA

Transitional RFC Series Editor

Embed Size (px)

DESCRIPTION

Transitional RFC Series Editor. Methods and Goals Glenn Kowack Transitional RFC Series Editor Wednesday, 24 March 2010 IETF 77, Anaheim, CA. Background. 2009 - effort made to hire permanent RFC Series Editor Alternate approach reached by IAB - PowerPoint PPT Presentation

Citation preview

Page 1: Transitional RFC Series Editor

Transitional RFC Series Editor

Methods and Goals

Glenn Kowack

Transitional RFC Series Editor

Wednesday, 24 March 2010

IETF 77, Anaheim, CA

Page 2: Transitional RFC Series Editor

Background

• 2009 - effort made to hire permanent RFC Series Editor

• Alternate approach reached by IAB– Transitional RFC Series Editor Job

Description (4 November 2009)– TRSE Started 1 March 2010– Bob Braden still iRSE until 19 April 2010

Page 3: Transitional RFC Series Editor

Method• Maintain Continuity of Editorial Operations• Learn

– Do the RSE Job for an extended period• Critical unknown #1: what is the content of the job?

– Obtain community input• Critical unknown #2: what is the structure of community opinion; is a

consensus readily available?

• Deliverables– Update RSE job description– Update RFC 5620 - “RFC Series & RFC Editor”– Make recommendations: recruitment, selection, & hiring

processes

Page 4: Transitional RFC Series Editor

More on Method

• Engage with– Bob Braden, RFC Editorial staff, RSAG

(RFC Series Advisory Group)

• Be sure to– have the big picture– Be certain we’ve extracted all the important

parts and subtleties

Page 5: Transitional RFC Series Editor

Structure

Structured to provide

• Sufficient calendar time

• Sufficient experience

to not limit the completeness of the proposal(s) nor to force a particular solution

Page 6: Transitional RFC Series Editor

Schedule

• Target: call for RSE nominees during IETF 79 Beijing

• Allows for exposure to most RSE activities, including 2 IETF meetings

• Success possible only if community consensus can be reached

• Challenge to community: provide input to reach consensus by Sept-Oct 2010