IETF 101 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: Saturday and Sunday, March 17 and 18, 2018
Where: Hilton London Metropole, Room: Sovereign
Sign up for the Hackathon here: Register
View the list of registered Hackathon attendees: Attendees

Keep up to date by subscribing to

The Hackathon is free to attend and is open to everyone.


Saturday, March 17
      08:00: Room open for setup by project champions    
      09:00: Room open for all - Pastries and coffee provided
      09:30: Hackathon kickoff 
      09:45: Form Teams
      12:30: Lunch provided
      15:30: Afternoon break - Snacks provided
      19:00: Dinner provided
      22:00: Room closes but is NOT locked
  Sunday, March 18
      09:00: Room opens - Pastries and coffee provided
      12:30: Lunch provided
      13:30: Hacking stops, prepare brief presentation of project
      14:00: Project presentation to other participants and judges
      15:45: Closing remarks and opportunities for next time
      16:00: Hackathon ends
      17:00: Tear down complete

For your planning purposes, be aware that we will also have:

  • Code Lounge: Space for groups to gather and collaborate on running code. View the schedule and reserve space for your team/project.
  • Hot RFC: Lightning talks Sunday, 18 March 18:00-19:00. Submit your proposal related to your hackathon project. Deadline is noon Sunday.
  • Hack Demo Happy Hour: Share your hackathon project with IETF community, Monday 18:00 - 20:00 in Code Lounge. Register for space to demo your project.

Meeting Materials

Participant Preparation and Prerequisites

  • Champions will have table signs on the center of their table identifying their project and be available to answer questions at the start and throughout the hackathon. Optionally, champions may create and display posters on flip charts with additional information on their project. 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
  • Development Environment
    • Bring a laptop on which you are comfortable developing software
    • Some projects may require installing additional software or make use of VMs
    • Installing and becoming familiar with VirtualBox or something similar will help
    • Note to champions: if planning to make use of VMs, please bring on USB drives to make available to others as download times can be painful
    • Specific coding languages are called out for some of projects (e.g. Python, Java), but this is heavily dependent on the project(s) you choose
  • Network
    • Wireless access to the IETF network will be provided, and from there to the outside world
    • Wired access to the IETF network is available by request only
    • If you have additional requirements, email Charles Eckel: eckelcu@
  • Code Lab
    • Thanks to Comcast and Arris, we have the ability to create experimental networks. We also have access to a CMTS and cable modems to simulate home networks. Email requests for these to Charles Eckel: eckelcu@ and Chris Tuska: Chris.Tuska@
  • 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
  • Training Materials

Remote participation

  • Participating in person is preferred, but we understand not everyone can travel. If you want to participate remotely, please contact the champion(s) for that project to determine how best to coordinate.
  • Jabber room:
  • Meetecho: Active and recorded Saturday from 09.30-10.00 and Sunday from 14.00-16.00

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)


ARC (related to DMARC WG)

  • Champion(s)
    • Kurt Andersen
  • Project(s)
    • Interoperability Validation across all known implementations
    • Experimenting with strategies for crypto algorithm evolution

