RFC Series Editor Updates IETF 102 Montreal, Canada

RFC Format Project Update – Primary Goals Project goals: XML as the unchanging, underlying format TXT, PDF/A-3, HTML as the outputs SVG line art (black and white) allowed Non-ASCII characters allowed http://www.rfc-editor.org/rse/format-faq 7/9/2019 RFC Series Editor Status Report

RFC Format Project – Update Text publication formatter (v3 to TXT) will be released for testing later this month Phase 1 (basic functionality) is mostly complete for rfc-xmldiff, rfclint, and svgcheck Phase 2 underway to add interactive aspell to rfclint, xmldiff (advanced html file output), issue fixes https://trac.tools.ietf.org/tools/ietfdb/wiki/FormatToolsPlan 7/9/2019 RFC Series Editor Status Report

AUTH48 Experiment - GitHub The RPC is working with the IESG and authors to use GitHub for the AUTH48 phase of draft-ietf-tls13-28 draft-ietf-rtcweb-jsep-24 See the RSE wiki page for an outline of the experiment A final report on the experiment will be produced after both docs are published as RFCs 7/9/2019 RFC Series Editor Status Report

RFC Streams and Statuses Community discussion underway re: the question of clarity around the different streams and document statuses for RFCs Mailing list: https://www.ietf.org/mailman/listinfo/rfcplusplus BoF: Monday, 16 July 2018 @ 18:10-19:40, Laurier room 7/9/2019 RFC Series Editor Status Report

SLA – RFC Editor Time (RET) Tier 1 PGTE < 1950 67% RFCs pub <= 6 wks RET Tier 2 1950 < PGTE < 3072 50% RFCs pub <= 12 wks RET (given quarter or subsequent quarter) Tier 3 3072 < PGTE possibly renegotiate expected RET “Tier 2*” indicates when Tier 2 is being applied in the “subsequent quarter” per the SLA. as noted above) Tier 1: When there is a normal amount of input, the SLA is 67% of documents published within the period have an RFC Editor-controlled time that adds up to six weeks or fewer. Where ‘normal’ is defined as less than 1950 Pages gone to EDIT (PGTE). Tier 2: When there is a moderate burst in the amount of input, then the SLA shifts to 50% of documents published within the period have an RFC Editor-controlled time that adds up to 12 weeks or fewer within the given quarter or the subsequent quarter. Where a ‘moderate’ burst is defined as 1950 – 3072 (inclusive) Pages gone to EDIT (PGTE). Tier 3: When there is a large burst in the amount of input, then the SLA must be discussed and renegotiated. Where ‘large’ burst is defined as greater than 3072 Pages gone to EDIT (PGTE). Q1 2017: 66% (met SLA at tier 1) Q1 2017: 32% of published docs were part of cluster sizable clusters: 6 part of C279; 8 part of C283 Q1 Expedited requests for: draft-hardy-pdf-mime Q1 2016: missed target – delayed effect of burst 89% published within 12 wks (tier 2) Stats & Metrics: The RPC has deployed the code John Levine provided per the RFC Editor’s Statistics and Reporting project.  The current code uses a more accurate algorithm for counting PGTE (pages to EDIT); this change results in the RPC having missed the SLA for Q1 2016.  Note that, previously, the RPC’s stats machinery was focused on monthly document counts; PGTE was informative and was not part of the SLA equation. Recovery from high subs in Q1 and Q3 with average subs in Q2 – no real slow down until Q4 Processing well in Q4, but then SLA goal shifts to fewer weeks in Q1 Cluster impact: Q1 2016: 29% of published docs were part of a cluster Q4 2015: 29% Q3 2015: 34% Q2 2015: 44% Q1 2015: 30% Notes: New SLA went into effect Jan. 2017; earlier data is provided for context. PGTE is calculated more accurately since a switch to new stats software in Oct. 2016.

If looking at page counts, not so as low as it looks per doc Average pg ct / doc = 26 pgs/doc (2015-2016) Current = 22% of submitted pages so far (compared with 2017) – but only 17% of docs Page counts moved to EDIT/PUB (using JL stats): 2013: 7099 / 6622 2014: 8003 / 8174 2015: 8655 / 7984 2016: 7795 / 8097 2017: 6204 / 6589 YTD: 1392 / 1199 (only went back to 2013 because that is first complete year we have state history for) 7/9/2019 IETF 101