¶ IETF 121 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: 02 - 03 November 2024 (Saturday - Sunday)
Where: The Convention Centre Dublin (CCD)
Room: The Liffey B
| Gold Running Code Sponsor | Silver Running Code Sponsor | Bronze Running Code Sponsor |
|---|---|---|
 |
 |
 |
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)
¶ Saturday, 02 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
- 12:30 : Lunch provided
- 15:30 : Afternoon break - snacks provided
- 18:30 : Dinner provided
- 20:30 : Room closes
¶ Sunday, 03 November
- 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, 04 November, Time: 19:00 - 20:00, Room: Ground Floor Foyer
- View the schedule or reserve space for your team/project
- Reservations for space must be made by 13:00, Monday 04 November
¶ Shared Workspace
- Space for groups to gather and collaborate on running code
- Monday - Friday, 04 - 08 November, Room: Liffey Meeting Room 1
- 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.
- Please use the Powerpoint Template
- 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.
¶ 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 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.
For this Hackathon event, the goal is to introduce people to Thread and OpenThread programming. This Hackathon event is open to all — Thread Group membership is not required, though of course Thread Group members are also welcome to participate. If you plan to participate in the Thread work at the Hackathon (on-site or remotely), please add your name to the participant list. If you already have a Thread developer board and the OpenThread build environment on your laptop, please bring that. If not, we will have a few extra Thread developer boards available and we can help you get the build environment set up. For people totally new to Thread development, we have some recommendations from Allie Clifford and Ann Olivo.
We have a list of some project ideas. Other ideas are welcome and encouraged. Please feel free to add suggestions to the project list. -
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.
¶ Identifier Locator Network Protocol (ILNP)
-
Champions
- Saleem Bhatti saleem@st-andrews.ac.uk
- Rodney Grimes rgrimes@freebsd.org
- Alistair Woodman awoodman@netdef.org
-
Participants
- Gregor Haywood (remote) gh66@st-andrews.ac.uk
- Ryo Yanagida ryo@htonl.net
-
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.
¶ CoAP Group Communication with Group OSCORE
-
Champions
-
Project Info
- Message exchange of group and pairwise messages protected with Group OSCORE
-
Specifications
¶ application/dns+cbor Updates
- Champions
- Martine Lenders (martine.lenders@tu-dresden.de)
- Project Info
- Update cbor4dns to newest draft version
- More implementations welcome!
- Specifications
¶ SW103K and Havi Expansion Protocols
Champions
Chazah Group (chief3@chazahgroup.org)
Project Info
The SW103K project is a cutting-edge compression and decompression protocol designed to enhance data transmission efficiency in high-throughput networking environments. By leveraging advanced algorithms, SW103K reduces data packet sizes while maintaining optimal speed and security, making it ideal for applications that handle large volumes of data, such as cloud services, streaming, and data centers. The protocol adapts dynamically to fluctuating network conditions, maximizing bandwidth utilization and minimizing latency, while ensuring data integrity during transmission. The project has been submitted as an Internet-Draft to the IETF to foster collaboration, testing, and adoption within various networking infrastructures, with a focus on scalability, reliability, and security in modern data transport systems.
specification:
URL: https://www.ietf.org/archive/id/draft-rfcxml-rfc-swl-103k-02.txt
Status: https://datatracker.ietf.org/doc/draft-rfcxml-rfc-swl-103k/
HTML: https://www.ietf.org/archive/id/draft-rfcxml-rfc-swl-103k-02.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-rfcxml-rfc-swl-103k
Diff: https://author-tools.ietf.org/iddiff?url2=draft-rfcxml-rfc-swl-103k-02
Repositories
Github repo: https://github.com/chazahgroup/expansion
¶ Key Update for OSCORE using KUDOS
-
Champions
-
Project Info
- Performing key update for OSCORE using the KUDOS procedure
-
Specifications
¶ EDHOC
- Champion(s)
- Marco Tiloca (marco.tiloca at ri.se)
- Project Info
- Establish keying material for OSCORE using the EDHOC protocol
- Specifications:
¶ EDHOC and OSCORE Profile of the ACE Framework
- Champion(s)
- Marco Tiloca (marco.tiloca at ri.se)
- Project Info
- Use the ACE access control framework combined with the EDHOC protocol for mutual authentication and establishment of keying material for OSCORE
- Specifications:
¶ lakers implementation of EDHOC, ELA, and remote attestation
- Champion(s)
- Geovane Fedrecheski (geovane.fedrecheski at inria.fr)
- Project Info
- lakers is an implementation of EDHOC in Rust, optimized for microcontrollers, with bindings for C and Python. It also includes an implementation of ELA (lake-authz), and the edhoc-psk draft.
- plans for the hackathon include:
- pure Rust crypto backend for CryptoCell 310
- CI task to measure and report memory usage
- EDHOC error messages
- support for message_4
- remote attestation over EDHOC
- updates to the implementation of ELA
- interoperability tests
- Specifications:
¶ Formal Analysis of 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 (Sec. 4 in this draft)
- 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
- Tutorial slides from side meeting of IETF 120
- Some slides and videos at this repo, such as this.
¶ RATS Conceptual Message Wrappers
-
Champions
- Ionut Mihalcea (ionut.mihalcea at arm.com)
- Thomas Fossati (thomas.fossati at linaro.org)
-
Project Info
- Implementation of the RATS Conceptual Message Wrappers draft
-
Specification
¶ Post-Quantum Cryptography (PQC) in X.509, Signatures, KEMs, and protocols
-
Champion(s)
John Gray (john.gray@entrust.com)
Mike Ounsworth (mike.ounsworth@entrust.com)
Julien Prat (julien.prat@cryptonext-security.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-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://datatracker.ietf.org/doc/draft-ietf-lamps-cert-binding-for-multi-auth/01/
https://www.ietf.org/id/draft-lamps-okubo-certdiscovery-00.html
https://datatracker.ietf.org/doc/draft-bonnell-lamps-chameleon-certs/
https://datatracker.ietf.org/doc/draft-gazdag-x509-hash-sigs/ -
Project Info
Purpose is to make use of PQ in real world X.509 structures like keys, signatures, certificates and protocols. This will allow us to test interoperability between different algorithm implementations, gain experience using these new algorithms, and provide feedback to the standards groups about practical usage in the real world.
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 121, we plan to update the artifact repository to support the FIPS 203, 204 and 205 algorithm standards as well as updates to the Certificate Mechanisms for transitioning to PQ.
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.).
¶ Protocols for Quantum Key Distribution Networks (QKDN)
- Champions
- Internet Draft
- Project Info
- A first attempt to define and implement protocols for control and management of QDKNs, i.e., between two adjacent Key Management Systems (KMS) and between a network controller and the KMS.
¶ Roughtime
- Champions
- Marcus Dansarie (marcus at dansarie.se)
- Project Info
- Document interoperability of Roughtime implementations
- Update Roughtime implementations for interoperatbility and compatibility with the latest draft
¶ IETF TE Topology Graphical Display
- Champions
Henry Yu (hyu2010b@gmail.com) - Project Info
- This project develops a toolkit which includes YANG datastore, GUI of YANG data, and RESTCONF server with Swagger interface.
- We use this toolkit to demonstrate some key aspects of the IETF TE topology model (RFC8795), such as bidirectional links and link hierarchy.
- Specification
¶ Low-Latency, Low-Loss, Scalable Throughput (L4S) and Accurate ECN Interop
-
Champions
Greg White (g.white at 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.
- As has been the case at several previous IETFs, the intent is to begin work during the Hackathon, and then continue in a nearby room for the rest of the week.
-
Specifications
¶ 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
¶ Implement GoBGP BGP-LS Extensions for SRv6 Service Chaining
- Champion(s)
- Yuta Fukagawa (y.fukagawa@ntt.com)
- Project Info
- Implement GoBGP BGP-LS Extensions for SRv6 Service Chaining
- Specifications
- Repositories
¶ Interface to In-Network Functions (I2INF) Project
- Champion(s)
- Jaehoon Paul Jeong (pauljeong@skku.edu)
- Project(s)
- Demonstrate Interface to In-Network Functions (I2INF) Intent Translator of Intent Service Application for IoT Device.
- 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
¶ Congestion control testing
- Champions
- Reese Enghardt (ietf@tenghardt.net)
- Related Groups
- Project Info
- Build tooling and test congestion control algorithms and other related proposals, including those discussed in CCWG, ICCRG, or TSVWG
- Potential project ideas:
- Test congestion control proposals in simulated or emulated environments or in the field
- Refine tooling such as the ns-3 simulator to support congestion control testing better
- Design a suite of test cases based on 5033bis, the proposed new BCP on Specifying New Congestion Control Algorithms
¶ Validate BMP Extension for Path Status TLV
-
Champion(s)
Paolo Lucente (paolo @ pmacct.net)
Maxence Younsi (maxence.younsi @ insa-lyon.fr)
Yannick Buchs (yannick.buchs @ swisscom.com)
Thomas Graf (thomas.graf @ swisscom.com)
Daniel Voyer (daniel.voyer @ bell.ca) -
Draft Specifications
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-path-marking-tlv -
Project Info
Validate BMP Extension for Path Status TLV implementation in frrouting, Wireshark dissector and pmacct. -
Repository
https://github.com/mxyns/frr/tree/bmp-draft-path-marking
https://github.com/network-analytics/wireshark/tree/draft-cppy-grow-bmp-path-marking-tlv
https://github.com/pmacct/pmacct
¶ Validate Configured Subscription YANG-Push Publisher Implementations
-
Champion(s)
Thomas Graf (thomas.graf @ swisscom.com)
Yannick Buchs (yannick.buchs @ swisscom.com)
Daniel Voyer (daniel.voyer @ bell.ca)
Holger Keller (holger.keller @ telekom.de)
Rob Wilton (rwilton @ cisco.com) -
Draft Specifications
https://datatracker.ietf.org/doc/html/rfc8639
https://datatracker.ietf.org/doc/html/rfc8641
https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang
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-tgraf-netconf-notif-sequencing
https://datatracker.ietf.org/doc/html/draft-ietf-netconf-yang-notifications-versioning
https://datatracker.ietf.org/doc/html/draft-tgraf-netconf-yang-push-observation-time -
Project Info
Validate three YANG-Push configured subscription vendor implementations in terms of configuring periodical and on-change subscriptions and validating subscription state change and push-update and push-change-update notifications according to RFC 8639 and 8641.
Validate draft-ietf-netconf-udp-notif and draft-ietf-netconf-distributed-notif packet format on the wire.
Validate first YANG-Push extensions enabling Apache Kafka integration according to draft-ietf-nmop-yang-kafka-integration.
- Repository
https://github.com/network-analytics/ietf-network-analytics-document-status/tree/main/121/Hackathon
¶ YANG-Push to Message Broker Integration
-
Champion(s)
Ahmed Elhassany (ahmed.elhassany at swisscom.com)
Alex Huang-Feng (alex.huang-feng at insa-lyon.fr) -
Draft Specifications
https://datatracker.ietf.org/doc/html/draft-ietf-nmop-yang-kafka-integration
https://datatracker.ietf.org/doc/html/draft-aelhassany-anydata-validation -
Project Info
draft-aelhassany-anydata-validation implemented in YANG schema registry and message broker YANG data producer and consumer. -
Repository
¶ Implement find relationship solution with Augmented-by list in ietf-yang-library
-
Champion(s)
Zhuoyao Lin (zhuoyao.lin1 @ huawei-partners.com)
Benoit Claise (benoit.claise @ huawei.com) -
Draft Specifications
https://datatracker.ietf.org/doc/draft-lincla-netconf-yang-library-augmentedby/ -
Project Info
Validate based on draft-ietf-netconf-yang-notifications-versioning that with draft-lincla-netconf-yang-library-augmentedby all datastore-subtree-filter or datastore-xpath-filter referenced YANG modules and their dependencies can be fully identified. -
Repository
https://github.com/network-analytics/libyangpush
https://github.com/Zephyre777/draft-lincla-netconf-yang-library-augmentation.git
¶ Antagonist (ANomaly TAGging ON hISTorical data)
- Champions
- Vincenzo Riccobene (vincenzo.riccobene@huawei-partners.com)
- Wanting (Wanting.Du@swisscom.com)
- Project Info
Antagonist is a tool supporting the tagging of historical timeseries data. This is envisioned to support Network Anomaly Detection and it is created with the purpose of supporting network operators tagging their data with network anomaly related metadata. - Hackathon plan
Antagonist currently exists as a PoC. The objective for this hackathon is to improve the system design, extend the validation of the models defined in the drafts below, and showcase integration with third parties components. - Specifications
- Repositories
Github repo: https://github.com/vriccobene/antagonist
¶ Automatic DNS Delegation Synchronization Using DNS UPDATE
- Champions
- Johan Stenstam (johan.stenstam@internetstiftelsen.se)
- Project Info
Add new functionality to a working open source nameserver implementation (called "TDNS", written in Go) to
provide fully automatic management of delegation information between child zones (both
DNSSEC-signed and unsigned) and parent zones.
This time we will look at implementing a new EDNS(0) option called KeyState (see the keystate draft below) which will be used to augment the communication between child and parent to allow more detailed expression of the state of the SIG(0) keys used for signing and validating DNS UPDATEs.
This is a continuation of the work we did during the IETF 119 and 120 Hackathons.
Detailed project suggestions: https://github.com/johanix/hackathon121/
-
Specifications
-
Repositories
Github repo for the code we will use as a starting point: (https://github.com/johanix/tdns)
¶ NIPC in ASDF
- Champions
- Bart Brinckman bbrinckm@cisco.com
- Ari Keränen ari.keranen@ericsson.com
- Project Info
- NIPC in SDF: Work on NIPC integration in SDF: Specify how NIPC integrates into SDF, create a few sample models, build a library/sample app that ingests a SDF model with NIPC integration.
- Specifications
- Repositories
¶ SCHC Interoperability
- Champions
- Javier Alejandro Fernandez (javier-alejandro.fernandez@imt-atlantique.fr)
- Project Info
"SCHC Interoperability" addresses the current challenges between three SCHC protocol implementations: OpenSCHC in Python, cSCHC in C, and the recently open-sourced Lab.SCHC FullSDK for embedded devices. Interoperability issues exist due to missing features in OpenSCHC and differences in rule formats. This hackathon project aims to implement the missing features and develop tools to ensure seamless operation between implementations, enabling cross-platform compatibility and facilitating the adoption of SCHC-based IoT networks. - Specifications
- Repositories
¶ Experiments with MTL Mode in Recursive Resolvers
-
Champions
- Joe Harvey (jsharvey@verisign.com)
- Swapneel Sheth (ssheth@verisign.com)
- Willem Toorop (willem@nlnetlabs.nl)
-
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/ -
Project Info
Following-up from the IETF-120 Hackathon “Exploring Implementation Approaches for Merkle Tree Ladder Mode Signatures for DNSSEC” [4], we would like to do interoperability experiments with MTL Mode [1] validation at the recursive resolver using the “request / retry” or “flag” approach in the MTL considerations draft [2]. This will be initially expressed as the SOA lookup approach in the appendix of the MTL DNSSEC draft [3] while we work towards the full EDNS option implementation from the draft. This configuration allows us to validate our initial assumptions on the average endurance [5] of a reference value that would be sent to a requester in MTL mode and the query/response sizes. We would also like to collect further feedback from the resolver community and setup for additional proof-of-concept implementations in other code bases and collect overall operational experience.
[4] https://wiki.ietf.org/en/meeting/120/hackathon
[5] https://eprint.iacr.org/2022/1730.pdf -
Related Groups
- DNS Operations (DNSOP) Working Group
- Crypto Forum Research Group (CFRG)
¶ NTPv5
-
Champions
- Karen O’Donoghue (kodonog@pobox.com)
- Dieter Sibold (dsibold.ietf@gmail.com)
-
Project Info
- Interoperability testing between different NTPv5 implementations.
-
Specifications
-
Repositories
- NTPD-RS: https://github.com/pendulum-project/ntpd-rs
- NTPv5-EXP: https://github.com/mlichvar/ntp5-exp
¶ Multipath QUIC Interop testing
- Champions
Magnus Westerlund (magnus.westerlund@ericsson.com) - Project Info
Interop testing of Multipath QUIC implementations - see https://github.com/quicwg/multipath/wiki/Implementation-Draft-Interop
¶ Digital Map for ISIS and OSPF
-
Champions
- Sherif Mostafa (sherif.mostafa@huawei.com)
- Olga Havel (olga.havel@huawei.com)
- Vivekananda Boudia (vivekananda.boudia@insa-lyon.fr)
- Oscar Gonzalez De Dios (oscar.gonzalezdedios@telefonica.com)
- Yannick Buchs (yannick.buchs@swisscom.com)
- Daniel Voyer (daniel.voyer@bell.ca)
- Benoit Claise (benoit.claise@huawei.com)
- Pierre Francois (pierre.francois@insa-lyon.fr)
-
Project Info
- The goal is to demonstrate how operators can use the IETF Topology Yang models to represent a real carrier IP/MPLS network.
- We start with one particular problem space: How to use IETF topology model to represent a real carrier network based on IS-IS and OSPF domains for planning/simulation purposes.
- We want to demonstrate if RFC8345 is the suitable standard for representing the multi-layered topology for Digital Map and show the models comparison 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/
-
Hackathon plan
- The project has started at IETF120 Hackathon, where we focused on generic topology queries and addressed subset of gaps we identified for RFC8345 using IS-IS scenario in the operator LAB
- The objective for this hackathon is to improve the IETF120 Hackathon prototype, including:
-
Related Groups
¶ RPP - RESTful Provisioning Protocol
-
Champions
- Pawel Kowalik (pawel.kowalik@denic.de)
- Maarten Wullink (maarten.wullink@sidn.nl)
-
Project Info
RPP is a new proposed standard for domain name provisioning using a RESTful API.
- Based on HTTP using the REST architectural style
- Compatible (where possible) with existing EPP standards (STD69)
- Using JSON data format and schema validation
¶ The following areas would be worked on during the hackathon:
- Requirements for the protocol framework
- Requirements for object representations
- Modeling of object representations into JSON
- Code experiments of data transformation from/to EPP/JSON
- Code experiments of RESTful API using above transformations
-
Specifications
- Draft for RESTful EPP (which is start for RPP) - https://datatracker.ietf.org/doc/draft-wullink-restful-epp/
- Draft for conversion of EPP data model to JSON data model - https://datatracker.ietf.org/doc/draft-wullink-rpp-json/
-
Repositories
- Prototype API based on OpenAPI spec - https://github.com/SIDN/ietf-rpp-api
- Prototype implementation of schema conversion from draft-wullink-rpp-json - https://github.com/pawel-kow/epp-xsd-to-json-schema
¶ Encryption algorithm Rocca-S
- Champions
Yuto Nakano (yt-nakano at kddi.com) - Project Info
Rocca-S is an authenticated encryption with associated data (AEAD) algorithm designed for high performance applications.
The goal of this hackathon is to evaluate the performance of Rocca-S on mobile phones. - Draft Specification
https://datatracker.ietf.org/doc/draft-nakano-rocca-s/
¶ IPsec - Enhanced ESP implementation planning
- Champions
Steffen Klassert (steffen.klassert at secunet.com) - Project Info
Investigate on how a new security protocol can be implemented into the Linux Kernel xfrm subsystem.
First implementation steps. - Draft Specification
https://datatracker.ietf.org/doc/draft-klassert-ipsecme-eesp/
¶ Support for DNS CHAIN Queries (RFC 7901)
- Champions
Philip Homburg philip@nlnetlabs.nl - Project Info
Chain queries are an interesting approach to speed up local DNSSEC valition. I'll look into adding both the server and client side to the (Rust) Domain crate NLnet Labs is working on.
¶ Greasing the DNS
- Champions
Stéphane Bortzmeyer bortzmeyer@nic.fr - Project Info
Adding greasing support to DNS software (for starting: in the authoritative name server Drink) and testing through various systems such as the RIPE Atlas probes) that it does not break anything. - Draft Specification
https://datatracker.ietf.org/doc/draft-ietf-dnsop-grease
¶ Resumable Uploads for HTTP (RUFH)*
This project is beginner-friendly and we encourage all newcomers (and experienced) visitors to join from the kickoff or at any time during day.
-
Champions
- Marius Kleidl (marius@transloadit.com)
- Guoye Zhang (guoye_zhang@apple.com)
-
Project info
- HTTP provides resumable downloads out of the box, but not resumable uploads. To handle unreliable networks, many platforms implement their own proprietary approach for resumable uploads. With RUFH, we attempt to find a standard method for resumable uploads allowing interoperable implementations and widespread use.
- List of existing implementations: https://github.com/tus/rufh-implementations
-
Specifications
-
Challenges
- Updating implementations to support the latest draft. As the draft has been stable and is nearing its completion, we want to update existing implementations from earlier drafts to work with the latest revision.
- Testing interoperability between different clients and servers.
¶ vCon
-
Champions
- Dan Petrie (dan.ietf@sipez.com)
-
Project Info
WG: vCon
I-D: vCon container
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 and appended features of vCon have not been implemented or tested. The redacted feature has been implemented and tested mainly with text transcriptions. Further exploration of redacted audio and video dialogs had not been well tested. -
Hackathon Work Items
- Implement amended vCon and generate example for the vCon Container I-D
- Implement group vCon and generate example for the vCon Container I-D
- Implement redacted for video and/or audio media dialogs
¶ TLS Client puzzles
- Champions
David Venhoek: david@venhoek.nl - Project Info
TLS client puzzles are a way to have a client perform some amount of computational work before the server starts processing the handshake. This is intended to defend against DDoS attacks that exploit the asymmetry in effort needed to generate a client hello versus processing it at the TLS server.
Our goal during the hackathon will be to implement TLS client puzzles in more TLS libraries and test them against a demo server using the RusTLS implementation of tls client puzzles.
- Current implementations
- RusTLS patches: https://github.com/tweedegolf/rustls-pow
- Relevant documents
- Draft soon to be uploaded to datatracker: https://github.com/tweedegolf/draft-TLS-client-puzzles
- Original Nygren draft: https://datatracker.ietf.org/doc/draft-nygren-tls-client-puzzles/
¶ CBOR: Implementing packed
-
Champions
Christian Amsüss chrysn@fsfe.org -
Project Info
CBOR is a binary serialization format that is compact and extends the JSON model. Packed CBOR is a compression mechanism that uses CBOR's extension points; unlike stream compression, it can be used in place without unpacking. The current draft is an implementation draft: We believe it is feature complete, but it has not been tested with many implementations.In this hackathon project will change that.
-
Implementations under consideration
cbor2 (Python),
minicbpr (Rust for embedded), cbor-edn (Rust for diagnostic notation) -
Repository: https://codeberg.org/chrysn/cbor-packed-examples
¶ KIRA Routing Architecture: Testing of Prototypical Implementation
-
Champion(s)
Roland Bless roland.bless@kit.edu -
Project Info
KIRA offers highly scalable zero-touch IPv6 connectivity, i.e., it can connect hundred thousands of routers and devices in a single network (without requiring any form of hierarchy like areas). It is self-organizing to achieve a zero-touch solution that provides resilient (control plane) IPv6 connectivity without requiring any manual configuration by operators. It works well in various topologies and is loop-free even during convergence. The architecture consists of the ID-based network layer routing protocol R²/Kad in its routing tier and a Path-ID-based forwarding tier. The topological independent IDs can be embedded into IPv6 addresses, so that KIRA provides zero-touch IPv6 connectivity between KIRA nodes. -
Internet Draft:
See https://datatracker.ietf.org/doc/draft-bless-rtgwg-kira/ -
Hackathon Objective
Get several test cases running for KIRA. -
Code
The current prototype is written in Rust. -
Repository
Git repository https://gitlab.kit.edu/kit/tm/telematics/kira/kira-rust
(may change to github for convenience) -
Additional Info:
Papers, slides etc. https://s.kit.edu/KIRA
¶ YANG To RDF
-
Champions
- Michael Mackey (michael.mackey@huawei.com)
- Anatolii Pererva (anatolii.pererva@huawei.com)
- Benoit Claise (benoit.claise@huawei.com)
-
Project Info
Knowledge Graphs are an essential tool for connecting data and recording dynamic relationships. A big barrier to using Knowledge Graphs within the networking world is the ability to represent networking data in a Knowledge Graph. In order to bridge this gap we introduce YANG2RDF, a tool that takes YANG files and converts them to RDF. -
Hackathon plan
YANG2RDF is currently a PoC, we plan to improve the translation during the IETF. -
Specifications
https://datatracker.ietf.org/doc/draft-mackey-nmop-kg-for-netops/ -
Repositories
Github repo: https://github.com/Huawei-IOAM/yang2rdf
¶ DNS DELEG support in BIND
- Champions
Petr Špaček, pspacek@isc.org - Project Info
Implement https://www.ietf.org/archive/id/draft-wesplaap-deleg-01.html for BIND, starting with DNSSEC signer and authoritative server.
¶ DNSSEC rollover improvements
- Champions
CSILLAG Tamás (PCH), cstamas+dnssec@cstamas.hu - Project Info
Try to enhance https://www.rfc-editor.org/rfc/rfc6781.html#section-4.3.5 - the process of changing dnssec providers. The idea is: let's the new provider do most of the work, because less coordination needed that way and less work for the previous owner.
The goal is to confirm if this is feasible, describe the process and possibly create a minimal tool to help.
previous owner = owner1
new owner = owner2
- Owner1 gives escrow and signed zone to owner2.
- Owner2 generates new ksk+zsk.
- Owner2 puts new ksk into the parent as additional ds. (this might need a process change from IANA)
- Owner2 puts new ksk+zsk and owner1's zsk into the dnskey rrset.
- ... wait parent DS TTL time ....
- Owner2 publishes the zone with old signatues except for the DNSKEY rrset.
- ... wait previous DNSKEY TTL time ...
- Owner2 publishes the zone with new signatures only.
¶ rpki-rtr updates
- Champions
- Tom Harrison tomh@apnic.net
- Project Info
- Proof of concept updates for draft-ietf-sidrops-8210bis.
- Specifications
- Repositories
¶ EAPRAD -- EAP and RADIUS
- Champions
- Jan-Frederik Rieckers rieckers@uni-bremen.de
- Karri Huhtanen kh@radiatorsoftware.com
- Heikki Vatiainen hvn@radiatorsoftware.com
- Project Info
Working on EAP(-FIDO), RADIUS, OpenRoaming technologies as well as with RADEXT working group drafts and issues related to them. Detailed plan to be discussed and decided in the group.
- Location
- Onsite: Table 2
- Remote: Please contact the champions, if you want to participate remotely
¶ scitt Supply Chain Integrity, Transparency, and Trust
- Champions
- Jon Geater jon.geater@rkvst.com
- Nobuo Aoki n_aoki@ieee.org
- Roy Williams
- Project Info
- SCRAPI - CBOR ALL The Things
- ScraPy - Python implementation of SCRAPI
- Architecture Hacking
- Slide hackings (Promothing transparency)
- Location
- Onsite: Table 1
¶ Ultra-Low Latency Cryptography
- Champion(s)
- Yumi Sakemi (yumi.sakemi@gmo-cybersecurity.com)
- Satoru Kanno (satoru.kanno@gmo-cybersecurity.com)
- Project Info
- In future communication technologies such as 6G, there are technical requirements that demand ultra-low latency and high levels of security. So, the purpose of this project is to achieve low-latency and highly secure cryptographic techniques targeting future communication technologies.
- TBD
- Paper at https://tches.iacr.org/index.php/TCHES/article/view/10279/9727
- We are currently recruiting collaborators who will join us in this project.
- Specifications
- https://datatracker.ietf.org/doc/draft-sakemi-areion/
- Work in progress
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.