wiki:103hackathon


IETF 103 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 and Sunday, November 3 and 4, 2018
Where: Mariott Marquis Queen's Park, Room: Sala Thai
Sign up for the Hackathon here: REGISTER!
View the list of registered Hackathon attendees: Attendees

Keep up to date by subscribing to https://www.ietf.org/mailman/listinfo/hackathon

The Hackathon is free to attend and is open to everyone. It is a collaborative event, not a competition. Any competition is friendly and in the spirit of advancing the pace and relevance of new and evolving internet standards.


Agenda

Hackathon

  • Saturday, November 3
    • 08:30: Room open for setup by project champions
    • 09:00: Room open for all - Pastries and coffee provided
    • 09:30: Hackathon kickoff - Join via Meetecho
    • 09:45: Form Teams
    • 12:30: Lunch provided
    • 15:30: Afternoon break - Snacks provided
    • 19:00: Dinner provided
    • 22:00: Room closes
  • Sunday, November 4
    • 08:30: Room opens - Pastries and coffee provided
    • 12:30: Lunch provided
    • 13:30: Hacking stops, prepare brief presentation of project
    • 14:00: Project presentations to other participants Join via Meetecho
    • 15:45: Closing remarks and opportunities for next time
    • 16:00: Hackathon ends
    • 17:00: Tear down complete

DOODLE FOR VOTING: https://doodle.com/poll/d8inriipidvbxfc6

Related activities before and after the Hackathon weekend

  • Code Lounge
    • Space for groups to gather and collaborate on running code
    • Monday - Friday, November 5-9 in Sala Thai
    • View the schedule or reserve space for your team/project
  • Hackdemo Happy Hour
    • Share your hackathon project with IETF community
    • Monday, November 5, 18:30 - 20:00 in Room: Sala Thai
    • View the schedule or reserve space for your team/project
      • Reservations for space must be made by 12:00, Monday, November 5

Meeting Materials


Participant Preparation and Prerequisites

  • Choosing a Project
    • Champions will have table signs on the center of their table identifying their project and be available to answer questions at the start and throughout the hackathon
    • Optionally, champions may create and display posters on flip charts with additional information on their project
    • Details on each project and links to additional information for each project are in this wiki in the "Projects Included in Hackathon" section
    • Familiarity with technology area(s) in which you plan to participate will certainly help
    • It is perfectly fine, even encouraged, to work on multiple projects
  • 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, Vagrant, 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 by some 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
  • 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
    • IETF Hackathon GitHub Org
      • If you would like to have your project/code hosted here, send your GitHub ID and the name of your project via email to Charles Eckel: eckelcu@ cisco.com
  • Training Materials
  • Champions for each technology are encouraged to share any other things they think would be helpful in preparation for the hackathon
  • Project Presentations
    • All teams have the opportunity to present what they did on Sunday afternoon at the end of the hackathon
      • https://github.com/IETF-Hackathon/ietf103-project-presentations is for IETF hackathon participants to upload their hackathon project presentations
      • You must be a member of the IETF-Hackathon GitHub org to upload a new presentation or update/replace an existing presentation
      • To be added as a member, email Charles Eckel: eckelcu@ cisco.com your GitHub ID at your earliest convenience
      • DO NOT WAIT until just before hackathon project presentations start or your request may be lost in the chaos

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) of the project to determine how best to coordinate.
  • Jabber room: xmpp:hackathon@jabber.ietf.org
  • Meetecho: http://ietf103.conf.meetecho.com/

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.


Projects Included in Hackathon (add your project using the template provided below)

QUIC

  • Champion(s)
    • Lars Eggert
  • Project(s)
    • interop around latest drafts

RIFT Flooding

  • Champions
    • Tony Przygienda <prz at juniper.net>
  • Project(s)
    • RIFT is a STD track WG working on a modern IP fabric/DC routing protocol
    • Implement basic TIDE/TIRE exchange, try to get a North Node TIE flooded
  • Preconditions:

DNS

  • Champion(s)
    • Petr Špaček <petr.spacek at nic.cz>
  • Project(s) (tentatively)
    • DNS configuration using YANG+RESTCONF

DNS Service Discovery Extensions

