Internet Engineering Task Force 101, 18 Mar 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: IETF101-HACKATHON-20180318-1400

Description

HACKATHON meeting session at IETF101
2018/03/18 1400

https://datatracker.ietf.org/meeting/101/proceedings/

A

Barry, how are you doing with your timer so.

B

Everybody's going to get three minutes and we're gonna be held pretty closely to that. And when you hear the greatest song ever written.

B

It's not picking much up anyway. Leila will tell you that your time is up so.

B

Yeah, it's barely audible, but what are you gonna do.

A

Okay and I think to get things started. We're going to start with a mailing list. Analysis is that yeah Neil's great.

C

You can stop, you can upload.

D

E

Create patient.

E

Timer ready set, go we've been working on a tool for qualitative mailing-list analysis on ITF mailing lists. What it does now is doing. Data collection on those 34 gigabytes of IETF mailing lists does basic statistics worth analysis and network analysis by using Jupiter, notebooks and Python. We came up some quite some interesting issues that happen when people run their own mill servers with weird encoding issues, weird dates like 30 seconds of January and the unix time it's beautiful.

E

You can find and contribute on github on in the big bang repo and we've been working on this with a lot of academics and civil society people. So we've been analyzing roughly two million emails from almost two hundred thousand email addresses from 955 mailing lists. There are a bit over a thousand, but these were the ones we could crepin that were not too weird a one email address send about 80,000 of those of those emails, but most contributors sends one or two messages which could indicate a spam issue.

E

What is interesting is what you see here is these are most of them are mailing lists, but also some individual contributors is that you see that the community is quite modularized, but also quite integrated, which is probably that to be expected and some good news. There are some outliers. We won't tell you who they are so another question we had of our presumption is that mailing lists are often Domino dominated by early participants. That's not true, so we've been researching into tenure, it's a complicated analysis. Nik will tell you everything about it.

E

If you approach him after a session, we've also been analyzing a number of messages sent by contributor and even though a few people send a lot of messages, there is a pretty good.

E

Tailor there's a pretty long tail and a few people are not dominating all the list here as well. So what's interesting when we look at individual email list such as IETF an IETF dot org, if you look at the longest threats be, these are all quite recent, so this indicates there is still quite some active discussion and some some of you might be interested in the discussions that actually brought up so much stuff.

E

Then we all could also come up with centrality and you can see the the redder. They are the more people reply to people and there are also some famous people that speak a lot but do not reply to anyone.

E

We can. We can also do word trends and there we can phrase and see that there is a steady increase in the mention of privacy. Security got much more uptake and access got popular and then lost popular over time. You can do with it whatever you want. So if you want to do funky analysis and come to cool tor conclusions, join us and make pull requests.

A

Ok, thank you so in case you're wondering the order I'm gonna kind of go in first in is first to present, so dough did you guys have a day. You do have a presentation. Oh.

A

You don't want this one whoops.

A

C

F

Okay, so this is your fall for the price of one bumper DNS presentation: I'm gonna cover deep adda. Can you hear that? Okay, sorry so I'm gonna cover DNS DNS service, discovery, deprived and overall in three minutes um I'm yesterday morning about half of the people here we're interested in working on DNS over HTTP, which is doe, so they looked at multiple implementations of the o3 version of the draft and the other half of the folks here wanted to work on smaller projects and the other areas.

F

So what got done in doe, if you're interested in nitty gritty details, follow the link at the top, which will take you to a repo which tells you everything about these implementations, the in overview. We had seven different implementations in everything from C to JavaScript, and we also had an interrupt test framework that got started as well.

F

What was learnt there will be a full report at the DOE working group, so if you're interested go along there, but the main thing that we learned is Wow, don't you learn a lot when you put DNS folks and HTTP people at the same tables and they write code together? The headline is it mostly works? Most of the interrupt was okay and there's also interrupts with the public servers that are available.

F

For this, though, two very specific feedbacks of the draft one was that the draft didn't say enough about, should a must on implementing getting posts. That's going straight back to the authors and also that oops error handling was completely unspecified in the draft. So that's going to go in there as you'd expect.

F

We worked through a whole bunch of minor clarifications and bugs we have one fail where doe was not a good fit for the go dns library where nice every lies had already been implemented, and also who knew you can write a Perl, DOE client in 20 lines of code. If that's, how you get your kicks in the other areas for DNS, SD, um Ted and Stuart spent the whole weekend working on the N DNS relay implementation.

F

There was work done on an old draft that optimized how you do Iook so FAR's for dinner, sex signs owned and what they want to do with some measurements to see. If it's worth resurrecting that draft, they didn't quite get there, but they made good progress. There was an epic in trying to implement ever curves validation, but thank Nick Harper thought help with his asm1. In that respect, some issues with throwing I've been trying to implement the latest KS case Sentinel draft and there's also work on a name and wind up.

F

We also did some work in deprive so they get the NS library and stubby can now connect your resolved, it's just by name, and this works for URI for a doe server or name for a Taylor server. We also did a bunch of implementation work around TLS in system Bini, resolve D and find Danis, perfect benchmarking tool, those more compelling and also an experimental chain server is available and just to put it the names of the teams that I haven't mentioned so far, we had two remote participants and Fri first timers. Thank you very much.

F

A

A

Nice use of the template.

A

So how about I to NSF.

D

Hello, everyone: this is a temporal junk from some given University in South Korea this time my student, the PhD student, Jin, Yong ping, him and I championed our eye to another project.

D

So I turned a NSF. It is for the how to apply neck companion and last uncle yang to import a high-level security policy into network security. Function later, look beautifuller XI! So this time 7th grade student at sang-gyun university, six students are participating.

