Skip to main content
  • IETF 126 Highlights

    The IETF 126 meeting was held 18–24 July 2026 at the Hilton Vienna Park in Vienna, Austria, and online, hosted by Cisco. The week included the IETF Hackathon and Code Sprint, the New Participants' Program, five Birds-of-a-Feather (BoF) sessions, and more than 100 working group and research group sessions. The Applied Network Research Workshop also took place during the IETF 126 meeting week.

    1 Sep 2026
  • 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

Filter by topic and date

Filter by topic and date

IASA2 Working Group Chartered

25 Apr 2018

The IETF has chartered a new working group to document changes to its administrative arrangements.

For legal purposes, the current IETF Administrative Support Activity (IASA) is organized as an activity of the Internet Society (ISOC). In November 2016, Jari Arkko launched a project as IETF Chair to re-assess the IETF's administrative arrangements. Since then, the IETF community has discussed the challenges we face, the properties we expect from future arrangements, and options for the legal and organizational structure of future arrangements. This process identified that the IETF's administrative tasks have grown; the current organizational structure is not as clear, efficient, or as fully resourced as it should be; aspects of the division of responsibilities between the IETF and ISOC continue to evolve; expectations about transparency have changed; and the IETF faces continued challenges related to funding activities against a backdrop of increasing costs and lack of predictability in our funding streams.

After considering a number of different legal structure options, the community identified the creation of a new limited liability corporation (LLC) that is a disregarded entity of ISOC (i.e., it is treated as a branch or division of ISOC for tax purposes) as the preferred option to house the administration of the IETF. Last week we announced the formation of the IETF Administrative Support Activity 2, which is chartered to document the normative changes to IETF administrative structures and processes necessary to effectuate this change.

I wanted to highlight a few additional important points that have come up in the discussions leading up to this point.

First, aside from instances where they presently relate to IASA, it is outside the scope of this working group to consider any changes to anything related to the oversight or steering of the standards process as currently conducted by the Internet Engineering Steering Group and the Internet Architecture Board (IAB), the appeal chain, the confirming bodies for existing IETF and IAB appointments, the Internet Research Task Force (IRTF), or ISOC's memberships in other organizations.

Second, this work has the support of the Internet Society. The ISOC Board of Trustees has stated their commitment to working with the IETF along the way, and in working with the IETF to implement the outcome of the IASA2 working group process, as needed. Both the IETF community and ISOC expect to reap the benefits of clarifying and solidifying the IETF's administrative structure.

Third, many details remain to be worked out, including decisions about transitioning existing contracts and support functions, about the financial relationship between ISOC and the new LLC (including as regards the IETF Endowment), and about the relationship between the IETF community and those working on behalf of the LLC. I am confident that we will be able to identify arrangements in all of these areas that will strengthen the IETF's ability to achieve its mission of making the Internet work better.

Those interested in joining the discussion are welcome to join the iasa20@ietf.org mailing list.

Bibliography


Share this page