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

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