Internet Engineering Task Force 111, 23 Jul 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: IETF111-HACKATHON-20210723-1900

Description

HACKATHON meeting session at IETF111
2021/07/23 1900

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

A

Hi everybody we've hit the top of the hour. This is the hackathon closing session. I still see the participant number increasing a bit, so I think I'm going to wait a couple of minutes and see let that settle down and then we'll start. The closing.

A

A

Okay, it looks like the the numbers have sepaled welcome everybody to the closing session of the ietf 111 hackathon. I hope everybody had a great time all the feedback. I've gotten is that it's been a good hackathon and I'm sorry. We had to do another one of these online and I hope we can do one in person again soon, but in the meantime, welcome to the iutf hackathon closing.

A

So we have uh we've done all of this. The agenda, the note. Well, uh what we mostly have to do today is the project presentations so again we're looking for short presentations, of which it looks like we have about 10 posted talking about what problem you tried to solve what you accomplished during the week and some highlights of what happened. Lessons learned: what feedback you have to bring back to working groups and what impact on on open source and other sdos you have.

A

So here is the url for the page to submit your presentations. If you haven't already, I will try to accommodate you if you post them now, but we're going to go through the presentations that are there first and then we'll see what we have and that's it. So let me go to let me change my sharing and share the page with that. Let's see.

A

A

Okay, so that should be it and let's go to the first presentation: uh we're going to start with uh bmwg container benchmark.

A

Benchmarking, uh let me grab that okay. I guess I need to share that all right.

A

I'm learning this as I go. Having not done this remotely yet.

A

A

Sharing and here's the powerpoint I do wish a double click worked, but it does not. Here we go all.

A

A

Okay, just to just say next and I will change the slides.

B

Okay, so uh yeah, so let's start so uh hi, so my name is kj's son, so from sunshine university.

B

uh So today, so I'll talk about our hackathon project, bmwj containerized, infrastructure benchmarking, so our hackathon project have been worked from the itef 106 and we maintain our main goal uh is to implement container benchmark environment with the virus, various networking models and compare network performance with various impacting factors.

B

So the older result and the discussion during this hecaton are using to update our bmw draft, but unfortunately, the currently current our draft state was expired last month. So in this time we had one more goal, which is to discuss for updating our draft to uh zero six version.

B

Okay, the next slide, please.

B

Yeah, so this is the contents in the hackathon wiki page, so our team is organized from the sunshine university in south korea and then co-working with uh itunesf and ipwave team together at the itef korea forum. uh So the second term for benchmarking, our main goal is uh to verify packing lost pokemons between different acceleration technologies which are bpp and then dpdk, obs and sriov, and we estimate that the bpp and ustpdk use different pre-switch entities and the packet processing mechanism.

B

So there may be performance gaps of throughput as well as a packet loss at the switch, and another goal is to verify numa affinity impact to networking performance.

B

Actually, this work was done at our previous hackathon actually, but at the time our test was not correct, because our understanding of container talking model was not good, so we tested it again and then there was the numa testing report from other committee, uh which is the vine puff of the anuk projects. So we tested following their test on methodology and verifying in our testbed environment.

B

So at the same time so we're discussing about the draft update. Okay. Next, try please.

B

Okay, so I briefly uh talked about the draft update discussion uh and then move to the testing, so in our previous draft, uh so we found that there was some clear definition and the figures for describing container networking models also, uh first with a survey and then discussion in this hackathon and the really classified container networking model with the pre-switch aspect uh also for describing performance impact factor in the containerized environment.

B

So we gathered the benchmarking experience of our testing as well as testing done from other communities.

B

So it was very useful to us to make our draft more more clear and then contribute to the bmw g to bring the considerations of the container benchmarking. Okay next slide. Please.

B

Yeah, uh so the end for your testing, so first we made our test bed with different acceleration technologies, so we used the three accelerations, uh which is uh the overstep tpdk bpp and the sriv.

B

So for all case or all cases, packets from the external traffic generator are bypassing corner space and the old packet processing is handled at the user's user space level, so we're firstly, testing uh performance from baseline and then especially, we tried to test packet loss uh between the obs, tpdk and then bpp for making the multi-interfaced container. We use the multi-cni to make the v-host user interface and the srv.

B

We have driver interface and the full track traffic generator. So we used t-rex on the parameter server and the between testing server. uh There was no switch or hub between the two servers. Okay next slide, please.

B

Yeah, so the our the second testing was to compare the network performance with the pneuma affinity, which allocates cpu cores for v-switch and the container to the same or different luma node.

