User Tools

Site Tools


IETF 97 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 November 12, 2016 and Sunday November 13, 2016

Where: Conrad Seoul, Park Ballroom 1 and 2

Signup for the Hackathon here: Hackathon Registration

View the list of Hackathon Attendees: Attendees

Keep up to date by subscribing to

The Hackathon is free to attend.

Agenda (subject to change)

  Saturday, November 12
      09:00: Room opens - Pastries and coffee
      09:00: Posters of all technologies on display
      09:30: Hackathon kickoff 
      09:45: Form Teams
      12:30: Lunch
      15:30: Afternoon break - Snacks provided
      18:30: Progress check and sharing
      19:00: Dinner
      22:00: Room closes and is locked
  Sunday, November 13
      09:00: Room opens - Pastries and coffee 
      12:30: Lunch 
      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

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

  • Space reserved in the IETF Lounge throughout the week of IETF, November 14-18, for people to gather and collaborate on hackathon activities
  • A table at Bits-N-Bites on Thursday, November 17, for hackathon participants to share their projects with the IETF community at large

Meeting Materials

Technologies Included in Hackathon (more can be added)

DDoS Open Threat Signaling (DOTS)


Interface to the Routing System(I2RS)

  • Champion(s)
  • Project(s)
  • I2RS RIB - Getting the code to run with Quagga
    • code: ConfD for netconf client and netconf agent
    • routing code: routing deamon + quagga code
    • The work between IETF 96 and IETF was OBE (overcome by events)
  • I will be working on getting the code compiled into the quagga deamon and debugged.
  • If you are a quagga expert, I would appreciate you dropping by on Saturday pm.
  • Watch for code releases between IETF97 and IETF 98

TLS 1.3

  • Champions
  • Project(s)
    • NSS (EKR, Martin Thomson)
    • BoringSSL (David Benjamin, Nick Harper, Steven Valdez)
    • mBed TLS (Hannes Tschofenig)
    • Mint (Richard Barnes)
  • Targets: achieve interop at draft-18, including 0-RTT


  • Champion(s)
  • Project(s)
    • Benoit Claise: improve YANG model monitoring tools at (yuma compiler, bugs fix)
    • Joe Clarke, Carl Moberg (remotely), Benoit Claise: YANG catalog (
    • Qin Wu,Zitao Wang,Yumin Xie (remotely): YANG model statistics publication
    • Hariharan Ananthakrishnan
    • Vinod Kumar (remotely): help with xym, the YANG extraction tool
    • Victor Kuarsing (Sunday)
    • Kent Watsen: reference implementation of the call home draft
    • Gaurav Agarwal : YANG based common driver implementation in ONOS, compiler annotation extension for MAP generation
    • Rob Wilton: pyang plugin - mapping combined config/state YANG models to split config/state models (IETF and/or OpenConfig structure).



  • Champion(s)
  • Project(s)
    • Use of different protocols as ACTN interface
      • BGP-LS / PCEP-LS / PCEP
      • RestConf / Yang
    • Possible inter-op issue resolution
  • WG
    • TEAS
      • ACTN Requirements and Framework
      • Yang Models
    • PCE
      • Stateful H-PCE, PCEP-LS
    • IDR
      • BGP-LS

Multipath TCP




SFC Service Function

  • Champion(s)
  • Project(s)
    • Service Function Development Kit
      • We are intending to make it easier to develop NSH-enabled ServiceFunctions written in C/C++.
      • Would you like to migrate an existing Service Function to have NSH awareness?
      • Within Sandvine's private cloud “Nubo” we will create and test a simple NFV service function using the library we are developing. Within this environment, traffic will be sent to the Service Function from Sandvine's Traffic Steering Engine (a classifier and SFF).
  • Skills that we would appreciate:
    • C/C++
    • DPDK
    • VPP (
    • Ubuntu
    • Doxygen
    • Make

Capturing and analyzing network data features

Interface to Network Security Functions (I2NSF) Framework

Vector Packet Processor (VPP)

  • Champion(s)
  • Project(s)
    • Have some fun using Open Source's Vector Packet Processor (VPP)
    • Breaking the internet with a high-perf stateless-TCP file server.
    • Add gRPC + protobuf for VPP.

LoRaWAN Wireshark dissector

  • Champion(s)
    • (only available on Sat)
  • Project(s)
    • develop a Wireshark dissector for LoRaWAN to be used in the LPWA Working Group.
    • preferably in C (full integration with Wireshark recompilation), but easier alternatives can be discussed based on contributors expertise (lua, WSGD)
    • [update] I was pointed at as an (almost complete?) project for a LoRaWAN dissector. We'll check it out.

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 request a wiki account, please click on the login button on the top right corner of the page, and choose register. If you need a new password please click on the login button on the top right corner of the page and choose Send new password.

Participant Preparation and Prerequisites

  • Bring a laptop on which you are comfortable developing software
    • Some projects may require installing additional software
  • Familiarity with the technology area(s) in which you plan to participate will certainly help
  • Brief introductions will be provided at the start of the Hackathon by the champions associated with each technology
  • Your laptop is the default development platform for each technology
  • Anything else that is required will be provided, such as VMs you can install on our laptop or access from your laptop
    • 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
  • Wireless access to the IETF network will be provided, and from there to the outside world
  • Wired access to the IETF network will be provided as well
  • Git/GitHub is commonly used for open source projects. Familiarizing yourself with it is recommended.
  • Champions for each technology are encouraged to share any other things they think would be helpful in preparation for the hackathon

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:

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.

97hackathon.txt · Last modified: 2016/12/09 17:39 by