The Internet Engineering Task Force (IETF) is holding a hackathon to encourage developers and subject matter experts to discuss, collaborate, and develop utilities, ideas, sample code, and solutions that show practical implementations of IETF standards.
When: 14 - 15 March 2026 (Saturday - Sunday)
Where: Futian Shangri-La
Room: TBD
Sign up for the Hackathon
View the list of registered:
Keep up to date by subscribing to the IETF Hackathon email list.
The IETF Hackathon is free to attend and is open to everyone. It is a collaborative event, not a competition. Any competition is friendly and in the spirit of advancing the pace and relevance of new and evolving internet standards.
¶ Agenda
Subject to Change
Hackathon (all times are GMT-4)
¶ Saturday, 14 March
- 09:30 : Room open for setup by project champions
- 10:00 : Room open for all - pastries and coffee provided
- 10:30 : Hackathon kickoff
- 10:45 : Form teams, see Team Schedule
- 12:30 : Lunch provided
- 15:30 : Afternoon break - snacks provided
- 18:30 : Dinner provided
- 20:30 : Room closes
¶ Sunday, 15 March
- 09:30 : Room opens - pastries and coffee provided
- 12:30 : Lunch provided
- 13:30 : Hacking stops, prepare brief presentation of project
- 14:00 : Project results presentations
- 16:00 : Hackathon ends
- 17:00 : Tear down complete
Related activities before and after the Hackathon weekend
¶ Hackdemo Happy Hour
- Share your Hackathon project with the IETF community
- Monday, 16 March, Time: 19:00 - 20:00, Room: TBD
- View the schedule or reserve space for your team/project
- Reservations for space must be made by 13:00, Monday 16 March
¶ Shared Workspace
- Space for groups to gather and collaborate on running code
- Monday - Friday, 16 - 20 March, Room: TBD
¶ Meetecho
NOTE: You will need an IETF Datatracker account to login to the Hackathon Meetecho sessions.
When you register for the IETF Hackathon, you are sent a separate email to create an IETF Datatracker account if you don't already have one.
If you already have an IETF Datatracker account, please ensure that the email address with which you registered is associated with your Datatracker account.
If you received the email but the link to create an account has expired, please see the instructions below:
- Go to https://datatracker.ietf.org/accounts/create/
- Select "New Account" from the User menu at the top
- Enter the email address that you registered with for the Hackathon
- Follow the instructions in the email you receive
¶ Presentation and Meeting Materials
- You can share the code you're working on through the IETF Hackathon GitHub, or via the links provided in the project descriptions below.
- Request to be added to IETF GitHub organization by sending your GitHub ID to (hackathon-chairs@ietf.org).
- Hackathon project result presentations should be uploaded to Datatracker under the specific session Hackathon Results Presentations at 14:00-16:00.
- To upload your presentation, you must have a Datatracker account and be logged in.
- The Hackathon Results presentations from Sunday, 14:00-16:00, are available on Datatracker:
¶ Participant Preparation and Prerequisites
¶ Project Teams and Champions
- Champions are the leads for individual projects in the Hackathon
- Champions are individuals familiar with a given technology who volunteer to help get others get up and running with that technology
- Before the Hackathon, champions should:
- Add information about your project to the list of Projects included in Hackathon
- Recruit participants from associated working groups, open source projects, etc. Announcing your projects via an email to (hackathon@ietf.org) can be helpful as well.
- Specify when and how the project team will meet on the Team Schedule
- At the Hackathon, champions should:
- Make themselves available to answer questions and help others
- Hack on things themselves in their copious free time
- Additional projects are welcome at any time. For any questions, contact the chairs at (hackathon-chairs@ietf.org)
¶ Choosing a Project
- Champions post and lead projects
- Details on each project and links to additional information for each project are in the list of Projects included in Hackathon
- How and when teams meet during the week is up to them and can be found in the Team Schedule.
- Familiarity with technology area(s) in which you plan to participate will certainly help
- It is perfectly fine, even encouraged, to work on multiple projects
¶ Lost & Found
- Participants looking for a team and champions wanting help on their projects are encouraged to visit the Lost & Found.
¶ Development Environment
- Bring a laptop on which you are comfortable developing software
- Some projects may require installing additional software or make use of VMs or containers
- Installing and becoming familiar with !VirtualBox, Vagrant, Docker or something similar may be helpful
- Specific coding languages are called out by some projects (e.g. Python, Go, Java, C++), but this is heavily dependent on the project(s) you choose
¶ Sharing Code
- Git/GitHub is commonly used for open source projects. Familiarizing yourself with it is recommended.
- An online tutorial is available here: Git Tutorial
- The IETF Hackathon GitHub organisation is used by some of the Hackathon projects to host their repositories.
- If you would like to have your project/code hosted here, send your GitHub ID and the name of your project via email to (hackathon-chairs@ietf.org)
¶ Project Presentations
- All teams have the opportunity to present what they did at the end of the Hackathon.
- Hackathon project result presentations should be uploaded to Datatracker under the specific session Hackathon Results Presentations at 14:00-16:00.
- To upload your presentation, you must have a Datatracker account and be logged in.
- DO NOT WAIT until just before the start of the Hackathon project presentations to upload your presentation, as it may be lost in the chaos.
¶ Network
Access to the IETF network
The NOC team has an ongoing experiment that allows you to join the IETF network remotely as well as at an IETF meeting venue.
Requests for networking capabilities beyond wireless access to the IETF network (e.g., wired ports, L2 access, prefix delegation) can be sent to support@ietf.org.
All requests are addressed on a best effort basis. Advance notice is appreciated and improves the odds of your request being fulfilled.
¶ Webex sessions for teams
Champions can request a Webex account they can use to schedule meetings for their team. These are similar to the Webex accounts allocated to working group chairs to be used for virtual interim meetings. An account can be requested by a team champion at any time. Accounts will remain active and available for the duration of the IETF meeting. Request your account HERE. In the request form, you can use your project name where it asks for "Working Group Name" ("Hackathon Project Name").
¶ Ongoing Communication
In addition to registering for the Hackathon and subscribing to the Hackathon list. It is recommended to monitor both the Hackathon wiki and the list as the Hackathon approaches, determine which project(s) are of interest to you, and reach out to the champions of those projects to determine how best to be involved and coordinate with the rest of the team working on each project.
Champions are welcome and encouraged to list times and mechanisms for collaborating with their team in the Team Schedule. Participants can use this page to determine how and when to reach other team members.
The Hackathon kickoff and the project results presentations can be joined via Meetecho. The Hackathon Zulip stream may be used for general and project specific communication.
¶ IPR and Code Contribution Guideline
All Hackathon participants are free to work on any code. The rules regarding that code are what each open source project and each participant's organization says they are. The code itself is not an IETF Contribution. However, discussions, presentations, demos, etc., during the Hackathon are IETF Contributions (similar to Contributions made in working group meetings). Thus, the usual IETF policies apply to these Contributions, including copyright, license, and IPR disclosure rules.
¶ Projects Included in Hackathon
Note, all projects are open to everyone. However, some champions have identified their projects as being particularly good for those who are new to the IETF or new to the Hackathon. These projects are marked with a star, i.e. *. If you are championing a project that is great for newcomers, please add a * at the end of your project name.
For inspiration and examples of previous Hackathon projects see the previous Hackathon page.
¶ High Performance Wide Area Networks (HP-WAN)
-
Champions
Quan Xiong (xiong.quan@zte.com.cn)
Daniel King (d.king@lancaster.ac.uk)
Kehan Yao (yaokehan@chinamobile.com)
Junfeng Zhao (zhaojunfeng@caict.ac.cn) -
Project Info
High-performance WAN (HP-WAN) is designed specifically to meet the high-speed, low-latency, and high-capacity needs of data-intensive applications and enable the host-and-network collaboration for the high-speed and high-throughput data transmission, coupled with fast completion time.
Thanks to Tim Chown for Hackathon input.
-
Hackathon Plan
1.HPWAN deployment on topologies for public networks and service scenarios based on the HP-WAN framework
2.Learn about HPWAN developments and open-source controllers and orchestrators for integrated HPWAN connection management (IETF RestConf/NetConf/YANG)
3.Integration and simulation of the HP-WAN functions, such as the rate negotiation, admission control, traffic scheduling, and resource reservations with distributed signalling (IETF RSVP-TE)
4.Perform the CC algorithms optimizations (e.g. DCQCN algorithm) to simulate the traffic transmission with negotiated rates and compare with the HPWAN approach
5.Work on improvements to IETF protocols and models for cooperation between HPWAN domains. -
Related documents
Framework for High Performance Wide Area Network (HP-WAN)
https://datatracker.ietf.org/doc/draft-xhy-hpwan-framework/
Current State of the Art for High Performance Wide Area Networks
https://datatracker.ietf.org/doc/draft-kcrh-hpwan-state-of-art/
¶ YANG2API
-
Champions
Chongfeng Xie (xiechf@chinatelecom.cn)
Sicong Ma (masc@chinatelecom.cn)
Wenbin Yu (yuwb6@chinatelecom.cn)
Jibin Sun (sunjb@chinatelecom.cn)
Guozhen Dong (donggz@chinatelecom.cn)
Linda Dunbar (linda.dunbar@futurewei.com)
Bo Wu (lana.wubo@huawei.com) -
Project Info
YANG2API refers to a mechanism that converts YANG data models into APIs. It enables operators to expose YANG-based network and service abstractions to external systems, thereby better supporting dynamic, short-lived operational needs or heterogeneous environments. To improve consistency and reduce integration friction, it is important to explore how to efficiently integrate IETF YANG data models with externally developed frameworks via YANG2API, such as TMF640. Based on the YANG2API tool jointly developed, this project will investigate the effectiveness of transforming existing mainstream network and service abstractions into APIs, discuss and evaluate identified issues in the process with partners. The purpose of this project is to explore mature patterns for exposing YANG-based abstractions to external applications. -
Hackathon Plan
1.Design and implement a lightweight YANG2API environment engine that automatically generates directly callable upper-layer APIs by parsing YANG models defined in IETF standards.
2.Develop a demonstration program to showcase the automated conversion and provisioning of L3VPN and other models, verify the generated APIs by invoking them in Swagger UI, and observe the real-time generation of Netconf messages in the backend. -
Related documents
Onions Problem Statement
https://datatracker.ietf.org/doc/draft-xie-onions-problem-statement/
RFC8299 - YANG Data Model for L3VPN Service Delivery
https://datatracker.ietf.org/doc/rfc8299/
RFC8466 - A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
https://datatracker.ietf.org/doc/rfc8466/
RFC 9182 - A YANG Network Data Model for Layer 3 VPNs
https://datatracker.ietf.org/doc/rfc9182/
RFC9291 - A YANG Network Data Model for Layer 2 VPNs
https://datatracker.ietf.org/doc/rfc9291/
RFC 9833 - A Common YANG Data Model for Attachment Circuits
https://datatracker.ietf.org/doc/rfc9833/
RFC 9834 - YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
https://datatracker.ietf.org/doc/rfc9834/
RFC 9835 - A Network YANG Data Model for Attachment Circuits
https://datatracker.ietf.org/doc/rfc9835/
¶ YANG Data Model for Network Inventory (IVY)
-
Champions
Yanxia Tan (tanyx11@chinaunicom.cn)
Haomian Zheng (zhenghaomian@huawei.com) -
Project Info
Network inventory management is a fundamental functional block in the overall network management. It is a critical part for ensuring that the network remains healthy, well planned, and maintained appropriately to meet the operational objectives. Also, it allows operators to keep track of all the components deployed in their networks, including relevant embedded software and hardware. The scope of this project is to evaluate the implementation of ivy WG data models. The base model is assumed to be technology-agnostic, and could be augmented with application- and technology-specific details. -
Hackathon Plan
1.Inventory model verification, verifying the usability and interoperability of the model specified in the draft.
2.Learn and discuss other ivy draft and data models related to network inventory management. -
Related documents
A Base YANG Data Model for Network Inventory
https://datatracker.ietf.org/doc/draft-ietf-ivy-network-inventory-yang/
¶ SRv6 for Inter-Layer Network Programming
-
Champions
Minxue Wang (wangminxue@chinamobile.com )
Junfeng Zhao (zhaojunfeng@caict.ac.cn )
Jie Dong (jie.dong@huawei.com )
Ran Chen (chen.ran@zte.com.cn )
Junfang Wang (wjf@fiberhome.com ) -
Project Info
SRv6 END.IL is a variant of the SRv6 End behavior, an SRv6 END.IL SID steers packets to a remote network node via an underlay network connection. SRv6 END.IL behavior can be used for SRv6 based inter-layer path programming and traffic engineering, so as to provide differentiated and guaranteed performance for different services. -
Hackathon Plan
1.Learn about the background and key protocol mechanism of SRv6 END.IL;
2.Demonstrate multi-vendor interworking networking and perform testing for SRv6 END.IL;
3.Validate service connectivity and performance guarantee in SRv6 END.IL interworking scenarios;
4.Review the current SRv6 END.IL draft, propose necessary updates and future related work in IETF. -
Related documents
SRv6 for Inter-Layer Network Programming
https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-inter-layer-programming/
¶ Validate YANG-Push to Message Broker End-To-End Data Processing Chain
-
Champion(s)
Thomas Graf (thomas.graf @ swisscom.com)
Wanting Du (wanting.du @ swisscom.com)
Ahmed Elhassany (ahmed.elhassany @ swisscom.com)
Leonardo Rodoni (leonardo.rodoni @ swisscom.com)
Rafael Julio (rafael.julio @ swisscom.com)
Benoit Claise (benoit @ everything-ops.net)
Paolo Lucente (paolo @ pmacct.net)
Rob Wilton (rwilton @ cisco.com)
Scott Huang (scohuang @ cisco.com)
Daniel Voyer (davoyer @ cisco.com)
Sivakumar Sundaravadivel (sivakuma @ ciena.com) -
Draft Specifications Message Broker
https://datatracker.ietf.org/doc/html/draft-ietf-nmop-yang-message-broker-integration
https://datatracker.ietf.org/doc/html/draft-ietf-nmop-message-broker-telemetry-message
https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-anydata-validation -
Draft Specifications YANG-Push
https://datatracker.ietf.org/doc/html/rfc8639
https://datatracker.ietf.org/doc/html/rfc8641
https://datatracker.ietf.org/doc/html/rfc9196
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-notif-envelope
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-yang-notifications-versioning
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-distributed-notif
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-yp-transport-capabilities -
Project Info
https://www.network-analytics.org/yp/, validate and verify -
5 YANG-Push Publishers
-
2 YANG-Push Receivers
-
2 YANG-Push Network Telemetry Message
-
1 YANG Message Broker Producer and Schema Registry
-
3 YANG Message Broker Consumers
implementation in the area of YANG data integration automation. Subscribe to YANG data on YANG-Publisher, obtain and register all YANG modules necessary to build YANG schema tree, register YANG schemas to Schema Registry and verify YANG notifications against scheme trees and produce and consume from Message Broker.
- Repository
https://github.com/network-analytics/ietf-network-analytics-document-status/tree/main/125/Hackathon
https://github.com/NetGauze/NetGauze/releases/tag/v0.9.1
https://github.com/pmacct/pmacct
https://github.com/CESNET/libyang/releases/tag/v4.2.2
https://github.com/CESNET/libyang/compare/master...devel
¶ DKIM2
- Champions
Bron Gondwana brong@fastmailteam.com - Project Info
Continuing DKIM2 work, following on from the last hackathon. - Repository -
https://github.com/dkim2wg/interop
¶ Agent Communication Framework for Network AIOps
-
Champions
Qiong Sun (sunqiong@chinatelecom.cn)
Xin Song (songx18@chinatelecom.cn)
Yu Fu (fuy44@chinatelecom.cn)
Jiajun Li (lijj124@chinatelecom.cn) -
Project Info
As the development of large model and agent technology, it is a trend for multi-agent collaboration to solve complex problems. This project proposes a multi-agent communication and collaboration framework that facilitates the coordination of heterogeneous multi-agents and supports intelligent automatic network operations and maintenance (AIOps). Its architecture includes an AI gateway and an Agent Name Service, along with capabilities such as monitoring and tracking, as well as security protection. This Agent Communication Framework provides a comprehensive solution for multi-agent communication and collaboration, laying the foundation for future interactive, scalable, secure, and controllable multi-agent network intelligent operations and maintenance. -
Hackathon Plan
1.A multi-agent communication and collaboration framework includes an AI gateway and an Agent Name Service specified in the draft.
2.Use cases for multi-agent communication and collaboration to support intelligent automatic network operation and maintenance. -
Related documents
Agent Communication Framework for Network AIOps
https://datatracker.ietf.org/doc/draft-fu-nmop-agent-communication-framework/
¶ Agent Gateway for Dynamic Multi-agent Secured Collaboration
-
Champions
Sicong Ma (masc@chinatelecom.cn)
Jibin Sun (sunjb@chinatelecom.cn)
Xing Zhang (hszhang@bupt.edu.cn)
Zhuoran Li (lizr9@chinatelecom.cn)
Wei Wang (wangw36@chinatelecom.cn) -
Project Info
With the rapid development of agent-related technologies, agent communication is evolving toward heterogeneity and multi-agent collaboration, giving rise to requirements such as on-demand access, dynamic networking and elastic collaboration for agents. To meet the requirements, this project proposes an agent gateway based on the dynamic multi-agent secured collaboration framework, which supports capabilities including automatic discovery, registration, capability synchronization, secure communication, and flexible scalability for agents. The core objective of this project is to explore a feasible solution for inter-agent communication, laying a foundation for the advancement of agent communication technologies. -
Hackathon Plan
1.A Dynamic Multi-agent Secured Collaboration Infrastructure Architecture from an infrastructure perspective. For detailed descriptions, please see the draft in related documents.
2.A demo for dynamic multi-agent secured collaboration gateway. -
Related documents
Dynamic Multi-agent Secured Collaboration Infrastructure Architecture
https://datatracker.ietf.org/doc/html/draft-li-dmsc-inf-architecture-03
¶ Optimizing Agent Context Interaction
-
Champions
Zeze Chang (changzeze@huawei.com)
Shuping Peng (pengshuping@huawei.com) -
Project Info
Multi-agent collaboration has been widely studied as an effective approach for addressing complex and multi-turn interactive tasks. However, in current agentic workflows, contextual information is often exchanged in an unstructured and redundant manner, leading to excessive token consumption, increased execution latency, and reduced task completion success rates, especially in multi-step and multi-agent scenarios. The project focuses on designing and experimenting with structured agent context interaction mechanisms, including precise context distribution, context isolation among agents, and fine-grained task and progress management. A master–invoked agent interaction scheme is expected to demonstrate how task-related contexts can be selectively delivered to invoked agents and incrementally updated during task execution. -
Hackathon Plan
- Design and implement a multi-agent context interaction framework based on the structured context schemas defined in the draft.
- Develop a demo to demonstrate the effectiveness of the proposed agent context interaction mechanism.
- Related documents
to be released
¶ Agent Communication Gateway for Semantic Routing and Working Memory
-
Champions
Xiaohui Xie (xiexiaohui@tsinghua.edu.cn)
Zian Wang (zianwang@bupt.edu.cn)
Tianshuo Hu (huts22@mails.tsinghua.edu.cn) -
Project Info
As multi-agent systems are increasingly used for complex, multi-step interactive tasks, the way agents exchange context has become a key bottleneck: in many current agentic workflows, context is transmitted in an unstructured, redundant, and broadcast-like manner, which causes excessive token consumption, higher latency, and lower task success rates—especially when multiple agents are orchestrated across multiple steps. This project proposes and prototypes an Agent Communication Gateway that sits between agents and tools/services, providing two core capabilities: Semantic Routing, which intelligently routes messages/contexts to the most relevant agent(s) or tool endpoints based on semantic intent, task state, and routing policies to reduce unnecessary fan-out and duplicated context delivery; and Gateway Memory, which maintains structured, scoped memory (e.g., per-task / per-agent / per-session) to support selective context retrieval, context compression/summarization, and incremental updates, enabling agents to receive only the context they need at each step while preserving long-horizon task continuity. -
Hackathon Plan
- Design and implement a lightweight agent communication gateway with (a) semantic routing policies and (b) structured working memory.
- Integrate the gateway into a simple multi-agent workflow and validate that context delivery becomes more selective and less redundant.
- Develop a demo to showcase improvements such as reduced token usage, reduced latency, and improved task completion stability.
-
Related documents
To be released
¶ IPsec and IKEv2
- Champions
Valery Smyslov (valery@smyslov.net) - Project Info
Interoperability testing of new IKEv2 extensions:
-- Downgrade Prevention for the Internet Key Exchange Protocol Version 2 (IKEv2)
-- Optimized Rekeys in the Internet Key Exchange Protocol Version 2 (IKEv2)
-- Separate Transports for IKE and ESP
-- Post-quantum Hybrid Key Exchange with ML-KEM in the Internet Key Exchange Protocol Version 2 (IKEv2)
-- Post-quantum Hybrid Key Exchange in IKEv2 with FrodoKEM
-- Using IKE Fragmentation for Large Messages
-- IKEv2 Support for Child SA PFS Policy Information
-- A Larger Internet Key Exchange version 2 (IKEv2) Payload
-- Using Classic McEliece in the Internet Key Exchange Protocol Version 2 (IKEv2) - Specifications
-- https://datatracker.ietf.org/doc/draft-ietf-ipsecme-ikev2-downgrade-prevention/
-- https://datatracker.ietf.org/doc/draft-ietf-ipsecme-ikev2-sa-ts-payloads-opt/
-- https://datatracker.ietf.org/doc/draft-ietf-ipsecme-ikev2-reliable-transport/
-- https://datatracker.ietf.org/doc/draft-ietf-ipsecme-ikev2-mlkem/
-- https://datatracker.ietf.org/doc/draft-wang-ipsecme-hybrid-kem-ikev2-frodo/
-- https://datatracker.ietf.org/doc/draft-smyslov-ipsecme-ikev2-fragm-large-msg/
-- https://datatracker.ietf.org/doc/draft-pwouters-ipsecme-child-pfs-info/
-- https://datatracker.ietf.org/doc/draft-nir-ipsecme-big-payload/
-- https://datatracker.ietf.org/doc/draft-smyslov-ipsecme-ikev2-mceliece/
¶ Low-Power Wireless IPv6 Networking with Thread *
-
Champion
Stuart Cheshire <cheshire@apple.com> -
Thread Overview
Thread is a specification for how to carry IPv6 datagrams over a self-configuring mesh of low-power IEEE 802.15.4 wireless links. Stuart Cheshire gave a brief presentation about Thread at the IETF 119 IAB Open meeting in Brisbane. The Thread specification is developed and published by the Thread Group. There are several independent implementations of Thread, the main one being the OpenThread open source project. This Hackathon event is open to all — Thread Group membership is not required, though of course Thread Group members are also welcome to participate.
-
Participants and Project Info
- To avoid taking up too much space on the main Hackathon page, Thread participants and projects are listed separately on the Thread Projects page.
Don’t see anything that interests you? Feel free to add a project to the list, sign up as its champion, and show up to work on it. Note: you must login to the wiki to add content. If you add a new project, we suggest you send an email to (hackathon@ietf.org) to let others know. You may generate interest in your project and find other people who want to contribute to it.
TEMPLATE: Copy/paste and update the following template to add your project to the list:
### Your Project
- **Champions**
name and email
- **Project Info**
project description
To edit the wiki, log in using your IETF Datatracker login credentials. If you don't yet have an IETF Datatracker account, you may get one by going here and requesting a new account.