1 / 7

RSE & RSOC Report

RSE & RSOC Report. IETF 88 Vancouver, BC, Canada. RFC Series Oversight Committee (RSOC). IAB Members Joel Halpern (Lead) Bernard Aboba Non-IAB Members Nevil Brownlee Tony Hansen Joe Hildebrand Bob Hinden Alexey Melnikov (Chair) Heather Flanagan (RSE) Ray Pelletier (IAOC Liaison).

russell-ryan
Download Presentation

RSE & RSOC Report

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. RSE & RSOC Report IETF 88 Vancouver, BC, Canada

  2. RFC Series Oversight Committee (RSOC) • IAB Members • Joel Halpern (Lead) • Bernard Aboba • Non-IAB Members • Nevil Brownlee • Tony Hansen • Joe Hildebrand • Bob Hinden • Alexey Melnikov (Chair) • Heather Flanagan (RSE) • Ray Pelletier (IAOC Liaison)

  3. RSOC Highlights • Completed review and recommendation to the IAOC regarding: • RFC Production Center and RFC Publisher Statements of Work and contracts • RFC Series Editor contract

  4. RSE Avenues of Communication • The RSE wiki • http://www.rfc-editor.org/rse/wiki • rfc-interest mailing list • http://www.rfc-editor.org/mailman/listinfo/rfc-interest

  5. RFC Style Guide • Progress since IETF 87 includes • Continue to establish guidelines for citations (e.g., IEEE vs Institute of Electrical and Electronics Engineers) • Focus on areas that will need to be modified with format changes (e.g., changes to author names and indexing) • Clearly defining "most stable reference” • Revise requirements and recommendations in Authors’ Addresses section • Remove guidance on Headers and Boilerplates that is already covered in RFC 5741

  6. RFC Format • Process since Berlin • Design Team active and engaged • IAB's i18n program providing input on non-ASCII requirements for series • Discussion with IESG about normative vs informative text, images, and accessibility BoF = Thursday, 7 November @ 17:30-18:30in Regency B https://www.rfc-editor.org/rse/wiki/doku.php?id=design:start

  7. Homework Please review the content on the wiki before the BoF https://www.rfc-editor.org/rse/wiki/doku.php?id=design:start This is a public read-only wiki space

More Related