RFC Editor Reports

This page contains useful information regarding the performance of the RFC Production Center (RPC). It includes news items (updated as needed) and stats about production that are updated on a monthly basis.

The RFC Editor strives to provide excellent and timely editorial service. To ensure the RFC Editor is providing the best possible service, the RPC regularly reviews its processes and liaises with the communities served. In addition, the rfc-interest mailing list is dedicated to discussing topics related to the RFC Editor.

Table of Contents

Service Level Agreements

The Service Level Ageement indicates that 67% of the documents should be published with an RFC-Editor time (RET) of 6 weeks or less. The following table indicates whether we are meeting this goal. It also includes a running 12-month average. Note that pre-2014 SLA monthly reports are available in the reports archive.


June 2014:The processing times over the last few months have been particularly high as the RPC worked its way through a few big cluters (e.g., httpbis), which are processed simultaneously.

While processing times have been high, the graphs below show that the overall queue is decreasing in size and is becoming more managable. The RPC continues to work through the current queue, and at the same time continues to train its newest editor. In addition, staff is working with the RSE to get the new Style Guide published and provide input on various discussion (e.g., RFC design, SoWs for tools).

May 2014:

Thanks to the additional support from the IAOC to work through the recent busrt of submissions, we have a new editor that started working with the RPC in May. In addition to processing documents, the RPC has updated their procedures and invested in the training of their newest editor.

April 2014: The RFC Editor did not meet the SLA target for the fourth month in a row. The 67th percentile indicates that we are just short of hitting the 6-week goal.

By this time of year, we would normally be seeing a slow down in documents moving into EDIT, after the submission burst associated with the IESG turnover. However, that slow period has not yet started, as we've seen an average (or even slightly high) number of documents move to EDIT in March and April (36 in March and 32 in April). 52% of the documents submitted for publication in 2013 have already been approved for publication in the first 4 months of 2014. This number is even higher for documents that have moved to EDIT; see the notes under "Monthly Submission and Publication Stats." The RPC continues to work hard to reduce the queue size and processing time in RFC Editor states.

March 2014: As mentioned previously, the RFC Production Center continues to work through the surge of documents released into EDIT earlier this year. While the RPC did not meet the SLA in March, the target is being met on an annual scale.

February 2014: The January issues listed below continue to be a factor. In addition, 67 documents were released into the EDIT queue this month. This means 118 documents have entered the EDIT queue in the first 2 months of the year. This is a significant number, as it means 43% of all documents published in 2013 have already entered the EDIT queue this year.

While the RPC did not meet the SLA in February, the target was not missed by much, as 67% of RFCs have an RET time of 6.1 weeks. The RPC continues to meet the SLA on an annual scale.

January 2014:The RFC Editor did not meet the SLA target. There are a few exceptional factors that contributed to processing delays:

While the RPC did not meet the SLA in January, the target was not missed by much, as 67% of RFCs have an RET time of 6.1 weeks. The RPC continues to meet the SLA on an annual scale.

May 2013: The RPC went through some cross-training exercises. This training caused our processing times to be slower than normal, but it was seen as a necessary tradeoff to ensure we have backup coverage during absences.

Monthly Submission and Publication Stats

The following figures show the recent submission and publication rates. The figures also include "moved to EDIT", which provides a more accurate picture of the RPC's incoming workload for a given month. "moved to EDIT" refers to documents that were released into the EDIT state.

Detailed submission and publication data can be found on the Comprehensive Sub/Pub Stats page.


June 2014 The last three months have been big publication months. As can be seen, the size of the overall queue and the number of documents in EDIT continues to decrease. The decrease in queue size indicates that the RPC is working through the queue.

May 2014 April and May have been big publication months. We have seen a steady decline in the number of documents moving to EDIT since February. The increase in publications is an indication that the RPC is starting to work its way through the burst of documents that entered the queue earlier this year.

April 2014 The graph shows that, while submissions are down, the number of documents entering EDIT has not slowed as is tyipcal post IESG changeover. 64% of the documents that moved into EDIT in 2013 have already been released to EDIT in the first 4 months of 2014.

March 2014: The submission rates and the number of documents released into edit in the first quarter of 2014 have been extremely high. See the notes under the SLA report for details.

November and December 2013: A flurry of high-page-count documents were released from MISSREF, and (as noted above) expedited processing was requested for one of the large clusters, impacting the production times of the other documents in the queue.

Queue Statistics

Summary of queue statistics about the processing times of documents as they move through the RFC Editor queue are available on the Queue Summary page. The summary includes document counts, page counts, and average times in queue per state (EDIT, RFC-EDITOR, AUTH48, and AUTH48-DONE). See state definitions for help understanding the states.

The number of documents in the primary processing states at the end of a given month is shown in the figures below.

Note that there is a ripple effect, as spikes in document counts in any one state may be due to clusters of documents moving through the queue together. A cluster does not move to the next state until the entire set is ready to be moved. You will often see bursts in EDIT, then RFC-EDITOR, and finally PUB, as the set of documents move through the states together to publication.

Generally speaking, the more documents there are in the queue, the longer it takes for documents to move through the queue.


June 2014:The number of documents submitted to the queue and entering EDIT since December 2013 have remained high. While May was a low submission month, submission numbers were again high in June. The RPC is starting to make headway in to the queue, as we see the third big publication month in a row.

May 2014: This figure shows that, since February, there has a steady decline in the number of documents in EDIT and the overall queue.

April 2014: The figure shows that the number of documents in EDIT has gone down consistently in March and April. The number of documents in RFC-EDITOR and AUTH48 has grown, which is largely due to the clusters currently in these states (i.e., most of C160 in RFC EDITOR, and the following clusters in AUTH48: a portion of C160, as well as C199, C203, C218, C222).

March 2014: A number of documents are being held in AUTH48-DONE because of the clusters. As cluster documents are approved for publication, they are moved to AUTH48-DONE and (typically) held until the entire cluster of documents has been approved. Once the cluster has been approved, we announce all of the documents in the cluster.

Other Reports

Report Description

Current Queue (sortable) A list of all of the documents in the RFC Editor queue, ordered by state. (Updated dynamically)
State Changes by Month Summary of document movement through the RFC Editor queue. (Updated weekly)
Annual Publication Rate Bar graph showing the number of RFCs published per year since 1969. (Updated annually).
RFC Editor Reports at IETF Summary of the RFC publication process, including the state of the queue and a breakdown of the reasons for any long delays in the publication process. The report also may include recent changes in policy and improvements in tools or procedures. (Updated quarterly)
RFC Errata Reports Summary of errata reports and their status, stream, and type. (Updated quarterly)
Vendor Reports Links to performance reports, e.g., 2013 performance review of the RPC. (Updated annually)
RFC Status Changes (post publication) List of the RFCs whose statuses have changed since publication. (Updated as needed)