• Banishing the bane of bufferbloat

    Bufferbloat affects everyone who uses the Internet, resulting in frustratingly slow web browsing, laggy video calls, and overall poor quality of experience for Internet users and there's a lot of work underway in the IETF to address it.

    • Bjørn Ivar TeigenIETF Participant
    23 May 2023

  • IETF 116 post-meeting survey

    IETF 116 Yokohama was held 25-31 March 2023 and the results of the post-meeting survey are now available on a web-based interactive dashboard.

    • Jay DaleyIETF Executive Director
    26 Apr 2023

  • Catching up on IETF 116

    Recordings are now available for sessions held during the IETF 115 meeting and the IETF Hackathon, where more than 1500 participants gathered in London and online 5-11 November 2022.

      1 Apr 2023

    • Reducing IETF Meeting Scheduling Conflicts

      With many IETF participants active across a number of active working groups and limited time slots in an IETF meeting week, we aim to arrange sessions in the agenda to minimize conflicts that prevent participants from joining sessions that are of interest to them. In each post-meeting survey we ask meeting participants to comment on the scheduling conflicts they experienced in the meeting agenda and we then use this information to improve the meeting agenda.

      • Alexa MorrisIETF Managing Director
      31 Mar 2023

    • Messaging Layer Security: Secure and Usable End-to-End Encryption

      The IETF has approved publication of Messaging Layer Security (MLS), a new standard for end-to-end security that will make it easy for apps to provide the highest level of security to their users. End-to-end encryption is an increasingly important security feature in Internet applications. It keeps users’ information safe even if the cloud service they’re using has been breached.

      • Nick SullivanMLS Working Group Chair
      • Sean TurnerMLS Working Group Chair
      29 Mar 2023
    • Show all

    Filter by topic and date

    Filter by topic and date

    IANA Changes

    • Jari ArkkoIETF Chair

    1 Apr 2014

    Two weeks ago there was an announcement from the US government regarding their role in managing IANA.

    As we knew this might be coming, Russ and I (along with IESG and IAB) had worked with various Internet technical organisations to prepare a statement as well, essentially saying that we intend to build on the existing organizations and their roles. We noted that the Internet technical community is strong enough take on the stewardship function as it transitions from the US Government, while maintaining our current roles.

    I wanted to provide some further updates, with several of us having visited ICANN’s 49th meeting, which was held last week in Singapore. The US government announcement designated ICANN as the facilitator of the process to propose the changes that might be necessary. Not the decider, but the one that starts the process and makes sure that the rest of the Internet community and organisations are engaged in this discussion. This process was started last week, and indeed, it was the biggest discussion topic of the week. We at the IETF need to participate in discussions around IANA and its possible evolution as well, particularly when it comes to the part that we are in charge of, i.e., the protocol parameters.

    With this in mind, I wanted to point out a few things that are going on:

    • The IAB has lead a discussion about general principles on how we view IANA. The latest update of the principles was posted at the internetgovtech list. There are also some initial thoughts and discussions on what the changes in the role of US government might mean in practice, also at the same list. These discussions will continue – please contribute!
    • At ICANN 49, a lot has been said about this topic. For instance, the transcript from the opening session on this topic is here. And I found this blog article useful to understand the various things that US government officials have said about the topic. Among other things, they emphasise the role of the “customers” of IANA (such as IETF in the case of protocol parameters.) Also, both Russ and I spoke about our views from an IETF perspective. What I said is here.
    • There is an ongoing discussion about how the IANA changes process itself is designed. The input gathered during ICANN’s meeting will be summarised by 7th of April, but the discussion will continue. Once a process is in place, we can talk more about the actual substance.

    In the IETF system, the IAB is the entity responsible for the IANA relationship. The IAB is supported by the IANA program.

    Share this page