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: 01 - 02 November 2025 (Saturday - Sunday)
Where: Fairmont The Queen Elizabeth
Room: Centre Ville/Agora
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, 01 November
- 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
- 13:00 : Lunch provided
- 15:30 : Afternoon break - snacks provided
- 18:30 : Dinner provided
- 20:30 : Room closes
ΒΆ Sunday, 02 November
- 09:30 : Room opens - pastries and coffee provided
- 13:00 : 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, 03 November, Time: 19:00 - 20:00, Room: Espace 21 Gallerie
- View the schedule or reserve space for your team/project
- Reservations for space must be made by 13:00, Monday 03 November
ΒΆ Shared Workspace
- Space for groups to gather and collaborate on running code
- Monday - Friday, 03 - 07 November, Room: Rue Sherbrooke/Rue Mansfield
ΒΆ 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.
ΒΆ 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.
ΒΆ Space Networking/TIPTOP Experiment
-
Champion
Marc Blanchet <marc.blanchet@viagenie.ca> -
Objectives
Space communications have large delays (2 secs one-way delay to Moon, 4-22 mins to Mars) and intermittence (because relay orbiters going on the other side of the celestial body). The key adaptations to make to the IP stacks are (briefly, see drafts for details) - for forwarders facing intermittence, store temporarily packets instead of dropping them, when a link goes down - adjust transport and application timers. The TIPTOP working group is making group progress on specifications. The purpose of this experiment is to start trying early implementations and get experience on using applications in this environment.
- Project Info
We will be broadcasting two SSID on the hackathon wireless network: ietf-moon which will inject a 2 seconds one-way delay and ietf-mars which will inject a 4 minutes delay. Both will also see intermittence. Everybody is very welcome to participate and test the network, but make sure to follow the instructions as typical Internet applications won't work as is in this environment.
ΒΆ SCONE - Standard Communication with Network Elements
-
Champions
- Wesley Eddy (wesleyeddy@meta.com)
- Matt Joras (mjoras@meta.com)
- Marcus Ihlar (marcus.ihlar@ericsson.com)
- Zahed Sarker (zahed.sarker.ietf@gmail.com)
-
Project Info
Prototyping and testing of SCONE technology, including:- QUIC client implementations
- QUIC server implementations
- network element implementations
- applications
- tools, etc.
ΒΆ 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.
ΒΆ Identity Crisis in Attested TLS Protocols 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:
-
Proposed Readings
Technical Concepts: https://www.researchgate.net/publication/396199290_Perspicuity_of_Attestation_Mechanisms_in_Confidential_Computing_Technical_Concepts
General Approach: https://www.researchgate.net/publication/396593308_Perspicuity_of_Attestation_Mechanisms_in_Confidential_Computing_General_Approach
Validation of TLS 1.3 Key Schedule: https://www.researchgate.net/publication/396245726_Perspicuity_of_Attestation_Mechanisms_in_Confidential_Computing_Validation_of_TLS_13_Key_Schedule -
Background on Attestation
-
Background on Attested TLS
ΒΆ 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
ΒΆ KIRA β Scalable Zero-Touch Routing
-
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 at https://s.kit.edu/KIRA
-
-
Draft Specifications
Internet Draft: https://datatracker.ietf.org/doc/draft-bless-rtgwg-kira/ -
Side Meeting
- Thursday, November 6th, 14:45β15:45h, Room: McGill
- Agenda: Overview/Intro, Q&A, Discussion on next steps within IETF
- Thursday, November 6th, 14:45β15:45h, Room: McGill
-
Hackathon Plan (Potential Working Items)
- Testing and debugging KIRA with NEST (Connectivity Tests, Reaction to Link or Node Failures and Restoration)
- Creating automated tests for CI/CD pipelines
- 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
-
Remote Participation
- we will use Gather
-
Source Code Repository
- Gitlab Repository: https://gitlab.kit.edu/kit/tm/telematics/kira/kira-rust
- Github Repository is in preparation
ΒΆ AI-network: Data and Agent Aware Inference and Training Network (DA-ITN)
-
Champion
- Maryam Hosseini (maryam.hosseini3@huawei.com)
- Hesham Moussa (Hesham.moussa@huawei.com)
- Arashmid Akhavain (arashmid.akhavain@huawei.com)
-
Project Info
Artificial Intelligence (AI) is rapidly reshaping industries and daily life, driven by advances in large language models (LLMs) such as ChatGPT, Claude, Grok, and DeepSeek. These models have demonstrated the transformative potential of AI across diverse applications, from productivity tools to complex decision-making systems. However, the effectiveness and reliability of AI hinge on two foundational processes: training and inference. Each presents unique challenges related to data management, computation, connectivity, privacy, trust, security, and governance. In this project, we introduce the Data and Agent Aware-Inference and Training Network (DA-ITN) framework β a unified, intelligent, multi-plane network architecture designed to address the full spectrum of AI system requirements. The architecture features dedicated control, data, and operations & management (OAM) planes to orchestrate training, inference, and agentic services while ensuring reliability, transparency, and accountability.
In this demo, we will be showcasing the first look into a concept that we refer to as data descriptors. These are unique extractions collected from data available for training and can be used to guide the all of the AI services that the DA-ITN enables. As an exampled, we will be demonstrating how these data descriptors are used to facilitate efficient sequential training of a model across a knowledge sharing network that consists of a number of connected data nodes and an orchestrator.
- Resources
For more information on the AI-Network (DA-ITN), please refer to our submitted draft at: https://datatracker.ietf.org/doc/draft-akhavain-moussa-ai-network/
ΒΆ Secure Hybrid Network Monitoring
-
Champions
- Yutaka Oiwa (AIST, Japan), y.oiwa@aist.go.jp
-
Members
- Satoru Kanno (GMO CONNECT, Inc., Japan), kanno@gmo-connect.jp
- Yumi Sakemi (GMO CONNECT, Inc., Japan), sakemi-yumi@gmo-connect.jp
-
Project Info
We propose Secure Hybrid Network Monitoring that analyzes requirements for ensuring and monitoring the security status of the network used under complex network environment such as hybrid cloud or mixed cloud settings. -
Hackathon Work Item
- updating Internet-Drafts
- developing a PCS (Path Characteristics Service) demo
-
Relevant Drafts
-
Secure Hybrid Network Monitoring β Problem Statement
https://datatracker.ietf.org/doc/draft-oiwa-secure-hybrid-network/ -
Secure Hybrid Network Monitoring β Path Characteristics Service
https://datatracker.ietf.org/doc/draft-oiwa-path-characteristics-service/
-
ΒΆ Model Context Protocol (MCP) for Network Management
-
Champions
- YUANYUAN YANG (yangyuanyuan55@huawei.com)
- RUYI ZHANG (zhangruyi8@huawei.com)
- GUANMING ZENG (zengguanming@huawei.com)
- LEI QI (qilei1@huawei.com)
- YUN LIANG (liangyun25@huawei.com)
-
Project Info
- The Model Context Protocol (MCP) is an open protocol that provides a standardized way to connect Large Language Models (LLMs) to data sources and tools. This project investigates the application of MCP in network management to create a decoupled, agile architecture for exposing network capabilities as tools for AI agents. It enables intent-based network operations, closed-loop automation, and fosters an ecosystem for innovation by allowing third-party AI applications to interact with network functions seamlessly.
- This Hackathon project brings together MCP client and server implementations to test and demonstrate their use in network management, including network exposure and integration with existing protocols and data models. We have successfully integrated CLI with MCP, and our next phase will focus on integrating YANG interfaces.
-
Specifications
- Internet Draft: https://datatracker.ietf.org/doc/draft-yang-nmrg-mcp-nm/
- Internet Draft: https://datatracker.ietf.org/doc/draft-yang-nmrg-a2a-nm/
- Meeting Link: https://app.huawei.com/wmeeting/join/94106947/2bsMAWnt2PL8PmyJFTXu8ZfTYGS0aG5ob
- Github reference: https://github.com/Yuanyuan4666/Integration-of-MCP-and-Network-Management-Protocols/tree/main
ΒΆ Multi-modal Knowledge Graph for Network Management
- Champions
Mingzhe Xing xingmz@zgclab.edu.cn
Chenguang Du ducg@zgclab.edu.cn
Yujia Gao gaoyj@zgclab.edu.cn - Project Info
The Problem: Network management are getting more complex, coming from many different data sources and large scale networks. Traditional network management systems struggle to keep up, and while AI models like GPT are great with language, they don't understand the specific logic of network management well enough to be truly effective.
Our Hackathon Solution: We built MMKG, an intelligent defense system that acts like a network expert's brain. It connects the power of large language models (LLMs) with a structured knowledge base built specifically for understanding network requirements.
How It Works: - The "Operator Brain" (Knowledge Graph): We created a pipeline that automatically builds a unified knowledge graph from diverse textual data sources. This graph understands the relationships between different terms.
- Speaking the Language of Networks (PCAPBERT): We developed a custom AI model that translates raw network traffic data into meaningful, semantic embeddings. This allows our system to "understand" network packets in context.
- The Intelligent Reasoning Engine (KGRAG): This is the core of our project. It uses our knowledge graph to provide the LLM with accurate, structured, and causally consistent information. This supercharges the LLM, enabling it to perform complex network management tasks with high reliability.
ΒΆ Semantic Routing-Driven Secure and Scalable Multi-Agent Communication
-
Champions
Chenguang Du (ducg@zgclab.edu.cn)
Yihan Chao (chaoyh@zgclab.edu.cn)
Mingzhe Xing (xingmz@mail.zgclab.edu.cn) -
Project Info
As the number of AI agents grows quickly, new problems appear: how to find, verify, and use the right agent safely among thousands of similar ones. Todayβs task planners often use fixed agent lists, which are hard to update and can cause unsafe or incorrect tool calls.
This project builds a semantic routing middleware β an intelligent layer that connects agent intentions with the right capability endpoint using semantic understanding and safety checks.
- Semantic Routing Engine: Turns each task request into a semantic vector and searches a database of agent capabilities. It uses two steps β semantic recall and fine re-ranking β to pick the most relevant and reliable agent quickly.
- Scalable and Decoupled Architecture: Separates the task planning logic from the actual execution. The planner does not need to know all agents; it just asks the router, which returns the best endpoint and example parameters. New agents can join easily without changing the planner.
- Safety and Trust Control: Checks every agent for safety and reliability before use. The system filters out unsafe or fake agents using trust data such as capability proofs, past performance, and security ratings.
-
Hackathon Plan
- Develop public registry adapters and intent-routing APIs
- Integrate with A2A protocol frameworks
- Implement retrieval, re-ranking, and trust scoring pipelines
-
Draft Specification
ΒΆ A YANG Data Model for Multi-Statements of SCITT
-
Champions
- Nobuo AOKI n_aoki@ieee.org
-
Member
-
Project Info
We propose an extension for SCITT as an A YANG Data Model for Multi-Statements to provide integrated Supply Chain information for the computer system protection.
During the hachathon, we will solicit additional adaptable use cases and explore flexible YANG models that complement area not coverd by exisitang Supply Chain Security specifications.
However, we will take care not to impact the ongoing RFC making work for the pioneering SCITT Architecture and SCITT SCRAPI.
Upon discovering the SCITT and RATS tables, attempt to join them to facilitate consensus-building discussions. -
Hackathon Work Item
- Looking for SCITT tables in Hackathon room
- uploading revised draft version 00 w/o ToDO
- soliciting use-case
- developing a prototyping YANG schemer
-
Relevant Draft
- A YANG Data Model for Multi-Statements of SCITT (Beta)
https://github.com/aoki-n1/draft-nobuo-scitt-extension-schemer - An Architecture for Trustworthy and Transparent Digital Supply Chains
https://datatracker.ietf.org/doc/draft-ietf-scitt-architecture/ - SCITT Reference APIs
https://datatracker.ietf.org/doc/draft-ietf-scitt-scrapi/ - RFC 9472
- Hardware Bill of Materials (HBOM) Framework for Supply Chain Risk Management
https://www.cisa.gov/resources-tools/resources/hardware-bill-materials-hbom-framework-supply-chain-risk-management - Concise Reference Integrity Manifest
https://datatracker.ietf.org/doc/draft-ietf-rats-corim/
- A YANG Data Model for Multi-Statements of SCITT (Beta)
ΒΆ SCHC Context Management & Rule Usage KPI
-
Champions
- J. Alejandro FERNANDEZ javier-alejandro.fernandez@imt-atlantique.fr
- L. TOUTAIN laurent.toutain@imt-atlantique.fr
-
Project Info
The Static Context Header Compression (SCHC) mechanism is a framework that reduces protocol overhead in IoT environments, where computing resources are limited (little memory or processing power, large battery life-span constraints, ...).
As its name suggests, SCHC relies on a static shared context, or set of rules, to be able to compress and decompress network packets. This is a challenge in highly dynamic or constantly evolving network traffic.
The CORECONF (CoAP Management Interface) standard is a promising means to manage client/server resources and configurations in constrined networks.
We propose extending the SCHC framework with rule and context management capabilities through CORECONF, to make it possible to adapt SCHC rules on the fly. -
Hackathon Work Item
- SCHC + CORECONF Integration PoC
- Rule Management Scenario Demo (Sample Use-Case)
- Implementation of Rule Usage KPIs
-
Relevant Documents
- SCHC: Generic Framework for Static Context Header Compression and Fragmentation - RFC 8724.
- CoAP Management Interface (CORECONF) - draft-ietf-core-comi-20.
- CORECONF Rule management for SCHC - draft-toutain-schc-coreconf-management-01.
ΒΆ Composable Code of Things with Embedded Rust, WASM
-
Champions
- Antoine Lavandier (antoine.lavandier@inria.fr)
- Christian AmsΓΌss (christian@amsuess.com)
- Emmanuel Baccelli (emmanuel.baccelli@inria.fr)
-
Room for online participation
- see you in GatherTown or ping us via email!
-
Project Info
In the context of the recent T2TRG interim meeting on Composable Code for Things we will play around with trevm, the implementation of a set of capabilities and bindings for tiny embedded Webassembly virtual machines bolted on Ariel OS, an embedded Rust real-time operating system. -
Running Code on Ariel OS
Already available code includes examples such as a tiny wasm VM with CoAP/OSCORE server bindings, all of which runs on common boards with Cortex-M, RISC-V microcontrollers. Check it out and help us extend this base!
ΒΆ PQC in OSS
- Champions
Kavish Nadan kn@cyberstorm.mu
Loganaden Velvindron logan@cyberstorm.mu
Poshan Peeroo poshanpeeroo@cyberstorm.mu
Atish Joottun - Project Info
PQC in FOSS
ΒΆ 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 124, we plan to add more automation and others are invited to test interoperability. Also, the composite signatures recently had IANA OIDs assigned, so a number of people are interested in testing composite signatures interoperability.
ΒΆ ML-DSA and ML-KEM Composite Provider for OpenSSL
-
Champion(s)
Felipe Ventura (felipe.ventura@entrust.com)
Massimiliano Pala (massimiliano.pala@wellsfargo.com) -
Draft Specifications
https://datatracker.ietf.org/doc/draft-ietf-lamps-dilithium-certificates/
https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-sigs/
https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-kem/ -
Project Info
This project implements the emerging ML-DSA and ML-KEM composite cryptographic standards through a dedicated OpenSSL provider, enabling modular and standards-compliant support for post-quantum and hybrid digital signatures and key encapsulation mechanisms. By leveraging OpenSSL's provider architecture, the implementation ensures clean integration, extensibility, and interoperability with existing TLS and PKI infrastructures. The goal is to accelerate experimentation and adoption of composite cryptography in real-world applications, aligning with IETF efforts to future-proof secure communications against quantum threats. -
Project GitHub Repo:
https://github.com/openca/composite-provider -
Composite Provider - Microsoft Teams Meeting:
IETF - Composite Provider Collaboration
Monday, October 27, 2025
9:00 AM - 5:00 PM (EST)https://teams.live.com/meet/9338287328934?p=lTjABidDG9QMY1W3bj
At IETF 124, we plan to start this new project and use the lessons learned in previous implementations to provide a clean, easy to understand, composite cryprography implementation.
ΒΆ Remote Attestation with Exported Authenticators
-
Champions
Ionut Mihalcea ionut.mihalcea@arm.com
Thomas Fossati thomas.fossati@linaro.org -
Project Info
Deployment of Remote Attestation (RA) in the field is complicated by a lack of standard mechanisms to help combine it with existing protocols. Most notable is the lack of any widely-deployed approach to leveraging PKI and RA together to set up a secure channel. The newly minted Secure Evidence and Attestation Transport (SEAT) WG aims to standardize solutions in this space. The Remote Attestation with Exported Authenticators (draft-fossati-seat-expat) draft is meant to provide a solution for integrating RA into a TLS stack. This hackathon project deals with producing working code for draft-fossati-seat-expat. -
Hackathon goals
- Make progress on Rust implementation of the draft
-
Relevant Documents
- Remote Attestation with Exported Authenticators - draft-fossati-seat-expat
ΒΆ Validate Network Telemetry Messages Implementations
-
Champion(s)
Paolo Lucente (paolo @ pmacct.net)
Thomas Graf (thomas.graf @ swisscom.com)
Yannick Buchs (yannick.buchs @ swisscom.com)
Ahmed Elhassany (ahmed.elhassany @ swisscom.com)
Holger Keller (holger.keller @ telekom.de) -
Draft Specifications
https://datatracker.ietf.org/doc/html/draft-ietf-nmop-message-broker-telemetry-message
https://datatracker.ietf.org/doc/html/rfc8639
https://datatracker.ietf.org/doc/html/rfc8641
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-notif-envelope
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-yang-notifications-versioning -
Supporting Draft Specifications
https://datatracker.ietf.org/doc/html/draft-ietf-nmop-yang-message-broker-integration
https://datatracker.ietf.org/doc/html/draft-netana-nmop-yang-message-broker-message-key
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-distributed-notif -
Project Info
https://www.network-analytics.org/yp/
Validate Pmacct as second YANG Model for Network Telemetry Messages Implementation on the following aspects:- Message Broker Integration
- Network Telemetry Protocol Metadata
- Data Collection Manifest
- Network Operator Metadata
- YANG-Push Subscription Metadata
- YANG-Push Payload
-
Repository
https://github.com/network-analytics/ietf-network-analytics-document-status/tree/main/123/Hackathon
https://github.com/pmacct/pmacct
ΒΆ Improving RADIUS Proxy Fabrics
-
Champions
Jan-Frederik Rieckers (rieckers @ dfn.de)
Alan DeKok (alan.dekok@inkbridge.io) -
Draft Specifications
https://datatracker.ietf.org/doc/draft-ietf-radext-radiusdtls-bis/
https://datatracker.ietf.org/doc/draft-ietf-radext-status-realm/
https://datatracker.ietf.org/doc/draft-janfred-radext-radius-congestion-control/
https://datatracker.ietf.org/doc/draft-dekok-protocol-error/
https://datatracker.ietf.org/doc/draft-dekok-proxy-bcp/ -
Project Info
RADIUS has had 30 years of protocol issues. The existing specifications say that servers must discard well-formed, authentic, packets from known clients. There are no provisions for rate limiting packets. In many cases, packets are sent and never see a reply, which contributes to network instability.
We want to add some functionality (current plan is to focus primarily on Protocol-Error) to RADIUS servers (FreeRADIUS, radsecproxy, Radiator)
Implementation notes for FreeRADIUS: https://github.com/FreeRADIUS/freeradius-server/blob/v3.2.x/doc/antora/modules/developers/pages/protocol-error.adoc
ΒΆ TEEP&RATS - Secure Software Provisioning with TEEP Protocol & VERAISON
-
Champions
-
Project Info
We want to deliver mature ecosystem implementations of the Trusted Execution Environment Provisioning (TEEP) Protocol for distributing WasmApp as Trusted Applications, leveraging VERAISON as a Verifier for the Trusted Application Manager (TAM). -
Goals
- Deploy a WasmApp to the latest and genuine WasmRuntime inside a TEE
- The TAM can dynamically trust the key of TEEP Agent, a managing program inside the TEE, only if the Evidence is affirmed by the Verifier
- The Verifier can appraise the Evidence against Reference Value, e.g. the digest of the TEE programs, ensuring that the WasmRuntime and TEEP Agent is not modified nor out dated
-
Related RFCs and Internet Drafts
- Entity Attestation Token (EAT): https://datatracker.ietf.org/doc/rfc9711/
- EAT Measured Component: https://datatracker.ietf.org/doc/draft-ietf-rats-eat-measured-component/
- Arm's Platform Security Architecture (PSA) Attestation Token: https://datatracker.ietf.org/doc/rfc9783/
- Concise Reference Integrity Manifest: https://datatracker.ietf.org/doc/draft-ietf-rats-corim/
- EAT Attestation Results: https://datatracker.ietf.org/doc/draft-ietf-rats-ear/
- Trusted Execution Environment Provisioning (TEEP) Protocol: https://datatracker.ietf.org/doc/draft-ietf-teep-protocol/
- A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest: https://datatracker.ietf.org/doc/draft-ietf-suit-manifest/
ΒΆ DKIM2
-
Champions
- Allen Robinson (arobins@google.com)
- Bron Gondwana (brong@fastmailteam.com)
- John Levine (johnl@taugh.com)
- Richard Clayton (richard@highwayman.com) [Remote]
- Wei Chuang (weihaw@google.com) [Remote]
-
Project Info
To build multiple DKIM2 implementations creating and validating signatures on flat file messages shared through the Github repository. Weβve decided that SMTP transaction support is out of scope for this first hackathon activity. We hope to have a small handful of common scenarios to cover during testing. The goal is to just validate assumptions being made in the design phase and try to surface any gaps.
-
Participation Details
- Chatroom: https://zulip.ietf.org/#narrow/channel/366-dkim/topic/ietf-124-hackathon/
- Video / Voice: https://meet.google.com/sbv-rjxh-vaq
- GitHub Repo: https://github.com/dkim2wg/interop
-
Project Files
Code and samples at https://github.com/dkim2wg/interop
ΒΆ Testing Congestion Control and Queue Management Mechanisms
-
Champions
- Mohit P. Tahiliani (tahiliani@nitk.edu.in) [Remote]
- Vishal Kamath (vishalkamath.221cs261@nitk.edu.in)
- Hemang J. Jamadagni (hemangj.221cs129@nitk.edu.in)
- Tanay Praveen Shekokar (tanayshekokar.221cs159@nitk.edu.in)
- Monika Gautam (monikagautam.242cs024@nitk.edu.in) [Remote]
- Arun Kumar Rajaraman (arunkumarr.242cs011@nitk.edu.in) [Remote]
- Ayush Nigam (ayushnigam.242cs012@nitk.edu.in) [Remote]
- Jayesh Akot (jayesh.242cs007@nitk.edu.in) [Remote]
-
Project Info
-
Related documents
-
Repositories
ΒΆ 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/02/
- https://datatracker.ietf.org/doc/draft-beeram-pce-pcep-mpted/00/
- https://datatracker.ietf.org/doc/draft-beeram-teas-yang-mpted/01/
- https://datatracker.ietf.org/doc/draft-stone-spring-mpte-sr/01/
ΒΆ Interface to In-Network Computing Functions (I2ICF) Project
-
Champion(s)
- Jaehoon Paul Jeong (pauljeong@skku.edu)
-
Project(s)
- The Interface to In-Network Computing Functions (I2ICF) aims to establish a framework and a set of interfaces that enable users in the cloud to configure and monitor mobile entities such as robotic AI agents and other moving objects.
- Demonstrate the I2ICF Intent Translator, a component of the Intent Service Application, which interprets user intents for IoT devices, including Software-Defined Vehicles (SDVs).
- Set up deploying In-Network Computing Functions (ICFs) for mobile platforms such as Software Defined Vehicle (SDVs) and Unmanned Aerial Vehicles (UAVs), focusing on the configuration, operation, and monitoring of these In-Network functions.
-
Specifications
- [draft-jeong-nmrg-i2icf-problem-statement-00]
(https://datatracker.ietf.org/doc/draft-jeong-nmrg-i2icf-problem-statement/) - [draft-jeong-nmrg-i2icf-framework-00]
(https://datatracker.ietf.org/doc/draft-jeong-nmrg-i2icf-framework/) - [draft-an-nmrg-i2icf-cits-00]
(https://datatracker.ietf.org/doc/draft-an-nmrg-i2icf-cits/) - [draft-gu-nmrg-intent-translator-02]
(https://datatracker.ietf.org/doc/draft-gu-nmrg-intent-translator/)
- [draft-jeong-nmrg-i2icf-problem-statement-00]
ΒΆ An Integrated Security Service System for 5G Networks using an I2NSF Framework
-
Champion(s)
- Jaehoon Paul Jeong (pauljeong@skku.edu)
-
Project(s)
- This project presents an integrated framework for automated security management in 5G edge networks using the Interface to Network Security Functions (I2NSF) architecture.
- The proposed system leverages Intent-Based Networking (IBN) to allow users or administrators to declare high-level security intents, which are translated into enforceable network and application policies. Network-level policies are delivered to 5G core components via the Network Exposure Function (NEF), while application-level policies are enforced directly on a User Equipment (UE) through distributed IBN Controllers.
- This architecture supports adaptive, context-aware, and distributed policy enforcement, enabling real-time response to dynamic edge conditions and user mobility scenarios such as handovers.
-
Specifications
ΒΆ PacketScope: LLM-Powered eBPF for Protocol Stack Defense
-
Champions
- Zhaoxi Li (li-zx24@mails.tsinghua.edu.cn)
- Yuxiang Yang (yangyx22@mails.tsinghua.edu.cn)
-
Project Info
PacketScope is a general-purpose protocol stack analysis and debugging tool based on eBPF. It integrates performance optimization, anomaly diagnosis, and security defense to provide fine-grained tracing and intelligent analysis of network packets at the protocol stack level. The project aims to solve common pain points such as difficult diagnosis of performance bottlenecks, unclear packet transmission paths, and hard-to-detect low-level protocol attacks (e.g., at layers below traditional WAF/IDS).The tool consists of three main microservice modules:
- Analyzer: Provides multidimensional statistics on packet movement (latency, packet loss, etc.) and visualizes cross-layer data flow.
- Tracer: Maps network routes and latency from the host to any global IP, visualizing the data on a global topology.
- Guarder: Filters and controls abnormal packets using customizable rules and leverages an intelligent engine (LLM) to provide context for potential threats.
-
Hackathon Goals
- Deploy PacketScope in the IETF hackathon network testbed to monitor and analyze live traffic.
- Evaluate and enhance the
Guardermodule's rule-based engine for detecting and mitigating low-level protocol attacks and anomalies. - Test the
Analyzermodule's ability to identify performance bottlenecks and trace packet paths within complex network topologies. - Explore potential integrations between PacketScope's eBPF-based telemetry and other network management or security tools.
- Develop and test new eBPF probes for tracing interactions with specific protocols being discussed at the IETF.
- Gather feedback on the tool's usability and visualization for network operators and security engineers.
GitHub Repo: https://github.com/Internet-Architecture-and-Security/PacketScope
Project Docs: https://internet-architecture-and-security.github.io/packetScope-website/
Live Demo: http://82.156.141.213:4173/ -
Specifications
- Problem Statement for Cross-Layer Vulnerabilities due to Forged ICMP Errors (https://datatracker.ietf.org/doc/draft-xu-intarea-vulnerabilities-forged-icmp/)
- Enhancing ICMP Error Message Authentication Using Challenge-Confirm Mechanism (https://datatracker.ietf.org/doc/draft-xu-intarea-challenge-icmpv4/)
- Enhancing ICMPv6 Error Message Authentication Using Challenge-Confirm Mechanism (https://datatracker.ietf.org/doc/draft-xu-intarea-challenge-icmpv6/)
ΒΆ IPsec EESP
-
Champions
- Steffen Klassert (steffen.klassert@secunet.com)
-
Project Info
- Prototyping and testing of the Linux implementation of the EESP protocol.
-
Specifications
ΒΆ 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@everything-ops.net)
- Project Info
The goal of this project is to demonstrate how operators can utilize IETF Topology YANG models to represent a real carrier network based on BGP, SRV6, L3VPN, ISIS, and also how to take advantage of this modeling, for example, compute the path of a packet.
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 path, 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/rfc9130/
https://datatracker.ietf.org/doc/rfc9129/
https://datatracker.ietf.org/doc/draft-ietf-nmop-simap-concept/
https://datatracker.ietf.org/doc/draft-havel-nmop-simap-yang/
https://datatracker.ietf.org/doc/draft-vivek-simap-external-relationship/ -
Hackathon Plan
During the IETF123 Hackathon we demonstrated how RFC 8345 can be used to model a Layer-3 VPN service running over an SRv6-enabled core within a virtual lab environment, and how to link the SIMAP to external sources (e.g., inventory and metrics).
The objective of this hackathon is to exploit the SIMAP to run βwhat-ifβ scenarios: compute packet paths before and after link failures, and represent those paths using RFC 8345. -
Related Groups
Network Management Operations (nmop)
ΒΆ Rocca-S in parallel mode
- Champions
Yuto Nakano - Project Info
The goal of this project is to implement Rocca-S in parallel and evaluate its performance. Rocca-S is an authenticated encryption with associated data (AEAD) algorithm designed for high performance applications. By implementing in parallel, even higher performance can be expected. We will try to find out how fast Rocca-S can perform in parallel. - Related Draft
Encryption algorithm Rocca-S
https://datatracker.ietf.org/doc/draft-nakano-rocca-s/
ΒΆ PQC DNSSEC MTL Mode Updates to add support for ML DSA
-
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. The original specification for MTL mode provided support for SLH-DSA underlying signatures. The latest version 08 of draft-harvey-cfrg-mtl-mode updates the hash function constructions and underlying signature bindings to also add support for ML-DSA. This update was based on community feedback and a desire to offer better crypto agility when using MTL mode. This hackathon will look at:- Test interoperability between open-source resolvers with both algorithms.
- Look at the performance for each algorithm relative to the other when leveraging MTL Mode.
-
Draft Specifications
[1] https://datatracker.ietf.org/doc/draft-harvey-cfrg-mtl-mode/
[2] https://datatracker.ietf.org/doc/draft-harvey-cfrg-mtl-mode-considerations/
[3] https://datatracker.ietf.org/doc/draft-fregly-dnsop-slh-dsa-mtl-dnssec/ -
Related Groups
PQ DNSSEC Research Side Meetings
DNS Operations (DNSOP) Working Group
Crypto Forum Research Group (CFRG)
Post-Quantum Use in Protocols (PQUIP)
ΒΆ YANG Provenance Signatures Integrated with the Kafka Schema Registry
-
Champions
Diego Lopez diego.r.lopez@telefonica.com
Ana Mendez ana.mendezperez@telefonica.com
Lucia Cabanillas lucia.cabanillasrodriguez@telefonica.com -
Project Info
This topic will demonstrate how the YANG provenance signature module already presented at previous IETF hackathons can be integrated with the Kafka YANG Schema Registry project, supporting:
- Augment patterns for extending any valid YANG module
- Schema-based management of provenance signature elements
- Direct integration with message flows using Kafka
Besides this, the improved signing and verification methods, without requiring Kafka or its registry, will also be demonstrated.
Interested participants are welcome to bring their YANG modules and discuss how to apply provenance signatures
-
Draft Specifications
https://datatracker.ietf.org/doc/draft-ietf-opsawg-yang-provenance/
https://datatracker.ietf.org/doc/draft-ietf-nmop-yang-message-broker-integration/ -
Related Groups
Operations and Management Area Working Group (opsawg)
Network Management Operations (nmop)
ΒΆ Knowledge Graphs For Network Operations
- Champions
Michael Mackey michael.mackey@huawei.com
Bohdan Yeriemienko bohdan.yeriemienko@huawei.com
Lionel Tailhardat lionel.tailhardat@orange.com
FOLZ Pauline pauline.folz@orange.com
Beyza Yaman beyza.yaman@adaptcentre.ie
This project will demonstrate how existing IETF YANG Models and related instance data can be quickly converted into a Knowledge Graph. By using Semnatic Web Technologies, these models and data can easily be intergrated or extened with external ontologies to enhance the information present and allow graph queries across the data to find deep insights.
Specifically it will show how the draft SIMAP YANG model can be represented in RDFS and how it can be integrated with an external wider Ontology (represented by NORIA-O).
- Draft Specifications
https://datatracker.ietf.org/doc/draft-mackey-nmop-kg-for-netops/
https://datatracker.ietf.org/doc/draft-marcas-nmop-kg-construct/
https://datatracker.ietf.org/doc/draft-tailhardat-nmop-incident-management-noria/
ΒΆ SRv6 SFC Architecture with SR-aware Functions
- Champions
Wataru Mishima (mishima@nw.kanagawa-it.ac.jp)
Taisei Tanabe (tanabe@nii.ac.jp)
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/03/
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-sr-service-segments/02/
ΒΆ DNS - DELEG implementation
- Champions
Petr Ε paΔek, pspacek@isc.org - Project Info
Move forward DELEG implementation in authoritative DNS servers and resolvers of your choice. Find holes in draft https://datatracker.ietf.org/doc/draft-ietf-deleg/ and provide WG with implementation feedback.
ΒΆ vCon
-
Champions
- Dan Petrie (dan.ietf@sipez.com)
-
Project Info
WG: vCon
I-D: vCon core
Repos:
One of the primary goals of vCon is to ease and standardize the integration and data transfer of conversational data between enterprise or contact center:
-
Communications systems (email, sms, web chate, voice and video calls)
-
Data consumer or customer data platform
-
AI, ML and algorithmic analysis services, model training and testing
-
CRM systems
-
Hackathon Objective
The goal for this hackathon is to implement and test portions of the vCon I-D that have not been well tested. The group features, transfer type dialog object and single channel per party recordings for multiple parties in a call fir vCon have not been fully implemented or tested.
-
Hackathon Work Items
-
Implement SIP Session ID Object
-
Implement transfer type dialog object
-
Test support for dialogs with separate recording file for each party
-
Implement recording dialog update (hash, duration, URL, mediatype, file)
-
Implement group vCon and generate example for the vCon Container I-D
-
Implement group method
-
Implement group processor
-
ΒΆ SDF: Implementation of Instance-Related Drafts
- Champions
Jan Romann, jan.romann@uni-bremen.de - Project Info
Over the course of the last interim and design team meetings, two drafts within the ASDF working group that deal with instance-related information about IoT devices (in addition to SDF models which only contain class-level information) have come closer to convergence.
This project will work on experimental implementations of the two drafts and evaluate the latest approaches discussed in the Working Group, investigating how well-suited the new design already is and which limitations may still exist. In this context, we will work on experimental tooling and an ESP32-based prototype that will be described via the new instance-related message formats that emerged in the two drafts.
- Related Internet-Drafts
ΒΆ 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
ΒΆ QUANTUM
- Champions
Rod Van Meter rdv@sfc.wide.ad.jp
Monet "bob" Tokuyama Friedrich bob@sfc.wide.ad.jp - Project Info
Working on network specifications for a network that distributes quantum entanglement.
ΒΆ IPv6 Web Resource checker
- Champions
Philipp S. Tiesel philipp.tiesel@sap.com - Project Info
The IPv6 Web Resource Chceker (webres6) is a small tool/api to checks IPv6-only readiness of a Web page or app. It loads a given URL using Selenium and displays the IP addresses and protocols of all hosts it fetches resources from and comes with a CLI and Web client.
We plan to "release" this tool at the end of the IETF Hackahon: https://github.com/sap/webres6
A demo is available at https://webres6.dev.sap/
ΒΆ Authenticated Transfer (AT) Sync Tooling
- Champions
Bryan Newbold bnewbold@robocracy.org - Project Info
Authenticated Transfer (AT) is a framework for distributing content-addressed social web data (there is a BoF on Wednesday morning). A number of developers from the AT ecosystem will be in Montreal on Sunday (not Saturday), hacking on various projects. One project will be a new open source "sync channel" service, which helps services with bootstraping existing data of a given type from the network, and then keeping up to date with live updates, in particular helping with the "cutover" between bulk indexing to live updates.
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.