IETF Meeting Wiki

User Tools

Site Tools

Trace: • 100hackathon
100hackathon

Table of Contents

IETF 100 Hackathon

The IETF 100 Hackathon is now over (see summary). Thanks to all who had a hand in its success.

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 11, 2017 and Sunday November 12, 2017
Where: Moor/Morrison
Sign up for the Hackathon here: Hackathon Registration
View the list of registered Hackathon attendees: Attendees
Sign up to demo your work on Wednesday, November 15, 2017: Hackathon Demos at IETF 100

Keep up to date by subscribing to https://www.ietf.org/mailman/listinfo/hackathon
The Hackathon is free to attend.

Agenda

  Saturday, November 11
      08:00: Room open for setup of posters at tables by projects champions    
      09:00: Room open for all - Pastries and coffee provided
      09:30: Hackathon kickoff 
      09:45: Form Teams
      12:30: Lunch provided
      15:30: Afternoon break - Snacks provided
      19:00: Dinner provided
      22:00: Room closes and is locked
  Sunday, November 12
      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
      17:00: Tear down complete

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. Schedule time for your team.
  • Project Demos: Sign up to demo your Hackathon work in the Fairmont Ballroom Foyer on Wednesday.

—-

Meeting Materials

—-

Participant Preparation and Prerequisites

  • Champions will have posters describing their project(s) and be available to answer questions at the start and throughout the hackathon
    • Familiarity with technology area(s) in which you plan to participate will certainly help
  • Development Environment
    • Bring a laptop on which you are comfortable developing software
    • Some projects may require installing additional software or make use of VMs
    • 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
  • Network
    • Wireless access to the IETF network will be provided, and from there to the outside world
    • Wired access to the IETF network is available by request only
    • If you have additional requirements, email Charles Eckel eckelcu@cisco.com
  • Code Lab
    • 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
    • Git/GitHub is commonly used for open source projects. Familiarizing yourself with it is recommended.
    • An online tutorial is available here: Git Tutorial
  • Training Materials

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
  • Meetecho: Active and recorded Saturday from 09.30-10.00 and Sunday from 14.00-16.00

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.

Technologies Included in Hackathon (more can be added)

Data Leak Prevention (DLP)

  • Champion(s)
    • Reinaldo Penno
  • Project(s)
    • Equifax, Home Depot, Target, HBO (Game of Thrones), do any of these security breaches scare you?
    • Do you want to participate on a open source project that sets well known standards on data protection?
    • We have open sourced an alpha DLP project that lays the foundation for such work.
    • We will be discussing next steps on IETF-100
    • https://github.com/magengit
    • There is a Hello World application at https://github.com/magengit/magen-hwa

IPv4-IPv6 Transition Technology Interop

  • Champion(s)
    • Lee Howard, Ole Trøan
  • Mailing list: http://lists.retevia.net/listinfo.cgi/v6-interop-retevia.net
  • Project(s)
    • Develop test plan/matrix. Based on tickets https://tickets.meeting.ietf.org/wiki/nat64 and discussion, include at least Palo Alto VPN, OpenVPN, Outlook for Mac, Jabber (Google), voice calls, Spotify.
    • Develop public site to record findings (available over IPv6-only, of course)
    • Test applications on ietf-NAT64
    • Configure 464xlat network(s). May include CPE-based CLAT, and/or device-based CLAT.
    • Configure DS-Lite network(s). May include multiple vendors' implementations.
    • Configure MAP-T network(s). May include multiple vendors' implementations.
    • Configure MAP-E network(s). May include multiple vendors' implementations.

JMAP Interop

  • Champion(s)
    • Bron Gondwana
  • Project(s)
    • JMAP Proxy server
    • Test client libraries
    • Test server implementations

DNS

  • Champion(s)
    • Benno Overeinder
  • 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 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)
    • DANE authentication of DNS-over-TLS upstreams (draft-ietf-dprive-dtls-and-tls-profiles)

DNSSD (DNS-Based Service Discovery)

TLS

  • Champion(s)
    • Nick Sullivan
  • Project(s)
    • TLS 1.3 draft 21 testing and interop
    • Implementation in applications (wget)
    • Implementation and interoperability testing of adopted drafts
    • TLS/DTLS 1.3 Implementations

NETVC

SACM

YANG/NETCONF/RESTCONF

  • Champion(s)
    • Benoit Claise
  • Project(s)
    • yangcatalog.org: Joe Clarke, Benoit Claise
    • yuma123 (API, netconfd, yangcli) : Vladimir Vassilev report
    • yangvalidator.com: Mahesh Jethanandani
      • Add support for yandump-pro.
      • Add support for multiple files to be uploaded as part of the first option
      • Add support for validation using a draft id. Currently returns 403.

QUIC

  • Champion(s)
    • Lars Eggert
  • Project(s)
    • Interop around the -07 drafts. See the QUIC WG wiki for details on what will be tested.

Captive Portals

  • Champion(s)
    • Martin Thomson
  • Project(s)
    • API
    • MAC address propagation
    • HTTPS

Interface to Network Security Functions (I2NSF) Framework

Public Interest & HTTP Status Code 451

Generating Certificate Requests for Short-Term, Automatically-Renewed (STAR) Certificates

IPv6 compression+fragmentation prototype implementation for LoRaWAN

  • Champion(s)
    • Laurent Toutain (firstname.lastname at imt-atlantique dot fr)
    • Dominique Barthel (firstname.lastname at orange dot com)
  • Project(s)
    • IPv6 compression for LPWAN technologies is being defined at the LPWAN WG. We recently added fragmentation. See https://tools.ietf.org/html/draft-ietf-lpwan-ipv6-static-context-hc-07.
    • At this hackathon, we'll work on a prototype implementation of the fragmentation, on both the End-Device and the Network server sides.
    • We'll test it on a live LoRaWAN network.
    • A radio gateway will be provided. A few Pycom boards (https://pycom.io/product/lopy/) will be available as development platforms for the end-device.

DOTS Interop

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

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

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.

100hackathon.txt · Last modified: 2017/12/11 23:34 by eckelcu_cisco.com

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki