User Tools

Site Tools


95hackathon

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
95hackathon [2016/03/24 16:28]
danyork Added my name (Dan York) to DNS champions
95hackathon [2016/07/04 12:24] (current)
sara
Line 37: Line 37:
         15:30: Awards presented, prizes given         15:30: Awards presented, prizes given
         16:00: Hackathon ends         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) ==== ==== Technologies Included in Hackathon (more can be added) ====
  
 **DNS/​DNSSEC/​DANE/​DNS-over-(D)TLS** **DNS/​DNSSEC/​DANE/​DNS-over-(D)TLS**
-     ​* ​Champion(s)+     ​* ​Champions/​Hackers
        * Coordinator:​ Allison Mankin <​allison.mankin@gmail.com> ​        * Coordinator:​ Allison Mankin <​allison.mankin@gmail.com> ​
-       * Benno Overeinder ​ +       * Benno OvereinderWillem Toorop, Ralph Dolman 
-       ​* ​Willem Toorop +       * Sara Dickinson, John Dickinson 
-       * Sara Dickinson +       ​* ​Shane Kerr 
-       ​* ​John Dickinson +       * Shumon Huque 
-       * Linus Nordberg+       * Dave Lawrence 
 +       * Daniel Kahn Gillmor 
 +       * Linus Nordberg ​(remote) 
 +       * Melinda Shore (remote) 
 +       * Gowri Visweswaran (remote)
        * Jan Včelák        * Jan Včelák
-       * Evan Hunt+       * Evan Hunt (plus others on BIND team, reporting separately)
        * Dan York        * Dan York
-       ​* ​Others ​welcome, remote participants welcome+       ​* ​All welcome, remote participants welcome
      * Project(s)      * Project(s)
        * Library-independent interfacing with TLS        * Library-independent interfacing with TLS
Line 61: Line 72:
        * getdns version for Raspbian ​        * getdns version for Raspbian ​
        * automated DNSSEC key maintenance/​rollover scheduling tool for BIND        * 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         * And more 
  
-**ICE**+**Network Based Metrics Analytics**
      * Champion(s)      * Champion(s)
-       * Pål-Erik Martinsen +       * Pål-Erik Martinsen (palerikm@gmail.com)
-       *  +
-     * Project(s) +
-       * Metrics and analytics+
  
- 
-**Network Based Metrics Analytics** 
-     * Champion(s) 
-       * Pål-Erik Martinsen 
-       ​* ​ 
      * Project(s)      * Project(s)
-       ​* ​Setting up end testing if apache spark is suitable for analysing metrics from the network +       ​* ​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** **NETCONF/​YANG,​ I2RS, OpenDaylight**
      * Champion(s)      * Champion(s)
 +       * YANG: Benoit Claise ​
        * Susan Hares <​shares@ndzh.com>​        * Susan Hares <​shares@ndzh.com>​
-       ​* ​+       ​* ​Kent Watsen
      * Project(s)      * 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]]) ​        * 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** **NETVC**
      * Champion(s)      * Champion(s)
-       ​* ​TBD +       ​* ​Tim Terriberry 
-       ​* ​+       ​* ​Thomas Daede <​tdaede@mozilla.com>​
      * Project(s)      * Project(s)
-       ​* ​TBD +       ​* ​Updates to the "Are We Compressed Yet" tools
-       ​* ​+
  
 **IBNEMO(Intent Based Network Modeling)** **IBNEMO(Intent Based Network Modeling)**
Line 119: Line 134:
  
 **Homenet** **Homenet**
-     ​* ​Champion(s+     ​* ​Teaming with VPP on source address dependent routing ​(SADR
-       * TBD +     ​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
-     ​* ​Project(s) +
-       * TBD+
  
 **RIOT (OS for internet of things)** **RIOT (OS for internet of things)**
Line 136: Line 149:
        * Ole Trøan        * Ole Trøan
      * Project(s)      * Project(s)
-       * Source Address Dependent Routing+       * 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** **TLS 1.3**
Line 170: Line 184:
      * Anything else that is required will be provided, such as VMs you can install on our laptop or access from your laptop      * 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        * 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 may available to others as download times can be painful+       * 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      * 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      * 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. ​      * 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        * 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        * 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      * 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 ==== ==== 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. 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.
95hackathon.1458836913.txt.gz · Last modified: 2016/03/24 16:28 by danyork