B

So you can see the four different core allocation scenarios in the slide, so the older and the oldest scenario we tested performance with the obs and then vpp. Okay, next slide, please yeah. So these tables are shown the uh the specification and the configuration of our testbed environment.

B

So for testing we use the 10g nic card with srv functionality and for cpu location, so it was enabled to provide the higher threading technology and then you can see the other. The configurations are in the tables. Okay, next slide, please yeah. So the as the lizards. uh These graphs are the result of the pneuma affinity test. So the upper two graphs are throughput result in the bpp case and the lower two graphs are the shown obvious obvious pdk result uh so, and each graph includes the four scenario with a different number affinity.

B

So compared with the two different networking technology, the performance results show much better than the obvious tpk result and in both cases, results show that allocating same pneuma node or we switch course and then contain, of course, is more effective for the probe. Improving the network performance.

B

Okay, next slide, please, okay, so the this is for the benchmarking summary uh actually for packing loss measurement. uh So we cannot make any useful result because uh the uh whenever we try to measure with the packing loss with 110 percent of the throughput uh based on the the methodology. But our results were not the consistency.

B

So we have some issues uh raising of about the t-rex uh are having some problem to draw packets, but at this time we cannot say it is exactly tracks problems. So after this hackathon, so uh we will keep our work on these issues and then uh and then the pneuma affinity testing was the research that the most re we expected and it has some performance degradation compared with the uh buying puff test report. But it was uh some reasonable because we tested in the less resources that or then there's uh environment.

B

uh However, the even we consider some scaling, uh but the performance was quite worse, which is uh some some kind of terrible to use, especially in case of the small size packet, so the uh we uh we will check against our the testing methodology and the environment and configuration, and then we uh we improved our some testing result so the based on this hackathon.

B

So our future work is to bring that experience and the discussion by updating our draft and at the same time, so we want to make the some opportunity for discussing with other uh the related communities uh uh for the container benchmarking.

B

So from that, so we hope that it may bring the uh some improvements of our bmw work. Okay, next slide, please, okay! So this is the last slide and then these are the participation of our team and then it is made up the sushi university and then uh thanks to the ita korea forum, to make the joint hackathon local event on and also or with uh it nsf and ipwave team. So uh so the follow the git link uh in in the link.

B

So you can check the old some environment configuration uh related files uh for our hotel project uh so uh and then we hope to meet itf at the on-site hackathon as soon as possible. Okay. So this is the end of my presentation. Thank you for.

A

Listening are there any questions for kj.

A

Okay, I, the next step, is i2 nsf. Thank you, kj uh nice presentation and uh the next one is i2 nsf, which I'm going to bring up now so get ready and after that will be ipwaves, so you can be on.

A

A

Okay, here is i2 nsf and do we have somebody presenting the i2 nsf presentation.

C

Okay, hello larry, and uh this is the jumper jump. Can you hear me.

A

Yes, we can hear you thanks.

C

Okay, let's start, let me start okay, yes, okay! uh This is the hackathon project for i2 nsx working group. So the champions are me and my phd student, patrick ringa. Let's move on next slide, please.

C

So this is the poster for this hackathon project next slide. Please.

C

So our hackathon project, we want to demonstrate the latest version of nsf monitoring, interface data model and also security policy translator. This time we demonstrated two features. The first one is automatic data model mapper for the itunes security policy translator. The second feature is to support real-time monitoring data visualization of via web-based monitoring next slide. Please.

C

This figure shows the i2 nsf framework, the basically, uh the analyzer collects an asset for monitoring data from nsf below the figure and then an analyzer visualize, the monitoring data to detect the security attack and then that information will be delivered over uh application interface and the security controller will update or generate a new policy according me, and then the new policy will be delivered to nsf nsfs next slide, please the basically uh what got done on this custom project left-hand side. This is the architecture of security policy translator.

C

So this time we made a new component.

C

That name is data model mapper between a high level, data model and low level data model next slide. Please.

C

So the first tech task is automatic data model. Mapper, like this figure right-hand side. We have two data models. The first one is consumer-facing interface data model, which means the high-level young data model and also below that uh we have nsf facing interface data model, which means loadable young data model, the. Basically we want to map between variables of high level, young module and loadable young module in terms of young trees.

C

So basically we are using a zhang chacha algorithm to calculate the tree edit distance, to minimize the the distance between young variables as the three unknowns, and then we can map next slide. Please.

C

The second task is a real-time monitoring data visualization. So you can see this web browser displays real time. You are a filter, filtering resources, data. The upper graph is the company resources such as the cpu memory and desk utilization, and then the below figure, the input and the output data traffic.

