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

IETF email service issues resolved as of 4 March 2025

4 Mar 2025

The IETF email processing system delays reported on 3 March 2025 have been resolved. All messages in the queue were delivered by 0700 UTC on 4 March and the system is now keeping up.

The mail processing system encountered reduced disk I/O capacity due to an incident in the underlying filesystem that took some time to recover.

During this period of reduced I/O capacity, email submission to lists was very high—driven by the Internet-Draft submission deadline at 2359 UTC Monday, 3 March. This led to very long queue time for messages going to mailing lists. We are looking into ways to improve the baseline I/O capacity of the system to provide better resiliency for the future.

We believe this issue is currently resolved so will not be updating this post further.

As previously shared:

Following the email processing infrastructure transition last month, the new system was experiencing delay—sometimes over 4 hours—in delivering messages with the increased load resulting from the Internet-Draft submission deadline for the upcoming IETF 122 Bangkok meeting. We are working on short-term and long-term fixes.

Email messages were being delivered almost immediately to the IETF mailarchive.ietf.org system, which can be searched for specific messages. While it does not reflect delivery delays, general system status can be found on the IETF Status page.

One factor contributing to these delays was the number of messages being sent automatically due to the Internet-Draft submission deadline. This deadline for documents to be considered at an IETF meeting generally results in a burst of Internet-Draft (I-D) submissions. An announcement of each submission is distributed to a variety of lists, including several with large subscriber lists, such as I-D Announce. A single submission may result in many thousands, and sometimes many-10s-of-thousands of email messages being generated. This burst of I-D submissions has put additional strain on the new email processing system.

We looked into and believe we now have an understanding of the root causes of the congestion and how to help the delivery queues drain more quickly.  We are also considering longer-term changes to avoid the backup in the future.


Share this page