¶ IETF 118 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: Saturday - Sunday, 4-5 November 2023
Where: Hilton Prague, Prague, Czechia
Room: Congress Hall 1/2, Lower Lobby Level
Sponsored by
| Gold Running Code Sponsor | Silver Running Code Sponsor | Bronze Running Code Sponsors |
|---|---|---|
 |
 |
  |
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
Hackathon (all times are CET UTC+1)
¶ Saturday, 4 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, 5 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, 6 November, Time: 18:30 - 19:30, Room: Ballroom Foyer, Mezzanine Level
- View the schedule or reserve space for your team/project
- Reservations for space must be made by 13:00, Monday 6 November
¶ Code Lounge
- Space for groups to gather and collaborate on running code
- Tuesday - Friday, 7-10 November, Room: Karlin 3, Mezzanine Level
- 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
¶ Meeting Materials
- Code can be accessed from IETF Hackathon GitHub, or from links provided within project descriptions below.
- Request to be added to IETF GitHub organization by sending your GitHub ID to (hackathon-chairs@ietf.org).
- Results of Hackathon projects should be uploaded to GitHub. See the README for details.
¶ 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 org is used for Hackathon presentations and contains repositories for some Hackathon projects.
- 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.
- IETF Hackathon teams should upload their Hackathon project presentations to GitHub.
- You must be a member of the IETF-Hackathon GitHub org to upload a new presentation or update/replace an existing presentation
- To be added as a member, see details in the README
- DO NOT WAIT until just before Hackathon project presentations start or your request 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.
¶ BIER plugfest
- Champion(s)
- mc36 (remote) freertr.org with a programmable asic up to 12tbps in pizzabox and providing images / pdfs also...
- Simon Leinen (on-site) swit.ch with a laptop helping the collaboration, manage / present the results / advocate achievements, etc...
- Jeffrey Zhaohui Zhang (on-site) juniper.net with a Ubuntu laptop running virtual routers
- Project Info
- its a plugfest, so its normal that we have different targets....
- freertr.org interested in https://datatracker.ietf.org/doc/html/draft-ietf-bier-pim-signaling-12 , here is a pre-recorded demo https://files.fm/f/2eanhgkmx
- The goal is informal interop testing with BGP-MVPN overlay, ISIS signaling, and BIER forwarding with MPLS encapsulation
¶ RIFT plugfest
-
Champion(s)
- AntoniPrzygienda (prz@juniper.net)
- Jordan Head (jhead@juniper.net)
- Sandy Zhang (zhang.zheng@zte.com.cn)
- Benchong Xu (xu.benchong@zte.com.cn)
- Yuehua Wei (wei.yuehua@zte.com.cn)
-
Project Info
- It's a plugfest, The goal is informal interop testing with rift base specification, including:
- Bring up adjacency with fixed level config
- Bring up adjacencies with ZTP
- Exchange TIEs
- Verify routing tables
- It's a plugfest, The goal is informal interop testing with rift base specification, including:
-
Draft Specifications
¶ SCION open source applications
-
Champion(s)
- Matthias Frei (matzf at scion.org)
- Dominik Roos (roos at anapaya.net)
- Thorben Krüger (thorben.krueger at ovgu.de)
- François Wirz (wirzf at inf.ethz.ch)
-
Project Info
- Projects centered on open-source SCION applications (Dominik Roos)
- HTTP3-over-SCION Plugin for Caddy
Create an HTTP3-over-SCION plugin for Caddy, the popular web server.
This plugin will enable Caddy to seamlessly act as a reverse proxy
for legacy HTTP servers, unlocking SCION adoption without the need
for extensive code modifications on existing applications.
Foundations have been established in Caddy,
simplifying integration with custom SCION-based networks.
project description - Integrating SVC resolution in QUIC handshake
Optimize the SCION control plane RPCs by integrating the SVC
resolution into the QUIC handshake. This will reduce the number
of round trips required for the RPCs. Our open proposal aims to
eliminate this round trip, simplifying the entire exchange process.
project description - QUIC-Based VPN over SCION
Prototype a VPN solution over SCION utilizing QUIC, eliminating the
need for a SCION-IP Gateway as an intermediary. Building on our
existing QUIC-over-SCION support, this prototype aims to connect
hosts seamlessly. We can draw inspiration from quincy for this prototype.
project description - Connect over SCION
Enable Connect, an HTTP-based RPC
framework, to operate over SCION. Unlike gRPC, connect-go
features a compact codebase primarily built on the Go stdlib,
simplifying the implementation process.
- HTTP3-over-SCION Plugin for Caddy
- DNS over QUIC (RFC 9250) for SCION (Thorben Krüger)
- Projects centered on open-source SCION applications (Dominik Roos)
-
Draft Specifications
¶ SCION Deployment guide
-
SCION Deployment guide
-
Champion(s)
- John Studarus (John.Studarus at martincoit.net)
- Nicola Rustignoli (nic at scion.org)
- Corine de Kater (cdk at scion.org)
-
Project info
Part of having a successful open source implementation is making it easy for newcomers (developers, hobbyists, students, etc) to set up and run a SCION environment. SCIONLab and the SCION development (scion.sh) are two starting points but going to the “next level” - a stand alone network, can be daunting. This came about when attempting to perform large scale testing of SCION which would have been inappropriate across SCIONLab and unfeasible in a local development environment.
Goals:- Documentation written up and placed as part of the existing SCION Docs webpage
- Deployment options (bare metal, VMs, containers)
- Requirements (hardware and network)
- Prerequisites - OS version/configuration, network interface configuration
- Sample deployment architecture(s)/Topologies
- Where to find packages/binaries (i.e. tagged/tested releases)
- Creating configuration files
- Setting up keys (and on-going key operations)
- Verifying Proper Operations/Troubleshooting guide
- Prometheus monitoring of SCION metrics
¶ Does Not Scale: Rethinking DNS for the Future of the Internet
- Champion(s)
- Petr Špaček (pspacek at isc.org)
- Project Info
Brainstorming session with people who work on Domain Name System protocol, write implementations and operate networks. How do we make DNS:- ... transfers scale to millions of zones? And how do we monitor it?
- ... protocol & transport handle humongous post-quantum crypto keys and signatures?
- ... support distributed multi-master setups?
- ... extensible to new wire format & at the same time, maintain a single namespace?
- ... simpler to operate? What if we rethink basic assumptions? (see the talk starting at 33:40)
¶ 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)
Tomofumi Okubo (tomofumi.okubo@digicert.com)
Massimiliano Pala (m.pala@cablelabs.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-ounsworth-pq-composite-sigs/
https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-kem/00/
https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-kemri/
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
¶ PQ Encrypted Client Hello
-
Champion(s)
- Georgios Tasopoulos (g.tasop@isi.gr)
- Evangelos Haleplidis (haleplidis@isi.gr)
- Apostolos Fournaris (fournaris@isi.gr)
-
Project Info
- Our goal is to initiate an effort to introduce Post-Quantum algorithms (specifically PQ KEMs) into the TLS 1.3 extension Encrypted Client Hello (ECH). We have selected the wolfSSL library as our TLS 1.3 implementation as it includes an ECH extension implementation and we are the most familiar with. We have setup a common code starting point using Vagrant and a github repository in order to help the development between participants during the Hackathon.
-
Draft Specifications
-
Additional Information
-
You can find additional information in our project github page: https://github.com/IETF-Hackathon/pq-ech
-
¶ Tapsce, TAPS in space
-
Champion(s)
- Emile Stephan (emile.stephan@orange.com)
- Marc Blanchet (marc.blanchet@viagenie.ca)
-
Project Info
-
The purpose of the project is to devellop an open-source TAPS transport service for space an deep space based on existing open source QUIC stack and extensions.
-
This includes prior knowledge parameters already discussed during at Marc table during IETF117 hackathon : need to customize the bootstrapping parameters, default parameters, multipath...
-
When needed, the project will extend TAPS API for covering DTN transport services like store-and-forward, routing, dynamic network paths...;
-
To ease the work during this first table it is suggested to start with Christian QUIC to Mars open-source QUIC implementation.
-
-
documents
-
media
-
materials
- Huitema Picoquic: https://github.com/private-octopus/picoquic
- pytaps: https://github.com/fg-inet/python-asyncio-taps/tree
- aioquic: https://github.com/aiortc/aioquic
¶ Are long-lived TCP sessions a problem for (DNS) statistics?
- Champion(s)
- Jerry Lundström (jerry at dns-oarc.net) (remote)
- Roy Arends (roy at dnss.ec)
- Project Info
-
Some tools uses packet capturing to do statistics for DNS and some of them needs to see the beginning of the TCP sessions. If resolver systems out there start keeping TCP session against authorities open for a very long time (days or weeks) then it might become a problem for these tools.
We would like to look at two things;
- First to poke at data to see if there are very long-lived TCP sessions out there today, or not(!) which is equally interesting to know.
- Second to survey DNS statistics tools out there to see how they handle long-lived TCP sessions to understand how wide a problem this might be, if any. And maybe fix some of them if issues are spotted when doing this.
Sounds interesting? Do you have data to poke at? Hope to see you at the hackathon then!
-
Please join #IETF Hackathon LLTCP (on DNS-OARC's Mattermost) to discuss the project with all participants.
-
¶ Media over QUIC (MoQ)
-
Champion
- Suhas Nandakumar
-
Project Info
- Media over QUIC is developing a low-latency media delivery solution suitable for ingest and distribution of media with for support for relays.This effort is expected to be focused on testing the MoQ transport, using the latest version of draft-ietf-moq-transport as an implementation target.
-
Documents
-https://datatracker.ietf.org/doc/draft-ietf-moq-transport/
¶ Tie Die IoT Onboarding and Application Layer Gateway
-
Champions
-
Project Info
- Tie Die is a combination of IoT provisioning technology and an application layer gateway that may be used to register new IoT devices, whether they are BLE, Zigbee, or IP-based. Tie Die starts with the SCIM model for provisioning, with the notion that schemas should be technology neutral. The first code we have, though, is primarily BLE. By the time of the Hackathon we will have Zigbee. We hope also to do some work to enable both DPP, and to extend the SCIM device model to also handle Fido Device Onboarding.
-
Documents
-
Code
¶ Low-Latency, Low-Loss, and Scalable Throughput (L4S) and Accurate ECN Interop
- Champion(s)
- Greg White (g.white at cablelabs.com)
- Project Info
- L4S and AccECN enable applications to receive fine-grained 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 the Code Lounge for the rest of the week.
- Documents
¶ Encryption algorithm Rocca-S
-
Champion(s)
- 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 include Rocca-S as one of the algorithms in OpenSSL.
- The academic paper of Rocca-S is presented at ESORICS 2023 (https://esorics2023.org/)
-
Draft Specification
¶ Attestation and TLS
- Champion(s)
- Project Info
- TLS extensions to support attestation tokens as first-class authentication credentials
- End-to-end demonstrator with attester, verifier and relying party
- Specifications:
- Code
¶ Vector Commitment based Proof of Transit
- Champion(s)
- Chunchi Liu (liuchunchi at huawei.com)
- Project Info
- Proof of transit is a technique that provides evidence that a data packet has traveled through certain predetermined nodes or hops.
- Proof of transit is critical to support protocols and frameworks that feature centralized/source path planning, such as Service Function Chaining, Segment Routing, etc.
- We implement and demonstrate a new solution to proof of transit using a cryptographic primitive named "vector commitment".
- Specifications
- Code
¶ Network Telemetry - YANG Push Integration into Apache Kafka
- Champion(s)
- Alex Huang-Feng (alex.huang-feng at insa-lyon.fr)
- Zhuoyao Lin (zephyre888 at gmail.com)
- Jean Quilbeuf (jean.quilbeuf at huawei.com)
- Benoit Claise (benoit.claise at huawei.com)
- Ahmed Elhassany (ahmed.elhassany at swisscom.com)
- Draft(s)
- 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-yang-notifications-versioning
- https://datatracker.ietf.org/doc/html/draft-tgraf-netconf-notif-sequencing
- https://datatracker.ietf.org/doc/html/draft-tgraf-yang-push-observation-time
- Project info
- Marry YANG Push wit Apache Kafka message broker.
- Project site
¶ Network Telemetry - Semantic Metadata Annotation for Network Anomaly Detection
-
Champion(s)
- Vincenzo Riccobene (vincenzo dot riccobene at huawei-partners dot com)
- Wanting Du (wanting dot Du at swisscom dot com)
- Benoit Claise (benoit.claise at huawei.com)
- Thomas Graf (thomas dot graf at swisscom dot com)
-
Project Info
- Semantic Metadata Annotation for Network Anomaly Detection. Categorizing and defining unified semantics for operational Network Telemetry data.
- https://datatracker.ietf.org/doc/html/draft-netana-opsawg-nmrg-network-anomaly-semantics
¶ YANG SIDs — making PYANG fit for YANG SIDs
-
Champion(s)
- Carsten Bormann (cabo@tzi.org)
-
Project Info
- PYANG can be used for automatically generating the numerical YANG SIDs that are to accompany YANG Modules.
- Almost at least. It cannot fully reproduce the .sid file in https://www.ietf.org/archive/id/draft-ietf-core-sid-23.html yet.
- We want to make sure that PYANG can be used as a routine tool for that by IANA and Designated Expert teams.
¶ MADINAS - Wi-Fi OpenRoaming
- Champion(s)
- Bruno Tomas (bruno at wballiance.com)
- Mark Grayson (mgrayson at cisco.com)
- Project Info
- OpenRoaming works similarly to Eduroam, allowing users to automatically connect to Wi-Fi networks, but with a federated structure that allows multiple Access Network Providers (ANPs) and multiple Identity Providers (IDPs) to interoperate under the same federation. It leverages technologies developed in the IETF, IEEE802 and Wi-Fi Alliance (WFA), such as RADIUS/RADSEC/PKI (RFCs 2865, 3579, 4372, 5280, 6614…), IEEE 802.1X, 802.11, and WFA WPA2/WPA3. OpenRoaming is being discussed as a solution to some of the use cases considered by the IETF MADINAS WG. The project will look for potential areas of improvement to IETF protocols, as well as potential leakage of PIIs.
NOTE1: Hackathon participants wanting to be issued a test certificate for use in mutual authenticated OpenRoaming signalling exchanges, should email pki@wballiance.com with the subject “IETF Hackathon Test Certificate Request”.
NOTE2: The OpenRoaming PKI Certificate Policy and WBA issuing I-CA require specific subject distinguished name values. An example certificate signing request configuration that meets the OpenRoaming Certificate Policy is available here (https://github.com/wireless-broadband-alliance/openroaming-config/blob/main/OpenRoaming CSR config.cfg)
- Useful resources
Howto enable OpenRoaming on the MikroTik series of devices (by Warren Kumari, based on his setup for IETF 117): https://wkumari.dev/2023/10/16/mikrotik-openroaming
¶ Formal Specification and Verification of Architecturally-defined Attestation in Confidential Computing
- Champion(s)
- Muhammad Usama Sardar (muhammad_usama.sardar at tu-dresden.de)
- Project Info
- Arm CCA
- Intel TDX
- Analysis tool: ProVerif
- Technical specs
https://www.researchgate.net/publication/367284929_SoK_Attestation_in_Confidential_Computing - Code
https://github.com/CCC-Attestation/formal-spec-TEE
¶ IP-Based Mobile Object Networking (IPMON) over 5G V2X
- Champion(s)
- Jaehoon (Paul) Jeong (pauljeong at skku.edu)
- Participant(s)
- Project Info
- Build an IP-based 5G network that guarantee the safety of flights in drone networks; V2I scenarios.
- Evaluate the performance of safety message information exchange in drone networks.
- Search for technology gaps between current practice and the standard process.
- Specifications
¶ Intent-Based Network Management Automation for 5/6G Core Networks
-
Champion(s)
- Jaehoon (Paul) Jeong (pauljeong at skku.edu)
-
Participant(s)
-
Project Info
- Evaluate Intent-Based Network Management Automation for 5/6G Core Networks.
¶ Multipath QUIC
- Champion(s)
- Magnus Westerlund (magnus.westerlund@ericsson.com
- Project Info
- Interop testing of the current draft of Multipath QUIC.
- Specification
¶ EDHOC
- Champion(s)
- Marco Tiloca (marco.tiloca at ri.se)
- Project Info
- Establish keying material for OSCORE using the EDHOC protocol
- Specifications:
¶ Interfaces of the OSCORE Group Manager
- Champion(s)
- Marco Tiloca (marco.tiloca at ri.se)
- Project Info
- User and admin interface of the OSCORE Group Manager based on the ACE framework
- Specifications:
¶ A Rust API for DNS
- Champion
- Philip Homburg (philip at nlnetlabs.nl)
- Project Info
- APIs are often specified in C (for example, the socket interface, getaddrinfo, getdns) and then bindings are created for other languages. Rust is both a low level language and sufficiently different from C that it makes sense to take a new look at an API for DNS.
¶ Ad-hoc IoT Networking
- Champions
- Andreas Foglar (foglar@innoroute.com)
- Marian Ulbricht (ulbricht@innoroute.de)
- Project Info
https://datatracker.ietf.org/doc/draft-foglar-ipv6-ull-routing/
an experimental network has been created in Germany with the prefix AF49/16.
The "6Tree" network is ideal vor IoT thanks to- IPv6 with phone number prefix and MAC address mapping
- Intrinsic security thanks to verified IPv6 prefix
- no DNS for lower access latency
- low latency thanks to hierarchical network structure
- Participants are invited to test and evaluate the 6Tree network, for example latency.
Instant access to this network is possible with a PC and a mobile phone with German telephone number. A phone call is used for prefix verification. For non-German residents pre-paid SIM cards will be provided. Technology hand-over to Polish operator planned at the Hackathon.
- Participants are invited to test and evaluate the 6Tree network, for example latency.
¶ RPKI ASPA Interop
- Champions
- Tassilo Tanneberger tassilo.tanneberger@tu-dresden.de
- Carl Seifert carl.seifert1@mailbox.tu-dresden.de
- Moritz Schulz moritz.schulz@proton.me
- Participants
- …
- Project Info
- https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-8210bis-11#name-aspa-pdu
- https://datatracker.ietf.org/doc/draft-ietf-sidrops-aspa-verification/
- https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-aspa-profile-16
- https://github.com/rtrlib/rtrlib
- ASPA fork https://github.com/tanneberger/rtrlib
¶ High-level CoAP abstraction in RIOT
- Champions
- Martine Lenders martine.lenders@tu-dresden.de
- Tim Rieß tim.riess@mailbox.tu-dresden.de
- Jan Sommer jan.sommer@mailbox.tu-dresden.de
- Dennis Kraus dennis.kraus@mailbox.tu-dresden.de
- Niko Kirste niko.kirste@mailbox.tu-dresden.de
- Project Info
- There are many diverging implementations for the Constrained Application Protocol (CoAP, RFC 7252)
- We try to implement a prototype for a high-level API for the RIOT operating system that can be used on top of different CoAP implementations.
¶ Dynamic Network Routing
-
Champion(s)
- Li Zhang zhangli344@huawei.com
- Jie Dong jie.dong@huawei.com
- Tianran Zhou zhoutianran@huawei.com
- Qiangzhou Gao gaoqiangzhou@huawei.com
- Zhenbin Li lizhenbin@huawei.com
-
Project Info
- Dynamic Network means the topology of network changes frequently, the typical Dynamic Network use cases include energy efficiency network, resource limited network and satellite network.
- The goal of this project is to evaluate the performance of existing routing protocols on dynamic networks. This project will simulate the topology change of Dynamic Network and run some existing routing protocols on it. Based on that, we will know the problems of dynamic network routing.
-
Documents
¶ Measuring transparent DNS-forwarders
- Champions
- Maynard Koch
- Florian Dolzmann florian.dolzmann@mailbox.tu-dresden.de
- Carl Bennet Kuhlmann carl_bennet.kuhlmann@mailbox.tu-dresden.de
- Maximilian Stäps maximilian.staeps@mailbox.tu-dresden.de
- Project Info
- We work on a framework to measure and analyze the open DNS infrastructure especially the commonly overlooked transparent DNS forwarders.
- Our goal is to extend https://odns.secnow.net/ tool to support DNS-over-TCP and QUIC.
- Documentation
- Code
¶ Identifier Locator Network Protocol (ILNP)
- Champions
- Saleem Bhatti saleem@st-andrews.ac.uk
- Gregor Haywood gh66@st-andrews.ac.uk
- 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 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 research demonstration will be based on IPv6.
¶ IPFIX On-Path Telemetry with SRv6
- Champions
- Wataru Mishima watal@wide.ad.jp
- Yuta Fukagawa skyline@fkgw.org
- Motoki Takenaka m.takenaka@ntt.com
- Yuya Tajima yuya.tajima@ntt.com
- Project Info
- In this project, we aim to implement on-path delay measurement for SRv6 flow on a Linux router and export the data with IPFIX. This feature will be integrated to the Fluvia Exporter, an IPFIX exporter using eBPF/XDP developed during the in IETF117.
- Documents
- Code
¶ NTPv5 and Roughtime
- Champions
- Karen O'Donoghue kodonog@pobox.com
- Dieter Sibold dsibold.ietf@gmail.com
- Project Info
- In this project we plan to work on implementations of Roughtime and NTPv5.
- Documents
¶ Explicit Flow Measurements
-
Champion(s)
- Massimo Nilo (massimo.nilo at telecomitalia.it)
- Fabio Bulgarella (fabio.bulgarella at guest.telecomitalia.it)
-
Project Info
- Explicit flow measurement techniques applied to performance parameters (e.g. Latency) for trasport-layer protocols.
-
Documents
¶ Trusted Execution Environment (TEEP)
- Champion(s)
- Dave Thaler (dthaler at microsoft.com)
- Akira Tsukamoto (akira.tsukamoto at alaxala.com)
- Project Info
- TEEP/SUIT/RATS integration
- Update TEEP Protocol implimentation applying feedbacks after IETF117
- Discussing about Formal Verification of TEEP
- Specifications
- Repositories
- TEEP Protocol wiki
- Hackathon branches on github
¶ CoAP Group Communication with Group OSCORE
- Champion(s)
- Project Info
- Message exchange of group messages protected with Group OSCORE
- Specifications
¶ SAV Open Playground
- Champion(s)
- Yuqian Shi (shiyuqian at zgclab.edu.cn)
- Lancheng Qin (qlc19 at mails.tsinghua.edu.cn)
- Libin Liu (liulb at zgclab.edu.cn)
- Li Chen (lichen at zgclab.edu.cn)
- Project Info
- SAV Open Playground(SAVOP) provides an open platform to emulate different SAV mechanisms.
- Code: https://github.com/SAV-Open-Playground/
- Feel free to share your ideas at https://github.com/SAV-Open-Playground/savop/discussions
- Hackathon Plan
- Emulations of SAV mechanisms based on SAVOP
- Evaluation of SAV mechanisms with SAVOP in terms of the following aspects
- Validation accuracy in different scenarios, such as limited propagation of prefixes, hidden prefixes, attacks by source address spoofing within a customer cone, attacks by source address spoofing from a provider/peer AS
- Control plane performance and data plane performance
- Scalability of SAVOP
¶ Streamlining Social Decision Making for Improved Internet Standards (sodestream)
- Champion(s)
- Stephen McQuistin (sm at smcquistin.uk)
- Ignacio Castro (i.castro at qmul.ac.uk)
- Project Info
- Working on tasks related to the sodestream (sodestream.github.io) project, which applies natural language processing and social networking techniques to data produced by the IETF, in order to better understand standardisation processes.
¶ 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
¶ Collective Communication Optimizations(CCO)
- Champion(s)
- Kehan Yao (yaokehan@chinamobile.com)
- Yizhou Li (liyizhou@huawei.com)
- Wenfei Wu(wenfeiwu@pku.edu.cn)
- Hongyi Huang(hongyi.huang@huawei.com)
- Dirk KUTSCHER(ietf@dkutscher.net)
- Project Info
- Collective communication plays a key role in high performance computing and the modern distributed AI training workloads such as recommender systems and natural language processing. It involves a group or groups of processes participating in collective operations like AllReduce or Bcast. The communication model can be one-to-all, all-to-one or all-to-all, but is usually realized by a sequence of unicast messages in underlying network.
- Designing network assissted collective communication, that is to offload some collective opeartions to the network to execute one or some key steps in the process, so as to provide more efficient group communication, is drawing some special attentions as the ways for collective communication optimizations (CCO). It also imposes some challenges and requirements for both message transport and packet forwarding, and co-design of protocols and distributed learning frameworks.
- Documents
¶ Sustainability Insights
-
Champions
- Jan Lindblad jlindbla@cisco.com
- Marisol Palmero mpalmero@cisco.com
-
Participants
- Per Andersson perander@cisco.com
- Kristian Larsson k@centor.se
- Snezana Mitrovic snmitrov@cisco.com
- Esther Roure erourevi@cisco.com
- Emile Stephan emile.stephan@orange.com
- Ajit Thyagarajan ajthyaga@cisco.com
- Vesna Manojlovic BECHA@ripe.net
-
Project Info
- Our group is working on “Sustainability Insights", philatelist, label-tsdb and POWEFF drafts.
- Our objective is to validate, test and extend green monitoring open source tool to include:
- YANG-capable devices as part of Telegraph connector.
- Connect real lab devices, to facilitate testing.
- Introduce Data Normalization effort through POWEFF model.
-
Documentation
-
Code
¶ Revision Label in YANG tooling
-
Champions
- Per Andersson perander@cisco.com
-
Project Info
- draft-ietf-netmod-yang-module-versioning defines the revision-label extension, this change also also updates the specified filename schema for YANG modules (currently module.yang or module@YYYY-MM-DD.yang) to also support module#revision-label.yang.
- Currently there are ongoing discussions about this change, if it should be or not. One question raised was that it could require a big effort to update tooling to understand the assumed filenames for a YANG module.
- During this hackathon we explore if changing the assumptions on filenames, and other revision label extensions, for YANG modules requires a big effort.
-
Documentation
-
Code
¶ Comprehensive Evaluation of Multicast Source Routing over IPv6
-
Champions
- Wu Weihong(wuweihong@bupt.edu.cn)
- Jiang Yuxin(jyxin728@gmail.com)
- Tang Yunyi(tangyunyi0708@bupt.edu.cn)
- Pei Anbang(anbangpei@bupt.edu.cn)
- Liu Jiang(liujiang@bupt.edu.cn)
-
Project Info
- Implement MSR6 BE, MSR6 TE and MSR6 TE with RLB on hardware using the P4 language.
- Emulate the P4 programs of MSR6 based on several P4 switches.
- Conduct numerical simulations to evaluate the resource performance of MSR6 and other 5 state-of-art multicast solutions from a macro perspective based on real network topology.
-
Documents
- https://datatracker.ietf.org/doc/draft-eckert-msr6-problem-statement
- https://datatracker.ietf.org/doc/draft-geng-msr6-traffic-engineering/02
- https://datatracker.ietf.org/doc/draft-geng-msr6-rlb-segment/02/
- https://datatracker.ietf.org/doc/draft-chen-pim-srv6-p2mp-path/
- https://datatracker.ietf.org/doc/draft-chen-pim-mrh6/
¶ 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)
- Merlijn Vos (merlijn@transloadit.com)
- Jonathan Flat (jflat@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 implementions and widespread use.
- We have a hackathon repository for this project with extra context and requirements: https://github.com/tus/ietf-hackathon
-
Specifications
-
Challenges
- Resumability polyfill for the Fetch API in browsers. Creating a polyfill for the Fetch API for resumable uploads in the browser. It could help to find a suitable API for resumable upload in browsers.
- Plugins for popular HTTP proxies for handling resumable uploads. Plugins for popular HTTP proxies, which handle resumability with buffering. Once the upload is complete, it will forward the upload as a regular HTTP request to your backend.
- CLI program to test if a server conforms to the spec. Implementing RUFH means re-implementing the same kind of end-to-end tests over and over again. To ensure compatability and interoperability between servers and clients, a tool for checking conformness to the protocol is helpful.
- JavaScript runtime compatibility. There is a rise in JavaScript runtimes, such as Deno, Bun, Cloudfare Workers, AWS Lambda, and more. These should have minimal differences, but the devil is in the details and we need to know if the current version of RUFH works in most runtimes, particularly on the edge. This would be done with a minimal proof of concept of RUFH in JavaScript with different adapters for runtimes.
¶ 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.
- At IETF117 hackathon, we undertook efforts to make the low-latency cryptography ‘Areion’ available for use with TLS 1.3. Based on this work, at the IETF118 Hackathon, we will take on the challenge of applying “Areion” to QUIC and WebRTC.
- 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
¶ Introduction to the MTL Mode Open Source Library
An opportunity for participants to engage around the recently released open-source library for Merkle Tree Ladder Mode (MTL) signatures (https://github.com/verisign/MTL). MTL Mode is described in the recent I-D for CFRG (https://datatracker.ietf.org/doc/draft-harvey-cfrg-mtl-mode/) as a means for reducing the size impact of PQC algorithms for some use cases, such as DNSSEC.
- Champions
- Joe Harvey (jharvey@verisign.com)
- Andy Fregly (afregly@verisign.com)
- Project Info
- Participation in the project will provide an opportunity to:
- Learn from two members of the team that developed MTL Mode about how it works and how it might be used
- Receive guided walkthroughs of the open-source library and example code
- Receive guidance on how the code can be built into a docker container
- If hacking, receive support in developing code that incorporates the open-source library or is derived from the example code
- Influence future activities related to the open-source library such as additional language bindings and support for additional underlying PQC signature schemes
- Participation in the project will provide an opportunity to:
¶ IP-TFS in Linux (swan support)
- Champions
Christian Hopps (chopps@chopps.org) - Project Info
IP-TFS in Linux is the implementation of IP-TFS in Linux. The code is nearing the point of merging and the netlink API is stable. As such it's time to start extending the swans to support configuring IP-TFS. Plan on adapting existing strongswan code published previously. Participants welcome to help or bring support to other swans (libre).
¶ Improving IPv6-only experience on Linux
-
Champions
- Ondřej Caletka (ondrej.caletka@gmail.com)
-
Project Info
In order to work properly on an IPv6-only network a CLAT is typically needed to help with corner cases like using IPv4-only applications or IPv4 literals. This is especially useful with the advent of IPv6-mostly networks where a host can opt-out from IPv4 using IPv6-Only Preferred DHCP option. Support for this option is already implemented in Linux DHCPv4 clients (systemd-networkd, dhcpcd) but a properly integrated CLAT is still missing.
Let's try to figure out if anything can be done in this area. For instance a daemon similar tordnssdthat would look for PREF64 option in router advertisments and set up some NAT46 translator when such option is received. -
Resources
- clatd - a CLAT daemon utilizing userspace translator TAYGA
- nat46 - stateles kernel-space SIIT
- tundra - a user-space NAT64 translator
- ndisc6 - userspace Neighbor Discovery tools, including
rdnssd - systemd-networkd 464XLAT issue
- PREF64 RA deamon
-
Relevant documents
¶ Additional Addresses for QUIC
- Champion(s)
- Maxime Piraux (maxime.piraux@uclouvain.be)
- François Michel (francois.michel@uclouvain.be)
- Project Info
- The QUIC protocol specifies two techniques for network path migration: Client Migration and Server Preferred Address. The first enables the client to use another local address while the other indicates a server preferred address to be used shortly after the handshake. However, the server cannot advertise additional addresses that a client may use. We proposed an extension consisting of a frame indicating the server's additional addresses in the I-D draft-piraux-quic-additional-addresses.
- During the hackathon, we will implement the specified extension in open-source QUIC implementations and perform interop testing. We're aiming at testing both QUIC and MPQUIC.
- Coordination will happen on channel #additional-addresses of the quicdev Slack.
- Specifications
¶ Testing SCE and the DelTiC AQM with Antler
- Champion(s)
- Pete Heist (pete@heistp.net)
- Rodney Grimes (rgrimes@freebsd.org)
- Project Info
- Some Congestion Experienced is an experimental high-fidelity congestion control protocol that provides fine-grained congestion signaling for transports to increase utilization and decrease latency.
- DelTiC is a fully time-domain AQM based on a delta-sigma control loop and a numerically-controlled oscillator. Delta-sigma means a PID controller lacking a Proportional term, with the D term accumulated into the I term.
- Antler is a congestion control testing tool currently in development.
- For this hackathon, we will review the code for DelTiC, and see if we can use Antler to test a multipath routing topology change.
- Documents
¶ vCon
-
Champions
Dan Petrie dan.ietf@sipez.com -
Project Info
We will be working on the py-vcon server.
vCon tentative charter
vCon ID
¶ RIFT Interop
- Champions
Tony Przygienda prz@juniper.net
We will have multiple implementations of RIFT from open source and vendors and interop those.
Workplan will be mashed up on first day dependig on who shows up with what gear.
¶ COSE encryption implemenation -- t_cose
- Champions
Laurence Lundblade lgl@island-resort.com - Project Info
Continue to improve the t_cose implementation of COSE encryption. Hoping to
complete more testing and support of non-aead ciphers (Thanks Ken!)
https://github.com/laurencelundblade/t_cose/tree/dev
¶ ASDF SDF
- Champions
Ari Keränen ari.keranen@ericsson.com
Carsten Bormann cabo@tzi.org - Project Info
Progressing the implementations of the Semantic Definition Format (SDF) and pressure testing the CDDL grammar. - Documents
https://www.ietf.org/archive/id/draft-ietf-asdf-sdf-16.html - Implementations
https://github.com/one-data-model/tools
https://github.com/EricssonResearch/ipso-odm
¶ Careful Resume - Speeding-up QUIC Start-up
- Champions
Ana Custura ana@erg.abdn.ac.uk
Gorry Fairhurst gorry@erg.abdn.ac.uk
Joerg Deutschmann joerg.deutschmann@fau.de - Project Info
Implementing a Careful Resume server and testing with new clients; Adding QLOG support. - Documents
https://www.ietf.org/archive/id/draft-ietf-tsvwg-careful-resume-04 - Implementations
https://github.com/ana-cc/quiche
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.