Multilingual email

  • Champion(s)
    • Nik Tomkinson (rfc.nik.tomkinson at
  • Project(s)


  • Champion(s)
    • Lars Eggert (lars@…)
  • Project(s)
    • Interop testing of current "implementation draft" (likely 08 or maybe 09)

Scalable, Privacy-preserving In-Network (SPIN Bit) Measurement

  • Champion(s)
    • Brian Trammell (ietf@…)
  • Project(s)
    • Passive transport measurement using
      • TCP SEQ/ACK RTX/loss
      • QUIC spin bit RTT/loss event
    • QUIC Spin Bit development and interop (note: this is separate from QUIC to not distract from -08 / -09 interop, but we'll set up next to the QUIC table)
    • QUIC loss/reordering measurement signals bake-off

Architecture measurements

Public interest technology

  • Champion(s)
    • Mallory Knodel
  • Project(s)
    • HTTP status code 451
    • Measuring leakage from IoT with a MITM proxy
    • WebRTC Apple discoverability, IP route leaks
    • Web protocol privacy considerations
    • Privacy impact assessment tool on RFCs.

ANIMA voucher and ACP

  • Champion(s)
    • Michael Richardson
  • Project(s)
    • use of the ANIMA BRSKI for enrollment of devices into a PKI
    • use of IPsec and RPL to construct the ANIMA ACP overlay between devices
      • ACP construction can include people who are remote!


  • Champion(s)
    • Bron Gondwana
    • Neil Jenkins
  • Project(s)
    • Interoperability testing
    • Check that spec covers client needs


  • Champion(s)
    • Martine Lenders
  • Project(s)
    • Implementing (parts) of draft-dhcwg-dhc-rfc3315bis for the RIOT operating system. Main focus will be to replace the proprietary UHCP client implementation with DHCPv6 prefix delegation. If time permits address assignment via DHCPv6 will also be implemented.
    • There's also a plan to extend Kea DHCP server to provide Netconf interface, see down below in the Yang/Netconf? section.

SACM/XMPP Interface Discovery

Making Multicast IP more successful

  • Champion(s)
    • Lucas Pardue (lucas.pardue at
  • Project(s)
    • HTTP over multicast QUIC (draft-pardue-quic-http-mcast-02)
      • Uplift of sender application to IETF QUIC wire format
      • Uplift of receiver application to IETF QUIC wire format
      • (note: this is a separate activity to the QUIC interop)
    • Browser HTTP Server push API
      • Further exploration and interop of server push API
  • Champion(s)
    • Jake Holland ( at
  • Project(s)
    • An open reference platform implementing an "AMT Gateway" as described in BCP 213 section 3.3 (
      • Integrate amtgwd into a quagga image
      • Add support for pimd. (build membership reports from kernel forwarding table instead of forwarding a received membership report)
      • Publish a deployable distro

WebRTC Data Channels

  • Champion(s)
    • Lennart Grahl (lgrahl@…), Felix Weinrank (weinrank@…), Michael Tüxen (tuexen@…)
  • Project(s)

WISHI (Work on IoT Semantic / Hypermedia Interoperability)

For WISHI (Work on IoT Semantic / Hypermedia Interoperability), we meet in person at IETF101 at the Hackathon. For latest draft agenda, see

Interoperation between NEAT and PvD (provisining domains - intarea)

Limited Usage of Remote Key (LURK) for TLS1.2

  • Champion(s)
    • Daniel Migault (daniel.migault@…), Dmitry Kravkov (Qwilt), Sanjay Mishra (Verizon)
  • Project(s): LURK implementation on providing an interface between a cryptographic service (Key Server) and an Edge Server (TLS servers) terminating TLS sessions.
    • Implementing LURK for TLS1.2: (draft-mglt-lurk-lurk and draft-mglt-lurk-tls12)
    • Integrating LURK with NGINX Web Server.
    • YANG models for configuring LURK Client / LURK Server
    • Measuring LURK performances
    • Porting LURK on UDP/DTLS
    • Porting LURK on TCP/TLS


  • Champion(s)
    • Benoit Claise
  • Project(s)
    • Joe Clarke, Benoit Claise
    • yuma123: Vladimir Vassilev - yang-push testcase, validation, interoperability: report

YANG based EVC Service Modeling in OpenDaylight?

  • Champion(s)
    • Mahesh Jethanandani (mjethanandani at
  • Project(s)
    • Demonstrate configuration and management of E-Line, E-LAN, and E-Tree Services in OpenDaylight?, Santanu De (Xoriant), Kiran Ambardekar (Xoriant), Shrinivas Joshi (Xoriant)
    • Use Postman and other tools to invoke REST APIs to configure, update, and delete services, Santanu De (Xoriant), Kiran Ambardekar (Xoriant), Shrinivas Joshi (Xoriant)

YANG/Netconf interface in Kea DHCPv6 server

  • Champion(s)
    • Tomek Mrugalski (tomasz(dot)mrugalski(at)
    • Expected participants: Razvan Becheriu, Andrei Pavel, Francis Dupont, Mathias Ehrlin (?)
  • Project

DTN (Delay Tolerant Networking) - Bundle Protocol v7 PoC Python implementation

LPWAN: IPv6 compression+fragmentation implementation and testing, a shot at ICMPv6

6LoRITT: 6LoWPAN Interoperability Testing Sessions (plugtest) with the F-Interop Testing Platform

  • Champion(s)
    • Alain Ribault (firstname.lastname at kereval dot com)
    • Benjamin Tertereau (firstname.lastname at kereval dot com)
  • Project(s)
    • 6LoWPAN interoperability testing sessions (plugtest)
    • At the hackaton, we'll organize a 6LoWPAN plugtest using the F-Interop Testing Platform
    • F-Interop Testing Platform is composed of a website (test management) describing the tests to realize and gathering tests results and of agents (sniffer) to collect test logs to be analyzed
    • The tests cover the following RFCs:
      • 1) RFC4944: Transmission of IPv6 Packets over IEEE 802.15.4 Networks
      • 2) RFC6282: Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks
      • 3) RFC6775: Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)
    • We'll come with an implementation based on linux-WPAN running on a RPi and the radio chip
    • For the testing session, we could provide the agents (sniffer)
    • During the hackaton, we'll discuss about the needs of such a testing platform for 6lo and other protocols

WebRTC Identity

  • Champion(s)
    • Harald Alvestrand <harald at>
  • Project(s)
    • Use Firefox' "identity" API to perform protection of WebRTC media channels
    • Set up at least one, maybe several, identity providers and see if they interoperate


ICN for critical, time sensitive systems.

  • Champion(s)
    • Pete Maynard <p.maynard at>
  • Project(s)
    • Map a field bus protocol (IEC101/4, TSN, OPC UA) to an ICN implementation CCN/NDN.
    • Develop an application gateway to a: a) Physical PLC b) Raspberry Pi Traffic lights c) VM Software based PLC emulator.
    • Develop a HMI web interface to control remote devices via ICN.
    • Identify key performance indicators (KPI) for SCADA systems over ICN.