C

So in this scenario we attentionally made the dos attack and then we can observe the input data curve, the significant increases, and then we can determine this is a dos attack next slide, please!

C

So what we learned this time and then we learned the security policy. Translator can be exported by automatic data model mapper to possibility uh pre-requisite setting for translation and also the monitoring and data of visualization can support the monitoring of multiple nsfs in near time in terms of computing resources and traffic.

C

Finally, with this monitoring data visualization feature, we can perform the analysis of an nsf behavior, such as security attack detection. Next slide, please next step. uh We also enhance the security policy translation transition later in terms of context for the grammar auto construction.

C

Basically, uh this one uh can um partially aid the generation of low level uh young xml file, using this uh context-free grammar based on facing interface data young model, and also we can uh improve nsf i2sf analyzer, with machine learning to detect the new security attack, and then we can update or create a security apology.

C

Finally, uh we want to migrate from um fair interface, the virtualization to container-based virtualization for itunes. F next slide. Please.

C

This is open source project at guitar next slide, and also we uploaded the demonstration video clip at youtube. You can see the performance on ledger next slide.

C

So we built the team with sunshield sunshield university and actually and kanga national university, uh along with my skk team, so our itunes have a team uh work with the ipwave and the benchmarking working group hackathon project this time next slide. So we got a multiple supporter, such as the sponsors from an nrf, iitf, tta and also itep korea forum next slide.

C

So this is the portal for our i2 nsf and the benchmarking okay group and ip wave hackathon teams this time. Thank you for your.

C

A

um Any questions for paul.

A

All right, thanks for the presentation and um the next one, yes, the next one up is uh ipwave and after that will be bmp yang, so you can get ready and I'm going to set up the uh bpwave presentation. Now, I'm sorry, the i2 of the ipwave presentation.

A

A

A

Okay, I have to do it to get out of full screen. First.

A

There's the ipwave: now I can go to full screen.

A

Okay, um ipwave is ready, go ahead, paul.

C

Okay, thank you, lady okay. This is, um if you waiver basic a protocol project. The champions are me and the doctor, uh even a christian next slide.

C

So this is the poster for our ipoa project next slide, please!

C

So, basically, um the last hackathon project item one one zero. So we demon and directed the feasibility uh by udp based mobility, information sharing. So, as you can see, two robots of vehicles, uh which means uh ai on robotics r1 model, so we allowed the message exchange between two rubber beakers using udp, so the ccm and the hdmcm is a corporation contact method for regular driving and ecm is urgent emergency contacts, messages to detect some obstacles in roadway and and then advertise their message to neighbor speakers to avoid accident next slide. Please.

C

This time we want to demonstrate ipv8, 6, neighbor discovery message for sharing a mobility information among our beakers. Using new um nd option label discovery option. It is called the weaker mobility information option vmi, so it contains a gps coordinate such as a latitude and longitude speed and direction.

C

So our question is how to design a new nd option for vmi and how to test the nd option.

C

So we have several of opponents, including uh linux, loss of cat and also rfcs, and the internet draft, so for the uh through approval concept, poc use the law for cap based icmp version 6 to design and test the new nd uh vmi option next slide. Please.

C

This figure shows our new uh nd uh vmi vehicle mobility information option, so this option is described in the following two draft next slide. Please.

C

This shows linux corner and the data structure. Basically using existing linux, icm 2006 neighbor discovery advertisement message and then we can construct the vmi option. Message next slide.

C

Please we demonstrated the um iphone 6 n a vmi option. This message includes a gps location information such as latitude and the longitude in busan, western association, busan, hotel in korea. Next slide. Please.

C

What got done uh we tested the iphone 6 neighbor discovery in the law, socket based, icm 2006 by open source code, and then uh we demonstrated low socket, is a feasible approach to test a new iphone 6 nd option. In the last time we tried to use the corner the modification.

C

It is not easy. So this time we showed the feasibility of a low social care approach, so we tested our two iterably out to the 11 ocd enabled laptop to exchange any messages that include the vmi option. Next slide. Please.

C

As you can see, the sender transmit vmi option message, including latitude and longitude in poisson, and then receiver node, okay, this is a labor of beaker uh displays the transmitter. Centers coordinate. Okay next slide, please!

C

So what we learned you can see. Two laptop computers are regarded as two speakers, so we introduced the ma message: exchange for sharing a fee capability information so to support this feature. The existing network discovery process needed to be updated by defining a new option type, a different mechanism for sending labor advertisement and the neighbor cash dedicated for this new option. Next slide, please next step, we will apply our implementation of nd vmi option to logo vehicle that is the ai on robotics r1 model.

