This is an old revision of the document!
==== 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:** [[https://www.ietf.org/registration/ietf97/hackathonregistration.py|Hackathon Registration]] **View the list of Hackathon Attendees:** [[https://www.ietf.org/registration/ietf97/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, 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 ==== * Prep Call, Wednesday, November 9, 2016, 8:00am PST (UTC-8:00) * Play recording (xx min x sec), Recording password: xxxxxx - COMING SOON * Presentations can be accessed from [[https://datatracker.ietf.org/meeting/97/session/hackathon/|IETF Hackathon Materials]] * Send presentations you want uploaded to Charles Eckel <eckelcu@cisco.com> * Code can be accessed from [[https://github.com/ietf-hackathon|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@cisco.com> ---- ==== Technologies Included in Hackathon (more can be added) ==== **DDoS Open Threat Signaling (DOTS)** * Champion(s) * Tirumaleswar Reddy <tireddy@cisco.com> * Project(s) * Working Group is [[https://datatracker.ietf.org/wg/dots/charter/|chartered]] to propose a standard method of coordinating defensive measures among willing peers to mitigate attacks quickly and efficiently * DOTS client uses DOTS signal to inform the DOTS server that it is under attack and requests the DOTS server to take precautionary measures to mitigate the attack * DOTS server enables mitigation on behalf of the DOTS client by communicating the DOTS client's request to the DDOS mitigator and relaying any mitigator feedback to the requesting DOTS client * Implement a POC for DOTS signal and data channel (it’s using CoAP) * Working Group Drafts: * [[https://tools.ietf.org/html/draft-ietf-dots-architecture-00]] * [[https://tools.ietf.org/html/draft-ietf-dots-requirements-02]] * [[https://tools.ietf.org/html/draft-reddy-dots-data-channel-00]] * [[https://tools.ietf.org/html/draft-reddy-dots-signal-channel-00]] ** DNS/DPRIVE/DNSSEC/DANE ** * Champion(s) * Sara Dickinson <sara@sinodun.com> * Allison Mankin <allison.mankin@gmail.com> * Benno Overeinder <benno@nlnetlabs.nl> * Melinda Shore <melinda.shore@nomountain.net> * Willem Toorop <willem@nlnetlabs.nl> * Others welcome * Projects * DNS Session signaling (draft-ietf-dnsop-session-signal) * Asyncio support in getdns Python binding * Adding out-of-order processing to Unbound TCP * DBUS API and nss-resolv support for Stubby [[https://getdnsapi.net/presentations/stubby-nanog68.pdf]] * TLS chain extension (draft-ietf-tls-dnssec-chain-extension-01) * IPv6-only prefix discovery for DNS64 (RFC 7050) * Others welcome **Interface to the Routing System(I2RS)** * Champion(s) * Susan Hares <shares@ndzh.com> * Project(s) * tbd **TLS 1.3** * Champions * EKR <ekr@rtfm.com> * 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 **YANG/NETCONF/RESTCONF** * Champion(s) * YANG: Benoit Claise (bclaise) <bclaise@cisco.com> * Project(s) * Benoit Claise: improve YANG model monitoring tools at [[http://www.claise.be/]] (yuma compiler, bugs fix) * Joe Clarke, Carl Moberg (remotely), Benoit Claise: YANG catalog (yangcatalog.org) * Hariharan Ananthakrishnan * Vladimir Vassilev: ietf-alarms.yang draft implementation for yuma123 * 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). **PCE** * Champion(s) * Satish K <satish.karunanithi@gmail.com> * Dhruv Dhody <dhruv.ietf@gmail.com> * Project(s) * Support for LSP Scheduling * TEAS - [[https://tools.ietf.org/html/draft-zhuang-teas-scheduled-resources-03]] * PCE - [[https://tools.ietf.org/html/draft-zhuang-pce-stateful-pce-lsp-scheduling-03]] **ACTN** * Champion(s) * Dhruv Dhody <dhruv.ietf@gmail.com> * Haomian Zheng <zhenghaoman@huawei.com> * 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** * Champion(s) * Benjamin Hesmans <benjamin.hesmans@uclouvain.be> * Project(s) * Allow TCP-based application to intelligently use Multipath TCP based on the enhanced socket API * Multipath TCP on Linux - [[https://www.multipath-tcp.org]] * Socket API draft - [[https://tools.ietf.org/html/draft-hesmans-mptcp-socket-00]] * Socket API paper - [[https://irtf.org/anrw/2016/anrw16-final16.pdf]] * List here the application, client or server that you would like to tune for MPTCP * TBD **COSE/JOSE** * Champion(s) * Jim Schaad <ietf@augustcellars.com> * Matt Miller <mamille2@cisco.com> * Project(s) * Building test cases * Open source library development * Documents under development * OSCOAP - [[https://datatracker.ietf.org/doc/draft-seitz-ace-oscoap-profile/]] * EDHOC - [[https://datatracker.ietf.org/doc/draft-selander-ace-cose-ecdhe/]] * PASSportT - [[https://datatracker.ietf.org/doc/draft-ietf-stir-passport/]] * CBOR Web Token - [[https://datatracker.ietf.org/doc/draft-ietf-ace-cbor-web-token/]] **SFC** * Champion(s) * Vu Anh Vu <vuva@dcn.ssu.ac.kr> * Project(s) * Hierarchical SFC with flow-stateful classifier using ODL - [[https://datatracker.ietf.org/doc/draft-ietf-sfc-hierarchical/]] * Controlling SF access to NSH using ODL - [[https://datatracker.ietf.org/doc/draft-vu-sfc-sf-access-control/]] * Support scheduling of SFC with calendaring using ONOS - (1) Supoort Time range (2) Support repeat option within time range - Swarup Nayak <swarup.nayak1@huawei.com> **SFC Service Function** * Champion(s) * David Dolson <ddolson@sandvine.com>, Kyle Larose <klarose@sandvine.com> * 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). * We've started here: https://github.com/dcdolson/nsh-sf-devkit * Skills that we would appreciate: * C/C++ * DPDK * VPP (FD.io) * Ubuntu * Doxygen * Make **Capturing and analyzing network data features** * Champion(s) * David McGrew <mcgrew@cisco.com> * Project(s) * Using and extending the Joy package [[https://github.com/davidmcgrew/joy]] * Adding SSH awareness to enable passive security audit **Interface to Network Security Functions (I2NSF) Framework** * Champion(s) * Jaehoon Paul Jeong <pauljeong@skku.edu> * Jinyong Tim Kim <timkim@skku.edu> * Jung-Soo Park <pjs@etri.re.kr> * Tae-Jin Ahn <taejin.ahn@kt.com> * Project(s) * I2NSF Framework for provisioning Network Security Functions (NSFs) * Firewall in I2NSF Framework using Software-Defined Networking (SDN) * Deep Packet Inspection (DPI) for VoIP-VoLTE Security Service in I2NSF Framework * Working Group Drafts * https://tools.ietf.org/html/draft-ietf-i2nsf-framework-04 * https://tools.ietf.org/html/draft-hares-i2nsf-capability-data-model-00 * https://tools.ietf.org/html/draft-kim-i2nsf-nsf-facing-interface-data-model-00 * https://tools.ietf.org/html/draft-jeong-i2nsf-sdn-security-services-05 * https://tools.ietf.org/html/draft-kim-i2nsf-security-management-architecture-03 * https://tools.ietf.org/html/draft-kim-i2nsf-consumer-facing-interface-dm-00 * https://tools.ietf.org/html/draft-hyun-i2nsf-nsf-triggered-steering-00 * https://tools.ietf.org/html/draft-hyun-i2nsf-registration-interface-im-00 * https://tools.ietf.org/html/draft-ahn-i2nsf-communications-security-use-case-01 **Vector Packet Processor (VPP)** * Champion(s) * Pierre Pfister <ppfister@darou.fr> * Project(s) * Have some fun using Open Source FD.io's Vector Packet Processor (VPP) [[https://fd.io/]] * Breaking the internet with a high-perf stateless-TCP file server. * Add gRPC + protobuf for VPP. 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** * 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. * A basic tutorial is provided in this post: https://mailarchive.ietf.org/arch/msg/92hackathon/lM8Ag_is4a00PsudnzaqdV1vhoE * 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.
