Skip to main content
  • Towards a net zero IETF

    Introducing a new project to measure and potentially offset IETF carbon emissions so that the IETF could potentially reach the level of a net zero emitter.

    • Jay DaleyIETF Executive Director
    6 May 2022
  • IETF 113 post-meeting survey

    The results from our IETF 113 post-meeting survey are now available on a web-based interactive dashboard. This commentary highlights where changes we have made based on feedback have been a success, and areas we still need to work on.

    • Jay DaleyIETF Executive Director
    2 May 2022
  • IETF 113 Hackathon – Back in person!

    The IETF 113 Hackathon held 19-20 March 2022 in Vienna and online marked the return to in-person collaboration on running code related to Internet standards.

    • Charles EckelIETF Hackathon Co-chair
    19 Apr 2022
  • IETF Datatracker updates and service outages planned

    Two updates in the coming weeks will significantly revise the look of the IETF Datatracker and, after a short outage on 25 April 2022, upgrade the hardware for most IETF services.

    • Robert SparksIETF Tools Project Manager
    13 Apr 2022
  • New Independent Submissions Editor looks for interoperability, continuous improvement

    Eliot Lear, a long-time Internet Engineering Task Force participant and engineer for Cisco Systems, was recently appointed independent submissions editor by the Internet Architecture Board (IAB).

    • Grant GrossIETF Blog Reporter
    31 Mar 2022

Filter by topic and date

Filter by topic and date

Proposed Process to Conduct Assessment Activity of IETF Administrative Support Activity

  • Jason LivingoodIETF Administration LLC Board Chair

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