<?xmlversion="1.0" encoding="us-ascii"?> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.3.4 --> <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ ]> <?rfc toc="yes"?> <?rfc sortrefs="yes"?> <?rfc symrefs="yes"?> <?rfc comments="yes"?>version='1.0' encoding='utf-8'?> <rfcipr="trust200902"xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" docName="draft-huitema-rfc-eval-project-07"category="info">indexInclude="true" ipr="trust200902" number="8963" prepTime="2021-01-12T22:14:50" scripts="Common,Latin" sortRefs="true" submissionType="independent" symRefs="true" tocDepth="3" tocInclude="true" xml:lang="en"> <link href="https://datatracker.ietf.org/doc/draft-huitema-rfc-eval-project-07" rel="prev"/> <link href="https://dx.doi.org/10.17487/rfc8963" rel="alternate"/> <link href="urn:issn:2070-1721" rel="alternate"/> <front> <titleabbrev="RFC-Eval-2018">Evaluationabbrev="RFC Evaluation 2018">Evaluation of a Sample ofRFCRFCs Produced in 2018</title> <seriesInfo name="RFC" value="8963" stream="independent"/> <author initials="C." surname="Huitema" fullname="Christian Huitema"><organization>Private<organization showOnFrontPage="true">Private Octopus Inc.</organization> <address> <postal> <street>427 Golfcourse Rd</street> <city>Friday Harbor</city><code>WA 98250</code> <country>U.S.A</country><region>WA</region> <code>98250</code> <country>United States of America</country> </postal> <email>huitema@huitema.net</email> </address> </author> <dateyear="2020"/> <area>General</area> <keyword>Internet-Draft</keyword> <abstract> <t>Thismonth="01" year="2021"/> <keyword>RFC Series</keyword> <keyword>Independent Submissions Editor</keyword> <keyword>documents</keyword> <keyword>publications</keyword> <keyword>publication delays</keyword> <abstract pn="section-abstract"> <t indent="0" pn="section-abstract-1">This document presents the author's effort to understand the delays involved in publishing an idea in the IETF or through the Independent Stream, from the first individual draft to the publication of the RFC. We analyze a set of randomly chosenRFCRFCs approved in 2018, looking for history and delays. We also use two randomly chosen sets ofRFCRFCs published in 2008 and 1998 for comparing delays seen in 2018 to those observed 10 or 20 years ago. The average RFC in the 2018 sample was produced in 3 years and 4 months, of which 2 years and 10 months were spent in theWorking Group,working group, 3 to 4 months for IETF consensus and IESG review, and 3 to 4 months in RFC production. The main variation in RFC production delays comes from theAUTH-48AUTH48 phase.</t><t>We<t indent="0" pn="section-abstract-2">We also measure the number of citations of the chosen RFC using Semantic Scholar, and compare citation counts with what we know about deployment. We show that citation counts indicate academic interest, but correlate only loosely with deployment or usage of the specifications. Counting web references could complement that.</t><t>The RFCs selected</abstract> <boilerplate> <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1"> <name slugifiedName="name-status-of-this-memo">Status of This Memo</name> <t indent="0" pn="section-boilerplate.1-1"> This document is not an Internet Standards Track specification; it is published forthis survey wereinformational purposes. </t> <t indent="0" pn="section-boilerplate.1-2"> This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document atrandomits discretion andrepresent a small samplemakes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not candidates for any level ofall RFCs produced, and only approximately 10%Internet Standard; see Section 2 of RFC 7841. </t> <t indent="0" pn="section-boilerplate.1-3"> Information about theRFCs produced in eachcurrent status of1998, 2008,this document, any errata, and how to provide feedback on it may be obtained at <eref target="https://www.rfc-editor.org/info/rfc8963" brackets="none"/>. </t> </section> <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2"> <name slugifiedName="name-copyright-notice">Copyright Notice</name> <t indent="0" pn="section-boilerplate.2-1"> Copyright (c) 2021 IETF Trust and2018. It is possible that different samples would produce different results. Furthermore,theconclusions drawn frompersons identified as theobservations made in thisdocumentrepresent the author's opinionsauthors. All rights reserved. </t> <t indent="0" pn="section-boilerplate.2-2"> This document is subject to BCP 78 anddo not have consensusthe IETF Trust's Legal Provisions Relating to IETF Documents (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. </t> </section> </boilerplate> <toc> <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1"> <name slugifiedName="name-table-of-contents">Table of Contents</name> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1"> <li pn="section-toc.1-1.1"> <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t> </li> <li pn="section-toc.1-1.2"> <t indent="0" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-methodology">Methodology</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2"> <li pn="section-toc.1-1.2.2.1"> <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.2.1.1"><xref derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-defining-the-important-mile">Defining theIETF.</t> </abstract>Important Milestones</xref></t> </li> <li pn="section-toc.1-1.2.2.2"> <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.2.2.1"><xref derivedContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-selecting-a-random-sample-o">Selecting a Random Sample of RFCs</xref></t> </li> <li pn="section-toc.1-1.2.2.3"> <t indent="0" pn="section-toc.1-1.2.2.3.1"><xref derivedContent="2.3" format="counter" sectionFormat="of" target="section-2.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-conventions-used-in-this-do">Conventions Used in This Document</xref></t> </li> </ul> </li> <li pn="section-toc.1-1.3"> <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-analysis-of-20-selected-rfc">Analysis of 20 Selected RFCs</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2"> <li pn="section-toc.1-1.3.2.1"> <t indent="0" pn="section-toc.1-1.3.2.1.1"><xref derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8411">RFC 8411</xref></t> </li> <li pn="section-toc.1-1.3.2.2"> <t indent="0" pn="section-toc.1-1.3.2.2.1"><xref derivedContent="3.2" format="counter" sectionFormat="of" target="section-3.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8456">RFC 8456</xref></t> </li> <li pn="section-toc.1-1.3.2.3"> <t indent="0" pn="section-toc.1-1.3.2.3.1"><xref derivedContent="3.3" format="counter" sectionFormat="of" target="section-3.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8446">RFC 8446</xref></t> </li> <li pn="section-toc.1-1.3.2.4"> <t indent="0" pn="section-toc.1-1.3.2.4.1"><xref derivedContent="3.4" format="counter" sectionFormat="of" target="section-3.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8355">RFC 8355</xref></t> </li> <li pn="section-toc.1-1.3.2.5"> <t indent="0" pn="section-toc.1-1.3.2.5.1"><xref derivedContent="3.5" format="counter" sectionFormat="of" target="section-3.5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8441">RFC 8441</xref></t> </li> <li pn="section-toc.1-1.3.2.6"> <t indent="0" pn="section-toc.1-1.3.2.6.1"><xref derivedContent="3.6" format="counter" sectionFormat="of" target="section-3.6"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8324">RFC 8324</xref></t> </li> <li pn="section-toc.1-1.3.2.7"> <t indent="0" pn="section-toc.1-1.3.2.7.1"><xref derivedContent="3.7" format="counter" sectionFormat="of" target="section-3.7"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8377">RFC 8377</xref></t> </li> <li pn="section-toc.1-1.3.2.8"> <t indent="0" pn="section-toc.1-1.3.2.8.1"><xref derivedContent="3.8" format="counter" sectionFormat="of" target="section-3.8"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8498">RFC 8498</xref></t> </li> <li pn="section-toc.1-1.3.2.9"> <t indent="0" pn="section-toc.1-1.3.2.9.1"><xref derivedContent="3.9" format="counter" sectionFormat="of" target="section-3.9"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8479">RFC 8479</xref></t> </li> <li pn="section-toc.1-1.3.2.10"> <t indent="0" pn="section-toc.1-1.3.2.10.1"><xref derivedContent="3.10" format="counter" sectionFormat="of" target="section-3.10"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8453">RFC 8453</xref></t> </li> <li pn="section-toc.1-1.3.2.11"> <t indent="0" pn="section-toc.1-1.3.2.11.1"><xref derivedContent="3.11" format="counter" sectionFormat="of" target="section-3.11"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8429">RFC 8429</xref></t> </li> <li pn="section-toc.1-1.3.2.12"> <t indent="0" pn="section-toc.1-1.3.2.12.1"><xref derivedContent="3.12" format="counter" sectionFormat="of" target="section-3.12"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8312">RFC 8312</xref></t> </li> <li pn="section-toc.1-1.3.2.13"> <t indent="0" pn="section-toc.1-1.3.2.13.1"><xref derivedContent="3.13" format="counter" sectionFormat="of" target="section-3.13"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8492">RFC 8492</xref></t> </li> <li pn="section-toc.1-1.3.2.14"> <t indent="0" pn="section-toc.1-1.3.2.14.1"><xref derivedContent="3.14" format="counter" sectionFormat="of" target="section-3.14"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8378">RFC 8378</xref></t> </li> <li pn="section-toc.1-1.3.2.15"> <t indent="0" pn="section-toc.1-1.3.2.15.1"><xref derivedContent="3.15" format="counter" sectionFormat="of" target="section-3.15"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8361">RFC 8361</xref></t> </li> <li pn="section-toc.1-1.3.2.16"> <t indent="0" pn="section-toc.1-1.3.2.16.1"><xref derivedContent="3.16" format="counter" sectionFormat="of" target="section-3.16"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8472">RFC 8472</xref></t> </li> <li pn="section-toc.1-1.3.2.17"> <t indent="0" pn="section-toc.1-1.3.2.17.1"><xref derivedContent="3.17" format="counter" sectionFormat="of" target="section-3.17"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8471">RFC 8471</xref></t> </li> <li pn="section-toc.1-1.3.2.18"> <t indent="0" pn="section-toc.1-1.3.2.18.1"><xref derivedContent="3.18" format="counter" sectionFormat="of" target="section-3.18"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8466">RFC 8466</xref></t> </li> <li pn="section-toc.1-1.3.2.19"> <t indent="0" pn="section-toc.1-1.3.2.19.1"><xref derivedContent="3.19" format="counter" sectionFormat="of" target="section-3.19"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8362">RFC 8362</xref></t> </li> <li pn="section-toc.1-1.3.2.20"> <t indent="0" pn="section-toc.1-1.3.2.20.1"><xref derivedContent="3.20" format="counter" sectionFormat="of" target="section-3.20"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rfc-8468">RFC 8468</xref></t> </li> </ul> </li> <li pn="section-toc.1-1.4"> <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-analysis-of-process-and-del">Analysis of Process and Delays</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2"> <li pn="section-toc.1-1.4.2.1"> <t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-delays-from-first-draft-to-">Delays from First Draft to RFC</xref></t> </li> <li pn="section-toc.1-1.4.2.2"> <t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-working-group-processing-ti">Working Group Processing Time</xref></t> </li> <li pn="section-toc.1-1.4.2.3"> <t indent="0" pn="section-toc.1-1.4.2.3.1"><xref derivedContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-preparation-and-publication">Preparation and Publication Delays</xref></t> </li> <li pn="section-toc.1-1.4.2.4"> <t indent="0" pn="section-toc.1-1.4.2.4.1"><xref derivedContent="4.4" format="counter" sectionFormat="of" target="section-4.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-copy-editing">Copy Editing</xref></t> </li> <li pn="section-toc.1-1.4.2.5"> <t indent="0" pn="section-toc.1-1.4.2.5.1"><xref derivedContent="4.5" format="counter" sectionFormat="of" target="section-4.5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-independent-stream">Independent Stream</xref></t> </li> </ul> </li> <li pn="section-toc.1-1.5"> <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-citation-counts">Citation Counts</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2"> <li pn="section-toc.1-1.5.2.1"> <t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-citation-numbers">Citation Numbers</xref></t> </li> <li pn="section-toc.1-1.5.2.2"> <t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-comparison-to-1998-and-2008">Comparison to 1998 and 2008</xref></t> </li> <li pn="section-toc.1-1.5.2.3"> <t indent="0" pn="section-toc.1-1.5.2.3.1"><xref derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-citations-versus-deployment">Citations versus Deployments</xref></t> </li> <li pn="section-toc.1-1.5.2.4"> <t indent="0" pn="section-toc.1-1.5.2.4.1"><xref derivedContent="5.4" format="counter" sectionFormat="of" target="section-5.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-citations-versus-web-refere">Citations versus Web References</xref></t> </li> </ul> </li> <li pn="section-toc.1-1.6"> <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-observations-and-next-steps">Observations and Next Steps</xref></t> </li> <li pn="section-toc.1-1.7"> <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t> </li> <li pn="section-toc.1-1.8"> <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t> </li> <li pn="section-toc.1-1.9"> <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="9" format="counter" sectionFormat="of" target="section-9"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t> </li> <li pn="section-toc.1-1.10"> <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t> </li> <li pn="section-toc.1-1.11"> <t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-address">Author's Address</xref></t> </li> </ul> </section> </toc> </front> <middle> <section anchor="introduction"title="Introduction"> <t>Asnumbered="true" toc="include" removeInRFC="false" pn="section-1"> <name slugifiedName="name-introduction">Introduction</name> <t indent="0" pn="section-1-1">As stated on the organization's web site, "The IETF is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet." The specifications produced by the IETF are published in the RFC series, along withindependent submissions, research papersdocuments from the IAB, IRTF, andIAB documents.Independent streams (as per RFC 8729). In this memo, the author attempts to understand the delays involved in publishing an idea in the IETF or through the Independent Stream, from the first individual draft to the publication of the RFC. This is an individual effort, and the author's conclusions presented here are personal. There was no attempt to seek IETF consensus.</t><t>The<t indent="0" pn="section-1-2">The IETF keeps records of documents and process actions in the IETFdatatrackerDatatracker <xreftarget="TRKR"/>.target="TRKR" format="default" sectionFormat="of" derivedContent="TRKR"/>. The IETFdatatrackerDatatracker provides information about RFCs and drafts, from which we can infer statistics about the production system. We can measure how long it takes to drive a proposition from initial draft to final publication, and how these delays can be split betweenWorking Groupworking group discussions, IETF reviews, IESG assessment, RFC Editor delays and final reviews by the authors–-- or, for Independent Stream RFCs, draft production, reviews by the IndependentStreamSubmissions Editor, conflict reviews, RFC Editor delays and final reviews. Tracker data is available for all RFCs, not just IETFstreamStream RFCs.</t><t>Just<t indent="0" pn="section-1-3">Just measuring production delays may be misleading. If the IETF or theeditors of theotherseriesstreams simply rubber-stamped draft proposals and published them, the delays would be short but the quality and impact might suffer. We hope that most of theRFCRFCs that are published are useful, but we need a way to measure that usefulness. We try to do that by measuring the number of references of the published RFCs in Semantic Scholar <xreftarget="SSCH"/>,target="SSCH" format="default" sectionFormat="of" derivedContent="SSCH"/>, and also by asking the authors of each RFC in the sample whether the protocols and technologies defined in the RFCs were implemented and used on the Internet. The citations measured by the Semantic Scholar include citations in other RFCs and inInternet drafts.Internet-Drafts. We also measure the number of references on the web, which provides some results but would be hard to automate.</t><t>In<t indent="0" pn="section-1-4">In order to limit theresourceresources required for this study, we selected at random 20 RFCs published in 2018, as explained in <xreftarget="sample-selection"/>.target="sample-selection" format="default" sectionFormat="of" derivedContent="Section 2.2"/>. The statistical sampling picked both IETFstreamStream and Independent Stream documents. For comparison purposes, we also selected at random 20RFCRFCs published in 1998 and 20 published in 2008. Limiting the sample to 20 out of 209 RFCs published in 2018 allows forin depthin-depth analysis of each RFC, but readers should be reminded that the this is a small sample. The sample is too small to apply general statistical techniques and quantify specific ratios, and discussions of correlation techniques would be inappropriate. Instead, the purpose is to identify trends, spotissuesissues, and document future work.</t><t>The<t indent="0" pn="section-1-5">The information gathered for every RFC in the sample is presented in <xreftarget="sample-rfc-analysis"/>.target="sample-rfc-analysis" format="default" sectionFormat="of" derivedContent="Section 3"/>. In <xreftarget="process-analysis"/>target="process-analysis" format="default" sectionFormat="of" derivedContent="Section 4"/>, we analyze the production process and the sources of delays, comparing the 2018 sample to the selected samples for 1998 and 2018. In <xreftarget="citation-numbers"/>target="citation-numbers" format="default" sectionFormat="of" derivedContent="Section 5.1"/>, we present citation counts for the RFCs in the samples, and analyze whether citation counts could be used to evaluate the quality of RFCs.</t><t>The<t indent="0" pn="section-1-6">The measurement of delays could be automated by processing dates and events recorded in thedatatracker.Datatracker. The measurement of published RFCs could be complemented by statistics on abandoned drafts, which would measure the efficiency of the IETF triaging process. More instrumentation would help understanding how large delays happen duringWorking Groupworking group processes. These potential next steps are developed in <xreftarget="conclusion"/>.</t>target="conclusion" format="default" sectionFormat="of" derivedContent="Section 6"/>.</t> </section> <section anchor="methodology"title="Methodology"> <t>Thenumbered="true" toc="include" removeInRFC="false" pn="section-2"> <name slugifiedName="name-methodology">Methodology</name> <t indent="0" pn="section-2-1">The study reported here started with a simple idea: take a sample of RFCs, and perform an in-depth analysis of the path from the first presentation of the idea to its publication, while also trying to access the success of the resulting specification. This requires defining the key milestones that we want to track, and drawing a random sample using an unbiased process.</t> <section anchor="milestones"title="Definingnumbered="true" toc="include" removeInRFC="false" pn="section-2.1"> <name slugifiedName="name-defining-the-important-mile">Defining the ImportantMilestones"> <t>TheMilestones</name> <t indent="0" pn="section-2.1-1">The IETFdatatrackerDatatracker records a list of events for each document processed by IETFWorking Groups.working groups. This has a high granularity, and also a high variability. Most documents start life as an individual draft, are adopted by aWorking Group,working group, undergo a Working Grouplast call,Last Call, are submitted to the IESG, undergo an IETFlast callLast Call and an IESG review, get eventually approved by the IESG, and are processed for publication by the RFC Editor, but there are exceptions. Some documents are first submitted to oneWorking Groupworking group and then moved to another. Some documents are published through the Independent Stream, and are submitted to the IndependentStreamSubmissions Editor instead of the IESG.</t><t>In<t indent="0" pn="section-2.1-2">In order to simplify tabulation, we break thedelayperiod frombetweenthe submission of the first draftandto the publication of the RFCininto three big components:</t><t><list style="symbols"> <t>The Working Group<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2.1-3"> <li pn="section-2.1-3.1">The working group processing time, from the first draft to the start of the IETF lastcall;</t> <t>Thecall;</li> <li pn="section-2.1-3.2">The IETF processing time, which lasts from the beginning of the IETF last call to the approval by the IESG, including the reviews by variousdirectorates;</t> <t>Thedirectorates;</li> <li pn="section-2.1-3.3">The RFC production, from approval by the IESG to publication, including theAUTH-48 reviews.</t> </list></t> <t>ForAUTH48 reviews.</li> </ul> <t indent="0" pn="section-2.1-4">For submissions to the Independent Stream, we don't have aWorking Group.working group. We consider instead the progression of the individual draft until the adoption by theISEIndependent Submissions Editor (ISE) as the equivalent of the "Working Group" period, and the delay from adoption by the ISE until submission to the RFC Editor as the equivalent of the IETFdelay.</t> <t>Weprocessing time.</t> <t indent="0" pn="section-2.1-5">We measure thestaringstarting point of the process using the date of submission of the first draft listed on that RFC page in the IETFdatatracker.Datatracker. In mostcase,cases, this first draft is an individual draft that then resubmitted as aWorking Groupworking group draft, or maybe resubmitted with a new name as the draft was searching for a home in an IETFWorking Group,working group, or before deciding for submission on the Independent Stream.</t><t>The<t indent="0" pn="section-2.1-6">The IETFdatatrackerDatatracker entries for RFCs and drafts do not <em>always</em> listWorking Groupworking group events like Working Group Last Call. The only intermediate event that we list between the first draft and the submission to the IESG is theWorking Group Adoption. For that,working group adoption, for which we use the date of submission oftheversion 00 of the draft eventually published as RFC. We also usethe same definitionthat date (of submission of version 00) for drafts submitted to the Independent Stream.</t> </section> <section anchor="sample-selection"title="Selectingnumbered="true" toc="include" removeInRFC="false" pn="section-2.2"> <name slugifiedName="name-selecting-a-random-sample-o">Selecting a Random Sample ofRFCs"> <t>BasicRFCs</name> <t indent="0" pn="section-2.2-1">Basic production mechanisms could be evaluated by processing data from the IETFdatatracker,Datatracker, but subjective data requires manual assessment of results, which can betime consuming.time-consuming. Since our resources are limited, we will only perform this analysis for a small sample of RFCs, selected at random from the list of RFCs approved in 2018. Specifically, we will pick 20 RFC numbers at random between:</t><t><list style="symbols"> <t>RFC<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2.2-2"> <li pn="section-2.2-2.1">RFC 8307, published in January 2018,and</t> <t>RFCand</li> <li pn="section-2.2-2.2">RFC 8511, published December2018.</t> </list></t> <t>The2018.</li> </ul> <t indent="0" pn="section-2.2-3"> The list of 20 selected RFCs is: RFC 8411, RFC 8456, RFC 8446, RFC 8355, RFC 8441, RFC 8324, RFC 8377, RFC 8498, RFC 8479, RFC 8453, RFC 8429, RFC 8312, RFC 8492 , RFC 8378, RFC 8361, RFC 8472, RFC 8471, RFC 8466, RFC 8362, and RFC 8468.</t><t>When<t indent="0" pn="section-2.2-4">When evaluating delays and impact, we will compare the year 2018 to 2008 and 1998, 10 and 20 years ago. To drive this comparison, we pick 20 RFCs at random among those published in 2008, and another 20 among those published in 1998.</t><t>The<t indent="0" pn="section-2.2-5">The list of the 20 randomly selected RFCs from 2008 is: RFC 5227, RFC 5174, RFC 5172, RFC 5354, RFC 5195, RFC 5236, RFC 5348, RFC 5281, RFC 5186, RFC 5326, RFC 5277, RFC 5373, RFC 5404, RFC 5329, RFC 5283, RFC 5358, RFC 5142, RFC 5271, RFC 5349, and RFC 5301.</t><t>The<t indent="0" pn="section-2.2-6">The list of the 20 randomly selected RFCs from20081998 is: RFC 2431, RFC 2381, RFC 2387, RFC 2348, RFC 2391, RFC 2267, RFC 2312, RFC 2448, RFC 2374, RFC 2398, RFC 2283, RFC 2382, RFC 2289, RFC 2282, RFC 2404, RFC 2449, RFC 2317, RFC 2394, RFC 2297, and RFC 2323.</t> </section> <section numbered="true" removeInRFC="false" toc="include" pn="section-2.3"> <name slugifiedName="name-conventions-used-in-this-do">Conventions Used in This Document</name> <t indent="0" pn="section-2.3-1">The following abbreviations are used in the tables:</t> <dl spacing="compact" indent="6" newline="false" pn="section-2.3-2"> <dt pn="section-2.3-2.1">BCP</dt> <dd pn="section-2.3-2.2">Best Current Practice</dd> <dt pn="section-2.3-2.3">Exp</dt> <dd pn="section-2.3-2.4">Experimental</dd> <dt pn="section-2.3-2.5">Info</dt> <dd pn="section-2.3-2.6">Informational</dd> <dt pn="section-2.3-2.7">PS</dt> <dd pn="section-2.3-2.8">Proposed Standard</dd> <dt pn="section-2.3-2.9">DS</dt> <dd pn="section-2.3-2.10">Draft Standard [This maturity level was retired by RFC 6410.]</dd> </dl> <t indent="0" pn="section-2.3-3">In addition, Status is as defined in RFC 2026, and Stream is as defined in RFC 8729.</t> </section> </section> <section anchor="sample-rfc-analysis"title="Analysisnumbered="true" toc="include" removeInRFC="false" pn="section-3"> <name slugifiedName="name-analysis-of-20-selected-rfc">Analysis of 20 SelectedRFCs"> <t>WeRFCs</name> <t indent="0" pn="section-3-1">We review each of the RFCs listed in <xreftarget="sample-selection"/>target="sample-selection" format="default" sectionFormat="of" derivedContent="Section 2.2"/> for the year 2018, trying both to answer the known questions and to gather insight for furtheranalyzes.analyses. In many cases, the analysis of the data is complemented by direct feedback from the RFC authors.</t> <section anchor="section"title="8411"> <t>IANAnumbered="true" toc="include" removeInRFC="false" pn="section-3.1"> <name slugifiedName="name-rfc-8411">RFC 8411</name> <t indent="0" pn="section-3.1-1">"IANA Registration for the Cryptographic Algorithm Object IdentifierRangeRange" <xreftarget="RFC8411"/>:</t> <figure><artwork><![CDATA[ Informational, 5 pages 4 drafts (personal), first 2017-05-08. Last call announced 2017-10-09 IESG evaluation starts 2017-12-28 Approved 2018-02-26, draft 03 AUTH-48 2018-04-20 AUTH-48 complete 2018-07-17 Published 2018-08-06 IANA action: create table ]]></artwork></figure> <t>Thistarget="RFC8411" format="default" sectionFormat="of" derivedContent="RFC8411"/>:</t> <dl indent="20" spacing="compact" newline="false" pn="section-3.1-2"> <dt pn="section-3.1-2.1">Status (Length):</dt> <dd pn="section-3.1-2.2">Informational (5 pages)</dd> <dt pn="section-3.1-2.3">Overview:</dt> <dd pn="section-3.1-2.4">4 individual drafts</dd> <dt pn="section-3.1-2.5">First draft:</dt> <dd pn="section-3.1-2.6">2017-05-08</dd> <dt pn="section-3.1-2.7">Last Call start:</dt> <dd pn="section-3.1-2.8">2017-10-09</dd> <dt pn="section-3.1-2.9">IESG eval. start:</dt> <dd pn="section-3.1-2.10">2017-12-28</dd> <dt pn="section-3.1-2.11">IESG approved:</dt> <dd pn="section-3.1-2.12">2018-02-26 (draft 03)</dd> <dt pn="section-3.1-2.13">AUTH48 start:</dt> <dd pn="section-3.1-2.14">2018-04-20</dd> <dt pn="section-3.1-2.15">AUTH48 complete:</dt> <dd pn="section-3.1-2.16">2018-07-17</dd> <dt pn="section-3.1-2.17">Published:</dt> <dd pn="section-3.1-2.18">2018-08-06</dd> <dt pn="section-3.1-2.19">IANA action:</dt> <dd pn="section-3.1-2.20">create table</dd> </dl> <t indent="0" pn="section-3.1-3">This RFC was published from the individual draft, which was not resubmitted as aWorking Groupworking group draft.</t><t>The<t indent="0" pn="section-3.1-4">The draft underwent minor copyeditediting before publication.</t><t>Some<t indent="0" pn="section-3.1-5">Some but not all of the long delay inAUTH-48AUTH48 is due to clustering with <xreftarget="RFC8410"/>.target="RFC8410" format="default" sectionFormat="of" derivedContent="RFC8410"/>. MISSREFwas clearedstate concluded on 2018-05-09 and the document re-enteredAUTH-48AUTH48 at once.AUTH-48AUTH48 lasted over two months afterthat.</t> <t>Thethat. (For state definitions, see <eref brackets="angle" target="https://www.rfc-editor.org/about/queue/#state_def"/>.)</t> <t indent="0" pn="section-3.1-6">The time afterAUTH-48AUTH48 and before publication (3 weeks) partly overlaps with travel forIETF-102IETF 102 and is partly due to coordinating the cluster.</t> </section> <sectionanchor="section-1" title="8456"> <t>Benchmarkinganchor="sec-1" numbered="true" toc="include" removeInRFC="false" pn="section-3.2"> <name slugifiedName="name-rfc-8456">RFC 8456</name> <t indent="0" pn="section-3.2-1">"Benchmarking Methodology for Software-Defined Networking (SDN) ControllerPerformancePerformance" <xreftarget="RFC8456"/>:</t> <figure><artwork><![CDATA[ Informational, 64 pages 2 personal drafts,target="RFC8456" format="default" sectionFormat="of" derivedContent="RFC8456"/>:</t> <dl indent="20" spacing="compact" newline="false" pn="section-3.2-2"> <dt pn="section-3.2-2.1">Status (Length):</dt> <dd pn="section-3.2-2.2">Informational (64 pages)</dd> <dt pn="section-3.2-2.3">Overview:</dt> <dd pn="section-3.2-2.4">2 individual drafts; 9 WGdrafts, first 2015-03-23 WG adoption on 2015-10-18 Last call announced 2018-01-19 IESG evaluation starts 2018-02-27 IESG approved 2018-05-25 AUTH-48 2018-08-31 AUTH-48 complete 2018-10-16 Published 2018-10-30 ]]></artwork></figure> <t>Thedrafts</dd> <dt pn="section-3.2-2.5">First draft:</dt> <dd pn="section-3.2-2.6">2015-03-23</dd> <dt pn="section-3.2-2.7">WG adoption:</dt> <dd pn="section-3.2-2.8">2015-10-18</dd> <dt pn="section-3.2-2.9">Last Call start:</dt> <dd pn="section-3.2-2.10">2018-01-19</dd> <dt pn="section-3.2-2.11">IESG eval. start:</dt> <dd pn="section-3.2-2.12">2018-02-27</dd> <dt pn="section-3.2-2.13">IESG approved:</dt> <dd pn="section-3.2-2.14">2018-05-25</dd> <dt pn="section-3.2-2.15">AUTH48 start:</dt> <dd pn="section-3.2-2.16">2018-08-31</dd> <dt pn="section-3.2-2.17">AUTH48 complete:</dt> <dd pn="section-3.2-2.18">2018-10-16</dd> <dt pn="section-3.2-2.19">Published:</dt> <dd pn="section-3.2-2.20">2018-10-30</dd> </dl> <t indent="0" pn="section-3.2-3"> The draft underwentveryextensive copy editing, covering use of articles,turn of phrases, choice of vocabulary.syntax, and word choice. The changes are enough to cause pagination differences. The "diff" tool marks pretty much every page as changed. Some diagrams see change in protocol elements like message names.</t><t>According<t indent="0" pn="section-3.2-4">According to the author, the experience of producing thisdraftdocument mirrors a typical one in the Benchmarking Methodologies Working Group (BMWG). There were multiple authors in multiple time zones, which slowed down theAUTH-48AUTH48 process somewhat, although theAUTH-48AUTH48 delay of 46 days is only a bit longer than the average draft.</t><t>The<t indent="0" pn="section-3.2-5">The RFC was part of cluster with <xreftarget="RFC8455"/>.</t> <t>BMWGtarget="RFC8455" format="default" sectionFormat="of" derivedContent="RFC8455"/>.</t> <t indent="0" pn="section-3.2-6">BMWG publishesinformationalInformational RFCs centered around benchmarking, and the methodologies in RFC 8456 have been implemented in benchmarking products.</t> </section> <sectionanchor="section-2" title="8446"> <t>Theanchor="sec-2" numbered="true" toc="include" removeInRFC="false" pn="section-3.3"> <name slugifiedName="name-rfc-8446">RFC 8446</name> <t indent="0" pn="section-3.3-1">"The Transport Layer Security (TLS) Protocol Version1.31.3" <xreftarget="RFC8446"/>,target="RFC8446" format="default" sectionFormat="of" derivedContent="RFC8446"/>, as the title indicates, defines the new version of the TLS protocol. From the IETFdatatracker,Datatracker, we extract the following:</t><figure><artwork><![CDATA[ Proposed standard 160 pages 29<dl indent="20" spacing="compact" newline="false" pn="section-3.3-2"> <dt pn="section-3.3-2.1">Status (Length):</dt> <dd pn="section-3.3-2.2">Proposed Standard (160 pages)</dd> <dt pn="section-3.3-2.3">Overview:</dt> <dd pn="section-3.3-2.4">29 WGdrafts first 2014-04-17. Last call announced 2018-02-15 IESG evaluation starts 2018-03-02 Approved 2018-03-21, draft 28 AUTH-48 2018-06-14 AUTH-48 complete 2018-08-10 Published 2018-08-10 ]]></artwork></figure> <t>Thisdrafts</dd> <dt pn="section-3.3-2.5">First draft:</dt> <dd pn="section-3.3-2.6">2014-04-17</dd> <dt pn="section-3.3-2.7">Last Call start:</dt> <dd pn="section-3.3-2.8">2018-02-15</dd> <dt pn="section-3.3-2.9">IESG eval. start:</dt> <dd pn="section-3.3-2.10">2018-03-02</dd> <dt pn="section-3.3-2.11">IESG approved:</dt> <dd pn="section-3.3-2.12">2018-03-21 (draft 28)</dd> <dt pn="section-3.3-2.13">AUTH48 start:</dt> <dd pn="section-3.3-2.14">2018-06-14</dd> <dt pn="section-3.3-2.15">AUTH48 complete:</dt> <dd pn="section-3.3-2.16">2018-08-10</dd> <dt pn="section-3.3-2.17">Published:</dt> <dd pn="section-3.3-2.18">2018-08-10</dd> </dl> <t indent="0" pn="section-3.3-3">This draft started as a WG effort.</t><t>The<t indent="0" pn="section-3.3-4">The RFC was a major effort in the IETF. WorkingGroup membersgroup participants developed and tested several implementations. Researchers analyzed the specifications and performed formal verifications. Deployment tests outlined issues that caused extra work when the specification was almost ready.TheseThis complexity largely explains the time spent in theWorking Group.</t> <t>Comparingworking group.</t> <t indent="0" pn="section-3.3-5">Comparing the final draft to the published version, we find relatively light copy editing. It includes explaining acronyms on first use, clarifying some definitions standardizingpunctiationpunctuation and capitalization, and spelling out some numbers in text. This generally fall in the category of "style", although some of the clarifications go into message definitions. However, that simple analysis does not explain why theAUTH-48AUTH48 phase took almost two months.</t><t>This<t indent="0" pn="section-3.3-6">This document'sAUTH-48AUTH48 process was part of the"Github"GitHub experiment", which tried to usegithubGitHub pull requests to track theAUTH-48AUTH48 changes and review comments. TheRPCRFC Production Center (RPC) staff had to learn usingGithubGitHub for that process, and this required more work than the usual RFC.AuthorThe author and AD thoroughly reviewed each proposed edit, accepting some and rejecting some. The concern there was that any change in a complex specification might affect a protocol that was extensively reviewed in theWorking Group,working group, but of course these reviews added time to theAUTH-48AUTH48 delays.</t><t>There<t indent="0" pn="section-3.3-7">There are 21 implementations listed in the Wiki of the TLS 1.3 project <xreftarget="TLS13IMP"/>.target="TLS13IMP" format="default" sectionFormat="of" derivedContent="TLS13IMP"/>. It has been deployed on major browsers, and is already used in a large fraction of TLS connections.</t> </section> <sectionanchor="section-3" title="8355"> <t>Resiliencyanchor="sec-3" numbered="true" toc="include" removeInRFC="false" pn="section-3.4"> <name slugifiedName="name-rfc-8355">RFC 8355</name> <t indent="0" pn="section-3.4-1">"Resiliency Use Cases in Source Packet Routing in Networking (SPRING)NetworksNetworks" <xreftarget="RFC8355"/>target="RFC8355" format="default" sectionFormat="of" derivedContent="RFC8355"/> is aninformationalInformational RFC. It originated froma use casean informationaldraft thatuse-case draft; it was mostly used for the BOF creating the WG, and then to drive initialwork/evolutionswork and evolutions from the WG.</t><figure><artwork><![CDATA[ Informational, 13 pages. 2 personal drafts (personal), first 2014-01-31.<dl indent="20" spacing="compact" newline="false" pn="section-3.4-2"> <dt pn="section-3.4-2.1">Status (Length):</dt> <dd pn="section-3.4-2.2">Informational (13 pages)</dd> <dt pn="section-3.4-2.3">Overview:</dt> <dd pn="section-3.4-2.4">2 individual drafts; 13 WGdrafts. WG adoption on 2014-05-13 Last call announced 2017-04-20 IESG evaluation starts 2017-05-04, draft 09 Approved 2017-12-19, draft 12 AUTH-48 2018-03-12 AUTH-48 complete 2018-03-27 Published 2018-03-28 ]]></artwork></figure> <t>Minordrafts</dd> <dt pn="section-3.4-2.5">First draft:</dt> <dd pn="section-3.4-2.6">2014-01-31</dd> <dt pn="section-3.4-2.7">WG adoption:</dt> <dd pn="section-3.4-2.8">2014-05-13</dd> <dt pn="section-3.4-2.9">Last Call start:</dt> <dd pn="section-3.4-2.10">2017-04-20</dd> <dt pn="section-3.4-2.11">IESG eval. start:</dt> <dd pn="section-3.4-2.12">2017-05-04 (draft 09)</dd> <dt pn="section-3.4-2.13">IESG approved:</dt> <dd pn="section-3.4-2.14">2017-12-19 (draft 12)</dd> <dt pn="section-3.4-2.15">AUTH48 start:</dt> <dd pn="section-3.4-2.16">2018-03-12</dd> <dt pn="section-3.4-2.17">AUTH48 complete:</dt> <dd pn="section-3.4-2.18">2018-03-27</dd> <dt pn="section-3.4-2.19">Published:</dt> <dd pn="section-3.4-2.20">2018-03-28</dd> </dl> <t indent="0" pn="section-3.4-3">Minor set of copy edits, mostly for style.</t><t>No<t indent="0" pn="section-3.4-4">No implementation of the RFC itself, but the technology behind itsuch(such as Segment Routing(architecture RFC 8402,Architecture <xref target="RFC8402" format="default" sectionFormat="of" derivedContent="RFC8402"/> and TI-LFAdraft-ietf-rtgwg-segment-routing-ti-lfa)<xref target="I-D.ietf-rtgwg-segment-routing-ti-lfa" format="default" sectionFormat="of" derivedContent="TI-LFA"/>) is widely implemented and deployment is ongoing.</t><t>According<t indent="0" pn="section-3.4-5">According to participants in the discussion, the process of adoption of the source packet routing standards was very contentious. The establishment of consensus at both theWorking Groupworking group level and the IETF level was difficult andtime consuming.</t>time-consuming.</t> </section> <sectionanchor="section-4" title="8441"> <t>Bootstrappinganchor="sec-4" numbered="true" toc="include" removeInRFC="false" pn="section-3.5"> <name slugifiedName="name-rfc-8441">RFC 8441</name> <t indent="0" pn="section-3.5-1">"Bootstrapping WebSockets withHTTP/2HTTP/2" <xreftarget="RFC8441"/></t> <figure><artwork><![CDATA[ Proposed standard,target="RFC8441" format="default" sectionFormat="of" derivedContent="RFC8441"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.5-2"> <dt pn="section-3.5-2.1">Status (Length):</dt> <dd pn="section-3.5-2.2">Proposed Standard (8 pages)</dd> <dt pn="section-3.5-2.3">Overview:</dt> <dd pn="section-3.5-2.4">3 individual drafts; 8pages.WG drafts; Updates RFC6455. 3 personal drafts (personal), first 2017-10-15. 8 WG drafts. WG adoption on 2017-12-19 Last call announced 2018-05-07, draft 05 IESG evaluation starts 2018-05-29, draft 06 Approved 2018-06-07, draft 07 AUTH-48 2018-08-13 AUTH-48 complete 2018-09-15 Published 2018-09-21 IANA Action: table entries ]]></artwork></figure> <t>This6455</dd> <dt pn="section-3.5-2.5">First draft:</dt> <dd pn="section-3.5-2.6">2017-10-15</dd> <dt pn="section-3.5-2.7">WG adoption:</dt> <dd pn="section-3.5-2.8">2017-12-19</dd> <dt pn="section-3.5-2.9">Last Call start:</dt> <dd pn="section-3.5-2.10">2018-05-07 (draft 05)</dd> <dt pn="section-3.5-2.11">IESG eval. start:</dt> <dd pn="section-3.5-2.12">2018-05-29 (draft 06)</dd> <dt pn="section-3.5-2.13">IESG approved:</dt> <dd pn="section-3.5-2.14">2018-06-18 (draft 07)</dd> <dt pn="section-3.5-2.15">AUTH48 start:</dt> <dd pn="section-3.5-2.16">2018-08-13</dd> <dt pn="section-3.5-2.17">AUTH48 complete:</dt> <dd pn="section-3.5-2.18">2018-09-15</dd> <dt pn="section-3.5-2.19">Published:</dt> <dd pn="section-3.5-2.20">2018-09-18</dd> <dt pn="section-3.5-2.21">IANA action:</dt> <dd pn="section-3.5-2.22">table entries</dd> </dl> <t indent="0" pn="section-3.5-3">This RFC defines the support of WebSockets in HTTP/2, which is different from the mechanism defined for HTTP/1.1 in <xreftarget="RFC6455"/>.target="RFC6455" format="default" sectionFormat="of" derivedContent="RFC6455"/>. The process was relatively straightforward, involving the usual type of discussions, some on details and some on important points.</t><t>Comparing<t indent="0" pn="section-3.5-4">Comparing the final draft and published RFC shows a minor set of copyedit,edits, mostly for style. However, the author recalls a painful process. The RFC includes many charts and graphs that were very difficult to format correctly in the author's production process thatinvolveinvolved conversions from markdown to XML, and then from XML to text. The author had to get substantial help from the RFCeditor.</t> <t>ThereEditor.</t> <t indent="0" pn="section-3.5-5">There are several implementations, including Firefox and Chrome, making RFC 8441 a very successful specification.</t> </section> <section anchor="analyse-8324"title="8324"> <t>DNSnumbered="true" toc="include" removeInRFC="false" pn="section-3.6"> <name slugifiedName="name-rfc-8324">RFC 8324</name> <t indent="0" pn="section-3.6-1">"DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for AnotherLook?Look?" <xreftarget="RFC8324"/>.target="RFC8324" format="default" sectionFormat="of" derivedContent="RFC8324"/>. This is an opinion piece on DNS development, published on the Independent Stream.</t><figure><artwork><![CDATA[ Informational, 29 pages.<dl indent="20" spacing="compact" newline="false" pn="section-3.6-2"> <dt pn="section-3.6-2.1">Status (Length):</dt> <dd pn="section-3.6-2.2">Informational (29 pages)</dd> <dt pn="section-3.6-2.3">Overview:</dt> <dd pn="section-3.6-2.4">5 individual drafts; IndependentStream. 5 personal drafts (personal), first 2017-06-02. ISEStream</dd> <dt pn="section-3.6-2.5">First draft:</dt> <dd pn="section-3.6-2.6">2017-06-02</dd> <dt pn="section-3.6-2.7">ISE reviewstarted 2017-07-10, draft 03 IETFstart:</dt> <dd pn="section-3.6-2.8">2017-07-10 (draft 03)</dd> <dt pn="section-3.6-2.9">IETF conflict reviewand IESG review started 2017-10-29 Approved 2017-12-18, draft 04 AUTH-48 2018-01-29, draft 05 AUTH-48 complete 2018-02-26 Published 2018-02-27 ]]></artwork></figure> <t>Thisstart:</dt> <dd pn="section-3.6-2.10">2017-10-29</dd> <dt pn="section-3.6-2.11">Approved:</dt> <dd pn="section-3.6-2.12">2017-12-18 (draft 04)</dd> <dt pn="section-3.6-2.13">AUTH48 start:</dt> <dd pn="section-3.6-2.14">2018-01-29 (draft 05)</dd> <dt pn="section-3.6-2.15">AUTH48 complete:</dt> <dd pn="section-3.6-2.16">2018-02-26</dd> <dt pn="section-3.6-2.17">Published:</dt> <dd pn="section-3.6-2.18">2018-02-27</dd> </dl> <t indent="0" pn="section-3.6-3">This RFC took only 9 months from first draft to publication, which is the shortest in the 2018 sample set. In part, this is because the text was privately circulated and reviewed byISE designatedthe ISE's selected experts before the first draft was published. The nature of the document is another reason for the short delay. It is an opinionpiece,piece and does not require the same type of consensus building and reviewsthanas a protocol specification.</t><t>Comparing<t indent="0" pn="section-3.6-4">Comparing the final draft and the published version shows only minor copyedit,edits, mostly for style. According to the author,becausethis is because he knows how to write in RFCStylestyle with the result that his documents often need a minimum of editing. He also makes sure that the document on which the RFC Production Center starts working already has changes discussed and approved during Last Call and IESG reviewincorporatedincorporated, rather than expecting the Production Center to operate off of notes aboutchangedchanges to be made.</t> </section> <sectionanchor="section-5" title="8377"> <t>Transparentanchor="sec-5" numbered="true" toc="include" removeInRFC="false" pn="section-3.7"> <name slugifiedName="name-rfc-8377">RFC 8377</name> <t indent="0" pn="section-3.7-1">"Transparent Interconnection of Lots of Links (TRILL):Multi-TopologyMulti-Topology" <xreftarget="RFC8377"/></t> <figure><artwork><![CDATA[ Proposed standard, 20 pages. Updates RFC 6325, 7177. 3 personal drafts (personal), first 2013-09-03.target="RFC8377" format="default" sectionFormat="of" derivedContent="RFC8377"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.7-2"> <dt pn="section-3.7-2.1">Status (Length):</dt> <dd pn="section-3.7-2.2">Proposed Standard (20 pages)</dd> <dt pn="section-3.7-2.3">Overview:</dt> <dd pn="section-3.7-2.4">3 individual drafts; 7 WGdrafts. WG adoption on 2015-09-01 Last call announced 2018-02-19, draft 05 IESG evaluation starts 2018-03-02, draft 06 Approved 2018-03-12, draft 05 AUTH-48 2018-04-20, draft 06 AUTH-48 complete 2018-07-31 Published 2018-07-31 IANA Table, table entries ]]></artwork></figure> <t>Minordrafts; Updates RFCs 6325 and 7177</dd> <dt pn="section-3.7-2.5">First draft:</dt> <dd pn="section-3.7-2.6">2013-09-03</dd> <dt pn="section-3.7-2.7">WG adoption:</dt> <dd pn="section-3.7-2.8">2015-09-01</dd> <dt pn="section-3.7-2.9">Last Call start:</dt> <dd pn="section-3.7-2.10">2018-02-19 (draft 05)</dd> <dt pn="section-3.7-2.11">IESG eval. start:</dt> <dd pn="section-3.7-2.12">2018-03-06 (draft 05)</dd> <dt pn="section-3.7-2.13">IESG approved:</dt> <dd pn="section-3.7-2.14">2018-03-12 (draft 06)</dd> <dt pn="section-3.7-2.15">AUTH48 start:</dt> <dd pn="section-3.7-2.16">2018-04-20 (draft 06)</dd> <dt pn="section-3.7-2.17">AUTH48 complete:</dt> <dd pn="section-3.7-2.18">2018-07-31</dd> <dt pn="section-3.7-2.19">Published:</dt> <dd pn="section-3.7-2.20">2018-07-31</dd> <dt pn="section-3.7-2.21">IANA action:</dt> <dd pn="section-3.7-2.22">table entries</dd> </dl> <t indent="0" pn="section-3.7-3">Minor set of copy edits, mostly for style, also clarity.</t> </section> <sectionanchor="section-6" title="8498"> <t>Aanchor="sec-6" numbered="true" toc="include" removeInRFC="false" pn="section-3.8"> <name slugifiedName="name-rfc-8498">RFC 8498</name> <t indent="0" pn="section-3.8-1">"A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol(SIP)(SIP)" <xreftarget="RFC8498"/>.</t> <figure><artwork><![CDATA[ Informational, 15 pages. 5 personal drafts (personal), first 2016-03-21.target="RFC8498" format="default" sectionFormat="of" derivedContent="RFC8498"/>.</t> <dl indent="20" spacing="compact" newline="false" pn="section-3.8-2"> <dt pn="section-3.8-2.1">Status (Length):</dt> <dd pn="section-3.8-2.2">Informational (15 pages)</dd> <dt pn="section-3.8-2.3">Overview:</dt> <dd pn="section-3.8-2.4">5 individual drafts; 9 WGdrafts. WG adoption on 2017-05-15 Last call announced 2018-10-12, draft 05 IESG evaluation starts 2018-11-28, draft 07 Approved 2018-12-10, draft 08 AUTH-48 2019-01-28 AUTH-48 complete 2019-02-13 Published 2019-02-15 IANA Action, tabledrafts</dd> <dt pn="section-3.8-2.5">First draft:</dt> <dd pn="section-3.8-2.6">2016-03-21</dd> <dt pn="section-3.8-2.7">WG adoption:</dt> <dd pn="section-3.8-2.8">2017-05-15</dd> <dt pn="section-3.8-2.9">Last Call start:</dt> <dd pn="section-3.8-2.10">2018-10-12 (draft 05)</dd> <dt pn="section-3.8-2.11">IESG eval. start:</dt> <dd pn="section-3.8-2.12">2018-11-28 (draft 07)</dd> <dt pn="section-3.8-2.13">IESG approved:</dt> <dd pn="section-3.8-2.14">2018-12-11 (draft 08)</dd> <dt pn="section-3.8-2.15">AUTH48 start:</dt> <dd pn="section-3.8-2.16">2019-01-28</dd> <dt pn="section-3.8-2.17">AUTH48 complete:</dt> <dd pn="section-3.8-2.18">2019-02-13</dd> <dt pn="section-3.8-2.19">Published:</dt> <dd pn="section-3.8-2.20">2019-02-14</dd> <dt pn="section-3.8-2.21">IANA action:</dt> <dd pn="section-3.8-2.22">table rowsadded. ]]></artwork></figure> <t>Copy editadded.</dd> </dl> <t indent="0" pn="section-3.8-3">Copy edits for style, but also clarification of ambiguous sentences.</t> </section> <sectionanchor="section-7" title="8479"> <t>Storinganchor="sec-7" numbered="true" toc="include" removeInRFC="false" pn="section-3.9"> <name slugifiedName="name-rfc-8479">RFC 8479</name> <t indent="0" pn="section-3.9-1">"Storing Validation Parameters inPKCS#8PKCS#8" <xreftarget="RFC8479"/></t> <figure><artwork><![CDATA[ Informational, 8 pages.target="RFC8479" format="default" sectionFormat="of" derivedContent="RFC8479"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.9-2"> <dt pn="section-3.9-2.1">Status (Length):</dt> <dd pn="section-3.9-2.2">Informational (8 pages)</dd> <dt pn="section-3.9-2.3">Overview:</dt> <dd pn="section-3.9-2.4">5 individual drafts; IndependentStream. 5 personal drafts (personal), first 2017-08-08. ISEStream</dd> <dt pn="section-3.9-2.5">First draft:</dt> <dd pn="section-3.9-2.6">2017-08-08</dd> <dt pn="section-3.9-2.7">ISE reviewstarted 2018-12-10, draft 00 IETFstart:</dt> <dd pn="section-3.9-2.8">2018-12-10 (draft 00)</dd> <dt pn="section-3.9-2.9">IETF conflict reviewand IESG review started 2018-03-29 Approved 2018-08-20, draft 03 AUTH-48 2018-09-20, draft 04 AUTH-48 complete 2018-09-25 Published 2018-09-26 ]]></artwork></figure> <t>Thestart:</dt> <dd pn="section-3.9-2.10">2018-03-29</dd> <dt pn="section-3.9-2.11">Approved:</dt> <dd pn="section-3.9-2.12">2018-08-20 (draft 03)</dd> <dt pn="section-3.9-2.13">AUTH48 start:</dt> <dd pn="section-3.9-2.14">2018-09-20 (draft 04)</dd> <dt pn="section-3.9-2.15">AUTH48 complete:</dt> <dd pn="section-3.9-2.16">2018-09-25</dd> <dt pn="section-3.9-2.17">Published:</dt> <dd pn="section-3.9-2.18">2018-09-26</dd> </dl> <t indent="0" pn="section-3.9-3">The goal of the draft was to document what the gnutls implementation was using for storing provably generated RSA keys. This is a short RFC that was published relatively quickly, although discussion between the author, the IndependentSeries EditorSubmissions Editor, and the IESG lasted several months. In the initial conflict review,Thethe IESG asked the ISE to not publish this document before IETFWorking Groupsworking groups had an opportunity to pick up the work. The author met that requirement by a presentation to the SECDISPATCH WGinduring IETF 102. Since no WG was interested inpickuppicking up the work, the document progressed on the Independent Stream.</t><t>Very<t indent="0" pn="section-3.9-4">Very minor set of copyedit,edits, moving some references from normative to informative.</t><t>The<t indent="0" pn="section-3.9-5">The author is not aware of other implementations than gnutls relying on this RFC.</t> </section> <sectionanchor="section-8" title="8453"> <t>Frameworkanchor="sec-8" numbered="true" toc="include" removeInRFC="false" pn="section-3.10"> <name slugifiedName="name-rfc-8453">RFC 8453</name> <t indent="0" pn="section-3.10-1">"Framework for Abstraction and Control of TE Networks(ACTN)(ACTN)" <xreftarget="RFC8453"/></t> <figure><artwork><![CDATA[ Informational, 42 pages. 3 personal drafts, first 2015-06-15.target="RFC8453" format="default" sectionFormat="of" derivedContent="RFC8453"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.10-2"> <dt pn="section-3.10-2.1">Status (Length):</dt> <dd pn="section-3.10-2.2">Informational (42 pages)</dd> <dt pn="section-3.10-2.3">Overview:</dt> <dd pn="section-3.10-2.4">3 individual drafts; 16 WGdrafts. WG adoption on 2016-07-15 Out of WG 2018-01-26, draft 11 Expertdrafts</dd> <dt pn="section-3.10-2.5">First draft:</dt> <dd pn="section-3.10-2.6">2015-06-15</dd> <dt pn="section-3.10-2.7">WG adoption:</dt> <dd pn="section-3.10-2.8">2016-07-15</dd> <dt pn="section-3.10-2.9">Out of WG:</dt> <dd pn="section-3.10-2.10">2018-01-26 (draft 11)</dd> <dt pn="section-3.10-2.11">Expert reviewrequested, 2018-02-13 Last call announced 2018-04-16, draft 13 IESG evaluation starts 2018-05-16, draft 14 Approved 2018-06-01, draft 15 AUTH-48 2018-08-13 AUTH-48 complete 2018-08-20 Published 2018-08-20 IANA Action, tablerequested:</dt> <dd pn="section-3.10-2.12">2018-02-13</dd> <dt pn="section-3.10-2.13">Last Call start:</dt> <dd pn="section-3.10-2.14">2018-04-16 (draft 13)</dd> <dt pn="section-3.10-2.15">IESG eval. start:</dt> <dd pn="section-3.10-2.16">2018-05-16 (draft 14)</dd> <dt pn="section-3.10-2.17">IESG approved:</dt> <dd pn="section-3.10-2.18">2018-06-01 (draft 15)</dd> <dt pn="section-3.10-2.19">AUTH48 start:</dt> <dd pn="section-3.10-2.20">2018-08-13</dd> <dt pn="section-3.10-2.21">AUTH48 complete:</dt> <dd pn="section-3.10-2.22">2018-08-20</dd> <dt pn="section-3.10-2.23">Published:</dt> <dd pn="section-3.10-2.24">2018-08-23</dd> <dt pn="section-3.10-2.25">IANA action:</dt> <dd pn="section-3.10-2.26">table rowsadded. ]]></artwork></figure> <t>Minoradded.</dd> </dl> <t indent="0" pn="section-3.10-3">Minor copy editing.</t> </section> <sectionanchor="section-9" title="8429"> <t>Deprecateanchor="sec-9" numbered="true" toc="include" removeInRFC="false" pn="section-3.11"> <name slugifiedName="name-rfc-8429">RFC 8429</name> <t indent="0" pn="section-3.11-1">"Deprecate Triple-DES (3DES) and RC4 inKerberosKerberos" <xreftarget="RFC8429"/></t> <figure><artwork><![CDATA[ BCP, 10 pages. 6target="RFC8429" format="default" sectionFormat="of" derivedContent="RFC8429"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.11-2"> <dt pn="section-3.11-2.1">Status (Length):</dt> <dd pn="section-3.11-2.2">BCP (10 pages)</dd> <dt pn="section-3.11-2.3">Overview:</dt> <dd pn="section-3.11-2.4">6 WGdrafts, first 2017-05-01. Last call announced 2017-07-16, draft 03 IESG evaluation starts 2017-08-18, draft 04 Approved 2018-05-25, draft 05 AUTH-48 2018-07-24 AUTH-48 complete 2018-10-31 Published 2018-10-31 IANA Action, tabledrafts</dd> <dt pn="section-3.11-2.5">First draft:</dt> <dd pn="section-3.11-2.6">2017-05-01</dd> <dt pn="section-3.11-2.7">Last Call start:</dt> <dd pn="section-3.11-2.8">2017-07-16 (draft 03)</dd> <dt pn="section-3.11-2.9">IESG eval. start:</dt> <dd pn="section-3.11-2.10">2017-08-18 (draft 04)</dd> <dt pn="section-3.11-2.11">IESG approved:</dt> <dd pn="section-3.11-2.12">2018-05-25 (draft 05)</dd> <dt pn="section-3.11-2.13">AUTH48 start:</dt> <dd pn="section-3.11-2.14">2018-07-24</dd> <dt pn="section-3.11-2.15">AUTH48 complete:</dt> <dd pn="section-3.11-2.16">2018-10-31</dd> <dt pn="section-3.11-2.17">Published:</dt> <dd pn="section-3.11-2.18">2018-10-31</dd> <dt pn="section-3.11-2.19">IANA action:</dt> <dd pn="section-3.11-2.20">table rowsadded. ]]></artwork></figure> <t>Thisadded.</dd> </dl> <t indent="0" pn="section-3.11-3">This draft started as aWorking Groupworking group effort.</t><t>This<t indent="0" pn="section-3.11-4">This RFC recommendsto deprecatedeprecating two encryption algorithms that are now considered obsolete and possibly broken. The document was sent back to the WG after the firstlast call,Last Call, edited, and then there was a secondlast call.Last Call. The delay from first draft to Working Grouplast callLast Call was relatively short, but the number may be misleading. The initial draft was a replacement of a similar draft in the KITTEN Working Group, which stagnated for some time before the CURDLE Working Group took up the work. The deprecation of RC4 was somewhat contentious, but the WG had already debated this prior to the production of this draft, and the draft was not delayed by this debate.</t><t>Most<t indent="0" pn="section-3.11-5">Most of the 280 days between IETF LC and IESG approvalwaswere because the IESG had to talk about whether this document should obsolete RFC 4757 or move it tohistoric RFC 4757,Historic status, and no one was really actively pushing that discussion for a while.</t><t>The<t indent="0" pn="section-3.11-6">The 99 days inAUTH-48AUTH48 are mostly because one of the authors was a sitting AD, and those duties ended up taking precedence over reviewing this document.</t><t>Minor<t indent="0" pn="section-3.11-7">Minor copy editing, for style.</t><t>The<t indent="0" pn="section-3.11-8">The implementation of the draft would be the actual removal of support for 3DES and RC4 in major implementations. This is happening, but very slowly.</t> </section> <sectionanchor="section-10" title="8312"> <t>CUBICanchor="sec-10" numbered="true" toc="include" removeInRFC="false" pn="section-3.12"> <name slugifiedName="name-rfc-8312">RFC 8312</name> <t indent="0" pn="section-3.12-1">"CUBIC for Fast Long-DistanceNetworksNetworks" <xreftarget="RFC8312"/></t> <figure><artwork><![CDATA[ Informational, 18 pages. 2 personal drafts, first 2014-09-01.target="RFC8312" format="default" sectionFormat="of" derivedContent="RFC8312"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.12-2"> <dt pn="section-3.12-2.1">Status (Length):</dt> <dd pn="section-3.12-2.2">Informational (18 pages)</dd> <dt pn="section-3.12-2.3">Overview:</dt> <dd pn="section-3.12-2.4">2 individual drafts; 8 WGdrafts WG adoption on 2015-06-08 Last call announced 2017-09-18, draft 06 IESG evaluation starts 2017-11-14 Approved 2017-10-04, draft 07 AUTH-48 2018-01-08 AUTH-48 complete 2018-02-07 Published 2018-02-07 IANA Action, tabledrafts</dd> <dt pn="section-3.12-2.5">First draft:</dt> <dd pn="section-3.12-2.6">2014-09-01</dd> <dt pn="section-3.12-2.7">WG adoption:</dt> <dd pn="section-3.12-2.8">2015-06-08</dd> <dt pn="section-3.12-2.9">Last Call start:</dt> <dd pn="section-3.12-2.10">2017-09-18 (draft 06)</dd> <dt pn="section-3.12-2.11">IESG eval. start:</dt> <dd pn="section-3.12-2.12">2017-10-04</dd> <dt pn="section-3.12-2.13">IESG approved:</dt> <dd pn="section-3.12-2.14">2017-11-14 (draft 07)</dd> <dt pn="section-3.12-2.15">AUTH48 start:</dt> <dd pn="section-3.12-2.16">2018-01-08</dd> <dt pn="section-3.12-2.17">AUTH48 complete:</dt> <dd pn="section-3.12-2.18">2018-02-07</dd> <dt pn="section-3.12-2.19">Published:</dt> <dd pn="section-3.12-2.20">2018-02-07</dd> <dt pn="section-3.12-2.21">IANA action:</dt> <dd pn="section-3.12-2.22">table rowsadded. ]]></artwork></figure> <t>Minoradded.</dd> </dl> <t indent="0" pn="section-3.12-3">Minor copy editing, for style.</t><t>The<t indent="0" pn="section-3.12-4">The TCP congestion control algorithm Cubic wasdefinedfirst defined in 2005, was implemented in Linux soon after, and was implemented in major OSes after that. After some debates from 2015 to 2015, the TCPM Working Group adopted the draft, with a goal of documenting Cubic in theRFc series.RFC Series. According to the authors, this was not ahigh priorityhigh-priority effort, as Cubic was already implemented in multiple OSes and documented in research papers. At some point, only one of the authors was actively working on the draft.ThsThis may explain why another two years was spent progressing the draft after adoption by the WG.</t><t>The<t indent="0" pn="section-3.12-5">The RFC publication may or may not have triggered further implementations. On the other hand, several OSes picked up bug fixes from the draft and the RFC.</t> </section> <sectionanchor="section-11" title="8492"> <t>Secureanchor="sec-11" numbered="true" toc="include" removeInRFC="false" pn="section-3.13"> <name slugifiedName="name-rfc-8492">RFC 8492</name> <t indent="0" pn="section-3.13-1">"Secure Password Ciphersuites for Transport Layer Security(TLS)(TLS)" <xreftarget="RFC8492"/></t> <figure><artwork><![CDATA[ Informational, 40 pages. (Independent Stream) 10 personal drafts, first 2012-09-07.target="RFC8492" format="default" sectionFormat="of" derivedContent="RFC8492"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.13-2"> <dt pn="section-3.13-2.1">Status (Length):</dt> <dd pn="section-3.13-2.2">Informational (40 pages)</dd> <dt pn="section-3.13-2.3">Overview:</dt> <dd pn="section-3.13-2.4">10 individual drafts; 8 WGdrafts Targeted to ISE stream 2016-08-05 ISEdrafts; Independent Stream</dd> <dt pn="section-3.13-2.5">First draft:</dt> <dd pn="section-3.13-2.6">2012-09-07</dd> <dt pn="section-3.13-2.7">Targeted to ISE:</dt> <dd pn="section-3.13-2.8">2016-08-05</dd> <dt pn="section-3.13-2.9">ISE reviewstarted 2017-05-10, draft 01 IETFstart:</dt> <dd pn="section-3.13-2.10">2017-05-10 (draft 01)</dd> <dt pn="section-3.13-2.11">IETF conflict reviewand IESG review started 2017-09-04 Approved 2017-10-29, draft 04 AUTH-48 2018-10-19, draft 05 AUTH-48 complete 2019-02-19 Published 2019-02-21 IANA Action, tablestart:</dt> <dd pn="section-3.13-2.12">2017-09-04</dd> <dt pn="section-3.13-2.13">Approved:</dt> <dd pn="section-3.13-2.14">2017-10-29 (draft 02)</dd> <dt pn="section-3.13-2.15">AUTH48 start:</dt> <dd pn="section-3.13-2.16">2018-10-19 (draft 05)</dd> <dt pn="section-3.13-2.17">AUTH48 complete:</dt> <dd pn="section-3.13-2.18">2019-02-19</dd> <dt pn="section-3.13-2.19">Published:</dt> <dd pn="section-3.13-2.20">2019-02-21</dd> <dt pn="section-3.13-2.21">IANA action:</dt> <dd pn="section-3.13-2.22">table rowsadded. ]]></artwork></figure> <t>Thisadded.</dd> </dl> <t indent="0" pn="section-3.13-3">This RFC has a complex history. The first individual draft was submitted to the TLS Working Group on September 7, 2012. It progressed there, and was adopted by the WG after 3 revisions. There were then 8 revisions in the TLS WG, until the WG decided to not progress it. The draft was parked in 2013 by the WG chairs after failing to get consensus in WGlast call.Last Call. The AD finally pulled the plug in 2016, and the draft was then resubmitted to the ISE.</t><t>At<t indent="0" pn="section-3.13-4">At that point, the author was busy and was treating this RFC with a low priority because, in his words, it would not be a "real RFC". There were problems with the draft that only came up late. In particular, it had to wait for a change in registry policy that only came about with the publication of TLS 1.3, which caused the draft toonlybe published after RFC 8446, and also required adding references to TLS 1.3. The author also got a very late comment while inAUTH-48AUTH48 that caused somerewrite.rewriting. Finally, there was some IANA issue with the extension registry where a similar extension was added by someone else. The draft was changed to just use it.</t><t>Changes<t indent="0" pn="section-3.13-5">Changes inAUTH-48AUTH48 includeaddedadding a reference to TLS 1.3,copy-editingcopy editing for style, some added requirements, added paragraphs, and changes in algorithms specification.</t> </section> <sectionanchor="section-12" title="8378"> <t>Signal-Freeanchor="sec-12" numbered="true" toc="include" removeInRFC="false" pn="section-3.14"> <name slugifiedName="name-rfc-8378">RFC 8378</name> <t indent="0" pn="section-3.14-1">"Signal-Free Locator/ID Separation Protocol (LISP)MulticastMulticast" <xreftarget="RFC8378"/>target="RFC8378" format="default" sectionFormat="of" derivedContent="RFC8378"/> is anexperimentalExperimental RFC, defining how to implement Multicast in the LISP architecture.</t><figure><artwork><![CDATA[ Experimental, 21 pages. 5 personal drafts, first 2014-02-28.<dl indent="20" spacing="compact" newline="false" pn="section-3.14-2"> <dt pn="section-3.14-2.1">Status (Length):</dt> <dd pn="section-3.14-2.2">Experimental (21 pages)</dd> <dt pn="section-3.14-2.3">Overview:</dt> <dd pn="section-3.14-2.4">5 individual drafts; 10 WGdrafts WG adoption on 2015-12-21 Last call announced 2018-02-13, draft 07 IESG evaluation starts 2018-02-28, draft 08 Approved 2018-03-12, draft 09 AUTH-48 2018-04-23 AUTH-48 complete 2018-05-02 Published 2018-05-02 ]]></artwork></figure> <t>Preparingdrafts</dd> <dt pn="section-3.14-2.5">First draft:</dt> <dd pn="section-3.14-2.6">2014-02-28</dd> <dt pn="section-3.14-2.7">WG adoption:</dt> <dd pn="section-3.14-2.8">2015-12-21</dd> <dt pn="section-3.14-2.9">Last Call start:</dt> <dd pn="section-3.14-2.10">2018-02-13 (draft 07)</dd> <dt pn="section-3.14-2.11">IESG eval. start:</dt> <dd pn="section-3.14-2.12">2018-02-28 (draft 08)</dd> <dt pn="section-3.14-2.13">IESG approved:</dt> <dd pn="section-3.14-2.14">2018-03-12 (draft 09)</dd> <dt pn="section-3.14-2.15">AUTH48 start:</dt> <dd pn="section-3.14-2.16">2018-04-23</dd> <dt pn="section-3.14-2.17">AUTH48 complete:</dt> <dd pn="section-3.14-2.18">2018-05-02</dd> <dt pn="section-3.14-2.19">Published:</dt> <dd pn="section-3.14-2.20">2018-05-02</dd> </dl> <t indent="0" pn="section-3.14-3">Preparing the RFC took more than 4 years. According to the authors, they were notaggressiveaggressively pushing it and just let theWorking Groupworking group process decide to pace it. They also did implementations during that time.</t><t>Minor<t indent="0" pn="section-3.14-4">Minor copy editing, for style.</t><t>The<t indent="0" pn="section-3.14-5">The RFC was implemented by lispers.net andcisco,Cisco, and it was used in doing IPv6 multicast over IPv4 unicast/multicast at the Olympics in PyeungChang. The plan is to work on aproposedstandardProposed Standard once the experiment concludes.</t> </section> <sectionanchor="section-13" title="8361"> <t>Transparentanchor="sec-13" numbered="true" toc="include" removeInRFC="false" pn="section-3.15"> <name slugifiedName="name-rfc-8361">RFC 8361</name> <t indent="0" pn="section-3.15-1">"Transparent Interconnection of Lots of Links (TRILL): Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast (BUM)TrafficTraffic" <xreftarget="RFC8361"/></t> <figure><artwork><![CDATA[ Proposed Standard, 17 pages. 3 personal drafts, first 2013-11-12.target="RFC8361" format="default" sectionFormat="of" derivedContent="RFC8361"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.15-2"> <dt pn="section-3.15-2.1">Status (Length):</dt> <dd pn="section-3.15-2.2">Proposed Standard (17 pages)</dd> <dt pn="section-3.15-2.3">Overview:</dt> <dd pn="section-3.15-2.4">3 individual drafts; 14 WGdrafts WG adoption on 2014-12-16 Last call announced 2017-11-28, draft 10 IESG evaluation starts 2017-12-18, draft 11 Approved 2018-01-29, draft 13 AUTH-48 2018-03-09 AUTH-48 complete 2018-04-09 Published 2018-04-12 ]]></artwork></figure> <t>Accordingdrafts</dd> <dt pn="section-3.15-2.5">First draft:</dt> <dd pn="section-3.15-2.6">2013-11-12</dd> <dt pn="section-3.15-2.7">WG adoption:</dt> <dd pn="section-3.15-2.8">2014-12-16</dd> <dt pn="section-3.15-2.9">Last Call start:</dt> <dd pn="section-3.15-2.10">2017-11-28 (draft 10)</dd> <dt pn="section-3.15-2.11">IESG eval. start:</dt> <dd pn="section-3.15-2.12">2017-12-18 (draft 11)</dd> <dt pn="section-3.15-2.13">IESG approved:</dt> <dd pn="section-3.15-2.14">2018-01-29 (draft 13)</dd> <dt pn="section-3.15-2.15">AUTH48 start:</dt> <dd pn="section-3.15-2.16">2018-03-09</dd> <dt pn="section-3.15-2.17">AUTH48 complete:</dt> <dd pn="section-3.15-2.18">2018-04-09</dd> <dt pn="section-3.15-2.19">Published:</dt> <dd pn="section-3.15-2.20">2018-04-12</dd> </dl> <t indent="0" pn="section-3.15-3">According to the authors, the long delays in producing this RFCwaswere due to a slow uptake of the technology in the industry.</t><t>Minor<t indent="0" pn="section-3.15-4">Minor copy editing, for style.</t><t>There<t indent="0" pn="section-3.15-5">There was at least1one partial implementation.</t> </section> <sectionanchor="section-14" title="8472"> <t>Transportanchor="sec-14" numbered="true" toc="include" removeInRFC="false" pn="section-3.16"> <name slugifiedName="name-rfc-8472">RFC 8472</name> <t indent="0" pn="section-3.16-1">"Transport Layer Security (TLS) Extension for Token Binding ProtocolNegotiationNegotiation" <xreftarget="RFC8472"/></t> <figure><artwork><![CDATA[ Proposed Standard, 8 pages. 1 personal drafts, 2015-05-29.target="RFC8472" format="default" sectionFormat="of" derivedContent="RFC8472"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.16-2"> <dt pn="section-3.16-2.1">Status (Length):</dt> <dd pn="section-3.16-2.2">Proposed Standard (8 pages)</dd> <dt pn="section-3.16-2.3">Overview:</dt> <dd pn="section-3.16-2.4">1 individual draft; 15 WGdrafts WG adoption on 2015-09-11 Last call announced 2017-11-13, draft 10 IESG evaluation starts 2018-03-19 Approved 2018-07-20, draft 14 AUTH-48 2018-09-17 AUTH-48 complete 2018-09-25 Published 2018-10-08 ]]></artwork></figure> <t>Thisdrafts</dd> <dt pn="section-3.16-2.5">First draft:</dt> <dd pn="section-3.16-2.6">2015-05-29</dd> <dt pn="section-3.16-2.7">WG adoption:</dt> <dd pn="section-3.16-2.8">2015-09-11</dd> <dt pn="section-3.16-2.9">Last Call start:</dt> <dd pn="section-3.16-2.10">2017-11-13 (draft 10)</dd> <dt pn="section-3.16-2.11">IESG eval. start:</dt> <dd pn="section-3.16-2.12">2018-03-19</dd> <dt pn="section-3.16-2.13">IESG approved:</dt> <dd pn="section-3.16-2.14">2018-07-20 (draft 14)</dd> <dt pn="section-3.16-2.15">AUTH48 start:</dt> <dd pn="section-3.16-2.16">2018-09-17</dd> <dt pn="section-3.16-2.17">AUTH48 complete:</dt> <dd pn="section-3.16-2.18">2018-09-25</dd> <dt pn="section-3.16-2.19">Published:</dt> <dd pn="section-3.16-2.20">2018-10-08</dd> </dl> <t indent="0" pn="section-3.16-3">This is a pretty simple document, but it took over 3 years from individual draft to RFC. According to the authors,the biggest setbacks occurred at the start: it took a while to find a home for this draft. It was presented in the TLS WG (because it's a TLS extension) and UTA WG (because it has to do with applications using TLS). Then the ADs determined that a new WG was needed, so the authors had to work through the WG creation process, including running a BOF.</t><t>Minor<t indent="0" pn="section-3.16-4">Minor copy editing, for style, with the addition of a reference to TLS 1.3.</t><t>Perhaps<t indent="0" pn="section-3.16-5">Perhaps partially due to the delays, some of the implementers lost interest in supporting this RFC.</t> </section> <sectionanchor="section-15" title="8471"> <t>Theanchor="sec-15" numbered="true" toc="include" removeInRFC="false" pn="section-3.17"> <name slugifiedName="name-rfc-8471">RFC 8471</name> <t indent="0" pn="section-3.17-1">"The Token Binding Protocol Version1.01.0" <xreftarget="RFC8471"/></t> <figure><artwork><![CDATA[ Proposed Standard, 18 pages. 1 personal drafts, 2014-10-13.target="RFC8471" format="default" sectionFormat="of" derivedContent="RFC8471"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.17-2"> <dt pn="section-3.17-2.1">Status (Length):</dt> <dd pn="section-3.17-2.2">Proposed Standard (18 pages)</dd> <dt pn="section-3.17-2.3">Overview:</dt> <dd pn="section-3.17-2.4">1 individual draft; 19 WGdrafts WG adoption on 2015-03-15 Last call announced 2017-11-13, draft 16 IESG evaluation starts 2018-03-19 Approved 2018-07-20, draft 19 AUTH-48 2018-09-17 AUTH-48 complete 2018-09-25 Published 2018-10-08 ]]></artwork></figure> <t>Presentation ofdrafts</dd> <dt pn="section-3.17-2.5">First draft:</dt> <dd pn="section-3.17-2.6">2014-10-13</dd> <dt pn="section-3.17-2.7">WG adoption:</dt> <dd pn="section-3.17-2.8">2015-03-15</dd> <dt pn="section-3.17-2.9">Last Call start:</dt> <dd pn="section-3.17-2.10">2017-11-13 (draft 16)</dd> <dt pn="section-3.17-2.11">IESG eval. start:</dt> <dd pn="section-3.17-2.12">2018-03-19</dd> <dt pn="section-3.17-2.13">IESG approved:</dt> <dd pn="section-3.17-2.14">2018-07-20 (draft 19)</dd> <dt pn="section-3.17-2.15">AUTH48 start:</dt> <dd pn="section-3.17-2.16">2018-09-17</dd> <dt pn="section-3.17-2.17">AUTH48 complete:</dt> <dd pn="section-3.17-2.18">2018-09-25</dd> <dt pn="section-3.17-2.19">Published:</dt> <dd pn="section-3.17-2.20">2018-10-08</dd> </dl> <t indent="0" pn="section-3.17-3">This document presents a Token Binding Protocol for TLS. We can notice adelayperiod of 5 months before adoption of the draft by the WG. That explains in part the overalldelaytime of almost 4 years from first draft topublication.</t> <t>Minorpublication. </t> <t indent="0" pn="section-3.17-4">Minor copy editing, for style.</t><t>The<t indent="0" pn="section-3.17-5">The web referencesindicatesindicate adoption in multiple development projects.</t> </section> <sectionanchor="section-16" title="8466"> <t>Aanchor="sec-16" numbered="true" toc="include" removeInRFC="false" pn="section-3.18"> <name slugifiedName="name-rfc-8466">RFC 8466</name> <t indent="0" pn="section-3.18-1">"A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) ServiceDeliveryDelivery" <xreftarget="RFC8466"/></t> <figure><artwork><![CDATA[ Proposed Standard, 158 pages. 5 personal drafts, first 2016-09-01.target="RFC8466" format="default" sectionFormat="of" derivedContent="RFC8466"/></t> <dl indent="20" spacing="compact" newline="false" pn="section-3.18-2"> <dt pn="section-3.18-2.1">Status (Length):</dt> <dd pn="section-3.18-2.2">Proposed Standard (158 pages)</dd> <dt pn="section-3.18-2.3">Overview:</dt> <dd pn="section-3.18-2.4">5 individual drafts; 11 WGdrafts WG adoption on 2017-02-26 Last call announced 2018-02-21, draft 07 IESG evaluation starts 2018-03-14, draft 08 Approved 2018-06-25, draft 10 AUTH-48 2018-09-17 AUTH-48 complete 2018-10-09 Published 2018-10-12 ]]></artwork></figure> <t>Copydrafts</dd> <dt pn="section-3.18-2.5">First draft:</dt> <dd pn="section-3.18-2.6">2016-09-01</dd> <dt pn="section-3.18-2.7">WG adoption:</dt> <dd pn="section-3.18-2.8">2017-02-26</dd> <dt pn="section-3.18-2.9">Last Call start:</dt> <dd pn="section-3.18-2.10">2018-02-21 (draft 07)</dd> <dt pn="section-3.18-2.11">IESG eval. start:</dt> <dd pn="section-3.18-2.12">2018-03-14 (draft 08)</dd> <dt pn="section-3.18-2.13">IESG approved:</dt> <dd pn="section-3.18-2.14">2018-06-25 (draft 10)</dd> <dt pn="section-3.18-2.15">AUTH48 start:</dt> <dd pn="section-3.18-2.16">2018-09-17</dd> <dt pn="section-3.18-2.17">AUTH48 complete:</dt> <dd pn="section-3.18-2.18">2018-10-09</dd> <dt pn="section-3.18-2.19">Published:</dt> <dd pn="section-3.18-2.20">2018-10-12</dd> </dl> <t indent="0" pn="section-3.18-3">Copy editing for style and clarity, with also corrections to theyangYANG model.</t> </section> <sectionanchor="section-17" title="8362"> <t>OSPFv3anchor="sec-17" numbered="true" toc="include" removeInRFC="false" pn="section-3.19"> <name slugifiedName="name-rfc-8362">RFC 8362</name> <t indent="0" pn="section-3.19-1">"OSPFv3 Link State Advertisement (LSA)ExtensibilityExtensibility" <xreftarget="RFC8362"/>target="RFC8362" format="default" sectionFormat="of" derivedContent="RFC8362"/> is a major extension to the OSPF protocol. It makes OSPFv3 fully extensible.</t><figure><artwork><![CDATA[ Proposed Standard, 33 pages. 4 personal drafts, first 2013-02-17.<dl indent="20" spacing="compact" newline="false" pn="section-3.19-2"> <dt pn="section-3.19-2.1">Status (Length):</dt> <dd pn="section-3.19-2.2">Proposed Standard (33 pages)</dd> <dt pn="section-3.19-2.3">Overview:</dt> <dd pn="section-3.19-2.4">4 individual drafts; 24 WGdrafts WG adoption on 2013-10-15 Last call announced 2017-12-19, draft 19 IESG evaluation starts 2018-01-18, draft 20 Approved 2018-01-29, draft 23 AUTH-48 2018-03-19 AUTH-48 complete 2018-03-30 Published 2018-04-03 ]]></artwork></figure> <t>Thedrafts</dd> <dt pn="section-3.19-2.5">First draft:</dt> <dd pn="section-3.19-2.6">2013-02-17</dd> <dt pn="section-3.19-2.7">WG adoption:</dt> <dd pn="section-3.19-2.8">2013-10-15</dd> <dt pn="section-3.19-2.9">Last Call start:</dt> <dd pn="section-3.19-2.10">2017-12-19 (draft 19)</dd> <dt pn="section-3.19-2.11">IESG eval. start:</dt> <dd pn="section-3.19-2.12">2018-01-18 (draft 20)</dd> <dt pn="section-3.19-2.13">IESG approved:</dt> <dd pn="section-3.19-2.14">2018-01-29 (draft 23)</dd> <dt pn="section-3.19-2.15">AUTH48 start:</dt> <dd pn="section-3.19-2.16">2018-03-19</dd> <dt pn="section-3.19-2.17">AUTH48 complete:</dt> <dd pn="section-3.19-2.18">2018-03-30</dd> <dt pn="section-3.19-2.19">Published:</dt> <dd pn="section-3.19-2.20">2018-04-03</dd> </dl> <t indent="0" pn="section-3.19-3">The specification was first submitted asa personalan individual draft in the IPv6 WG, then moved to the OSPF WG. The long delay of producing this RFC is due to the complexity of the problem, and the need to wait for implementations. It is a very important change to OSPF that makes OSPFv3 fully extensible. Since it was a non-backward compatible change, the developers started out with some very complex migration scenarios but ended up with either legacy or extended OSPFv3 LSAs within an OSPFv3 routing domain. The initial attempts to have a hybrid mode of operation with both legacy and extended LSAs also delayed implementation due to the complexity.</t><t>Copy<t indent="0" pn="section-3.19-4">Copy editing for style and clarity.</t><t>This<t indent="0" pn="section-3.19-5">This specification either was or will be implemented by all the router vendors.</t> </section> <sectionanchor="section-18" title="8468"> <t>IPv4,anchor="sec-18" numbered="true" toc="include" removeInRFC="false" pn="section-3.20"> <name slugifiedName="name-rfc-8468">RFC 8468</name> <t indent="0" pn="section-3.20-1">"IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics (IPPM)FrameworkFramework" <xreftarget="RFC8468"/>.</t> <figure><artwork><![CDATA[ Informational, 15 pages. 3 personal drafts, first 2015-08-06.target="RFC8468" format="default" sectionFormat="of" derivedContent="RFC8468"/>.</t> <dl indent="20" spacing="compact" newline="false" pn="section-3.20-2"> <dt pn="section-3.20-2.1">Status (Length):</dt> <dd pn="section-3.20-2.2">Informational (15 pages)</dd> <dt pn="section-3.20-2.3">Overview:</dt> <dd pn="section-3.20-2.4">3 individual drafts; 7 WGdrafts WG adoption on 2016-07-04 Last call announced 2018-04-11, draft 04 IESG evaluation starts 2018-05-24, draft 05 Approved 2018-07-10, draft 06 AUTH-48 2018-09-13 AUTH-48 complete 2018-11-05 Published 2018-11-14 ]]></artwork></figure> <t>RFC8468drafts</dd> <dt pn="section-3.20-2.5">First draft:</dt> <dd pn="section-3.20-2.6">2015-08-06</dd> <dt pn="section-3.20-2.7">WG adoption:</dt> <dd pn="section-3.20-2.8">2016-07-04</dd> <dt pn="section-3.20-2.9">Last Call start:</dt> <dd pn="section-3.20-2.10">2018-04-11 (draft 04)</dd> <dt pn="section-3.20-2.11">IESG eval. start:</dt> <dd pn="section-3.20-2.12">2018-05-24 (draft 05)</dd> <dt pn="section-3.20-2.13">IESG approved:</dt> <dd pn="section-3.20-2.14">2018-07-10 (draft 06)</dd> <dt pn="section-3.20-2.15">AUTH48 start:</dt> <dd pn="section-3.20-2.16">2018-09-13</dd> <dt pn="section-3.20-2.17">AUTH48 complete:</dt> <dd pn="section-3.20-2.18">2018-11-05</dd> <dt pn="section-3.20-2.19">Published:</dt> <dd pn="section-3.20-2.20">2018-11-14</dd> </dl> <t indent="0" pn="section-3.20-3">RFC 8468 was somehow special in that there was not a technicalreason/interestreason or interest that triggered it, but rather a formal requirement. While writingRFC7312RFC 7312, the IP Performance Metrics (IPPM) Working Group(IPPM)realized that RFC 2330, the IP Performance Metrics Framework supported IPv4 only and explicitly excluded support for IPv6. Nevertheless, people used the metrics that were defined on top of RFC 2330 (and, therefore, IPv4 only) for IPv6, too. Although the IPPM WG agreed that the work was needed, the interest of IPPM attendees in progressing (and reading/reviewing) the IPv6 draft was limited. Resolving the IPv6 technical part wasstraight-forward,straightforward, but subsequently some people asked for a broader scope (topics like header compression,6lo, etc.)6LoWPAN, etc.), and it took some time to figure out and later on convince people that these topics are out of scope. The group also had to resolve contentious topics, forexampleexample, how to measure the processing of IPv6 extension headers, which is sometimesnon-standard.</t> <t>The AUTH-48 delaynonstandard.</t> <t indent="0" pn="section-3.20-4">The time in AUTH48 state for thisdraftdocument was longer than average. According to the authors, the main reasons include:</t><t><list style="symbols"> <t>Work-load<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.20-5"> <li pn="section-3.20-5.1">Workload and travel caused bybusy-work-periodsbusy work periods of allco-authors</t> <t>Timecoauthors</li> <li pn="section-3.20-5.2">Time zone difference betweenco-authorscoauthors and editor (at least US, Europe, and India, not consideringtravel)</t> <t>Editor proposingtravel)</li> <li pn="section-3.20-5.3"> RFC Production Center proposed andcommittingcommitted some unacceptable modifications that needed to bereverted</t> <t>Lengthyreverted </li> <li pn="section-3.20-5.4">Lengthy discussions on a new document title (required high effort and took a long time, in particular reaching consensus betweenco-authorscoauthors and editor was time-consuming and involved theAD)</t> <t>EditorAD)</li> <li pn="section-3.20-5.5">RFC Production Center correctlyidentifyingidentified some nits (obsoleted personal websites ofco-authors)coauthors) andco-authorscoauthors attempting to fixthem.</t> </list></t> <t>Thethem.</li> </ul> <t indent="0" pn="section-3.20-6">The differences between the final draft and thepublishpublished RFC show copy editing for style and clarity, but do not account for the back and forth between authors and editors mentioned by the authors.</t> </section> </section> <section anchor="process-analysis"title="Analysisnumbered="true" toc="include" removeInRFC="false" pn="section-4"> <name slugifiedName="name-analysis-of-process-and-del">Analysis of Process andDelays"> <t>WeDelays</name> <t indent="0" pn="section-4-1">We examine the 20 RFCs in the sample, measuring various characteristics such as delay and citation counts, in an attempt to identify patterns in the IETF processes.</t> <section anchor="first-draft-to-rfc-delays"title="Firstnumbered="true" toc="include" removeInRFC="false" pn="section-4.1"> <name slugifiedName="name-delays-from-first-draft-to-">Delays from First Draft toRFC Delays"> <t>WeRFC</name> <t indent="0" pn="section-4.1-1">We look at the distribution of delays between the submission of the first draft and the publication of the RFC, using the threebigmilestones defined in <xreftarget="milestones"/>:target="milestones" format="default" sectionFormat="of" derivedContent="Section 2.1"/>: processing time in theWorking Group,working group, IETF processing time, andpublication delay.RFC production time. The following table shows thedelaysnumber of days in each phase for the 20 RFCs in the sample:</t><texttable> <ttcol align='right'>RFC</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Pages</ttcol> <ttcol align='right'>Overall</ttcol> <ttcol align='right'>WG</ttcol> <ttcol align='right'>IETF</ttcol> <ttcol align='right'>Edit</ttcol> <c>8411</c> <c>Info</c> <c>5</c> <c>455</c> <c>154</c> <c>140</c> <c>161</c> <c>8456</c> <c>Info</c> <c>64</c> <c>1317</c> <c>1033</c> <c>126</c> <c>158</c> <c>8446</c> <c>PS</c> <c>160</c> <c>1576</c> <c>1400</c> <c>34</c> <c>142</c> <c>8355</c> <c>Info</c> <c>13</c> <c>1517</c> <c>1175</c> <c>243</c> <c>99</c> <c>8441</c> <c>PS</c> <c>8</c> <c>341</c> <c>204</c> <c>31</c> <c>106</c> <c>8324</c> <c>ISE</c> <c>29</c> <c>270</c> <c>38</c> <c>161</c> <c>71</c> <c>8377</c> <c>PS</c> <c>8</c> <c>1792</c> <c>1630</c> <c>21</c> <c>141</c> <c>8498</c> <c>Info</c> <c>15</c> <c>1061</c> <c>935</c> <c>59</c> <c>67</c> <c>8479</c> <c>ISE</c> <c>8</c> <c>414</c> <c>233</c> <c>144</c> <c>37</c> <c>8453</c> <c>Info</c> <c>42</c> <c>1162</c> <c>1036</c> <c>46</c> <c>80</c> <c>8429</c> <c>BCP</c> <c>10</c> <c>548</c> <c>76</c> <c>313</c> <c>159</c> <c>8312</c> <c>Info</c> <c>18</c> <c>1255</c> <c>1113</c> <c>16</c> <c>126</c> <c>8492</c> <c>ISE</c> <c>40</c> <c>2358</c> <c>1706</c> <c>172</c> <c>480</c> <c>8378</c> <c>Exp</c> <c>21</c> <c>1524</c> <c>1446</c> <c>27</c> <c>51</c> <c>8361</c> <c>PS</c> <c>17</c> <c>1612</c> <c>1477</c> <c>62</c> <c>73</c> <c>8472</c> <c>PS</c> <c>8</c> <c>1228</c> <c>899</c> <c>249</c> <c>80</c> <c>8471</c> <c>PS</c> <c>18</c> <c>1228</c> <c>899</c> <c>249</c> <c>80</c> <c>8466</c> <c>PS</c> <c>158</c> <c>771</c> <c>538</c> <c>124</c> <c>109</c> <c>8362</c> <c>PS</c> <c>33</c> <c>1871</c> <c>1766</c> <c>41</c> <c>64</c> <c>8468</c> <c>Info</c> <c>15</c> <c>1196</c> <c>979</c> <c>90</c> <c>127</c> <c> </c> <c>average</c> <c>35</c> <c>1186</c> <c>948</c> <c>117</c> <c>121</c> <c> </c> <c>average(not ISE)</c> <c>36</c> <c>1217</c> <c>999</c> <c>110</c> <c>107</c> </texttable> <t>The<table align="center" pn="table-1"> <thead> <tr> <th align="right" colspan="1" rowspan="1">RFC</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Pages</th> <th align="right" colspan="1" rowspan="1">Overall</th> <th align="right" colspan="1" rowspan="1">WG</th> <th align="right" colspan="1" rowspan="1">IETF</th> <th align="right" colspan="1" rowspan="1">Edit</th> </tr> </thead> <tbody> <tr> <td align="right" colspan="1" rowspan="1">8411</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">455</td> <td align="right" colspan="1" rowspan="1">154</td> <td align="right" colspan="1" rowspan="1">140</td> <td align="right" colspan="1" rowspan="1">161</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8456</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">64</td> <td align="right" colspan="1" rowspan="1">1317</td> <td align="right" colspan="1" rowspan="1">1033</td> <td align="right" colspan="1" rowspan="1">126</td> <td align="right" colspan="1" rowspan="1">158</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8446</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">160</td> <td align="right" colspan="1" rowspan="1">1576</td> <td align="right" colspan="1" rowspan="1">1400</td> <td align="right" colspan="1" rowspan="1">34</td> <td align="right" colspan="1" rowspan="1">142</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8355</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">13</td> <td align="right" colspan="1" rowspan="1">1517</td> <td align="right" colspan="1" rowspan="1">1175</td> <td align="right" colspan="1" rowspan="1">243</td> <td align="right" colspan="1" rowspan="1">99</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8441</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">327</td> <td align="right" colspan="1" rowspan="1">204</td> <td align="right" colspan="1" rowspan="1">31</td> <td align="right" colspan="1" rowspan="1">92</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8324</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">29</td> <td align="right" colspan="1" rowspan="1">270</td> <td align="right" colspan="1" rowspan="1">38</td> <td align="right" colspan="1" rowspan="1">161</td> <td align="right" colspan="1" rowspan="1">71</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8377</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">1792</td> <td align="right" colspan="1" rowspan="1">1630</td> <td align="right" colspan="1" rowspan="1">21</td> <td align="right" colspan="1" rowspan="1">141</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8498</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">15</td> <td align="right" colspan="1" rowspan="1">1059</td> <td align="right" colspan="1" rowspan="1">935</td> <td align="right" colspan="1" rowspan="1">59</td> <td align="right" colspan="1" rowspan="1">65</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8479</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">414</td> <td align="right" colspan="1" rowspan="1">233</td> <td align="right" colspan="1" rowspan="1">144</td> <td align="right" colspan="1" rowspan="1">37</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8453</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">42</td> <td align="right" colspan="1" rowspan="1">1165</td> <td align="right" colspan="1" rowspan="1">1036</td> <td align="right" colspan="1" rowspan="1">46</td> <td align="right" colspan="1" rowspan="1">83</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8429</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">10</td> <td align="right" colspan="1" rowspan="1">548</td> <td align="right" colspan="1" rowspan="1">76</td> <td align="right" colspan="1" rowspan="1">313</td> <td align="right" colspan="1" rowspan="1">159</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8312</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">18</td> <td align="right" colspan="1" rowspan="1">1214</td> <td align="right" colspan="1" rowspan="1">1113</td> <td align="right" colspan="1" rowspan="1">16</td> <td align="right" colspan="1" rowspan="1">85</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8492</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">40</td> <td align="right" colspan="1" rowspan="1">2358</td> <td align="right" colspan="1" rowspan="1">1706</td> <td align="right" colspan="1" rowspan="1">172</td> <td align="right" colspan="1" rowspan="1">480</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8378</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">21</td> <td align="right" colspan="1" rowspan="1">1524</td> <td align="right" colspan="1" rowspan="1">1446</td> <td align="right" colspan="1" rowspan="1">27</td> <td align="right" colspan="1" rowspan="1">51</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8361</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">17</td> <td align="right" colspan="1" rowspan="1">1612</td> <td align="right" colspan="1" rowspan="1">1477</td> <td align="right" colspan="1" rowspan="1">62</td> <td align="right" colspan="1" rowspan="1">73</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8472</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">1228</td> <td align="right" colspan="1" rowspan="1">899</td> <td align="right" colspan="1" rowspan="1">249</td> <td align="right" colspan="1" rowspan="1">80</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8471</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">18</td> <td align="right" colspan="1" rowspan="1">1228</td> <td align="right" colspan="1" rowspan="1">899</td> <td align="right" colspan="1" rowspan="1">249</td> <td align="right" colspan="1" rowspan="1">80</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8466</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">158</td> <td align="right" colspan="1" rowspan="1">771</td> <td align="right" colspan="1" rowspan="1">538</td> <td align="right" colspan="1" rowspan="1">124</td> <td align="right" colspan="1" rowspan="1">109</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8362</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">33</td> <td align="right" colspan="1" rowspan="1">1871</td> <td align="right" colspan="1" rowspan="1">1766</td> <td align="right" colspan="1" rowspan="1">41</td> <td align="right" colspan="1" rowspan="1">64</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8468</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">15</td> <td align="right" colspan="1" rowspan="1">1196</td> <td align="right" colspan="1" rowspan="1">979</td> <td align="right" colspan="1" rowspan="1">90</td> <td align="right" colspan="1" rowspan="1">127</td> </tr> <tr> <td colspan="2" align="left" rowspan="1">average</td> <td align="right" colspan="1" rowspan="1">35</td> <td align="right" colspan="1" rowspan="1">1172</td> <td align="right" colspan="1" rowspan="1">948</td> <td align="right" colspan="1" rowspan="1">117</td> <td align="right" colspan="1" rowspan="1">118</td> </tr> <tr> <td colspan="2" align="left" rowspan="1">average (not ISE)</td> <td align="right" colspan="1" rowspan="1">36</td> <td align="right" colspan="1" rowspan="1">1200</td> <td align="right" colspan="1" rowspan="1">999</td> <td align="right" colspan="1" rowspan="1">110</td> <td align="right" colspan="1" rowspan="1">104</td> </tr> </tbody> </table> <t indent="0" pn="section-4.1-3">The average delay from first draft to publication is about 3 years and 3 months, but this varies widely. Excluding the RFCs from the IndependentStream submissions,Stream, the average delay from start to finish is 3 years and 4 months, of which on average 2 years and 9 months are spent getting consensus in theWorking Group,working group, and 3 to 4 months each for IETF consensus and for RFC production.</t><t>The<t indent="0" pn="section-4.1-4">The longest delay is found for <xreftarget="RFC8492"/>,target="RFC8492" format="default" sectionFormat="of" derivedContent="RFC8492"/>, 6.5 years from start to finish. This is however a very specialcase,case -- a draft that was prepared for the TLS Working Group and failed to reach consensus. After that, it was resubmitted to the ISE, and incurred atypical production delays.</t><t>On<t indent="0" pn="section-4.1-5">On average, we see that 80% of the delay is incurred in WG processing, 10% in IETF review, and 10% for edition and publication.</t><t>For<t indent="0" pn="section-4.1-6">For IETFstreamStream RFCs, it appears that the delays forinformationalInformational documents are slightly shorter than those for protocol specifications, maybe six months shorter on average. However, there are lots of differences between individual documents. The delays range from less than a year to more than 5 years for protocol specifications, and from a year and 3 months to a bit more than 4 years forinformationalInformational documents.</t><t>We<t indent="0" pn="section-4.1-7">We can compare the delays in the 2018 samples to those observed 10 years ago and 20 years before:</t><texttable> <ttcol align='left'>RFC (2008)</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Pages</ttcol> <ttcol align='right'>Delay</ttcol> <c>5326</c> <c>Exp</c> <c>54</c> <c>1584</c> <c>5348</c> <c>PS</c> <c>58</c> <c>823</c> <c>5281</c> <c>Info</c> <c>51</c> <c>1308</c> <c>5354</c> <c>Exp</c> <c>23</c> <c>2315</c> <c>5227</c> <c>PS</c> <c>21</c> <c>2434</c> <c>5329</c> <c>PS</c> <c>12</c> <c>1980</c> <c>5277</c> <c>PS</c> <c>35</c> <c>912</c> <c>5236</c> <c>ISE</c> <c>26</c> <c>1947</c> <c>5358</c> <c>BCP</c> <c>7</c> <c>884</c> <c>5271</c> <c>Info</c> <c>22</c> <c>1066</c> <c>5195</c> <c>PS</c> <c>10</c> <c>974</c> <c>5283</c> <c>PS</c> <c>12</c> <c>1096</c> <c>5186</c> <c>Info</c> <c>6</c> <c>2253</c> <c>5142</c> <c>PS</c> <c>13</c> <c>1005</c> <c>5373</c> <c>PS</c> <c>24</c> <c>1249</c> <c>5404</c> <c>PS</c> <c>27</c> <c>214</c> <c>5172</c> <c>PS</c> <c>7</c> <c>305</c> <c>5349</c> <c>Info</c> <c>10</c> <c>1096</c> <c>5301</c> <c>PS</c> <c>6</c> <c>396</c> <c>5174</c> <c>Info</c> <c>8</c> <c>427</c> </texttable> <texttable> <ttcol align='left'>RFC (1998)</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Pages</ttcol> <ttcol align='right'>Delay</ttcol> <c>2289</c> <c>PS</c> <c>25</c> <c>396</c> <c>2267</c> <c>Info</c> <c>10</c> <c>unknown</c> <c>2317</c> <c>BCP</c> <c>10</c> <c>485</c> <c>2404</c> <c>PS</c> <c>7</c> <c>488</c> <c>2374</c> <c>PS</c> <c>12</c> <c>289</c> <c>2449</c> <c>PS</c> <c>19</c> <c>273</c> <c>2283</c> <c>PS</c> <c>9</c> <c>153</c> <c>2394</c> <c>Info</c> <c>6</c> <c>365</c> <c>2348</c> <c>DS</c> <c>5</c> <c>699</c> <c>2382</c> <c>Info</c> <c>30</c> <c>396</c> <c>2297</c> <c>ISE</c> <c>109</c> <c>28</c> <c>2381</c> <c>PS</c> <c>43</c> <c>699</c> <c>2312</c> <c>Info</c> <c>20</c> <c>365</c> <c>2387</c> <c>PS</c> <c>10</c> <c>122</c> <c>2398</c> <c>Info</c> <c>15</c> <c>396</c> <c>2391</c> <c>PS</c> <c>10</c> <c>122</c> <c>2431</c> <c>PS</c> <c>10</c> <c>457</c> <c>2282</c> <c>Info</c> <c>14</c> <c>215</c> <c>2323</c> <c>ISE</c> <c>5</c> <c>unknown</c> <c>2448</c> <c>ISE</c> <c>7</c> <c>92</c> </texttable> <t>We<table align="center" pn="table-2"> <thead> <tr> <th align="left" colspan="1" rowspan="1">RFC (2008)</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Pages</th> <th align="right" colspan="1" rowspan="1">Delay</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">5326</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">54</td> <td align="right" colspan="1" rowspan="1">1584</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5348</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">58</td> <td align="right" colspan="1" rowspan="1">823</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5281</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">51</td> <td align="right" colspan="1" rowspan="1">1308</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5354</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">23</td> <td align="right" colspan="1" rowspan="1">2315</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5227</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">21</td> <td align="right" colspan="1" rowspan="1">2434</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5329</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">12</td> <td align="right" colspan="1" rowspan="1">1980</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5277</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">35</td> <td align="right" colspan="1" rowspan="1">912</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5236</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">26</td> <td align="right" colspan="1" rowspan="1">1947</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5358</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">7</td> <td align="right" colspan="1" rowspan="1">884</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5271</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">22</td> <td align="right" colspan="1" rowspan="1">1066</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5195</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">10</td> <td align="right" colspan="1" rowspan="1">974</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5283</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">12</td> <td align="right" colspan="1" rowspan="1">1096</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5186</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">6</td> <td align="right" colspan="1" rowspan="1">2253</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5142</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">13</td> <td align="right" colspan="1" rowspan="1">1005</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5373</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">24</td> <td align="right" colspan="1" rowspan="1">1249</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5404</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">27</td> <td align="right" colspan="1" rowspan="1">214</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5172</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">7</td> <td align="right" colspan="1" rowspan="1">305</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5349</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">10</td> <td align="right" colspan="1" rowspan="1">1096</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5301</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">6</td> <td align="right" colspan="1" rowspan="1">396</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5174</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">427</td> </tr> </tbody> </table> <table align="center" pn="table-3"> <thead> <tr> <th align="left" colspan="1" rowspan="1">RFC (1998)</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Pages</th> <th align="right" colspan="1" rowspan="1">Delay</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">2289</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">25</td> <td align="right" colspan="1" rowspan="1">396</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2267</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">10</td> <td align="right" colspan="1" rowspan="1">unknown</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2317</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">10</td> <td align="right" colspan="1" rowspan="1">485</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2404</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">7</td> <td align="right" colspan="1" rowspan="1">488</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2374</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">12</td> <td align="right" colspan="1" rowspan="1">289</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2449</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">19</td> <td align="right" colspan="1" rowspan="1">273</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2283</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">9</td> <td align="right" colspan="1" rowspan="1">153</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2394</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">6</td> <td align="right" colspan="1" rowspan="1">365</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2348</td> <td align="left" colspan="1" rowspan="1">DS</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">699</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2382</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">30</td> <td align="right" colspan="1" rowspan="1">396</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2297</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">109</td> <td align="right" colspan="1" rowspan="1">28</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2381</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">43</td> <td align="right" colspan="1" rowspan="1">699</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2312</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">20</td> <td align="right" colspan="1" rowspan="1">365</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2387</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">10</td> <td align="right" colspan="1" rowspan="1">122</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2398</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">15</td> <td align="right" colspan="1" rowspan="1">396</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2391</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">10</td> <td align="right" colspan="1" rowspan="1">122</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2431</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">10</td> <td align="right" colspan="1" rowspan="1">457</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2282</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">14</td> <td align="right" colspan="1" rowspan="1">215</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2323</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">unknown</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2448</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">7</td> <td align="right" colspan="1" rowspan="1">92</td> </tr> </tbody> </table> <t indent="0" pn="section-4.1-10">We can compare the median delay, and the delays observed by the fastest and slowest quartiles in the three years:</t><texttable> <ttcol align='left'>Year</ttcol> <ttcol align='right'>Fastest 25%</ttcol> <ttcol align='right'>Median</ttcol> <ttcol align='right'>Slowest 25%</ttcol> <c>2018</c> <c>604</c> <c>1179</c> <c>1522</c> <c>2008</c> <c>869</c> <c>1081</c> <c>1675</c> <c>1998</c> <c>169</c> <c>365</c> <c>442</c> </texttable> <t>The<table align="center" pn="table-4"> <thead> <tr> <th align="left" colspan="1" rowspan="1">Year</th> <th align="right" colspan="1" rowspan="1">Fastest 25%</th> <th align="right" colspan="1" rowspan="1">Median</th> <th align="right" colspan="1" rowspan="1">Slowest 25%</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">2018</td> <td align="right" colspan="1" rowspan="1">715</td> <td align="right" colspan="1" rowspan="1">1221</td> <td align="right" colspan="1" rowspan="1">1537</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2008</td> <td align="right" colspan="1" rowspan="1">869</td> <td align="right" colspan="1" rowspan="1">1081</td> <td align="right" colspan="1" rowspan="1">1675</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">1998</td> <td align="right" colspan="1" rowspan="1">169</td> <td align="right" colspan="1" rowspan="1">365</td> <td align="right" colspan="1" rowspan="1">442</td> </tr> </tbody> </table> <t indent="0" pn="section-4.1-12">The IETF takes three to four times moretimesto produce an RFC in 2018 than it did in 1998, but about the same time as it did in 2008. We can get a rough estimate of how this translates intermterms of "level of attention" per RFC by comparing the number of participants in the IETF meetings of 2018,20082008, and 1998 <xreftarget="IETFCOUNT"/>target="IETFCOUNT" format="default" sectionFormat="of" derivedContent="IETFCOUNT"/> to the number ofRFCRFCs published these years <xreftarget="RFCYEAR"/>.</t> <texttable> <ttcol align='left'>Year</ttcol> <ttcol align='right'>Nb RFC</ttcol> <ttcol align='right'>Spring P.</ttcol> <ttcol align='right'>Summer P.</ttcol> <ttcol align='right'>Fall</ttcol> <ttcol align='right'>Average P.</ttcol> <ttcol align='left'>Attendees/RFC</ttcol> <c>2018</c> <c>208</c> <c>1235</c> <c>1078</c> <c>879</c> <c>1064</c> <c>5.1</c> <c>2008</c> <c>290</c> <c>1128</c> <c>1181</c> <c>962</c> <c>1090</c> <c>3.8</c> <c>1998</c> <c>234</c> <c>1775</c> <c>2106</c> <c>1705</c> <c>1862</c> <c>9.0</c> </texttable> <t>Thetarget="RFCYEAR" format="default" sectionFormat="of" derivedContent="RFCYEAR"/>.</t> <table align="center" pn="table-5"> <thead> <tr> <th align="left" colspan="1" rowspan="1">Year</th> <th align="left" colspan="1" rowspan="1">Number of RFCs</th> <th align="right" colspan="1" rowspan="1">Spring P.</th> <th align="right" colspan="1" rowspan="1">Summer P.</th> <th align="right" colspan="1" rowspan="1">Fall P.</th> <th align="right" colspan="1" rowspan="1">Average P.</th> <th align="left" colspan="1" rowspan="1">Attendees/RFC</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">2018</td> <td align="right" colspan="1" rowspan="1">208</td> <td align="right" colspan="1" rowspan="1">1235</td> <td align="right" colspan="1" rowspan="1">1078</td> <td align="right" colspan="1" rowspan="1">879</td> <td align="right" colspan="1" rowspan="1">1064</td> <td align="left" colspan="1" rowspan="1">5.1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2008</td> <td align="right" colspan="1" rowspan="1">290</td> <td align="right" colspan="1" rowspan="1">1128</td> <td align="right" colspan="1" rowspan="1">1181</td> <td align="right" colspan="1" rowspan="1">962</td> <td align="right" colspan="1" rowspan="1">1090</td> <td align="left" colspan="1" rowspan="1">3.8</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">1998</td> <td align="right" colspan="1" rowspan="1">234</td> <td align="right" colspan="1" rowspan="1">1775</td> <td align="right" colspan="1" rowspan="1">2106</td> <td align="right" colspan="1" rowspan="1">1705</td> <td align="right" colspan="1" rowspan="1">1862</td> <td align="left" colspan="1" rowspan="1">8.0</td> </tr> </tbody> </table> <t indent="0" pn="section-4.1-14">The last column in the table provides the ratio of average number of participantsbyto the number ofRFC produced.RFCs published. If the IETFwaswere a centralized organization, and if all participants and documents were equivalent, this ratio would be the number of participants dedicated to produce an RFC on a given year. This is of course a completely abstract figure because none of the hypotheses aboveisare true, but it still gives a vague indication of the "level of attention" applied to documents. We see that this ratio has increased from 2008 to 2018, as the number of participants was about the same for these two years but the number of published RFCs decreased. However,thatthis ratio was much higher in 1998. The IETF had many more participants, and there were probably many more eyes available to review any given draft. If we applied the ratios of 1998, the IETF would be producing 119 documents in 2018 instead of 208.</t> </section> <section anchor="working-group-processing-time"title="Workingnumbered="true" toc="include" removeInRFC="false" pn="section-4.2"> <name slugifiedName="name-working-group-processing-ti">Working Group ProcessingTime"> <t>TheTime</name> <t indent="0" pn="section-4.2-1">The largest part of the delays is spent in theWorking Groups,working groups, before the draft is submitted to the IESG for IETF review. As mentioned in <xreftarget="milestones"/>,target="milestones" format="default" sectionFormat="of" derivedContent="Section 2.1"/>, the only intermediate milestone that we can extract from the IETFdatatrackerDatatracker is the date at which the document was adopted by theWorking Group,working group, or targeted for independent submission. The breakdown of the delays for the documents in our sample is:</t><texttable> <ttcol align='left'>RFC</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>WG</ttcol> <ttcol align='right'>Until adoption</ttcol> <ttcol align='right'>After adoption</ttcol> <c>8411</c> <c>Info</c> <c>154</c> <c>0</c> <c>154</c> <c>8456</c> <c>Info</c> <c>1033</c> <c>209</c> <c>824</c> <c>8446</c> <c>PS</c> <c>1400</c> <c>0</c> <c>1400</c> <c>8355</c> <c>Info</c> <c>1175</c> <c>102</c> <c>1073</c> <c>8441</c> <c>PS</c> <c>204</c> <c>65</c> <c>139</c> <c>8324</c> <c>ISE</c> <c>38</c> <c>0</c> <c>38</c> <c>8377</c> <c>PS</c> <c>1630</c> <c>728</c> <c>902</c> <c>8498</c> <c>Info</c> <c>935</c> <c>420</c> <c>515</c> <c>8479</c> <c>ISE</c> <c>233</c> <c>0</c> <c>233</c> <c>8453</c> <c>Info</c> <c>1036</c> <c>396</c> <c>640</c> <c>8429</c> <c>BCP</c> <c>76</c> <c>0</c> <c>76</c> <c>8312</c> <c>Info</c> <c>1113</c> <c>280</c> <c>833</c> <c>8492</c> <c>ISE</c> <c>1706</c> <c>1428</c> <c>278</c> <c>8378</c> <c>Exp</c> <c>1446</c> <c>661</c> <c>785</c> <c>8361</c> <c>PS</c> <c>1477</c> <c>399</c> <c>1078</c> <c>8472</c> <c>PS</c> <c>899</c> <c>105</c> <c>794</c> <c>8471</c> <c>PS</c> <c>1127</c> <c>153</c> <c>794</c> <c>8466</c> <c>PS</c> <c>538</c> <c>178</c> <c>360</c> <c>8362</c> <c>PS</c> <c>1766</c> <c>240</c> <c>1526</c> <c>8468</c> <c>Info</c> <c>979</c> <c>333</c> <c>646</c> <c> </c> <c>Average</c> <c>948</c> <c>285</c> <c>663</c> </texttable> <t>The<table align="center" pn="table-6"> <thead> <tr> <th align="left" colspan="1" rowspan="1">RFC</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">WG</th> <th align="right" colspan="1" rowspan="1">Until adoption</th> <th align="right" colspan="1" rowspan="1">After adoption</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">8411</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">154</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">154</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8456</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1033</td> <td align="right" colspan="1" rowspan="1">209</td> <td align="right" colspan="1" rowspan="1">824</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8446</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1400</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">1400</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8355</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1175</td> <td align="right" colspan="1" rowspan="1">102</td> <td align="right" colspan="1" rowspan="1">1073</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8441</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">204</td> <td align="right" colspan="1" rowspan="1">65</td> <td align="right" colspan="1" rowspan="1">139</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8324</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">38</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">38</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8377</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1630</td> <td align="right" colspan="1" rowspan="1">728</td> <td align="right" colspan="1" rowspan="1">902</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8498</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">935</td> <td align="right" colspan="1" rowspan="1">420</td> <td align="right" colspan="1" rowspan="1">515</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8479</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">233</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">233</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8453</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1036</td> <td align="right" colspan="1" rowspan="1">396</td> <td align="right" colspan="1" rowspan="1">640</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8429</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">76</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">76</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8312</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1113</td> <td align="right" colspan="1" rowspan="1">280</td> <td align="right" colspan="1" rowspan="1">833</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8492</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">1706</td> <td align="right" colspan="1" rowspan="1">1428</td> <td align="right" colspan="1" rowspan="1">278</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8378</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">1446</td> <td align="right" colspan="1" rowspan="1">661</td> <td align="right" colspan="1" rowspan="1">785</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8361</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1477</td> <td align="right" colspan="1" rowspan="1">399</td> <td align="right" colspan="1" rowspan="1">1078</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8472</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">899</td> <td align="right" colspan="1" rowspan="1">105</td> <td align="right" colspan="1" rowspan="1">794</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8471</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1127</td> <td align="right" colspan="1" rowspan="1">153</td> <td align="right" colspan="1" rowspan="1">794</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8466</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">538</td> <td align="right" colspan="1" rowspan="1">178</td> <td align="right" colspan="1" rowspan="1">360</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8362</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1766</td> <td align="right" colspan="1" rowspan="1">240</td> <td align="right" colspan="1" rowspan="1">1526</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8468</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">979</td> <td align="right" colspan="1" rowspan="1">333</td> <td align="right" colspan="1" rowspan="1">646</td> </tr> <tr> <td align="left" colspan="2" rowspan="1">Average</td> <td align="right" colspan="1" rowspan="1">948</td> <td align="right" colspan="1" rowspan="1">285</td> <td align="right" colspan="1" rowspan="1">663</td> </tr> </tbody> </table> <t indent="0" pn="section-4.2-3">The time beforeWorking Groupworking group adoptionaverageaverages to a bit more than 9 months, compared to 1yearsyear and almost 10 months for processing time after adoption. We see that RFC 8492 stands out, with long delays spent attempting publication through aWorking Groupworking group before submission to the IndependentStreamSubmissions Editor. If weremovedremove RFC 8492 from the list, the average time until adoption drops to just over 7 months, and becomes just 25% of the total processing time in the WG.</t><t>There<t indent="0" pn="section-4.2-4">There are a few documents that started immediately asWorking Groupworking group efforts, or were immediately targeted for publication in the Independent Stream. Those documents tend to see short processing times, with the exception of RFC 8446 on which the TLS Working Group spent a long time working.</t> </section> <section anchor="preparation-and-publication-delays"title="Preparationnumbered="true" toc="include" removeInRFC="false" pn="section-4.3"> <name slugifiedName="name-preparation-and-publication">Preparation and PublicationDelays"> <t>TheDelays</name> <t indent="0" pn="section-4.3-1">The preparation and publication delays include three components:</t><t><list style="symbols"> <t>the<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4.3-2"> <li pn="section-4.3-2.1">the delay from submission to the RFC Editor to beginning ofAUTH-48,AUTH48, during which the document isprepared;</t> <t>the AUTH-48prepared (referred to as "RFC edit" below);</li> <li pn="section-4.3-2.2">the AUTH48 delay, during which authors review and eventually approve the changes proposed by theeditors;</t> <t>theeditors (referred to as "AUTH48" below);</li> <li pn="section-4.3-2.3">the publication delay, from final agreement by authors and editors to actualpublication.</t> </list></t> <t>Thepublication (referred to as "RFC Pub" below).</li> </ul> <t indent="0" pn="section-4.3-3">The breakdown of the publication delays for each RFC is shown in the following table.</t><texttable> <ttcol align='right'>RFC</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Pages</ttcol> <ttcol align='right'>RFC edit</ttcol> <ttcol align='right'>AUTH-48</ttcol> <ttcol align='right'>RFC Pub</ttcol> <ttcol align='right'>Edit(total)</ttcol> <c>8411</c> <c>Info</c> <c>5</c> <c>53</c> <c>88</c> <c>20</c> <c>161</c> <c>8456</c> <c>Info</c> <c>64</c> <c>98</c> <c>46</c> <c>14</c> <c>158</c> <c>8446</c> <c>PS</c> <c>160</c> <c>85</c> <c>57</c> <c>0</c> <c>142</c> <c>8355</c> <c>Info</c> <c>13</c> <c>83</c> <c>15</c> <c>1</c> <c>99</c> <c>8441</c> <c>PS</c> <c>8</c> <c>67</c> <c>33</c> <c>6</c> <c>106</c> <c>8324</c> <c>ISE</c> <c>29</c> <c>42</c> <c>28</c> <c>1</c> <c>71</c> <c>8377</c> <c>PS</c> <c>8</c> <c>39</c> <c>102</c> <c>0</c> <c>141</c> <c>8498</c> <c>Info</c> <c>15</c> <c>49</c> <c>16</c> <c>2</c> <c>67</c> <c>8479</c> <c>ISE</c> <c>8</c> <c>31</c> <c>5</c> <c>1</c> <c>37</c> <c>8453</c> <c>Info</c> <c>42</c> <c>73</c> <c>7</c> <c>0</c> <c>80</c> <c>8429</c> <c>BCP</c> <c>10</c> <c>60</c> <c>99</c> <c>0</c> <c>159</c> <c>8312</c> <c>Info</c> <c>18</c> <c>96</c> <c>30</c> <c>0</c> <c>126</c> <c>8492</c> <c>ISE</c> <c>40</c> <c>355</c> <c>123</c> <c>2</c> <c>480</c> <c>8378</c> <c>Exp</c> <c>21</c> <c>42</c> <c>9</c> <c>0</c> <c>51</c> <c>8361</c> <c>PS</c> <c>17</c> <c>39</c> <c>31</c> <c>3</c> <c>73</c> <c>8472</c> <c>PS</c> <c>8</c> <c>59</c> <c>8</c> <c>13</c> <c>80</c> <c>8471</c> <c>PS</c> <c>18</c> <c>59</c> <c>8</c> <c>13</c> <c>80</c> <c>8466</c> <c>PS</c> <c>158</c> <c>84</c> <c>22</c> <c>3</c> <c>109</c> <c>8362</c> <c>PS</c> <c>33</c> <c>49</c> <c>11</c> <c>4</c> <c>64</c> <c>8468</c> <c>Info</c> <c>15</c> <c>65</c> <c>53</c> <c>9</c> <c>127</c> <c> </c> <c>Average</c> <c> </c> <c>76</c> <c>40</c> <c>5</c> <c>121</c> <c>-8492</c> <c>Average</c> <c> </c> <c>62</c> <c>35</c> <c>5</c> <c>102</c> </texttable> <t>On<table align="center" pn="table-7"> <thead> <tr> <th align="right" colspan="1" rowspan="1">RFC</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Pages</th> <th align="right" colspan="1" rowspan="1">RFC edit</th> <th align="right" colspan="1" rowspan="1">AUTH48</th> <th align="right" colspan="1" rowspan="1">RFC Pub</th> <th align="right" colspan="1" rowspan="1">Edit (total)</th> </tr> </thead> <tbody> <tr> <td align="right" colspan="1" rowspan="1">8411</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">53</td> <td align="right" colspan="1" rowspan="1">88</td> <td align="right" colspan="1" rowspan="1">20</td> <td align="right" colspan="1" rowspan="1">161</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8456</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">64</td> <td align="right" colspan="1" rowspan="1">98</td> <td align="right" colspan="1" rowspan="1">46</td> <td align="right" colspan="1" rowspan="1">14</td> <td align="right" colspan="1" rowspan="1">158</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8446</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">160</td> <td align="right" colspan="1" rowspan="1">85</td> <td align="right" colspan="1" rowspan="1">57</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">142</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8355</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">13</td> <td align="right" colspan="1" rowspan="1">83</td> <td align="right" colspan="1" rowspan="1">15</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">99</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8441</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">56</td> <td align="right" colspan="1" rowspan="1">33</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">92</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8324</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">29</td> <td align="right" colspan="1" rowspan="1">42</td> <td align="right" colspan="1" rowspan="1">28</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">71</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8377</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">39</td> <td align="right" colspan="1" rowspan="1">102</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">141</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8498</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">15</td> <td align="right" colspan="1" rowspan="1">48</td> <td align="right" colspan="1" rowspan="1">16</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">65</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8479</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">31</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">37</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8453</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">42</td> <td align="right" colspan="1" rowspan="1">73</td> <td align="right" colspan="1" rowspan="1">7</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">83</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8429</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">10</td> <td align="right" colspan="1" rowspan="1">60</td> <td align="right" colspan="1" rowspan="1">99</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">159</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8312</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">18</td> <td align="right" colspan="1" rowspan="1">55</td> <td align="right" colspan="1" rowspan="1">28</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">85</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8492</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">40</td> <td align="right" colspan="1" rowspan="1">355</td> <td align="right" colspan="1" rowspan="1">123</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">480</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8378</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">21</td> <td align="right" colspan="1" rowspan="1">42</td> <td align="right" colspan="1" rowspan="1">9</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">51</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8361</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">17</td> <td align="right" colspan="1" rowspan="1">39</td> <td align="right" colspan="1" rowspan="1">31</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">73</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8472</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">59</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">13</td> <td align="right" colspan="1" rowspan="1">80</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8471</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">18</td> <td align="right" colspan="1" rowspan="1">59</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">13</td> <td align="right" colspan="1" rowspan="1">80</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8466</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">158</td> <td align="right" colspan="1" rowspan="1">84</td> <td align="right" colspan="1" rowspan="1">22</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">109</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8362</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">33</td> <td align="right" colspan="1" rowspan="1">49</td> <td align="right" colspan="1" rowspan="1">11</td> <td align="right" colspan="1" rowspan="1">4</td> <td align="right" colspan="1" rowspan="1">64</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8468</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">15</td> <td align="right" colspan="1" rowspan="1">65</td> <td align="right" colspan="1" rowspan="1">53</td> <td align="right" colspan="1" rowspan="1">9</td> <td align="right" colspan="1" rowspan="1">127</td> </tr> <tr> <td colspan="2" align="left" rowspan="1">Average</td> <td align="right" colspan="1" rowspan="1"/> <td align="right" colspan="1" rowspan="1">74</td> <td align="right" colspan="1" rowspan="1">39</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">118</td> </tr> <tr> <td colspan="2" align="left" rowspan="1">Average (without 8492)</td> <td align="right" colspan="1" rowspan="1"/> <td align="right" colspan="1" rowspan="1">59</td> <td align="right" colspan="1" rowspan="1">35</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">99</td> </tr> </tbody> </table> <t indent="0" pn="section-4.3-5">On average, the total delay appears to be about four months, but the average is skewed by the extreme values encountered for <xreftarget="RFC8492"/>.target="RFC8492" format="default" sectionFormat="of" derivedContent="RFC8492"/>. If we exclude that RFC from the computations, the average delay drops to a just a bit more than 3 months: about 2 months for the preparation, a bit more than one month for theAUTH-48AUTH48 phase, and 5 days for the publishing.</t><t>Of<t indent="0" pn="section-4.3-6">Of course, these delays vary from RFC to RFC. To try explain the causes of the delay, we compute the correlation factor between the observed delays and several plausible explanation factors:</t><t><list style="symbols"> <t>The<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4.3-7"> <li pn="section-4.3-7.1">the number of pages in thedocument,</t> <t>Thedocument,</li> <li pn="section-4.3-7.2">the amount of copyedit,editing, as discussed in <xreftarget="copy-editing"/>,</t> <t>Whethertarget="copy-editing" format="default" sectionFormat="of" derivedContent="Section 4.4"/>,</li> <li pn="section-4.3-7.3">whether or notanIANAaction was required,</t> <t>Theactions were required,</li> <li pn="section-4.3-7.4">the number ofauthors,</t> <t>Theauthors,</li> <li pn="section-4.3-7.5">the number ofdrafts revisions,</t> <t>The Working Group delay.</t> </list></t> <t>Wedraft revisions,</li> <li pn="section-4.3-7.6">the working group delay.</li> </ul> <t indent="0" pn="section-4.3-8">We find the following values:</t><texttable> <ttcol align='left'>Correlation</ttcol> <ttcol align='right'>RFC edit</ttcol> <ttcol align='right'>AUTH-48</ttcol> <ttcol align='right'>Edit(total)</ttcol> <c>Nb pages</c> <c>0.50</c> <c>-0.04</c> <c>0.21</c> <c>Copy-Edit</c> <c>0.42</c> <c>0.24</c> <c>0.45</c> <c>IANA</c> <c>-0.14</c> <c>-0.21</c> <c>0.12</c> <c>Nb Authors</c> <c>0.39</c> <c>-0.07</c> <c>0.18</c> <c>Nb drafts</c> <c>0.18</c> <c>-0.33</c> <c>-0.19</c> <c>WG delay</c> <c>0.03</c> <c>-0.16</c> <c>-0.15</c> </texttable> <t>We<table align="center" pn="table-8"> <thead> <tr> <th align="left" colspan="1" rowspan="1">Correlation</th> <th align="right" colspan="1" rowspan="1">RFC edit</th> <th align="right" colspan="1" rowspan="1">AUTH48</th> <th align="right" colspan="1" rowspan="1">Edit(total)</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">Number of pages</td> <td align="right" colspan="1" rowspan="1">0.50</td> <td align="right" colspan="1" rowspan="1">-0.04</td> <td align="right" colspan="1" rowspan="1">0.21</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">Copy-Edit</td> <td align="right" colspan="1" rowspan="1">0.42</td> <td align="right" colspan="1" rowspan="1">0.24</td> <td align="right" colspan="1" rowspan="1">0.45</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">IANA</td> <td align="right" colspan="1" rowspan="1">-0.14</td> <td align="right" colspan="1" rowspan="1">-0.21</td> <td align="right" colspan="1" rowspan="1">0.12</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">Number of authors</td> <td align="right" colspan="1" rowspan="1">0.39</td> <td align="right" colspan="1" rowspan="1">-0.07</td> <td align="right" colspan="1" rowspan="1">0.18</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">Number of drafts</td> <td align="right" colspan="1" rowspan="1">0.18</td> <td align="right" colspan="1" rowspan="1">-0.33</td> <td align="right" colspan="1" rowspan="1">-0.19</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">WG delay</td> <td align="right" colspan="1" rowspan="1">0.03</td> <td align="right" colspan="1" rowspan="1">-0.16</td> <td align="right" colspan="1" rowspan="1">-0.15</td> </tr> </tbody> </table> <t indent="0" pn="section-4.3-10">We see some plausible explanations for the production delay. It will be somewhat longer for longerdocuments,documents or for documents that require a lot of copy editing (see <xreftarget="copy-editing"/>).target="copy-editing" format="default" sectionFormat="of" derivedContent="Section 4.4"/>). Somewhat surprisingly, it alsotendtends to increase with the number of authors. It does not appear significantly correlated with the presence or absence of IANA action.</t><t>The<t indent="0" pn="section-4.3-11">The analysis of RFC 8324 in <xreftarget="analyse-8324"/>target="analyse-8324" format="default" sectionFormat="of" derivedContent="Section 3.6"/> explains its short editing delays by the experience of the author. This makes sense: if a document needs less editing, the editing delays would be shorter. This is partially confirmed by the relation between the amount of copy editing and the publication delay.</t><t>We<t indent="0" pn="section-4.3-12">We see fewer plausible explanations for the AUTH48 delays. These delays vary much more than the preparation delay, with a standard deviation of 20 days forAUTH-48AUTH48 versus 10 days for the preparation delay. In theory,AUTH-48AUTH48 is just a final verification: the authors receive the document prepared by the RFC production center, and just have to give their approval, or maybe request a last minute correction. The name indicates that this is expected to last just two days, but in average it lasts more than a month.</t><t>We<t indent="0" pn="section-4.3-13">We often hypothesize that the number of authors influences theAUTH-48AUTH48 delay, or that authors who have spent a long time working on the document in theWorking Groupworking group somehow get demotivated and spend even longer to answer questions duringAUTH-48.AUTH48. This may happen sometimes, but our statistics don't show that–- if anything, the numerical results point in the opposite direction.</t><t>After<t indent="0" pn="section-4.3-14">After asking the authors of the RFCs in the sample why theAUTH-48AUTH48 phase took a long time, we got three explanations:</t><t>1- Some<ol indent="adaptive" spacing="normal" start="1" type="1" pn="section-4.3-15"> <li pn="section-4.3-15.1" derivedCounter="1.">Some RFCs have multiple authors in multiple time zones. This slows down the coordination required for approvingchanges.</t> <t>2- Somechanges.</li> <li pn="section-4.3-15.2" derivedCounter="2.">Some authors found some of the proposed changes unnecessary or undesirable, and asked that they be reversed. This required long exchanges between authors andeditors.</t> <t>3- Someeditors.</li> <li pn="section-4.3-15.3" derivedCounter="3.">Some authors were not giving high priority toAUTH-48 responses.</t> <t>AsAUTH48 responses.</li> </ol> <t indent="0" pn="section-4.3-16">As mentioned above, we were not able to verify these hypotheses by looking at the data. The author's experience with this document suggests another potential delay for the Independent Stream RFC: processing delay by the IndependentStreamSubmissions Editor, discussed in <xreftarget="independent-stream"/>.</t>target="independent-stream" format="default" sectionFormat="of" derivedContent="Section 4.5"/>.</t> </section> <section anchor="copy-editing"title="Copy Editing"> <t>Wenumbered="true" toc="include" removeInRFC="false" pn="section-4.4"> <name slugifiedName="name-copy-editing">Copy Editing</name> <t indent="0" pn="section-4.4-1">We can assess the amount of copy editing applied to each published RFC by comparing the text of the draft approved for publication and the text of the RFC. We do expect differences in the "boilerplate" and in the IANA section, but we will also see differences due to copy editing. Assessing the amount of copy editing is subjective, and we do it using a scale of 1 to 4:</t><t>1- Minor editing</t> <t>2- Editing<dl indent="4" newline="false" spacing="normal" pn="section-4.4-2"> <dt pn="section-4.4-2.1">1:</dt> <dd pn="section-4.4-2.2">Minor editing</dd> <dt pn="section-4.4-2.3">2:</dt> <dd pn="section-4.4-2.4">Editing for style, such as capitalization, hyphens,that"that" versuswhich,"which", andexpendingexpanding all acronyms at leastone.</t> <t>3- Editingonce.</dd> <dt pn="section-4.4-2.5">3:</dt> <dd pn="section-4.4-2.6">Editing for clarity in addition to style, such as rewriting ambiguous sentences and clarifying use of internal references. ForYangYANG models, that may include model corrections suggested by theverifier.</t> <t>4- Extensive editing.</t> <t>Theverifier.</dd> <dt pn="section-4.4-2.7">4:</dt> <dd pn="section-4.4-2.8">Extensive editing.</dd> </dl> <t indent="0" pn="section-4.4-3">The following table shows that about half of the RFCs required editing for style, and the other half at least some editing for clarity.</t><texttable> <ttcol align='right'>RFC</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Copy Edit</ttcol> <c>8411</c> <c>Info</c> <c>2</c> <c>8456</c> <c>Info</c> <c>4</c> <c>8446</c> <c>PS</c> <c>3</c> <c>8355</c> <c>Info</c> <c>2</c> <c>8441</c> <c>PS</c> <c>2</c> <c>8324</c> <c>ISE</c> <c>2</c> <c>8377</c> <c>PS</c> <c>3</c> <c>8498</c> <c>Info</c> <c>3</c> <c>8479</c> <c>ISE</c> <c>1</c> <c>8453</c> <c>Info</c> <c>2</c> <c>8429</c> <c>BCP</c> <c>2</c> <c>8312</c> <c>Info</c> <c>2</c> <c>8492</c> <c>ISE</c> <c>3</c> <c>8378</c> <c>Exp</c> <c>2</c> <c>8361</c> <c>PS</c> <c>2</c> <c>8472</c> <c>PS</c> <c>2</c> <c>8471</c> <c>PS</c> <c>2</c> <c>8466</c> <c>PS</c> <c>3</c> <c>8362</c> <c>PS</c> <c>3</c> <c>8468</c> <c>Info</c> <c>3</c> </texttable> <t>This<table align="center" pn="table-9"> <thead> <tr> <th align="right" colspan="1" rowspan="1">RFC</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Copy Edit</th> </tr> </thead> <tbody> <tr> <td align="right" colspan="1" rowspan="1">8411</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8456</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">4</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8446</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8355</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8441</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8324</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8377</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8498</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8479</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8453</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8429</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8312</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8492</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8378</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8361</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8472</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8471</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8466</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8362</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> <tr> <td align="right" colspan="1" rowspan="1">8468</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> </tbody> </table> <t indent="0" pn="section-4.4-5">This method of assessment does not take into account the number of changes proposed by the editors and eventually rejected by the authors, since these changes are not present in either the final draft or the published RFC. It might be possible to get an evaluation of these "phantom changes" from the RFC Production Center.</t> </section> <section anchor="independent-stream"title="Independent Stream"> <t>Outnumbered="true" toc="include" removeInRFC="false" pn="section-4.5"> <name slugifiedName="name-independent-stream">Independent Stream</name> <t indent="0" pn="section-4.5-1">Out of 20 randomly selected RFCs, 3 were published through the Independent Stream. One is an independent opinion, another a description of a non-IETF protocol format, and the third was <xreftarget="RFC8492"/>,target="RFC8492" format="default" sectionFormat="of" derivedContent="RFC8492"/>, which is a special case. Apart from this special case, the publication delays were significantly shorter for the Independent Stream than for the IETFstream.</t> <t>TheStream.</t> <t indent="0" pn="section-4.5-2">The authors of these 3 RFCs are regular IETF contributors. This observation motivated a secondary analysis of all the RFCs published in the Independent Stream in 2018. There are 14 such RFCs: 8507, 8494, 8493, 8492, 8483, 8479, 8433, 8409, 8374, 8369, 8367, 8351,83288328, and 8324.(RFC(RFCs 8367 and 8369 were published on 1 April 2018.) The majority of the documents were published by regular IETF participants, but two of them were not. One describes "The BagIt File Packaging Format (V1.0)" <xreftarget="RFC8493"/>,target="RFC8493" format="default" sectionFormat="of" derivedContent="RFC8493"/>, and the other the "Yeti DNS Testbed" <xreftarget="RFC8483"/>.target="RFC8483" format="default" sectionFormat="of" derivedContent="RFC8483"/>. They document a data format and a system developed outside theIETF,IETF and illustrate the outreach function of the Independent Stream. In both cases, the authors include one experienced IETF participant, who presumably helped outsiders navigate the publication process.</t><t>Th<t indent="0" pn="section-4.5-3">Th present document experienced some publication delays due to the IndependentStreamSubmissions Editor. The ISE is a bottleneck and is a volunteer resource. Although the ISE as a lone person operating as a volunteer is still roughly adequate resource for the job, the delivery will necessarily be best effort with delays caused by spikes in ISE load, work commitments, and other life events. These delays may not be fundamentally critical to RFC delivery, but they are capable of introducing a significant percentage delay into what might otherwise be a smooth process.</t> </section> </section> <section anchor="citations"title="Citation Counts"> <t>Innumbered="true" toc="include" removeInRFC="false" pn="section-5"> <name slugifiedName="name-citation-counts">Citation Counts</name> <t indent="0" pn="section-5-1">In this exploration, we want toassessexamine whether citation counts provide a meaningful assessment of the popularity of RFCs. We obtain the citation counts through the Semantic Scholar API, using queries of theform:</t> <figure><artwork><![CDATA[ http://api.semanticscholar.org/ v1/paper/10.17487/rfc8446?include_unknown_references=true ]]></artwork></figure> <t>Inform: <eref brackets="angle" target="https://api.semanticscholar.org/v1/paper/10.17487/rfc8446?include_unknown_references=true"/> </t> <t indent="0" pn="section-5-2">In these queries, the RFC is uniquely identified by its DOI reference, which is composed of the RFC Series prefix 10.17487 and the RFC identifier. The queries return a series of properties, including a list of citations for the RFC. Based on that list of citations, we compute three numbers:</t><t><list style="symbols"> <t>The<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5-3"> <li pn="section-5-3.1">The total number ofcitations</t> <t>Thecitations</li> <li pn="section-5-3.2">The number of citations in the year of publication and the year afterthat</t> <t>Forthat</li> <li pn="section-5-3.3">For the RFC published in 1998 or 2008 that we use for comparison, the number of citations in the years 2018 and2019.</t> </list></t> <t>All2019.</li> </ul> <t indent="0" pn="section-5-4">All the numbers were retrieved on October 6, 2019.</t> <section anchor="citation-numbers"title="Citation Numbers"> <t>Asnumbered="true" toc="include" removeInRFC="false" pn="section-5.1"> <name slugifiedName="name-citation-numbers">Citation Numbers</name> <t indent="0" pn="section-5.1-1">As measured on October 6, 2019, the citation counts for the RFC in our sample set were:</t><texttable> <ttcol align='left'>RFC(2018)</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Total</ttcol> <ttcol align='right'>2018-2019</ttcol> <c>8411</c> <c>Info</c> <c>1</c> <c>0</c> <c>8456</c> <c>Info</c> <c>1</c> <c>1</c> <c>8446</c> <c>PS</c> <c>418</c> <c>204</c> <c>8355</c> <c>Info</c> <c>3</c> <c>3</c> <c>8441</c> <c>PS</c> <c>1</c> <c>1</c> <c>8324</c> <c>ISE</c> <c>0</c> <c>0</c> <c>8377</c> <c>PS</c> <c>0</c> <c>0</c> <c>8498</c> <c>Info</c> <c>0</c> <c>0</c> <c>8479</c> <c>ISE</c> <c>0</c> <c>0</c> <c>8453</c> <c>Info</c> <c>3</c> <c>3</c> <c>8429</c> <c>BCP</c> <c>0</c> <c>0</c> <c>8312</c> <c>Info</c> <c>25</c> <c>16</c> <c>8492</c> <c>ISE</c> <c>4</c> <c>4</c> <c>8378</c> <c>Exp</c> <c>1</c> <c>1</c> <c>8361</c> <c>PS</c> <c>0</c> <c>0</c> <c>8472</c> <c>PS</c> <c>1</c> <c>1</c> <c>8471</c> <c>PS</c> <c>1</c> <c>1</c> <c>8466</c> <c>PS</c> <c>0</c> <c>0</c> <c>8362</c> <c>PS</c> <c>1</c> <c>1</c> <c>8468</c> <c>Info</c> <c>1</c> <c>1</c> </texttable> <t>The<table align="center" pn="table-10"> <thead> <tr> <th align="left" colspan="1" rowspan="1">RFC (2018)</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Total</th> <th align="right" colspan="1" rowspan="1">2018-2019</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">8411</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8456</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8446</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">418</td> <td align="right" colspan="1" rowspan="1">204</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8355</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8441</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8324</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8377</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8498</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8479</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8453</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8429</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8312</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">25</td> <td align="right" colspan="1" rowspan="1">16</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8492</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">4</td> <td align="right" colspan="1" rowspan="1">4</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8378</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8361</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8472</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8471</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8466</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8362</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8468</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> </tbody> </table> <t indent="0" pn="section-5.1-3">The results indicate that <xreftarget="RFC8446"/>target="RFC8446" format="default" sectionFormat="of" derivedContent="RFC8446"/> is by far the most cited of the 20 RFC in our sample. This is not surprising, since TLS is a key Internet Protocol. The TLS 1.3 protocol was also the subject of extensive studies by researchers, and thus was mentioned in a number of published papers. Surprisingly, the Semantic Scholar mentions a number of citations that predate the publication date. These are probably citations of the various draft versions of the protocol.</t><t>The<t indent="0" pn="section-5.1-4">The next most cited RFC in the sample is <xreftarget="RFC8312"/>target="RFC8312" format="default" sectionFormat="of" derivedContent="RFC8312"/> which describes the Cubic congestion control algorithm for TCP. That protocol was also the target of a large number of academicpublications.Thepublications. The otherRFCRFCs in the sample only have a small number of citations.</t><t>There<t indent="0" pn="section-5.1-5">There is probably a small bias when measuring citations at a fixed date. An RFC published in January 2018 would have more time to accrue citations than one published in December. That may be true to some extent, as the second most cited RFC in the set was published in January. However, the effect has to be limited. The most cited RFC was published in August, and the second most cited was published in 2019. (That RFC got an RFC number in 2018, but publication was slowed by longAUTH-48AUTH48 delays.)</t> </section> <section anchor="comparison-to-1998-and-2008"title="Comparisonnumbered="true" toc="include" removeInRFC="false" pn="section-5.2"> <name slugifiedName="name-comparison-to-1998-and-2008">Comparison to 1998 and2008"> <t>In2008</name> <t indent="0" pn="section-5.2-1">In order to get a baseline, we can look at the number of references for the RFCs published in 2008 and 1998. However, we needtotaketo take time into account. Documents published a long time ago are expected to have accrued more references. We try to address this by looking at three counts for each document: the overall number of references over the document's lifetime, the number of references obtained in the year following publication, and the number of references observed since 2018:</t><texttable> <ttcol align='left'>RFC(2008)</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Total</ttcol> <ttcol align='right'>2008-2009</ttcol> <ttcol align='right'>2018-2019</ttcol> <c>5326</c> <c>Exp</c> <c>138</c> <c>14</c> <c>15</c> <c>5348</c> <c>PS</c> <c>14</c> <c>3</c> <c>0</c> <c>5281</c> <c>Info</c> <c>69</c> <c>15</c> <c>7</c> <c>5354</c> <c>Exp</c> <c>17</c> <c>13</c> <c>0</c> <c>5227</c> <c>PS</c> <c>19</c> <c>1</c> <c>2</c> <c>5329</c> <c>PS</c> <c>24</c> <c>6</c> <c>1</c> <c>5277</c> <c>PS</c> <c>32</c> <c>3</c> <c>2</c> <c>5236</c> <c>ISE</c> <c>25</c> <c>5</c> <c>4</c> <c>5358</c> <c>BCP</c> <c>21</c> <c>2</c> <c>0</c> <c>5271</c> <c>Info</c> <c>7</c> <c>2</c> <c>0</c> <c>5195</c> <c>PS</c> <c>7</c> <c>4</c> <c>2</c> <c>5283</c> <c>PS</c> <c>8</c> <c>1</c> <c>0</c> <c>5186</c> <c>Info</c> <c>14</c> <c>4</c> <c>2</c> <c>5142</c> <c>PS</c> <c>8</c> <c>4</c> <c>0</c> <c>5373</c> <c>PS</c> <c>5</c> <c>2</c> <c>0</c> <c>5404</c> <c>PS</c> <c>1</c> <c>1</c> <c>0</c> <c>5172</c> <c>PS</c> <c>2</c> <c>0</c> <c>0</c> <c>5349</c> <c>Info</c> <c>8</c> <c>0</c> <c>2</c> <c>5301</c> <c>PS</c> <c>5</c> <c>1</c> <c>0</c> <c>5174</c> <c>Info</c> <c>0</c> <c>0</c> <c>0</c> </texttable> <texttable> <ttcol align='left'>RFC(1998)</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Total</ttcol> <ttcol align='right'>1998-1999</ttcol> <ttcol align='right'>2018-2019</ttcol> <c>2289</c> <c>PS</c> <c>2</c> <c>0</c> <c>1</c> <c>2267</c> <c>Info</c> <c>982</c> <c>5</c> <c>61</c> <c>2317</c> <c>BCP</c> <c>9</c> <c>1</c> <c>2</c> <c>2404</c> <c>PS</c> <c>137</c> <c>6</c> <c>1</c> <c>2374</c> <c>PS</c> <c>42</c> <c>4</c> <c>0</c> <c>2449</c> <c>PS</c> <c>7</c> <c>2</c> <c>0</c> <c>2283</c> <c>PS</c> <c>17</c> <c>3</c> <c>2</c> <c>2394</c> <c>Info</c> <c>13</c> <c>2</c> <c>1</c> <c>2348</c> <c>DS</c> <c>5</c> <c>0</c> <c>0</c> <c>2382</c> <c>Info</c> <c>17</c> <c>12</c> <c>0</c> <c>2297</c> <c>ISE</c> <c>36</c> <c>11</c> <c>0</c> <c>2381</c> <c>PS</c> <c>39</c> <c>12</c> <c>0</c> <c>2312</c> <c>Info</c> <c>14</c> <c>3</c> <c>0</c> <c>2387</c> <c>PS</c> <c>4</c> <c>1</c> <c>0</c> <c>2398</c> <c>Info</c> <c>17</c> <c>0</c> <c>1</c> <c>2391</c> <c>PS</c> <c>31</c> <c>3</c> <c>0</c> <c>2431</c> <c>PS</c> <c>3</c> <c>0</c> <c>0</c> <c>2282</c> <c>Info</c> <c>8</c> <c>0</c> <c>0</c> <c>2323</c> <c>ISE</c> <c>1</c> <c>0</c> <c>0</c> <c>2448</c> <c>ISE</c> <c>0</c> <c>0</c> <c>0</c> </texttable> <t>We<table align="center" pn="table-11"> <thead> <tr> <th align="left" colspan="1" rowspan="1">RFC(2008)</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Total</th> <th align="right" colspan="1" rowspan="1">2008-2009</th> <th align="right" colspan="1" rowspan="1">2018-2019</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">5326</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">138</td> <td align="right" colspan="1" rowspan="1">14</td> <td align="right" colspan="1" rowspan="1">15</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5348</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">14</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5281</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">69</td> <td align="right" colspan="1" rowspan="1">15</td> <td align="right" colspan="1" rowspan="1">7</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5354</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">17</td> <td align="right" colspan="1" rowspan="1">13</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5227</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">19</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5329</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">24</td> <td align="right" colspan="1" rowspan="1">6</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5277</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">32</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5236</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">25</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">4</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5358</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">21</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5271</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">7</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5195</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">7</td> <td align="right" colspan="1" rowspan="1">4</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5283</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5186</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">14</td> <td align="right" colspan="1" rowspan="1">4</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5142</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">4</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5373</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5404</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5172</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5349</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5301</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5174</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> </tbody> </table> <table align="center" pn="table-12"> <thead> <tr> <th align="left" colspan="1" rowspan="1">RFC (1998)</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Total</th> <th align="right" colspan="1" rowspan="1">1998-1999</th> <th align="right" colspan="1" rowspan="1">2018-2019</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">2289</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2267</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">982</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">61</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2317</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">9</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2404</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">137</td> <td align="right" colspan="1" rowspan="1">6</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2374</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">42</td> <td align="right" colspan="1" rowspan="1">4</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2449</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">7</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2283</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">17</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2394</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">13</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2348</td> <td align="left" colspan="1" rowspan="1">DS</td> <td align="right" colspan="1" rowspan="1">5</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2382</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">17</td> <td align="right" colspan="1" rowspan="1">12</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2297</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">36</td> <td align="right" colspan="1" rowspan="1">11</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2381</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">39</td> <td align="right" colspan="1" rowspan="1">12</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2312</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">14</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2387</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">4</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2398</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">17</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2391</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">31</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2431</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2282</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">8</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2323</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2448</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> </tr> </tbody> </table> <t indent="0" pn="section-5.2-4">We can compare the median number of citations and the numbers of citations for the least and most popular quartiles in the three years:</t><texttable> <ttcol align='left'>References</ttcol> <ttcol align='right'>Lower 25%</ttcol> <ttcol align='right'>Median</ttcol> <ttcol align='right'>Higher 25%</ttcol> <c>RFC (2018)</c> <c>0</c> <c>1</c> <c>3</c> <c>RFC (2008)</c> <c>6.5</c> <c>11</c> <c>21.75</c> <c>RFC<table align="center" pn="table-13"> <thead> <tr> <th align="left" colspan="1" rowspan="1">References</th> <th align="right" colspan="1" rowspan="1">Lower 25%</th> <th align="right" colspan="1" rowspan="1">Median</th> <th align="right" colspan="1" rowspan="1">Higher 25%</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">RFC (2018)</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">3</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">RFC (2008)</td> <td align="right" colspan="1" rowspan="1">6.5</td> <td align="right" colspan="1" rowspan="1">11</td> <td align="right" colspan="1" rowspan="1">21.75</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">RFC (2008), until2009</c> <c>1</c> <c>2.5</c> <c>4.5</c> <c>RFC2009</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">2.5</td> <td align="right" colspan="1" rowspan="1">4.5</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">RFC (2008), 2018 andafter</c> <c>0</c> <c>0</c> <c>2</c> <c>RFC (1998)</c> <c>4.75</c> <c>13.5</c> <c>32.25</c> <c>RFCafter</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">2</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">RFC (1998)</td> <td align="right" colspan="1" rowspan="1">4.75</td> <td align="right" colspan="1" rowspan="1">13.5</td> <td align="right" colspan="1" rowspan="1">32.25</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">RFC (1998), until1999</c> <c>0</c> <c>2</c> <c>4.25</c> <c>RFC1999</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">2</td> <td align="right" colspan="1" rowspan="1">4.25</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">RFC (1998), 2018 andafter</c> <c>0</c> <c>0</c> <c>1</c> </texttable> <t>Theafter</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">1</td> </tr> </tbody> </table> <t indent="0" pn="section-5.2-6">The total numbers show new documents with fewer citations than the older ones. This can be explained to some degree by the passage of time. If we restrict the analysis to the number of citations accrued in the year of publishing and the year after that, we still see about the same distribution for the three samples.</t><t>We<t indent="0" pn="section-5.2-7">We also see that the number of references toRFCRFCs fades over time. Only the most popular of the RFC produced in 1998 are still cited in 2019.</t> </section> <section anchor="citations-versus-deployments"title="Citations Versus Deployments"> <t>Thenumbered="true" toc="include" removeInRFC="false" pn="section-5.3"> <name slugifiedName="name-citations-versus-deployment">Citations versus Deployments</name> <t indent="0" pn="section-5.3-1">The following table shows side by side the number of citations as measured in <xreftarget="citation-numbers"/>target="citation-numbers" format="default" sectionFormat="of" derivedContent="Section 5.1"/> and the estimation of deployment as indicated in <xreftarget="sample-rfc-analysis"/>.</t> <texttable> <ttcol align='left'>RFC(2018)</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Citations</ttcol> <ttcol align='right'>Deployment</ttcol> <c>8411</c> <c>Info</c> <c>1</c> <c>medium</c> <c>8456</c> <c>Info</c> <c>1</c> <c>medium</c> <c>8446</c> <c>PS</c> <c>418</c> <c>high</c> <c>8355</c> <c>Info</c> <c>3</c> <c>medium</c> <c>8441</c> <c>PS</c> <c>1</c> <c>high</c> <c>8324</c> <c>ISE</c> <c>0</c> <c>N/A</c> <c>8377</c> <c>PS</c> <c>0</c> <c>unknown</c> <c>8498</c> <c>Info</c> <c>0</c> <c>unknown</c> <c>8479</c> <c>ISE</c> <c>0</c> <c>one</c> <c>8453</c> <c>Info</c> <c>3</c> <c>unknown</c> <c>8429</c> <c>BCP</c> <c>0</c> <c>some</c> <c>8312</c> <c>Info</c> <c>25</c> <c>high</c> <c>8492</c> <c>ISE</c> <c>4</c> <c>one</c> <c>8378</c> <c>Exp</c> <c>1</c> <c>some</c> <c>8361</c> <c>PS</c> <c>0</c> <c>one</c> <c>8472</c> <c>PS</c> <c>1</c> <c>medium</c> <c>8471</c> <c>PS</c> <c>1</c> <c>medium</c> <c>8466</c> <c>PS</c> <c>0</c> <c>unknown</c> <c>8362</c> <c>PS</c> <c>1</c> <c>medium</c> <c>8468</c> <c>Info</c> <c>1</c> <c>some</c> </texttable> <t>Fromtarget="sample-rfc-analysis" format="default" sectionFormat="of" derivedContent="Section 3"/>.</t> <table align="center" pn="table-14"> <thead> <tr> <th align="left" colspan="1" rowspan="1">RFC (2018)</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Citations</th> <th align="right" colspan="1" rowspan="1">Deployment</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">8411</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">medium</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8456</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">medium</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8446</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">418</td> <td align="right" colspan="1" rowspan="1">high</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8355</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">medium</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8441</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">high</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8324</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">N/A</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8377</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">unknown</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8498</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">unknown</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8479</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">one</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8453</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">unknown</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8429</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">some</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8312</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">25</td> <td align="right" colspan="1" rowspan="1">high</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8492</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">4</td> <td align="right" colspan="1" rowspan="1">one</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8378</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">some</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8361</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">one</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8472</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">medium</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8471</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">medium</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8466</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">unknown</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8362</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">medium</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8468</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">some</td> </tr> </tbody> </table> <t indent="0" pn="section-5.3-3">From looking at these results, it is fairly obvious that citation counts cannot be used as proxies for the "value" of an RFC. In our sample, the two RFCs that have high citation counts were both widely deployed, and can certainly be described as successful, but we also see many RFCs that saw significant deployment without garnering a high level of citations.</t><t>Citation<t indent="0" pn="section-5.3-4">Citation counts are driven by academic interest, but are only loosely correlated with actual deployment. We saw that <xreftarget="RFC8446"/>target="RFC8446" format="default" sectionFormat="of" derivedContent="RFC8446"/> was widely cited in part because the standardization process involved many researchers, and that the high citation count of <xreftarget="RFC8312"/>target="RFC8312" format="default" sectionFormat="of" derivedContent="RFC8312"/> is largely due to the academic interest in evaluating congestion control protocols. If we look at previous years, the most cited RFC in the 2008 sample is <xreftarget="RFC5326"/>,target="RFC5326" format="default" sectionFormat="of" derivedContent="RFC5326"/>, an experimental RFC defining security extensions to an experimental delay tolerant transport protocol. This protocol does not carry a significant proportion of Internet traffic, but has been the object of a fair number of academic studies.</t><t>The<t indent="0" pn="section-5.3-5">The citation process tends to privilege the first expression of a concept. We see that with the most cited RFC in the 1998 set is <xreftarget="RFC2267"/>,target="RFC2267" format="default" sectionFormat="of" derivedContent="RFC2267"/>, an informational RFC defining Network Ingress Filtering that was obsoleted in May 2000 by <xreftarget="RFC2827"/>.target="RFC2827" format="default" sectionFormat="of" derivedContent="RFC2827"/>. It is still cited frequently in 2018 and 2019, regardless of its formal status in the RFCseries.Series. We see the same effect at work with <xreftarget="RFC8441"/>,target="RFC8441" format="default" sectionFormat="of" derivedContent="RFC8441"/>, which garners very few citations although itobsoletesupdates <xreftarget="RFC6455"/>target="RFC6455" format="default" sectionFormat="of" derivedContent="RFC6455"/> that has a large number of citations. The same goes for <xreftarget="RFC8468"/>,target="RFC8468" format="default" sectionFormat="of" derivedContent="RFC8468"/>, which is sparsely cited while the <xreftarget="RFC2330"/>target="RFC2330" format="default" sectionFormat="of" derivedContent="RFC2330"/> is widely cited. Just counting citations will not indicate whether developers still use an old specification or have adopted the revised RFC.</t> </section> <section anchor="citations-versus-web-references"title="Citations Versusnumbered="true" toc="include" removeInRFC="false" pn="section-5.4"> <name slugifiedName="name-citations-versus-web-refere">Citations versus WebReferences"> <t>WebReferences</name> <t indent="0" pn="section-5.4-1">Web references might be another indicator of the popularity of an RFC. In order to evaluate these references, we list here the number of results returned by searches on Google and Bing, looking for the search term "RFCnnnn" (e.g.,RFC8411),"RFC8411"), and copying the number of results returned by the search engines. The table below presents the results of these searches, performed on April 4, 2020.</t><texttable> <ttcol align='left'>RFC(2018)</ttcol> <ttcol align='left'>Status</ttcol> <ttcol align='right'>Citations</ttcol> <ttcol align='right'>Google</ttcol> <ttcol align='right'>Bing</ttcol> <c>8411</c> <c>Info</c> <c>1</c> <c>301</c> <c>94</c> <c>8456</c> <c>Info</c> <c>1</c> <c>266</c> <c>8456</c> <c>8446</c> <c>PS</c> <c>418</c> <c>25900</c> <c>47800</c> <c>8355</c> <c>Info</c> <c>3</c> <c>521</c> <c>114</c> <c>8441</c> <c>PS</c> <c>1</c> <c>2430</c> <c>59500</c> <c>8324</c> <c>ISE</c> <c>0</c> <c>393</c> <c>138</c> <c>8377</c> <c>PS</c> <c>0</c> <c>264</c> <c>10900</c> <c>8498</c> <c>Info</c> <c>0</c> <c>335</c> <c>10100</c> <c>8479</c> <c>ISE</c> <c>0</c> <c>564</c> <c>11000</c> <c>8453</c> <c>Info</c> <c>3</c> <c>817</c> <c>11400</c> <c>8429</c> <c>BCP</c> <c>0</c> <c>391</c> <c>41600</c> <c>8312</c> <c>Info</c> <c>25</c> <c>1620</c> <c>2820</c> <c>8492</c> <c>ISE</c> <c>4</c> <c>323</c> <c>9400</c> <c>8378</c> <c>Exp</c> <c>1</c> <c>418</c> <c>11600</c> <c>8361</c> <c>PS</c> <c>0</c> <c>499</c> <c>92</c> <c>8472</c> <c>PS</c> <c>1</c> <c>496</c> <c>169</c> <c>8471</c> <c>PS</c> <c>1</c> <c>1510</c> <c>11600</c> <c>8466</c> <c>PS</c> <c>0</c> <c>766</c> <c>173</c> <c>8362</c> <c>PS</c> <c>1</c> <c>67</c> <c>147</c> <c>8468</c> <c>Info</c> <c>1</c> <c>453</c> <c>127</c> </texttable> <t>The results<table align="center" pn="table-15"> <thead> <tr> <th align="left" colspan="1" rowspan="1">RFC(2018)</th> <th align="left" colspan="1" rowspan="1">Status</th> <th align="right" colspan="1" rowspan="1">Citations</th> <th align="right" colspan="1" rowspan="1">Google</th> <th align="right" colspan="1" rowspan="1">Bing</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">8411</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">301</td> <td align="right" colspan="1" rowspan="1">94</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8456</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">266</td> <td align="right" colspan="1" rowspan="1">8456</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8446</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">418</td> <td align="right" colspan="1" rowspan="1">25900</td> <td align="right" colspan="1" rowspan="1">47800</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8355</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">521</td> <td align="right" colspan="1" rowspan="1">114</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8441</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">2430</td> <td align="right" colspan="1" rowspan="1">59500</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8324</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">393</td> <td align="right" colspan="1" rowspan="1">138</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8377</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">264</td> <td align="right" colspan="1" rowspan="1">10900</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8498</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">335</td> <td align="right" colspan="1" rowspan="1">10100</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8479</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">564</td> <td align="right" colspan="1" rowspan="1">11000</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8453</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">3</td> <td align="right" colspan="1" rowspan="1">817</td> <td align="right" colspan="1" rowspan="1">11400</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8429</td> <td align="left" colspan="1" rowspan="1">BCP</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">391</td> <td align="right" colspan="1" rowspan="1">41600</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8312</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">25</td> <td align="right" colspan="1" rowspan="1">1620</td> <td align="right" colspan="1" rowspan="1">2820</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8492</td> <td align="left" colspan="1" rowspan="1">Info (ISE)</td> <td align="right" colspan="1" rowspan="1">4</td> <td align="right" colspan="1" rowspan="1">323</td> <td align="right" colspan="1" rowspan="1">9400</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8378</td> <td align="left" colspan="1" rowspan="1">Exp</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">418</td> <td align="right" colspan="1" rowspan="1">11600</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8361</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">499</td> <td align="right" colspan="1" rowspan="1">92</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8472</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">496</td> <td align="right" colspan="1" rowspan="1">169</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8471</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">1510</td> <td align="right" colspan="1" rowspan="1">11600</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8466</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">0</td> <td align="right" colspan="1" rowspan="1">766</td> <td align="right" colspan="1" rowspan="1">173</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8362</td> <td align="left" colspan="1" rowspan="1">PS</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">67</td> <td align="right" colspan="1" rowspan="1">147</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8468</td> <td align="left" colspan="1" rowspan="1">Info</td> <td align="right" colspan="1" rowspan="1">1</td> <td align="right" colspan="1" rowspan="1">453</td> <td align="right" colspan="1" rowspan="1">127</td> </tr> </tbody> </table> <t indent="0" pn="section-5.4-3">The result counts from Bing are sometimes surprising. Why would RFC 8441 gather 59,500 web references? Looking at the results in detail, we find a mix of data. Some of them are logs of development projects implementing Web Sockets, which is exactly what we are looking for, but others appear spurious. For example, a shop selling rugby jerseys is listed because its phone number ends with "8441". Other pages were listed because street numbers or product numbers matched the RFC number. The same type of collision may explain the large reference counts on Bing forRFCRFCs 8377, 8498, 8479, 8453, 8429, 8378, and 8471. The result counts on Bing do not appear to provide a good metric.</t><t>On<t indent="0" pn="section-5.4-4">On Google, allRFCRFCs garner at least a 250 references, largely because the whole RFC catalog is replicated on a large number of web servers. Deviations from thatbase linebaseline are largely correlated with the number of citations in the Semantic Scholar, with a couple of exception: RFC8441,8441 and RFC 8471 garner more references than the low citation counts would predict. Looking at the results, we find many references in development databases explaining how these protocols are implemented in various code bases and open source projects. This means that counting Google results would give some indication about an RFC's popularity, complementing the citation counts.</t><t>There<t indent="0" pn="section-5.4-5">There are some practical problems in using the counts of Google results. Google searches are personalized, the results depend on the source of the queries, and the counts may vary as well. The searchresultresults depend on the search algorithm, and there is no guarantee that counts will not change when the algorithm changes. On the other hand, the results do indicate that some of theRFCRFCs in our sample arebeeingbeing used by developers or in deployments.</t> </section> </section> <section anchor="conclusion"title="Observationsnumbered="true" toc="include" removeInRFC="false" pn="section-6"> <name slugifiedName="name-observations-and-next-steps">Observations and NextSteps"> <t>TheSteps</name> <t indent="0" pn="section-6-1">The author's goal was to get a personal understanding of the "chain of production" of the RFCs, and in particular to look at the various causes of delays in the process. As shown in <xreftarget="process-analysis"/>,target="process-analysis" format="default" sectionFormat="of" derivedContent="Section 4"/>, the average RFC was produced in 3 years and 4 months, which is similar to what was found in the 2008 sample, but more than three times larger than the delays for the 1998 sample.</t><t>The Working Group<t indent="0" pn="section-6-2">The working group process appears to be the main source of delays. Efforts to diminish delays should probably focus there, instead of on the IETF and IESG reviewsofor the RFC production. For the RFC production phase, most of the variability originates in theAUTH-48AUTH48 process, which is influenced by a variety of factors such as number of authors or level of engagement of these authors.</t><t>Most<t indent="0" pn="section-6-3">Most of the delay is spent in theWorking Group,working group, but the IETFdatatrackerDatatracker does not hold much information about what happens inside theWorking Groups.working groups. For example, events like Working Group Last Calls were not recorded in the history of the selected drafts available in thedatatracker.Datatracker. Such information would have been interesting. Of course, requiring that information would create an administrative burden, so there is clearly a trade-off between requiring more work from working group chairs and providing better data for process analysis. (It appears that this information can be available in thedatatrackerDatatracker for more recent drafts, if the WG chairs use thedatatrackerDatatracker properly.)</t><t>The<t indent="0" pn="section-6-4">The Independent Stream operates as expected. The majority of the authors of the Independent Stream RFCs appear to be in IETF insiders, but there is significant amount of engagement by outside parties.</t><t>The<t indent="0" pn="section-6-5">The analysis of citations in <xreftarget="citation-numbers"/>target="citation-numbers" format="default" sectionFormat="of" derivedContent="Section 5.1"/> shows that citation numbers are a very poor indication of the "value" of an RFC. Citation numbers measure the engagement of academic researchers with specific topics, but have little correlation with the level of adoption and deployment of a specific RFC. The result counts of Google searches do capture references outside academia, such as logs of development projects. This might be informative, but it is not clear that the counts would not change over time due to algorithm changes orpersonaliztion.</t> <t>Thispersonalization.</t> <t indent="0" pn="section-6-6">This document analyses a small sample of RFCs "in depth". This allowed gathering of detailed feedback on the process and the deployments. On the other hand, much of the data on delays is available from the IETFdatatracker.Datatracker. It may be worth considering adding an automated reporting of delay metrics in the IETFdatatracker.</t> <t>ThisDatatracker.</t> <t indent="0" pn="section-6-7">This document only considers the RFCs that were published in a given year. This approach can be criticized as introducing a form of "survivor bias". There are many drafts proposed to the IETF, and only a fraction of them end up being published as RFCs. On onehandhand, this is expected, because part of the process is to triage between ideas that can gather consensus and those that don't. On the other hand, we don't know whether that triage is too drastic and has discouraged progress on good ideas.</t><t>One<t indent="0" pn="section-6-8">One way to evaluate the triage process would be to look at publication attempts that wereabandoned,abandoned -- forexampleexample, drafts that expired without progressing or being replaced. The sampling methodology could also be used for that purpose. Pick maybe 20 drafts at random, among those abandoned in a target year, and investigate why they were abandoned. Was it because better solutions emerged in theWorking Group?working group? Or maybe because the authors discovered a flaw in their proposal? Or was it because some factional struggle blocked a good idea? Was the idea pursued in a different venue? Hopefully, someone will try this kind of investigation.</t> </section> <section anchor="security-considerations"title="Security Considerations"> <t>This draftnumbered="true" toc="include" removeInRFC="false" pn="section-7"> <name slugifiedName="name-security-considerations">Security Considerations</name> <t indent="0" pn="section-7-1">This document does not specify any protocol.</t><t>We<t indent="0" pn="section-7-2">We might want to analyze whether security issues were discovered after publication of specific standards.</t> </section> <section anchor="iana-considerations"title="IANA Considerations"> <t>This draft does not require anynumbered="true" toc="include" removeInRFC="false" pn="section-8"> <name slugifiedName="name-iana-considerations">IANA Considerations</name> <t indent="0" pn="section-8-1">This document has no IANAaction.</t> <t>Peliminaryactions.</t> <t indent="0" pn="section-8-2">Preliminary analysis does not indicate that IANA is causing any particular delay in the RFC publication process.</t> </section><section anchor="acknowledgements" title="Acknowledgements"> <t>Many thanks to the authors of the selected RFCs who were willing to provide feedback on the process: Michael Ackermann, Zafar Ali, Sarah Banks, Bruno Decraene, Lars Eggert, Nalini Elkins, Joachim Fabini, Dino Farinacci, Clarence Filsfils, Sujay Gupta, Dan Harkins, Vinayak Hegde, Benjamin Kaduk, John Klensin, Acee Lindem, Nikos Mavrogiannopoulos, Patrick McManus, Victor Moreno, Al Morton, Andrei Popov, Eric Rescorla, Michiko Short, Bhuvaneswaran Vengainathan, Lao Weiguo, and Li Yizhou. Many thanks to Adrian Farrel for his useful advice, to Stephen Farrell and Colin Perkins for their guidance on the use of citations, and to Dave Crocker for a comprehensive review.</t> </section></middle> <back> <displayreference target="I-D.ietf-rtgwg-segment-routing-ti-lfa" to="TI-LFA"/> <referencestitle='Informative References'>pn="section-9"> <name slugifiedName="name-informative-references">Informative References</name> <referenceanchor="TRKR" target="https://datatracker.ietf.org/">anchor="IETFCOUNT" target="https://www.ietf.org/how/meetings/past/" quoteTitle="true" derivedAnchor="IETFCOUNT"> <front><title>IETF Data Tracker</title> <author > <organization>IETF</organization><title>Past IETF Meetings</title> <author> <organization showOnFrontPage="true">IETF</organization> </author><date year="2020"/></front> </reference> <referenceanchor="SSCH" target="https://www.semanticscholar.org/">anchor="RFC2267" target="https://www.rfc-editor.org/info/rfc2267" quoteTitle="true" derivedAnchor="RFC2267"> <front><title>Semantic Scholar</title><title>Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing</title> <author> <organization>Allen Institute for AI</organization>initials="P." surname="Ferguson" fullname="P. Ferguson"> <organization showOnFrontPage="true"/> </author><date year="2020"/> </front> </reference> <reference anchor="TLS13IMP" target="https://github.com/tlswg/tlswg-wiki/blob/master/IMPLEMENTATIONS.md"> <front> <title>TLS 1.3 Implementations</title><author> <organization>TLS WG</organization>initials="D." surname="Senie" fullname="D. Senie"> <organization showOnFrontPage="true"/> </author> <dateyear="2020"/>year="1998" month="January"/> <abstract> <t indent="0">This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS attacks which use forged IP addresses to be propagated from 'behind' an Internet Service Provider's (ISP) aggregation point. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.</t> </abstract> </front> <seriesInfo name="RFC" value="2267"/> <seriesInfo name="DOI" value="10.17487/RFC2267"/> </reference> <referenceanchor="RFCYEAR" target="https://www.rfc-editor.org/rfcs-per-year/">anchor="RFC2330" target="https://www.rfc-editor.org/info/rfc2330" quoteTitle="true" derivedAnchor="RFC2330"> <front><title>Number of RFC Published per YEAR</title><title>Framework for IP Performance Metrics</title> <author> <organization>RFC Editor</organization>initials="V." surname="Paxson" fullname="V. Paxson"> <organization showOnFrontPage="true"/> </author><date year="2020"/> </front> </reference> <reference anchor="IETFCOUNT" target="https://www.ietf.org/how/meetings/past/"> <front> <title>Past IETF Meetings</title><author> <organization>IETF</organization>initials="G." surname="Almes" fullname="G. Almes"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Mahdavi" fullname="J. Mahdavi"> <organization showOnFrontPage="true"/> </author><date year="2020"/> </front> </reference> <reference anchor="RFC8411" target='https://www.rfc-editor.org/info/rfc8411'> <front> <title>IANA Registration for the Cryptographic Algorithm Object Identifier Range</title><authorinitials='J.' surname='Schaad' fullname='J. Schaad'><organization /></author> <author initials='R.' surname='Andrews' fullname='R. Andrews'><organization /></author>initials="M." surname="Mathis" fullname="M. Mathis"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='August' /> <abstract><t>When the Curdle Security Working Group was chartered, a range of object identifiers was donated by DigiCert, Inc. for theyear="1998" month="May"/> <abstract> <t indent="0">The purpose ofregistering the Edwards Elliptic Curve key agreement and signature algorithms. This donated set of OIDs allowedthis memo is to define a general framework forshorter values than wouldparticular metrics to bepossible usingdeveloped by theexisting S/MIME or PKIX arcs.IETF's IP Performance Metrics effort. Thisdocument describes the donated range andmemo provides information for theidentifiers that were assigned from that range, transfers controlInternet community. It does not specify an Internet standard ofthat range to IANA, and establishes IANA allocation policies foranyfuture assignments within that range.</t></abstract>kind.</t> </abstract> </front> <seriesInfoname='RFC' value='8411'/>name="RFC" value="2330"/> <seriesInfoname='DOI' value='10.17487/RFC8411'/>name="DOI" value="10.17487/RFC2330"/> </reference> <referenceanchor="RFC8410" target='https://www.rfc-editor.org/info/rfc8410'>anchor="RFC2827" target="https://www.rfc-editor.org/info/rfc2827" quoteTitle="true" derivedAnchor="RFC2827"> <front><title>Algorithm Identifiers for Ed25519, Ed448, X25519,<title>Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing</title> <author initials="P." surname="Ferguson" fullname="P. Ferguson"> <organization showOnFrontPage="true"/> </author> <author initials="D." surname="Senie" fullname="D. Senie"> <organization showOnFrontPage="true"/> </author> <date year="2000" month="May"/> <abstract> <t indent="0">This paper discusses a simple, effective, andX448straightforward method forUse in theusing ingress traffic filtering to prohibit DoS (Denial of Service) attacks which use forged IP addresses to be propagated from 'behind' an InternetX.509 Public Key Infrastructure</title> <author initials='S.' surname='Josefsson' fullname='S. Josefsson'><organization /></author> <author initials='J.' surname='Schaad' fullname='J. Schaad'><organization /></author> <date year='2018' month='August' /> <abstract><t>ThisService Provider's (ISP) aggregation point. This document specifiesalgorithm identifiers and ASN.1 encoding formatsan Internet Best Current Practices forelliptic curve constructs usingthecurve25519 and curve448 curves. The signature algorithms covered are Ed25519Internet Community, andEd448. The key agreement algorithms covered are X25519requests discussion andX448. The encodingsuggestions forpublic key, private key, and Edwards-curve Digital Signature Algorithm (EdDSA) structures is provided.</t></abstract>improvements.</t> </abstract> </front> <seriesInfoname='RFC' value='8410'/>name="BCP" value="38"/> <seriesInfo name="RFC" value="2827"/> <seriesInfoname='DOI' value='10.17487/RFC8410'/>name="DOI" value="10.17487/RFC2827"/> </reference> <referenceanchor="RFC8456" target='https://www.rfc-editor.org/info/rfc8456'>anchor="RFC5326" target="https://www.rfc-editor.org/info/rfc5326" quoteTitle="true" derivedAnchor="RFC5326"> <front><title>Benchmarking Methodology for Software-Defined Networking (SDN) Controller Performance</title><title>Licklider Transmission Protocol - Specification</title> <author initials="M." surname="Ramadas" fullname="M. Ramadas"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Burleigh" fullname="S. Burleigh"> <organization showOnFrontPage="true"/> </author> <authorinitials='V.' surname='Bhuvaneswaran' fullname='V. Bhuvaneswaran'><organization /></author> <author initials='A.' surname='Basil' fullname='A. Basil'><organization /></author> <author initials='M.' surname='Tassinari' fullname='M. Tassinari'><organization /></author> <author initials='V.' surname='Manral' fullname='V. Manral'><organization /></author> <author initials='S.' surname='Banks' fullname='S. Banks'><organization /></author>initials="S." surname="Farrell" fullname="S. Farrell"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='October' /> <abstract><t>Thisyear="2008" month="September"/> <abstract> <t indent="0">This documentdefines methodologies for benchmarking the control-plane performance of Software-Defined Networking (SDN) Controllers. The SDN Controller is a core component in the SDN architecture that controls the behavior ofdescribes thenetwork. SDN Controllers have been implemented with many varying designs in orderLicklider Transmission Protocol (LTP), designed toachieve their intended network functionality. Hence,provide retransmission-based reliability over links characterized by extremely long message round-trip times (RTTs) and/or frequent interruptions in connectivity. Since communication across interplanetary space is theauthorsmost prominent example of thisdocument have taken the approachsort ofconsidering an SDN Controller to be a black box, defining the methodologyenvironment, LTP is principally aimed at supporting "long-haul" reliable transmission ina manner thatinterplanetary space, but it has applications in other environments as well.</t> <t indent="0">This document isagnostic to protocolsa product of the Delay Tolerant Networking Research Group andnetwork services supportedhas been reviewed bycontrollers.that group. No objections to its publication as an RFC were raised. Thisdocument provides a methodmemo defines an Experimental Protocol formeasuringtheperformance of all controller implementations.</t></abstract>Internet community.</t> </abstract> </front> <seriesInfoname='RFC' value='8456'/>name="RFC" value="5326"/> <seriesInfoname='DOI' value='10.17487/RFC8456'/>name="DOI" value="10.17487/RFC5326"/> </reference> <referenceanchor="RFC8455" target='https://www.rfc-editor.org/info/rfc8455'>anchor="RFC6455" target="https://www.rfc-editor.org/info/rfc6455" quoteTitle="true" derivedAnchor="RFC6455"> <front><title>Terminology for Benchmarking Software-Defined Networking (SDN) Controller Performance</title><title>The WebSocket Protocol</title> <authorinitials='V.' surname='Bhuvaneswaran' fullname='V. Bhuvaneswaran'><organization /></author> <author initials='A.' surname='Basil' fullname='A. Basil'><organization /></author> <author initials='M.' surname='Tassinari' fullname='M. Tassinari'><organization /></author> <author initials='V.' surname='Manral' fullname='V. Manral'><organization /></author> <author initials='S.' surname='Banks' fullname='S. Banks'><organization /></author>initials="I." surname="Fette" fullname="I. Fette"> <organization showOnFrontPage="true"/> </author> <author initials="A." surname="Melnikov" fullname="A. Melnikov"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='October' /> <abstract><t>This document defines terminology for benchmarkingyear="2011" month="December"/> <abstract> <t indent="0">The WebSocket Protocol enables two-way communication between aSoftware-Defined Networking (SDN) controller's control-plane performance. It extends the terminology already definedclient running untrusted code inRFC 7426a controlled environment to a remote host that has opted-in to communications from that code. The security model used forthe purpose of benchmarking SDN Controllers. The terms provided in this document help to benchmark an SDN Controller's performance independently of the controller's supported protocols and/or network services.</t></abstract> </front> <seriesInfo name='RFC' value='8455'/> <seriesInfo name='DOI' value='10.17487/RFC8455'/> </reference> <reference anchor="RFC8446" target='https://www.rfc-editor.org/info/rfc8446'> <front> <title>The Transport Layer Security (TLS) Protocol Version 1.3</title> <author initials='E.' surname='Rescorla' fullname='E. Rescorla'><organization /></author> <date year='2018' month='August' /> <abstract><t>This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t><t>This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.</t></abstract> </front> <seriesInfo name='RFC' value='8446'/> <seriesInfo name='DOI' value='10.17487/RFC8446'/> </reference> <reference anchor="RFC8355" target='https://www.rfc-editor.org/info/rfc8355'> <front> <title>Resiliency Use Cases in Source Packet Routing in Networking (SPRING) Networks</title> <author initials='C.' surname='Filsfils' fullname='C. Filsfils' role='editor'><organization /></author> <author initials='S.' surname='Previdi' fullname='S. Previdi' role='editor'><organization /></author> <author initials='B.' surname='Decraene' fullname='B. Decraene'><organization /></author> <author initials='R.' surname='Shakir' fullname='R. Shakir'><organization /></author> <date year='2018' month='March' /> <abstract><t>This document identifies and describes the requirements for a set of use cases related to Segment Routing network resiliency on Source Packet Routing in Networking (SPRING) networks.</t></abstract> </front> <seriesInfo name='RFC' value='8355'/> <seriesInfo name='DOI' value='10.17487/RFC8355'/> </reference> <reference anchor="RFC8441" target='https://www.rfc-editor.org/info/rfc8441'> <front> <title>Bootstrapping WebSockets with HTTP/2</title> <author initials='P.' surname='McManus' fullname='P. McManus'><organization /></author> <date year='2018' month='September' /> <abstract><t>This document defines a mechanism for running the WebSocket Protocol (RFC 6455) over a single stream of an HTTP/2 connection.</t></abstract> </front> <seriesInfo name='RFC' value='8441'/> <seriesInfo name='DOI' value='10.17487/RFC8441'/> </reference> <reference anchor="RFC6455" target='https://www.rfc-editor.org/info/rfc6455'> <front> <title>The WebSocket Protocol</title> <author initials='I.' surname='Fette' fullname='I. Fette'><organization /></author> <author initials='A.' surname='Melnikov' fullname='A. Melnikov'><organization /></author> <date year='2011' month='December' /> <abstract><t>The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this isthis is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or <iframe>s and long polling).[STANDARDS-TRACK]</t></abstract>[STANDARDS-TRACK]</t> </abstract> </front> <seriesInfoname='RFC' value='6455'/>name="RFC" value="6455"/> <seriesInfoname='DOI' value='10.17487/RFC6455'/>name="DOI" value="10.17487/RFC6455"/> </reference> <referenceanchor="RFC8324" target='https://www.rfc-editor.org/info/rfc8324'>anchor="RFC8312" target="https://www.rfc-editor.org/info/rfc8312" quoteTitle="true" derivedAnchor="RFC8312"> <front><title>DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time<title>CUBIC forAnother Look?</title>Fast Long-Distance Networks</title> <author initials="I." surname="Rhee" fullname="I. Rhee"> <organization showOnFrontPage="true"/> </author> <author initials="L." surname="Xu" fullname="L. Xu"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Ha" fullname="S. Ha"> <organization showOnFrontPage="true"/> </author> <author initials="A." surname="Zimmermann" fullname="A. Zimmermann"> <organization showOnFrontPage="true"/> </author> <author initials="L." surname="Eggert" fullname="L. Eggert"> <organization showOnFrontPage="true"/> </author> <authorinitials='J.' surname='Klensin' fullname='J. Klensin'><organization /></author>initials="R." surname="Scheffenegger" fullname="R. Scheffenegger"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='February' /> <abstract><t>The basic design of the Domain Nameyear="2018" month="February"/> <abstract> <t indent="0">CUBIC is an extension to the current TCP standards. It differs from the current TCP standards only in the congestion control algorithm on the sender side. In particular, it uses a cubic function instead of a linear window increase function of the current TCP standards to improve scalability and stability under fast and long-distance networks. CUBIC and its predecessor algorithm have been adopted as defaults by Linux and have been used for many years. This document provides a specification of CUBIC to enable third-party implementations and to solicit community feedback through experimentation on the performance of CUBIC.</t> </abstract> </front> <seriesInfo name="RFC" value="8312"/> <seriesInfo name="DOI" value="10.17487/RFC8312"/> </reference> <reference anchor="RFC8324" target="https://www.rfc-editor.org/info/rfc8324" quoteTitle="true" derivedAnchor="RFC8324"> <front> <title>DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for Another Look?</title> <author initials="J." surname="Klensin" fullname="J. Klensin"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="February"/> <abstract> <t indent="0">The basic design of the Domain Name System was completed almost 30 years ago. The last half of that period has been characterized by significant changes in requirements and expectations, some of which either require changes to how the DNS is used or can be accommodated only poorly or not at all. This document asks the question of whether it is time to either redesign and replace the DNS to match contemporary requirements and expectations (rather than continuing to try to design and implement incremental patches that are not fully satisfactory) or draw some clear lines about functionality that is not really needed or that should be performed in some otherway.</t></abstract>way.</t> </abstract> </front> <seriesInfoname='RFC' value='8324'/>name="RFC" value="8324"/> <seriesInfoname='DOI' value='10.17487/RFC8324'/>name="DOI" value="10.17487/RFC8324"/> </reference> <referenceanchor="RFC8377" target='https://www.rfc-editor.org/info/rfc8377'>anchor="RFC8355" target="https://www.rfc-editor.org/info/rfc8355" quoteTitle="true" derivedAnchor="RFC8355"> <front><title>Transparent Interconnection of Lots of Links (TRILL): Multi-Topology</title><title>Resiliency Use Cases in Source Packet Routing in Networking (SPRING) Networks</title> <authorinitials='D.' surname='Eastlake 3rd' fullname='D. Eastlake 3rd'><organization /></author>initials="C." surname="Filsfils" fullname="C. Filsfils" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Previdi" fullname="S. Previdi" role="editor"> <organization showOnFrontPage="true"/> </author> <authorinitials='M.' surname='Zhang' fullname='M. Zhang'><organization /></author> <author initials='A.' surname='Banerjee' fullname='A. Banerjee'><organization /></author>initials="B." surname="Decraene" fullname="B. Decraene"> <organization showOnFrontPage="true"/> </author> <author initials="R." surname="Shakir" fullname="R. Shakir"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='July' /> <abstract><t>Thisyear="2018" month="March"/> <abstract> <t indent="0">This documentspecifies extensions toidentifies and describes theIETF TRILL (Transparent Interconnection of Lotsrequirements for a set ofLinks) protocoluse cases related tosupport multi-topology routing of unicast and multi-destination traffic basedSegment Routing network resiliency onIS-IS (Intermediate System to Intermediate System) multi-topology specifiedSource Packet Routing inRFC 5120. This document updates RFCs 6325 and 7177.</t></abstract>Networking (SPRING) networks.</t> </abstract> </front> <seriesInfoname='RFC' value='8377'/>name="RFC" value="8355"/> <seriesInfoname='DOI' value='10.17487/RFC8377'/>name="DOI" value="10.17487/RFC8355"/> </reference> <referenceanchor="RFC8498" target='https://www.rfc-editor.org/info/rfc8498'>anchor="RFC8361" target="https://www.rfc-editor.org/info/rfc8361" quoteTitle="true" derivedAnchor="RFC8361"> <front><title>A P-Served-User Header Field Parameter<title>Transparent Interconnection of Lots of Links (TRILL): Centralized Replication foran Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)</title>Active-Active Broadcast, Unknown Unicast, and Multicast (BUM) Traffic</title> <authorinitials='M.' surname='Mohali' fullname='M. Mohali'><organization /></author> <date year='2019' month='February' /> <abstract><t>The P-Served-User header fieldinitials="W." surname="Hao" fullname="W. Hao"> <organization showOnFrontPage="true"/> </author> <author initials="Y." surname="Li" fullname="Y. Li"> <organization showOnFrontPage="true"/> </author> <author initials="M." surname="Durrani" fullname="M. Durrani"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Gupta" fullname="S. Gupta"> <organization showOnFrontPage="true"/> </author> <author initials="A." surname="Qu" fullname="A. Qu"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="April"/> <abstract> <t indent="0">In Transparent Interconnection of Lots of Links (TRILL) active-active access, a Reverse Path Forwarding (RPF) check failure issue may occur when using the pseudo-nickname mechanism specified in RFC 7781. This document describes a solution to resolve this RPF check failure issue through centralized replication. All ingress Routing Bridges (RBridges) send Broadcast, Unknown Unicast, and Multicast (BUM) traffic to a centralized node with unicast TRILL encapsulation. When the centralized node receives the BUM traffic, it decapsulates the packets and forwards them to their destination RBridges using a distribution tree established per the TRILL base protocol (RFC 6325). To avoid RPF check failure on an RBridge sitting between the ingress RBridge and the centralized replication node, some change in the RPF calculation algorithm is required. RPF checks on each RBridge MUST be calculated as if the centralized node wasdefinedthe ingress RBridge, instead of being calculated using the actual ingress RBridge. This document updates RFC 6325.</t> </abstract> </front> <seriesInfo name="RFC" value="8361"/> <seriesInfo name="DOI" value="10.17487/RFC8361"/> </reference> <reference anchor="RFC8362" target="https://www.rfc-editor.org/info/rfc8362" quoteTitle="true" derivedAnchor="RFC8362"> <front> <title>OSPFv3 Link State Advertisement (LSA) Extensibility</title> <author initials="A." surname="Lindem" fullname="A. Lindem"> <organization showOnFrontPage="true"/> </author> <author initials="A." surname="Roy" fullname="A. Roy"> <organization showOnFrontPage="true"/> </author> <author initials="D." surname="Goethals" fullname="D. Goethals"> <organization showOnFrontPage="true"/> </author> <author initials="V." surname="Reddy Vallem" fullname="V. Reddy Vallem"> <organization showOnFrontPage="true"/> </author> <author initials="F." surname="Baker" fullname="F. Baker"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="April"/> <abstract> <t indent="0">OSPFv3 requires functional extension beyond what can readily be done with the fixed-format Link State Advertisement (LSA) as described in RFC 5340. Without LSA extension, attributes associated with OSPFv3 links and advertised IPv6 prefixes must be advertised in separate LSAs and correlated to the fixed-format LSAs. This document extends the LSA format by encoding the existing OSPFv3 LSA information in Type-Length-Value (TLV) tuples and allowing advertisement of additional information with additional TLVs. Backward-compatibility mechanisms are also described.</t> <t indent="0">This document updates RFC 5340, "OSPF for IPv6", and RFC 5838, "Support of Address Families in OSPFv3", by providing TLV-based encodings for the base OSPFv3 unicast support and OSPFv3 address family support.</t> </abstract> </front> <seriesInfo name="RFC" value="8362"/> <seriesInfo name="DOI" value="10.17487/RFC8362"/> </reference> <reference anchor="RFC8377" target="https://www.rfc-editor.org/info/rfc8377" quoteTitle="true" derivedAnchor="RFC8377"> <front> <title>Transparent Interconnection of Lots of Links (TRILL): Multi-Topology</title> <author initials="D." surname="Eastlake 3rd" fullname="D. Eastlake 3rd"> <organization showOnFrontPage="true"/> </author> <author initials="M." surname="Zhang" fullname="M. Zhang"> <organization showOnFrontPage="true"/> </author> <author initials="A." surname="Banerjee" fullname="A. Banerjee"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="July"/> <abstract> <t indent="0">This document specifies extensions to the IETF TRILL (Transparent Interconnection of Lots of Links) protocol to support multi-topology routing of unicast and multi-destination traffic based ona requirementIS-IS (Intermediate System to Intermediate System) multi-topology specified in RFC 5120. This document updates RFCs 6325 and 7177.</t> </abstract> </front> <seriesInfo name="RFC" value="8377"/> <seriesInfo name="DOI" value="10.17487/RFC8377"/> </reference> <reference anchor="RFC8378" target="https://www.rfc-editor.org/info/rfc8378" quoteTitle="true" derivedAnchor="RFC8378"> <front> <title>Signal-Free Locator/ID Separation Protocol (LISP) Multicast</title> <author initials="V." surname="Moreno" fullname="V. Moreno"> <organization showOnFrontPage="true"/> </author> <author initials="D." surname="Farinacci" fullname="D. Farinacci"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="May"/> <abstract> <t indent="0">When multicast sources and receivers are active at Locator/ID Separation Protocol (LISP) sites, the core network is required to use native multicast so packets can be delivered from sources to group members. When multicast is not available to connect the3rd Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem)multicast sites together, a signal-free mechanism can be used to allow traffic to flow between sites. The mechanism described inorder to conveythis document uses unicast replication and encapsulation over theidentity ofcore network for theserved user, his/ her registration state,data plane and uses thesession case that applies to that particular communication session and application invocation. A session case is metadata that capturesLISP mapping database system so encapsulators at thestatus ofsource LISP multicast site can find decapsulators at thesession ofreceiver LISP multicast sites.</t> </abstract> </front> <seriesInfo name="RFC" value="8378"/> <seriesInfo name="DOI" value="10.17487/RFC8378"/> </reference> <reference anchor="RFC8402" target="https://www.rfc-editor.org/info/rfc8402" quoteTitle="true" derivedAnchor="RFC8402"> <front> <title>Segment Routing Architecture</title> <author initials="C." surname="Filsfils" fullname="C. Filsfils" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Previdi" fullname="S. Previdi" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="L." surname="Ginsberg" fullname="L. Ginsberg"> <organization showOnFrontPage="true"/> </author> <author initials="B." surname="Decraene" fullname="B. Decraene"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Litkowski" fullname="S. Litkowski"> <organization showOnFrontPage="true"/> </author> <author initials="R." surname="Shakir" fullname="R. Shakir"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="July"/> <abstract> <t indent="0">Segment Routing (SR) leverages the source routing paradigm. A node steers aserved user regardlesspacket through an ordered list ofwhetherinstructions, called "segments". A segment can represent any instruction, topological ornot the served user is registeredservice based. A segment can have a semantic local to an SR node or global within an SR domain. SR provides a mechanism that allows a flow to be restricted to a specific topological path, while maintaining per-flow state only at thesession originates or terminatesingress node(s) to the SR domain.</t> <t indent="0">SR can be directly applied to the MPLS architecture with no change to theserved user. This document updates RFC 5502 by definingforwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as anew P-Served-User header field parameter, "orig-cdiv".stack of labels. Theparameter conveyssegment to process is on thesession case used bytop of the stack. Upon completion of aproxy when handling an originating session after Call Diversion (CDIV) services have been invoked forsegment, theserved user. This document also fixesrelated label is popped from theABNF in RFC 5502 and provides more guidance for usingstack.</t> <t indent="0">SR can be applied to theP-Served-User header field in IP networks.</t></abstract> </front> <seriesInfo name='RFC' value='8498'/> <seriesInfo name='DOI' value='10.17487/RFC8498'/> </reference> <reference anchor="RFC8479" target='https://www.rfc-editor.org/info/rfc8479'> <front> <title>Storing Validation Parameters in PKCS#8</title> <author initials='N.' surname='Mavrogiannopoulos' fullname='N. Mavrogiannopoulos'><organization /></author> <date year='2018' month='September' /> <abstract><t>This memo describesIPv6 architecture, with amethodnew type ofstoring parameters needed for private-key validation in the Private-Key Information Syntax Specificationrouting header. A segment is encoded asdefinedan IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses inPKCS#8 format (RFC 5208). Itthe routing header. The active segment isequally applicable toindicated by thealternative implementationDestination Address (DA) of thePrivate-Key Information Syntax Specification as defined in RFC 5958.</t><t>The approach describedpacket. The next active segment is indicated by a pointer inthis document encodestheparameters under a private enterprise extension and does not form part of a formal standard.</t></abstract>new routing header.</t> </abstract> </front> <seriesInfoname='RFC' value='8479'/>name="RFC" value="8402"/> <seriesInfoname='DOI' value='10.17487/RFC8479'/>name="DOI" value="10.17487/RFC8402"/> </reference> <referenceanchor="RFC8453" target='https://www.rfc-editor.org/info/rfc8453'>anchor="RFC8410" target="https://www.rfc-editor.org/info/rfc8410" quoteTitle="true" derivedAnchor="RFC8410"> <front><title>Framework<title>Algorithm Identifiers forAbstractionEd25519, Ed448, X25519, andControl of TE Networks (ACTN)</title>X448 for Use in the Internet X.509 Public Key Infrastructure</title> <author initials="S." surname="Josefsson" fullname="S. Josefsson"> <organization showOnFrontPage="true"/> </author> <authorinitials='D.' surname='Ceccarelli' fullname='D. Ceccarelli' role='editor'><organization /></author> <author initials='Y.' surname='Lee' fullname='Y. Lee' role='editor'><organization /></author>initials="J." surname="Schaad" fullname="J. Schaad"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='August' /> <abstract><t>Traffic Engineered (TE) networks have a variety of mechanisms to facilitate the separation of the data planeyear="2018" month="August"/> <abstract> <t indent="0">This document specifies algorithm identifiers andcontrol plane. They also have a range of managementASN.1 encoding formats for elliptic curve constructs using the curve25519 andprovisioning protocols to configurecurve448 curves. The signature algorithms covered are Ed25519 andactivate network resources. These mechanisms representEd448. The keytechnologies for enabling flexibleagreement algorithms covered are X25519 anddynamic networking.X448. Theterm "Traffic Engineered network" refers to a network that uses any connection-oriented technology under the control of a distributed or centralized control plane to support dynamic provisioning of end-to- end connectivity.</t><t>Abstraction of network resources is a technique that can be applied to a single network domain or across multiple domains to create a single virtualized network thatencoding for public key, private key, and Edwards-curve Digital Signature Algorithm (EdDSA) structures isunderprovided.</t> </abstract> </front> <seriesInfo name="RFC" value="8410"/> <seriesInfo name="DOI" value="10.17487/RFC8410"/> </reference> <reference anchor="RFC8411" target="https://www.rfc-editor.org/info/rfc8411" quoteTitle="true" derivedAnchor="RFC8411"> <front> <title>IANA Registration for thecontrol ofCryptographic Algorithm Object Identifier Range</title> <author initials="J." surname="Schaad" fullname="J. Schaad"> <organization showOnFrontPage="true"/> </author> <author initials="R." surname="Andrews" fullname="R. Andrews"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="August"/> <abstract> <t indent="0">When the Curdle Security Working Group was chartered, anetwork operator orrange of object identifiers was donated by DigiCert, Inc. for thecustomerpurpose of registering theoperator that actually ownsEdwards Elliptic Curve key agreement and signature algorithms. This donated set of OIDs allowed for shorter values than would be possible using thenetwork resources.</t><t>Thisexisting S/MIME or PKIX arcs. This documentprovides a framework for Abstractiondescribes the donated range andControlthe identifiers that were assigned from that range, transfers control ofTE Networks (ACTN)that range tosupport virtual network servicesIANA, andconnectivity services.</t></abstract>establishes IANA allocation policies for any future assignments within that range.</t> </abstract> </front> <seriesInfoname='RFC' value='8453'/>name="RFC" value="8411"/> <seriesInfoname='DOI' value='10.17487/RFC8453'/>name="DOI" value="10.17487/RFC8411"/> </reference> <reference anchor="RFC8429"target='https://www.rfc-editor.org/info/rfc8429'>target="https://www.rfc-editor.org/info/rfc8429" quoteTitle="true" derivedAnchor="RFC8429"> <front> <title>Deprecate Triple-DES (3DES) and RC4 in Kerberos</title> <authorinitials='B.' surname='Kaduk' fullname='B. Kaduk'><organization /></author> <author initials='M.' surname='Short' fullname='M. Short'><organization /></author>initials="B." surname="Kaduk" fullname="B. Kaduk"> <organization showOnFrontPage="true"/> </author> <author initials="M." surname="Short" fullname="M. Short"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='October' /> <abstract><t>Theyear="2018" month="October"/> <abstract> <t indent="0">The triple-DES (3DES) and RC4 encryption types are steadily weakeningin cryptographic strength, and the deprecation process should begin for their use in Kerberos. Accordingly, RFC 4757 has been moved to Historic status, as none of the encryption types it specifies should be used, and RFC 3961 has been updated to note the deprecation of the triple-DES encryption types. RFC 4120 is likewise updated to remove the recommendation to implement triple-DES encryption and checksum types.</t></abstract> </front> <seriesInfo name='BCP' value='218'/> <seriesInfo name='RFC' value='8429'/> <seriesInfo name='DOI' value='10.17487/RFC8429'/> </reference> <reference anchor="RFC8312" target='https://www.rfc-editor.org/info/rfc8312'> <front> <title>CUBIC for Fast Long-Distance Networks</title> <author initials='I.' surname='Rhee' fullname='I. Rhee'><organization /></author> <author initials='L.' surname='Xu' fullname='L. Xu'><organization /></author> <author initials='S.' surname='Ha' fullname='S. Ha'><organization /></author> <author initials='A.' surname='Zimmermann' fullname='A. Zimmermann'><organization /></author> <author initials='L.' surname='Eggert' fullname='L. Eggert'><organization /></author> <author initials='R.' surname='Scheffenegger' fullname='R. Scheffenegger'><organization /></author> <date year='2018' month='February' /> <abstract><t>CUBIC is an extension to the current TCP standards. It differs from the current TCP standards only in the congestion control algorithm on the sender side. In particular, it uses a cubic function instead of a linear window increase function of the current TCP standards to improve scalability and stability under fast and long-distance networks. CUBICin cryptographic strength, andits predecessor algorithm havethe deprecation process should begin for their use in Kerberos. Accordingly, RFC 4757 has beenadoptedmoved to Historic status, asdefaults by Linux and have been used for many years. This document provides a specificationnone ofCUBIC to enable third-party implementationsthe encryption types it specifies should be used, and RFC 3961 has been updated tosolicit community feedback through experimentation onnote theperformancedeprecation ofCUBIC.</t></abstract>the triple-DES encryption types. RFC 4120 is likewise updated to remove the recommendation to implement triple-DES encryption and checksum types.</t> </abstract> </front> <seriesInfoname='RFC' value='8312'/>name="BCP" value="218"/> <seriesInfo name="RFC" value="8429"/> <seriesInfoname='DOI' value='10.17487/RFC8312'/>name="DOI" value="10.17487/RFC8429"/> </reference> <referenceanchor="RFC8492" target='https://www.rfc-editor.org/info/rfc8492'>anchor="RFC8441" target="https://www.rfc-editor.org/info/rfc8441" quoteTitle="true" derivedAnchor="RFC8441"> <front><title>Secure Password Ciphersuites for Transport Layer Security (TLS)</title><title>Bootstrapping WebSockets with HTTP/2</title> <authorinitials='D.' surname='Harkins' fullname='D. Harkins' role='editor'><organization /></author>initials="P." surname="McManus" fullname="P. McManus"> <organization showOnFrontPage="true"/> </author> <dateyear='2019' month='February' /> <abstract><t>This memoyear="2018" month="September"/> <abstract> <t indent="0">This document definesseveral new ciphersuitesa mechanism for running theTransport Layer Security (TLS) protocol to support certificateless, secure authentication using onlyWebSocket Protocol (RFC 6455) over asimple, low-entropy password. The exchange is called "TLS-PWD". The ciphersuites are all based onsingle stream of anauthentication and key exchange protocol, named "dragonfly", that is resistant to offline dictionary attacks.</t></abstract>HTTP/2 connection.</t> </abstract> </front> <seriesInfoname='RFC' value='8492'/>name="RFC" value="8441"/> <seriesInfoname='DOI' value='10.17487/RFC8492'/>name="DOI" value="10.17487/RFC8441"/> </reference> <referenceanchor="RFC8378" target='https://www.rfc-editor.org/info/rfc8378'>anchor="RFC8446" target="https://www.rfc-editor.org/info/rfc8446" quoteTitle="true" derivedAnchor="RFC8446"> <front><title>Signal-Free Locator/ID Separation<title>The Transport Layer Security (TLS) Protocol(LISP) Multicast</title>Version 1.3</title> <authorinitials='V.' surname='Moreno' fullname='V. Moreno'><organization /></author> <author initials='D.' surname='Farinacci' fullname='D. Farinacci'><organization /></author>initials="E." surname="Rescorla" fullname="E. Rescorla"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='May' /> <abstract><t>When multicast sources and receivers are active at Locator/ID Separation Protocol (LISP) sites,year="2018" month="August"/> <abstract> <t indent="0">This document specifies version 1.3 of thecore network is required to use native multicast so packets can be delivered from sources to group members. When multicast is not availableTransport Layer Security (TLS) protocol. TLS allows client/server applications toconnectcommunicate over themulticast sites together,Internet in asignal-free mechanism can be used to allow trafficway that is designed toflow between sites. The mechanism described in thisprevent eavesdropping, tampering, and message forgery.</t> <t indent="0">This documentuses unicast replicationupdates RFCs 5705 andencapsulation over the core network for the data plane6066, anduses the LISP mapping database system so encapsulators at the source LISP multicast site can find decapsulators at the receiver LISP multicast sites.</t></abstract>obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.</t> </abstract> </front> <seriesInfoname='RFC' value='8378'/>name="RFC" value="8446"/> <seriesInfoname='DOI' value='10.17487/RFC8378'/>name="DOI" value="10.17487/RFC8446"/> </reference> <referenceanchor="RFC8361" target='https://www.rfc-editor.org/info/rfc8361'>anchor="RFC8453" target="https://www.rfc-editor.org/info/rfc8453" quoteTitle="true" derivedAnchor="RFC8453"> <front><title>Transparent Interconnection of Lots of Links (TRILL): Centralized Replication<title>Framework forActive-Active Broadcast, Unknown Unicast,Abstraction andMulticast (BUM) Traffic</title>Control of TE Networks (ACTN)</title> <author initials="D." surname="Ceccarelli" fullname="D. Ceccarelli" role="editor"> <organization showOnFrontPage="true"/> </author> <authorinitials='W.' surname='Hao' fullname='W. Hao'><organization /></author> <author initials='Y.' surname='Li' fullname='Y. Li'><organization /></author> <author initials='M.' surname='Durrani' fullname='M. Durrani'><organization /></author> <author initials='S.' surname='Gupta' fullname='S. Gupta'><organization /></author> <author initials='A.' surname='Qu' fullname='A. Qu'><organization /></author>initials="Y." surname="Lee" fullname="Y. Lee" role="editor"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='April' /> <abstract><t>In Transparent Interconnectionyear="2018" month="August"/> <abstract> <t indent="0">Traffic Engineered (TE) networks have a variety ofLotsmechanisms to facilitate the separation ofLinks (TRILL) active-active access, a Reverse Path Forwarding (RPF) check failure issue may occur when usingthepseudo-nickname mechanism specified in RFC 7781. This document describesdata plane and control plane. They also have asolutionrange of management and provisioning protocols toresolve this RPF check failure issue through centralized replication. All ingress Routing Bridges (RBridges) send Broadcast, Unknown Unicast,configure andMulticast (BUM) trafficactivate network resources. These mechanisms represent key technologies for enabling flexible and dynamic networking. The term "Traffic Engineered network" refers to acentralized node with unicast TRILL encapsulation. Whennetwork that uses any connection-oriented technology under the control of a distributed or centralizednode receivescontrol plane to support dynamic provisioning of end-to- end connectivity.</t> <t indent="0">Abstraction of network resources is a technique that can be applied to a single network domain or across multiple domains to create a single virtualized network that is under theBUM traffic, it decapsulatescontrol of a network operator or the customer of the operator that actually owns thepacketsnetwork resources.</t> <t indent="0">This document provides a framework for Abstraction andforwards themControl of TE Networks (ACTN) totheir destination RBridges using a distribution tree established per the TRILL base protocol (RFC 6325). To avoid RPF check failure on an RBridge sitting between the ingress RBridgesupport virtual network services and connectivity services.</t> </abstract> </front> <seriesInfo name="RFC" value="8453"/> <seriesInfo name="DOI" value="10.17487/RFC8453"/> </reference> <reference anchor="RFC8455" target="https://www.rfc-editor.org/info/rfc8455" quoteTitle="true" derivedAnchor="RFC8455"> <front> <title>Terminology for Benchmarking Software-Defined Networking (SDN) Controller Performance</title> <author initials="V." surname="Bhuvaneswaran" fullname="V. Bhuvaneswaran"> <organization showOnFrontPage="true"/> </author> <author initials="A." surname="Basil" fullname="A. Basil"> <organization showOnFrontPage="true"/> </author> <author initials="M." surname="Tassinari" fullname="M. Tassinari"> <organization showOnFrontPage="true"/> </author> <author initials="V." surname="Manral" fullname="V. Manral"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Banks" fullname="S. Banks"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="October"/> <abstract> <t indent="0">This document defines terminology for benchmarking a Software-Defined Networking (SDN) controller's control-plane performance. It extends thecentralized replication node, some changeterminology already defined in RFC 7426 for theRPF calculation algorithm is required. RPF checks on each RBridge MUST be calculated as if the centralized node was the ingress RBridge, insteadpurpose ofbeing calculated using the actual ingress RBridge. Thisbenchmarking SDN Controllers. The terms provided in this documentupdates RFC 6325.</t></abstract>help to benchmark an SDN Controller's performance independently of the controller's supported protocols and/or network services.</t> </abstract> </front> <seriesInfoname='RFC' value='8361'/>name="RFC" value="8455"/> <seriesInfoname='DOI' value='10.17487/RFC8361'/>name="DOI" value="10.17487/RFC8455"/> </reference> <referenceanchor="RFC8472" target='https://www.rfc-editor.org/info/rfc8472'>anchor="RFC8456" target="https://www.rfc-editor.org/info/rfc8456" quoteTitle="true" derivedAnchor="RFC8456"> <front><title>Transport Layer Security (TLS) Extension<title>Benchmarking Methodology forToken Binding Protocol Negotiation</title>Software-Defined Networking (SDN) Controller Performance</title> <author initials="V." surname="Bhuvaneswaran" fullname="V. Bhuvaneswaran"> <organization showOnFrontPage="true"/> </author> <author initials="A." surname="Basil" fullname="A. Basil"> <organization showOnFrontPage="true"/> </author> <author initials="M." surname="Tassinari" fullname="M. Tassinari"> <organization showOnFrontPage="true"/> </author> <author initials="V." surname="Manral" fullname="V. Manral"> <organization showOnFrontPage="true"/> </author> <authorinitials='A.' surname='Popov' fullname='A. Popov' role='editor'><organization /></author> <author initials='M.' surname='Nystroem' fullname='M. Nystroem'><organization /></author> <author initials='D.' surname='Balfanz' fullname='D. Balfanz'><organization /></author>initials="S." surname="Banks" fullname="S. Banks"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='October' /> <abstract><t>Thisyear="2018" month="October"/> <abstract> <t indent="0">This documentspecifies a Transport Layer Security (TLS) extensiondefines methodologies for benchmarking thenegotiationcontrol-plane performance ofToken Binding protocol version and key parameters. NegotiationSoftware-Defined Networking (SDN) Controllers. The SDN Controller is a core component in the SDN architecture that controls the behavior ofToken Bindingthe network. SDN Controllers have been implemented with many varying designs inTLS 1.3 and later versions is beyondorder to achieve their intended network functionality. Hence, thescopeauthors of thisdocument.</t></abstract> </front> <seriesInfo name='RFC' value='8472'/> <seriesInfo name='DOI' value='10.17487/RFC8472'/> </reference> <reference anchor="RFC8471" target='https://www.rfc-editor.org/info/rfc8471'> <front> <title>The Token Binding Protocol Version 1.0</title> <author initials='A.' surname='Popov' fullname='A. Popov' role='editor'><organization /></author> <author initials='M.' surname='Nystroem' fullname='M. Nystroem'><organization /></author> <author initials='D.' surname='Balfanz' fullname='D. Balfanz'><organization /></author> <author initials='J.' surname='Hodges' fullname='J. Hodges'><organization /></author> <date year='2018' month='October' /> <abstract><t>Thisdocumentspecifies version 1.0 ofhave taken theToken Binding protocol. The Token Binding protocol allows client/server applications to create long-lived, uniquely identifiable TLS bindings spanning multiple TLS sessions and connections. Applications are then enabled to cryptographically bind security tokensapproach of considering an SDN Controller to be a black box, defining theTLS layer, preventing token export and replay attacks. To protect privacy, the Token Binding identifiers are only conveyed over TLSmethodology in a manner that is agnostic to protocols andcan be resetnetwork services supported by controllers. This document provides a method for measuring theuser at any time.</t></abstract>performance of all controller implementations.</t> </abstract> </front> <seriesInfoname='RFC' value='8471'/>name="RFC" value="8456"/> <seriesInfoname='DOI' value='10.17487/RFC8471'/>name="DOI" value="10.17487/RFC8456"/> </reference> <reference anchor="RFC8466"target='https://www.rfc-editor.org/info/rfc8466'>target="https://www.rfc-editor.org/info/rfc8466" quoteTitle="true" derivedAnchor="RFC8466"> <front> <title>A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery</title> <authorinitials='B.' surname='Wen' fullname='B. Wen'><organization /></author> <author initials='G.' surname='Fioccola' fullname='G. Fioccola' role='editor'><organization /></author> <author initials='C.' surname='Xie' fullname='C. Xie'><organization /></author> <author initials='L.' surname='Jalil' fullname='L. Jalil'><organization /></author>initials="B." surname="Wen" fullname="B. Wen"> <organization showOnFrontPage="true"/> </author> <author initials="G." surname="Fioccola" fullname="G. Fioccola" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="C." surname="Xie" fullname="C. Xie"> <organization showOnFrontPage="true"/> </author> <author initials="L." surname="Jalil" fullname="L. Jalil"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='October' /> <abstract><t>Thisyear="2018" month="October"/> <abstract> <t indent="0">This document defines a YANG data model that can be used to configure a Layer 2 provider-provisioned VPN service. It is up to a management system to take this as an input and generate specific configuration models to configure the different network elements to deliver the service. How this configuration of network elements is done is out of scope for thisdocument.</t><t>Thedocument.</t> <t indent="0">The YANG data model defined in this document includes support for point-to-point Virtual Private Wire Services (VPWSs) and multipoint Virtual Private LAN Services (VPLSs) that use Pseudowires signaled using the Label Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as described in RFCs 4761 and6624.</t><t>The6624.</t> <t indent="0">The YANG data model defined inthis document conforms to the Network Management Datastore Architecture defined in RFC 8342.</t></abstract> </front> <seriesInfo name='RFC' value='8466'/> <seriesInfo name='DOI' value='10.17487/RFC8466'/> </reference> <reference anchor="RFC8362" target='https://www.rfc-editor.org/info/rfc8362'> <front> <title>OSPFv3 Link State Advertisement (LSA) Extensibility</title> <author initials='A.' surname='Lindem' fullname='A. Lindem'><organization /></author> <author initials='A.' surname='Roy' fullname='A. Roy'><organization /></author> <author initials='D.' surname='Goethals' fullname='D. Goethals'><organization /></author> <author initials='V.' surname='Reddy Vallem' fullname='V. Reddy Vallem'><organization /></author> <author initials='F.' surname='Baker' fullname='F. Baker'><organization /></author> <date year='2018' month='April' /> <abstract><t>OSPFv3 requires functional extension beyond what can readily be done with the fixed-format Link State Advertisement (LSA) as described in RFC 5340. Without LSA extension, attributes associated with OSPFv3 links and advertised IPv6 prefixes must be advertised in separate LSAs and correlated to the fixed-format LSAs. This document extends the LSA format by encoding the existing OSPFv3 LSA information in Type-Length-Value (TLV) tuples and allowing advertisement of additional information with additional TLVs. Backward-compatibility mechanisms are also described.</t><t>This document updates RFC 5340, "OSPF for IPv6", and RFC 5838, "Support of Address Families in OSPFv3", by providing TLV-based encodings for the base OSPFv3 unicast support and OSPFv3 address family support.</t></abstract>this document conforms to the Network Management Datastore Architecture defined in RFC 8342.</t> </abstract> </front> <seriesInfoname='RFC' value='8362'/>name="RFC" value="8466"/> <seriesInfoname='DOI' value='10.17487/RFC8362'/>name="DOI" value="10.17487/RFC8466"/> </reference> <reference anchor="RFC8468"target='https://www.rfc-editor.org/info/rfc8468'>target="https://www.rfc-editor.org/info/rfc8468" quoteTitle="true" derivedAnchor="RFC8468"> <front> <title>IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics (IPPM) Framework</title> <authorinitials='A.' surname='Morton' fullname='A. Morton'><organization /></author> <author initials='J.' surname='Fabini' fullname='J. Fabini'><organization /></author> <author initials='N.' surname='Elkins' fullname='N. Elkins'><organization /></author> <author initials='M.' surname='Ackermann' fullname='M. Ackermann'><organization /></author> <author initials='V.' surname='Hegde' fullname='V. Hegde'><organization /></author>initials="A." surname="Morton" fullname="A. Morton"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Fabini" fullname="J. Fabini"> <organization showOnFrontPage="true"/> </author> <author initials="N." surname="Elkins" fullname="N. Elkins"> <organization showOnFrontPage="true"/> </author> <author initials="M." surname="Ackermann" fullname="M. Ackermann"> <organization showOnFrontPage="true"/> </author> <author initials="V." surname="Hegde" fullname="V. Hegde"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='November' /> <abstract><t>Thisyear="2018" month="November"/> <abstract> <t indent="0">This memo updates the IP Performance Metrics (IPPM) framework defined by RFC 2330 with new considerations for measurement methodology and testing. It updates the definition of standard-formed packets to include IPv6 packets, deprecates the definition of minimal IP packet, and augments distinguishing aspects, referred to as Type-P, for test packets in RFC 2330. This memo identifies that IPv4-IPv6 coexistence can challenge measurements within the scope of the IPPM framework. Example use cases include, but are not limited to, IPv4-IPv6 translation, NAT, and protocol encapsulation. IPv6 header compression and use of IPv6 over Low-Power Wireless Area Networks (6LoWPAN) are considered and excluded from the standard-formed packetevaluation.</t></abstract>evaluation.</t> </abstract> </front> <seriesInfoname='RFC' value='8468'/>name="RFC" value="8468"/> <seriesInfoname='DOI' value='10.17487/RFC8468'/>name="DOI" value="10.17487/RFC8468"/> </reference> <referenceanchor="RFC8493" target='https://www.rfc-editor.org/info/rfc8493'>anchor="RFC8471" target="https://www.rfc-editor.org/info/rfc8471" quoteTitle="true" derivedAnchor="RFC8471"> <front> <title>TheBagIt File Packaging Format (V1.0)</title>Token Binding Protocol Version 1.0</title> <author initials="A." surname="Popov" fullname="A. Popov" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="M." surname="Nystroem" fullname="M. Nystroem"> <organization showOnFrontPage="true"/> </author> <authorinitials='J.' surname='Kunze' fullname='J. Kunze'><organization /></author> <author initials='J.' surname='Littman' fullname='J. Littman'><organization /></author> <author initials='E.' surname='Madden' fullname='E. Madden'><organization /></author> <author initials='J.' surname='Scancella' fullname='J. Scancella'><organization /></author> <author initials='C.' surname='Adams' fullname='C. Adams'><organization /></author>initials="D." surname="Balfanz" fullname="D. Balfanz"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Hodges" fullname="J. Hodges"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='October' /> <abstract><t>Thisyear="2018" month="October"/> <abstract> <t indent="0">This documentdescribes BagIt, a setspecifies version 1.0 ofhierarchical file layout conventionsthe Token Binding protocol. The Token Binding protocol allows client/server applications to create long-lived, uniquely identifiable TLS bindings spanning multiple TLS sessions and connections. Applications are then enabled to cryptographically bind security tokens to the TLS layer, preventing token export and replay attacks. To protect privacy, the Token Binding identifiers are only conveyed over TLS and can be reset by the user at any time.</t> </abstract> </front> <seriesInfo name="RFC" value="8471"/> <seriesInfo name="DOI" value="10.17487/RFC8471"/> </reference> <reference anchor="RFC8472" target="https://www.rfc-editor.org/info/rfc8472" quoteTitle="true" derivedAnchor="RFC8472"> <front> <title>Transport Layer Security (TLS) Extension forstorageToken Binding Protocol Negotiation</title> <author initials="A." surname="Popov" fullname="A. Popov" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="M." surname="Nystroem" fullname="M. Nystroem"> <organization showOnFrontPage="true"/> </author> <author initials="D." surname="Balfanz" fullname="D. Balfanz"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="October"/> <abstract> <t indent="0">This document specifies a Transport Layer Security (TLS) extension for the negotiation of Token Binding protocol version andtransferkey parameters. Negotiation ofarbitrary digital content. A "bag" has just enough structure to enclose descriptive metadata "tags"Token Binding in TLS 1.3 and later versions is beyond the scope of this document.</t> </abstract> </front> <seriesInfo name="RFC" value="8472"/> <seriesInfo name="DOI" value="10.17487/RFC8472"/> </reference> <reference anchor="RFC8479" target="https://www.rfc-editor.org/info/rfc8479" quoteTitle="true" derivedAnchor="RFC8479"> <front> <title>Storing Validation Parameters in PKCS#8</title> <author initials="N." surname="Mavrogiannopoulos" fullname="N. Mavrogiannopoulos"> <organization showOnFrontPage="true"/> </author> <date year="2018" month="September"/> <abstract> <t indent="0">This memo describes a method of storing parameters needed for private-key validation in the Private-Key Information Syntax Specification as defined in PKCS#8 format (RFC 5208). It is equally applicable to the alternative implementation of the Private-Key Information Syntax Specification as defined in RFC 5958.</t> <t indent="0">The approach described in this document encodes the parameters under afile "payload" butprivate enterprise extension and does notrequire knowledgeform part ofthe payload's internal semantics. This BagIt format is suitable for reliable storage and transfer.</t></abstract>a formal standard.</t> </abstract> </front> <seriesInfoname='RFC' value='8493'/>name="RFC" value="8479"/> <seriesInfoname='DOI' value='10.17487/RFC8493'/>name="DOI" value="10.17487/RFC8479"/> </reference> <reference anchor="RFC8483"target='https://www.rfc-editor.org/info/rfc8483'>target="https://www.rfc-editor.org/info/rfc8483" quoteTitle="true" derivedAnchor="RFC8483"> <front> <title>Yeti DNS Testbed</title> <authorinitials='L.' surname='Song' fullname='L. Song' role='editor'><organization /></author> <author initials='D.' surname='Liu' fullname='D. Liu'><organization /></author> <author initials='P.' surname='Vixie' fullname='P. Vixie'><organization /></author> <author initials='A.' surname='Kato' fullname='A. Kato'><organization /></author> <author initials='S.' surname='Kerr' fullname='S. Kerr'><organization /></author>initials="L." surname="Song" fullname="L. Song" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="D." surname="Liu" fullname="D. Liu"> <organization showOnFrontPage="true"/> </author> <author initials="P." surname="Vixie" fullname="P. Vixie"> <organization showOnFrontPage="true"/> </author> <author initials="A." surname="Kato" fullname="A. Kato"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Kerr" fullname="S. Kerr"> <organization showOnFrontPage="true"/> </author> <dateyear='2018' month='October' /> <abstract><t>Yetiyear="2018" month="October"/> <abstract> <t indent="0">Yeti DNS is an experimental, non-production root server testbed that provides an environment where technical and operational experiments can safely be performed without risk to production root server infrastructure. This document aims solely to document the technical and operational experience of deploying a system that is similar to but different from the Root Server system (on which the Internet's Domain Name System is designed andbuilt).</t></abstract>built).</t> </abstract> </front> <seriesInfoname='RFC' value='8483'/>name="RFC" value="8483"/> <seriesInfoname='DOI' value='10.17487/RFC8483'/>name="DOI" value="10.17487/RFC8483"/> </reference> <referenceanchor="RFC5326" target='https://www.rfc-editor.org/info/rfc5326'>anchor="RFC8492" target="https://www.rfc-editor.org/info/rfc8492" quoteTitle="true" derivedAnchor="RFC8492"> <front><title>Licklider Transmission Protocol - Specification</title><title>Secure Password Ciphersuites for Transport Layer Security (TLS)</title> <author initials="D." surname="Harkins" fullname="D. Harkins" role="editor"> <organization showOnFrontPage="true"/> </author> <date year="2019" month="February"/> <abstract> <t indent="0">This memo defines several new ciphersuites for the Transport Layer Security (TLS) protocol to support certificateless, secure authentication using only a simple, low-entropy password. The exchange is called "TLS-PWD". The ciphersuites are all based on an authentication and key exchange protocol, named "dragonfly", that is resistant to offline dictionary attacks.</t> </abstract> </front> <seriesInfo name="RFC" value="8492"/> <seriesInfo name="DOI" value="10.17487/RFC8492"/> </reference> <reference anchor="RFC8493" target="https://www.rfc-editor.org/info/rfc8493" quoteTitle="true" derivedAnchor="RFC8493"> <front> <title>The BagIt File Packaging Format (V1.0)</title> <author initials="J." surname="Kunze" fullname="J. Kunze"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Littman" fullname="J. Littman"> <organization showOnFrontPage="true"/> </author> <author initials="E." surname="Madden" fullname="E. Madden"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Scancella" fullname="J. Scancella"> <organization showOnFrontPage="true"/> </author> <authorinitials='M.' surname='Ramadas' fullname='M. Ramadas'><organization /></author> <author initials='S.' surname='Burleigh' fullname='S. Burleigh'><organization /></author> <author initials='S.' surname='Farrell' fullname='S. Farrell'><organization /></author>initials="C." surname="Adams" fullname="C. Adams"> <organization showOnFrontPage="true"/> </author> <dateyear='2008' month='September' /> <abstract><t>Thisyear="2018" month="October"/> <abstract> <t indent="0">This document describes BagIt, a set of hierarchical file layout conventions for storage and transfer of arbitrary digital content. A "bag" has just enough structure to enclose descriptive metadata "tags" and a file "payload" but does not require knowledge of theLicklider Transmissionpayload's internal semantics. This BagIt format is suitable for reliable storage and transfer.</t> </abstract> </front> <seriesInfo name="RFC" value="8493"/> <seriesInfo name="DOI" value="10.17487/RFC8493"/> </reference> <reference anchor="RFC8498" target="https://www.rfc-editor.org/info/rfc8498" quoteTitle="true" derivedAnchor="RFC8498"> <front> <title>A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol(LTP), designed to provide retransmission-based reliability over links characterized by extremely long message round-trip times (RTTs) and/or frequent interruptions(SIP)</title> <author initials="M." surname="Mohali" fullname="M. Mohali"> <organization showOnFrontPage="true"/> </author> <date year="2019" month="February"/> <abstract> <t indent="0">The P-Served-User header field was defined based on a requirement from the 3rd Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) inconnectivity. Sinceorder to convey the identity of the served user, his/ her registration state, and the session case that applies to that particular communicationacross interplanetary spacesession and application invocation. A session case is metadata that captures themost prominent examplestatus ofthis sortthe session ofenvironment, LTPa served user regardless of whether or not the served user isprincipally aimed at supporting "long-haul" reliable transmission in interplanetary space, but it has applications in other environments as well.</t><t>Thisregistered or the session originates or terminates with the served user. This documentisupdates RFC 5502 by defining aproduct ofnew P-Served-User header field parameter, "orig-cdiv". The parameter conveys theDelay Tolerant Networking Research Group and has been reviewedsession case used bythat group. No objections to its publication asa proxy when handling anRFC were raised.originating session after Call Diversion (CDIV) services have been invoked for the served user. Thismemo defines an Experimental Protocoldocument also fixes the ABNF in RFC 5502 and provides more guidance for using theInternet community.</t></abstract>P-Served-User header field in IP networks.</t> </abstract> </front> <seriesInfoname='RFC' value='5326'/>name="RFC" value="8498"/> <seriesInfoname='DOI' value='10.17487/RFC5326'/>name="DOI" value="10.17487/RFC8498"/> </reference> <referenceanchor="RFC2267" target='https://www.rfc-editor.org/info/rfc2267'>anchor="RFCYEAR" target="https://www.rfc-editor.org/rfcs-per-year/" quoteTitle="true" derivedAnchor="RFCYEAR"> <front><title>Network Ingress Filtering: Defeating Denial<title>Number ofService Attacks which employ IP Source Address Spoofing</title>RFC Published per YEAR</title> <author> <organization showOnFrontPage="true">RFC Editor</organization> </author> </front> </reference> <reference anchor="SSCH" target="https://www.semanticscholar.org/" quoteTitle="true" derivedAnchor="SSCH"> <front> <title>Semantic Scholar | AI-Powered Research Tool</title> <author> <organization showOnFrontPage="true">Allen Institute for AI</organization> </author> </front> </reference> <reference anchor="I-D.ietf-rtgwg-segment-routing-ti-lfa" quoteTitle="true" target="https://tools.ietf.org/html/draft-ietf-rtgwg-segment-routing-ti-lfa-05" derivedAnchor="TI-LFA"> <front> <title>Topology Independent Fast Reroute using Segment Routing</title> <author fullname="Stephane Litkowski"> <organization showOnFrontPage="true">Cisco Systems</organization> </author> <author fullname="Ahmed Bashandy"> <organization showOnFrontPage="true">Individual</organization> </author> <author fullname="Clarence Filsfils"> <organization showOnFrontPage="true">Cisco Systems</organization> </author> <author fullname="Bruno Decraene"> <organization showOnFrontPage="true">Orange</organization> </author> <authorinitials='P.' surname='Ferguson' fullname='P. Ferguson'><organization /></author> <author initials='D.' surname='Senie' fullname='D. Senie'><organization /></author>fullname="Daniel Voyer"> <organization showOnFrontPage="true">Bell Canada</organization> </author> <dateyear='1998' month='January' /> <abstract><t>This paper discusses a simple, effective,month="November" day="15" year="2020"/> <abstract> <t indent="0"> This document presents Topology Independent Loop-free Alternate Fast Re-route (TI-LFA), aimed at providing protection of node andstraightforward method for using ingress traffic filtering to prohibit DoS attacks which use forged IP addressesadjacency segments within the Segment Routing (SR) framework. This Fast Re-route (FRR) behavior builds on proven IP-FRR concepts being LFAs, remote LFAs (RLFA), and remote LFAs with directed forwarding (DLFA). It extends these concepts tobe propagatedprovide guaranteed coverage in any IGP network. A key aspect of TI-LFA is the FRR path selection approach establishing protection over the expected post-convergence paths from'behind' an Internet Service Provider's (ISP) aggregation point. This memo provides information fortheInternet community. It does not specify an Internet standardpoint ofany kind.</t></abstract>local repair, dramatically reducing the operational need to control the tie-breaks among various FRR options. </t> </abstract> </front> <seriesInfoname='RFC' value='2267'/> <seriesInfo name='DOI' value='10.17487/RFC2267'/>name="Internet-Draft" value="draft-ietf-rtgwg-segment-routing-ti-lfa-05"/> <format type="TXT" target="https://www.ietf.org/internet-drafts/draft-ietf-rtgwg-segment-routing-ti-lfa-05.txt"/> <refcontent>Work in Progress</refcontent> </reference> <referenceanchor="RFC2827" target='https://www.rfc-editor.org/info/rfc2827'>anchor="TLS13IMP" target="https://github.com/tlswg/tlswg-wiki/blob/master/IMPLEMENTATIONS.md" quoteTitle="true" derivedAnchor="TLS13IMP"> <front><title>Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing</title> <author initials='P.' surname='Ferguson' fullname='P. Ferguson'><organization /></author> <author initials='D.' surname='Senie' fullname='D. Senie'><organization /></author><title>TLS 1.3 Implementations</title> <author> <organization showOnFrontPage="true">TLS WG</organization> </author> <dateyear='2000' month='May' /> <abstract><t>This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS (Denial of Service) attacks which use forged IP addresses to be propagated from 'behind' an Internet Service Provider's (ISP) aggregation point. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>day="14" month="October" year="2019"/> </front> <seriesInfoname='BCP' value='38'/> <seriesInfo name='RFC' value='2827'/> <seriesInfo name='DOI' value='10.17487/RFC2827'/>name="commit" value="dcb7890"/> </reference> <referenceanchor="RFC2330" target='https://www.rfc-editor.org/info/rfc2330'>anchor="TRKR" target="https://datatracker.ietf.org/" quoteTitle="true" derivedAnchor="TRKR"> <front><title>Framework<title>IETF Datatracker</title> <author> <organization showOnFrontPage="true">IETF</organization> </author> </front> </reference> </references> <section anchor="acknowledgements" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a"> <name slugifiedName="name-acknowledgements">Acknowledgements</name> <t indent="0" pn="section-appendix.a-1">Many thanks to the authors of the selected RFCs who were willing to provide feedback on the process: <contact fullname="Michael Ackermann"/>, <contact fullname="Zafar Ali"/>, <contact fullname="Sarah Banks"/>, <contact fullname="Bruno Decraene"/>, <contact fullname="Lars Eggert"/>, <contact fullname="Nalini Elkins"/>, <contact fullname="Joachim Fabini"/>, <contact fullname="Dino Farinacci"/>, <contact fullname="Clarence Filsfils"/>, <contact fullname="Sujay Gupta"/>, <contact fullname="Dan Harkins"/>, <contact fullname="Vinayak Hegde"/>, <contact fullname="Benjamin Kaduk"/>, <contact fullname="John Klensin"/>, <contact fullname="Acee Lindem"/>, <contact fullname="Nikos Mavrogiannopoulos"/>, <contact fullname="Patrick McManus"/>, <contact fullname="Victor Moreno"/>, <contact fullname="Al Morton"/>, <contact fullname="Andrei Popov"/>, <contact fullname="Eric Rescorla"/>, <contact fullname="Michiko Short"/>, <contact fullname="Bhuvaneswaran Vengainathan"/>, <contact fullname="Lao Weiguo"/>, and <contact fullname="Li Yizhou"/>. Many thanks to <contact fullname="Adrian Farrel"/> forIP Performance Metrics</title> <author initials='V.' surname='Paxson' fullname='V. Paxson'><organization /></author> <author initials='G.' surname='Almes' fullname='G. Almes'><organization /></author> <author initials='J.' surname='Mahdavi' fullname='J. Mahdavi'><organization /></author> <author initials='M.' surname='Mathis' fullname='M. Mathis'><organization /></author> <date year='1998' month='May' /> <abstract><t>The purposehis useful advice, to <contact fullname="Stephen Farrell"/> and <contact fullname="Colin Perkins"/> for their guidance on the use ofthis memo iscitations, and todefine a general framework<contact fullname="Dave Crocker"/> forparticular metricsa comprehensive review. Thanks also tobe developed by<contact fullname="Alice Russo"/> and theIETF's IP Performance Metrics effort. This memo provides informationRFC Editor team for their work improving this document and checking theInternet community. It does not specify an Internet standardaccuracy ofany kind.</t></abstract> </front> <seriesInfo name='RFC' value='2330'/> <seriesInfo name='DOI' value='10.17487/RFC2330'/> </reference> </references>the data.</t> </section> <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b"> <name slugifiedName="name-authors-address">Author's Address</name> <author initials="C." surname="Huitema" fullname="Christian Huitema"> <organization showOnFrontPage="true">Private Octopus Inc.</organization> <address> <postal> <street>427 Golfcourse Rd</street> <city>Friday Harbor</city> <region>WA</region> <code>98250</code> <country>United States of America</country> </postal> <email>huitema@huitema.net</email> </address> </author> </section> </back><!-- ##markdown-source: H4sIAJIHll8AC729e3PbSLIv+H99CoQ7Tox9gqQJ8O0bG7Oy/GjN+KFoqcc7 e2PjBERCFNokwQFAqTktn8+++cvMegAkZc/cG7djRpZIoFCoysr85bvb7Zo6 r1fZq+jtfbrapXVebKLiNkqjq3S9XWX4/Zd359FlWSx282wR5Zso6cdTk97c lNn9K3zZxa1d/nRRzDfpmkZblOlt3b3b5XW2Trvl7byb4aJtWfyWzetuf2Lm aZ0ti3L/ioa8LcyC/nxFQyd9Y6o63Sz+K10VG/pon1XG5NvyVVSXu6pO+v1Z PzFpmaWvovfZJivTlfn68Cq62NRZucnq7hs82ph5scg3y1fRruqm1TzPzTZ/ Ff3Puph3oqgqyrrMbqtOVO3X8su8WK+zTV39f8aku/quKF+ZiP/r6r8RzbN6 FZ33op/lrdzn8sbnd2Ve1Xm6Ofi+KGkal2V+T68YfZ7XxXZX0XTnPXdFRbPJ 6lfRMJlE74vV7bzYlVUW/bJwV8zzmlbqXZkv0n30c1reFKX/rljQ87+cRbNp MuoHH+82Ndb3195V78x9TDPLV68i3Zr/W//t0crRMtNOlGsigvtMXv/6l7/+ 8srdWqflEtO8q+tt9erlS9qztC7T+des7OVZfdujN33prxa6unh7/S56Q1dG 13Kpu6C5zsFa4Rb3aUgY+Pvq6vzn01N6eHjoVfQ+mzqfV/O7YpWWR2d1pddE V3LR9yd1tlplG9o22uN6RxtJKxWdXZyc5vWHq3hw8fHy9FSXeX23u+kR4b2s V9XDUn52H/Kv+cubVXHzcp1WRNIvaZAPbz++/XR9dn3x+dNVb71ovww9K4p7 g+gCJxZUzMe4+v474cYv70++A53tv789e4IAsNp8thd5XchC059Vd5uV3X2W lgfL/mm3vslKx1R2N6u8uiOuQjdEeNT3p4z73vLjTk4b5HP++ddP109P3FHs XfHwck3nj9hF9XJLi34w7Uv6UAj5o173v0DE3W43Sm8qHBw6ctd3eRUR29xh 36JtmVXgQlF9l+nQf6qi7JaIrY7qItptFlnJ7JGvWGSrdF8RY7ovVvfZgs5v tJU1pTlGxIryRZaCZeNinj8RbX1XFrvlnXxG420z+kHPviImlK470W1ZrPGl uc3pUXT3Ir/PF7t0JUwd08Ct/KC5Exj4iPamZ77QxDfpav9P+jeqshpfljTh Yr3aR3TY6P14E9MtCYN7L1E60aoovmLeOFm0KrTFe4M3lbfsRRh5VdEiEGus H4qDUelhlSWtrSMtHr4/jTBSPJtNDYanQ7dNSzxMl7DKaACdibwhDRkVN1VW Yo5xHyuX9CNQdRWly6IX0dbRhO5JAC351e068xCVSM+HtKI99aJzYAegyQyj dbGp76qOoTk/3OXzuygJvqZHyvfRQ1ZmUbXFHukjvhQlr9R72sltxwwwYzsc Lx/v9Zx4QLapdjLexdur9xGJ7Dx76PAHzbty3hUjk8Wm9iK8HwmLTXRPSyUb LVdF/iq7frSgWcWkYzDBs1+vf+4Op9H2Lq2ynjF269ZZWu3obXDNxvECEm7C sSwhBWSyq/Cill0bZdfyBrKLmbtfRB4tGHFWWtG0pqWLvm6KBzpvxa6muW5X xR4Hjcm0ooNPj6PL2gOA5oFPonSeLrI1iYkc6CKr6k50s6sJW5QlvTddUGyI /ohwq4z+5ef6h4BkdhWoQ1+L9nCe3+qhqXrmHE/D6z1kN7Q1t/SEzTzDYu5W 8nbCznmSPcMER2sCal0RiiKSuuXzTByEVvU+2wup6OrRe8kJ4bUqM+Uthk7l Ol2tLIkC7NFfPK4lVVlefjc+pr/nBArwhnH/P+gGU9uJhLSdpUTBNBoOWYfP nAyD89AjrkzUSzcUVZXfrDLD677Ib/mla50MbR2/ug4bfE9z361qYgLRu11J jy/XRZl1eCJE5vMVkQnohzjUw8ZxMD2/Sltr2ko5QAHHNW5dmiw3Krb5hm9j DlREm6KO7ui0B6dKdtXgrPWEra/zxYLezfwENOrOiDFntEFEYRnWVCZWLtNN /k+e2Z8q3v+KcFgnenZtOTVNMo1WkFs0F2ZOwLd8ByFewNXdhkAhZkHY7YE4 ApFelS8JEROcpVvKlDgo/XpP/J1/ETKoiMPMaQErXjhA5gUTLq9lRoJkF7J0 i6oj3EQznNc4vlb+VOuiIJKXhx25q/eMabZJ955obvZeMOEcN5i20hjRepln mD2pA0uZaR5IrWp3s84r3v2Oe7tom24z5aMXZ6/dbtOZu1ACWGfrohPsOR0X wsFbiN7/s2I2YjFr/kUxGzFuyCuDp/tbBSl03AY5eg4PiRI8LfMd2AWvPL0u 6KqH/SpFbm0KuyaYCwnIry2xohyJP/yaZduK1p8444JPhltyngttOTE2+n0u yDRcq0CLiP74AxrHt28qXQ++B2Sgxa4ip6nQsghzZ37EhxXLV+kCi1wlMTBP N1BvaAycRGhq80rv5GX2Eq3aE+xeM9ygm5zIImFhmARzuiP9mjGhLEirA86h 24mz5Xw/P5eYB+mCwV7e5rS84W52GNuICKL9cIKUHnmDI7Oi59zQwQYwach7 4orVfGdJnpdIxDohCRbyaVXRWmPxOwFctg/AU2Uyepc9hkIrVUR8rCABS+tr DumWl7mjr+UXrdMe7MidMo0Osa7NLS1C7Wb9I5MEQSgNgB6YO96TIpuSLGEp aGVYhzn1bzsL2Cs/bRrD/AVfyJZiQQ+BzJr0a1p/4imrLIUFoRdd3LYONvFJ nm1lZWEBiaScihg5ibJ9VO5uCN50idrWW+IZbsWITggKyalw/I7uX3dCXiNy 8IZBCkH/GyXTf9AhB9Onuw09ho4TzXR5BzYISclEe0fsWGDNuqjqgGnIh01G i78IT9/uVh2Dh9BJ2WT4nFjAHnTrERvdK1duiLr4SXXJlywK+Za23q8sJKNH eAG40fn4KfDBJYbQVsmJGUDX//aN2Zlh/EiPSKuvOr6jWBqSwUcAwgVPmIe7 jLdGj3hdzAtdexJld5tiVSyxZYuMiK0hdhR15xaCYUnoLloAyHDTEHIMlD2G 1RVz4u3gvXKw4kV4S74xQkKOieUbL3qFoXn95yiINuESy2sQqugoA3R8syKc bsEUU5UjtLu0XGA3aVELoD3i7iQriZ1j+Ypola9zoUG6u9iVc/zyj11eNlBo vVvsOyAih1A9CiXdVzBjUzWD5kfSJvt9u0rtJvzxh+xfV4ahNYJIYChhmTdh IL6GT3FOjIFeAlgkPPQs/g8ZUYAG3nldkOQfTa2k40lowzzoWh99j0MNE5hX we6h6tkzH7B4lmoVd9Oa0sWQP0S+SX8WHV8cMLbiQbS6HFxqSwCIFewqb1A+ aya0JymgC9iG7mtJ+gu9/kLOKCZQC3SImopAT6CaTC6HdCv0exDFFixtKebW cBPkHOX/2GVMt4YYFNH67d5hvoiRoaLPQHKx3qdqFNhvMI4jSRIA0D620D4z QDcSzOmio/yDt0pmCgAmj6Ud3ixg190W0DcqnZe3sNzugGAN8DLkAd45xBLL FOdQaToj5X5/yFVYj3EYis6uI1fYwuzegGIvQMqKfYIvcECsjaQFPvRi4xA2 HzVBVCwZOoHtom1tUMjoaNYqVXgXNn14dYxnZhlQV7iIzszqQ22l+FZln+XX fkEqwTL2lSzTbQ8wt/vKXJQmm4nLIWuINjHgWHCpvE7U6VtvbdCRLLNiZqtr x1Yd+kwIkvYQzxZk6ll8aLqOjjzInUPhWe6BXimXZwZgkpEoWASYmAWhzH6N UHTItwmo5/Oc2PXe6UxgXDWR+lKByZzF7McCYogov9w5y66cEHOXrbaBqoLb ACdFZ9SVuqMTRAByIUK5iSP1GVnFR5/OEp0ZHCM61Zvsd8IUNTA9EMKCVnFF sEKZs1cmiMih7X6kDS8WkKZ72TYWBLA5EHixegZNkv9gK0kqMClj1ekVA2p8 FvqchGcYUk1wPFnN2nSZ/0Uh/+MDRKe2pVBZMm5oTniYAbuoqwYUxzatlOMT qOGzRUxvzjoL0/lOftdxRIDSZaah2qpWpnJRYYU9qF8zgkf0lKomAqmEGz9A 09qIrgdilHMEIwYrllbi6LKIKYzWYbe5yVOcIUsltAc/RW/Cp12ssfQY+6N/ 5h8/+Ql8M8c1LKvCpSTxBT3qCWKGCFkTGKuFfvggsLm7QV+VLsdditHuCKZG S3qhHdEnnXMRCLzi+iVbGW9yMAGQPT3cCWrDtEMzus2AFZo6Lx+1DtNpuii2 ejDTlpFUDsqSntacJR0XehJJspUMwfaEuhYGJefy6n1w90aWzN2lnK9pXl0S auNlo/lZG9p9aPDAkHxjmfllZMt0qO/r5V496lhFQNX27Pc5nQc2JkZXQHZ+ xfC1HITGG9HWt7iAShpSdHmKoPsNg9GjQ4Yqy9P2Dft67QU9plSq8peLgPcc 8eo9ZHQIQ5lrsKBPb3YrPb1Aazc00FevQQk3sPqzHGFrKLLji+FFFDMrb4+b W0RqlBk9Jl+yDKB1pCV5Zcx/svQ4ylj5LObrrG3raRp4hLQDIWAiT13/wz6A ie5gXAH3uLryz7jJSIIwIwglixuSnktPYPWJyZJOUIMsRTuxfMSr9XQTTmix I75G3G1OGwYh62bY9AvoOx97BF68wXzdE3Ve1nlgVX/DMD0w9LmjeYTsHkCx mz+psbbFBdjsD/tVDnKy5KYQbFlmDfI4sMjBWL9iEmY+E5zQi6u34Ess2In3 0wsrjMAnzxpTeAZbW14QinUYLyDYYwPLYwPy1bcPPKEnny3sHePjIH3JGhgE lMdYo8j9HdZSJ8JGoRKLZD8DEx4gXRxIC2vfTmuhBrg+Tlj6GIHCPmHmJMk6 opOE4+VH2bxTYjYsgy1ngUxosXWVCkQ463R/kzUuVwSyyR44dsNunTzhISVx w1Zk64sk+QRGSG9iuX9LtNA1N9ltwUBpni/0PhNynM0Jgu2dEMN0BRuT8PyW ZdN6I1g+N2Ziwe4q/9pmSR9w/M/p+AvaZdcOexTW2QLalYgrh0owtgm5Z7g1 Tjc5IEk+3rmsZnNmZ0rYvegdqxFpzUeVXblHaczSI6lg/Ge/b/0tMolAvAbW rEqM41/8yBU2WICYWGdhZOR1NIei/tj2ELK6EisEQ7JfBJI1oqOArA4MFsa8 TivSfwPlbk06brrJq3WgUFgd6IgGk3p/aps+BAjQCyCaCiZovtwBzzXBLDoy 3hAsNji2+nSMSA01NEOQMEvcrdnYeUXcmN5rVzo7j6gAbP+BZxCYNScxAhJy 4JyPr0PlcmjaXkaB9IcGFeMkl0WcQvCt+ACamsXatOl+HjD+GLXJqB4bGGuU hllQ44rpoD/pNK0sf8FikZ6vpihSOey1ozgOr32TzTO2tvF05ODaKdME3JuJ glxJrMp0iEHkt9HY/ja0vw1GI/eZvW6QDDtGfptM7Lfwqcpvk5kbb2B/S+xn gzhxdySR/XBibx6MYx16OHEXTtwEx25a40QQnH6O1/0CrqvkGkROsLWSTdF+ T6xjHpuKiAYXVmEjMYw4ieO+NZoFcRXX1q3CROWtczw8dlstcME2m3RdsLSC RejA/qZYVFAtbj55NWbV2lixsfhYk+YuM+nyS9n9HiWJ7tkongzdb7rYo8FI 93YUz3TnR8lgbL8dTu1n09jeO3XfJva3xNLFaDBRGhgN+3bkgaUGGmXgnmtH joeJGyV2z5357R4N+vH/4iIkw4EOnQym/reJ/Y1e08hvM/ttMnbfWhJOhnY5 koFdSrrDfuZejkZO3GczHTlxn2Fh7Hgz9wz3tJn9NplN/CIkg2TApo2zwNRA S3DVeHPH9huGPwZaAl5dUIQznClOOmHkdkY2d2o61iBh2LzN6ln1oC4NxLZs IhhNaxerQFeIERP4ln1DGPNWoiasjU4c4SQm9hHwV6We8JZZxXra2kYvwf/R bZYtbkgceQbOcV3ilBHJCe5nLs4+nUW/kFaCmDcnhHH9ebnf1gS80y2JpOhs tSxKgmbr6DPLtehCrLo5HCPphsDkH3/8mR6BQb99I5b+3//93xG9h7PepqTD jxh2VmZo0dJz69t+0VEUQ8s66fZHXbbMO7Uo3WyK3QZhCfx93O/2Z+JPzXxk NCtrlV6RdJOpObNiCpvV7dNnY+se7Q+MVWXky2E36buPZFHrTL+j8SbGB0TK h/S/sSyfOM5fRXNCJTCYwu+J99cAQiw8x5q5AdyeHFpK1CfOLv46BMaGLTVH cLSyA6sGkfL0AFBBiIH9J9s9O0QtCA6UO2gdbEUAXMHTsNJKXexMF92HToNd FsTm7NiUDRMjAdRcoz785vdhdfx4cXX1y9t3/BrzFZ0WUT5k3WhvZw6mOntV mXUzDuNauKeltUEQTM99ADUZI93jhD0UNjqO3jsT2KpLwbBJPnVjbRZHViB6 PiC5lX2tXhBhljVhJoy9SrcapkZH4j5buaA9ortERGql17vlKIqSVIvU+pGM rg+WmE/aaGxeZ5v53TqV/QuMsjz8VXFbP9A6dd+ot/OThA3h2udXbz69iMx5 gbCl1Yre6lKQXQo0aFd+NLbHrn3qxkM9dokLJXEm8Fn05b0PyrAnkLZo0E0G hr5zSq/s3whnL56eOpq0vXE3fupoyjGcaDBE83yOusmodSqn3UF84lRiIuP2 qaQPB3179g4PBfuMst/rjLgvh4vp6aBlhu/mXiga6gki78o6n6+Y/+5K1nm2 d6Uw5Pldkc8zqNr3xZyNXeVeXc13YIYCy7ONGOGIPlKMuYX7QBbEBs8Rgpf7 nuGTZ3DsrSIQCXux6npv1jviB+LsYp0dR4qfsbA2wDwlJr3mMFn9CmfWetSj TKSDap5rUjowDHRryIGz+ZxJd2n1LBERInOy32EPyVjpuFVlSSg8r3Rt13lZ ws2fRvV+y05HWDHFsHCK5KE7NxnZ89cfv7x/wSuBACf8WMOID+3EBhLQmO4z nHDzT5jKLcesVsUDXDuQuaGdyppM4Ft/YM02XdF41jhqLxNWRy85HJNk3bML lpWoNLoh5gl2KDxGRreRxSEDdmxeTYbKApr8cTRirwxe18mDRsBUqtGec8sN U1ogZl5+KTvOOrVurKkGAIMXiIXthgOnA3yQbxoDWf3XAYLhmF/lmsBkBR9F 9CHd0ytcZfMd/ALR8+sPVy+QbySk9TfV/5HfYN9wOOagELEzcIi+sRG7iE1i 9iZfwsRjLQgqdpDzYAm3F72zYvJQw34AcUqUPltACjjikVIkHPCSQ3ngZYXz LS1Jpxn3LRcMeJ5neUMggHhyEnQw34pHT3O2AV3UBh3ESGMLOgBJGuxt3I2H p0AHmNkR0BELe7v2R9D67gQgvNc4wxZVpsRVfoOXSNIVAstfr3UW15no6d6v KCE5kL2mAiciGnVEpeHSBCF97KriWDVENeNLObRKxBddYJjuVyCDIPaalHkX po3nVojEWEn8iUQNSGB4yr5qpoMIwhIRRZvDh8r7rzjgCiEYwqkr6y/+HYTN ftnV3ka6MIEaxhGnY/tphc8b7n4JijuMEOX9U0pn0qULEe274mQuxKizKgBp ZFQa9TgkW2KRXPwNG7nmZbHZr9mjLcS7g4l2DsfdLesiHEXkjWpVZOwhyP/J Z55outaUAQ7UT7d5na404Fm0LHrpFUfvIASGB7TWGywErXhPCFCDTugVbnFi dJVs9iBO9bOq3q+yZwHb5eFsLgFP2268WRawexZOSAVv0Yt+JgZ/n7Fkos1X D7XTihZFJpBZ14rEwv4w2wHy9aulBQ8he61Unz9VB/Ij5OzsOHjPGWIqInHT MyuKYByGqmcg8yWRjBZ9tWITIJOzdSk3RJBDDkwbrKDavEcmWPPL5TnO+u0t MXdWJYGsN+oM0OncqgHXzttGG3vP9yJCdL6cFyfPdtVOBA+BbY24ptvO3sAO w55ExEzynHDgUglaEw7LFNthf/y2dvQnL/GbWmbxkcIjCWtXN+lDKkfZsK7r oEtqT2brHEs0JS0A9M/UIxwxjHOcmiI7EtxuukfTcljn4SgnTuasmR9Yf1q6 4JAsnH51izZgQqWxSernTeI2N1Q7gg2k/pJ/zUMBB2mpubaIqdZcRA5Jqtkh z2JbUlVEcRLWfVMWD1WmyQIGNt0VszMJ2eF1k/CS21I0UjwUD6RF34gRwwr6 wWhkiGPnK4ly+ZVe/hzIlkM9JYDwEpK2jn4hDoBloy8aKsnlLxef3r+wn1VW /A8AcJx/qIVqeuYCeTc5o2CrBqcMt2HoaN0Q+JSwtziyK31Xa6J4/fmdKN2W A39578Lr4fcwYqu08d6Y6UuXRRF4Zb+87x3VnOKBYIbeoep03HQxhP4ziHu4 04GM3hE9aghtJx6cNnGIPeIpEwcU6aEzZ8wauIMNIPHMfhsnLdwx6AYftXDH AOpZG3cMYE5hteoj2xU0d9ApUESUukHYG+b5tKSfitbRaLjt6ypb3bqoCR/0 ixjvO0jIHF4U4jVpZa6yJcMBS47PGykvgnr7SSe6vuh+eHemGe5IIu2W9fJh 2a3k/m4p93frvLu6TV+AUh/yBWRwAJM1sdFhENYFlgXEckth2rKOmG9TSUwT k4aLo+w0nLbQKB0RaM6ZHLWtHDWdmxPXInRY86MTzNFfxU7VRRIjKe+QdSAF +YS1BNseMD2SF8QZne4gkQf4iJ8D/TOfk4IlB6jpebLqQWxeF0UNU+F2yzFr 2c1VgcmrweTn6+vLl4nXBeJv304A8k401bMV/bqViEDs4pg0pJ4Z/NhpY0Ng POrRUE8eNj0NT0B7OkoTd5S+A/JH3cQdrP64DffH4UiTA2tGPDh17GbQLtrH bkbKg9gYz9TGyMZF64FuGRlD5arabVmBI9IINolIVLbIYpW88nl83lTsfKEu +B6nmu+Me7HYx7HDY9FnmSIDoGQCaAtagdimAR542yVRyzJsAR71fsuQsJE8 A9BgOPejTnNNDBDsyDqtRtBxfETVgOIhDG9mcnDK2h0itlO1j7b5WMccsLEQ eLqEtDIDHWGcLYHN293KB4Wq1mUcel8ruik134pN6i7IsMzkiPvzh4QklkKS yjqvORwgePqfqiNRyTKepsHh6KrCUcm2QuMX40gR/T8fPwRikr+mjxjrANrz G+h7CtI0iJmrdjc4vCxJObq14VnQKgMhMDqhK4ZRTO8IkN4Wv/Nkzu9ovIw2 IGWWZf2utMS8PhrliaVuxnUqokmG0R8/iTqQdfHnN/Pm05WU9pjvO4prnZbD /mqa3K9sz3u7kYokHZpFCvTEMOtjWnOgiXqeiPMh8mDHMueVuQaL5EIT6rz8 QLrFnx0Qogl8c5mAgEOatBpt82zORIzpqZLN+WDGE+pTISlHcEoys7z02B2j H+WmYF4JgbSrt1YBsaYF+Rr8NvCf2ITDMGGsnc3eHIHYNU31CFKZumGHLZYZ h9x2dIp5wrNzwDzZztzkkKz+cXzNzGXkg4pboX/t8GNhlMxWkfGVceUFI45X H+FfId3oYsOgQIOmcoB5Mf4KxPm91rIDXHAG5RHyco5YSUUdTmtB1C7tg2QN M1pmTROJQeLGaAf+NDxMki9C9wEdWYehdbVwYqqQLBFIFbj8JJ9NQ9Iu6mOE q7kiVttWpdK4aB7Lyj0eudnlq4UERy+cisWaZ6DCtY/0acNKIxg0tKwoZ+fd bTm/LDg1AVc/afj2G9bcQHXpVpIWWkQPJeFPW5rhCoOq0+jOxqALSw4NC0CB BORsGh9NM1/v1hzIbe0+P0uoO9hgxqUDMhdX57cQRi2xNZByeullwTlbjS1e sdqa1RPvnO+gsqJWyc45YjQXwUWkHZxn4t1FueXw0oUpxZfNmwnynDtF7HBO iG/mVHSQxy2S4oh+Mpvmqy4NXIUEz3SRWb4+mRgxR6dca4AT77xCi6X7UEhp kQ/5hhTR59e/XHz48OJV9BHOgu414U7WKSxfnkyewKRJ/ygoHSSjTjSJJ5Mf hqYDYLf+oBdNnoamI74uftrqPPtRaAr782loCqXvCCv17u/w1lOO8EF8wGf5 Qwap1wCnnWMY9Ye1xo6kHcwlEYGIQDSP2dScRZfdK6740iWhTXCUs+kIQmSr RXRJUnudgc44vm0TfVYzAwiSCflNbvnE8/M3F397QSqlxDKei+mBydZ+dsEW A15g5+x4fnVx+cKpNrMpO3KOGQ1G1mjwg4J3LE6CXuiMPa7GwGYwOk0r0IaS H6SVmATrNFRUGrQCmezJoeG1mLFMnh6lkBmT66BJITPrOfFqjCWRsrDWtp6Q ybkLVwgIAgYCTxS3QQZAur7JlztEvXO+H3tTlWAmM+LJBTOzv6WrfKGbacmE VaHLv55f/TR1WzqZWc7Q2tHp/x50NeWgluPoqr3k/X8ZXYmRZtY+9NPwXLdj XmbhlycdUTO45Y9opmPvZ18WqQsd8XCE089VYj2oDDPLza4mxallF8LlYsiW jS9sBYB7IhSb3MqhXVdnyNaq1AEhmbIMW1wSfTPWJtBFCarMvyI81foijFc4 G+kooQ+8sedSREAzYhSJyDHT2BSr86hfIbrYaJyPWCBb+9nR9BGuC/GVBGqt aQW1RJHrW0SNqjgWAB4GuyOdC/KcBC3UYylBAziLuMzdlmciubWBhkfHQZZN oZw8Ao7vRpKegqSrt8Q8ry7Prs9/BrPKNeY+Jr1Bo5M3Bb6AFcCWZRLjNCYR zKHTBDQ2xcPpPkcykeho/w2a4AnNHTlSzv8QJNwzwN/Y0omckOwrKaqXVNci F1CbIhIHgwtIblv3Ge4oGRN1sdOt0Mo1bOXWkJ+BeQduw9V/WE/UunLW8aYB PWylf+st6c/Pzq8/eUEzGpzgSsPEypkDTNIM5RmzjSwePy1dxqzfjcxncYzQ BU4Bc0FzcWzeshZi+Y96tDKGTopWThq1GWXEfrDB9+xswbXDI3Y251aPD6OG TtvZwBCPuNVhbP8BAfWxqVgEtlFivW9QropLk12XCFPpvnl7FT0f0M8XYkE4 H+Ik/DUrb7KycD4TutVu8evzSw681o0dH43OEtN//ER8JHZy3NDUn3AjTFvq 92FM1knQOOkmp6QGArEOoKJ8+CPrfDK8oWHQDiIdVMFHhix8pguRPm5D4Osl doCQVj5+NppVzWY47yhFZ9PPiBUXN1XBr8MmRKmMtocP7mum5fe8bEsFgEQ3 7NMt1KfkAhOtou6zWdlpaku51Rq1oA5RFGakeSz85fo4n4nWMlc0s3l8MiFG C02xd1x+yvpbtDrJkZo614HE8tI8RTm2VTp3aficJp6jaIpmhYms++vF9fXb T21/q0Zp1alaM1jMg1NzKFdg0zj/9Zc3H962NprtNg0JJuF9ur8KB3G+eC80 1it0m/j3po2BVdMqxYvshicE9m22ZV6ULnbD67AMbSxF+gpefnEgNniDbCIx LuaRiTo/BqV+kmlfAsws3mD5+eHcQzuXlgkZGlqP+Ft1/dfp6quqzr6MTggS tMaIo+KiNMghxr1SvjOf84EZTkYaWb+RBGQhGkmNnivlbHdSTY199QFmklwi zs9XQTqbaficDxrG2VItz74NnqPrYaP7lPLzmjW2szd2kUlBN4tdDdiVcaUU UEGqwWsZcTyJTrxnYxZkko9P1KXoHePanYafkgn+qKNSd9gmhPGM50htQ+kW 3iVOjBNfC4YEt7fMHgEA4ro/CJey4FVKQPCEQJ9i6V4VD6u9tX/EiTn/9fXF OY/+Dmf7Q7FZdt/ksFrQqx944OPkBGCIpye92U0XNlS8hlPtuOGCRPDJQOAJ O7SmgUXhyWj9uNuS8BLjPzzpSYu7/eMqKGOQ/qEDmz/89yT8Ia1cn1+Ctywl tYPZDICckyrR+e6Gzhe7Va0DTev1IheHBCq+Cj3O9MWHfLP7nXgXxBMEh5yA 1oWRI6nPV1kj9D064981+gucRz0/2CxJ74pHgrpp+h/bhQa0OIOj+Y5NxFXV ztjjxAYVfj1XkGuu1dVOGlUrNYcrpzRaVIK5LXQUVxmxClbOMuj229sYYCyA CcsHyfetMpM0J41gY09hR+zDhwzI8CMtw7OWU/XDSJgvHVopQReEmLnMNQAM yZNjCYSgQePy1m2ythiweZ/ayeQcgmIDNsMUBTxQEqV9mdO6zJdLqYSkqUMH DObzJih+RwrLouN0U6YcLctFW3+zg8v09yyIh2la2gOdZpYYjgVGeFBV0SqR FpNvEfSJSvWSXPqd4GFnQDvFpobOBvv8UAd8YYCOTzKvhJnXpMm8rrm+uBiX oVxrATLReQBxT3u8RqFNJv43PF6YzhHOFvi0Wg4v2PC+5/ASi9rsiJkt+RfQ NQhNyr/YaDut6y0A8ESBcabudtUQLlXf4CcFSgYSR2GIOWHtMGGXUqDoM+T1 XE5ZkHEHQk/KgBe2snLTJQgwbJ76Ly0/krr5HeMqQjApIPdfJsyGFZ1FlKu7 O/ChpeVXl9g8gCVEh5jfpXlpWe5tmq+UzcE37r1ddN+X923ofvZGXFhIyt6t Vspnt6vdUp8zPoYp63YlBZsJf/UWcUhqtlG2FsQm4N6bXbV3K1v7EDmbjia8 3RDS8FxY0Rn88+y0wvGGt97iHywcynpFz4APMc4zV5I2k1o5RG3ryrvBghA+ ZrtzeAi5rA/hYusqRdBDWnZMXltw+5CqATgNgkJLyVEkMFrQ6du3R1UsbGsl t0rFaNilVUM0cjyYYiFD3QR+RSM77XPCXU0kF0lLZwrLGhibaCB9Vi80LPFt S5iWBOJxeXKN7tX6VgFi5lczOkk1Z7G3sRe9EzLqBPoiX8CnnoPj/eprNGyx MW7tHiQ4wylu7hI9gQtRXzAkRGS2qrLgfLCMDDx1XMgVeB6nyJhzdS2GCYNa TVNGdusULFOHoVZXoVZg9jcSR6w3OtMkol/5MyKdVCJptN68f3qg3R8NFZlM zRW86qvuO5QN+lDMUY375cUb8Ky0bPt9PlxcXb4Qd+Ic59p5Eqcc6mrU+SlR 4HIwOr68mHqLnYAOBlKGhfFNGM+ofqW3waAdhBmfcis10TsyX3swIj0N32OW Fk/6HQcB/P5eRt809BY94XecHfodT5rqRkinaQN5/pCl2GWZBTECLrxjLZYE 2pWhILKnYakW5jds+F0KXrvPnMqbCw5iUl9l9ZGoSht/JSJGokLnmVHJspez v8gXB3bkhS3GC88I7fMPKqo2oyfExTfIIakY73I9eJwHUtMLyRQT54oItQXC WKOLy/uxIGkmRFaf6bNhtNvwJy/9dxp68Hm1XxNm5Orgl/tst1nycdfYvxXC vZn7sbW72Liy29nCetejgk8+wQV/WrT0+cL57Qbj+N9z9xuEGZRIY4GTKNs6 7s+Wd8b1Xfknel0W6QLv1jG/biRL/1d5beEk/oA+f/3rxxcAtAjNc+d+fBjV euUiCOLJj1jlB6zyEiKKh08e0yG7BcdPZMKHbtz46YDxRqBVHLePaRhpFbc9 hYhnOHVMYTE4OKaYuRzTJw9fkGheadZqmGOqtG40zTpl2wghCC5JqQpcEDee W2/bYgdx92MHyppdcb6xzLGgkoPARedZTsx3VJy3TqqyPgSLcfQ6lyKgTqx8 yggPaIyB80AnT1CWs97Eh4QlBhlEJvcQf/Adw82MyOZJkvKc/0mSEt5+4HKe BF7luB3PN0MphX/B0Qwz0DTQWtjhK6nRNgfM6v9iQkMhbI7yu2fdQXRyLft/ 2MVBUp4CCjUhheL3G6jaqNSY1TDvE+uZ02Yz+hPOyOvxyj1X7aHaVmBhC5S5 MtyaMnxhAwF9qeJAe4meW1NpjmS0lD92YE28Sb9en7WuZHVOar4zEEZhaJd4 Kd510CfzbM2SfgO5hUpjbKQSXwgn5ooPlwPV4KeoGkfXAXVJIvO1JqEmsbLh 45LDcN9yJ7UPU2TufO90djySBc52MR9HYSQNdpmVd6jcoKfXF2eorfNEg8pd DUEnQOmNVgUDMvFYYzPUqBuyIscBYrECHj/YPim6H/mT/aTM+M7RHrJVYEBH e/a9oz14IkCofbSfssn+yNFuQ7l//2hftsoBp6fWlvnphyvX/4NAWz6HQuPy 90c2rlddSkHKjfH6nje60VlIa5/2m4tOyt8WbC5b+bE1b3QYMpWmK86E5VV+ DM612ku5XHk/89DoGcSL2xxCF/I0Hpuz6O9nn95LR8ePxUJrl4iQSqK/5SW7 Lmy7S3UdkIaT/O3y0wuEt9xjOd9kq5zVVEu94/FT1Dua/ohmMrZ+hTh+kogn Gs39lGbiM+q/p5kQEQ9PaybjwLkd93+cnKX+0CE5W8hzHuy433CB5bbCsphg OKxNsjzyoHjqnqA1ETJtoMPFifl8dfnufsC4F8tPkzlb0DbVeSWK5fMPV2cO fEitZo9ZE03LtGUAHERREx4GD0ovkHiSAGR96O1utXKVU25WVkU9Qg4DlzM5 fBIAQ8Gc9KLkaQA8kBSvJ1haI8/xO5Vn4gAAo9rTaQCcHALg+CQAHqDmzCEA 7g98gNxhQYJ2/We2xDYXzFVpgLaG1Na6UQqa1TJsG3wH1w0sfaRcC6dcVqFM DMof+PqysOD5+iIcpx5a5A78DJolIGYtn5aldju6FTOUhnJPE5SGj+UabECs fdMF4ELWmBQarHGdjizd5WyJirJyVndrBRRJr8mTYt5e50u17VTzbINyydJl xfqVDd+X5ewyWWXLdM6eF54jrrDn7+pMTJxSc1Y/1eRNwl7oytiMobDdy1Dd Xisf3+1vynzBR5wDzVyTNp4D52/qDLAVbgr8bDEoaLBBc0PM0e3t/QhHslE0 TUrV1cCWwLKM+pE3Wdv0wIWrkfVAa0AXa087J5amBqaFDpOxaNj4u8tUfV7Q DCsO3X3lYu5tOsrFpQkrXX3M6hK9HJ5fXF6SWu6D65yY+oGY7O/EykEoNIL2 T0XK9YdPh7nFgYPne+mkw9Df0wZc8bGwfCehTtnOCOn1DwEXu9mZJ+l6OQMy rJSVpsTlUibaeBMz28a0C8ycYx+QNvTSwWUxYTmnZK6dODU9JI20yktgxu2Z L6wlwayt2X6TQZzotocFzozd9lbFKCECeCLyf1rVRYpDDvqdp8bxdKMQPxOC 1HpPfNygN+U1Myg2Ty0aMR6g3B6hJwjfu2zFSs42K6QNhEbxrvVpPsvTRgKw zN3aXriYbvSc/bO83gCtfFSGBvN54R7YgXpJumpYvQprwI6yZZnZNbAhUg31 DRLe7RY9mW8EWyKuklnDi/NVP5dMLY4Ge+mial5IWC5OrfdRaeVhrv8TpPXy VZ5eGFJz7W7NBu66dGAtlVwhkHSDFRdfvawmB0WrJ+gGVjsEOBCczsxzWkIs L9c0u5NMEJwALRPficarohNl9bwnyrLVzl3IGcD6bb7k/LidWEzhlCkjiee4 Z2Gk07DryvVj+LGp3obgH8xH5O9SQinAnlVBLnlVsjAQTYcQRSD7XVIHxUlg wgLwQblp3jBaUA/a5I2rIDkRL4b3qlhwWpur6hjNKmdNU4RsY1DfTGubPWE1 FwJP2SkHRlBZP88rY7p8TrurItW6UVJCUZ1ZJCzgmeyCQLtSa7+yTW7nRdfG YtAonF2LCm9BqTwXM+cvFfEo8fjPnQnv16uOebsjbIqjRApVKo0HbXQnvxLP 6wUepeH82iZSExXhnNNgNKaZ3UYq3LBDncR2UNKKmaWcNM1fK5k1ECeg0T9k m2V9t2+219qolcWF63GhtOi58yxyfIzW6kK1FzUtMcKT9hJ56D3FRkhN/CDv 8mCxTLBY7BemgbquyIO2tpM2qmodCtcnSEbXhl5ucTbo2fPcxhouvIgl5bbi wBDSvv08XugK+00UgKSkdpv/jsfb8vtBqcSoWfX+ZFKoS/Rv6N4e95iGJgYW pGX7aY/RDsshEA7oxcXYiDv3+EPiqwzHRnF7qWbLzoNCxZe23eoGVcvZ8P3H Twd9yLhOMdgDyQwJHO0fae7VCZo62gYgc5vBrq2vUELFcCQaDr+4hhq9vzra PSFoKOtatm3xYemCK0zY6sQ6bd4xfnoTmFT1vfgdVky5mr8KL3R+45oYq93/ f1cnmE7QGMN3hAn6OqkINlzAImi39O1Vu33LiapRRzu9GFdkQmekCdQcRWML E2pVYMlR9hZJR2lHt5f46SOv5yMr/LS5j9ElcCz9+1mtU48AAI8ys0c+q9Ej 3dXtdl/xz24Uyb/6p/7b/Ek3oHAzxiHgTP+M6P/DEX7GoyF+Dvv4OY4juXY0 9teO+YJBPME/fdL/6Z9kzLdO9fIh/ry84iF4oNFkLKPir4E8IZGLB/xYHTvm 0UYydjzBN8kQn81mdujYDj3lofBn0seIg5gnNNZhE3yGSK9H1EugHxN+9tS+ VzTRlxtMJuGQ8WSW8DUDXJ/woEO7DrNpMNeRPA9XzAb4Y4TnjCd67WTmJoC7 hjEmlMh6DXnC9srRwI865IfH40RWF8vGqznt68X8Mq/PL/l7PHSI0Xl9B7p8 ulYA2H62/G6J7HEsF47t1sm7JW6+vPvJYCTr0efrJvh6aKcxmOC7t79v3RqN EtlWnm2CJR3ZBR67PZONHfPE4iEvPL/pZGAXLWnsRZLgn+mMN3A4C9dh4gf9 3qVjT478ShO+dyS0INPu2zUbuwnITk352njCYzC1gf5l2ANiiGe4asY7P2PC Tyb/3vF8dDVnaSIy9pTH5t2OZR0TWWB37XPINNrBF7hJNpcvnPGixEwucR8z 0jQ4W9b2ZKpJyOZym7xvvWzggwO1v9t8i7wyEEyZrbPVIxoJe1gdaTjW6Bpf +2mZYFrSmEt8bBD4NJdwFkM3C5IOgpELh2xNElzp6oBwxRqu9bnMBPc1gvoO hYGR16U52KdJZURbLTwsySUIotWGy/ZxkEByW20dImGn14exsqTS9Eah56G1 BD4h9k7qFbnCOarWSy+ntF1Xb8tRNKJmGeeBPOhCh4DHTHUavKVvNK+B59I2 SMx35njUYkchpvOfasXog0bftDKf3XZpy2JVw6b9/3C5GXbB3IgSfOnlc8fE dLlNUrU5t5gEPmcFTB2LLRGubc3aTcr5/ZCxgU3wVTm8JG9VMGx056u4yqvN w/LVpNHo5Fb0jyO1UFAigXtkVYSKhcyMHaAIlLWwSJXWX1ppoMwRAG1CX7jr uOzTzCq0E+FKkkRoK60uBaWFW1+gQqsLsnI0SeRz8hWYgqTaI48QcgoJ7ECV 7YPILR70xJpqzzR4AcOONj6URFCVK8+jvhWsNikqXEcC8tL1tmk0u9GEtFds KIueo38KeOgBCGOcGxnh3MrI3b+Ooxt0h3HSUfDUaDqMDHrKWOnCgmiaDOjT ZBoiMRY3g/4Ul/O9KmQH/IPkjEFbGzsMy16CSDw6QwORcyxgZyQBDRrUOJEG STKjLw0a3ThxL+htNpzwM6cOX+C+KU88mQRTTASbkEQ06Jzjntln2ceXTwfN mfRnfPE0hJE80ggLwFhQL2eh2+/jNQcTN4oIaYh1g+Y67uMJLwEeGXvkgA8H MgLjACui+34mg75DDwycZHqTob+aIRuNrySBbkSnSUIpok0QnjIMt8Nx0x7J Mw232mnNcCcxaoYb40QNqDecjgz30AnfdDidGm7K01hxeprhJjvuU8HAA56J W1fGBSN8OJgFL89rMsbDhGLfMMXiixmGHUwDYMkwWV9mNnE0xYgKFdC57ZB9 HmN5HSREp0nfP3HqyFV2LEl4em2wJY8czOIjVw8HzU+Howm/d4iHGY3H/EQ+ WzLtUWMHhvz28g0DqeQoE+K+fSrMgsh+YU2O+6id4BaVIyox83AXA/r9HzuY dlaZY2SizjJvIqb0d/DQR84GxNXJ6D/or4/yUCJJHYQ+NgH5vbL/CE9i1khr z8RD+FF2nlaLm0URvY/5kz7vVTyejLgtGP8+k73BOg6ToEdizQ4+mSoXMdyV kdgkhbPzrwCRLO/hfbL9WzEZqUZNYoBjZaXflxZ/YZSparFt71IFl2LKPbsR yMdII4lJQoLeWtsXso0VEKlG9N6KPU1czbxEAS7zTEqhwhhZi612w+1AeYo3 +1Znd02ehps1KAFrKz7zaqyzDDBSm1PB8WwbrPGrEbjDZeeff/10/e2bRUl+ XFQVCxv6wvoswuqPP+i7v789+wUFBh0xfLqxloItz/Kyh9936zX6xfSYWtha cKYYnz87sy6Al3jcSWI5SjlJX9Ql0Ub6rP9NhYz6bBIY9WJLTIkoP3EiygrT 1ExVWv5q0Jta+krEHDARZT9WZbPPT5nyPbNeX6Eze+CK1W69cQeFDbTwoeUL LYXKnlXeWH11WWTT2jxscmP5LZ0uetFF0LFV3NNzH25sinKZblxlyVzM2Y2h wzTFStxBvh+sJEcamWYj1fg4lREjkRihxeFhMmxaXub32YapxWca+2LnqfMV Isdbi5JE6gzRaEKzCVIk7/bbggmQFT4U1MYh2mUu4JJOGb0xnsqhAOly55p+ BBa6oyeMYxTlTQJo94URv1GIjeL1vDiIbySwD69Dtgha20l269S1HXHrZhrr xjvX5CVqfquyIIGzVSABo4QVZDnSX6bQbkqgW4hq5ahbDSM+t3rT3oWOUcI7 xFVhmS+Gc3TSIkyqQgkk46/P9ljme1LImNZZJdNMxL1uvSasEtk+ZH6J7zIh MiYGYa+eqi3d+bCRmCCCJ1rLpYM+4Am4LizATXXx0ttH4cWxR7VkLTfsoWCx evVEkw0YEhiLB9F7+WEKomRgOtVbFoRUU9oJZ5fPN6Zp9ZXXP2y3666x3luW K7bfzO2prjS2Rij3y01rX6GxUSnE2FRrG4N40K64tvmqolF6+4g3jAgtcVt1 LurbXFBrU25sHoSxFirNK1VsAvjKRuRfOWXShTs8qmpvPzBOPsjPV61/TNOG LJZjMfcOTdNmrHbihEHhNMHXgY1YzMJ9/dW0TMJiBkYvNpY7AxMagcX0y+Ak HsxMw+zL9j0x+prQyqum3QlLp1k/MU27rthyhwxJRwQQG5Zcsd+KeRQzCU23 aq4dsBFwPKQXCY21bKHl545NyzQr5liUCoEFEsMGtlhrfx3ydJMJv4s3vqrB dSwmbVIQGuZWMbEOxP7Xx72hhVU/xutOZtiTwKbKlkvoBu5Lb0VVyynPYjDG hnmrqVpKE3EgjJKxaRpKxTg64GUcD8ffpbEAwljrZzJlVWQ8CNr/afjvkSoH uTebHDM9WINgxyiiZxYTByZDDQMmRcKWEBbrTcN/1MzyZ3DqbFi/2BbA7Kbn 7kYaDxpmwwhPDFyjoe1Vg+5NuyKSvvaR7t+Hdlbx61opwfVMRMIJvTU6PzcM sfKGuyazWJTFtnJZoZx9MXFLKe0XaUFJcvH3UFls/k5Rp6uT/rf3jZLiaXSb PRjP16QVkIb+5Wtl4IA17Xgh8aVXzGBZsIZXW47L9YEbJu6TdbgJV8GUFEwl k/6u2GUpSNh6JTT39qm53C1HyxZphnGjqu8RM6wShA8CsGUqRAhLOqTv63QZ vIf1x15zYEnzugPPpQvnUFUO54CEIb0kHT/zn4HtVezQB7SGF9KgAY6HWOaS 9kHvqpEoHZv8aKJjYjL3Zun/YZ/YiGFx98vN1h8fVGQIWtBrcWPGP5HLE3YN jFQOqx/fPe9gWTrWIQIzJEdcaanEY+EAiOaJbKmgpmH5qOQ+sglsnoapXSN3 4Tq2FGlafuXeE45iW50fjFPXUD4kAonEY/ycz+CLlmfq0JB58t+j/mMWFVNR FaMnnccsbYci1aKn/MbM6EcTBw5Ouoyn4vjEj+iks5hNbSJ4oqc8xUMxoOlg J9zEg5kDJTK3ky5itsGxrzWJTruH2WJlX+C0Z5hNonZBTvqEefFYuosUPukQ ZqgycOjrpC9YVjwWI3T0lB+YZ2mffMoDzIvHbzyITjp/2Zs+dTt8wu974qq2 y3fK5r5En3jS3St7xe8RPeXpHTuC5xvUyxuFWCVSyMfrJ6vHq9Hl1W1fyvOQ IAJLV02nmBedGthj3VIcgSZqLlvgmv7YzFghDpby1fYaEKFUIzg3QqAyl1vj 8KBMfYMNZ6SCBqPhsR7WONAAobFzHT9C8CDTdXAhFUDAMMx4GGa9Q6/0VZIQ bNVNMdY5AHEkrgxf7y5vtAEULXskpercgKLkcwVEWmprLumofUC58n1aqtyT ggOSQXqNhn6+MBQvAMwotlu7UQnyYBcm00UqpT4jUoVJWKDJWxAL5SzF+mzu gCNFnAw9aMeJE/LQTTgI1Lv/ZGdeaEBaemuyy5jVy9I1R701y+mmQZMAafkT Vuog7Zlu/qK1B2niHD63iYKG6FpKUCIaOwczctGk7S+0jLYr7GOvaPU+5yAr Nr9znm3diLYSGub4qfNgkU9IwyMy8Eekn2Gr61blbL83wsnu9nusgvZ7Go2B 1IuuxGXRh8wO6Tu5ZDjiS3jR+FaWf125l76PRcDRU84UY+BT5pZ4zkQumsol um7ykVzBPAzDzsyjlEHC2cMVffvNWP8dGaujSAT2MfoKT1/TZc+JQDY9xNXf 1LBieHH1V4eXGYhjtBaYV3phmNukSI5Mx/zahPiix23s+YnVrtyWOTA3iuTk WjjeYnNrO/SZxQfkyC+C9iZSEISZaoQeLOzO5gh1e2rpWLhxJI8blShLmFRt y+zgNNhK00EkKAN/oA0+XY3eRd+ClNS6EoXC9oZ1YZOWbYdNun3kqZp+tY9I tqmyV2ybdivOMcuVuPddeqqFwsFznGlQ4w68TdmlWhsURcu5pa/Oyh25Rl31 Qz5jA4/BJA9jKB1NktpH2/QdosSBDpp0Xgd82zDfZquslxItMeKYtBTHcnVL FsSInCE76XupYRkIGksQ5I79V6Y1tDsk/NCiRD8qWyKpsgKQNQsTtkJ+FQYS o7Zxlt9nTVXJhe/oujdDjLSNuCjg/BipH1iwnRg35KUrONvROoMcwM51vbmj aIUm7xsSWcYnqkqoCHrIBwnL3lqfV9oORownPAY/HUb2BSfiIz8o94aYXKoj V8HupCLxhQakbY51ROT/9EkZ5uAIIwqHuL/U4zrUHG2HXFd59k6z8qRo4xH9 2pWBdPrpEUO1S6OC/3GRrYuak6ylvw6GFp3UpVog4KQCUfNKhwWBdL7u/O61 SqxxOR7avnbHnX5qjfNeFJs/1RL1zu9HUorP+2Zf37mjTYtF9DUnOpMWRZXU j7NvhMYBCNgnyW932hg1AldfrfPTrpyPvG7FLXNlzAPUxRk4ppHE8JBxVTSx M4RnmiR33I3A1mV43iCXBe832n9W24QRW10XvnSsChz3kcItzmeRE+lSLTi9 iI8AB/2JeYBeO9Hn24dJWF5YQMKZEKxNYYc6Rehdjd7XJR5LtxC5ltIXh42H nNJkiXfvskXYm3Td6NOMdcIYBLJ1/CfyD2jCg9aE2cwFKUZnnSuRNWquEgHa 3SFS2CKcD4M0PCbs7eNdcmNZlxOzqb1i48BBiEpUtM3M1muj7pA07DjxpyoU WSpBG6Wrd1xxpXK1VWnwjPsO2ghQmx96aNMkYmnE8ssNyhuD603DBtppI93A 69KV+D/OLP3pJ0ZzfBeN7mI/UiRDVE+KOO/mlPbZjZ6UN3vTDC/gRnGNEtSu Q1fbRGmjS4JbDOskX8CwlA83YgD1qD67KfJVVm6BZJ5pZKYsE0BLJce/Y8Bp QADAdgymII7D4TTluNETITrjFXEMgxfFtBdF/HjcJPzeFgLlSee1ZnKQFCZe xQcu5khb4QtSVyOzu5B07Y6E1WO0dfBBf3si1rtMlNK0trKb7YgdnDZNAM2k 8ghn987LYrNfByWi6HDIeQsfq/lEnExj69XAHtycjVRy5KFt8yI81fUv8inZ kl/F5dJvxT+54Rxau/C9CCGqf3eVIqqO8DnOtN87Gy5/16gxoefLYwaBHBm6 dw67toDEfRZ0uLg+TGWJbCpLagN07tLVbUMmWE7mgGvY5UvJ1hYoXt365WUe mx0u7TErpzuPp42XB8bJ5IgdcnhgcRwcsS0mB3bE5IjN8MA+ODhiChwcmv3i I0a+5NCilxwx3iWHdrrBEYPcgfUtObC0JQdmteTAhDY4NJYdMYzhMwlKJ9hy V3DIgHBKZvOuhyQXcyMCL2z6nWlqZt+x2LfN/WX2GyNP08zDoyOYawHCKnNj pirWtA4XDq+WPGAre5Bi2LQSCeOWOikI6+bICWkSkmlRYK4L6pP+5WDQo58R GKKXXds5PGs20j3onChy51DWGduqh1SSktagWCO2PFsJ7JZw9YEGkQRxZL5Y 17EOS583mXb9DAMPtANox0lkFFyq5mXufFhSr8Omx3EQuJGwbX/UScqXUoyy mdfgcpjTRq4CCREOFsHqmNqVpnCZDCfcJvzCTYXdxsubJ4ADqxzuex/332gQ VfldHAiLA/2U2ZJzcG3Sh6Q4si0B1G/EjKfV3K1a4Nq8ACuGRgFbTAPDB4FH Jz2RNjDH1sbGjOKhyBuM8cpMR2hJTqs95J8D/png55R/n8zwc8C/9/H7YIIr B2P+fYx7B6O4g1gKCV8Et+tFz8V8MZ7oZ+OZFFJtdDGOaRPLfCUzfMEokAsQ SdEZ04xSadHqzb65tM04KSiQUCdlR9YOoaL0fabkeUMn/Bme+Tpd0kl9h4oT l+n8a7qEZHnH9Bk9/1vc6794ZhxRDkCUTfnEeOnvpHxx0+Zrkp432eKZo+Pp QLug751vGkcEVbjkEAj0j6o9id21K1vD1WoqLhqrRKcZMqsV6lcSmUgN/10t OTe3u03Qjua4W/piI9VjcEbE8G68tiSIgCs7OwS+OFjcDqvE4Ii7NXffQ7dv hDnKZGmkTXqfL1M1Yodn0DZBx6FxPNUtSfhQMTIeHt+ggM3pkAWJpCMpx0yD 3rdeZaR5Saq2lCMqVvBdcFeYihTledYunUF3cyDnCsshCetGy/AAnDUHAfPh GEfmnvApLwjbYAXs8JZ3mN+Km451kUsVNYbOVjHMpcr4Dawrmt/PKpC+vtRJ gOiqtvlXAeuYKuopdKSuh1QmsLWw6YWFRFf5bSZi0Jq+jI5pW0fQY4mCFqlU lIYhE0gUCViatW1n7HxFe05cIgDNgE9gqAsPTEMuixWErck7eFigwyZrREDy LB/yKpMa8tW6AJl6giHVyqaln3NaevTHTzZRHenwF9phD1aCwvp9oJjg6cAO ooPZbkitHHcbERylKLKBaAQ0kg/QiFXpi+1OcbwYaCUYtbipnV9HBzY6cChR r7I1zSafR1fzuwJ86+zywial/2MnzSNtVjvxhVdSq+iurrevXr4kNaVX6QCV 3N8ryuVLoPoouo9fckOTl3G/F0+G08nL8nYOuPpnPdb/pVkK/+U1hP8LQbpS 70cMj7T4Oo2Owxs5zBY5fewLO+TCfGF4fvP5wqscHeNENceEcLdGh/dtd0w6 9qjgYOcZthHxD9AzbBelzOpduWGZaBcJaA/F7bJGBdGUo5EYFVracFKdAdnr 1PWQhD7RvrjlgoPZSYCm95mJUzWAn+5BbUeV+8ZKZ85tw9yP6OeS9wZTmhEt jYZ752ceNUQ9h8LTlxLdrEGoO00UVFNBxQ0+OKblO1OSUlOa4BbPYOVRkKHv LsKzRMmi7F6W7/O8LjDmuGPv+Sk4oZ/0Pn9EuzrUNzUhcSGbYyN1GqfIHs9g DxGnGwSros8npichq8/xJo28q2verkepcIUHhGkMUTObgQNUH6GePMaPfQ5J tX/FHIH6eHn1OIynj0l/yFGn8u3gUWJM8S1d+chRpY/Elh/7GIUUPXzDv5OK J/fIX5OZv4zUunC4ZPZI6pyOECfyVTJ6jMccfsf3DR+HHNz5SOqbzJFUN/+s SaIz4khN//t47K4hFS34fOrflo+ftQFbG76QmkU1w7HUjCRWcJvK9nDg4zyv /cFP+kZzePyeeQcRxI53yVkVDKFtLKW/Znup8I6i9bbIq3AGrevrs2KlJZTW IVazESaROXNFVROPEBOkbQKFGklazHAn8f9hODi0Fu8gd+fPNo4yVw1n4lEG r8NVjaH8IZQOLXQQLJZrIB7ugiJeqjQI9Q/u10W2pV2kC4f2MXffuqqdsqkb GAKDjdLtCazzebNZnCpgHjKDqUgfriebnHEx3vNLLaF7dKOMRFaKhsgpAKHH dU4oak1PCRal6l070O0nbnTiHKqvFRSrNTSlI4vuAkY5ilCX1F5/k6eMETZB 4Ry/3Km44X5HyAW3bjzbHPLmv6SbHZQ25qniGxXvhM1xi8SSQbK3SQnE1jZZ c6w3hArxArqG2osTYptNh2wHA33XLrVFe4Nif83h/mbt7td+vs0UcWBPHCCt GH6TGVfJ7bp5zm27icaYZ7vlrgpU+2BWcps5uIWlSPT82kYKLSVeBL/qJqoi K+gzoAkeizMjpdFF4X1k1tf7Qm3zVjByyDZkqMi8/pQRUFEuxPMmKYI3BBVW +UYcHDDjh6WKPGGFraQV47Pq33q7ILUvWOoHV0OVrVwa2uxNXT3zxqm/fsDQ B8mp6WXWcKjKEWASWwjdBWZhOCUQjISHLBalOCbylmcmsqG9TvqyhmlVNXY8 G1sA++hacIR3qL//qWIdRBx7jSU04W2MpL1Bg2GRNy0H2+6p68RAGhwlMgWU g/BkBQn9UyCBWz1LKvIPAAaLG5DAL0J4MH2Mh4/xiHP3WbQOSaD3OWlfpOt4 Rl8/TjhbX+6Z0G18ScJAIaYLHhNOz8efBCXGJJCRlo8/BwmNl3A+PmMAggQj ggHIw2fAkNC9PNhEnzeRv+PZCLdPCDQknHCPv6aMc5Bnr5J/KF/Hw0S+HuLr wYQvHslAw/7QAp0+p9HzJBlOIH9eBprS3wmnzcudeu3QgR/6m7fiIE/ebgW+ 6MZSieZf2QrkzdsZxQb58vLM2TSheYzpowEtOFZKljmx7zOY8DojM55hXsIv j5R4WTe8fKLrRiNgE5AErwtHf/LNtOlv8MJ4QeS969e0xXL/bMK7RpsXx3IJ r9Bgphc4qKd0g/R2ns6jXG7xI43I7zeYyf2xXD0cyJ/y/MQ+f6rzSQb89Fj+ HNJkFX5iO04nqh+DLs3DVx1XucRfk1rWr9rz99LXf/Gn+DH6UCAIopXC/rNk TtoM9oAYwkRkrc0hCkE/0lDpZskOFM3RCN4k7k1GwbcdTWFRfsCX8NXDXvMy pz1JUo88i1O+mrUghj3JTBvwKIOkl4yCC+zjlOb7kUZOt686+TQF7aF+KlkB jVKS2n5PAqaa+EMMmqsFl46BpGCYDpq4yWy8mQgY7SK75Bp64kbZplUF6w5A J5pVaQQwKsqW6IZZh8FtB9nsAV2p2GqqzMZH3x7RmCMpLoQ6QGyFgwu6lcgb lhZ05Clkp/VfJJDIubBd+Z6j0k0tYrfpwok6funPQKCQjQ16D4wgNmfcafFc +odnLXjKQqGGQl1x1xDij2+y7arYS9Gg015Xw0ZjGAmt8fjoSgd6uMTvtnX1 b1JbFHBQCiW4uox2FlxnYWPTzXkUWc5ueTv31Sq5EMFR9dy/4WPwcj+qo4M/ 7dYNRd195LV1BLY01HV/jWrFeoXT2j+9PAv0dlfgI1Tf/WdOiUdUeajG+0uc Mo+D09Tn5dFeo+fY9ECp1zusXi/PsJq9exGr3rsPrI7v5uA0fX+JU/f5GeYd F3MKISA0T7UBcLAsio+leYkGyTf3UqwYp6RlrDFz1DtnezIX9eUiYsXveVC5 /RnHXz9jLW+jntLQQqDpCw+FQGl+CoNajlFqG4fYOsVeDakhp/SJwtYcLQGh lpXAlWJcN1aV5blVuzlMzLe7lWgWDwET4KR6P4UqfWgYtf054NQ9MJxlWm6k grA2sXZFDUIF9Lz1BmACi5JT85EvZhVfW5Jbomy4qDRegfaoyo4EGms6mZ+V FEpIHw7tNqwz6Wo5vsPuVNsuijmnhrhqbIxrZeiqAGN9TGhMUeasrPPIbmEl GsaFvDKs+Df7MR0sAXve1VsutffahgdrYKD1lYxVq65tkSkAYmV80WkbqgL9 mLW0thEE2F48fqbdxtN38axshzdXg1uSV1r3iOujLlakOMEt4frE+c4qLHOd scQGQdCZKst926eCgIfSMmVnKKulH6FQMxT4G58wAquYYWsLDvIxY4taydRY 5DbPbj1C5bVIT35PEG4plCJlIOldtcC6WHTQvTHb1s3sZhcTf3wPWCjCUOE2 ABheNqBZP880dsA2K7rYSOfmd/mqznwDTe5Q4QpQ07M+pntUn+njwOlzpsmE U5dq78+T6d2Wrvy8GiFYMIq5uszozC84Sh4eMFGX0c6gEhmXS6d1LjnN3gtb vsSDEzW2YJpcmR8r5E5r7GIgjDCXSuo2EoILhbl1XhKbtu9pF3A8HI1QQki4 aGUOTW2eN7F5hye1LJRhh+0zfDSGQQvOyvMP7Wp3l9nVHAz6Yh8O2Uwv+suO a/IA64a2NSNe0KL2xmbrqmt0ccFVYE9I4lotWt1IitKI6UNLaNRsw77PKw3H OY6pvmQ3kVc5gAIbHbdc/I4NbtEJFg7XNZ2CKtAaBiXlXJmTqXZ0Bq3shbrT nuUNvMmi14j3S6xbymq5Rvz7olhqk5bXbD63wtuKWblYSlg9o0lt6L9n5nnW W/Y6Ee9pHL9QIVls94fFq6wDIJwB21tl4GyzzDWg2lZWusmkZzi79rW+kg7i YmPsO3TMVvpviCNIIkGG0HCSfu8H8KK+/yO//Q+YBkLkCMvEbNhAjglhJvzd 9PSMZv3+43Ay1TojFtuNkpg0+GGAIUn37j+OZiO+0CHJwWwAo1CAJpMx6fL9 Wb/pDRoMRvRp3G94hUa4lD5reoemsCZI4RMPLGEHGMbj/oG3KKEnTpN+CDFh BphJ4RQHM/Gusd5vseZwNnucJQHcHM7GNOIsdCeN4r69z2HOCf0So+6Kw5xj mvFw0sCceKE4mTQdTdbeCCT6mkFUmQWtK7yriHjo3V6t61ofISbshfNpRrMO bUKrcd6fow8NZBv4ttDhMs1XfBS1Jec6/531HISmc/KYCyOSwqlSte1Ysz3f +wjPAiu5KuZfs9r24jAcopByn4QHddzKmO7oavYG3qVyGWbbHbt4JKhX24J0 iJOTvrdFVN9K+mcu6YD+hmwBqZsEzpItIt8ClKDFHbwMesRZmLO4eYYVfNYz n5nFSc4i4+rWEIh6I+HsrD6lzSZyH5F4nmtJOuOt9+K1k/p8+20mAfA0awYL 8GuEubEinnwfTyWLYiNEgQQqCS6bSODa1IepjThMLZEwtanwNpCr8CjZ9NZ4 xjZ3kKWWmmkSDEJCsFhorx4pOiw8p8NheOymYJHsY5PTKBn1GwzeotsQWD/c kYDmdyBBkhI9RZzYIe1YhRseCmkQNNu04Xx8Y5POKhsemtYGHosILgshKX3w sXzEJyICrA/TqA/TJbzRqm0lzMeVJ3nlDp9fabsk8DuEBnlnYYKAOFDh+CTD E5rPSW1pnlXjdFB7Qlkva3TFbBxGnFusRWWpCrssiU+QP05T4GUKm5XROK5N BlqvySAcRLUlDC2hXMY11tQMrCy1rlyHa1Q0WSYjr8c5dWw688XvjNipBDT8 qQqwREfL8FleciQsolH7RiLmUILMFs1Grz5eG9/2wlL+rc7QLm3PztjhC/Y4 a58WVDHsNLimRN4ZTXzTEDeFQy6EyBrq9KE45ZxmCdWTOBYfSQsl9GTKuDah Tr9zLuWw+h1HD0TLXQpNytYCtNRksaS2GXyw/Yy9c9rmcUWfVTVi0XFnG235 Fy1a0Q9hgtdBZAPHw5G6pZkZjJcC+Mr12gL9XOLaPvv4X6G1T/DQX9XZlgNo CgQ3gU1+C0ONiVSWRSredOexdH11kFZWsvaudXXY6ELvjNgZ2/pRCiwGCRm2 /nrYOAjpmYHbU0+H8dULmgW1bbweKuvZgjTmjz8O2td8a9Z8cE7kwDp6vF6/ DzGr8nWuM3ywGp7k4GlQQKDNi0gNM3u5Bi2DCmaTpWdPzSJ5UnVU41ZkA5pp nVYxbtbXYP0W4swfDZt2/FYqTaHZ44JegdsT2JJed8oGNSrhtpizjS0ruaGT K6xYBM12uF8iihtKcaPq0NgsCbmNWDL3udF6F6yLB9EkqfaHpdOyREakd9W4 lE1t3+03xKXVStNHHicTnUjrTrgsJ++xdYHzpbeUkVpBRBGEXVa+W1JkzMdg rq7G/+kKkS5alQOZTViQ0aWY3EGX5OzvwMKgLoQHUZuRYYt3hEndHDykBcw0 0FbazzXphbtCnhN8IJXXJk2WGTqpeacHSRVaLtd21SVtaAUHX9tTKT14p150 1X6NIAaFLUHWpMYw2tcxMZKO5Swmh0Nw63ZWvdMFEy5i0CHTbnY0+w26pxvH nOeEh0qOrKGrFlm3uL11+an+SXwk2ejBKEYTqo10ygO/UgYgiAx30Bjw+Njg eX/+lLX0oucXrglDUCE2fB11abXXsVGsE2Nr6AQCl43tBprLnqCTvUzPYrrw ZglOXe0ReHJ9PFRdYskzdsPY2I1eIwHCNMo1uIN9PKu1CuDrTeZ6Wgi9IspN D4FsTmhF9BmpwbmjA2xzD1gYOINgmIrSgI5H3UdBDqCLi7Z6gtTrY1PWtijK 6EhB4EMvwXl7lLAlYpNvOItmYJ/W1r9qNDK21aIYSu+BnZEq0Ki74yCzr07s qkQSAgpcYWzytGNr3Z9DneO2jbSgfszTbb1rhOm45dfXSH2K6BH18wCSWpuV o/p7X41Z4y75gHpbvfpu5KQH2Mk5N615/gBDsRLokKKrZRKmbGvtksrF2dmA PYmhj54JLKrvnukLpCuO5zKi0iuIET0d9tgsW3DrvaKBOoJK+h5hEcAzDuBF AvCY01sJAkYSlDYM2atNvDPtUr7aAJ29SQ/c+i/sHYn0XvZT4+gWa67yQMod TPX2RSC1bAvYsCh8+Iz2IrLvxz6ncqgt8i1kGyFnWubbBGW+OUmcu/MIA5QE D+6Py37cMHkDdAMB/YyO131+j9JTeVo9C9PIWAtTmeSSL129ZZutJG1zaS3T MDlpDdtDxBVJXVyXxLZVmlYBbRumijvZ1WbZEOJnqk6HBaOdf0oiDAjGLH1T UFq11PIitAEQY1GzCZP0f+FruFxGUz1Q6uEcdNTSgGfVWCu17XGspdPqosDS oPSGVHfPK8hZ+nbheumC7GBgMDw1ti8gX2XfthjbYe3r+RrwRWSclyvMKdCG 4gFpkD68WSCumRvLGttYVnePr6O15boS1pUZtvzlymNsYqKjlc6tqOJjDIEt GbwFsSaQKKbHPlTrAr61RVW2uxJk0osuczq+UkwGJXMU2NSaqdoxJJUYiGA/ 3NyFrDVmGHRtNZZ7wJmlOA3YQr1vvXXPfJGOEJZsFEZUxWonIozkRrn0EKwB 2v4cfbaVb2z9+1Aw897ecyE8ovNV+qCD5LZpbLriER6aU2BN8lZORbpC7+Pd EoLhZgWL4cJan0Acf46+aHwv/sIqVju7HLbWAmoVbHbZn83PBC1udyvEpOMR OEOsEHPQJ87RV5hQOFvLrpvw7J+iK+vGPFc2o84Z5USc6OxAs4i6PZeVD2LM v2QqflzmFZj/P70/x/lK86raWTNjuIacBNNq4enkqvVJi+7MtSh+ZLKubhhN tll16zJDaPOmkWfrbmvq/nxjLll4wuH3ga5sbGKb17OOpj7+FJ3NwTpIkgla oSl/xFBQQb+64KgW7GtkbnMGJq8bdpYhe2Gs1fKEdHxlPpKilhKGOYN4Iea9 6Zj/N0Xqxtkq75irtEzvoteYQse8LnebAuHnZZptSDf4ANX2Lfq31x3zieT8 Jo/eroiQ6Nq/QKTk6+gdKY0bGuhNTre+Q7GSdD6nv89pbdiM+y5fVbc5ClFc 7X6jlXq/29YpXU/c+Oe0lMH+Rnft06/Rz9lyQc99nW1+Q4/b6K/pYvcVz7qj 31dwsdPsz+akxX9AJjpxjE/516KKPqb3xLZyRKBsiQ8VNORlCjn7Nfo4p1Xe 8TO4lOJHQvebgkZZ4dcaxUzONosyy6NLuve+Y96WwHEZEWa5onli+egZ0RXS xWlqd7v7dJNVD7BARX8D+ISmTHuI5SqiLxnKdzCHMh/y6O/5P4mrklhrbfXZ okRMI60XQU5mlKBe4g+cgLi4z+eIhinYHgQzlly4YsZ3XtBGoIk91s5GtRHX We7yRcoF34QCtEhIkOWWSsG7NwC952XhNJ5Uu6TfSc6M0UYJBv/BsQa6Mv6/ /x+YZQ0Qg/wAAA== --></rfc>