Skip to main content
  • 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
  • Secretariat restructuring and staffing update

    There have been a few changes in IETF Administration LLC staffing since January of this year (2026) including the recent insourcing of the Secretariat, which are summarised here to give an overall view of the staffing structure.

    30 Jul 2026

Filter by topic and date

Filter by topic and date

IETF IANA Transition Proposal Last Call

28 Nov 2014

In March the US government announced their intent to move their role in overseeing the IANA system to the Internet community. Since the announcement, the communities impacted by IANA functions have been working hard to develop a transition proposal.

he IANA transition Coordination Group (ICG) was set up to coordinate the process. However, most of the responsibility for the work resides in the communities served by IANA, such as ICANN global names and country-code name communities, the regional address registries (RIRs), and the IETF. The ICG requested these communities to make proposals for the parts that they are affected by.

The IETF’s response to this request, our draft proposal is now in IETF-wide review. The IANAPLAN working group was created for the purpose of developing a proposal, and the work started in August. The draft proposal is relatively straightforward, owing to the stated IETF community opinion that the existing arrangements between IETF and ICANN should be continued. But the details needed to be written down, and consensus found to support the proposal.

It was clear that everybody wanted a stable, secure, and well-working IANA oversight system for the IETF. We had some disagreements about the methods to achieve this, however, but talking through these issues helped everyone better understand the different viewpoints. In the end, I thought the working group had found quite reasonable agreement. And the chairs and the document shepherd have concluded that the WG has sufficient consensus to move forward to the broader review.

The proposal is now subject to review from the IETF community, in the Last Call process. The purpose of last calls is to identify any latent issues (while, of course, respecting the discussions and conclusions already stated in the working group process). The last call runs until December 15th, and after that the IESG will determine if it is ready to be approved. Some changes may also be made to documents in this stage, depending on IESG and community comments.


Share this page