IETF Meeting Clash List
Lists the organizations whose meeting dates we check before planning our meetings to ensure that we do not clash by booking meetings on the same dates.
Those organizations in Group A are identified as groups the IETF Meetings MUST not clash with, and with which there would be a one week break between the respective meetings, whenever possible. Group B organizations are those which the IETF prefers not to have clashing schedules. Appropriate parties from each organization are invited to contact the IETF meeting planner at meeting-planning@ietf.org to discuss coordination of schedules. If you would like to recommend an organization be added to the list, please send an email to meeting-planning@ietf.org with the name of the organization and an appropriate point of contact.
Version: 2024-05
(A) Bodies we MUST NOT clash with
- APNIC
- APRICOT
- ARIN
- 3GPP *
- ICANN *
- IEEE 802 *
- ITU-T (selected meetings)*
- LACNIC
- NANOG
- OMA *
- RIPE
- W3C *
* official IETF liaisons; contact liaison manager for calendar details
(B) Bodies and events we prefer not to clash with:
- ACM SIGCOMM conferences
- AfriNIC
- AfNOG
- Broadband Forum
- Connectathon
- CRYPTO conferences
- eBPF Foundation (added 2023-06)
- ETSI (selected meetings) (added 2024-05)
- IEEE INFOCOM conferences
- IEEE Security and Privacy symposium
- IEEE/IFIP NOMS conferences
- IEEE MANWEEK
- IFIP/IEEE IM conferences
- IFIP Networking conference
- IGF
- ISO (selected meetings) (added 2024-05)
- ISOC NDSS
- NENA
- OGF Meetings *
- SANOG
- TIA
- Unicode *
- USENIX Annual Technical Conferences
- USENIX LISA conferences
- USENIX Security symposia
- VON conference (VoIP)
* official IETF liaisons; contact liaison manager for calendar details