User Tools

Site Tools


100hackathon

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
100hackathon [2017/11/01 03:52]
kaname
100hackathon [2017/11/14 05:43] (current)
eckelcu_cisco.com [Agenda]
Line 5: Line 5:
 **When:** Saturday November 11, 2017 and Sunday November 12, 2017\\ **When:** Saturday November 11, 2017 and Sunday November 12, 2017\\
 **Where:** [[https://​datatracker.ietf.org/​meeting/​100/​floor-plan?​room=moor-morrison|Moor/​Morrison]] \\ **Where:** [[https://​datatracker.ietf.org/​meeting/​100/​floor-plan?​room=moor-morrison|Moor/​Morrison]] \\
-**Signup ​for the Hackathon here:** [[https://​www.ietf.org/​registration/​ietf100/​hackathonregistration.py|Hackathon Registration]]\\ +**Sign up for the Hackathon here:** [[https://​www.ietf.org/​registration/​ietf100/​hackathonregistration.py|Hackathon Registration]]\\ 
-**View the list of registered Hackathon attendees:​** [[https://​www.ietf.org/​registration/​ietf100/​hackathonattendance.py?​sortkey=3&​login=%0A|Attendees]]+**View the list of registered Hackathon attendees:​** [[https://​www.ietf.org/​registration/​ietf100/​hackathonattendance.py?​sortkey=3&​login=%0A|Attendees]]\\ 
 +**Sign up to demo your work on Wednesday, November 15, 2017:** [[100hackathon-demos|Hackathon Demos at IETF 100]] 
  
 Keep up to date by subscribing to [[https://​www.ietf.org/​mailman/​listinfo/​hackathon|https://​www.ietf.org/​mailman/​listinfo/​hackathon]]\\ Keep up to date by subscribing to [[https://​www.ietf.org/​mailman/​listinfo/​hackathon|https://​www.ietf.org/​mailman/​listinfo/​hackathon]]\\
Line 32: Line 34:
     ​     ​
 For your planning purposes, be aware that we will also have: For your planning purposes, be aware that we will also have:
-     * Code Lounge: Space reserved in the IETF Lounge throughout the week of IETF, November 13-17, for groups to gather and collaborate on running code. [[https://​www.ietf.org/​registration/​MeetingWiki/​wiki/​doku.php?​id=100codelounge | Schedule ]] time for your team.   +     * Code Lounge: Space reserved in the IETF Lounge throughout the week of IETF, November 13-17, for groups to gather and collaborate on running code. [[https://​www.ietf.org/​registration/​MeetingWiki/​wiki/​doku.php?​id=100codelounge | Schedule ]] time for your team. 
 +     * Project Demos: [[https://​www.ietf.org/​registration/​MeetingWiki/​wiki/​doku.php?​id=100hackathon-demos|Sign up]] to demo your Hackathon work in the Fairmont Ballroom Foyer on Wednesday. ​
 ---- ----
  
 ==== Meeting Materials ==== ==== Meeting Materials ====
  
-     * IETF Hackathon Prep Call - [[https://www.ietf.org/mail-archive/web/​hackathon/​current/​msg00405.html|scheduled]] for Wednesday, November 19:00am Pacific US +     * IETF Hackathon Prep Call - [[https://cisco.webex.com/ciscosales/lsr.php?​RCID=03eb136a10864f1795a2839b82147c50|Play recording (42 min 2 sec)]], password4gXDgzJB
      * Presentations can be uploaded and accessed from [[https://​datatracker.ietf.org/​group/​hackathon/​meetings/​]]      * Presentations can be uploaded and accessed from [[https://​datatracker.ietf.org/​group/​hackathon/​meetings/​]]
        * Send presentations you want uploaded to Charles Eckel <​eckelcu@cisco.com>​        * Send presentations you want uploaded to Charles Eckel <​eckelcu@cisco.com>​
Line 62: Line 64:
        * If you have additional requirements,​ email Charles Eckel <​eckelcu@cisco.com>​        * If you have additional requirements,​ email Charles Eckel <​eckelcu@cisco.com>​
      * Code Lab      * Code Lab
-       * Thanks to Comcast and Arris, we will have a rack of equipment that includes a CTMS, cable models, and VMs on demand. If you have questions or what access to generic VMs, a CTMS, a home network environment,​ etc., email Charles Eckel <​eckelcu@cisco.com>​ and Chris Tuska <​Chris.Tuska@arris.com>​+       * Thanks to Comcast and Arris, we will have a rack of equipment that includes a CMTS, cable modems, and VMs on demand. If you have questions or want access to generic VMs, a CMTS, a home network environment,​ etc., email Charles Eckel <​eckelcu@cisco.com>​ and Chris Tuska <​Chris.Tuska@arris.com>​
      * Sharing Code      * Sharing Code
        * 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. ​
Line 100: Line 102:
 **IPv4-IPv6 Transition Technology Interop** **IPv4-IPv6 Transition Technology Interop**
      * Champion(s)      * Champion(s)
-       * Lee Howard+       * Lee Howard, Ole Trøan
      * Mailing list: http://​lists.retevia.net/​listinfo.cgi/​v6-interop-retevia.net ​      * Mailing list: http://​lists.retevia.net/​listinfo.cgi/​v6-interop-retevia.net ​
      * Project(s)      * Project(s)
Line 121: Line 123:
 **DNS** **DNS**
      * Champion(s)      * Champion(s)
-       ​* ​tbd+       ​* ​Benno Overeinder
      * Project(s)      * Project(s)
        * Implementation of the "​opportunistic send of A record when queried for AAAA (and vice-versa) idea? (No draft, I think, only floating ideas.) We would need at least one auth. server to send these opportunistic answers and one recursive to cache them. Test that nothing breaks. (Contact Stéphane Bortzmeyer) ​        * Implementation of the "​opportunistic send of A record when queried for AAAA (and vice-versa) idea? (No draft, I think, only floating ideas.) We would need at least one auth. server to send these opportunistic answers and one recursive to cache them. Test that nothing breaks. (Contact Stéphane Bortzmeyer) ​
        * Implementation of DNS-wire-format over HTTPS (DOH WG). There are implementations of DNS-JSON over HTTPS but not wire-format. (Contact Stéphane Bortzmeyer) ​        * Implementation of DNS-wire-format over HTTPS (DOH WG). There are implementations of DNS-JSON over HTTPS but not wire-format. (Contact Stéphane Bortzmeyer) ​
        * Tests of multiple questions in the Question Section (no draft, just to compare with the other "​multiple answers"​ drafts). (Contact Stéphane Bortzmeyer) ​        * Tests of multiple questions in the Question Section (no draft, just to compare with the other "​multiple answers"​ drafts). (Contact Stéphane Bortzmeyer) ​
-       ​* ​tbd+       ​* ​DANE authentication of DNS-over-TLS upstreams (draft-ietf-dprive-dtls-and-tls-profiles)
  
 **DNSSD (DNS-Based Service Discovery)** **DNSSD (DNS-Based Service Discovery)**
Line 142: Line 144:
          * [[https://​www.ietf.org/​mailman/​listinfo/​dnssd ​                | DNSSD Working Group]]          * [[https://​www.ietf.org/​mailman/​listinfo/​dnssd ​                | DNSSD Working Group]]
        * An overview of these protocols can be found in the [[https://​tools.ietf.org/​html/​draft-cheshire-dnssd-roadmap | Service Discovery Road Map]]        * An overview of these protocols can be found in the [[https://​tools.ietf.org/​html/​draft-cheshire-dnssd-roadmap | Service Discovery Road Map]]
 +     * Note from Stuart: I will be arriving in Singapore at 06:50 Saturday morning, and then coming directly to the Hackathon. I hope to be at the Hackathon by 09:00 or soon after, but that will depend on whether the flight (UA37) arrives on time, time for customs, immigration,​ and travel time.
  
 **TLS** **TLS**
Line 151: Line 154:
        * Implementation and interoperability testing of adopted drafts        * Implementation and interoperability testing of adopted drafts
        * [[https://​trac.ietf.org/​trac/​tls/​wiki/​WikiStart | TLS/DTLS 1.3 Implementations]]        * [[https://​trac.ietf.org/​trac/​tls/​wiki/​WikiStart | TLS/DTLS 1.3 Implementations]]
 +
 +** NETVC **
 +     * Champion(s)
 +       * Timothy B. Terriberry <​tterribe@xiph.org>​
 +     * Project(s)
 +       * AV1 
 +         * Git repository: https://​aomedia.googlesource.com/​aom
 +         * Bug tracker: https://​bugs.chromium.org/​p/​aomedia/​issues/​list
 +         * Gerrit: https://​aomedia-review.googlesource.com/​
 +         * Contributor'​s Guide: http://​aomedia.org/​contributor-guide/​
 +       * Daala: https://​git.xiph.org/?​p=daala.git
 +       * Thor: https://​github.com/​cisco/​thor
 +       * Are We Compressed Yet: https://​github.com/​tdaede/​awcy
 +       * rd_tool (AWCY backend): https://​github.com/​tdaede/​rd_tool
 +     * Resources:
 +       * Are We Compressed Yet: https://​arewecompressedyet.com/​
 +       * Video test sets: https://​media.xiph.org/​video/​derf
 +
  
 ** SACM ** ** SACM **
Line 171: Line 192:
      * Project(s)      * Project(s)
        * yangcatalog.org:​ Joe Clarke, Benoit Claise        * yangcatalog.org:​ Joe Clarke, Benoit Claise
-       * yuma123 (API, netconfd, yangcli) : Vladimir Vassilev+       * yuma123 (API, netconfd, yangcli) : Vladimir Vassilev ​[[http://​www.yuma123.org/​wiki/​index.php/​IETF_100_Hackathon|report]]
        * yangvalidator.com:​ Mahesh Jethanandani        * yangvalidator.com:​ Mahesh Jethanandani
          * Add support for yandump-pro.          * Add support for yandump-pro.
Line 270: Line 291:
          * nttdots: https://​github.com/​nttdots/​go-dots          * nttdots: https://​github.com/​nttdots/​go-dots
          * internal implementation by Jon Shallow          * internal implementation by Jon Shallow
 +
 +**ECN / AQM Testing & Interop**
 +     * Champion(s)
 +       * Igor Lubashev, Kyle Rose, Aaron Falk
 +     * Project(s)
 +       * Performance comparison w/ & w/o ECN/AQM of video from Akamai origin through home router
 +
 +**IOAM**
 +     * Champion(s)
 +       * Mickey Spiegel, Shwetha Bhandari
 +     * Project(s)
 +       * Initial implementation of In-situ OAM (IOAM) in software (VPP) and hardware ​
 +       * Specifications:​
 +         * [[https://​tools.ietf.org/​html/​draft-ietf-ippm-ioam-data]]
 +         * [[https://​tools.ietf.org/​html/​draft-brockners-ioam-vxlan-gpe]]
 +         * [[https://​tools.ietf.org/​html/​draft-brockners-inband-oam-transport]]
 +
 +
 +**WISHI**
 +     * Champion(s)
 +       * Ari Keränen, Carsten Bormann
 +     * Project(s)
 +       * [[http://​wishi.space]] ​
 +       * For WISHI (Work on IoT Semantic/​Hypermedia Interoperability,​),​ we meet in person at IETF100 at the Hackathon. ​ The objective is to make use of the various interfaces of implementations we have for capturing and retrieving semantic information,​ such as oneIOTA, iot.schema.org,​ or the IPSO objects/​LWM2M repository. ​ We want to make sure that we all have some working knowledge about important systems that are out there for this purpose, and possibly write some code to try out the programmatic interfaces. ​ It would be nice if the protagonists of the various systems could be present in person and, for extra bonus, a short introduction how and why (when) one should use that system. ​ If we can capture learnings from this Hackathon in the WISHI wiki, that would also be a useful outcome.
 +       * remote participation:​ https://​jitsi.tools.ietf.org/​t2trg-wishi
 +       * Singapore is UTC+8, so this will be 0400Z..0600Z. ​ Sorry about the time, and to add insult to injury, no lunch for remotes (but you can watch us eat :-).
 +
 +
 +**CoAP-over-TCP**
 +     * Champion(s)
 +       * Carsten Bormann, Hannes Tschofenig
 +     * Project(s)
 +       * We want to do some interoperability testing of the fresh implementations based on draft-ietf-core-tcp-tls-10. ​ libcoap might serve as a reference implementation. ​ Some hacking on the implementations expected...
 +       * remote participation:​ https://​jitsi.tools.ietf.org/​coap-tcp
 +
  
  
 ---- ----
 +Testing the file uploaded feature. File {{:​test.pptx|here}}. ​
  
 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. 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.
Line 285: Line 342:
  
 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**//​. 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**//​.
- 
100hackathon.1509508360.txt.gz · Last modified: 2017/11/01 03:52 by kaname