wiki:107hackathon


IETF 107 Hackathon

THE HACKATHON HAS BEEN CANCELLED

Cancellation announcement: https://mailarchive.ietf.org/arch/msg/hackathon/9lgOLA-VBU827RU6MUjG7oIUs_M/.

The meeting materials, preparation info, project lists, etc., remain because they may be helpful other efforts related to running code. Keep up to date on future IETF hackathons by subscribing to https://www.ietf.org/mailman/listinfo/hackathon


Agenda

  • Hackathon - CANCELLED
  • Hackdemo Happy Hour - CANCELLED
  • Code Lounge - CANCELLED

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
  • Lost & Found
    • Participants looking for a team and champions wanting help on their projects are encouraged to visit the Lost & Found.
  • 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
  • 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/ietf107-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

Network and Power

  • Network
    • Wireless access to the IETF network will be provided, and from there to the outside world
    • The IETF network will be dual stack with both IPv6 and IPv4
    • Wired access to the IETF network is available by request only
    • For wired access, static IP addresses, or any other special network requests, please add your name, email address, and details of your request in the Requests section below.
  • Power
    • There will be two power strips per table (roughly one outlet per person/seat). If you need additional power for your project/team, please add your name, email address, and details of your request in the Requests section below.
  • Requests
    • Saleem Bhatti <saleem at st-andrews.ac.uk> : ILNP : a routable /60 if possible, please!
    • Michael Richardson, MUD/ANIMA/HOMENET table needs wired networking, extra power bar, and would like DHCPv6-PD.
    • Michael Richardson, SUIT/TEEP/RATS table needs wired networking, extra power, and would like to be near MUD/ANIMA table, but too many to share a table

Remote participation

Participating in person is preferred, but we understand not everyone can travel. We typically have a number of remote participants and even some projects that are championed remotely. Successful remote participation requires a bit more preparation by remote participants and champions of projects with remote participants.

In addition to registering for the hackathon and subscribing to the hackathon list, it is recommended to monitor both the hackathon wiki and the list as the hackathon approaches, determine which project(s) are of interest to you, and reach out to the champions of those projects to determine how best to be involved and coordinate with the rest of the team working on each project.

The hackathon kickoff and the closing presentations are available via Meetecho. The hackathon Jabber room may be used for general and project specific communication.

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 at end of project list)

  • Note, all projects are open to everyone. However, some champions have identified their projects as being particularly good for first time IETFers and/or first time hackathoners. These projects are marked with a star, i.e. '*'. If you are championing a project that is great for newcomers, please add a '*' at the end of your project name.

LPWAN SCHC header compression and fragmentation

  • Champion(s)
    • Laurent Toutain (IMT Atlantique) laurent dot toutain at imt dash atlantique dot fr
    • [REMOTE] Cedric Adjih (INRIA) cedric dot adjih at inria dot fr
    • Shoichi Sakane (Cisco) ssakane at cisco dot com
    • [REMOTE] Olivier Gimenez (Semtech) ogimenez at semtech dot com
    • [REMOTE] Dominique Barthel (Orange Labs) dominique dot barthel at orange dot com
  • Project(s)
    • Interop testing between several implementations.
      • We will provide a set of Rules (in the openSCHC format), that you can convert into your own representation before the Hackathon. We will provide test packets as text files containing JSON hex string.
      • A first test will be that some packets are compressed and compared to the known SCHC Packet output. Some SCHC Packets are decompressed and compared to the known packet output. Each implementation can perform this test independently of the others.
      • A second test is to interconnect two implementations in real time, and to compare the decompressed output with the original packet (before compression). This allows for some degree of random testing. The direct communication between two implementations will use UDP sockets.
      • If time permits, the No-ACK mode of fragmentation can be tested the same way as compression: first with test vectors, second with direct unidirectional communication between two implementations.
    • for documentation about SCHC, see
    • Other goals can be to advance the python open source implementation of SCHC compression and fragmentation. See openschc.net
      • improve the tutorial. In general, make it easier for a newcomer to join the project and contribute.
      • iron out implementation to fit latest draft revisions
      • interface to underlying network (UDP or interface to real hardware)

DNS Service Discovery

  • Champions:
    • Ted Lemon <mellon@…>
    • Stuart Cheshire <cheshire@…>
  • Project(s)
    • DNSSD Support clinic: if you need service discovery for your app, come talk to us and we'll help you figure out if DNSSD is the right solution for you.
    • DNSSD Home Network integration: implementing the HomeNet? Naming Architecture using DNS-SD
      • We've made a lot of progress on the underlying code for this. The task will be to actually try to use the functionality that we've developed for DNS-SD on homenet routers. Bring a couple of GL.inet AR750S routers or your other favorite OpenWRT hardware target device and join in the fun!

Secure Home Network

Champions:

  • Ted Lemon <mellon@…>
  • Michael Richardson
  • Projects:
    • Work on extending hncp implementation(s) to support DNSSEC and ACME so that you can connect to your home router UI from a web browser without a leap of faith and without publishing your root password on the link.
    • tbd