D

This hackathon by PhD student and I participated, and this hackathon and our son code located at this kid, have a link. You can access it. So this is the poster and shows the brief, so our city prefers professors and other Research Institute, dr. Park, and also to Korea Telecom mr. an participate and also student waste.

D

So in this custom project we show the two things. The first one is the dynamic configuration which means map a security function to actual Netaji function located at a security controller. The second one is a consumer facing interface based on last comp and the latest latest either our young data model. So let me explain a one by one. At a time, so you can see I to NSF. A user is other means later a program, so it has some policy such as some.

D

During our work time, employee cannot access some other web sites, such as Google, YouTube and Facebook, so that kind of security policy delivered to security controller using these kinds of the young their immoral. So we can improve import that policy, so security controller using dynamic computation. We trusted our security. Our service is a map into actual at expiry function, such as fire and the Web Filter translate kita and then that policy translated by these security controller and actual if I were a filter, nethersphere function are mapped so that kind of escape function automatically a map.

D

So we used this kind of open source and also we demonstrated our concern using this network comparation based on a mininet. Ok, so it access are blocking according to user group. So this is the project github. This time we showed our therapist on their combo. That works. Thank you for your attention. Ok,.

G

A

Need a lot of speaker for your music.

A

A

So the next one, what's going on here.

A

Okay, so how about we don't need to anymore, so the dots.

H

D

However, let me introduce the achievement of thoughts interrupts, so our haka sampler is here. We tasted the ability between independent implementations in order to see the maturity of these core aspects. Specification of those protocols. Now we have four implementations: one is Oasis by entity, so it is open to the public and rest three are from in the different vendors in the city, great aura and far away.

D

So this spreadsheet shows the our achievement. We check the.

B

D

Now we animate enumerated what are the features of the spec and reject 80s? So if it is supported- and also we check the integrity of those features visually, the test was successful because we could make it more green during this hackathon.

D

So here is our status so thoughts again that the doors open threading protocol protects the internet from DDoS attacks. It makes a distribute. It makes DDoS protection more effective with its programmatic capability. So now we confirm that we can do comparative DDoS protection operation between at least two individual implementations.

D

So this screen capture is almost into impressive and for us we successfully did mitigation request wrong. One is.

I

D

Client to proprietary dot server from a cigarette. Actually, the daughter is a DDoS mitigation at layers, and also we did the same things vice versa.

D

So here is what we learned. We can an idea. I can say we can meet the expectations for adult protocol for the markets in because the core most important specification is almost stable, stable and in this hackathon we tasty the based on the latest specification, so it is proven to work then also a we discussed a lot about current draft also.

D

We talked about new features and they will be shared to the watching groups and also, we really talked on yep on Tuesday rocky rip, okay, to wrap up I'm more than happy if we could include more people in the next action. Thank you.

A

Okay, so how about this one yeah, EMU, hackathon, dot, PDF, don't know which group that is oh e, pls.

H

Hi, so we were the PLS team and I have just one slide on what is heap for the benefit of those of you who don't know if, if stands.

I

For extensible.

H

Authentication protocol, it's used typically for network access. Authentication here is one example deployment where you would use heap or you might use. If is, if you are trying to connect to access point, then you first authenticate yourself a deep and then then you can actually connect to it and get internet access. So eep runs end-to-end between your laptop and and the server there's a bunch of eep method. It's it's not new. So over the past 10 years we have a TLS. We have EEP a ke which uses sim credentials.

H

We have a password a lot of them, but we were just looking at TLS, which is quite widely used specially in enterprise wireless access authentication. So some of you might know that method. Update group was recharter and restarted. It was actually just reach hearted last month and during to reach order discussions.

H

There was people reporting on the mailing list that there are some deployment issues with TLS and they know they notice that certificates have been growing larger, especially our with RSA keys of 4, 0, 9, 6 bits and the chains are also getting long, and this is the case in many enterprise deployments, and what this? What happens is that, even even though both the client and server have valid valid certificates to authenticate each other, they fail because access point implementations drop EEP sessions that don't complete within 40 packets.

H

So our goal was: can we reproduce this error? So in that terms we were probably the only team that was trying to break something that already works.

H

So we started in the morning yesterday by trying different types of configuration. So we had like many intermediate CS and to reproduce the error, we try to have very long chains and large certificates, so we are only using RSA keys, but we were still on to produce the error, so it was still authentication successful and we were very disappointed. So what we did next is there is a configuration parameter that allows you to reduce the maximum packet size. The default was 1396 bytes and we reduced it to 200, bytes and voila.

H

We have a failure, so the AP bars, as was reported on the mailing list, but we also noticed that for this to actually happen with the default 1396 bytes fragment size, you would need to have chain. There is roughly 55,000 bytes, so that's yeah. We only send this input on the mailing list and we'll probably discuss this tomorrow when he meets. We are also continuing our tests with with ECC based certificates, to see how how things are we have.

H

We had two first timers Lexi and clear, and then darshakon I have been before to the hackathon.

A

Ok and thank you to people for honoring that 3 minute time limit legato.

J

Hello: everyone distr I'm, going to present about that young base, TVC service modeling in open daylight.

J

This is that overall architecture over there, so legato is interacting with that business application or could be in the postman, which is or be any risk, client of which is interacting with that. Legato and rest of the thing is underlined.

J

For example, legato is interacting with Bristow and Bristow is communicating with that underlying infrastructure to create a flow or link between those switches. So here we use mininet. Hence we don't have get time to use that actual network box devices, so we used mignonette and in the mignonette we created the flows which have their two switches and between the switch 1 and switch two we're just creating that EVC.

