 How'd you do? Good, how about yourself? Yeah, not bad. Sorry, just got to go and get the door. We'll be back in a sec. Yep. Good morning. Sorry about that. Back now. Right, that's the meeting notes. Right, OK. So just running through upcoming events. So a couple of weeks. We've got the O&E Summit. And there's a lightning talk about CNF certification. That's good. Then we've got, after that, same place, the Elephant and Elephant Testing Forum, which includes a workshop services for the CNF. Is anyone from this group going to either of those events to be known? I can't travel at the moment, but if anyone from this, the three others on the call are going or not. I don't know. You can hear me, Tom. Yeah, I have plans to travel to the O&E Summit. Yeah, we'll be there also during the NAFIA Summit as well. Oh, OK. That's good to know. So then in April, we've got KubeCon. I think the CFPs are open for another couple of weeks yet. People want to get something for that. And then talking of KubeCon, I don't know if anyone was able to get to the event in Detroit last week. I don't know if there was any feedback on the Konectel Good Day or the event in general. Well, from my perspective, one of the interesting topics for me was multi-network. It seems like the community is retaking that topic again. So hopefully this time they can make it. There were basically two discussions. One, a brief discussion on, I guess, was the Monday. And the second largest discussion was Tuesday. So they tried to cover most of the use cases, implement in details, things like that. Hopefully they cover all the corner cases. We have something that supports multi-network. So they were like trying to focus from the API perspective, try to discuss about the different implementations or different tools, which was a little bit nice, I guess. OK, that's good to know. So was that specifically the network probing working group? Was it a wider group of people? Any other thoughts on KubeCon last week? Found any interesting sessions during the KubeCon? Yeah, I went to a great talk by Ed Warnacky of Cisco about the state of cloud-native networking. Really helped me put a lot of things together about what's going on. That's good to know. So I think most of these talks will be available on YouTube at some point as well, which would be good to watch out for. Right, so any of the agenda items of PR review and then issues review? So I'll put PRs first. So there aren't any open PRs at the moment. There are some open issues. Let's go run through those from the oldest first. So there's one here. Do not run containers with the privileged flag as a best practice. It's got Taylor and Victor as the assignee. But I don't know if you're working on anything in particular on that. Next one, requirements for multi-interface from Daniel Burnier. OK, yeah. Victor started creating that draft. Have you had any comments on that, Victor? Victor, your draft about multi-networks being defined in annotations? Yeah, probably that draft has to wait until the committee decides about the multi-network support, because definitely that new proposal is going to change the way that I'm suggesting the best practice or anything like that. OK, should I mark it as on hold for now then? Yeah, yeah. The other issue that I have, especially with NSM, they decided to reimplement most of the SDK. So when I was trying to update the source code, like to make a valid use case. Yeah, basically I couldn't make it work for NSM. So and also, then it seems to be abandoned. So yeah, so that reduces my use case only for multis, which is not the sense to have a level of opportunity among different platforms or solutions. Yeah. And so the committee you mentioned, is that the network plumbing working group? Or is it a different committee that we're talking about the multi-networking? No, no, no. The multi-network is the SIG network. OK. OK. Just note that down. OK. So the next one is a title to exceptions doc. This is one. So Victor, you were looking back in September and waiting on Ian Wells. I don't know whether you were going to crack on without his feedback or not. So the next one was signed to Taylor. I don't think we're going to be able to get updates on the rest of the issues today. There's one in my name that's assigned to me. I haven't had a chance to look at it. Unfortunately, so there's been no progress on that. So other than the, so there's no PRs, we've gone through the issues. Any other thoughts on QCon welcome? Anything else that people want to raise today? Well, one of the interesting things that I found in the QCon, and probably it's not really network, they were like developing a tool to try to detect some inclusive, I mean, or looking for words that is not part of the inclusive language. So probably I'm going to investigate more about that. Given that we have some documentation, maybe I can implement there. Just try to put it more into the commutation. I mean, it's not a big deal, but as long as the tool can provide us something. So say again, so it was a tool. Yeah, so basically, yeah, the tool is, yeah, I tried to look for words which are not part of a more an inclusive language. Yeah, so it's not a big deal. I mean, it's, but I don't know if they have automated the tool or like make it easier to consume it. Maybe that can help some. Yeah, useful in the documentation effort. Okay, any other thoughts on QCon? Well, as we'll close the call. And I think we're on next week. We're into November next week. Okay, good. I shall see you all next week. Thanks, Tom. Thank you. Thanks for that, William. I'll put that link in the notes. Thanks all. Have a good day, everybody. Have a good day.