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

Proposed Process to Conduct Assessment Activity of IETF Administrative Support Activity

12 Apr 2021

After three years of operation, the IETF Administration LLC (IETF LLC) is preparing to conduct a complete assessment of the structure, processes, and operation of the IETF Administrative Support Activity (IASA 2.0) and the IETF LLC. Before beginning this work, we are soliciting community feedback on the proposed timeline and process we will use to conduct the retrospective.

The assessment is required by BCP 101, which specifies the IETF Administrative Support Activity, including the IETF LLC. If you have any feedback, please provide it within the next two weeks, by the end of the day on 26 April 2021 via the public discussion mailing list, admin-discuss@ietf.org

Proposed timeline:

  1. April: Community input on the retrospective process
  2. May: Planning for the retrospective
  3. June - September: Conduct the retrospective, including community input at every step
  4. October: Write the report for the community on the results of the retrospective
  5. November: Present the report during the IETF 112 meeting plenary

Proposed approach:

  1. Create a list of goals and requirements from RFC 8711 and the Design Team Recommendations, and all other relevant IASA2 working group documents, then assess performance or progress towards meeting each item. This may help to highlight any areas where additional work may be needed.
  2. Create a list of administrative, financial, legal, or operational gaps; areas of improvement; and any areas of under-specification or over-specification in IASA2 documents that the IETF LLC Board, IETF Secretariat, IETF Executive Director, or the IETF community perceive. 
  3. The assessment may include recommendations for future changes or work. This could conceivably lead to the reactivation of the IASA2 working group or other work to be determined at the conclusion of the retrospective. 
  4. Documents will be maintained in a publicly accessible repository for continuous feedback from the community as the work progresses. 
  5. In addition, periodic status reports will be provided as this work progresses.

Feedback is requested generally, as well as on these specific questions:

  1. Does this proposed timeline properly balance providing sufficient time for community input against the need to complete the report on a timely basis?
  2. Does the proposed approach sound reasonable?
  3. Is anything missing in the proposed timeline and approach?
  4. What stakeholders outside of the IETF should be consulted?
  5. Should the IETF LLC retain a consultant with expertise in non-profit governance to conduct an independent assessment, as a supplement to this plan?

Share this page