J

This is that- module. Ii is a young based module and is a flexible. We can install it and uninstall it at any time, and if we install it, we can see the list of API is for that. Legato is visible in that API doc exploded and you can see that all those card operation for that legato we can get update post all kind of operations. We can do from that either from that Explorer screen or we can do from that postman script, and this is that implementation over there. So there is a two offices.

J

Look at it. One is San Diego another is that Los Angeles and those two have that two units are defined and inside the service provider network we're creating point-to-point EVC over within uni and uni too, and it's also possible to create multi point or EVC tree. But right now we are just creating that point-to-point EVC. So we are establishing relation between link between that even a one and UNL two and I'm sitting over here. If you want to see any demo, just let me know come to my spot.

J

I will show that what the steps we did and I can learn that small demo for that that the creating of EVC bit into a nice after that uni, we can verify the flow that data is going from. One end point to another end point and after that, a deletion of the DVC that low-traffic will drop down and then again we can verify that. Is it working or not? Okay, that's it from my side.

A

Next up multi-link, you email.

K

Great. Thank you.

K

Okay, so the original plan was to try to get some email implementations of this new multilingual email type underway.

K

The RFC that it is referring to is the RFC 8255, which is a new one that was finished off at the end of last year, and the idea is, you can send multiple translations in the same email and the client will identify, which is the correct one, to show to the the recipient based on their preferred language.

K

So the the plan for me was to bring along my java implementation that was almost finished and used as inspiration for other people. We with implementations of their own in their own languages, what we actually achieved. Well, the plan changed slightly and we developed an email reflecting service, this it's an MTA and it transforms a regular incoming email and returns a an email to the the sender, which is exactly the right kind of format for multilingual email.

K

According to that, the new spec we also developed some client codes that sits inside near mapped or will do when they merge it in and that correctly select the email part. Given a new preferred language configuration that you can set in the client and that will select the right type, the right part of the email given that configuration and also we had a little bit of feedback into my Java implementation. That was very useful. So this was the original plan that we circulated between us before the event, there's obviously quite a lot on there.

K

So we selected two things, so the top one is the the code in the client side for near mark so that when you receive an email, it shows the right part. Given those references and the one at the bottom is the reflector code so that you and create those correctly formed emails skip over this one. So to use a reflector, it's used just in an email, plain text, email with a specially formatted a recipient address, and then the that code looks at that address and then sends you back a an email, multilingual.

I

K

With all the parts and the translations obtained from Google Translate, so if we've got well, this has got English, French and Spanish, and it gets those from Google. Translate creates the multilingual, email and returns that to you. As for the near mark line side, part selection, stuff so on the left is what it would look like before any kind of implementation was added at the top in the middle is the preferred when you've got your preferred language set to French. That's what comes through and then what okay and that's all the code is completing upon.

K

A

Just a reminder to everyone: I really want to encourage you to I know. Three minutes is not nearly a lot enough time to do justice. Please do consider joining us tomorrow. Yeah Monday, 6 to 8, we'll have the happy hour thing where you can come and talk. You know in depth about your your presentation so network time, security.

A

L

Yes, hello on a project we work on the network, time security protocol and yes, it's a protocol, a security protocol to protect time protocols like NTP and.

L

Okay, we're going yesterday was to find remaining issues in the current 80s draft. So the question is: what is the best way to do this? We have currently two different implementations to complete independent implementations.

L

Both are still in progress and have proof of concept character and we performed yesterday is the first interoperability test to find out if it works or not.

L

Our test scenario is pretty simple: we have a small NTS client and an TS server. Two devices with two different limitations and C test results very interesting. We have two part in the communication. The first pass works over TLS 1.2.

L

Here we have T NT s key exchange, it works perfectly. We have small issues, but we solved it. No, it works, but the second way, the time exchange over MTP failed at the first test, because we have the interpretation of C NTS to aft on the server side. So it was a little bit tricky yesterday, but we fixed it and we improved the NTS to aft, so in the second one it works correctly and we can avoid such problems in the entire swath in the future.

L

Okay, what we learned interweb interoperability tests, is pretty important to find hidden issues within these specifications.

L

L

Nts draft works is correct, other implementations works correctly and we have some small issues. We have to discuss some small problems, but it's not a big thing and yes, we have to finish other tests. We have tests only client and so of our implementations, but we have to test the other way. Okay, so it was for more informations. You can shown us and could have or yes, okay.

A

Okay, AB nexts work.

M

Hello, my name is Sanjay Mishra and I'm. Just gonna be walking through as to what we did in this weekend.

M

So the the area that we actually worked on is having to do with delegation of HTTP video session and, in particular the at the hackathon. We worked on a CDN I use case of delegation, basically of content from an upstream Sydney end to a downstream CDN, and specifically, a use case of upstream CDN delegating HTTP content to the downstream CDN.

M

The key goal, of course, for for us is interoperability. Testing was to ensure trust. Boundaries are maintained to the right, as you see here in the picture and also the end user privacy is not breached. A couple of other things to call out here is that in the delegation model, the the trust boundaries are maintained and then the redirection, as it happens, whether it's DNS or it's just simple HTTP, redirect that can occur also that the ISP Kasia is only hold these certificate without the private key of the content provider.

M

In this case, video dot, example.com and and all the decryption material and everything in the keys are hold are held by the log server, which basically returns the decrypted master secret, but not the private keys. So the use case really is that we have an end user requesting to watch a content. From example, dot video comm and the content is hosted on a CDN of choice by the content provider and then delegated by it for the downstream to the downstream CDN, which in this case, is the ISP cache on the edge of the network.

