Skip to main content
  • RFC Production Center management transition

    After an extensive review of recent developments in the RFC Editor function, the IETF Administration LLC (IETF LLC) and Association Management Solutions LLC (AMS) have agreed that the IETF LLC will assume management of existing RFC Production Center (RPC) staff, under an Employer of Record arrangement with AMS, the employer of the RPC team.

    5 Jan 2025
  • Workshop on the Decentralization of the Internet at ACM CoNEXT 2024

    The recent Decentralization of the Internet (DIN) workshop at ACM CoNEXT-2024 brought together network researchers, law and policy experts, and digital right activists to discuss the consolidation and centralization of the existing Internet applications, services, and infrastructure observed in recent years.

    19 Dec 2024
  • Launch of the IETF Community Survey 2024

    The IETF Community survey is our major annual survey of the whole of the IETF community and is used to inform the actions of IETF leadership throughout the year. The 2024 IETF Community Survey is live and we want to hear from you!

    19 Dec 2024
  • Second IASA2 Retrospective Report

    The IETF Administration LLC (IETF LLC) has now completed the second IETF Administrative Support Activity (IASA 2.0) retrospective. The report was developed with community input and review, and is now available online.

    18 Dec 2024
  • IETF Administration LLC 2025 Draft Budget

    The IETF Administration LLC has prepared its draft budget for 2025 and now seeks community feedback.

    13 Dec 2024

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