RFC SERIES OVERSIGHT COMMITTEE (RSOC) February 26, 2020 RSOC Meeting Reported by: Cindy Morgan, IETF Secretariat ATTENDEES --------------------------------- - Jay Daley (IETF LLC Board Liaison, non-voting) - Christian Huitema (IAB Lead) - John Levine, (Temporary RFC Series Project Manager, non-voting) - Cindy Morgan (Scribe, non-voting) - Mark Nottingham - Adam Roach - Peter Saint-Andre GUEST --------------------------------- - Alice Russo (RFC Production Center) REGRETS --------------------------------- - Sarah Banks (RSOC Chair) - Tony Hansen RSOC DECISIONS: 2020 --------------------------------- 2019 Decisions: ACTION ITEM REVIEW --------------------------------- Done: - 2020-01-22: Sarah Banks to invite Sandy Ginoza to attend future RSOC meetings. - 2020-01-22: Mark Nottingham to draft a message to the IAB and RFC- interest on behalf of the RSOC about the impact of changes to the v3 format as it becomes operational. In Progress: - 2020-01-22: Sarah Banks to get an update on the current status of the RPC's tools from Sandy Ginoza. - 2020-01-22: Sarah Banks to add an item to the monthly RFC Series report to the IAB to note that the timeline to propose a new SLA for the RPC has slipped because the tools are not yet in a steady state. New: - 2020-02-26: John Levine to ask legal counsel (cc'ing Jay Daley) what exactly is required to authenticate an RFC when responding to a subpoena. - 2020-02-26: John Levine to draft a report for RSOC outlining all of the open issues with the v3 work. - 2020-02-26: Mark Nottingham to ask the IAB about reporting on the open issues with the v3 work during the IETF 107 plenary. - 2020-02-26: Mark Nottingham to investigate whether the current version of SVG Tiny will be deprecated by the W3C. - 2020-02-26: John Levine to draft a plan on how to manage canonical versions of the RELAX NG schema used in XML2RFC v3. - 2020-02-26: John Levine to draft a plan on how to manage change control for the v3 XML. 1. Administrivia Peter Saint-Andre chaired the meeting in Sarah Banks' absence. The minutes of the 2020-01-21 RSOC meetings were approved pending an edit to be made by Cindy Morgan. 2. Status of v3 work John Levine reported that while the number of tickets being filed against the v3 tools is going down, the total number of tickets does not give the full picture because there is a lot of informal back and forth between Henrik Levkowetz and the RPC, so some things are being fixed without tickets being opened. John said that Henrik does not expect the v3 tools to be stable before the end of the year. Most of the open issues are related to formatting the PDF versions of documents. XML is the canonical format, and the XML is embedded in the PDF-A versions of RFCs. The PDFs may be regenerated from the canonical XML. The PDF versions are what would be used to respond to subpoenas, so if the PDF gets regenerated there may be questions about which version to use. Mark Nottingham asked if there is any document that describes what the legal team needs to have in order to respond to a subpoena. * Action item: John Levine to ask legal counsel (cc'ing Jay Daley) what exactly is required to authenticate an RFC when responding to a subpoena. * Action item: John Levine to draft a report for RSOC outlining all of the open issues with the v3 work. * Action item: Mark Nottingham to ask the IAB about reporting on the open issues with the v3 work during the IETF 107 plenary. Christian Huitema asked if there were other open issues besides rendering the PDFs, such as with SVG or Unicode. John Levine replied that there is an open question about whether the version of SVG Tiny being used will be deprecated by the W3C. * Action item: Mark Nottingham to investigate whether the current version of SVG Tiny will be deprecated by the W3C. 3. SLA Update John Levine reported that the tools are not yet in a steady enough state for the RPC to know what their regular work flow will be under the new format. Peter Saint-Andre noted that this information should be included in the report to the community at IETF 107. Alice Russo reported that processing times have improved since the end of 2019, but are still longer than the milestone for the previous SLA. She also noted that a large chunk of Cluster 238 will move into AUTH48 soon, which may impact processing times. Peter Saint-Andre asked if the IESG was doing anything special to encourage authors to review things in AUTH48 in a timely manner. Adam Roach replied that the RPC is setting up a mailing list for all of the authors in Cluster 238 so that issues that affect multiple documents in the cluster can be discussed at the same time. 4. Status of xml2rfc and issues about archival XML RFCs John Levine reported that there was not much new to report since the RSOC meeting on 2020-01-21. Jay Daley noted that there are iterations on v3, and asked whether those iterations were being documented. Alice Russo replied that the RELAX NG (REgular LAnguage for XML Next Generation) (RNG) is part of the XML2RFC package for each release, and so each RFC's HTML can be matched to the RNG; John Levine was not sure how up-to-date that was. Jay Daley suggested that some discipline be inserted into the historical version management for XML2RFC v3 to ensure there are copies of all the things that were used. * Action item: John Levine to draft a plan on how to manage canonical versions of the RELAX NG schema used in XML2RFC v3. * Action item: John Levine to draft a plan on how to manage change control for the v3 XML. 5. AOB None