M

So the the flow really is that the user would request content and then the through the DNS see named allegation in this case CDN. Would the content provider would redirect to CDN and the CDN would redirect it to the to the ISP for, for the TLS handshake, overlook here's what we have done? Basically they're the two.

M

The two key aspect is that the TLS handshake occurs with the turn with the lure client, which is which we did on the nginx server and the between the nginx, which is the alert, client and the log server that happens over the world protocol and so just to quickly wrap up as to what we. What we did here was for the interoperability standpoint. We used a client browser and for the trial over the last two days. We really just used chrome and ie the the edge server software was basically nginx.

M

We used to patch the open SSL and then the end server was I guess times up.

A

Okay, my apologies for being so so brutal on the time, but I think we have to be.

A

Ok, mailing list analysis already did so Yuri. Are you here yet? No we'll come back to you re later riot ATP d6.

N

Hello I'm, a teen, leanness and yeah. Basically, I brought DHCP client for riot on all my own this weekend, so their goal was to provide a minimal implementation for prefix delegation on the basis of the current draft for an update for the dhcpv6 RC, and the motivation were that we currently have a very quick hack version of something that resembles DHCP, but isn't really the HTTP, which is called you HCP to configure the prefix of a 6lo border router so that it can disseminate its information throughout paper and so for.

N

Our implementation will required the message behavior for client for solicits, advertisers, requests, replies and renews. We had a very simple set up to so we just had a write native instance, which means that we can basically run riot as a process on linux and kia dhcp server to run our tests against and yeah.

N

We did manage to implement the behavior for solicits advertisement and requests, but we didn't I didn't manage to implement the parsing of the reply messages yet so no configuration happens actually right now, but, as you can see in this little Wireshark them, there are actually the messages exchanged between the server and the riot instance.

N

So what did we learn from the weekend?

N

Well, the most important lesson, I think is: don't get lost in details that took me maybe half a day to get all the information out of the DHCP specifications and put them in a header which I guess when I would have done it a little bit quicker and a little bit dirtier I would have been a lot faster with that and when in doubt, asked the author of the draft or one of the authors and I have to give thanks to Tom ik for helping me a lot out in this this weekend and further steps is, of course, to clean up the implementation.

N

So it's a little bit more camera already finish. The implementation of prefix delegation, then maybe later on down the road, provide more support for other DHCP food features and I already piarc the pull request to the riot repository. So if you want to have a look at the code, it's about a thousand lines of code, you can do it and with this URL. Thank you.

A

Kill us I'm gonna come back to tell us, because that's gonna be a remote presentation and I'm afraid of how that's gonna go.

A

O

Hi everybody I'm Lucas body, I work for BBC, R&D and I was running a little umbrella project, so to speak, all making multicast IP more successful. So if we think about what our problem was for the table to solve is that mass audience is for IP, be IP based. Tv distribution causes scalability issues to the Internet, so do some mathematics, 20 megabits per second per stream times.

O

20 million streams is unhappy for various people around the world, so one means to a solution for that is multicast, IP or IP multicast, and we think that's a scalable way to address audiences, but no, it's been used to date, but success has been limited across unmanaged and heterogeneous network. So we'd like to reach audiences across disparate kinds of networks. You know we realized that inter domain multicast is difficult, are not universally deployed and we have this idea of multicast Islands. So we want to improve discoverability of multicast beyond, say.

O

Maybe traditional means like SDP and I'll come on to that in a little bit. One solution to some of these problems is automatic, multicast tunneling and that helps you reach clients that maybe don't support a native multicast reception, but moving over to the streaming formats say, we think that HTTP based streaming is the future. It's pretty good for unique air and fold delivery, enabled new kinds of content experiences. So what we wanted was a solution to deliver this over IP multicast. So we looked at something like quick and thought that this was udb paste HTTP.

O

Could we make it work over IP multicast? We wrote up a graph that kind of does this and a server push context and a BBC R&D. We built an end-to-end prototype using Google, quick and we've had a demo on our table this week, showing that on a Raspberry Pi our ambition was to move to IETF HTTP over quick. So to enable us to do that, we took our current demo. We want deliver it into this building.

O

We had some of my colleagues working on the implementation, a new client library, what kind of server library to do HTTP over quick built on top of ng TCP 2 and we're also looking at different kinds of clients. So could we have a browser-based version of this and try and address some the multicast into a browser considerations for these things and and test betting and I mentioned AMT earlier, and we had J holin joining us continuing his work at well on AMT at the hackathon I've got an architecture.

O

Diagram I won't go into this in too much detail, but you know: multicast delivery is hard so to get multicast from our home base about 50 minutes away from here.

I

O

Had to go over a GRE tunnel and have support from the IDF network team, that was great, we've got that delivered our table and we had those kinds of clients consuming that stream successfully and what we got done was we continued the work we did that and ran tests successfully. We made some progress. We designed early implementation on this stuff and we learned loads of things thanks bye.

A

Hey I, thank you very much.

A

Okay, how about needs.

P

Hello, everyone, so, to give you a little bit of context, the problem we are trying to solve here is that on the Internet today, when you want to retrieve some unicorn picture, you just have too many ways of doing it. You can do it through your phones or your Wi-Fi, so you're wired link and sometimes our wired link is multi ohms. You can even go through a VPN it satellites. There are many ways of doing it.

P

So that's why the myth working group defines the notion of a PVD which is a consistent set of information that you get from all your different up links that lets you connect to the internet.

P

