2019-09-09-rsoc-minutes
slides-interim-2022-rfcedprog-09-sessa-2019-09-09-rsoc-minutes-00

RFC SERIES OVERSIGHT COMMITTEE (RSOC)
August 9, 2019 RSOC Meeting

Reported by: Cindy Morgan, IETF Secretariat

ATTENDEES
---------------------------------
  Sarah Banks (RSOC Chair) 
  Heather Flanagan (RSE, non-voting)
  Tony Hansen 
  Cindy Morgan (Scribe, non-voting)
  Mark Nottingham 
  Peter Saint-Andre
  Portia Wenze-Danley (IETF LLC Board Liaison, non-voting)

REGRETS
---------------------------------
  Christian Huitema (IAB Lead)
  Adam Roach


RSOC DECISIONS: 2019
---------------------------------

  - 2019-02-19: RSOC concludes that handling the management of the v3 
    grammar will be the RFC Series Editor's call.

  - 2019-04-30: RSOC endorses Heather Flanagan asking the IAB to 
    progress draft-flanagan-fiftyyears-05 on the IAB stream.

  - 2019-07-22: RSOC agrees on the following RPC SLA exception process:

    • The RSE will notify the IETF LLC that the SLA will be missed in Q3 
      2019, and that an exception has been requested by the RPC.
    • The IETF LLC will request a report from the RPC to explain why the 
      SLA will be missed, and how resources are being used for things 
      not currently counted towards the SLA.

  - 2019-07-25: RSOC will invite the RPC to participate as non-voting 
    members in face-to-face RSOC meetings.

  - 2019-08-12: RSOC will request that the IETF LLC extend the RPC 
    contract by two years. 

  - 2019-08-12: RSOC will put out an SOW for a temporary RFC Series 
    Project Manager to handle the day-to-day tactical functions while 
    the community discusses the evolution of the RFC Editor Model.

  - 2018-08-19: RSOC will request that that the IETF LLC suspend the RPC 
    SLA until after Q1 2020:

    • 2019-09-15: New format goes live
    • 2019-09-15 - 2019-10-31: Identify and fix critical bugs
    • 2019-11-01: RPC workload considered stable for new state of play
    • 2019-11-01 - 2020-01-21: RPC works in the new state of play and 
      collects input on what that means for their workload
    • 2020-01-21: RSOC proposes updated SLA


NEW ACTION ITEMS
---------------------------------

  - 2019-09-09: Heather Flanagan and the RSOC to produce a blog post 
    about the new format and the first v3 RFC.

  - 2019-09-09: Sarah Banks to collate the feedback on the new SOW.

  - 2019-09-09: Sarah Banks to send out a Doodle poll to schedule a call 
    during the week of 2019-09-16 to discuss the feedback on the SOW.

  - 2019-09-09: RSOC members to submit questions for the Q&A with 
    Heather Flanagan to be used for on-boarding future RSEs. 


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

1. Administrivia

1.1. Meeting Minutes.

  The following meeting minutes were approved:

  - 2019-08-19 RSOC meeting

1.2. Action item review

  In progress:

  - 2019-08-19: Sarah Banks and Portia Wenze-Danley to figure out who 
    will take the SLA timeline back to the LLC.

  - 2019-08-12: Portia Wenze-Danley to follow up with the IETF LLC 
    regarding a two-year extension of the RPC contract.

  - 2019-08-12: Mark Nottingham to check with Ted Hardie and Cindy 
    Morgan about setting up an RSOC wiki on the IAB website.

  Done: 

  - 2019-08-12: Sarah Banks to draft a statement of work for a person to 
    temporarily handle the tactical aspects of the RFC Series Editor 
    role during the ongoing community discussion about the RFC Editor 
    Model. Target date: Send to the IAB and IETF LLC by 2019-08-19.

  - 2019-08-19: Sarah Banks to draft a new SLA timeline and send it out 
    to the RSOC for review. Target date: 2019-08-20.

  - 2019-08-19: RSOC to review SLA timeline. Target date: 2019-08-23.


2. Format update

  Heather Flanagan reported that the RFC Production Center is busy with 
  the last-minute pieces for the transition to v3, including fixing a 
  bug in how Internet-Drafts are referenced. She is also working on the 
  XML vocabulary.

  On 2019-09-16, the RPC will convert documents that are in AUTH48 to 
  v3, and any RFCs published after that point will be in v3. Heather 
  Flanagan noted that she could not say when the first v3 RFC would be 
  published, as the timing depends on the AUTH48 process, which varies 
  by document.

  Sarah Banks said that it would be nice if some sort of message could 
  go out celebrating the first v3 RFC once it is published. Heather 
  Flanagan replied that Greg Wood has asked her about writing a post on 
  the new format for the IETF blog; she noted that a mutual RSE/RSOC 
  note about this would be good.

  Action item: Heather Flanagan and the RSOC to produce a blog post 
  about the new format and the first v3 RFC.


3. Interim meeting updates

  Heather Flanagan reported that there will be three virtual interim 
  meetings between now and IETF 106 in Singapore, as well as a BOF-like 
  session during IETF 106. The goal of the meetings is to discuss how 
  the community will have the conversation about how to evolve the RFC 
  Editor Model, and figure out who will determine the consensus for that 
  process. These meetings are not to discuss the evolution of the RFC 
  Editor Model itself, but to decide on the process that will be used 
  for that discussion.

  Details for the virtual interim meetings are available on the RSE 
  wiki: https://www.rfc-editor.org/rse/wiki/doku.php?id=interim

  Heather Flanagan noted that invitations had been sent to the IETF 
  discussion list, the RFC-interest list, the IETF WG chairs list, and 
  the IETF liaisons list. She has also been trying to reach out to 
  network operator groups and the ISOC chapter heads.

  Several RSOC members indicated that they plan to attend one of the 
  virtual interim meetings to listen to the discussion.


4. SOW Update

  Sarah Banks reported that she has been trying to collect the feedback 
  on the draft SOW that were received on the RFC-interest and IETF 
  discussion lists. She suggested that the RSOC hold a separate call to 
  go through the feedback once the comment period ends on 2019-09-14. 
  The RSOC agreed that was a good idea.

  Action item: Sarah Banks to collate the feedback on the new SOW.

  Action item: Sarah Banks to send out a Doodle poll to schedule a call 
  during the week of 2019-09-16 to discuss the feedback on the SOW.


5. Documenting the RSE Role

  Sarah Banks noted that during IETF 105, the RSOC discussed having 
  Heather Flanagan appear on a series of recorded WebEx calls where she 
  would answer questions that would be used as on-boarding materials for 
  future RSEs. Sarah said that if the RSOC wants to proceed with that 
  plan, they should put together a list of questions and then share it 
  with Heather, and then schedule those calls.

  Heather Flanagan replied that if she had the questions in advance, it 
  might be simpler for her to just give written responses, rather than 
  trying to set up a series of calls. She noted that whether calls were 
  set up or not, Heather would have her responses written out ahead of 
  time anyway. Given that, the RSOC agreed to forgo setting up those 
  calls. Instead, Heather Flanagan shared a Google document where RSOC 
  members could put in their questions.

  Action item: RSOC members to submit questions for the Q&A with Heather
  Flanagan to be used for on-boarding future RSEs. Submit questions at: 
  https://docs.google.com/document/d/1TBpjlRq0HwiBonmu_5mwger8XI2a3HYGKKeJvNAmKKQ/edit