IETF Mailing List Analysis

  • Champion(s)
    • Nick Doty <npdoty at>
  • Project(s)
    • Bigbang open source mailing list/community analysis software
    • What statistics/questions do you have about mailing list activity or IETF participation?
    • Crawling/collecting new IETF mail archives format

DOTS Interop

  • Champion(s)
    • Kaname Nishizuka
    • Jon Shallow
    • Liang 'Frank' Xia
  • Project(s)
    • DDoS Open Threat Signaling (DOTS).
      • The aim of DOTS is to develop a standards based approach for the realtime signaling of DDoS related telemetry and threat handling requests and data between elements concerned with DDoS attack detection, classification, traceback, and mitigation.
    • We will test the interoperability between 4 independent implementations:
      • The primary goal is to test the interoperability of signal-channel (CoAP over DTLS) of DOT protocol.
  • Specifications
  • Implementations

Messaging Layer Security

NFV on a Federated and Orchestrated Virtualisation Platform

Firmware Updates for Internet of Things

  • Champion(s)
    • Hannes Tschofenig <Hannes.Tschofenig at>
  • Project(s)
    • The main goal is to get hands-on experience with the firmware update mechanism and the manifest format. We will start on Saturday with a short tutorial to reach a common understanding and then start implementing the manifest functionality, particularly the security features, on IoT development boards. The boards will be made available by Arm.
  • Useful links:

ECN / AQM Testing & Interop

  • Champion(s)
    • Dave Plonka, Kyle Rose, Igor Lubashev, Mojgan Ghasemi
  • Project(s)
    • Performance comparison w/ & w/o ECN/AQM of content delivery from Akamai origin through ECN-capable router(s) and with varying host congestion control algorithms

TLS 1.3

  • Champion(s)
    • Nitin Mutkawoa (jmutkawoa at - remote
    • Loganaden Velvindron (logan at - remote
    • Codarren Velvindron (codarren at -remote
    • Pirabarlen Cheenaramen (selven at - remote
  • Project(s)
    • TLS 1.3 for applications (OpenSSL preview release)
    • Test and Interop with latest drafts if time permits
  • XMPP/Jabber link: TLSHackathon on

Interface to Network Security Functions (I2NSF) Framework

EAP TLS with large certificates and long certificate chains

  • Champion(s)
    • Aleksi Peltonen <aleksi.peltonen at>
    • Mohit Sethi <mohit at>
  • Project(s)
    • Test EAP-TLS 1.2 implementations with large certificates and long chains
    • We will use open source wpa_supplicant and hostapd implementations
    • We will have an enterprise D-Link wireless AP for experimentation
    • Our goal is to collect statistics with different types of certificates and long certificate chains as input to the EMU working group

DNS Service Discovery (DNSSD)

Network Time Security (NTS)

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 hackathon@ 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 4 years ago Last modified on 25/10/18 13:55:58