So now what we are trying to do in the entire working group is to add some more information attached to those pvd's by retrieving JSON object from the different upstream, so each upstream is going to give you some more details about the characteristic of each link, such that when the application wants to retrieve the picture of the unicorn, it can decide between.

P

You know which wanted to use an expensive, the captive portal upstream, the fast upstream or the secure through the VPN, and in order to present that information to to the application, we use the neat project, which gives a middleware such that application can else as well retrieve this information from the upstream the uplink characteristics. Now. One aspect is that if one of your uplink happens to be a captive portal, well we have something.

P

That's pretty nice is that you get your PVD as usual, you reach with your JSON objects and that JSON object is actually going to tell you that your captive, such that your laptop, can connect to the captive portal API and possibly dynamically authenticate yourself such that you get access to the Internet, so that's a way using the pvd's to dynamically attach to a captive portal uplink. Finally, one aspect is that in ipv6, when you have, when you have a multi home network, you don't want to do Nats.

P

So there is a there is some work going on at ITF and it's using a source test routing which basically means that you're not only going to look at the source and the destination address, but also the source address to route the packets. So during this hackathon we made a complete test apology with all those components plug together the PVD object. We had three different PV DS. One of them was kept here. We had some Linux routers, some Cisco routers doing Seder array DVD some Linux kernel was patched PV, DD g leaps. He was patched.

P

We also have an implementation in open wrt. So now not all that was done during the hackathon, but we plugged them all together and had some fixed system to make it all work, as well with the neat project, and now we have a wire Shakthi sector and you can find all that on the github. We also had some work with the captive portal done by Kyle. Thank you very much as 5-second. You can fetch the code and draft. Thank you.

A

A

Let's see we are yeah, we still have a few left, but if some of you haven't uploaded your presentation yet please be sure to do that. We can make another round and get back to you so spin bit. Although I know you have a better longer name.

Q

Okay, good afternoon I'm, so we've been working on scalable privacy-preserving in network bandwidth, independent technology or spin bit measurements in quic protocol. So first question is why um well what the spin but gives you it's a explicit signal that you can use for passive per flow RTP measurements. So we need this because quic is not exposed transport internals on the wire, which generally is good, but it also means that if you want to do passive performance measurements, the quality of your data is much worse.

Q

So the spin bit can be used to replace this loss of visibility, and it effectively gives you something similar back that you would get anticipate from looking at sequence, number and acknowledgment acknowledgement, sequences or timestamp sequences.

Q

It's also secured, and if you would just do a handshake measurement, because you get samples all through the flow and you don't measure any overhead, that's related to setting up the connection. So how does this work?

Q

Well, when a client initiates the connection it starts, sending packets to the server what's been 0, then the server will always reply to the client with packets that have the same spin as they lost off from the server and then the client will always do the opposite, so it will always flip the bits and then send it back to the server. So that way, you get this bit that spins through the network and if you then have an observer on the network and you just look at what these bits are.

Q

You extract the waveform and then you just measure what the half RT or the half period is of this waveform. Then you get the RT of your network. So what we did is we've implemented this into a couple of quick end points, so that's Ming, Pico, quick quickly and quick, oh, and what was really nice is that we saw for each of these ones.

Q

Basically, what you have to do is you have to spend some time familiar familiarizing yourself with the code base, and then you need like 10 minutes and 10 lines of code to add to spend it. So it's really super simple to implement, and then we also looked at a bunch of implementations for observers for this, so we have one, that's really minimal. Just built around go packets.

Q

We have one: that's used around VPP, which is a sort of or or around an experimental measurement platform that we have, that is based on VPP, and then we also have a b4, parser yeah and then a whole bunch of other projects, but the results of those we will hopefully be able to present that hackathon one or two. Thank you.

A

Hey. Thank you much for that.

A

A

Great, is he honest, run enough.

R

Okay, we, let's just we worked on firmware, updates for IOT devices, and this is a recently formed working group and deals with the basic problem that you start off with an ID device comes out of the factory and later you figure out that you have to update that device, because there's some new bugs that have been found. There's some new features that you want to add, and so that's what the this group does in describing the manifest metadata to the firmware and providing that firmware update to the device.

R

So we wanted to get provide feedback to the working group and by looking at the manifest format, which is a digitally signed, Seaborg cozy construct we wanted to get as the figure shows we wanted to get the firmware image with the manifest to the device, in our case using UART, but we've also had Alex to work on Elora based delivery, and we use these this one. Specific port are called k64, F and X people and there's a bootloader on that device that reads that stuff, very, very feisty, digital signature and installs. The new firmware.

R

We had a couple of people participating. Most important is to new participants from Marcos from Infineon and Max from Texas Instruments and Mike, my coworker Brendan from remote, who will be here next week. So it's a first-time attendee.

R

It was a pretty ambitious setup, so we initially started off with the setups of the development environment online IDE, desktop IDE, command-line environments. We got the code working for manifest creation, which is invitin. We max worked on up pseudo bootloader on the IOT device and also on the under update mechanism using UART. The laura1 is still working progress. We got all the setup with the keys and the examples.

R

The code, the C code for the verification, is still working progress. We're still dealing with some issues which I I will describe in the next slide. We produced a write-up which you can find on. This is a bad link. If you, if you're interested in the details and want to reproduce this, we ran into some challenges. um First of all, for those for the for the guys who haven't been involved in this work, setting up the environment and the Bison and all the embedded developing environment. Wasn't that easy?

R

We also had to update the firmware on the device. There's a separate bootloader there for you, art, communication and also debugging, of course, is more complicated. But most of the time we spent on battling issues with the cose see our library.

R

That's it. Thank you.

