RFC Series Approval Board (RSAB) Meeting Minutes 2022-07-25, Philadelphie 1. Administrivia 1.1. Attendance Lars Eggert Sandy Ginoza Mirja Kühlewind Eliot Lear Cindy Morgan (Scribe) Colin Perkins Regrets: Jay Daley Guests: John Levine (Temporary RFC Series Project Manager) Eric Rescorla (RFC Series Working Group Chair) Pete Resnick (RFC Series Working Group Chair) Peter Saint-Andre (former RSOC Chair) David Schinazi (former RSOC Member) Robert Sparks (Tools Team Project Manager) Observers: Belete Ageze Alessandro Amirante Mike Bishop Carsten Bormann Tommaso Caiazzi Dhruv Dhody John Klensin Paul Hoffman Julian Reschke Simon Romano Alice Russo Shu-Fang Shu Martin Thomson Alessandro Toppi Peter Wang Thom Wiggers Greg Wood Yoshiro Yoneya Li Zhang 1.2. Agenda bash and announcements No changes were made to the agenda. 1.3. Meeting Minutes The RSAB agreed on the following process for approving meeting minutes: • Minutes will be reviewed over email. • Approval requires at least one "yes" and no objections. • Approved minutes will be posted in the Datatracker. 1.4. RSAB Meeting Schedule The RSAB discussed whether they should reserve a regular meeting time or schedule meetings on an as-needed basis. Colin Perkins asked how often the RSWG is expected to meet. Pete Resnick replied that he expects that the RSWG will meet during IETF meetings and do everything else on the mailing list, at least initially. Lars Eggert said that he thinks RSAB should meet during IETF meetings, and suggested that the RSAB meetings could be combined with the existing stream managers' meeting. The RSAB agreed to meet in person during IETF meetings and schedule online meetings in between as the need arises. Eliot Lear pointed out that the RSAB is explicitly not part of the IETF, and that RSAB meetings are open to observers, so there needs to be a way for that to be possible without having to pay the IETF meeting fee. Mirja Kühlewind asked whether the RSAB needs to do any reporting at the IETF Plenary. Lars Eggert said that it does not by default, and should only if there is something important to report. 1.5. RSAB Chair Selection According to RFC 9280: The RSAB shall annually choose a chair from among its members using a method of its choosing. If the chair position is vacated during the chair's term, the RSAB chooses a new chair from among its members. The RSAB agreed that the RSAB Chair selection should be done annually after the IETF NomCom cycle has concluded. The RSAB selected Mirja Kühlewind as the RSAB Chair for the 2022-2023 term. 1.6. RFC Series Oversight Committee (RSOC) Handover The RSOC would like to make the RSAB aware of the need to address day- to-day operational issues that arise during the editing and publication of RFCs; these are currently handled via the "RFC XML and Style Guide Change Management Team (CMT)." Mirja Kühlewind noted that the CMT was set up because there was a big backlog and asked whether it needed to be kept on a permanent basis. Peter Saint-Andre replied that he did not necessarily think so, as some of these issues can be handled between the RFC Production Center (RPC) and the Tools Team, but with some other things, it is not clear whether it is a procedural issue or a policy issue. Someone needs to triage what comes into the RPC. Sandy Ginoza said that the RPC is not XML experts, so some of the questions are about whether things are bugs or if the vocabulary can be used in certain ways. Mirja Kühlewind said that while the CMT was initially convened under RSOC, the RPC can meet with whoever they need to in order to get the expertise they need. The RSAB agreed with that assessment. Peter Saint-Andre noted that the RSOC had overseen the work of the Temporary RFC Series Project Manager (John Levine), and it was RSOC's understanding that he will continue to serve in this role until the appointment of the RFC Series Consulting Editor (RSCE). Oversight of the Temporary RFC Series Project Manager can continue under the IETF LLC Board and Executive Director. The RSAB will invite John Levine to join RSAB meetings as long as he serves in the role of Temporary RFC Series Project Manager. Eliot Lear suggested that John Levine provide the RSWG with a list of the open issues to see if any of them should be picked up in the working group. 2. Document Approval There were no documents from the RSWG to approve at this time. The RSAB discussed whether they need balloting support in the Datatracker. Robert Sparks said that he was planning to add it, because things from the RSWG about XML grammar and the rendering format will require careful review. Lars Eggert asked how much effort would be required to add balloting for the RSAB. Robert Sparks replied that he expects it would take about a day; much of the necessary work was already done when adding balloting for the IRSG to the Datatracker. Lars Eggert requested that balloting for the RSAB be available by IETF 115. Lars Eggert asked Robert Sparks and the Tools Team to look at the workflow outlined in RFC 9280 and propose a tooling plan to support that. 3. RPC: Things to note Per RFC 9280: If issues arise with the implementation of particular policies, the RPC brings those issues to the RSAB, which interprets the policies and provides interim guidance to the RPC, informing the RSWG of those interpretations. Sandy Ginoza said that the RPC had nothing to note at this time. 4. RSAB, RSWG, and the IETF Note Well Peter Saint-Andre asked whether the IETF Note Well applies to the RSWG and the RSAB, noting that RFC 9280 says that the IETF's anti- harassment policy applies to the RSWG and the RSAB. Eric Rescorla said that he would add an item to the RSWG agenda to discuss this with the group.