**Session Date/Time:** 14 Nov 2026 18:30

[00:07:06] **Hackathon Co-Chair**: So... Hello? Good morning. Good morning. Can everybody hear me clearly? Yeah? Excellent. Thank you. Thank you. So welcome to the IETF 121 hackathon this weekend. As as usual, we have the kickoff meeting. And, also, as a tradition, we always ask, and for you, regulars, you have heard this question all for 10, 20, 30 times, But I like to ask who's the... For whom is this the first IETF hackathon? Thank you. Well, welcome. Oh, quite a so quite a number of hands raised, 15 or even more. So that's that's great. Really great. And the next question is the first IETF event for you. Is that... Raise your hands. Again, nice group of people. Thanks. Yeah. Yeah. Because why we always ask is this is a great moment or great event, actually. The hackathon is great start of the week to get the IETF a little bit... To know what's going on in the IETF, to make new friends, to work on IDs, etcetera. So that's that's why I think also the IETF hackathon became so popular as the start of the week. And so why are we here indeed? So one of the things is to move forward with the IETF drafts, discuss IDs. I think half of the work is probably programming, generating code, writing code, or sometimes generating codes today. But I think... And when I walk through the through the hall here to the room, I see many, many people also discussing stuff. And I also personally experience that as very valuable, just thinking about ideas, working out, well, what would work and what won't work, and feeding that back into the working group. So that... That's a great way to start a week. Yeah. The sample code proof of concept. Indeed, that's important of the IETF. And and I think we're pretty successful also in that it it attracts other people than the... Well, the people that typically are contributing to standards are... Also includes the software engineers, the software developers because they... These are essential in in deploying standards in the real world in and, again, university engagement. I think we've seen a lot of lot of students, PhD students working or attending the IETF hackathon. So that's that's a great way. Again, the proof of concepts and the tagline of the IETF is we believe in rough cons... Consensus and running code. That's why we're here, the running code part for this weekend. Great. Good. This is a note well. This is a IETF meeting, so the note well applies. I don't go in all the details, but there are three things we have to to be aware of. The note well says that you have to be friendly and respectful to each other in your communication. If you are aware of any patterns, Alright? So all the ICF contributions follow the RFC seventy one fifty four. So if you have any IP, you have to be clear and transparent about that, and can you also follow-up on the RFC eighty one seventy nine, I think. Yep. Intellectual copyrights in IETF technology. And finally, presentations are also recorded. Be aware of that. So that's sad. And and the rest, please read through the note well. It's important, and we assume you are aware of that. Good. Combining or continuing. So talking about IPR or pro... Intellectual property in general, copyrights. So the code contribution guidelines. So you can work on any code. Your code is not an IETF contribution. It's your own. Think about license, which license you want to publish your code. It's better not to publish code without a license. So think about some open source license or your... Whatever license you think about. Yeah. I mentioned that's not an IETF contribution, but your discussions, your presentations, etcetera, these are IETF contributions and go back to the note well, what's considered to be an IP... An IETF contribution. Good. Projects. Yeah. We have... Well, last counted this week, somewhere on Wednesday, I guess, was around 40, 40 plus projects. So I haven't counted today, But you can find all the projects advertised listed on our IETF hackathon wiki, so have a look. Thank you for everyone putting their project in the wiki. It's also helpful for people that haven't thought about where to... Well, in which project to contribute. You can go through the wiki and find interesting projects, but you can also... The outlining is not super, but you can also go to the lost and found. So if you're looking for participants, you can put your projects in lost and found. And vice versa, if you have some talents but not sure what to... What's a good match with your project, you can put also your expertise and your experience, and so people can find these other projects and people can find these other. So that's all on the hackathon wiki. Good. Agenda for today, we are here. The hackathon kickoff. After that, from Teams around 12:30, there's lunch provided and afternoon snacks. And seven... Sorry. 06:30, there will be dinner, and around 08:30, the room will be closed. As with putting your name to registering for the hackathon, you're also asked to indicate you will, well, will kind of... You sign up for the lunch or for dinner. So I hope you've all done that because that's really important for us in in in in planning how much food we should order for lunch and for dinner. We don't like to waste food. So think about that. And if you've done... Yeah. Well, okay. Right. Sunday. That's important. 09:30, the the the room opens again. At 12:30 is lunch, but at 01:30, everybody is asked to send in their slides for the presentations. So from two to six... Oh, sorry. From two to 04:00, there will be new presentations. I don't know how many presentations we have this week. In Vienna, we had more than 60 presentation, which was too much in the sense that every presentation halfway, I I had to change the rules. So instead of one minute thirty, I asked everyone to present their results in one minute, which was... I think they... The presenters did a really great job, but it was... It's a lot also for the room to hear all these presentations in one minute. So I also want to ask everybody to consider, do you want to present your results tomorrow between two and four, or can you present your results at the working group? So ask your working group chair, can we present some small... Some... Or hackathon results in the working group? I know a number of working groups all... Always plan for that after the chair slides, something like that. Just ask for five minutes, and you can present two or three or four projects high high over. Again, I will come back to that later. But, yeah, we really try to keep the whole two to four time slot manageable and keep within forty ish presentation. Everybody has two and a half, three minutes to present. Good. That's a little bit more time I want to spend on, but I think it's good. The hackathon answered two. The Gather present. So I think that Gather is available for the group that... The the PQ certificates group always use that. Anyone interested in Gather can drop by with Charles and myself. Oh, by the way, Charles is here in the front, my co chair, and Barry is on the back there. So if you have any questions, ask one of us about services or things you like to have. Good. The Gather part, I will skip that. There's a hackathon space, especially for hybrid groups can be very useful. I already mentioned this. Resource presentations, keep it in two minutes because of the number of presentations and really be on high over because people... After 20 presentations, people don't remember the details. So just what's the impact? Why it's important? High over why your project makes an impact and why everybody should learn about that. That's that's my challenge to you. Think about that and pre... Prepare presentations that fit in two minutes. Good. We use data tracker. I think everybody knows now. Yeah. Just like working groups, use data tracker. It's nicely integrated with MeetEco and in the IETF proceedings. So this is the routine. Go to agenda for tomorrow and Sunday. Go to the the two to 04:00 slots. Click on the up... Well, materials, I think. It's the icon materials, and then you can upload your slides to the right slot. So make sure you go upload your slides for the 02:00 slot on Sunday. Otherwise, they end up in the wrong place, and it's a lot of work for us. So we will ask you to resubmit it. Yep. Good. You know the routine. Yep. Also, what really helps us, if you will submit your slides before 02:00. That's that's really helpful for... In planning. Other thing, upload the PDF, and then maybe one of the most important things, if you submit a revision, use the same title because, otherwise, it will end up as a separate presentation, and then it becomes really difficult for us to manage. So you submit the re... If you submit a revision of your slide desk, use the same title of your presentation. Yep. Good. This is also... We still have... Oh, we still have. We have an IETF hackathon GitHub organization. There's the templates for the presentation PowerPoint and in HTML of people. I don't think people use it anymore, but we still provide it. But if you want to have a PowerPoint presentation template, you can use it. You can download it from the hackathon, IETF hackathon GitHub pages. There they are, the templates in HTML and in PowerPoint, but we don't use that anymore for presentations uploading and and and... As we did quite a lot of years ago. Oh, yeah. And people are, of course, can ask for us to to generate... To create a repo repository on the IETF hackathon if you want to share it over the couple of next ITFs and have a stable repository available. So there are some pip... There are some projects that have... So MDS responder p q... Sorry, post quantum crypto... Cryptography certificates. They have their repository in the IETF hackathon GitHub organization. So if it makes sense, ask us, and we create the repository, and we make you a maintainer of admin so you can run it on your own or maintain it on your own. Good. I want to mention this one briefly. As in the... If you have... If you're a author of a draft or it has become a working group document, then you have to ask the chair. There's this additional resources. So you can... Your resource from the hackathon, you can include that and reference that in the draft, in the data tracker. That's really fun and good, so it makes clear that there are implementations of the draft. So there are different tags you can use related implementation, GitHub repo. Have a look at it. If you're still individual draft, you can do it yourself. Once it become a working group document, you can ask the working group chair to update this this field. Good. Hack demo. Happy hour. Monday, they will be at 06:30. Hack... Sorry. Hack demo. Happy hour. You can share your hackathon results not only for the people here in the room, but to all the IETF participants. It's in the East Lounge. It's here just outside the door. And register your team before 01:00 on Monday. Yeah. It's really fun and really great experience to share your results. Any other things? The Code Lounge. Yeah. The Continental 2, I think, is just on the right, if I'm correct. There's the hackathon or the hackathon. There's the code Lounge. So if you want to work through the week, you can find your friends over there and continue to work on your on your hackathon project. Good. I think that's all. Oh, that's... Something went wrong. Apologies here. I will make... Good. So it's not here for some reason. ICANN is the sponsor of the of the hackathon, IETF hackathon. I really would like to thank ICANN for sponsoring this event. Yeah. Yeah. Apologies for the sponsor. I will put it later. Well, it should be in the in the PowerPoint, but this is the PDF rendered. I don't know. Something disappeared. Thanks. Any questions from the room, you can always drop by. I'm sitting here in front and Barry at the very end of the room. Thank you. Success.