C

We will implement and test our context aware: navigation, cmp service in such a lot of vehicles. Also, we try to design and implement this option with the ip button 6 over 5g vtex interfaces. Currently we are using dsr's interfaces next slide, please.

C

This is open source project at guitar next slide, please.

C

We also uh demonstrated our implementation, so you can see our demonstration video clip at youtube next slide, please.

C

So uh this hackathon project uh is a collaboration work with the sunshield university and the uh national university and congo national university. This is the portal of our active class members, our ip wave custom team. I work with the itunes theft and pm wg and hackathon teams this time next slide. Please.

C

We have multiple sponsors such as nrf, iitf, tta and itap korea forum next slide. Please.

C

This is our um teams for ipua, i2nsf, bmwg, hackathon teams. Thank you for your attention.

A

Okay, thank you very much again, uh paul.

C

A

Any questions for uh for paul about ipwave, okay,.

D

It looks like uh nick yeah you're in the queue.

A

Yeah all right go ahead. Nick.

E

uh Hi there thank thanks so much for um sharing the work. I'm I'm not familiar at all with the vehicle information sharing, but um it seems pretty exciting. I I was just curious if you either this week or in general, have done some work on the security and privacy considerations, it seems like potentially sensitive revealing data that might be shared and could potentially be misused in different ways. I was just curious if you had some initial work on that.

C

Okay, all right: that is a good question, so the information of the location speaker may be a privacy issue, but our goal is to share the location vehicle to support collision avoidance for driving safety, so also we can consider authentication mechanism to protect this message in near future. Thank you.

A

A

Brendan brandon go ahead and unmute. It.

F

Yeah, no, I attempted to- and it took a moment um so this is essentially going to construct the same issue as we have with automated number plate readers so anywhere that you would consider an automated number plate reader to be an invasion of privacy.

F

uh Anyone with an appropriate antenna will have the same thing and, unfortunately, authentication on its own is going to be difficult to make adequate, because anything that needs to do collision avoidance will need to have that authentication information, and I I see this as a very difficult mutual authentication problem to to actually get right without having some substantial cryptographic setup before you can actually exchange data and in a collision avoidance scenario, the latency required to do that sounds problematic.

A

Interesting. Thank you paul.

A

Okay, okay, um so thomas, uh is this more questions for this, or are you the bmp and yang guy.

G

Yep, can you hear me? Yes, we can okay excellent, so I'm thomas from the bmp and yang uh hackathon group next clip please.

A

Just before we go on so now could be prepared. Okay, next slide: you are you have it.

G

Great thanks a lot so this time we were focused installing on uh testing the performance on bmp, the the impact the bgp monitoring protocol has on on bgp and on cpu memory usage on the route processors there, especially in uh in context of bmp arches cited in out and the local with path marking and additional tlvs.

G

We were testing if there is a difference when the bmp session towards the collector is stable, unstable and also while it makes a difference if the peers are flapping or not, and also uh we were curious about the bmp route monitoring messages. If you can actually measure the delay across the bgp propagation and it's if it's always ensured that we have the complete view of the bgp rip state next time. Please.

G

So we were using pmact as a as a for data collection, cough car as a message broke through it for the time series db and pivo uh for actually accessing the data and wireshark for the bmpd sector and exobgb for generating the layouts. There is a link with the small tutorial how you can set up your own environment next slide, please.

G

So this is the the network we used, so we have on the very left hand, side. The exhibit should be generating the vpn v4 routes, where the the juniper route uh is uh basically the route reflector and we were meshing, adjacency rip out.

G

So basically the ultra advertisement towards the worldwide route reflector, where we are measuring adjacency in pre-policy and adjacency, rip out post policy and then importing the routes on two different uh and pspe router on ios on cisco, s60 and ios xr, the testbed was generating 1 million vpn v4 out as fast as possible and on the route reflector. We were supporting adjacency hip in out as well, also that the path marking and tlv drafts next slide, please.

G

So what we achieved this time is that the the automation continued. So we we continued to improve the testbed so now, including also different scenarios, uh where we have like a stable uh in stable, pgp environment versus also initiating uh the the the peerings again. So we can compare uh what's the difference between the two uh we are measuring through young push the cpn memory, consumption on the pgp process and have now uh also a comparison between the four different operating systems.

G

