 Hello, good morning, Lucina. Hello, hello. Hello, hello. Let's wait just one minute more and we're going to start in the meantime. Can you put your name in the minutes notes. Okay. Well, then welcome for another meeting for this. CNS working group. Today, it seems like we don't have too much items in the agenda, so I'm going to just review what we have it. So the first one is like, you already know, like we have a couple of events coming. The first one is obviously the coupon, and we have a collocated then one day before a coupon. And the rest is just like, it's also really with coupon and the sessions that we are going to have after that in Seattle, there's like one summit. Two weeks after the coupon, so it's pretty close and in the same place. In the same time, it's going to be there. And the developer. This forum. So you have opportunities. It's a nice place to do networking and catch all the chance and interesting things that all the colleagues are doing. So, I don't know, Tina, do you want to mention something about the next coupon or like any. Anything that I is right with those things are like, or it's anything that I have miss and the next coming event. Do you want to highlight. Any talks that anyone's interested in at the common Detroit, or one summit in Seattle, feel free to note those. At, I'll be giving a quick lightning talk on the certification and we'll also be giving a lightning talk about. You know, cloud native best practices and certification at one summit. And we'll be attending the development testing forum as well. We may have a. Another session. About certification. And then for coupon EU, that'll be in Amsterdam in April. And if these are open for another month. And if anyone is interested in sharing with their companies, the sponsorship form. There's an interest form available as Google form. And then they'll share the actual perspective for. In Europe and any telco days. This winter. And regarding the cloud native telco day. Has been published right. Remember. Can you repeat your question please. Yeah, I was just asking all the cloud native telco day. Regarding the schedule, the scope has been published someplace or like. I saw Jeff sharing like the schedule. Of the topics that is going to be present during the. I'll make telco day in Detroit. Yeah, I linked to the schedule up above. Okay. This one right. It'll be in person only. Thank you. Thank you. Thank you. All right. Any question. Any particular comments. Let's move forward with the next. Let's review the PRs. If you'll. Have any new PR, which. I don't know if that's good news or bad news, but. They feel free to add. New things or proposed new changes if you cover something. I think the issues have been. Pretty much the same. Last week. Don was reviewing them. So I don't expect too much changes on that. Yeah, we still. Have anything new on this. Issues. Probably the only. The only thing that we have something I had in proposes. Is just practice. I don't know if that is a best practice, but I will start. The discussion about this particular topic. So let's see what I'm proposing is. To support. Multiple annotations. For different. CNIs or CNI multiplexers. Those CNIs which provide. Multiple network interfaces per pot. So my proposal is to have. All of them defined in the annotations. And in that way. Maybe we can provide. That portability and. Support. Many platforms. Things like that. It is an initial draft where I expect like. Having. Kind of discussion like review and those things. I have provided the link. So you feel like. It would be a good idea or like. A good idea. I mean, it can be. Beneficial of this particular topic or like if you consider. It's not a good idea and also. If you think that. Is there would be a. Another. Best way to define. The. I guess. Is a place to start the discussion. Oh, I noticed that Taylor. Trying to the conversation. Yeah, basically this is the initial state of this proposal. It's not too much. But at least I expect to. To have. That initial conversation where we can. I noticed that. Ian has been. Some ideas. It's like channel. That's great. So. I don't know. I don't know. I don't know. I don't know. Something else. Taylor. This calls. Besides. Particular things in the agenda. Let's just check the PRs. We'll help the art. Which is very hard. Same. I will. They haven't had any particular change on that and. Just start talking about the. The draft that I have great like last week. Is there a either an issue or a get hub discussion. For the multi network should be defined as annotations. Well, we have this, which was great. Like Daniel. A couple of months ago. Yeah. Right. And in that we have. Kind of. Discussion for. I guess his name. He started initial. Conversational. In this time, he makes a few things about. Supporting multiple protocols. Like using it. In this case, he was expressing the usage of. And also. In this time and the mood to have, which is. Predefined the networks. He was combined. Those. Topics. Preprovisioning and. The usage of motors. We, I don't think that we conclude in something. Particular. Like. Was a lot of. Good things to discuss here. That's why. Daniel. It's kind of new. Issue. Some like her. The discussion, but it's not. You're actually related. So. And yeah, that's funny. The best practice is just my proposal, something I have. That I work in. In the past. So. Some experiments where I conclude basically. Where I'm proposing. Say, like. For example, in this case, I have. A CNF that I tried to define with. Multiple annotations. In this case, I was trying to support like motors. And. And the same time. So. That's that. Was the way to. Provide that for quality. So. Just wanted to put it like a. Not proposal or somewhere like. When someone can review it and maybe. Start like a conversation or like. Concluding something like we don't have to do this. Maybe it's not a best practice. It's like. Like that. But, but the point is like. Multiple interfaces in. In CNF is something that it is. Decidable. Or like people are looking. Ways to mitigate this particular issue or limitation in. And it would be nice to have a. Solution or like. Something that to recommend to others to. Work on this. So. Ian was. Asking the question is this. Trying to codify. What people are currently doing. Are we trying to communicate. Suggest an idea to improve the state of the art. Yeah, that's true. It's pretty hard to find. At least. An open source. CNF. For example, so real examples. We have a couple, but like, but most of them are. They're very complex. For example, I know that. Magma has. Improved something, but it's pretty hard to. Just all. What they have been doing. Or. In order to have a couple of them, but. It is just. Very dumb examples where like. I don't think that. Too much policy. To any. Any real example. So what I have seen is like, they just pick one solution. They, for example, just pick. Motos. The most common solution and they. Try to decide their own TNF. Motos. I don't know if it's a good approach. Or. They have to be open to more. More alternative. But yeah, the point is that. It seems very good. That's the chance like. We should be aware of what the OS are doing and. We have to. For something or like. I, this. Seems related to. Also. Not statically. Setting. Network information and code, like. Not putting IP addresses directly in code. Would be. Related to this, not specifying. Your network interfaces and your code. Instead, you're dynamically. Allocating and binding to the interfaces based on what's available. So that all sounds good. I'm just trying to see where it. Fits together and. The example that you're showing would be. One implementation, but the, the best practice doesn't specify. It's exactly how you're doing this, I guess. Which is fine. Yeah, exactly. I mean, maybe we can break it down in. To best practices like. I mean, the first one is maybe. I just say like. Pointing just to not to specify any. Any particular. Network details, like just limit them. The definition to the name of. And that's it. Which is in this case, I guess. The only thing is like. But this body is doing it. Just. Specifying which. Networks are going to be connected, but. It is not specifying the IP address or. Maybe there. I think that. Maybe next time it's a little bit more. The key, which I have to provide. A little bit more details, but probably we can. Reach out to me and say, well, maybe what can we do for. Reducing the. And one of the information. Yeah, you have to provide both like you have to provide the name of the. Name of the interface, but you don't, you're not saying. Anything related with the IP address or the, the sound that you're using. So. This is a little more specific. You have to say, well, it's not going to be attached to this interface. With Danon is just the name. And. With NSM. It's a. It's given his nature is. You have to consider if you are consuming the endpoint or if you are. Offering an endpoint. So which. The pain of the case. You have to define the things differently. But, but I guess I reached certain level of. Abstraction. And this is not. The standard way that they're saying, because they have like a. They need to, I need it containers and those containers have to. Specify all this information. So, so they have him provide. A level of abstraction. I just reached that level of abstraction. And I said, because I create multiple. Architects. But, but my point was. You, you can reach that level of abstraction. Once you have all these things. It's easier to. Get a similar thing and. And offer. This map for definition in the name of patients. But yeah. Ian saying is. Is the right way to do it. I don't know. So your example was. You were limited in trying to implement this based on the software that you were working with, which is emulating. The, yeah, and the specific interfaces are required for the application or, and they're, they're also, I think relevant as far as. What we're talking about in the group. So, yeah. So, yeah. I'm trying to integrate Kubernetes with external, like 5G protocols. Anyways, does anyone else have some feedback for. Victor. And also another thing that I noticed. Taylor is. Regarding the order because most of the. CNS that I have in. In. Yeah. Around it. They provide like a manual the steps to the point things. For example, they consider like. Once a particular container. It's a boy. They keep it. And they are not considered like that case where like. You try to. The boy open. And eventually you need to know reaching that. Ready state. So. That's why. We have created like. These other script, like. I mean, usually. This is what we can expect in. In places like Kubernetes. You, you, you'll have a particular order. Some of the containers are going to start before. Others and. The. Eventual. Readiness is something that is also important. I don't know if that's something that we have. Also put like another. Best practice or another point to discuss. But yeah, it's important to highlight that. The order is not something that we can control and. And eventually we can expect some failures. Like if one of the dependencies is working at the beginning, but eventually. And then the next time that it is. This running again and the treats and other IP address, but can we do with the rest of the. The dependencies. So we should modify the. The point, but they are connecting or like. Because yeah, probably they are expecting that. Point or send the company. Communication through. The last IP address, but. Between a new IP address can. Bring some problems or. Points to consider. Some of that will be covered with. Existing tests that are happening that. At least on that. Scenic certification around. The. Resiliency and other things where. Something comes up. It goes down. A component. It goes down. But writing up the best practice related to that. Probably. Be a good idea. So it's. De-coupling this part. So. You were talking about. How. The timing. Not, not having dependency on another component. I'm saying component, but. I guess if it's. If you're building something and microservices. And those microservices shouldn't. Depend on the exact order. To get up to. To get up to. At least the readiness. Checks. They should be able to get to some stage. Now, internally, they may. Yeah, but not only during. Day zero. Also. They want them to as well. Right. Like. Let's say that. Everything is. Up and running. And it's working fine. But eventually. One of those components are. Down. So. How. How the CNF has to behave like. To need to redeploy everything or like. Just modify the configuration point to a new. Component. For the example that. You were, you're working on with this. This GW tester. This is. Related to. The. Mobile core. Components. And. They're expecting. At least like the session manager or something to. Always be available. You look at. Like the eight. Yeah. And. This is only. Showing a couple of the components, but of course, there's a whole lot more here. So the. Right now it's dependent on. Specific address and stuff. Once it comes up, always to be available. So thank you. If one of them goes down, then at least the. Session manager is always available to go back and talk to, to get the IP address for the other components. And. Connecting the. That specific address, even if it was dynamic. When it was bootstrapped into the system. I don't think would be cloud native for this. After day one. It. Ideally still able to connect and look up using. Kubernetes services. So if. If it goes, if one of the components goes down, then it should come up and it's using. A service. That's going to be community service. It's using. A service that's going to be communicated by Kubernetes. Here's the new address versus whatever it. Had hard coded. And I'm not saying like the whole machine goes away, but maybe it reboots. So now your. Gateway rebooted and it's coming back up. Well, how does it find the MME? Maybe the MME actually moved to a. A new system and has a new address completely. But it should be able to. Find that. Dynamically every time. Yeah. For example, in that case, like. If MME. Is it a boot up or. It is a sign new IP address. All the benefits, for example, you know, the, or. The GW. Has to also. Oh. It is too possible. It's like a positive disease is just recreate a new one with a new IP address, which is going to. The same cabinet another. Or trigger another. Reboot in the dependencies, or they just have to modify the IP address. I'm going to a new. The new IP address assigned to MME. And then me component. So, so yeah, basically I tried. To this example, just like tried to experiment with something more complex. In terms like, or more realistic. Not pretend to be a very functional. I tried to exercise most of it. My, my learnings in. All the technologies. And I just discovered like. That good case where I can summarize all the. Network definition. All in the amount of patients and. Obviously, when I started doing all these things, I discovered. All their use cases. I mentioned that I have to cover. And I don't pretend like to use this in production. Definitely it's not that my purpose, but I just try to. You know, reach those image and try to. Fine. Does anyone else have feedback? Not right now, but I would do whatever I look at it. And a bit more detail. Is the Google doc. And comment mode for anyone that gets access to that link. I don't think that anyone can. Reveal it, but I'm not sure if anyone can modify it. Can they leave comments? Let's do a quick experiment, I guess. Yeah, let me see. No. Okay. Do you hear. If you make it where it's. Comment accessible. Well. If anybody with link could comment. Then we can change it a few and with a ton of spam, but probably okay. Dropping this for sure. And they get have discussions, but probably in the. Get hub issue. Okay. Can always modify it. At least have it in the Google doc and the get hub issue. So we can. The other Google doc. So say in a fourth group. Yeah. And also if you think that it should be that like. To reduce steps before. Before this one, like. I don't know the network definition. How can we define all these things. For proposing. Having all these. I don't know. I don't know. Like breaking down the particular. Just practicing in order to or like three. Yeah, it's also an opposite. Well. Think that. That was the last. Topic in the agenda. So anyone else has. Something to share. Comment. Hearing none. I don't know. Ping. I think you had. You had a. Comment about. Actually villa. Is a new release. And she. We forgot to reschedule the talk on music group. So I went over there just before the call. He was over on that call. From China mobile. Maybe it's not there. All right. May drop a link in there for the new release. Some get some info on XG villa release. Like to see some of the stuff they're doing. I mean, the. Multi interface. Multi network stuff was it when I was looking at the XG villa. A while back. I mean, it was part of the discussion. Yeah. And I'm sure they've looked into that as well. Right. Well, I don't have anything else. Anybody else. No, thank you. Thanks again. To you. Next week. All right. See y'all next week. Thanks. Bye.