IETF Meeting Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
{{ :94hackathon.jpg?500|}}

==== IETF 95 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 April 2, 2016 and Sunday April 3, 2016

**Where:** Hilton Buenos Aires (room [[https://https://tools.ietf.org/agenda/95/venue/?room=atlantico-c|Atlantico C)]] 
                                                        
**Signup for the Hackathon here:** [[https://www.ietf.org/registration/ietf95/hackathonregistration.py|Hackathon Registration]]

**View the list of Hackathon Attendees:** [[https://www.ietf.org/registration/ietf95/hackathonattendance.py?sortkey=3&login=%0A|Attendees]]

Keep up to date by subscribing to [[https://www.ietf.org/mailman/listinfo/hackathon|https://www.ietf.org/mailman/listinfo/hackathon]]

The Hackathon is free to attend.

----

==== Agenda (subject to change) ====
    Saturday, April 2
        09:00: Room opens - Pastries and coffee provided
        09:30: Hackathon kickoff - Intro to all technologies by champions, form teams
        12:30: Lunch provided
        15:30: Afternoon break - Snacks provided
        18:30: Progress check and sharing
        19:00: Dinner provided
        22:00: Room closes and is locked
    Sunday, April 3
        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

----

==== Meeting Materials ====
     * Presentations can be uploaded and accessed from the [[https://www.ietf.org/proceedings/95/hackathon.html|IETF Hackathon Team page]]
     * Code can be accessed from the [[https://github.com/ietf-hackathon|IETF Hackathon github]] or from links provided for within project descriptions below.
     * [[https://isoc.app.box.com/v/ietf95-hackathon|Photos]]

----

==== Technologies Included in Hackathon (more can be added) ====

**DNS/DNSSEC/DANE/DNS-over-(D)TLS**
     * Champions/Hackers
       * Coordinator: Allison Mankin <allison.mankin@gmail.com> 
       * Benno Overeinder, Willem Toorop, Ralph Dolman
       * Sara Dickinson, John Dickinson
       * Shane Kerr
       * Shumon Huque
       * Dave Lawrence
       * Daniel Kahn Gillmor
       * Linus Nordberg (remote)
       * Melinda Shore (remote)
       * Gowri Visweswaran (remote)
       * Jan Včelák
       * Evan Hunt (plus others on BIND team, reporting separately)
       * Dan York
       * All welcome, remote participants welcome
     * Project(s)
       * Library-independent interfacing with TLS
       * NSSWITCH getdns 
       * EDNS0 chain query 
       * DNSSEC cyber-ledger 
       * getdns version for Raspbian 
       * automated DNSSEC key maintenance/rollover scheduling tool for BIND
       * DNS over TLS and TCP out-of-order processing in [[https://www.knot-resolver.cz|Knot Resolver]] ([[https://gitlab.labs.nic.cz/knot/resolver/merge_requests/18/diffs|merge request]])
       * And more 

**Network Based Metrics Analytics**
     * Champion(s)
       * Pål-Erik Martinsen (palerikm@gmail.com)

     * Project(s)
       * Can a simple traceroute based metrics be used by a ML algorithm to find network problems (Ofcourse, but how..)
       * A zeppelin frontend to an apache spark cluster is available to run the analytics 
       * Runs at http://52.19.189.184:8888/ (ietf/ietf95)
       * Traceroute client that posts data to a database can be found at: https://github.com/NATTools/STUNTrace

**NETCONF/YANG, I2RS, OpenDaylight**
     * Champion(s)
       * YANG: Benoit Claise 
       * Susan Hares <shares@ndzh.com>
       * Kent Watsen
     * Project(s)
       * Eric Voit: Exending ODL's [[https://www.opendaylight.org/opendaylight-features-list#YANG PUBSUB|YANG PubSub Client implementation]] released in Beryllium.  See [[https://datatracker.ietf.org/doc/draft-ietf-netconf-yang-push/|draft-ietf-netconf-yang-push]]) 
       * Benoit Claise: improve YANG model monitoring tools at claise.be
       * Qin Wu and ANURAG BHARGAVA: tools to extract the info from YANG models to populate the catalog (draft-openconfig-netmod-model-catalog-00) 
       * Qin Wu and Dapeng Liu: pyang in the submission tool => include all the existing YANG models in the path.
       * Kent Watsen: Update https://github.com/Juniper/netconf-call-home
       * Mahesh Jethanandani, Daniel King (TBC), Lee Howard (TBC), William Lupton (Sunday) : YANG Development Kit and YANG explorer integration. See https://github.com/CiscoDevNet/ydk-py and https://github.com/CiscoDevNet/yang-explorer
       * Working remotely, Munish Nayyar, Pravin Gohite, Abhishek Keshav: YDK and YANGExplorer
       * Hariharan Ananthakrishnan: symd improvement. See http://gitlab.cisco.com/einarnn/symd
       * Dean Bodganovic
       * Ebben Aries
       * David Lamparter: code generation bridge between YANG schemas and Cap'n Proto schemas

**NETVC**
     * Champion(s)
       * Tim Terriberry
       * Thomas Daede <tdaede@mozilla.com>
     * Project(s)
       * Updates to the "Are We Compressed Yet" tools

**IBNEMO(Intent Based Network Modeling)**
     * Champion(s)
       * Tianran Zhou <zhoutianran@huawei.com>
     * NEMO Language is an Intent oriented network DSL (domain specific language) and NBI. Operator/End-user or 3rd party can use it to program network resource and behavior in their service applications. It's now being implemented in OpenDaylight (https://wiki.opendaylight.org/view/NEMO:Main).
     * Goals
       * Come up with an initial toolset to produce and manipulate NEMO
       * Implement the use cases as a proof of concept for NEMO
     * Tasks
       * set up the integration environment
       * develop applications to use the NEMO API
       * develop an Eclipse based NEMO editor
       * develop other useful tools
     * Possible use cases
       * end to end carrier network including vCPE
       * virtual private cloud integrating NetIDE
     * Prerequisites
       * Editor
         * Eclipse MARS with modeling tools
         * Xtext
       * Controller
         * OpenDaylight (see reference)
         * Mininet (VMs will be provided)

**Homenet**
     * Teaming with VPP on source address dependent routing (SADR)
     * Need to have some multi prefix setup to show that it works
     * Hoping to recruit Homenet or MIF people with multi prefix stacks – eg. take work from the last IETF and insert VPP

**RIOT (OS for internet of things)**
     * Champion(s)
       * TBD
       * 
     * Project(s)
       * TBD

**[[https://fd.io/|Vector Packet Processing]]**
     * Champions(s)
       * Ole Trøan
     * Project(s)
       * Source Address Dependent Routing [[https://tools.ietf.org/html/draft-ietf-rtgwg-dst-src-routing-01]]
       * Code: git clone https://gerrit.fd.io/r/vpp

**TLS 1.3**
     * Champions(s)
       * Nick Sullivan
     * Project(s)
       * TLS 1.3 interoperability testing (NSS, Golang, etc.)
     * Attending:
       * Eric Rescorla ([[https://github.com/nss-dev/nss|NSS]])
       * Richard Barnes ([[https://github.com/bifurcation/mint|mint]])

**SCTP**
     * Champion(s)
       * Randall Stewart <rrs@lakerest.net>
       * Michael Tüxen <tuexen@fh-muenster.de>
     * Project(s)
       * Progress the implementation of [[https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata|draft-ietf-tsvwg-sctp-ndata]] for the FreeBSD kernel stack ([[http://svnweb.freebsd.org/base/head/|src]]) and the userland stack ([[https://github.com/sctplab/usrsctp|usrsctp]]). The development is done in the GitHub repository [[https://github.com/sctplab/sctp-idata|i-data]].
       * Use and improve I-DATA test scripts for [[https://github.com/nplab/packetdrill|packetdrill]].
       * General SCTP improvements.


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.

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**//.

----
==== 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. 
       * A basic tutorial is provided in the previous post: https://mailarchive.ietf.org/arch/msg/92hackathon/lM8Ag_is4a00PsudnzaqdV1vhoE
       * Github project for hackathon presentations and code: https://github.com/eckelcu/ietf-hackathon
     * Champions for each technology are encouraged to share any other things they think would be helpful in preparation for the hackathon

==== Remote participation ====
    * While in person participation in preferred, we understand that not everyone can travel. If you want to participate in a project remotely, please contact the champion(s) for that project to determine how best to coordinate.
    * Jabber Room: hackathon95@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.