IETF 108 Hackathon

The Internet Engineering Task Force (IETF) is holding a Hackathon to encourage developers to discuss, collaborate and develop utilities, ideas, sample code and solutions that show practical implementations of IETF standards.

When: Monday July 20 through Friday July 24, 2020
Where: IETF 108 is an online only meeting and so is the Hackathon.
Sign up for the Hackathon here: Register.
View the list of registered Hackathon attendees: Here
IETF link:
Gather guidelines:
Hackathon Survey: Here

Keep up to date by subscribing to

The 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.



NOTE: You will need a datatracker account to login to the Hackathon Meetecho sessions and When you register for the hackathon, you are sent a separate email to create a datatracker account. If you already have a datatracker account, please ensure that the email address you registered with is added to your account. If you received the email but the link to create an account has expired, please see the instructions below:

  1. Go to
  2. Select ‘new account’ from the User menu at the top
  3. Enter the email address that you registered with for the hackathon
  4. Follow the instructions in the email you receive

Meeting Materials

Participant Preparation and Prerequisites

  • Choosing a Project
    • Champions post and lead projects
    • How and when teams meet during the week is up to them
    • Details on each project and links to additional information for each project are in this wiki in the "Projects Included in Hackathon" section
    • 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, Java), 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
    • IETF Hackathon GitHub Org
      • If you would like to have your project/code hosted here, send your GitHub ID and the name of your project via email to Charles Eckel:
  • Training Materials
  • Champions for each technology are encouraged to share any other things they think would be helpful in preparation for the hackathon
  • Project Presentations
    • All teams have the opportunity to present what they did on Friday during the closing session of the Hackathon.


Virtual IETF network for the Virtual Hackathon.

The NOC team has been working to allow you to join the IETF network while attending the meeting remotely. With a Raspberry Pi 2 or newer the NOC has a recipe that will allow your team to be virtually connected to the IETF network with IPv4 and IPv6 addresses and many options (IPv6ONLY, a closed user group, NAT64, IPv6PD, and more) for you to use for your projects. Your project champion can request getting access by sending a message to ietf108virtualnetwork @ Please include your project name and members. The NOC will provide you with the recipe.

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 closing presentations will be available via Meetecho. The hackathon Jabber room 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 participant's organization and/or open source project 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 (add your project using the template provided at end of project list)

  • Note, all projects are open to everyone. However, some champions have identified their projects as being particularly good for first time IETFers and/or first time hackathoners. 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.

BGP Monitoring Protocol (BMP)

Sliding Window FEC codec (SWIF)

IP Wireless Access in Vehicular Environments (IPWAVE) Basic Protocols

Interface to Network Security Functions (I2NSF) Framework

Intent-based, assurance, telemetry



  • Champion(s)
    • Lars Eggert <lars@…>
  • Project(s)
    • Interop around the latest set of implementation drafts

QUIC Measurements

  • Champion(s)
    • Jari Arkko <jari.arkko@…>
  • Participants: Cociglio Mauro, Nilo Massimo, Jari Arkko, Szilveszter Nadas, Bulgarella Fabio, Markus Ihlar, Alex Yu, Ferenc Fejes, Zaheduzzaman Sarker, Mirja Kuhlewind and possibly others!
  • Project(s)
    • Add exciting new measurement features!
    • Interop around the latest QUIC versions
    • Integrate and test recent feature and code requests
  • Join our daily call at 3PM (July 20-24) to discuss and tell us about your idea. Get call parameters from Jari Arkko (address above).


Network Time Security (NTS)

Low Latency, Low Loss, Scalable Throughput (L4S)

Network Interconnect Tester

CoAP Group Communication

CoRE Resource Directory Access Control

ACE Group Key Controller

NMRG Intent Based Networking (IBN) Cluster

  • Champion(s)
    • Walter Cerroni <walter.cerroni@…>
    • Davide Borsatti <davide.borsatti@…>
    • Barbara Martini <barbara.martini@…>
    • Molka Gharbaoui <molka.gharbaoui@…>
    • Bezahaf, Mehdi <mehdi.bezahaf@…>
    • (NMRG co-chair) Laurent Ciavaglia <laurent.ciavaglia@…>
    • (NMRG co-chair) Jérôme François <jerome.francois@…>
  • Project(s)
    • A Multi-Level Approach to IBN (Walter, Davide, Barbara, Molka)
    • Service Protection Period Intent (Mehdi)
  • Related IETF 108 Hackathon projects:
    • Intent-based, assurance, telemetry
    • Interface to Network Security Functions (I2NSF) Framework

In-situ Flow Information Telemetry (IFIT)

Application-aware IPv6/SRv6 Networking (APN6)

Software Update for the Internet of Things (SUIT)

LPWAN SCHC header compression and fragmentation

  • Champion(s)
    • Laurent Toutain (IMT Atlantique) laurent dot toutain at imt dash atlantique dot fr
    • Cedric Adjih (INRIA) cedric dot adjih at inria dot fr
    • Shoichi Sakane (Cisco) ssakane at cisco dot com
    • Olivier Gimenez (Semtech) ogimenez at semtech dot com
    • Dominique Barthel (Orange Labs) dominique dot barthel at orange dot com
  • Logistics
  • Project(s)
    • provide setup for testing interoperability between several implementations.
      • provide set of Rules (in the openSCHC format) and packets to be compressed/fragmented in an offline fashion We will provide test packets as text files containing JSON hex string.
      • A first test will be that some packets are compressed and compared to the known SCHC Packet output. Some SCHC Packets are decompressed and compared to the known packet output. Each implementation can perform this test independently of the others.
      • If time permits, the No-ACK mode of fragmentation can be tested the same way as compression: first with test vectors, second with direct unidirectional communication between two implementations.
      • setup server for live interop test
      • A second test is to interconnect two implementations in real time, and to compare the decompressed output with the original packet (before compression). This allows for some degree of random testing. The direct communication between two implementations will use UDP sockets.
    • for documentation about SCHC, see
    • Other goals can be to advance the python open source implementation of SCHC compression and fragmentation. See
      • improve the tutorial. In general, make it easier for a newcomer to join the project and contribute.
      • iron out implementation to fit latest draft revisions
      • interface to underlying network (UDP or interface to real hardware)

Don’t see anything that interests you? Feel free to add your preferred technology 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 technology, we strongly suggest that you send email to to let others know. You may generate interest in your technology, 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:


  • Champion(s)
    • tbd
  • Project(s)
    • tbd

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.

Last modified 22 months ago Last modified on 08/11/20 10:38:40

Attachments (1)

Download all attachments as: .zip