• IETF 117 Highlights

    IETF 117 is a few weeks behind us and Dhruv Dhody, IAB Member and liaison to the IESG, took the opportunity to report on a few highlights and some impressions.

    • Dhruv DhodyIAB Member and liaison to the IESG
    21 Aug 2023

  • Proposed response to meeting venue consultations and the complex issues raised

    The IETF Administration LLC recently sought feedback from the community on the possibility of holding an IETF Meeting in the cities of Beijing, Istanbul, Kuala Lumpur and Shenzhen, with received feedback including views that were well expressed and well argued but strongly conflicting. The IETF LLC has considered this feedback in-depth and now seeks community feedback on its proposed response.

    • Jay DaleyIETF Executive Director
    21 Aug 2023

  • Submit Birds of a Feather session proposals for IETF 118

    Now's the time to submit Birds of a Feather session (BOFs) ideas for the IETF 118 meeting 4-10 November 2023, with proposals due by 8 September.

      16 Aug 2023

    • Applied Networking Research Workshop 2023 Review

      More than 250 participants gathered online and in person for ANRW 2023, the academic workshop that provides a forum for researchers, vendors, network operators, and the Internet standards community to present and discuss emerging results in applied networking research.

      • Maria ApostolakiANRW Program co-chair
      • Francis YanANRW Program co-chair
      16 Aug 2023

    • IETF 117 post-meeting survey

      IETF 117 San Francisco was held 22-28 July 2023 and the results of the post-meeting survey are now available on a web-based interactive dashboard.

      • Jay DaleyIETF Executive Director
      11 Aug 2023
    • Show all

    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