Our next step will be to scale up with to scale up using now also c square 6r and xe as route reflectors and then psp routers, and we are looking forward for an improved timestamping on huawei vrp.

G

Next slide, please speaking about time, stamping. So these time stampings have been improved in in the wire. So this time also ios 6e is able to expose metrics with seconds and milliseconds time. Stamping, and we are looking forward on the huawei via beside that. Millisecond is supported as well. That's important because we want to measure the uh end-to-end propagation delay impact when bmp is enabled next type. Please, ah we were mostly using young push. Different young models, depending on the operating system, were available on some operating systems.

G

It's not yet available to measure that on a process level, so we are used screenscaping cli to get the data next slide. Please! So here uh just a comparison on the left side. uh Basically, when on the central route reflected either pmp is turned on or turned off, uh you see a slight difference in the bgp propagation delay, so the scale is how much prefixes within a second are being propagated across the network.

G

On the right hand, side you can see basically the same the comparison bmp on and off on the central route reflector, but compared to the left side on the right side, we were basically flapping all piers on the out reflector next slide. Please now same thing, but now collapsed on on one graph, so the difference between bmp on off and flapping next slide.

G

Here uh we are looking at the impact on the route reflector in in the middle in terms of memory and cpu cpu, so you can see in the middle. uh So at thousand we were basically flapping, the pier, so you can see basically before and after the flapping the difference if pmp is turned on or turned off in terms of cpu and memory utilization. So you see there is not much of a difference next slide, please, uh since we were uh measuring the the end to end delay across the route reflector.

G

This is basically on the juniper router. We can see how much the impact is, uh or basically when we leverage that bmp turned off turned on on the central route, reflector what impact it has on on the remote routers, and there is virtually no difference in terms of memory and cpu next site. Please also the same on the emperor's pe routers.

G

uh We don't see uh much of a difference. It all depends very much on uh when you're on, in a congestion. uh How quick the the data collection can keep up next slide, please!

G

So what we learned again, it's not the first time that good preparation and test automation was very important on the test paid side. uh We are, uh let's say we we noticed we need to improve in terms of scalability.

G

If we, if we are going towards four million rounds, we saw some instability and we need to inc increase the the performance on the data collection, the big data side and yet again, because it was virtual, we were missing the beers and the cocktails after next slide, thanks to alex pierre paolo, marco and marquis matthias for for joining the hackathon, it was a pleasure again to work with the team together.

G

That's all any questions.

A

For thomas sure,.

A

Also, I think we're all missing the beer and cocktails after and the other socialization that goes along with it. So all right, thank you for your presentation.

A

The next step is big bang and after that we will have id visualizations. So let me get big bang.

A

Started and big bang is here and.

A

A

A

Full screen: okay, carry on.

E

Hi, everyone uh good to see all of your uh projects um I'll be talking about big bang. Today, we've we've talked about this at a few hackathons in the past. uh So if you guys go to the next slide I'll talk about what it actually is, um this is an open source project, uh a sort of scientific toolkit uh used by a lot of researchers for studying, collaborative communities, open source projects and a lot of internet governance groups.

E

We pull in lots of data sources, email get data tracker, that sort of thing and then use the scientific python stack to do various analysis on that, and so we've been applying that to itf with its very long running, mailing lists and and lots of data.

E

If we go to the next slide, we talk about the plan um this time around, we had a slightly smaller group, but we were trying to add new data sources, uh getting mailing lists from a couple other fora, 3gpp and igf, which were of interest to a couple of researchers and then we're trying to connect the data tracker and maybe github as new data sources and that's to get at the sort of research question. We want to look at more this time around about organizational affiliations of participants and the email domains.

E

So if you go to the next slide, we can start looking at some graphs yeah, and this is two uh ietf mailing lists- uh do and the itf privacy discussion list um where the x-axis is the number of participants and the y-axis is the number of messages and that each point is uh is an organization. We've inferred the affiliation through the data tracker and then you can see, and I've tried to classify them roughly into corporations, academics and nonprofits, and so you can see.

E

Maybe what is not too surprising that um many corporations are sending more participants, but also that occasionally, a non-profit or an academic group um might only send one or two people, but send quite a few messages. So that's just a couple of mailing lists and, and hopefully we can apply that to a larger set of data on the next slide.

E

We can see some other work done on 3gbp, so this is a similar kind of analysis, except just using the email domain, rather than using the data tracker and document authorship to figure out um affiliations and and they've also looked at time zones uh kristoff maps the time zone of the mail center to see um where participants are sending from that might be something we should try to apply to ietf data as well, and then the next slide has another graph.

E