A

Alright, perfect timing.

A

D

A

Up DNS already did that one okay.

A

Did we do the DTN.

A

A

Etienne, though we didn't do this one yet did we no I, don't believe so.

A

Do we have the presenter coming up? Okay, I see you now.

S

Hello and will come to our presentation. We are DT an which stays for day later on networking team, which is basically internet in space. As far we are trying to address here from.

I

S

Works- and we also have Micro PC n participants, which is the referential implementation of the protocols. I will talk about next slide.

S

So what does our plan? Our plan was actually to check whether referential implementation Micronesian meets following drafts. There is bundle protocol version 7, which is going to Turing to standard pretty soon. We hope it's going to be proposed. Actually this Friday and the render is DTN TCP, calling the convergence layer protocol, which is RFC seven 242.

S

We focused on two problems to be solved. The first one was whether there is enough information in the draft to do the bundle encoding, a decoding- that's quite complicated in this protocol, because we are trying to save as much space as we can. So there is Tibor and all kinds of optimizations regarding sides of the of the bundle.

S

We also wanted to create an easy-to-use API, because Micronesian provides a lot of functionality, but it's not very intuitive to access that. So we created rest-based API and that can be exactly a postman and.

S

We also had difficulties to reproduce test cases, so we visualized in to the cur containers all the work we did so how we did it. We created another implementation based on specs and we let it talk to the referential one to find out whether or not there are some difficulties or other it works. So high results. We had some interesting discussions with our co-operators.

S

As said bono protocol was originally designed for space communication, but they pointed out there might be you phileas case is also on earth, which was kind of surprising for us. We were discussing providing delight or and peer-to-peer data network in developing countries. So basically the idea would be that you have ad hoc, Wi-Fi or Bluetooth or something, and it would distribute information, hope, I, hope. The trick is that the other party, the part, the recipient of your information, doesn't have to be online. So there's a kind of like opportunistic connectivity.

S

We have a new code which you are welcome to access called by DTN. During the inter operational testing, we found an issue that Micronesian actually use a special header which does not meet the draft, and surprisingly it was some historical reasons: yeah, okay, we are running out of time, so feel free to actually see us tomorrow. To answer your questions, this is our team. Thank you.

A

Okay, so we'll see you at the happy hour then and I hope many others. There is a sign-up page if I can get my mouse back.

A

It's on the wiki, if you're having problems finding it all all share a pointer with it later to it later, all right, so Who am I missing.

A

Okay, thank you.

A

451 all right great.

T

So we've been working to validate HTTP four five one, which is illegally withheld HTTP status code, RFC, seven, seven, two, five, it's it's our works part of the Human Rights HR PC group and Public Interest Technology Group. This time we've had new contributors from around the world. Some from Mauritius we've also got a bigger group working on this technology. We've got three new code modules, which makes now seven we're trying to answer a question: count: protocols, increased transparency and serve to protect human rights.

T

So it's a slightly social question and we're using code to answer that so I'm gonna hand it over to hirotaka who will talk about the new code and the new application.

U

Thank you, and so we had three modules. We have implemented that this haxon so to evaluate to measure the how much website extra using the 451 status code. We made the corner two called web page. Actually, we are calling the reddit web website right now and also the if he founds a 4-5-1. We need to have some corrector, so we implemented the corrector and also to visualize the results we made a dashboard of that. Thank you. So this is a dashboard.

U

So actually we haven't find any 4-5-1 say: that's called on the production website, but if you find a son a week and corolla will send to the results the collector, so we can see that what what's happening on the those those websites? Thank you. So um we have to worked on from the IDF ninety-ninth product, but and we have that Singapore water cooler and now we have the character to reflects the results results from the doles browser, extensions in Prague rain and Oh Sakura. Thank you send.

U

That is our our branch so that as soon as we protect the results, we hope we can fix, fix implementation or we can improve our FC, and that is our team and takes so much and you can get the code of github.com. So please take a look at. Let's go thanks. So much.

A

So the LP r, an LP when project is great.

G

Good afternoon, ok, so this work is done within the context of the LP one working group.

G

The purpose of the LP one working group is to compress ipv6 UDP and go up over low-power wide area network tech technologies such as laura1 Zig, fox 15.4, GE and NB iot to start with, and so we have one draft which has been in working group last call for some time now that we are trying to complete, and so we, the purpose for this hackathon was to consolidate the code, the pieces of code that we have for the compression part in the fragmentation.

G

Part of this draft also, the some one piece of code has been developed on a computer using full Python, not micro, Python. Some other parts have been developed for these little notes that one micro, and so the purpose was to get all that together and see it running.

G

So what we achieved. Well, we achieved dissemination of the knowledge of the sports team members got to play with those and understand and master them. We discussed the shake principles with some of the people, newcomers and other team members around the room.

G

We run the existing pieces of code, everybody got to experiment with the existing pieces and then we started the real stuff first implementing on the server side, replacing JavaScript code with Python fixing, bugs that we found in the compression implementation also sending fragments over laura1 using new board brought by the right team, so not quite integrating the fragmentation on riot, but bridging between the two and actually, this was used at the suit table to do the firmware update over Laura when we would send the fragments of the firmware and yeah I think we also got focused time to work on our implementations to discuss and have fun really uniting as a team.

G

What we learned yes once again- and we said before and in previous hackathon as well- it takes time to set up the laurel and gateways the lp1 gateways in general. The modes debugging takes longer, but we got that working yesterday and then we fix typos, discussed interpretation of the draft discuss the implementation of this draft. So I think we are in better shape now than yesterday and more coding to be done. The.

C

