Version 33 (modified by ari.keranen@…, 2 years ago) (diff)


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 TBD
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 of posters at tables by projects 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 and is 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:00: Recap and suggestions for improvements
      15:30: Awards presented, prizes given
      16:00: Hackathon ends
      17:00: Tear down complete

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

  • Code Lounge: Space reserved in the IETF Lounge throughout the week of IETF, March 19-23, for groups to gather and collaborate on running code.

Meeting Materials

  • IETF Hackathon Prep Call - Will be scheduled for sometime during the week before the hackathon
  • Presentations can be uploaded and accessed from
    • Send presentations you want uploaded to Charles Eckel: eckelcu@
  • 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 Charles Eckel: eckelcu@

Participant Preparation and Prerequisites

  • Champions will have posters describing their project(s) and be available to answer questions at the start and throughout the hackathon
    • 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 will have a rack of equipment that includes a CMTS, cable modems, and VMs on demand. If you have questions or want access to generic VMs, a CMTS, a home network environment, etc., email 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.

Technologies Included in Hackathon (add your project using the template provided)


  • Champion(s)
    • Stéphane Bortzmeyer bortzmeyer+ietf at
  • Project(s)
    • Implementing draft-woodworth-bulk-rr in NSD? Possible application: porting to IPv6 (where you need dynamicity, you cannot pre-generate all the names)

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)

(Privacy-Friendly, Scalable, Passive/Hybrid?) Transport Measurability

  • 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

Public interest technology

  • Champion(s)
    • Mallory Knodel
  • Project(s)
    • Human rights impact assessments: How do we know this works? Specific assessments include: TBA.
    • HTTP status code 451
    • Other TBD (note: additions, edits welcome).

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


SACM/XMPP Interface Discovery

  • Champion(s)
    • Adam Montville
    • Bill Munyan
  • Project(s)

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

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

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.