This is looking at uh participants based on email domains and to look at the sort of um standard deviation. How how much of a range there is within a single domain about how many messages are sent to a particular mailing list, and so said, benthal is working on this, hoping that we can maybe do some machine learning to do some inferences based on different domains and how they, how they send different uh patterns of messages to a particular mailing list.

E

So those are our graphs, uh hopefully we'll be able to build on that in the in the coming months. um On the next slide, we have a few lessons learned, um yeah or relearned. I appreciate that was one of the other presentations. um All data is messy. We always see this. It's always a surprise, even though we see it every time on on things like organization and affiliation. uh Those are very messy concepts.

E

uh The data tracker um thanks to everyone who helps run the data tracker that has some great data. The api is providing us um useful things about affiliation and document authorship. We also connect this at github, but that seems a little less promising um lots of people's affiliations are changing over time, particularly at ietf, um and so that would be useful to look into and then one challenge about the remote hackathon. We were all different countries, it's much harder to debug someone's python issue uh from a long way away.

E

um Finally, on the last slide, um these are team members and you can follow this link about the research project um and we welcome both contributions and also research questions. If there's something you've wanted to know about itf participation, um we have some tools and one and one look at that data.

A

Thanks everyone.

A

Okay, thanks uh thanks nick um um any questions for nick.

D

Yeah, I actually had a question. This is charles. You know the question I had was in regard to github and I don't know if you saw any instances where people were um having automated messages from like when you do.

H

D

Github it sends it to the ietf list. I don't know how prevalent that is, but did you encounter that and just how are you dealing with that.

E

uh That's a great question.

E

I I haven't run into that problem, yet, although I am, I am prepared for it um because yeah there there is often that case where um we're, assuming that an email address always refers to a person, but um yeah, like updates from um updates from github, might look like they're from a person but actually be from a robot, and we also see that, like there's often an outlier in many of the larger analyses for um sort of like administrative email addresses from the ietf right whenever they send an announcement of a new, uh a new draft publication or a meeting request.

E

Something like that. There's often an outlier where it looks like the most active person is uh internetdrafts.itf.org. um So that's that's one of those uh messy things. Do we have to clean up one of those outliers.

B

A

Okay, anything else.

A

All right, thanks nick appreciate that, and next we have id visualizations somebody up to present for that. Okay, here we go, go go for it uh just say next, when you want the next slide.

I

Cool, thank you. um My name is kasira and um ietf newcomer. Can you go to next slide? Please um so problem I tried to tackle was to visualize how people have contributed through internet drops over the time and how different working group has evolved over the time. For that I used a program called ghost, which is used to visualize how people have worked on a github repository, and what I try to do here is to simulate a git log from internet draft data. Can you go to next slide.

I

And uh uh there should be a nice uh image, but it's missing, but that's all right, um so I used bbxml3 reference data, so that has all this information um graph dates and the draft name. So I derived the uh all the information as commit authors as commit committers and then the from the id name. I put those uh drafts into a directory structure. That's, for example, for an ieta for working roof draft. It will be go under ietf.

I

Then the area then the working group and then the draft name and after that, the graph revision with the name as a file to simulate a git lock for that draft. Can you move to next slide.

I

um And can you click on the play button? Please.

I

I apologize for this.

I

Anyway, so feel free to watch that video later and mute, the music so and.

I

From the videos you can see like one one big cluster occurring for individual submissions and then based on a number of um graphs for a working group, there are different colors assigned for different working groups and they are forming different. uh They are from in their own clusters, and can you go to the next slide? Please.

I

uh Trying to do it trying to replay the video.

A

You had to click outside the video yeah.

I

A

Just doing that now, okay.

I

Thank you, and if you go to that github project, then there's a list of links for different work groups from from the beginning of date, from bpxml data uh on how the those were group areas has evolved all the time and there's another video I generated for 2021 for all the drop submissions, including individual ones, and the other working group based submissions to see how that evolves and how people have contributed over the time and that's it. Thank.

A

You, okay, okay. Sarah thank you for um thank you for this and um and welcome to ietf participation. uh Nick you have a comment.

E

uh Yeah, I'm I'm just really excited to see uh other researchers working on the itf data itself on on the drafts. That's that's great. um Have you looked at the data tracker api or can we can we help connect you to that.

I

Yet someone brought that to my attention that I can use the datatrack api.

I

I I I will be looking to make use of that crack api in the future, but so here I just use the data source that I knew about, but oh.

E

Yeah absolutely.

A

I

E

All I just want to make sure that we're sharing.

I

