RFC SERIES OVERSIGHT COMMITTEE (RSOC) April 7, 2016 RSOC Meeting Reported by: Cindy Morgan, IETF Secretariat ATTENDEES --------------------------------- Sarah Banks (Chair) (remote) Nevil Brownlee Heather Flanagan (RSE, non-voting) Joel Halpern Tony Hansen (remote) Joe Hildebrand Bob Hinden Cindy Morgan (Scribe, non-voting) Ray Pelletier (IAOC Liaison, non-voting) Adam Roach Robert Sparks (Lead) MINUTES --------------------------------- 1. RSE Goals Heather Flanagan reviewed the RSE's goals for 2015-2016. The RPC contract went out to bid, and a vendor was selected. Work on the new formats continues. The IAB expects to approve the format documents once the updated versions addressing comments from the community review period have been posted. Work on the RFC format tools is progressing. Heather Flanagan is currently waiting for the I-Ds to be approved, and for any final feedback from the Tools Team. She expects the RFC to be posted in April or May 2016. The RFC format CSS is still waiting for Tools Team feedback and needs to go out for community comment. The contract for the statistics and metrics project was awarded to StandCore, LLC. The work is expected to complete by the end of April 2016. Meetings were held during IETF to sort out how the new tool interprets data versus how the RPC interprets data. Robert Sparks asked to take a look at the code for the new stats and metrics tool. The digital preservation work remains on the back burner; there has been a slow back and forth with the Royal Library of Sweden. The RSS feed is mostly ready, but there has been some question about a publisher identifier that is used in the feed; the RFC series would not have control over that identifier, and so Heather Flanagan has asked if the RFCs' DOIs can be used instead. The currently-expired digital preservation draft needs to be updated to take into account information from "Digital Signatures on RFC and Internet-Draft Documents" . Progress is being made on the RFC Editor Infrastructure/Data Accessibility work. A team consisting of Sandy Ginoza, Heather Flanagan, Joe Hildebrand, Henrik Levkowetz, Alice Russo and Robert Sparks is working on the new architecture and hopes to begin implementing it in an incremental fashion starting in 2017. 2. RPC SLA Heather Flanagan reported that 2015 was a big year for the RFC Series; it received the third-most submissions in the series' history. Submissions were very bursty, and never really settled down over the course of the year. The RPC has worked through the backlog, and expects to be solidly with in the SLA as projected for Q2. 3. RFC Streams Design Team Joe Hildebrand reported that there have been questions from the IESG with respect to the Independent stream (as well as the IAB and IRTF streams), and how those interact with the larger RFC Series from a branding perspective. A few people are getting together to think about ideas in this space, as this is an opportune time for the discussion (the RSE contract is coming up for bid, and the current ISE is looking to retire). 4. Upcoming meetings Heather Flanagan is planning to attend the AMS/IETF/IAB/RFC Editor management team meeting on 2-3 May 2016, in Reston, VA. She is also planing to attend the IESG retreat on 10-12 May in Cambridge, MA. The RSOC discussed whether to hold a retreat at IETF 96, as been the norm for previous July IETF meetings. Noting the difficulty in scheduling such a retreat (conflicts with CodeSprint and Hackathon), and that it was unlikely that the agenda would be able to fill half a day, the RSOC decided to have a regular lunch meeting during IETF 96, as well as an executive session to discuss the RSE contract. Heather Flanagan will send out a Doodle poll once the preliminary agenda is published to find a time that works for everyone. Several people noted that it would be nice to have some sort of team- building activity (e.g. a dinner) outside of regular meeting time. 5. AOB Heather Flanagan asked if there were any objections to publishing the RSE Operations Guide on the RFC Editor website. There were no objections, so Heather will do that. Heather Flanagan noted that the IETF is currently discussing a privacy policy for the IETF website, and asked if the RFC Series should reuse what the IETF ends up with. The RSOC suggested waiting until the IETF (and perhaps IRTF) privacy policies are sorted out before setting policy for the RFC Editor website.