2020-10-19-rsoc-minutes
slides-interim-2022-rfcedprog-10-sessa-2020-10-19-rsoc-minutes-00

RFC SERIES OVERSIGHT COMMITTEE (RSOC)
October 19, 2020 RSOC Meeting

Reported by: Cindy Morgan, IETF Secretariat

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

GUEST
---------------------------------
 Sandy Ginoza (RFC Production Center)

REGRETS
---------------------------------
 Mark Nottingham 
 Adam Roach


RSOC DECISIONS: 2020
---------------------------------
  - 2020-10-19: RSOC agrees to reimplement the RPC's previous SLA, 
    understanding that the amount of work involved per page has 
    increased by roughly 50% from what it was before the XML transition, 
    and so the RPC will need to keep additional staff to meet the SLA. 
    The SLA will go back into effect for Q4 2020, with the understanding 
    that the imminent release of Cluster 238 will likely affect 
    processing times.

  - 2020-05-27: RSOC agrees that the RFC Series should plan to be able 
    to regenerate the output formats of RFCs. Related action item: John 
    Levine to draft a plan that defines when it is appropriate to 
    regenerate the output formats of RFCs.

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

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

  Done:

  - 2020-09-21: Jay Daley to draft a survey to ask authors who have 
    submitted RFCs in the past year what submission format they used, 
    and (if applicable) why they did not use the v3 XML submission 
    format.
    * Deadline: October RSOC meeting

  In Progress:

  - 2020-06-22: John Levine to document the factors that appear to 
    contribute to the very low adoption by authors of v3 XML as a 
    submission format.
    * Deadline: After the results of the submission formats survey are 
      available.

  - 2020-09-21: John Levine to resolve the open issues on the "RFC v3 
    Issues" document.
    (https://docs.google.com/document/d/1Q-DfUxnVV2hZzI7ecWREFgt4tCz-DX_mikqN9RX4Yco/)
    * Deadline: 2020-10-30

  - 2020-09-21: John Levine to draft a message to the community asking 
    for input on how to handle version control for RFC output formats 
    that have been regenerated and send it to the RSOC for review.
    * Deadline: 2020-10-30.

  - 2020-09-21: Jay Daley, John Levine, Henrik Levkowetz, Peter Saint-
    Andre, and Robert Sparks to work with Sandy Ginoza to propose a 
    minimum profile of v3 XML tags to be added by the RPC.
    * Deadline: 2020-10-21

  - 2020-09-21: Sarah Banks to update the IAB on the current plan to 
    reinstate the SLA.
    * Deadline: 2020-10-21

  New:

  - 2020-10-19: Jay Daley to send out the survey about submission 
    formats.
    * Deadline: 2020-10-26

  - 2020-10-19: Jay Daley to draft a note for the RSOC Chair to send to 
    the RFC XML and Style Guide change management team asking them to 
    work with the RPC to propose the minimum profile of v3 XML tags to 
    be added by the RPC.
    * Deadline: 2020-10-23


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

1. Administrivia

  The minutes of the 2020-09-21 RSOC meeting were approved.


2. v3 Issues and Tools

  Jay Daley reported that he has drafted a survey to ask authors who 
  have submitted RFCs in the past year what submission format they used, 
  and (if applicable) why they did not use the v3 XML submission format. 
  He plans to send the survey out by 2020-10-26.

  John Levine noted that his action item to document the factors that 
  appear to contribute to the very low adoption by authors of v3 XML as 
  a submission format is waiting for the results of the survey.

  * Action item: Jay Daley to send out the survey about submission 
    formats.

  John Levine reported that Sandy Ginoza had recently added comments to 
  the "RFC v3 Issues" document. Once those comments have been resolved, 
  he thinks the document will be ready to share. John plans to have the 
  comments resolved by Friday, 2020-10-30.

  John Levine reported that he plans to draft a message to the community 
  asking for input on how to handle version control for RFC output 
  formats that have been regenerated and send it to the RSOC for review 
  by Friday, 2020-10-30.

  Jay Daley reported that the RFC XML and Style Guide change management 
  team was waiting for the group to officially be announced before they 
  began work on proposing the minimum profile of v3 XML tags to be added 
  by the RPC. Jay suggested that the RSOC Chair send the RFC XML and 
  Style Guide change management team a note about this so that there is 
  a record of the request.

  * Action item: Jay Daley to draft a note for the RSOC Chair to send to 
    the RFC XML and Style Guide change management team asking them to 
    work with the RPC to propose the minimum profile of v3 XML tags to 
    be added by the RPC.

  Sarah Banks asked if RSOC should work with the Education (EDU) Team on 
  a tutorial about how to author a draft. 

  Cullen Jennings added that it would be helpful if search results would 
  stop returning outdated information. Jay Daley replied that he is 
  working on a project to remove old information from the IETF website.

  Sarah Banks reiterated that she is looking for slides that would show 
  an author how to create a draft, including how to use the available 
  tools.

  Sandy Ginoza asked Sarah Banks if she was looking for something 
  specifically about v3, noting that there had previously been EDU 
  tutorials about v2. She added that EDU tutorials can be difficult, 
  because the number of people who show up to them is not very large, 
  and the level of experience in the audience can vary widely.

  Sarah Banks said that the tutorial should be treated holistically and 
  pushed out to WG chairs as the audience. It should be a resource for 
  new authors about how to write RFCs, updated to use the v3 tools.

  John Levine noted that there are multiple tools available, and 
  multiple ways to write an RFC; everyone has their own favorite set of 
  tools.

  Cullen Jennings added that he would be able to write up a single slide 
  that describes how he would create a draft, but he would not be able 
  to do that for the methods that he does not use. He suggested waiting 
  for the results of the submission format survey, and use that to write 
  up the three most popular tool paths.


3. SLA

  RSOC agreed to reimplement the RPC's previous SLA, understanding that 
  the amount of work involved per page has increased by roughly 50% from 
  what it was before the XML transition, and so the RPC will need to 
  keep additional staff to meet the SLA. 

  Sandy Ginoza noted that it is unlikely that the RPC will meet the SLA 
  for Q4 2020 because of Cluster 238. The last of the documents in that 
  cluster are expected to complete AUTH48 during Q4, which will affect 
  the processing times for all of the other documents in the queue. 

  The SLA will go back into effect for Q4 2020, with the understanding 
  that the imminent release of Cluster 238 will likely affect processing 
  times.

  Sarah Banks will update the IAB on the plan to reimplement the SLA by 
  2020-10-21.


4. Next RSOC Meeting

  The next RSOC meeting is scheduled for 15:00 PST on Monday, 
  2020-11-16, which is during IETF 109. RSOC discussed whether to move 
  this meeting, but ultimately decided to leave it as is.

5. Other Business

  Jay Daley noted that there are two elements of the v3 transition that 
  RSOC still needs to consider. The first issue is that there have been 
  a number of changes implemented to the v3 XML since RFC 7991 was 
  published, including:

    1) the postal element and the postalLine sub-element
    2) the <toc> element
    3) the <contact> element, the <u> element, and non-ascii characters 
       generally

  Jay Daley suggested that the RFC XML and Style Guide change management 
  team work with the RPC to sort out these changes.

  The second issue Jay Daley noted is that at some point, RSOC should 
  consider the concept of "immutability" and whether it applies to the 
  content or to the markup; should there be the ability to add new 
  markup to and RFC later? RSOC agreed that this would be a good topic 
  for future discussion.