Software Updates for Internet of Things (SUIT)

  • Champion(s)
    • Brendan Moran <brendan.moran@…> (remote)
  • Project(s)
    • Demonstrating manifest creation
    • Demonstrating manifest parsers
    • Enabling TEEP with SUIT
  • Relevant documents:

Remote ATtestation ProcedureS (RATS)

Trusted Execution Environment Provisioning (TEEP)

  • Champion(s)
    • Dave Thaler <dthaler@…>
    • Hannes Tschofenig <Hannes.Tschofenig@…> (remote)
    • Mingliang Pei <mingliang.pei@…>
    • Akira Tsukamoto <akira.tsukamoto@…> (Not decided yet, remote or local)
  • Project(s)
    • Hannes: Implementation of TEEP protocol using CBOR encoding and the COSE security wrapper (server-side in Java, and client-side using C code by Dave Thaler). RSA and ECC-based crypto.
  • Relevant documents:

Sliding Window FEC codec (SWIF)

Computing in the Network

  • Champion(s)
    • Marie-Jose Montpetit (main), Jeffrey He and Eve Schooler
  • Project(s)
    • As the COIN concept is evolving the hackaton will address a group defined project that will be specified at the COIN interim meeting in February. The wiki will then be updates and the github site given as well as the slack channel for remote participation.

QUIC

  • Champion(s)
    • Lars Eggert <lars@…)
  • Project(s)
    • Interop around the latest set of drafts

DNS over QUIC

IoT Onboarding and MUD/ANIMA:

  • Champion(s)
    • Eliot Lear <lear@…>
    • Michael Richardson <mcr at sandelman.ca>
  • Project(s)
    • Work on NIST MUD-PD code to test various IoT devices, integrate with a repository.
    • Integrate MUD Maker with a github repo.
    • Develop and test DPP code with TEAP.

BGP Monitoring Protocol (BMP)

  • Champion(s)
    • Yunan Gu (guyunan at huawei.com), Paolo Lucente (paolo at ntt.net), Camilo Cardona (camilo at us.ntt.net), Thomas Graf (thomas.graf at swisscom.com)
  • Project(s)
    • Extend existing BMP capabilities with new RIB's, message types and TLV's at router and data collection.
    • Perform interoperability tests between router and data collection.
    • Verify that metrics can be used and are correctly referenced to device state and configuration.

RTCWeb beyond-browser Interop

  • Background: Many webRTC apps are based on rtcweb implementations that aren't browser derived. Mostly these stacks are tested against libwebrtc only. This Hackathon table aims to make a start at interop testing between the non-libwebrtc stacks.
  • See: https://github.com/pipe/rtcweb-interop/blob/master/README.md
  • Champion(s)
    • Tim Panton (tim at pi.pe)
    • Lorenzo Miniero (lorenzo at meetecho.com)
    • Sean DuBois? (sean at pion.ly)
    • Anton Venema (anton.venema at frozenmountain.com)
  • Project(s)
    • Collect some RTCweb stacks that aren't browser based or derived from libwebrtc
    • Define basic interop tests between RTCweb stacks
    • Do basic interop tests between RTCweb stacks (SDP)
    • Do basic interop tests between RTCweb stacks (ICE)
    • Do basic interop tests between RTCweb stacks (DTLS)
    • Do basic interop tests between RTCweb stacks (DataChannel?)
    • Do basic interop tests between RTCweb stacks (Video)
    • Do basic interop tests between RTCweb stacks (Audio)
    • Fix bugs....

WISHI (Work on IoT Semantic / Hypermedia Interoperability)

Identifier Locator Network Protocol (ILNP)

  • Champion(s)
    • Saleem Bhatti <saleem at st-andrews.ac.uk>
  • Project(s)

Formal Languages (<fdt at ietf.org>)

Privacy Pass (privacy-pass)

  • Champion(s)
    • Alex Davidson <alex.davidson92 at gmail.com>
  • Project(s)
  • Attendees(s)
    • Nick Sullivan <nick at cloudflare.com>

MPTCP Robust session Establishment (RobE)

JMAP

  • Champion(s)
    • Bron Gondwana <brong@…>
  • Project(s)
    • JSCalendar / JMAP Calendars
    • JMAP-Tester

CORECONF

Quantum Internet Simulators (QIRG)

  • Champion(s)
    • Rod Van Meter <rdv at sfc.wide.ad.jp>
  • Project(s)
    • Extending existing quantum network simulators with:
      • routing protocols
      • multiplexing protocols
      • traffic generator (gravity model?)
      • maybe multicast-like multi-party communication

DNSSEC

  • Champion(s)
    • Loganaden Velvindron (logan_at_cyberstorm.mu)
  • RFC 8624 in various open source projects.

DORMS (Discovery Of RESTCONF Metadata for SSM


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 3 years ago Last modified on 13/03/20 15:18:39