Skip to main content
  • IETF email infrastructure transition planned for 11 September

    A transition to a new modern, modular, and containerized infrastructure for email services provided for ietf.org, iab.org, irtf.org, rfc-editor.org (including email lists) is scheduled for 11 September 2026 starting at 2200UTC, with message delivery delayed up to 60 minutes. Further updates will be provided closer to the transition.

    28 Aug 2026
  • Post-Quantum Authentication: Up Next

    Post-quantum key establishment has moved from standards into deployment. Post-quantum authentication has not moved nearly as far, and specification work is no longer the only constraint. The IAB is holding a workshop in Prague on 11 and 12 October 2026 to bring deployment experience together with the people working on the relevant protocols and standards.

    27 Aug 2026
  • IETF 126 post-meeting survey: what we heard

    The IETF 126 Vienna meeting was held 18-24 July 2026 and the results of the post-meeting survey are now available.

    27 Aug 2026
  • Meet our new IETF NOC Lead

    Joe Clarke has been appointed as the new IETF NOC Lead and in this post Joe introduces himself and sets out his priorities for the IETF Network.

    10 Aug 2026
  • Secretariat restructuring and staffing update

    There have been a few changes in IETF Administration LLC staffing since January of this year (2026) including the recent insourcing of the Secretariat, which are summarised here to give an overall view of the staffing structure.

    30 Jul 2026

Filter by topic and date

Filter by topic and date

BPF: taking work to the IETF

5 Jul 2023

The new BPF Working Group is beginning work to document the state of the ecosystem and extensions for this technology that has origins in the Linux kernel and is increasingly being used beyond Linux.

eBPF, which is no longer an acronym for anything and is commonly referred to as BPF, is a technology that can run programs in a privileged context, such as an operating system kernel. It is used to safely and efficiently extend the capabilities of the kernel without requiring to change kernel source code or load kernel modules. BPF is widely deployed on operating systems, such as Linux and Microsoft Windows, and is also implemented in some network interface cards. 

BPF background

As the number of implementations and deployments of BPF has grown, there have been discussions about what kind of standardization is appropriate and required to support further adoption by an even broader range of manufacturers and platforms. Several options were considered by the eBPF Foundation, which was founded under the Linux Foundation in December 2021. In the end, the eBPF Steering Committee decided to pursue standardization in the IETF because of its openness, the relative ease of its processes and global scope, and its institutional experience with both networking and non-networking topics.

Discussions began between members of the BPF and IETF communities, including on an IETF mailing list, following an informal side meeting at IETF 115 in 2022 to discuss BPF standardization and explore whether IETF was an appropriate venue for that standardization. This was followed by a formal Birds of Feather session at the IETF 116 meeting in March 2023. These discussions, and subsequent due diligence, led to a formal chartering of the BPF Working Group in May 2023. A bit different from most IETF Working Groups, group discussions will take place simultaneously on the  bpf@ietf.org and bpf@vger.kernel.org mailing lists, with the list archives for both available for anyone to review. To propose changes to any working group document, you can create a patch to the bpf-next.git kernel tree, and email that patch to both lists for discussion and review. See Submitting patches: the essential guide to getting your code into the kernel for an overview of how to send patches to the Linux kernel mailing list, and How to Interact with the BPF Subsystem for BPF-specific patch submission processes.

Interested in learning more or getting involved? Sign up for one (or both) of the mailing lists, consider contributing to the instruction-set.rst document, or get more acquainted with how the IETF works generally and how to start participating.


Share this page