Yeah so will yeah thank you that that will be more accurate, because state record would have the actual submission dates and more information that I can gather from that.

E

Awesome I look forward to it thanks.

A

Thanks again quesara and um I'm sorry, I forgot to say that the next step is asdf, and here is the af asdf presentation already for you. So uh carsten go for it.

H

A

H

You maybe reload reload, that's not the one on the github okay, um but.

A

I can talk.

H

While you do that, so this is a small group that worked on related subjects having to do with the sdf data format, which is indent intended as a semantic definition, format for describing iot devices, their data models and their interaction.

H

Affordances and the the point of of this work is not to create a semantic definition form at number 16, but to to make that useful as a hub for translating between the various ecosystem, specific formats that are already out there.

H

So the the whole, the value of the whole thing, rests on whether we can convert to and from sdf into the the various ecosystem specific formats and.

A

um Yes, getting the right thing, I'm in the uh I'm in the github, but uh how do I get the presentation you want.

A

H

You can download.

A

The html: well, that's what I thought I did and that's what you said wasn't what was there so yeah? When did you do that uh right before we started? Oh, you updated it. Okay, all right! Let me try this again. Then.

H

Okay, sorry, that's okay, yeah! So one of the formats, one of the modeling formats that people here in the itf are probably uh familiar with, is yang. So that's one um target for for the converter work. There is a w3c activity called web of things. There is a microsoft thing called dtdl and so on.

H

So the the point of sdf is to be useful as a hub between all these formats, so that you can take a wot description converted into sdf and then convert it into a microsoft uh description and so on, so that that's the background um slide two please and um the the objective this.

H

The objective for this week was to to bring together the people working on the various converters and, of course, all these converters have a common, have a set of common or similar components that have to do with ingesting and processing and generating sdf. So it's useful for people to talk to each other, and we also wanted to produce some tangible results.

H

The the main result of a hackathon like this is that people talk to each other and understand what the other person is doing, but the tangible result is that we want to come up with some continuous integration modules that one dm, a group that tries to harmonize iot models between ecosystems can use in their model adoption process.

H

So the idea is that if you have a great model for a fridge or a light or light switch, you can send that to andream and and there people can look other similar models. Should this may be merged. Is there something that's missing for people being able to convert between their models?

H

So that's our target organization that that we're trying to do things for um the the main problems this week were number one. uh We have way too many programming languages and platforms. Actually, we are not aware of two projects that use the same language.

H

So it's not like everything here is written in python. Somebody is actually using python, but everybody else is using something else, and that's of course, also related to the fact that we have some some constraint devices that may want to make use of that, and that may be hard in python, and the other issue was that everybody is on vacation this week. So this was a particularly hard week to get people to join slide. Three, please!

H

So, uh despite all this, um what we actually got done was we. We now have a better shared understanding of how sdf actually works, and we have various improvements in the individual converters um that were brought to to the headphone and, most importantly, we have those prototypes of the continuous integration models modules and those will allow using github actions for the ci. So you can clone or fork the 1dm repository and throw your own stuff in there and see what happens, and I think that that's a really useful thing to have.

H

In the long run, um we have learned to look more at round tripping as a test strategy, and one issue with round tripping is that after a round trip you, it's really hard to decide whether you still have the same thing, so you need some comparison function um as well. We also had some interaction with the the w3c.

H

uh They have a meeting this week and probably will have another meeting next week and and we're trying to integrate some some of their work with our work slide. 4, please.

H

So, on the what we learned side, I think the biggest surprise was that we didn't have big surprises, so it all worked relatively smoothly in the direction where we thought we would be uh going.

H

But it's clear that we need to to talk about apis way more, so it is said that the iitf doesn't standardize apis, which, which is by the way, not true anyway, but I think we need more focus on on apis or at least design patterns for shared libraries, if we don't call them apis that ingest sdf and do various processing and validation steps on them.

H

And the next thing we found is that there are three things that that are difficult in computer science, and one of that is naming things and- and we hit by that as well. So we we have to do a little bit more work about name spacing and using json pointers for that um and, finally, a piece of new work that we probably will take to the working group is this uh sdf designed for dynamic action objects.

H

uh We already can do this that that, in the ace working groups, authorization information format, but we have to make sure that that similar things are possible in, in the other components working together and in particular we also have to talk about errors, because if you have physical interaction, you have unexpected things happening slide five.

H

So this was a small group of four uh people: first, two first timers among them, but we also could stand on the shoulders of of the people of at least two people who were on vacation, arie and jana, whose tools were used and which are linked in in the various notes we are taking. And in this slide, so we were six people, four of them present and made a little bit of progress.

