html5-img
1 / 6

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. Background. 2009 - effort made to hire permanent RFC Series Editor Alternate approach reached by IAB

phillip-turner
Download Presentation

Transitional RFC Series Editor

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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

  3. 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

  4. 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

  5. Structure Structured to provide • Sufficient calendar time • Sufficient experience to not limit the completeness of the proposal(s) nor to force a particular solution

  6. 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

More Related