Other references.

A

H

A

A

And your RA will have you up next just need to find your presentation here we go.

V

Thanks, so my name is yaara. Echo I worked with our to UM pero and Brian on various kinds of measurements tools or little tests that we thought were interesting for some reason or the other, and they were actually couple of different things. So the first thing that that we worked on and I'd be working a little bit for the last couple of weeks is basically experiment with different algorithms. That would do a similar thing, as traced out.

V

Does that yeah sort of figure out what hopes there are to a destination or how many hopes there are? And it actually turns out that that is it's quite an interesting space I've been trying to figure out if there are different algorithms that would actually excel over over other algorithms.

V

So here in the picture, for instance, you see the traceroute algorithm, basically just increase the TTL or decrease it, and until you hit the right destination and that that's sort of grows linearly as you, your destinations, further away, the more packets you need to send, and then we came up with this idea of a binary search.

V

You can sort of try and guess where, where the destination might be, and then, depending on the answer, you will go either on the lower the higher half and that actually obviously scales better now whether that actually matters depends on whether you you care about sending many packets on the network or not, if it's just debugging your own network, it may not matter in some other cases might actually matter and so the random looking graph.

V

Here's is a comparison, algorithm, just doing a random test on different kinds of TTL values and then deciding based on that and that obviously keeps random results. The other thing that we were testing on was or making making this little tool that would figure out if the destinations reports which TLS version and it can be used for many ways, for instance, testing across the internet for our sights.

V

What what they support so this this afternoon, I did this test, we're included, I, think 60, but most popular websites on the on the internet and came up with the answer that the average TLS version across the internet for those sites is one point two zero. Three. Two and there's a couple of other things as well, so we're not really sure where this leads, but but it's at least I found it interesting hacking I like to do so. That's it.

A

So we we have a TLS 1.3 presentation. Logan. Can we can we hear you or do I need to do something? So we can hear you.

A

Yeah we can. We get some feedback, but you're, audible,.

W

A

The audio is not great.

A

There anyone from meet echo or any of the audio folks are you here, I'm, not sure what to do to make that a little better hold on just a sec.

A

We're gonna see if we can get your audio a little better Logan.

A

Anyone else with a presentation we haven't done yet.

A

We got them all.

A

Anyone want to do a presentation like anyone want to talk about your project where you don't have a presentation. You're welcome to come up as well, otherwise, we'll just finish with with Logan in the tls presentation. Once we get the audio straightened out.

W

A

It's probably a little better we're still we're still working on it.

W

A

Okay, well, why don't you go ahead and go and if it gets bad, we'll stop you, but otherwise you can go and all advance slides for you. Thank.

W

W

So our in here was to look at T is 1.33 variety of hundred and one hug fun. So here what we are doing is and you'd go once like what this.

W

Jaws are connected, so the goal here is mercy around application. Integration, open SSL, pass without the release of open SSL with TLS 1.3, and the goal here is to work the drop, 23 and work with upstream open source project. So bad now you can principle, take something like double you get and just specified. I want to do a theorist, 1.3 only connection, so the.

I

Idea is to implement.

W

This across the.

I

W

Open source project so now that we are getting very close in the working group to finalizing TRS 1 2 3, the idea is more integration into application packages and, let's see what breaks there.

W

Okay, so this is what we've got done, w get. It was done just a few days before her ITF and her than one acaba money was done since ITF founder at hackathon. This time we just did tests with religious OpenSSL release, Nagios plugins check HTTP the pull request via was reviewed positively, and it's going to be in the next release. The HTTP per will request already merge. Nice thing is, but now we've get.

W

You can specify what you want here as one country and something but I didn't mention also is a period Eston, l, commercial incentive of meeting these vendors anniver nagas legging check said, which is which has been merged on the first day of a hackathon and then there's a nobleman.

I

W

See which is a HTTP downloader and when the interesting one is eclipse pow, it's basically a mqtt library and midnight TLS 100 millivolt, so it will go only up to gs-14 tube, so it's useful machine to machine from acacia and then there's hitch, which is a basically a TLS proxy, but partially still working progress. So what we learn? Basically, we have to work with upstream projects, because if you don't follow up with your batch, your bash become still and that's an issue. Also one comes to integration application.

W

We also have to take into account compatibility with all the OpenSSL releases, which makes reintegration harder and interoperability testing with vertical TLS. One point we serve optimization: we build a number of bugs actually so, for example, in what particular case we were able to development is one whole freaking, town, client, hello bucket, which was actually not well constructed, so with juice like workshop, which makes it really really helped to deliver care as modernity and whatever things.

W

But we learn is that we should have sent the announcement earlier so that we fill up the movie, so fatigue is completely removed from Mauritius. So we met in in a place called purgatory mushas, so best by few people were involved.

W

So I've just included a few pictures of remote participants.

W

So I think you get better weather.

A

And more fun than we did.

W

So again, thank you to everybody. Nixon, even thanks to Chavez was very cool, and the of a chair or vit apocryphon session have a meet equity, which are they very helpful to suit your pencils developers who took time.

I

To evolve with.

W

Your adventures doing.

I

W

And again, haven't half of everybody. I would like you see multi-purpose baton, Terrace, one two, three, maybe of the next idea. Thank you very.

X

A

Yeah Thank You Logan and enter the whole team there all right, no one else right or are we we're done with presentations? Anyone else last chance can run up here and remember, even if you weren't doing a presentation here, if you have some results, are you waiting to do a presentation? No, okay, still upload your.

A

