This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
100hackathon [2017/11/10 09:38] cabo Add WISHI |
100hackathon [2017/12/01 18:41] eckelcu_cisco.com |
||
---|---|---|---|
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. | ||
---- | ---- | ||
Line 43: | Line 45: | ||
* Code can be accessed from [[https://github.com/ietf-hackathon|IETF Hackathon Github]] or from links provided within project descriptions below. | * 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> | * Request to be added to IETF Github organization by sending your Github ID to Charles Eckel <eckelcu@cisco.com> | ||
- | * Photos | + | * [[https://isoc.box.com/v/IETF100-Hackathon-Photos|Photos]] |
+ | * Provide photo credit as © Stonehouse Photographic / Internet Society | ||
+ | * Contact Greg Wood <wood@isoc.org> if you want to use any of these photos for things not related to the IETF | ||
* Take and post your own on Twitter with hash tags #IETFHackathon #IETF100 | * Take and post your own on Twitter with hash tags #IETFHackathon #IETF100 | ||
- | |||
---- | ---- | ||
==== Participant Preparation and Prerequisites ==== | ==== Participant Preparation and Prerequisites ==== | ||
Line 121: | Line 124: | ||
**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 152: | Line 155: | ||
* 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 172: | Line 193: | ||
* 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 297: | Line 318: | ||
* remote participation: https://jitsi.tools.ietf.org/t2trg-wishi | * 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 :-). | * 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. |