* 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. ​

* 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) ​

* 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.

* 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.

* 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**

+

* Champion(s)

+

* Kaname Nishizuka

+

* Jon Shallow(Remote)

+

* Project(s)

+

* DDoS Open Threat Signaling (DOTS).

+

* The aim of DOTS is to develop a standards based approach for the realtime signaling of DDoS related telemetry and threat handling requests and data between elements concerned with DDoS attack detection, classification,​ traceback, and mitigation.

+

* We will test the interoperability between two independent implementations:​

+

* The primary goal is to test the interoperability of signal-channel (CoAP over DTLS) of DOT protocol.

* 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 268:

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**//​.