If you have a some slides that are useful and you don't feel like presenting them here, then that's that's fine, upload them to that same github repository and then all transfer those all to the meeting materials so that we have a record going forward. That's associated with the with this meeting. So a couple things now: one Tusker are you here.

A

First of all, I didn't want to say anything before the presentation started, because I was counting on the network to be up and it was, and so I really want to thank everyone who especially Khan and Chris Tusker, who kept the network up for us. If either of you are here.

A

So you know that they really did a great job of meeting as many of our requirements for the hackathon special Network, setups and and whatnot as they could. But the one thing they did ask me was next time. If we could get those in even earlier, they ship all their gear about a month before so for IETF 102, they're, gonna ship, it all the gear out a month before, if they, if they have requests for special things, they do the best they can with what they have here.

A

But if they learn about those requests ahead of time, then you know they can do even more. For us, for example, some people asked for four VMs if we had the ability to spin those up. If you let us know ahead of time, then yeah we'll send a server and be able to spend those up for you and get them on the network, just as an example. So any anything you think you're gonna need I, know it's hard to plan ahead, but but think about that- and please do plan ahead other than that.

A

I do have a couple slides that I want to share. So let me get my laptop.

A

And I want to thank I want to thank everyone for being so so good about the presentations and listening to.

A

And, as always, we'll be looking for ideas about what we can do to improve things in the future, so, hopefully I think putting things in github seemed to work pretty well, and it has some other side benefits too.

A

Need to read my email, sorry about that, okay, so what I wanted to show was just a couple reminders for what we still have to come. So after we leave this room, it's going to get converted into the IETF lounge and part of the IETF lounge is going to be the code. Lounge I'm, not sure exactly where it'll be, but it'll be in this room would be pretty easy to find. It's just going to be a portion of this room. That's kind of set up for coding or maybe it'll, be the whole room, but anyways.

A

If you come to this area, you're sure to find it, and you can schedule a time if you click on this link and there's a link in the in the wiki for the hackathon. You can set a time when it's mainly just for scheduling to help your team know. Hey we're gonna, be here at a specific time and to let other people who are interested in coming and working with. You know that you're gonna be here at a specific time, so you don't have to schedule time. It's not like. We turn anyone away.

A

It's just to help you with your own time management.

A

The other thing is what we haven't done before. This is an attempt to find a nice thing to replace what we're missing now by not having bits and bytes anymore, so we're calling it hack demo, happy hour, it's going to be in here as well. The thought is, you can set up your whatever your demo is, or you know, just set up some space here during the day tomorrow and then from 6:00 to not 6 to 8 we're just going to have some light. Refreshments here and there'll be non-alcoholic drinks.

A

There will be a cash bar if you feel like having a beer or a glass of wine, but really the idea is to have a couple hours where people can come and talk to you in depth about your project. If you have a demo, you can charm the demo, you can run them through your slides. They might want to see your code and learn. You know what you did, how to get access to it, how to build your project. They just might want to ask you questions. You know whatever.

A

So it's kind of a social atmosphere where you can have those more in-depth conversations that you know we couldn't do here with a three-minute presentation. So for that we would really appreciate that you, you sign up again. It's not so much that we have a shortage of space, but that's the only ways that people will know what projects are going to be here. So the sooner you sign up the sooner anyone else interested in that's thinking, hey should I go to that thing or not. They'll see!

A

Oh, hey the you know the quick projects going to be there. Cool I really want to see that or you know whatever your project is so I recommend you register as soon as possible if you're planning on doing it. If you haven't already, you know, please go ahead and do that. The links for that are also in the hackathon wiki.

A

A

So, as we always do, I would love any feedback, good feedbacks, always nice to hear but any constructive feedback. Any criticism. That's that's good to hear too so, if you feel like sharing something or have an idea- and you want to share it publicly now- that's that's fine, you can you can shout it out or run up here. Grab me anytime during the week. That would be fine as well yeah we ran out of shirts, so I you know, did a great job.

A

We actually got the shirts here on time, but we only had 200 of them and we had as of lunch. Yesterday we had 225 people in the room. That's not counting the remote participants, so sorry that I don't have more shirts. We're not going to get more shirts.

A

I want to thank I, do have a slide thanking my team because they put up some money so that I could get shirts, but only enough money to get 200 which, which seemed like more than enough. But the response here and the turnout was- was fantastic and I really want to to apologize for the lack of shirts. But thank all of you because you know, as you know, that this hackathon doesn't happen unless we have champions coming here.

A

Leading projects, participants participating in those projects, and it's really amazing the way all of you turn out a sacrifice your weekend and fortunately we didn't have to compete with the weather so much. This I don't think anyone wanted to be out in the snow. Maybe that helped, but but no really seriously. I appreciate everyone. You know taking advantage of this opportunity and we're seeing great work. Take what you learned back into your working group. I.

A

Think that's fantastic when that happens, and you spread the word seeing so many first-time ietf people here is fantastic and for those of you who came and you're not staying for the meeting. I hope you do stay involved with the IETF in other ways through the mailing list. You know whatever and maybe consider a future IHF meeting we'll definitely be having the hackathon in Montreal almost positive. The dates will be exactly the same. The Saturday in the Sunday same format, hopefully we'll get a really big room.

A

Hopefully we'll get enough t-shirts and I think that's all I have to say Barry I.

B

Just wanted to thank Charles because we don't he doesn't get thanked enough for the great work he puts in with this. It's a lot of work.

A

Wow we actually finished early, so so thanks again, I hope. Everyone has a great week here or you know evening, if that's all you're staying for and yeah.

I

A

For well I think was the the biggest and most successful hackathon. Yet.

C

I

Yeah, yes, the hot Archie.