H

A

All right, thanks, carsten and um again pleased to see a couple of first timers there.

A

Anybody have questions for carsten.

A

Okay, um that's all the presentations I think we have. Does anyone think you posted a presentation that I did not bring up brendan.

F

uh Hi yeah, um I thought that there was one for suit, teep and uh lightweight m2m.

A

I don't see it here, uh but.

H

hmm I'm not sure how much.

F

H

F

Oh, I thought fairly. Certain hannes did upload it.

A

Okay, I I don't see it in the uh hackathon 111 project presentations, yet.

F

Okay, um it was listed on the uh on the closing. I guess it didn't get uploaded.

A

Okay, do you want to be feel free to talk about uh what you guys did? um If you have slides you can email me, I can get them up quickly and if not, you can just talk.

F

Yeah I can, uh I can get those slides uh emailed over to you uh right away in just a moment.

D

Right because you could even share your strain.

A

Right you, you could just share them yourself. If you want that's true.

F

uh You should have them momentarily.

A

Okay, I can do that refresh my mail, um you send them to the hackathon list or what.

F

Oh, I sent them to uh barrylibacomputer.org.

A

Okay, I am refreshing, my mail, I am waiting for it.

A

Email is the best effort thing. Why don't we just do you want to go ahead and just yeah sure.

F

A

F

Get going with that, so it was uh software and firmware updates for iot devices. uh The hackathon plan that we started with was to get software and firmware to the uh well item. One get software and firmware to a device. Now for constrained iot devices. The plan is to use lightweight m2m, with oscore security for co-app and for regular iot devices, use teep for trusted app update on tee.

A

F

A

I'm bringing the slides up now. Oh.

F

You've got them excellent.

F

uh So next slide, please.

F

uh Then uh the idea was to secure the update using the suit manifest and then uh use the new software firmware uh next slide. Please.

F

So we identified a few issues with the t protocol which have been uh posted to the tp github.

F

um We started work on uh integration of oz core into lachan, for which is a lightweight m2m server and which is a lightweight m2m, client and and that's still in progress uh tested registration with the wakama client to the lashan server using oscore and there's a couple of links to the github for for getting this done, uh and then we also started suit integration in mcu boot and uh that's still in progress.

F

So there's uh a few uh bits that are are going on there and you can see the different parts that we've worked on uh in the um in the the repos that are listed there.

F

Next, please, so we learned a lot. um We had great interactions despite the online nature of the event, um but of course, regular work disturbs the flow and our our plan was uh too ambitious as always um and secure boot loaders turn out to be substantially more complex than you might think, and uh the testing of boot loaders, as it turns out, is uh substantially different than protocol testing.

F

And then we want to uh thank matt gamor for suggesting lightweight m2m. As a theme, it was a great way to sort of get more people involved and work with different people um and so for a wrap up. We've got the the various team members and uh there were some uh additional people helping out from um a variety of other working groups and yeah. Well, I guess in the case of lightweight mtm, more than just other working groups and that's about it.

A

Thanks brendan great that you guys got the lightweight mtm organization involved as well.

F

Yeah oma, I believe.

A

Yeah, how are they um so any questions for.

A

Brendan okay, I guess that um does anybody else have a presentation that I did not show.

A

Okay, uh then, I think that uh wraps up the wrap up uh I wanted to well, uh let's let charles make what comments he wants to make go ahead. Charles.

D

Yeah, I just wanted to get on to say thanks to everyone for for drawing the hackathon and and very fantastic job uh running it. Thanks really appreciate that um I I was uh had another standards meeting going on the same week, so I wasn't able to be as involved in the hackathon, as I typically like to be, but it's it was great to be able to see so much great stuff happen, and I wanted to show off my hackathon shirt too.

A

Very cool and- uh and I guess we will- we should thank icann again for their support um in sponsoring and uh thank all of you who participated then you've. uh You really made the hackathon work and uh and I'll say once again that charles and I are both listed as co-chairs of this hackathon, but charles is the one who does all the work on this. So thanks so much charles for putting these things together and having done so from the beginning.

A

D

Certainly my pleasure- and uh hopefully uh I don't know we'll see we'll find out pretty soon. I guess what's going to happen for 112, but we'll have a hackathon one way or the other so.

A

That way, yes, we will so either in madrid or online. We will see you in november and we'll see most of you next week online during the ietf meeting.

A

And that's a wrap all right! Well, thanks! Everyone.

H

D

A good weekend.

A

A