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

RFC SERIES OVERSIGHT COMMITTEE (RSOC)
October 15, 2019 RSOC Meeting

Reported by: Cindy Morgan, IETF Secretariat

ATTENDEES
---------------------------------
 Sarah Banks (RSOC Chair) 
 Heather Flanagan (RSE, non-voting)
 Tony Hansen 
 Christian Huitema (IAB Lead)
 Cindy Morgan (Scribe, non-voting)
 Adam Roach
 Peter Saint-Andre


REGRETS
---------------------------------
 Mark Nottingham 
 Portia Wenze-Danley (IETF LLC Board Liaison, non-voting)


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.

  - 2019-08-19: RSOC will request 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

  - 2019-10-15: RSOC will make sure that "maintenance of the RFC Style 
    Guide" goes into the SOW for the next permanent RSE.

  - 2019-10-15: RSOC will make sure that "updating the AUTH48 process" 
    goes into the SOW for the next permanent RSE.


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

  New:

  - 2019-10-15: Heather Flanagan to work with the RPC to write down 
    some guidance as to what is meant by the goal to to re-render the 
    output formats of existing documents as infrequently as possible.

  - 2019-10-15: Sarah Banks to follow up with the RSOC and Portia Wenze-
    Danley via email about asking the LLC to keep Heather Flanagan on 
    retainer for three months to help with the temporary RFC Series 
    Project Manager transition.

  In Progress:

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

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

1. Administrivia

1.1. Meeting Minutes

  The minutes of the 2019-09-09 RSOC meeting were approved.

1.2. Action item review

  The action item list was reviewed. (See list above.)


2. v3 Output Formats: Short/long Term Maintenance Plan 

  Heather Flanagan noted that when the v3 project started, they knew 
  that the output formats would not be the canonical format, but that 
  there would occasionally be a need to re-render the output formats 
  from the canonical XML. The original goal was to re-render the output 
  formats of existing documents as infrequently as possible. Heather 
  asked the RSOC if that was still the goal.

  Adam Roach asked what the concerns are with re-rendering documents. 
  Heather Flanagan replied that the RPC will need to track precisely 
  when a document is rendered or re-rendered because that information is 
  often requested in subpoenas; the RPC needs to be able to respond with 
  an accurate date for when each document was made available to the 
  public in each format.

  Peter Saint-Andre asked why the canonical XML format would not be used 
  to respond to subpoenas. Heather Flanagan replied that XML is not of 
  practical use to lawyers because it is not easily human-readable.

  After a discussion the RSOC agreed that minimal re-rendering should 
  remain the goal. 

  Action item: Heather Flanagan to work with the RPC to write down 
  some guidance as to what is meant by the goal to to re-render the 
  output formats of existing documents as infrequently as possible.

  Heather Flanagan noted that in the future, the RSOC may want to 
  consider whether to re-render the RFC output formats to keep up with 
  things like changes to best practices for accessibility.

3. RFC Style Guide

  Heather Flanagan proposed that she plan to update the RFC version of 
  the RFC Style Guide (RFC 7322) by the end of the year, and that 
  further changes be postponed until the next RSE is hired; this would 
  not be a project for the temporary RFC Series Project Manager. In the 
  interim period, the RPC can put any new changes into the web portion 
  of the Style Guide <https://www.rfc-editor.org/styleguide/part2/>.

  The RSOC agreed that this was a reasonable plan.

  Heather Flanagan noted that the RSOC should make sure that maintenance 
  of the RFC Style Guide goes into the SOW when the RSOC is looking to 
  hire the next RSE.


4. AUTH48 Changes 

  Heather Flanagan noted that making changes to the AUTH48 process had 
  been the next big planned project after the new format project was 
  completed. Since this will have broad implications, this should not be 
  something for the RFC Series Project Manager, but instead should go 
  into the SOW for the next RSE.

5. Current RSE priorities

  Heather Flanagan reviewed her list of current priorities for the rest 
  of 2019 with the RSOC:

    1. xml2rfc v3 7991bis and the v3 format, 
    2. RFC Model process discussion, 
    3. 2019 vendor evaluation, 
    4. publish new style guide (4 November I-D cut-off date), 
    5. RSE Ops Guide and Reading List
    6. AUTH48 for Fifty Years of RFCs, 
    7. resolve the RFC 32 issue, 
    8. archival support for v3 (contact archival partners) 


6. Reminder: 2020 marks 10 years with AMS as the home of the RPC/
   Publisher


7. LLC Board actions

  Sarah Banks asked the RSOC whether they should recommend that the IETF 
  LLC take Heather Flanagan up on her offer to remain available on 
  retainer for three months after the end of her contract to help with 
  the temporary RFC Series Project Manager transition. The RSOC members 
  who were on the call agreed that this was a good idea.

  Action item: Sarah Banks to follow up with the RSOC and Portia Wenze-
  Danley via email about asking the LLC to keep Heather Flanagan on 
  retainer for three months to help with the temporary RFC Series 
  Project Manager transition.