Skip to main content
  • Stepping towards a Sustainable Internet

    The IAB’s new Environmental Impacts of Internet Technology (E-Impact) program will hold its first virtual interim meeting over two slots on 15 and 16 February 2024. These interim meetings are open to participation, and we invite all interested community members to join, participate, and contribute.

    • Jari ArkkoE-Impact Program Lead
    • Suresh KrishnanE-Impact Program Lead
    7 Feb 2024
  • What’s the deal with Media Over QUIC?

    In 2022, the IETF formed a working group for Media Over QUIC (MoQ)—a media delivery solution that has the potential to transform how we send and receive media during live streaming, real-time collaboration, gaming, and more.

    • Brett BralleyThought Leadership Content Writer, Cisco
    25 Jan 2024
  • IETF Administration LLC 2024 Budget

    The IETF Administration LLC has finalised its budget for 2024.

    • Jay DaleyIETF Executive Director
    18 Jan 2024
  • Update on the IT Infrastructure Transition Project

    Begun in the last quarter of 2023, work is underway to define and deploy a new, cloud-based infrastructure approach for services that support the work of the IETF, and to move those services onto the new infrastructure.

    • Robert SparksIETF Tools Project Manager
    12 Jan 2024
  • Internet Society Extends Financial Support to the IETF

    An extended agreement with the Internet Society will continue providing major financial support to the IETF through March 2029.

    • Jason LivingoodIETF Administration LLC Board Chair
    10 Jan 2024

Filter by topic and date

Filter by topic and date

Reducing IETF Meeting Scheduling Conflicts

  • Alexa MorrisIETF Managing Director

1 Apr 2023

With many IETF participants active across a number of active working groups and limited time slots in an IETF meeting week, we aim to arrange sessions in the agenda to minimize conflicts that prevent participants from joining sessions that are of interest to them. In each post-meeting survey we ask meeting participants to comment on the scheduling conflicts they experienced in the meeting agenda and we then use this information to improve the meeting agenda.

When WG chairs request a session for an IETF Meeting, they note what other groups to avoid a scheduling conflict with. Over time, an extensive set of scheduling conflicts to avoid has been collected for use in the meeting agenda planning tool. While this avoids many conflicts, meeting participants often note conflicts in the post-meeting survey that were not included in the original meeting session request submitted by the working group chair.

Following IETF 115 London, we tallied conflicts reported by two or more participants in the post-meeting survey and shared that information directly with each working group chairs for them to review. For the first time, we are sharing the results of that process, including what action, if any, was taken.

It’s important to note that some sessions are harder to deconflict than others. For example, BOFs may appeal to a broad set of participants. Similarly, conflicts related to more general sessions such as dispatch, irtfopen, and iabopen are harder to avoid.

A copy of each session request is sent to the requesting working group, and the requests are also viewable in Datatracker to anyone in the community.  These session requests include the scheduling conflicts to avoid. If you believe that important conflict information is missing from the session request, please raise your concern with the working group chairs, ideally before the meeting. It's more helpful for a chair to understand who is raising which conflicts and why than to see the anonymized survey data after the meeting as that comes without context.

We ask that working group chairs closely review their conflict lists for each session request they make, before each and every IETF meeting. If you have requested your session prior to the BOF submission deadline, we ask that you review the list of approved BOFs and, if you see one that may conflict with your working group, please send a note to prior to the publication of the preliminary agenda, so that we can update your conflict list.  

If you have any suggestions for how we might improve the scheduling process, please feel free to send them to the Secretariat at or direct to the IESG at

Share this page