IETF 96 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 July 16, 2016 and Sunday July 17, 2016
Where: Intercontinental Berlin (Potsdam III)
Signup for the Hackathon here: Hackathon Registration
View the list of Hackathon Attendees: Attendees
Keep up to date by subscribing to https://www.ietf.org/mailman/listinfo/hackathon
The Hackathon is free to attend.
Agenda (subject to change)
Saturday, July 16
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, July 17
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, July 18-22, for people to gather and collaborate on hackathon activities
A table at Bits-N-Bites on Thursday, July 21, for hackathon participants to share their projects with the IETF community at large
Meeting Materials
Prep Call, Wednesday, July 6, 2016, 7:00 am (San Francisco, GMT-07:00)
-
Code can be accessed from
IETF Hackathon Github or from links provided for within project descriptions below.
Request to be added to IETF Github organization by sending your Github ID to Charles Eckel
eckelcu@cisco.com
-
Follow Teams through Hackathon and Bit-n-Bites -
Video
Technologies Included in Hackathon (more can be added)
I2RS
ACTN
Champion(s)
Volunteers
Satish K, Haomian Xheng, Victor Lopez, Yan Boyuan, Wang Wei etc
Remote
Project(s)
ACTN (Abstraction and Control of TE network)
Setup a hierarchy of controllers
Project 1 - Extend for multi-destination option ( i.e. selection of an endpoint from a possible list)
Project 2 - Survivability Analysis
For this project(s) we would be using ONOS platform
-
The code repository to be used -
GitHub
Detailed information at -
PCE based Central Control
Champion(s)
Volunteers
Remote
Project(s)
PCE based Central Control
PCEP over TLS (PCEPS)
For this project(s) we would be using ONOS platform
Code repository to be used -
GitHub
Detailed information at -
BGP-Flowspec/BGP-LS
Champion(s)
Volunteers
Dong Jie, Gaurav Agarwal, Oscar, Jeff Tantsura, Alessio Giorgetti
Remote
Project(s)
BGP-LS
BGP-Flowspec
For all the projects we would be using ONOS platform
Detailed information at -
Exporting topology learned from network via BGP-LS to a NBI using IETF Topology yang models
YANG/NETCONF/RESTCONF
Champion(s)
Project(s)
Benoit Claise: improve YANG model monitoring tools at claise.be (confd, new graphs, bug fix)
Hari Ananthakrishnan (On Sunday): Improve YANG tools (xym)
Carl Moberg, Reshad Rahman, Victor Kuarsingh: YANG module catalog (draft-openconfig-netmod-model-catalog-01)
Qin Wu,Yuming Xie,Michale Wang: Web based YANG Tool for module catalog
-
-
-
Vinod Kumar/Tianran Zhou: YANG compiler annotation implementation on ONOS
William Lupton (From Saturday pm): pyang yang-edit
and html
output formats
DNS/DNSSEC/DPRIVE/DANE
Champion(s)
-
Allison Mankin
Sara Dickinson
Melinda Shore
Willem Toorop
Tim Wicinski
Rick Lamb
Project(s)
Applications that use DNSSEC, DANE and
DNS privacy via getdns (Python,node.js, or C)
TLS and
DNS interfaces, including but not limited to the TLS
DNS chain extension
Completion and interop of edns keep-alive implementations (getdns, unbound, others) and testing of connection management by servers
RFC 5011 implementation and testing in getdns
-
Continued work on other projects from Hackathon 95
Make BIND work with smartcards without patches (Rick Lamb)
I've had this site for some time
http://ri.co.cr/ and many are using its contents for their own DNSSEC deployments (including a CCTLD or two). Problem is BIND currently must be patched to support this (originally 2008) mod. Every time BIND gets updated surgery needs to be done to make the patch work again. The solution I am offering is to write a PKCS11 intermediate driver that BIND can use in NATIVE PKCS11 mode to use any smartcards OpenSC supports. Initial tries show promise. At the Hackathon I would like to press this to the next step and publish.
DNSSEC deployment maps (Dan York)
Other projects TBD - please suggest and/or come join us with them
WebRTC/NUBOMEDIA/Kurento
LMAP
Champion(s)
Project(s)
lmapd integration with libnetconf2 or sysrepo or … to support RESTCONF (Juergen)
Implement a controller that controls a number of measurement agents
Implement a reporting task that sends results via RESTCONF to a collector
Implement a collector receiving results and storing stuff in a database
Packaging and integration into OpenWrt, Debian, Mac Ports, …
Internet measurement trials driven by lmapd
Integration with the IPPM metrics registry
ILA
NETVC
Champion(s)
Project(s)
Resources:
TLS 1.3
SFC
Champion(s)
Christophe Fontaine
Jerome Tollet
Project(s)
Mininet integration of VPP for SFC
Explore stateful usecases in VPP (Load balancing in a service chain, … )
SCTP and WebRTC Datachannels
Media Address Resolver Service (MARS)
IoT bootstrapping for Noobs with EAP-NOOB
Champion(s)
-
-
Raghavendra Mudugodu
Shiva Prasad
Project(s)
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@ietf.org 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:
Your-Technology-Name
To request a wiki account, please click on the login button on the bottom right corner of the page, and choose register. If you need a new password please click on the login button on the bottom right corner of the page and choose Send new password.
Webinar
Participant Preparation and Prerequisites
Bring a laptop on which you are comfortable developing 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: hackathon@jabber.ietf.org
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.