Skip to main content
  • IETF 126 Highlights

    The IETF 126 meeting was held 18–24 July 2026 at the Hilton Vienna Park in Vienna, Austria, and online, hosted by Cisco. The week included the IETF Hackathon and Code Sprint, the New Participants' Program, five Birds-of-a-Feather (BoF) sessions, and more than 100 working group and research group sessions. The Applied Network Research Workshop also took place during the IETF 126 meeting week.

    1 Sep 2026
  • IETF email infrastructure transition planned for 11 September

    A transition to a new modern, modular, and containerized infrastructure for email services provided for ietf.org, iab.org, irtf.org, rfc-editor.org (including email lists) is scheduled for 11 September 2026 starting at 2200UTC, with message delivery delayed up to 60 minutes. Further updates will be provided closer to the transition.

    28 Aug 2026
  • Post-Quantum Authentication: Up Next

    Post-quantum key establishment has moved from standards into deployment. Post-quantum authentication has not moved nearly as far, and specification work is no longer the only constraint. The IAB is holding a workshop in Prague on 11 and 12 October 2026 to bring deployment experience together with the people working on the relevant protocols and standards.

    27 Aug 2026
  • IETF 126 post-meeting survey: what we heard

    The IETF 126 Vienna meeting was held 18-24 July 2026 and the results of the post-meeting survey are now available.

    27 Aug 2026
  • Meet our new IETF NOC Lead

    Joe Clarke has been appointed as the new IETF NOC Lead and in this post Joe introduces himself and sets out his priorities for the IETF Network.

    10 Aug 2026

Filter by topic and date

Filter by topic and date

Report from the 2026 RPC Retreat

18 May 2026

The RFC Production Center (RPC) retreat was a two-day strategic planning session taking place the week of April 20 that gathered the entire RPC team and IETF Administration senior staff.

The team reviewed the transformational projects identified during the 2025 RPC retreat and agreed that they are still relevant.  The team acknowledged progress made and identified where further changes could be made.  In the past year, the RPC successfully:

  • updated the editorial process for efficiency gains, e.g., added an intake form where authors can answer some questions before editing of their document begins;
  • implemented monthly public reporting on RPC activities to improve transparency; and
  • rolled out pilot programs for editing in markdown and processing during AUTH48 in markdown and GitHub in response to community requests and tool usage.

For more details about the current status of transformational projects, refer to the monthly RPC reports (May 2026).

Much of the team’s focus was on the upcoming tools transition and related process changes.  The upcoming tools will modernize the RPC processes and improve transparency regarding the status of documents awaiting publication.  This change will completely overhaul the current editorial and publication practices.  The team discussed the transition plan and ways to smooth the process, while also acknowledging the tension between mastering the new tools and processes and continuing to publish RFCs.

With these transformations and the upcoming changes to tools, the team expressed excitement about re-imagining the editorial process once the new tools are in place, with particular attention on AUTH48 initially, to ensure an efficient and simple editing process for authors and editors alike.  The team is also exploring whether there are efficiency gains to be had by introducing AI into editorial process (e.g., can it help with formatting references and converting tables into RFCXML). With the increased visibility into the details of the editing flow, the team will be working to define a new service level agreement that considers community expectations and acknowledges the bursty nature of a project that has finite resources.

To keep up to date on RPC-related news, such as receiving the monthly RPC reports, subscribe to the rfc-interest mailing list.


Share this page