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

IANA Protocol Parameters Explained

20 Apr 2015

You may have heard about the IANA transition, or to be more precise, about the transition of US government oversight relating to IANA. In March 2014, the US government announced their intent to relinquish their role to the multistakeholder Internet community.

The communities served by IANA – such as the IETF – have been busy ensuring their systems are ready for this. In the case of the IETF, our community worked through a plan, and this plan was approved in January 2015. This plan calls for continuing the existing arrangements with regards to IANA as far as protocol parameters are concerned. Internet engineers have worked with the evolving IANA arrangements for more than 35 years, and more than 15 in the current setup. The system is mature today. It has handled and can handle IANA oversight adequately.

But we do get many questions around the IANA functions, particularly when meeting people who have not been involved in the IETF work. To begin with, what are protocol parameters? What is the role of IAB? What is oversight? Who draws contracts at the IETF? What role does the IAOC play? How can you ensure that the IETF leadership works according to the community’s wishes?

I wanted to share a few documents designed to answer these questions:

  • An introductory presentation describes how IETF deals with IANA functions and protocol parameters. You can find the presentation here.
  • An short document that describes the role of protocol parameters in the Internet, and what is the role various organisations. You can find the document here.
  • An earlier blog article discussed the importance of continuity in handling IANA functions. You can find the article here.
  • The official IETF plan for the transition is of course our primary document, and the document is here.

Hopefully you find these documents helpful. Do not hesitate to ask me or others at the IETF leadership if you have any questions on this matter.


Share this page