JMAP

  • Champion(s)
    • Neil Jenkins <neilj at fastmailteam.com>
  • Project(s)
    • Interop testing with implementations of last-call draft. Will have a client/server to test other clients/servers with.
    • Implementation experience for last-call feedback.

DTN

LPWAN CoAP/UDP/IPv6 SCHC compression and fragmentation

  • Champion(s)
    • Laurent Toutain (IMT-Atlantique) laurent dot toutain at imt dash atlantique dot fr
    • Cedric Adjih (INRIA) cedric dot adjih at inria dot fr
    • Dominique Barthel (Orange Labs) dominique dot barthel at orange dot com
  • Project(s)

Public interest technology

TCP Authentication Option (TCP-AO)

  • Champion(s)
    • Brian Weis (bew at cisco dot com)
  • Project(s)

TLS 1.3

  • Champion(s)
    • Loganaden Velvindron (logan at cyberstorm.mu) - remote
    • Codarren Velvindron (codarren at cyberstorm.mu) - remote
    • Muzaffar Auhammud (muzaffar at cyberstorm.mu) - remote
  • Project(s)
    • TLS 1.3 Integration & Interop.

SSH

EST-COAPS (ACE WG) + ANIMA BRSKI

  • Champion(s)
    • Michael Richardson (mcr at sandelman.ca)
    • Peter van der Stok (consultancy at vanderstok.org)

http 451

  • Champion(s)
    • Veegish Ramdani (veegish at cyberstorm.mu) - remote
    • Kifah Meeran (kifah at cyberstorm.mu) - remote
  • Project(s)
    • HTTP 451 module in Drupal.

Sliding Window FEC codec

WISHI (Work on IoT Semantic / Hypermedia Interoperability)

Interface to Network Security Functions (I2NSF) Framework

Multicast Ingest Platform

  • Champion(s)
    • Jake Holland <jholland at akamai.com>
    • Kyle Rose <krose at akamai.com>
  • Project(s)
    • We'll build a FRRouting-based image which launches a stub AMBI receiver and an AMT gateway, with sender info discovered via DNS in response to propagated PIM joins (and shuts them down in response to prunes). The ultimate goal is a deployable platform that can ingest authenticated multicast traffic from a remote AMT relay with AMBI support, with no config or peering required in the remote network to support a new receiving network.
    • draft-jholland-mboned-ambi
    • draft-nortz-optimal-amt-relay-discovery

Trusted Execution Environment Provisioning

  • Champion(s)
    • Dave Thaler <dthaler at microsoft.com>
  • Project(s)
    • Work on OTrP implementation(s) based on latest spec

DOTS Interop

  • Champion(s)
    • Kaname Nishizuka
    • Jon Shallow
    • Liang 'Frank' Xia
  • Project(s)

YANG/NETCONF/RESTCONF

Measurement Tools that follow/lead Standards

  • Champion(s)
    • Al Morton
    • Thomas Fossati
  • Possible Project(s)
    • Route Metrics (IPPM)
    • Spin Bit (QUIC)
    • Dataplane Benchmarking (BMWG)
    • IP Capacity Measurement (IPPM)
    • Measuring the impact of a loss-latency trade-off signal (similar to the one described in draft-you-tsvwg-latency-loss-tradeoff) on traffic crossing the mobile network

Limited Usage of Remote Keys (LURK)

SRv6 (Segment Routing IPv6) to user-plane of mobile networks (N3 and N9 interfaces)

In-Situ OAM

RTP Congestion Control Feedback

WebRTC / RTCWeb

  • Champion(s)
    • Harald A. <hta at google.com>
    • Youenn F. <yfablet at apple.com>
    • Dr. Alex G. <alex.gouaillard at cosmosoftware.io>
  • Project(s)
    • Simulcast testing and validation
    • more protocol-level testing in KITE
    • WebRTC over QUIC ?
    • anything that people interested in webrtc and present will want to tackle.

SUIT: Software Updates for IoT

Quantum Internet

  • Champion(s):
    • Shota Nagayama
  • Projects:
    • attempting to define "quantum ping"


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 edit the wiki, log in using your IETF datatracker login credentials. If you don't yet have an IETF datatracker account, you may get one by going here https://datatracker.ietf.org/accounts/create/ and requesting a new account.

Last modified 5 weeks ago Last modified on Nov 3, 2018, 8:26:40 PM