¶ IETF 123 Hackathon
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: 19 - 20 July 2025 (Saturday - Sunday)
Where: Meliá Castilla
Room: El Prado & Aranjuez
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+1)
¶ Saturday, 19 July
- 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, 20 July
- 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, 21 July, 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 21 July
¶ Shared Workspace
- Space for groups to gather and collaborate on running code
- Monday - Friday, 21 - 25 July, Room: TBD
- View the schedule or reserve space for your team/project
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.
¶ The Fast Software Authenticated Encryption HiAE *
-
Champions
- Phuong Pham pham.phuong@huawei.com
- Lucas Prabel lucas.prabel@huawei.com
- Shuzhou Sun sunshuzhou@huawei.com
- Frank Denis fdenis@fastly.com
-
Project Info
HiAE is a high-throughput authenticated encryption algorithm designed for next-generation wireless communication and data transmission applications. The design leverages the AES round function to ensure high and consistent performance across both ARM and x86 architectures, with support for AES acceleration. -
Hackathon Plan
The goal of this project is to evaluate the performance of HiAE across a range of devices — including mobile phones, laptops, and servers — on both x86 and ARM platforms.
We welcome all participants who are familiar with:
-
SIMD instruction sets
-
Mobile performance testing
-
Draft Specifications
-
Repository
¶ RESTful Provisioning Protocol (RPP)
-
Champions
Maarten Wullink maarten.wullink@sidn.nl
Pawel Kowalik pawel.kowalik@denic.de -
Project Info
The RPP working group is focused on designing a new protocol via a series of specifications known collectively as the RESTful Provisioning Protocol (RPP). -
Hackathon Plan
- Discuss/Develop/Validate proposals for protocol requirements and architecture
- Develop running code, e.g.:
- RPP server & client
- RPP to EPP adapter
- Other interesting ideas.
-
Related documents
¶ 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.
¶ PQC in open source software.
-
Kavish Nadan (kn@cyberstorm.mu)
-
Jaykishan Mutkawoa (jay@cyberstorm.mu)
-
Loganaden Velvindron (logan@cyberstorm.mu)
-
Project Info
PQC in open source software.
¶ CODECO - Benchmarking with network-compute metrics and energy-awareness across Edge-Cloud
-
Challenge 1: Green network observability and reporting
This challenge explores energy-awareness observability and reporting that may suit telco-cloud resource management. The challenge relies on approaches and code under development in the context of the Horizon Europe project CODECO, and also relates with a new informational draft being proposed to IETF GREEN.
The main goal of this challenge is to consider enhancements to CODECO (as a relevant example of an edge-cloud orchestrator that provides a data-compute-network approach) in terms of monitoring and exporting metrics aligned with GREEN principles e.g., CO2 network footprinting, green workload percentage.
The reporting will be provided to Prometheus and eventually to SDN; alignment to YANG will be considered.-
Champions
Rute C. Sofia (sofia@fortiss.org)
Dalal Ali (ali@fortiss.org)
Kaikang Huang (khuang@fortiss.org) -
Related WG
GREEN - Getting Ready for Energy-Efficient Networking -
Specifications
draft-sofia-ietf-green-energy-aware-diffserv -
Repository and Instructions
https://gitlab.eclipse.org/eclipse-research-labs/codeco-project/hackathon/challenge-GREEN
-
-
Challenge 2: Joint exposure of compute and network metrics for path selection
This enhancement to the CODECO framework introduces CATS-aligned path selection capabilities by leveraging CODECO’s existing compute and network observability. The goal is to support computing-aware traffic steering across the Edge-Cloud continuum, in line with the architectural direction of IETF CATS.
CODECO collects real-time infrastructure metrics -such as CPU , memory usage, latency, and network congestion— from its ACM and NetMA components and aggregates them via the PDLC-CA module into node and cluster scores. These scores are then used to inform microservice placement and potential workload redirection decisions, consistent with CATS principles.
The aim is to adapt the current approach to provide scores from PDLC and PDLC-CA to NetMA which may assist in Path ranking and selection based on dynamic network latency and congestion data.
This design supports the CATS use case of service instance selection and path steering based on combined compute and network metrics, helping optimize service experience in distributed, heterogeneous edge environments.
Setup instructions here.-
Champions
Luis Contreras (luismiguel.contrerasmurillo@telefonica.com)
Alberto del RĂo (arp@gatv.ssr.upm.es)
Alejandro Muñiz (alejandro.muniz@telefonica.com)
Jose Castillo Lema (jlema@redhat.com)
Guillermo Sánchez Illán (guillermo.sanchezillan@telefonica.com) -
Related WG
CATS - Computing-Aware Traffic Steering -
Specifications - Drafts
draft-ietf-cats-metric-definition -
Repository and Instructions
https://gitlab.eclipse.org/eclipse-research-labs/codeco-project/hackathon/challenge-CATS
-
-
Challenge 3: Benchmarking Network-aware Edge-Cloud Orchestration with CODEF
In alignment with the IETF BMWG's current focus on extending benchmarking methodologies to containerized and cloud-native environments, this initiative proposes the use of the CODECO CODEF —an open-source, microservice-driven software-based testbed framework— to evaluate the performance and scalability of edge-cloud orchestration across heterogeneous infrastructures.
CODEF supports comprehensive benchmarking of native and customized Kubernetes (K8s)-SDN distributions, container networking interfaces (CNIs), and orchestration components under realistic workload conditions.
This work directly supports BMWG's objective of providing standardized, reusable methodologies for benchmarking the performance of virtualized and containerized networking solutions in modern, distributed infrastructures.-
Objective:
Use the open-source CODEF framework to benchmark and compare the performance of various Container Network Interface (CNI) plugins, including L2S-M, within containerized edge-cloud environments. -
Champions
George Koukis (george.koukis@athenarc.gr)
Tina Samizadeh (samizadeh@fortiss.org)
Alex Tjaarda (abuning@pa.uc3m.es) -
Related WG
BMWG - Benchmarking Methodology -
Specifications
Draft being proposed - https://github.com/rute19104/ietf-bmwg-draft-2025-1 -
Repository and Instructions
https://gitlab.eclipse.org/eclipse-research-labs/codeco-project/hackathon/challenge-3
CODEF can be downloaded here
-
-
Background on CODECO
CODECO Project Repository in GITLAB
CODECO Project website
CODECO is an open source project. The code developed will be open source under the project and the IETF rules.
You can develop in your own repository or in the hackathon repository enabled to this purpose: Hackathon repository.
If you develop directly in the Hackathon repository or you upload the code to it, you will gain extra visibility and you will opt to IRCEP Awards. It is optional, and in order to do it, you will need to Register in the Eclipse Foundation, log in and sign the Eclipse Contributor Agreement.
For those interested on CODECO and looking for more information, please reach out to the coordinator Rute C. Sofia (sofia@fortiss.org).
¶ Identity Crisis in Attested TLS for Confidential Computing
-
Champions
- Muhammad Usama Sardar (muhammad_usama.sardar at tu-dresden.de)
-
Project Info
- 3 main ways to combine attestation in TLS:
- Pre-handshake attestation (Paper)
- Intra-handshake attestation (Internet draft)
- Post-handshake attestation (Internet draft and Sec. 4 in this paper)
- Hackathon plan
- Discuss the nits of identity crisis
- Discuss possible solutions
- Discuss open issues
- What is the "long-term identity" of the CC workload? How is "long-term identity" assigned to the CC workload? Which entity supplies this "long-term identity"? How is that Identity Supplier trusted?
- How is CA-certified Long-Term Key (LTK) injected in the Confidential Computing workload in the first place?
- We aim to seek collaborators (knowledgeable about at least one of the following: TLS, remote attestation, formal methods or confidential computing) who will join us in this project. We also welcome reviewers who can give us feedback on the draft. If you are interested, please contact by email.
- Tool for formal analysis: We currently use ProVerif but other tools are very welcome.
- 3 main ways to combine attestation in TLS:
-
Background on Attestation
-
Background on Attested TLS
¶ Identifier Locator Network Protocol (ILNP)
-
Champions
- Saleem Bhatti saleem@st-andrews.ac.uk
- Rodney Grimes rgrimes@freebsd.org
- Alistair Woodman awoodman@netdef.org
-
Project Info
- https://ilnp.cs.st-andrews.ac.uk
- RFCs 6740(E) - 6748(E)
- The basic approach to this is to deprecate the concept of an IP Address and replace it with addressing using a separate Locator and Identifier values, a pairing of which forms an Identifier-Locator Vector (ILV). Although the architectural concept is independent of any particular network protocol, our ongoing research demonstration is based on realising ILNP on IPv6.
¶ Mira: scalable multi-gateway TSCH networking over BLE
-
Champions:
Geovane Fedrecheski, geovane.fedrecheski@inria.fr -
Project Info
Mira (Micro-robot Interconnect Radio Architecture) is a lightweight, open-source protocol stack that brings multi-gateway Time Slotted Channel Hopping (TSCH) to Bluetooth Low Energy (BLE) radios, with support for node-initiated roaming. Mira is a completely new link layer that replaces the BLE controller and host software. Built to support large-scale robot swarms and dense IoT deployments, Mira enables fast handovers, predictable latency, and efficient over-the-air updates.
BLE alone does not scale beyond 5–20 concurrent connections (depending on the stack), Wi-Fi supports more nodes but suffers from collisions and higher power draw, and 6TiSCH offers deterministic communication but lacks native roaming support.
Mira fills this gap by:
- Implementing TSCH directly over the BLE PHY (bypassing the BLE controller and host stack)
- Supporting seamless roaming across multiple gateways without requiring coordination
- Running on widely available hardware (e.g., nRF52840)
- Enabling fast Over-The-Air Programming (OTAP) and dense deployments (100+ nodes)
While Thread and BLE Mesh are designed for static home automation using IPv6 over 6LoWPAN or flooding protocols, Mira targets mobile and high-density scenarios—such as robot swarms—where real-time communication, bounded latency, and remote firmware updates are crucial.
At the IETF 123 Hackathon, we aim to:
- Demonstrate a live Mira deployment
- Explore how Mira (as a link-layer protocol) can interoperate with upper-layer IETF technologies, including 6LoWPAN, UDP, and CoAP
- Specify/implement a secure association for Mira using IETF technologies such as EDHOC and ELA
We welcome collaboration with anyone working on:
- Low-power networking and Internet of Things protocols
- CoAP over BLE or lightweight embedded stacks
- Mobility extensions to 6TiSCH or RPL
- Robotics, swarm testbeds, or dense IoT deployments
¶ Post-Quantum Cryptography (PQC) in X.509, Signatures, KEMs, CMS and protocols
-
Champion(s)
John Gray (john.gray@entrust.com)
Mike Ounsworth (mike.ounsworth@entrust.com)
Massimiliano Pala (massimiliano.pala@wellsfargo.com)
Julien Prat (julien.prat@cryptonext-security.com) -
Draft Specifications
https://datatracker.ietf.org/doc/draft-ietf-lamps-dilithium-certificates/
https://datatracker.ietf.org/doc/draft-ietf-lamps-kyber-certificates/
https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-sigs/
https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-kem/
https://datatracker.ietf.org/doc/rfc9629/
https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc4210bis/
https://www.ietf.org/id/draft-ietf-lamps-certdiscovery/
https://datatracker.ietf.org/doc/draft-bonnell-lamps-chameleon-certs/
https://datatracker.ietf.org/doc/draft-gazdag-x509-hash-sigs/ -
Project Info
Test interoperability of Post Quantum algorithms in x.509 structures (Certificates, keys, CMS and other drafts). This project started in November 2022 and continues to evolve. We currently have some github automated actions to automaticlaly test submitted artifacts allowing implementations to get immedidate feedback on their compatibility. This allows us to test interoperability between different algorithm implementations, gain experience using these new algorithms, and provide feedback to the standards groups about practical usage.
A good starting place is our Github repository: https://github.com/IETF-Hackathon/pqc-certificates
For information on OIDs used to create interoperable structures, consult: https://github.com/IETF-Hackathon/pqc-certificates/blob/master/docs/oid_mapping.md
At IETF 123, we plan to add more automation, add interoperability testing for the private key formats (like ML-DSA and ML-KEM), and continue to update our implementations to support the FIPS 203, 204 and 205 algorithm standards. We are also looking for implementations of Composite Signatures, Composite KEM and other PQ transition mechanisms that are being standardized.
There is also interest in setup and testing the use of hybrid certificates for the TLSv1.3 protocol. The goal of the experiment is to explore different options for efficient use of hybrid certificates' and their multiple signature keys in the TLS protocol. We are looking for collaborations and ideas that can be then brought forward within the IETF and other standardization bodies (e.g., X9, ISO, etc.).
¶ Validate Configured Subscription YANG-Push Publisher Implementations
-
Champion(s)
Thomas Graf (thomas.graf @ swisscom.com)
Yannick Buchs (yannick.buchs @ swisscom.com)
Ahmed Elhassany (ahmed.elhassany @ swisscom.com)
Holger Keller (holger.keller @ telekom.de)
Rob Wilton (rwilton @ cisco.com)
Daniel Voyer (davoyer @ cisco.com)
Benoit Claise (benoit.claise @ huawei.com)
Haomian Zheng (zhenghaomian @ huawei.com)
Qiufang Ma (maqiufang1 @ huawei.com)
Jérémie Leska (jeremie.leska @ 6wind.com)
Samuel Gauthier (samuel.gauthier @ 6wind.com) -
Draft Specifications
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
https://datatracker.ietf.org/doc/html/draft-netana-nmop-message-broker-telemetry-message -
Project Info
https://www.network-analytics.org/yp/
Validate and verify 4 YANG-Push publisher and 1 YANG-Push receiver implementation in the area of: -
Subscription automation
Discover YANG-Push systems and notifications capabilities and configure periodical and on-change subscriptions with netconf. -
Notification integration
Validate subscription state change and push-update and push-change-update notifications against schema with yanglint
Validate draft-ietf-nmop-message-broker-telemetry-message in message broker for draft-ietf-nmop-yang-message-broker-integration integration -
Repository
https://github.com/network-analytics/ietf-network-analytics-document-status/tree/main/123/Hackathon
https://github.com/NetGauze/NetGauze/pull/213
¶ GREEN framework and Use Cases
-
Champion(s)
Luis M. Contreras (luismiguel.contrerasmurillo@telefonica.com)
Marisol Palmero (marisol.ietf@gmail.com)
Jan Lindblad (jan.lindblad+ietf@for.eco)
Emile Stephan (emile.stephan@orange.com)
Benoit Claise (benoit.claise@huawei.com)
Qin Wu (bill.wu@huawei.com)
Artur Hecker (Artur.Hecker@huawei.com)
Carlos J. Bernardos (cjbc@it.uc3m.es) -
Collaborator(s)
Prasad KN (skabbina@cisco.com)
Josei Tolentino (jotolent@cisco.com) -
Draft Specifications
https://datatracker.ietf.org/doc/draft-stephan-green-use-cases/
https://datatracker.ietf.org/doc/draft-belmq-green-framework/
https://datatracker.ietf.org/doc/draft-petra-path-energy-api/ -
Project Info
Validate GREEN Framework to cover different use cases listed in the GREEN use cases draft:
- device/component energy consumption report with information collected directly from the device or PDU connected.
- API integration to cover multi/inter domain.
- End-to-End use case, video streaming.
This use case aims to provide energy information at the service level to both users and providers, addressing the rebound effects seen in traditional energy efficiency approaches. By raising user awareness of ecological impacts and integrating incentivization methods, such as carbon market access, the goal is to internalize ecological effects for users. The demonstration platform will showcase energy information exposure through the collection, aggregation, and attribution of energy data across various network components, including wireless, transport, and data center equipment. Metrics will be expressed using standard data models like YANG to facilitate cross-domain energy information exchange. The platform will be validated with a video streaming example, while open questions remain about the best reporting interfaces and protocols, either as in-session reports or domain-specific exposure APIs.
The setup will consist on remote infrastrcuture in TelefĂłnica Network and Automation lab plus on-site devices.
- Repository
-
Sustainability Insights in a box Open Source
https://github.com/cisco-open/sustainability-insights-in-a-box.git -
Documentation for retrieving information from the SmartPDU at TelefĂłnica lab
https://github.com/luismcontreras/HackathonIETF123/wiki/Documentation
¶ Model-Based IOT Gateway (ASDF/NIPC)
-
Champion(s)
Bart Brinckman (bbrinckm@cisco.com)
Rohit Mohan (rohitmo@cisco.com) -
Draft Specifications
model registration: https://datatracker.ietf.org/doc/draft-ietf-asdf-sdf/
device onboarding: https://datatracker.ietf.org/doc/draft-ietf-scim-device-model/
gateway: https://datatracker.ietf.org/doc/draft-ietf-asdf-nipc/ -
Project Info
Provide the ability to interop with both a vendor implementation as well as an open source implementation of the drafts.
Furhter develop the open source implementation, python & java client libraries and sample applications
Provide the ability to provide feedback on the drafts -
Repository
gateway draft, model examples, openapi: https://github.com/ietf-wg-asdf/asdf-nipc
open source repo: https://github.com/iot-onboarding/tiedie
¶ MAPRG Happy Eyeballs and IPv6 Test Pod Open Testing
-
Champions
David Plonka dave@plonka.us (MAPRG co-chair, WiscNet's Principal Research Scientist) -
Project Info
The Measurement & Analysis for Protocols Research Group (MAPRG) and WiscNet (AS2381) will provide an open testing environment for participants to determine how well equipment and applications work, including Happy Eyeballs, in a variety of IPv6 network environments.To accomplish this, we will provide access to the IPv6 Test Pod (https://ipv6-pod.info/): a wireless and wired access point specially configured for testing IPv6 compatibility and graciously provided by Internet2 and the ARIN Community Grant program.
The IPv6 Test Pod provides a variety of IPv6 test networks via Wifi SSIDs and optionally over Wired Ethernet connections. All you have to do is provide a wired internet connection to the WAN interface (IPv4-only is OK), power, and it will provide a series of networks to test devices and software with:
- Dual-Stack (IPv4 and IPv6)
- IPv6-only
- IPv6 only with NAT64+DNS64
- IPv6-only with NAT64+PREF64
- IPv6 only with NAT64+DNS64+PREF64
In addition to employing the IPv6 Test Pod, we'll do complementary testing with IPvFoo browser extension, the IETF network, etc.
-
Open Call for Participants
Anyone can drop by for ad hoc IPv6-compatibility testing of your wireless or wired user equipment, e.g., smartphone, or application(s) of interest, web-based or otherwise.Please join the project, and stay a while, if you are an IPv6 or transition mechanism aficionado, or simply want to learn more about using IPv6 in a live environment. We could use help with testing and identifying the root causes of problems found.
-
Background:
¶ NTP Version 5
- Champions
Karen O'Donoghue (kodonog@pobox.com)
Dieter Sibold (dsibold.ietf@gmail.com) - Project Info
Interoperability testing between different NTPv5 implementations. - Draft Specifications
https://datatracker.ietf.org/doc/draft-ietf-ntp-ntpv5/ - Repositories
- NTPD-RS: https://github.com/pendulum-project/ntpd-rs
- Experimental: https://github.com/mlichvar/ntp5-exp
- NTPv5 in Chrony: https://github.com/mlichvar/chrony-ntp5
¶ Testing Congestion Control and Queue Management Mechanisms
-
Champions
- Mohit P. Tahiliani (tahiliani@nitk.edu.in)
- Akash Ravi (akashravi.211cs207@nitk.edu.in)
- Anirudh V. Gubbi (anirudhvgubbi.211cs210@nitk.edu.in)
- Aniket Singh (aniketsingh.232cs001@nitk.edu.in)
- Navaneet Y V N (navaneetyvn.211cs234@nitk.edu.in)
- Satyam Shukla (satyamshukla.211cs254@nitk.edu.in)
- Shashank G (shashankg.211cs256@nitk.edu.in)
-
Project Info
- Testing of FQ-CoDel and FQ-PIE using ns-3, NeST and WiFi APs
- Improving the delay-throughput tradeoff with a new version of CoDel
- An example for rate-limited sender implementation in ns-3
- Testing the effectiveness of Alternative Backoff with ECN (ABE) using ns-3
-
Related documents
-
Repositories
¶ Low-Latency, Low-Loss, Scalable Throughput (L4S) and Accurate ECN Interop
- Champions
Greg White (g.white@cablelabs.com) - Project Info
- L4S and AccECN enable applications to receive fine-grained congestion feedback from the network that allows them to achieve full link utilization, ultra-low latency, ultra-low latency variation, and near-zero packet loss.
- This Interop Event will bring together different congestion control implementations and different network implementations of L4S to test RFC/draft compliance, interoperability, and performance in various conditions.
- Specifications
¶ Agent Protocol Security
- Champions
Song Yurong (songyurong1@huawei.com)
Foo Chuan Ann (foo.chuan.ann1@h-partners.com) - Project Info
In recent years, AI agents have witnessed remarkable progress and are increasingly recognized as a pivotal force in various fields. Regarding agent protocols, they play a crucial role in enabling seamless communication between agents, external tools, and data sources. However, with the development of AI agents and their protocols, security has become a pressing concern.
In this hackathon we aim to validate the security design (e.g. identity, authentication, authiorization) for agent protocols, including agent-to-other protocols (e.g. MCP), or agent-to-agent protocols (e.g. A2A). - Related Side Meeting
- TBD
- Agent Protocol Background
https://modelcontextprotocol.io/introduction
https://www.a2aprotocol.org/zh - Repositories
- TBD
¶ EDHOC-PSK Interoperability Testing
-
Champions
Elsa Lopez Perez (elsa.lopez-perez@inria.fr) -
Project info
EDHOC (Ephemeral Diffie-Hellman Over COSE) is a lightweight authenticated key exchange protocol designed for constrained environments (IoT, embedded devices, etc.).
The LAKE working group is currently working in a new authentication method for eDHOC based on Pre-Shared Keys (PSK). There are different implementations of this authentication method, but it has not yet been tested.
This project aims to build a suite for interoperability testing between different EDHOC-PSK implementations. The goal is to define test vectors, capture and analyze trace logs, and report compatibility issues or specification gaps.
-
Hackathon Goals
-
Identify and collect existing EDHOC-PSK implementations
-
Define test vectors and expected message flows
-
Run cross-implementation tests and record results
-
Provide feedback to developers and IETF draft authors
-
-
EDHOC Background
-
Repositories
¶ SCONE
-
Champions
- On-site:
- Marcus Ihlar (marcus.ihlar@ericsson.com)
- Wesley Eddy (wesleyeddy@meta.com)
- Matt Joras (mjoras@meta.com)
- Zaheduzzaman Sarker (zahed.sarker.ietf@gmail.com)
- Off-site:
- Renjie Tang (renjietang@google.com)
- Jon Varsanik (jvarsanik@google.com)
- Tina Tsou (tina.tsou@tiktok.com)
- On-site:
-
Project Info
Collaborators will make progress on early implementation and testing of SCONE working group technology. SCONE requires support both by end-host QUIC stacks and by network elements, so work at the hackathon can be coordinated between people working on QUIC stacks, network devices, and other tools (e.g. Wireshark, etc.).
There will be a mixture of on-site and off-site collaborators supported. At least one prototype in-network element is expected to be available on-site. It may be possible to route traffic through it from off-site.
-
Hackathon Goals
- Test basic SCONE interoperation between in-network element prototypes and end-host stack prototypes.
- Take any lessons learned or clarifications for the spec back to the working group.
- Establish the foundation for future tests and collaboration on SCONE.
-
Repositories
- Participants can work on any code that they have access to, in order to add or test SCONE support.
- Some code planned to be tested is not open source.
- https://github.com/wesley-eddy/scone-tools
- TBD other open source repositories
¶ Network Attestation for Secured foRwarding
-
Champions
Michael Richardson (mcr@sandelman.ca)
Peter Chunchi Liu (liuchunchi@huawei.com)
Meiling Chen (chenmeiling@chinamobile.com)
Diego Lopez (diego.r.lopez@telefonica.com)
Antonio Perales (antonio.pastorperales@telefonica.com) -
Project Info
In the current network deployments, communicating entities implicitly rely on peer entities and use paths as determined by the control plane. These available path(s) are implicitly trusted. Communicating entities have very little information about the entities in the paths over which their traffic is carried, and have no available means to audit the entities and paths, beyond basic properties like latency, throughput, and congestion. However, increased demand in network security, privacy, and robustness makes tools for enabling visibility of the entities' security characteristics a necessity.
The Network Attestation for Secured foRwarding (NASR) aims to address the challenges associated with proving state and characteristics of a network path are compliant to a set of claims, so as to achieve predictable and verifiable forwarding behavior.
- Related Meetings
- Related Documents
https://datatracker.ietf.org/doc/draft-liu-nasr-architecture/
https://datatracker.ietf.org/doc/draft-lkspa-wimse-verifiable-geo-fence/
https://datatracker.ietf.org/doc/draft-richardson-rats-pop-endorsement/ - Repositories
- TBA
¶ Deterministic Networking
-
Champions
David Rico (david.rico@uc3m.es)
Carlos J. Bernardos (cjbc@it.uc3m.es)
Luis M. Contreras (luismiguel.contrerasmurillo@telefonica.com)
Marta Blanco (marta.blancocaamano@telefonica.com) -
Project Info
Our team brings together the PREDICT-6G, DESIRE6G and 6G-DATADRIVEN-04 projects to tackle Deterministic Networking (DetNet) at IETF 123 Hackathon in Madrid.
- Challenge 1: Controller plane API and intelligence
Building on PREDICT-6G’s open-source DetNet-based dataplane—an XDP/eBPF implementation that already supports PREOF (Packet Replication, Elimination, and Ordering Functions) and runs DetNet over MPLS-in-UDP/IP. Currently, its DetNet functionality is statically configured at boot time via JSON configuration files and lacks a standardized way to interact with the dataplane dynamically.
To overcome these limitations, we will design and implement a lightweight control and configuration API—exposed via REST/gRPC—that interfaces directly with the dataplane. This API will allow operators—and higher-level controllers—to define node behavior on the fly: pushing new service definitions, querying per-node state, updating PREOF replication and elimination settings, or modifying a node’s MPLS role (push, pop, forward), all without restarting or reloading static files.
On top of this, we will integrate a decision-making engine powered by a compact AI module. Given a service profile (with data such as bandwidth, latency bound, extra TSN needs such as PREOF-style reliability, etc.) and a network topology model, this engine will compute suitable DetNet paths—including disjoint and multi-path options—and automatically invoke the API to configure each hop. As services originate, change, or terminate, the system will coordinate per-flow S-Label usage, adjust resource reservations, and adapt routes—reconfiguring nodes seamlessly and meeting stringent DetNet guarantees end-to-end.- Related Documents
https://datatracker.ietf.org/doc/draft-ietf-detnet-controller-plane-framework/ - Repositories
- TBA
- Related Documents
- Challenge 2: In-band Telemetry (INT) for DetNet
5G and emerging 6G systems must make increasingly faster and more reliable decisions at the network edge. In industrial environments, determinism is one of the most critical connectivity requirements—the ability to deliver information at a precise moment in time (in-time) or within a strict delay bound (on-time). Deterministic communication not only constrains delivery latency, but also minimizes delay variation (jitter). In parallel, network reliability becomes essential to ensure uninterrupted service, particularly for mission-critical applications. Today, one of the leading proposals to support deterministic behavior at Layer 3 is defined by the IETF Deterministic Networking (DetNet) Working Group.
At DESIRE-6G, we’ve built a DetNet-based transport network that integrates Packet Replication, Elimination, and Ordering Functions (PREOF) to enhance reliability while connecting a fully deterministic environment like PREDICT-6G with the DESIRE-6G domain. This implementation is designed for the precise delivery of information, but how can we measure whether the network is performing as expected? One promising approach is to apply In-band Network Telemetry (INT), a technique that enables real-time data plane monitoring by embedding telemetry information within packets.
At Telefónica, we’ve been experimenting with this technology, and now we invite you to take part in the challenge:
Can you design a Wireshark dissector for INT headers to help advance the state of deterministic networking and contribute to the open-source community?
Join us and contribute to open networking innovation!- Related Documents
- Repositories
¶ Improving RPKI Repository Efficiency and Practices
-
Champions
- Taiji Kimura (taiji-k@nic.ad.jp)
- Wataru Ohgai (alt@nic.ad.jp)
-
Project Info
This project focuses on improving the efficiency and operational understanding of RPKI repositories, particularly in the context of RRDP (RPKI Repository Delta Protocol) object delivery.
First, we will analyze access logs from RRDP servers to determine the actual download patterns of clients—how often they downloadsnapshot.xmlversusdelta.xml. This analysis will help us assess the optimal number of delta files to retain in the repository in order to avoid unnecessary snapshot downloads, leading to more efficient bandwidth use and client synchronization.
Second, we will conduct a comparative study of RPKI repositories operated by other organizations. This includes inspecting the number of deltas and snapshots retained, repository structure, and consistency of RRDP behavior. The goal is to identify common practices and variations across implementations, which will inform operational recommendations.
Together, these efforts aim to support better-informed design and operation of RRDP-based RPKI repositories by offering both empirical data and tooling. -
Related Documents
-
Repository
-
Materials
Google Shared Drive. Please contact champions to access. -
Online Participation
Please register for the dedicated zoom call beforehand.
https://us06web.zoom.us/meeting/register/0_Ye7292SvOeUqa2NwhkXw
¶ Large Language Model Driven Automated Network Protocol Testing
-
Champions
Yong Cui (cuiyong@tsinghua.edu.cn)
Xiaohui Xie (xiexiaohui@tsinghua.edu.cn)
Yunze Wei (wyz23@mails.tsinghua.edu.cn)
Kaiwen Chi (ckw24@mails.tsinghua.edu.cn) -
Project Info
Traditional network protocol testing methods face significant challenges in adapting to rapid protocol evolution. The challenges stem primarily from protocol specification analysis and customized code development for testing. To address this, we propose NeTestLLM, a Large Language Model (LLM)-powered framework that automates protocol testing through two key components: (1) a hybrid test case generator that extracts protocol specifications and produces high-coverage test cases, and (2) a retrieval-feedback-enhanced engine that translates natural language descriptions into executable code. -
Hackathon Plan
- Apply LLM to RFC protocol comprehension, including functional modeling, field analysis, and state machine extraction.
- Leverage LLM to automatically transform protocol comprehension results into multiple test cases.
- Convert predefined test cases into executable test code and execute verification in real-world environments.
-
Draft Specification
-
Repositories
TBA
¶ Knowledge Graph–Driven Threat Intelligence Analysis and Network Configuration Generation
-
Champions
Yong Cui (cuiyong@tsinghua.edu.cn)
Mingzhe Xing (xingmz@mail.zgclab.edu.cn)
Chenguang Du (ducg@zgclab.edu.cn) -
Project Info
Traditional threat intelligence and network defense workflows are often siloed, making it difficult to achieve an automated closed loop from intelligence to protection configuration. To address this, this project develops a security-focused knowledge graph and multi-agent collaboration framework:- Knowledge Graph Construction: Build a unified knowledge graph from network device API manuals and existing threat intelligence data, enabling agents to gain deep semantic understanding of device capabilities and threat elements.
- Retrieval-Augmented Workflow Design: Design a knowledge-graph-based retrieval and augmentation pipeline so agents can dynamically fetch relevant device interfaces, policy templates, and past incident playbooks during threat analysis, improving inference accuracy.
- End-to-End Multi-Agent Collaboration: Implement a three-stage workflow—“Threat Intelligence Analysis - Configuration Intent Generation - Executable Network Configuration”—to fully automate the closed loop of network defense.
-
Hackathon Plan
- Data Ingestion & Knowledge Graph Visualization
- Intent Generation via LLM & Knowledge Graph
- Executable Configuration Command Generation
- End-to-End Demonstration & Validation
-
Draft Specification
-
Repositories
TBA
¶ Testing Privacy-preserving Ciphertext AI inference in Network Functions
-
Champions
Lun Li (lilun20@huawei.com)
Xuan Shen (skyone.beihai@gmail.com) -
Project Info
The academic community has been proposing new privacy technologies, but in existing networks, more pseudonymization is used to protect identifiers. Can these new privacy technologies enhance processing privacy?In this project, we try to let the network perform computing directly on ciphertext through privacy computing. The potential solution is to use homomorphic encryption. AI inference and neural networks are the types of computation we are primarily coped with. The main goal is as follows: -
Hackthon Plan
Test the performance of homomorphic encryption in AI inference -
Related Side Meeting
https://trello.com/c/mxsN80OT/58-1030-1200-next-generation-computing-enhancement-of-processing-privacy -
Related Drafts
https://datatracker.ietf.org/doc/draft-li-ppm-homomorphic-encryption/ -
Repositories
TBA
¶ Packet processing tracer
-
Champions
Ferenc Fejes (ferenc.fejes@ericsson.com) -
Project Info
tablesnoop is a real-time observability tool for Linux kernel table lookups. Using eBPF probes, it taps into the forwarding information base (FIB) for lookups and provides details about them. For example, it provides the source and destination addresses and the next-hop if the lookup was successful. At the moment, only IPv4 and IPv6 routing and rule lookups supported. -
Hackathon Tasks
- Extend the tool with SRv6 network programming tracing (e.g.: End behaviors, cSID visualization)
- Improve compatibility with older Linux kernel versions, distros
- GitHub CI to build and publish static binary executable
- Repository
tablesnoop: https://github.com/EricssonResearch/tablesnoop
¶ Public Interest Technology Group
-
Champions
Gurshabad Grover gurshabad@cis-india.org -
Project Info
The Public Interest Technology Group (PITG) https://pitg.network/ is a loosely organized group of individuals who self-identify as public-interest technologists, or are otherwise working on issues at the intersection of technology, rights and equity. -
Hackathon Tasks
Details coming soon!
¶ SIMap for Services provided over SRv6, relying on External Relationship models
-
Champions
- Sherif Mostafa (sherif.mostafa@huawei.com)
- Olga Havel (olga.havel@huawei.com)
- Vivekananda Boudia (vivekananda.boudia@insa-lyon.fr)
- Pierre Francois (pierre.francois@insa-lyon.fr)
- Oscar Gonzalez De Dios (oscar.gonzalezdedios@telefonica.com)
- Yannick Buchs (yannick.buchs@swisscom.com)
- Benoit Claise (benoit.claise@huawei.com)
-
Project Info
- The goal of this project is to demonstrate how operators can utilize IETF Topology YANG models to represent a real carrier IP/SRv6 network
- Using the IETF topology model to represent a carrier network based on BGP, SRV6, L3VPN, ISIS.
- Linking topological entities to external models/data using a templating approach.
- Evaluating whether RFC8345 is a suitable standard for representing multi-layered topologies for SIMap, and comparing models with and without the identified gaps.
-
Specifications
- https://www.rfc-editor.org/rfc/rfc8345
- https://www.rfc-editor.org/rfc/rfc8944
- https://www.rfc-editor.org/rfc/rfc8346
- https://datatracker.ietf.org/doc/draft-ogondio-nmop-isis-topology
- https://datatracker.ietf.org/doc/draft-ogondio-nmop-ospf-topology
- https://datatracker.ietf.org/doc/html/draft-havel-nmop-digital-map-concept
- https://datatracker.ietf.org/doc/html/draft-havel-nmop-digital-map
- https://datatracker.ietf.org/doc/draft-davis-nmop-some-refinements-to-rfc8345
- https://datatracker.ietf.org/doc/rfc9130/
- https://datatracker.ietf.org/doc/rfc9129/
- https://datatracker.ietf.org/doc/draft-vivek-simap-external-relationship/
- https://datatracker.ietf.org/doc/draft-havel-nmop-simap-yang/
-
Hackathon Plan
- In IETF122 Hackathon, we demonstrated how RFC8345 could be used to model an SRv6 enabled IS-IS network in both physical and virtual LAB environments, showcasing how to link topology to external data (such as inventory and metrics data).
- The objective for this hackathon is to improve upon that prototype by building the POC of a SIMAP for a Layer 3 VPN service provided in a SRv6 enabled core network
- Demonstrating use cases such as traversing queries and querying external data for topology entities.
-
Related Groups
- Network Management Operations (nmop)
¶ IPv6 Default Source Address Selection in Multihomed Envinronment.
-
Champions
David Lamparter, equinox@diac24.net
Jen Linkova, furry13@gmail.com -
Project Info
The goal is evaluate how different host operating systems behave in IPv6 multi-router multi-prefix network environments. We'll specifically test how hosts react to the addition and removal of routers and IPv6 prefixes on a link, focusing on their source address selection mechanism and overall adaptation to renumbering events and other topology changes.
-
Testing Plan
TBA -
Reading List
¶ CBOR Support in libyang
-
Champions
- Remote :
Siddharth Bhat (sidbhat.211ee151@nitk.edu.in)
Bharadwaja M. Chittapragada (meher.211cs216@nitk.edu.in)
Vartika T. Rao (vartikatrao.211it077@nitk.edu.in)
Hayyan Arshad (hayyanarshad.211cs222@nitk.edu.in)
- Remote :
-
Project Info
Our goal is to extend libyang, the widely used YANG data-modeling library written in C, by implementing full CBOR (Concise Binary Object Representation) support—both serialization and parsing—for YANG-modeled data.
-
Related Issue
https://github.com/CESNET/libyang/issues/2130 – feature request for CBOR support in data serializers
¶ Multipath TCP support in Linux apps
-
Champions
Matthieu Baerts (matttbe@kernel.org) -
Project Info
Multipath TCP or MPTCP is an extension to the standard TCP and is described in RFC 8684. It allows a device to make use of multiple interfaces at once to send and receive TCP packets over a single MPTCP connection. MPTCP can aggregate the bandwidth of multiple interfaces or prefer the one with the lowest latency. It also allows a fail-over if one path is down, and the traffic is seamlessly reinjected on other paths.Now that MPTCP is included in the Linux kernel, it is extremely easy to use it. Applications can support it natively (a "one line" modification), or can be forced. Some applications, mainly on the server side, even support it by default.
Fore more details, see the mptcp.dev website.
-
Specifications
-
Hackathon Plan
Add native MPTCP support in more apps. On Linux, adding native MPTCP support should be limited to the modification of thesocketsyscall. More details here.
Some applications already support MPTCP natively, see some examples. For some ideas, feel free to look at this spreadsheet: Firefox, OpenSSH, Syncthing, OpenVPN, IPerf2, etc.
Other ideas:- Add native support in some languages core net libraries, e.g. Python, Rust, etc.
- Improve some components, e.g. Path-Manager (better support the MP_CAPABLE C-flag), Packet Scheduler, socket options, etc.
¶ Benchmarking EverCBOR and EverCDDL, formally verified parsers and serializers for CBOR and CDDL
- Champions
Tahina Ramananandro (taramana@microsoft.com) - Project Info
With my colleagues Nik Swamy, Guido Martinez and Gabriel Ebner at Microsoft Research RiSE, we have recently been studying the CBOR and CDDL specifications and have produced a formal model of them, backed by formally verified executable code.
We present EverCBOR, a formally verified C and Rust implementations of CBOR, as well as EverCDDL, a formally verified parser and serializer generator from CDDL data descriptions, all proven correct for memory safety, arithmetic safety, functional correctness, non-ambiguity, and (for the deterministic subset of CBOR) non-malleability. We have used EverCDDL to produce a formally verified C and Rust implementation of COSE signing. The runtime performance of our implementation is in the ballpark of existing unverified implementations such as qcbor and tinycbor; we validate Deterministic CBOR in constant stack space.
The code and proofs are open-source and available on GitHub, along with a pre-built Docker image. Further details in the paper that we posted on arXiv, and that has just been accepted to ACM CCS 2025. - Goals
Performance benchmarking of EverCBOR
Applicability of EverCDDL to protocols using CBOR (and maybe CDDL). Examples may include but are not limited to: COSE, CWT, SCITT, IoTOPS, OSCORE, ACE, SDF,...
Performance benchmarking of parsers and serializers generated by EverCDDL
No prior formal methods background needed
¶ IPsec EESP
- Champions
Steffen Klassert (steffen.klassert@secunet.com) - Project Info
Discussion and prototyping of the EESP protocol. - Specifications
https://datatracker.ietf.org/doc/draft-klassert-ipsecme-eesp/
https://datatracker.ietf.org/doc/draft-klassert-ipsecme-eesp-ikev2/
https://datatracker.ietf.org/doc/draft-xia-ipsecme-eesp-stateless-encryption/
¶ RATS Endorsement Distribution to Verifiers with CoSERV
-
Champions
Paul Howard (paul.howard@arm.com)
Thomas Fossati (thomas.fossati@linaro.org) -
Project Info
Endorsements and Reference Values, defined in RFC9334, are essential artifacts for attestation evidence appraisal. They can originate from various sources throughout the supply chain, including silicon manufacturers, hardware integrators, firmware providers, and software providers. Their distribution is influenced by technical, commercial, and even geopolitical factors. The potential consumers of these artifacts, referred to as “Verifiers” in RATS terms, include cloud-hosted verification services, local verifiers bundled with relying parties, constrained nodes, and endpoint devices. This acute diversity creates challenges for software integration and poses fragmentation risks. Aligning on data formats and APIs will help address these challenges and maximise software component reuse for data transactions between endpoints.
This hackathon project will use components from the open-source Veraison project to demonstrate the use of CoSERV as the basis for a common endorsement distribution mechanism. -
Specifications
https://datatracker.ietf.org/doc/draft-howard-rats-coserv/
¶ AI Preferences
-
Champions
Martin Thomson (mt@lowentropy.net)
Bryan Newbold (bnewbold@robocracy.org) -
Project Info
The AIPREF working group is working on developing a grammar and expression format that will allow people to express their preferences about how AI systems use that information. These preferences can be expressed using robots.txt and HTTP headers, both in essence to ensure that the retrieval of content (or assets) can be accompanied by preferences. The focus of the hackathon session will be to validate the specification by implementing it. -
Specifications
https://datatracker.ietf.org/doc/html/draft-ietf-aipref-vocab
https://datatracker.ietf.org/doc/html/draft-ietf-aipref-attach
¶ SRv6 SFC Architecture with SR-aware Functions
-
Champions
Wataru Mishima (w.mishima@ntt.com)
Yuta Fukagawa (y.fukagawa@ntt.com) -
Project Info
Implement each component of Chapter 4 "Overview of Architecture" in "draft-watal-spring-srv6-sfc-sr-aware-functions" to achieve comprehensive management of SRv6 SFC. -
Specifications
https://datatracker.ietf.org/doc/draft-watal-spring-srv6-sfc-sr-aware-functions/02/
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-sr-service-segments/02/ -
Repository
https://github.com/nttcom/pola
https://github.com/watal/gobgp/tree/feature/bgp-ls-service-segments
¶ Updating ASPA and RTRv2 Implementation of the RTRlib and Performing ASPA Inter-Op Tests
-
Champions
Matthias Bräuer matthias.brauer@haw-hamburg.de
Tassilo Tanneberger tassilo.tanneberger@tu-dresden.de
Matthias Wählisch m.waehlisch@tu-dresden.de
Thomas Schmidt t.schmidt@haw-hamburg.de -
Project Info
ASPA (Autonomous System Provider Authorization) is a protocol proposed in the sidrops working group that enables routers to detect route leaks inside the AS_PATH of incoming BGP announcements. The RTR protocol allows to deliver ASPA data records, which are needed for verification, from a trusted relying party to a router.
The RTRlib is a C library that impelements both protocols. -
Hackathon Plan
We want to update the ASPA and RTRv2 implementation provided by the RTRlib to conform with current versions of the drafts. We also plan to perform inter-operatbility tests of the RTRlib with different RPKI cache servers such as Routinator. -
Related Documents
draft-ietf-sidrops-aspa-verification-22
draft-ietf-sidrops-8210bis-21 -
Repository
https://github.com/rtrlib/rtrlib
¶ Multipath Traffic Engineering (MPTE)
-
Champions
- Kireeti Kompella (kireeti.ietf@gmail.com)
- Vishnu Pavan Beeram (vbeeram@juniper.net)
-
Project Info
Multipath Traffic Engineering (MPTE) is a traffic engineering (TE) paradigm that combines TE with Equal/Unequal-Cost Multipath (ECMP/UCMP) load-balancing. The notions of MPTE and of an MPTE Directed Acyclic Graph (MPTED) tunnel are introduced in [draft-kompella-teas-mpte]. An MPTED tunnel is a Traffic Engineering (TE) construct that contains a constrained set of paths representing an optimized Directed Acyclic Graph (DAG) from one or more ingresses to one or more egresses. The paths that make up an MPTED tunnel traverse a set of junction nodes, and the state associated with the MPTED at each junction node constitutes a set of previous-hops and a set of next-hops over which traffic is load-balanced in a weighted fashion. Provisioning an MPTED tunnel in a TE network using a signaling protocol involves provisioning control and forwarding plane state at each junction node. An MPTED tunnel may be realized over a Multiprotocol Label Switching (MPLS) forwarding plane or a native Internet Protocol (IP) v4/v6 forwarding plane using an appropriate tunnel type. Depending on the deployment needs, a centralized or a distributed approach MAY be adopted for provisioning an MPTED tunnel.- Hackathon Goals:
- Evaluate the unique characteristics of MPTED tunnels (multiple ingresses, multiple egresses, largely pinned DAG shape, handling resource failures and congestion events)
- Evaluate the requirements of the signaling protocol.
- Evaluate RSVP signaling procedures and sequences in detail.
- Evaluate PCEP signaling procedures.
- Evaluate MPTED data model for managing MPTED tunnels and junctions (config/state).
- Evaluate different tunnel types (traditional/shared MPLS forwarding plane, Native v4/v6)
- Hackathon Goals:
-
Specifications
- https://datatracker.ietf.org/doc/draft/draft-kompella-teas-mpte/01/
- https://datatracker.ietf.org/doc/draft-kompella-lsr-mptecap/00/
- https://datatracker.ietf.org/doc/draft-kbr-teas-mptersvp/01/
- https://datatracker.ietf.org/doc/draft-beeram-pce-pcep-mpted/00/
- https://datatracker.ietf.org/doc/draft-beeram-teas-yang-mpted/00/
- https://datatracker.ietf.org/doc/draft-stone-spring-mpte-sr/00/
¶ KIRA – Scalable Zero-Touch Routing for Control Planes
-
Champions
- Roland Bless (roland.bless@kit.edu)
- Julius RĂĽberg (julius.rueberg@student.kit.edu)
-
Project Info
-
KIRA is a scalable zero-touch routing architecture that provides IPv6 connectivity without any configuration for hundreds of thousands of nodes. It is ID-based and also works well in fixed networks, data center networks, mobile ad-hoc networks, and LEO satellite networks. The prototypical implementation is written in Rust.
-
More info https://s.kit.edu/KIRA
-
-
Draft Specifications
- Internet Draft: https://datatracker.ietf.org/doc/draft-bless-rtgwg-kira/
-
Side Meeting
- Wednesday, July 23rd, 16:00–17:00h, Room Segovia, see Sidemeetings
-
Hackathon Plan (Potential Working Items)
- Testing and debugging KIRA with NEST (Connectivity Tests, Reaction to Link or Node Failures and Restoration)
- Check alignment of internal parameter values (timers etc.) with Internet-Draft defaults
- Implement wire format as defined in https://datatracker.ietf.org/doc/draft-bless-rtgwg-kira/
- Implement Wireshark Dissector for the wire format
- Improve Web Demonstrator interface (Python)
-
Technologies
- Rust
- IPv6
- Linux
- NEST / ContainerNet
- Python for the Web Demo Interface
-
Source Code Repository
- Gitlab Repository: https://gitlab.kit.edu/kit/tm/telematics/kira/kira-rust
- Github Repository is in preparation
¶ BMWG - YANG model for management of Network Tester
- Champion(s)
- Vladimir Vassilev (vladimir@lightside-instruments.com)
- Project(s)
- Specifications
- Repositories
- Scripting - YANG/NETCONF benchmark orchestration code
- Software - YANG/NETCONF device side code
- FPGA -HDL
- Hardware - board design
- Getting started - walk-through
¶ Constrained Implementation of a Packed CBOR Decoder
-
Champions
Mikolai GĂĽtschow (mikolai.guetschow@tu-dresden.de) -
Project Info
Packed CBOR is an active Internet Draft offering transformations of CBOR data items to a more size-efficient form. Compared to traditional compression techniques such as DEFLATE, the resulting "packed" CBOR item can be unpacked and decoded on the fly without a prior decompression step.
NanoCBOR is a CBOR decoder written in C and aimed at heavily constrained devices. The goal of this project is to enhance the existing PR for Packed CBOR support in order to test it's applicability even on constrained devices.
Participants interested in implementing Packed CBOR support even for other CBOR decoders are very welcome to join the project! -
Hackathon Plan
- update NanoCBOR shared reference PR from -11 to -16
- implement argument reference support in NanoCBOR
- evaluate memory consumption and benchmark processing time
-
Related Documents
https://datatracker.ietf.org/doc/draft-ietf-cbor-packed/ -
Repository
https://github.com/bergzand/NanoCBOR
¶ Implementation of DNS over CoAP (DoC)
-
Champions
Martine Lenders (martine.lenders@tu-dresden.de) -
Project Info
In Bangkok we provided a port of DoC for Unbound. The goal of the Hackathon is to get the PR for that into a mergeable state -
Hackathon Plan
- Proper integration into configuration
- Reuse TLS-PKI for DTLS
- Hunting bugs
-
Related Documents
-
Repository
https://github.com/NLnetLabs/unbound/
¶ Evaluation of Opus DRED speech codec*
-
Champions
Benson Muite <benson_muite at emailplus dot org> -
Project Info
Online evaluation of OPUS DRED through Mumble. -
Related Documents
https://datatracker.ietf.org/doc/draft-ietf-mlcodec-opus-dred/
¶ Interface to In-Network Computing Functions (I2ICF) Project
- Champion(s)
- Jaehoon Paul Jeong (pauljeong@skku.edu)
- Project(s)
- Demonstrate Interface to In-Network Computing Functions (I2ICF) Intent Translator of Intent Service Application for IoT Device (i.e., Software Defined Vehicles (SDVs)).
- Set up In-Network Computing Functions for mobile objects such as Software-Defined Vehicles (SDV) and Unmanned Aerial Vehicles (UAV) in terms of the configuration and monitoring of In-Network Functions.
- Specifications
¶ PQC DNSSEC Algorithms and Non-Existence Responses
-
Champions
Joe Harvey (jsharvey@verisign.com)
Swapneel Sheth (ssheth@verisign.com) -
Project Info
This hackathon topic continues our evaluation of post-quantum cryptography (PQC) DNSSEC by focusing on the PQC impact on three important topics:- Typical response size and frequency of request for different DNS record types.
- DNSSEC non-existence responses (NSEC/NSEC3)
- Name server implementations and measurement of new algorithms (NIST approved, other candidate algorithms, and MTL mode)
-
Draft Specifications
-
Related Groups
- PQ DNSSEC Research Side Meetings
- DNS Operations (DNSOP) Working Group
- Crypto Forum Research Group (CFRG)
- Post-Quantum Use in Protocols (PQUIP)
¶ WebTransport Interop
-
Champions
Alan Frindell / afrind@meta.com -
Project Info
Demonstrate interoperability across WebTransport implementations using the latest drafts
https://datatracker.ietf.org/group/webtrans/documents/.
See Devious Baton for a sample WebTransport application: https://www.ietf.org/archive/id/draft-frindell-webtrans-devious-baton-00.html
¶ Media over QUIC (MoQ) Interop
-
Champions
Alan Frindell / afrind@meta.com -
Project Info
Demonstrate interoperability across MoQ implementations using the latest versions of
Media over QUIC Transport (MoQT), MoQ Chat (moq-chat), MoQ Media Interop (moq-mi), MoQ Test, Low Overhead Container (LoC) and WARP.
https://datatracker.ietf.org/group/moq/documents/
¶ Tooling for SDF Instantiation and Derivation (ASDF)
-
Champion(s)
Jan Romann (jan.romann@uni-bremen.de) -
Draft Specifications
Instance Information for SDF: https://datatracker.ietf.org/doc/draft-bormann-asdf-instance-information/
SDF Mapping Files: https://datatracker.ietf.org/doc/draft-bormann-asdf-sdf-mapping/ -
Project Info
This project is dealing with two drafts that aim at extending the Semantic Definition Format (SDF) with capabilities for the description of device instances and the semantic derivation of models.
The goal is to develop open source tooling that can assist with both types of model evolution, to further discuss the two drafts listed above, and to ideally further align them with other documents from the SDF specification family and their implementations.
¶ In Loving Memory Dave Täht (1965-2025)
- Champions
Frank (Frantisek) Borsik frank@libreqos.io / frantisek.borsik@gmail.com - Project Info
Want to meet people that used to work with Dave and/or want to learn more about his work inside/outside of IETF. I plan to bring stickers - LibreQoS, Dave's latest thing, as well as his signature "This Machine Kills Vogons" and a scrap book with photos ready for anyone willing to share a thought or two, or just sign in...will be in place as well:
https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
Dave was one of the instigators of the IETF AQM and Packet Scheduling working group, and not only the co-author of RFC8290 (FQ-CoDel) and a contributor to RFC8289 (CODEL), but also RFC7567 (IETF Recommendations Regarding Active Queue Management), RFC8034 (Active Queue Management (AQM) Based on Proportional Integral Controller Enhanced (PIE) for Data-Over-Cable Service Interface Specifications (DOCSIS) Cable Modems), RFC7928 (Characterization Guidelines for Active Queue Management (AQM), RFC7806 (On Queuing, Marking, and Dropping), and RFC8033 (Proportional Integral Controller Enhanced (PIE): A Lightweight Control Scheme to Address the Bufferbloat Problem). He also made contributions to the DOCSIS 3.1 standard.
¶ Mouseworld – Knowledge Graphs for Network Digital Twins
- Champions
- Ignacio Dominguez Martinez-Casanueva (ignacio.dominguezmartinez@telefonica.com)
- Yenny Moreno Meneses (yennylisbeth.morenomeneses@telefonica.com)
- Project Info
- The Mouseworld defines a virtualization framework that emulates real networks in containerized twin networks.
- Mouseworld implements a knowledge graph that enables the creation and deployment of the network digital twin based on data retrieved from the real network.
- The implementation builds upon Semantic Web standards such as RDF, OWL and SPARQL and leverages open-source tools such as Apache Camel, Chimera, and GraphDB.
- The containerized twin network is deployed using KNE on Kubernetes.
- The proposed topology scenario runs network devices based on FRRouting (FRR).
- Work started in the context of the 6G-EDGEDT, ACROSS, and cPAID projects.
- Specifications
- Related Side Meeting
- Repositories
- Mouseworld Ontology – https://github.com/Mouseworld-Lab/mouseworld-ontology
- Mouseworld Knowledge Graph – https://github.com/Mouseworld-Lab/mouseworld-kg
¶ KEM-based Authentication for EDHOC
-
Champions
Lidia Pocero Fraile (pocero@isi.gr)
Apostolos Fournaris (fournaris@isi.gr)
Evangelos Haleplidis (haleplidis@isi.gr) -
Project Info
We will begin implementing the new Internet-Draft proposal for KEM-based authentication in EDHOC. This proposal introduces a signature-free, post-quantum secure method for authenticated key exchange using Post-Quantum Cryptography (PQC) KEMs.
Our implementation will extend the KEM-based authentication method on top of the PQ-EDHOC repository, which itself builds upon the uOSCORE-uEDHOC library to support PQC signature-based EDHOC. The C implementation targets both Linux-based high-end systems (x86 and 64-bit ARM architectures) and constrained devices based on Cortex-M4, running over the Zephyr RTOS. We aim to demonstrate end-to-end secure session establishment through EDHOC without relying on digital signatures, leveraging modern post-quantum KEMs.
-
Draft Specifications
-
Repository
https://github.com/LPFraile/PQ-EDHOC
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.