Skip to main content
  • Birds of a Feather at IETF 126

    The IETF 126 Vienna meeting takes place 18–24 July 2026. As at every IETF meeting, alongside the established Working Groups there will be a handful of Birds-of-a-Feather (BoF) sessions—and these are often the most interesting place to watch where Internet standards work is heading next.

    2 Jul 2026
  • From Lab to RFC: A PhD Student's Journey through the IETF

    Martine Sophie Lenders has been regularly participating in the IETF for over a decade, starting with the IETF 93 meeting in Prague in 2015. She has authored several Internet-Drafts—two of which recently were published as RFCs—and at the same time works on a PhD at FU Berlin and as a research associate at TU Dresden. We asked a few questions about what her experience in the IETF has been like while pursuing an academic journey.

    1 Jul 2026
  • Suggested IETF 126 Sessions for Getting Familiar with New Topics

    These IETF 126 meeting sessions are likely to include discussions and proposals that are accessible to a broad range of Internet technologists whether they are new to the IETF or long-time participants.

    29 Jun 2026
  • IETF LLC Board Retreat 2026

    The IETF Administration LLC Board of Directors held its annual retreat 29-30 April 2026 in Amsterdam. In addition to all Board members, the IETF Executive Director, the Director of Finance, and the Board Secretary were present. Here is a short summary of the main points we discussed.

    4 Jun 2026
  • IETF Administration LLC 2025 Annual Financial Audit

    IETF Administration LLC Board of Directors received from external auditors the report of a clean result for its 2025 annual financial statement.

    26 May 2026

Filter by topic and date

Filter by topic and date

Strange but familiar in Dublin

21 Oct 2015

We’re both at ICANN 54 in Dublin, and of course a big topic is the IANA transition.

At this meeting most of the focus is on ICANN accountability changes. Those are important for us because the IANA stewardship transition plan for the names community depends on those accountability changes. People want to make sure that ICANN (the organization) complies with the community’s will. Since we think that’s what it means to be a bottom-up organization, it seems like a natural reform to us and one the ICANN community deserves.

There are disagreements about the specific ways to do this, and people also recognize the risk of accidentally creating new issues when making a change. The amount of progress we’ve seen during the meeting is impressive, however. The feelings here are at once familiar and strange — the exact ways people hammer out consensus in ICANN are not the way we do things in the IETF, but seeing hard positions start to converge is for sure something we understand. One thing we’re noticing is people embracing practical power that rests with the community rather than mere legal enforcement by courts. We think that’s positive for three reasons. First, it hands the power directly to the people who need it instead of giving them indirect means to achieve it. Second, it seems to represent lower risk to IANA: lengthy legal proceedings would be bad operationally. Finally, this mode of operation has always worked for the IETF.

We care about the overall stability of Internet systems and organizations, but a current big interest in this is due to the IANA transition. If the different operational communities can’t together make this transition happen, we’ll have to face bad options. We will lose some of the confidence people have in the Internet community. The transition was part of the promise at the foundation of ICANN, and the promise has come due.

We really appreciate the hard work people are doing on these accountability changes. We are very happy with the progress that has already been made this week. The key to completing this process is to focus on the practical ways to put the appropriate and sufficient power in the community hands.

(This post represents our personal opinions.)


Share this page