2022-04-11-rsoc-minutes
slides-interim-2022-rfcedprog-12-sessa-2022-04-11-rsoc-minutes-00

RFC SERIES OVERSIGHT COMMITTEE (RSOC)
April 11, 2022 RSOC Meeting

Reported by: Cindy Morgan, IETF Secretariat

ATTENDEES
---------------------------------
 Jay Daley (IETF LLC Board Liaison, non-voting)
 Sandy Ginoza (RFC Production Center, guest)
 Tony Hansen 
 Cullen Jennings (IAB Lead)
 John Levine, (Temporary RFC Series Project Manager, non-voting)
 Cindy Morgan (Scribe, non-voting)
 Peter Saint-Andre (RSOC Chair) 

REGRETS
---------------------------------
 Sarah Banks 
 Adam Roach
 David Schinazi 

RSOC DECISIONS: 2022
---------------------------------
  - 2021 Decisions: 
<https://www.iab.org/wp-content/IAB-uploads/2022/01/rsoc-decisions-2021.txt>

  - 2020 Decisions: 
<https://www.iab.org/wp-content/IAB-uploads/2021/01/rsoc-decisions-2020.txt>

  - 2019 Decisions: 
<https://www.iab.org/wp-content/IAB-uploads/2020/01/rsoc-decisions-2019.txt>


ACTION ITEM REVIEW
---------------------------------

  New:

    - 2022-04-11: John Levine and Peter Saint-Andre to send an email to 
      the IESG about the backlog of unprocessed errata.  
      * Deadline: 2022-05

    - 2022-04-11: John Levine to post the new version of draft-iab-
      rfc7991bis to the Internet-Drafts repository and seek feedback on 
      the RFC-interest list. 
      * Deadline: 2022-05

  Done:

    - 2022-03-02: RSOC to write something up for the IAB that maps out 
      how RSOC responsibilities will be handled in the new model.
    * Deadline 2022-04

    - 2021-10-18: John Levine to update draft-iab-rfc7991bis with help 
      from Peter Saint-Andre.
      * Deadline 2022-04


MINUTES
---------------------------------

1. Administrivia

  Approval of the 2022-03-14 RSOC minutes was deferred to the next RSOC 
  meeting.


2. v3 Issues and Tools

  John Levine reported that he pushed a new version of draft-iab-
  rfc7991bis to GitHub that he believes matches what the code currently 
  does. 

    * Action item: John Levine to post the new version of draft-iab-
      rfc7991bis to the Internet-Drafts repository and seek feedback on 
      the RFC-interest list. 
      - Deadline: 2022-05


3. RFC-Futures Update 

  Peter Saint-Andre reported that all four documents related to the RFC 
  Editor Model transition are now in the RFC Editor Queue.

  The Call for Nominations for the RFC Series Working Group Chair 
  positions is open until 2022-04-18. Peter Saint-Andre encouraged RSOC 
  members to think about potential candidates and encourage them to 
  volunteer.


4. RSOC Transition Planning

  RSOC reviewed the RSOC transition plan drafted by Peter Saint-Andre. 
  Peter will send the plan to the IAB and follow up with Mirja Kühlewind 
  about the timing for the seating of the RFC Series Advisory Board.


5. Errata Backlog

  John Levine noted that there is a sizable backlog of unprocessed 
  errata and asked if there is anything that RSOC can do to help with 
  this, since having a lot of unresolved errata does not look good from 
  the outside.

  Cullen Jennings said that something like a Hackathon for errata might 
  help the IESG clear the backlog.

  Sandy Ginoza said that the RPC is actively working on the editorial 
  errata, so it is mostly technical errata that remains unprocessed. The 
  RPC is also looking at ways errata processing could be improved with 
  better tooling.

  * Action item: John Levine and Peter Saint-Andre to send an email to 
    the IESG about the backlog of unprocessed errata.  


6. AOB

  Jay Daley reported that the RSCE search committee has met once and 
  that the recruiters are currently interviewing members of the 
  community for input about the RSCE job description. 


7. Next RSOC Meeting

  The next RSOC meeting will be on Monday, 2022-05-09 at 1000 PDT.


Appendix: RSOC Transition Plan
  
  Author: Peter Saint-Andre
  Last Updated: 2022-03-28
  
  With our transition to version 3 of the RFC Editor Model, the RFC 
  Series Oversight Committee (RSOC) will be disbanded. This document 
  maps out how responsibilities currently assigned to the RSOC will be 
  handled under the new model.
  
  In accordance with RFC 6635, RSOC operates under authority delegated 
  by the IAB to do the following:
  
  1. Approve consensus policy and vision documents developed by the RFC 
     Series Editor (RSE). Under version 3, developing policy documents 
     is now the responsibility of the RFC Series Working Group (RSWG), 
     and approval of such documents is the responsibility of the RFC 
     Series Approval Board (RSAB).
  
  2. Complete annual reviews of the RSE. The RSE role has been split 
     amongst several groups and individuals, so this review function is 
     obsolete. However, the IETF LLC now has responsibility for review 
     of the RFC Series Consulting Editor, a new role under version 3 of 
     the Model.
     
  3. Manage RSE candidate selection and advise the IAB on candidate 
     appointment. Again, this function is now obsolete, however the IETF 
     LLC is now responsible for selection of the RSCE, advised by a 
     selection committee chosen by the IETF LLC Executive Director.
     
  4. Ensure that that the RFC Series is run in a transparent and 
     accountable manner. Transparency and accountability are now ensured 
     by the structure established through draft-iab-rfcedfp-rfced-model.
     
  5. Advise the RSE and other parties regarding disagreements that arise 
     during the execution of the RFC Editor operations. Under version 2 
     of the Model, resolution of such disagreements was primarily the 
     responsibility of the RSE, with the RSOC serving in an advisory 
     capacity. After the resignation of the RSE, the RSOC has been 
     filling in by working with the RPC, the Temporary RFC Series 
     Project Manager, and individuals associated with the tools used by 
     the RPC; this has been happening through the “RFC XML and Style 
     Guide change management team” that the RSOC established in October 
     2020, on which RSOC member Peter Saint-Andre has been serving. 
     Under version 3 of the model, the RPC will seek the advice of the 
     RSAB in resolving such disagreements where necessary.
     
  As far as we know, this is the extent of RSOC responsibilities under 
  version 2 of the RFC Editor Model.