 Good morning. Good morning. We just finished the. Well, not just a little while ago, we finished the telecom music group call. How was that? What was that? Did you say how was that? Yeah, how was it? Yeah. It was, it was all right. Tom brought forward a project that's getting going. And it was that open telco API or. It was a very generic name, but now they have a specific name. Kamara. I'm not sure how to pronounce it, but. Okay. No code. It's just. Documentation right now, but they do have a get have projects where they're putting some stuff. Interesting. Who was it that you started that? Well, I. Tom put the. Note on to the. In the meeting, that's just to check out. Okay. I'm not sure who actually created it. I'm making a new entry for today in our notes. Maybe I'll put a link to that. I'm not going to talk about it, but I just added it. As more of a notice for everyone in the notes. Welcome, Frederick. Does anyone have any agenda items to add? Nothing much other than wanting to say hello to Nikolai. It's been a super long time. Let's take a look at, I mean, I can go through the events, but I think. Maybe, maybe there are a few people that. New things. So. Let's see. Cube kind of use CFPs are closed. Probably the newest thing and make sure everyone knows about us. A new color-coded event at cube con. Called cloud native telco day. And CFPs are open. Sponsorship spots are open. So we're trying to get people to submit. Sessions and. Sponsor, if possible, and. Ideally bring in. More people from both. The cube con cloud native side and. Telcom side to talk and start working together. By having that event. Right there. And a dedicated versus the ad hoc that we've done in the past. And open source summit. I expect to see. More telcom. Growing in that. We've seen a little bit in the past. At least networking related. So that could be an interesting place to. For sessions, networking related. Yeah. So let's see what practice. I mean, what. Progress have we made. Anything on the air gaps environment. I don't see anything new. So. Jeffery's just started to participate more. I will. Try to ping him and see if he's ready to. Move forward on all the comments that have been made. On this. Otherwise, for anyone that's new. Go check it out. Get some. Updates on a. Victor you've. Combinate already. So we'll. Save it. We want to get user stories through even quicker, ideally, because they'll. Provide context for other things that we're going to. All right. Ian. Have. He was supposed to be on the call today. And I'll have to follow up with him, but let's see. Seven days ago. Fun guys made. A lot of small edits. Maybe right now. Can. Merge these. Let's see. This one is more of a. The comment may change. Compliance. Take a look at it. It doesn't look like a typo to me. Anyone else? I guess it's just, you know, so on. I don't know. I don't know if you just put it. And others, if that's what, you know, if that's what the issue is. It's just for illustrative purposes. Yeah. I mean, it looks like. Not a, the grammar looks correct to me. Unless someone wants a comma before the and, which is. More of a. Where did you study sort of thing? But otherwise it looks all right. I think that was the, maybe the question. Or something. Like maybe he thought it was going to be users, auditors, and. Other users. I don't know, or a specific choice. Versus saying, and so on. And similar. Compliance must use the one users, auditors, and so on. Can identify. Users, auditors, and. Interested parties. How's that? So one new trend we're starting to see in compliance is. What's being referred to as continuous compliance. And so one of the, one of the frameworks that's coming around to help with that from NIST is called Oscar. OS. And the basic idea is that you specify a set of. You define a set of catalogs using the Oscar. Control language. Which is basically like, here's how you do it in XML or Jason. Or. Or similar. And what happens is those, those particular things become something that are well-defined with very well-defined variables. And for some of the controls. You can pull information directly out of the infrastructure or directly from the application itself. So that the application itself is constantly reporting. Or the infrastructure is constantly reporting information about its compliance. So that when you generate these reports, it's no longer people taking screenshots of dashboards. It becomes the infrastructure is stating. This is the current state of the system, which then can be presented to the auditor and drive down the cost of demonstrating compliance. So. I'm going to start seeing it in the near future. So. I'm just keeping you all the heads up on that. Sounds like we need to. Get someone in to do a presentation about it. It also makes me think that. Things are moving back to. Puppet and chef and everything else. It is possible that. Puppet and chef or terraformer senior could play a part in that. It's also another, another spot for some of this could be. Some of the mutating acts with rollers or you might have a. A spire based the tester for determining whether you want to give something a identity or not. So there are. Cognitive ways to integrate with some of these as well that I expect to, to eventually show up over time. The Oscar framework is still very new. So we're not seeing production deployments of it just yet, but there is a lot of interest in energy there. And there will be in the near future, it's pending. To be scheduled, but there will be something in the CNCF. Tag security. On, on our scale that's going to be presented. So. When that's presented, that'd be something I would recommend. Joining in and watching on. All right. If you can you add. Some links to the. Relevant stuff about that into the next place. Sure. All right. Does this make it a little bit more clear. What on Kai was. Maybe reading misunderstanding. Sort of. And so on. We say in other interest parties. Clear to me. I'm going to let someone else do the commit. I'm going to let. And respond to this on what level of compliance. Just to comment. Should find out why compliance will be changed. So why compliance is limited to only a certain level. Okay. And they're tests like a problem. They can see that this is intentional and they can find out why compliance is not possible. This is. A little bit of a little bit of a. A little bit of a semantics and mainly trying to. Possibly be nicer with the words. And what Ian was intending was. Why compliance is not possible on a specific best practice. And you're either compliant or you're not. You may be. Close. Or you may be very far away, but just changing it. Put a comment. Does anyone else have thoughts? It looks. Correct. To me what Pankei is suggesting is a. A good update for grammar wise. This is. Hey, Ian. You joined. I did. Sorry about that. What do you think here about this. Small change. Sometimes I think we're looking at different grammar books. Well, yeah, but network function virtualization is not a thing. You can't talk. You can say I'm a VNF. You can't say a. And NFV. Okay. That makes sense to me. What about the comma or, or no comma? I suspect you can go either way and it doesn't matter. I think it depends on what. The grammar book you're looking at. It's an Oxford comma, so it's optional. So I'm going to leave that one. Can you respond? Yeah. Yeah. NFV is a concept versus VNF. Does that make sense? Oliver. You didn't respond. Yeah. I didn't respond. I just didn't really fully understand the. The relevance of NFV. In this best practices. Document. I mean, this, I know this is going to describe me sort of state status of compliance. I just didn't really understand. And I still don't be honest with you. I can see where all of us coming from. I don't know how it made it in there. I think it's one of the few places that, and I don't think there is anything else. So it's, it's not a. Let me back up. What Anne's tried to say in the past, but it's difficult. We may need to remove it anyways. There's the concept was Pankai saying. This idea of virtual environments. Versus physical machines that are being used. And that's really what this is about. It's about a networking. Platform. Slash. Applications, all the different pieces that come together. To build a solution. And it happens to be. Primarily or entirely. In. I hate the word virtual. Do we have any other word? Not virtual, not container. But that concept, not VMs. Not open stack or VMware or anything else, but just. The applications that are running in. An emulated environment. If we're saying NFE is the right phrase as opposed to VNF here, then fine. But another question is whether or not you need to use the phrase NFE here at all when all it's talking about is compliance recording. I think it's a strange point to get hung up on and take five minutes of meeting over though. I will go and have a look at that. Yeah. Well, I guess it's, are we going to stop using the word NFE mainly? This may be the bigger thing. Unless it's very relevant. So I guess if, if we're going to main. That. If you're going to have that conversation. Then I suggest. You and everybody else go and have a look at the definition of the glossary and see if you like it or hate it. Because that's what determines whether we use it or not. If you can change it, all I was going to say, and if you can change it with what you mean by NFA, then that'll probably make it easier for everyone else. I was fine with it there. But if, if you just, I'll have a look, I'll have a look, but I could probably change it not to mention NFE at all. But yeah, okay. All right. The next one is the same thing and NFA versus NFA. So I'll skip that, let you get to it. And I'm going to let you get to respond to this about motivation and qualifiers. More grammar, you can look at it. Both at the software and process them. That also seems fine. What he's saying, but easy to change. Can we make this the number one non-goal? Wait. That's one, I presume, which he commented on. Oh. Preventing delivery of components. And yeah, fine, we can. Let you do that too. More grammar. Well, no, that's a change in wording, a change in meaning, but yeah, fine. Are not perfect. Oh. And if they cannot be perfect. Go either way. Yeah, whatever. I'm not going to fight that one either. Regular review. This method will depend on the team and the working structure. No, I like how you put it. That's also not a big deal. That one looks like it's right. Yeah, you want me to just commit it. Yeah, I think so. Similarly using a standard format, standard encoded format. I don't like either of those, but yeah, fine. He just removed it. Yeah. Do you want me to commit it? No, I'll check that. The wording and I suspect there's a better one. Sounds good. So. That was it for that one. I cannot click on conversations for some reason. But you can get through it and then we'll. See what's remaining. Hopefully get that one finished out. Oliver. And we get this stateful one through. I don't know. What do we have here? I haven't seen any other additional comments or anything, but I did get a message from Tom. So actually. Honkai needs to create all these new ones that can be a new poll. PR or something else. And then otherwise what, there's nothing else. So yeah, my only comment was I've been chatting with our CSDB expert internally. So if they've got any additional use cases or tweaks, but I think if we want to. Merge this and then we can. Do that by another PR. Which is fine. I'm struggling a little bit. Yeah, I was giving me loads of errors this today. I noticed you and another person as well getting some kind of error. You said you were getting a, well, actually there was the files tab. I guess it is. Okay. Yeah. This says the PR on 208 though. Yeah, I think Pankaj has responded to my, my notification just by his email client. Well, that's like work for me. Yeah. Working for you right now. No, no, no. If I, if I try and do it now while we're on the call. Oops. Oh, it's a 500. Okay. Let me try to open the incognito window. But anyway, it worked for me. So I'm guessing that there's some type of. Gateway proxy on your side of the world. Tom. But like I say, if, if, if we want to merge this now, because I'm aware it's been open a while. I don't have any feedback from our. CSDB expert. We can do that as a separate chain. All right. Well, I'm going to give a looks good to me. Can everyone on the call please come and do a. Thumbs up. And Tom. No, what's your name to scroll down. Are you not listed as a reviewer request up to 100 viewers. Right. I need to add to you. As a collaborator so that you can. Be a reviewer, Tom. You'll have to accept it before I can make your reviewer. Tom. Sorry, it was on mute. Yeah, I've just, I've just got the email. I'll accept that. Okay. Yeah. Right. You're a reviewer. Add a check mark. Denver. Nikolai Victor. Let's get this one. Approved and merged. I'll have to add mine as a comment in the. In the stream there, because when I click on approve, it just gives me a 500 error again. Oh my gosh. Okay. Yeah, that's from my child as well. I'm getting that 500. Just give us a. A thumbs up in there. As a comment if you can. Okay. Okay, done. All right. So that's what did I get double thumbs up. Tom and Nikolai. And you all gave it. Okay. One, two, three, four. So we have four. Can I get one more in? You're going to add a thumbs up to this. I can't even log in to get her at the moment. So now I'm afraid I can go in a good place for that. That's awesome. Denver. Lucena. Save us. If one of you will give a thumbs up, then the call can end. We are all stuck here. We just need one more y'all. How about key sure. We have four other people. Anyone of y'all can give us a thumbs up. All right. I'll check this part. Yeah. Sure. Just add a thumbs up comment. End of the ticket. Unless you haven't looked at this at all. We've been talking about this. Oliver, did you submit this in December? Yes, before the holiday. Okay. It's been here long enough. It's been here long enough for everyone to have had a chance to read it. These are. User stories. We're not saying this is a best practice that everyone must be compliant with. These are user stories and use cases to give us context. Specifically, they're focused around stateful CNFs. So that when we're talking about practices that have to do a lot with the real world scenarios. And I want to suggest. And to everyone on the call. That we adjust the number of thumbs up for user stories and user use cases to be lower. Three, maybe. That works for me. So I'll put that in as a suggestion and a pull request against our process stocks. Okay. I guess can I get a, just a verbal. Or add your notes to the Google doc. If anyone wants Denver. Y'all can just do a thumbs up on. If you give me like five minutes, I will do it after the meeting. I'm just not logged in right now. So. Yeah, I figure you may have. GitHub issues. Yeah, but I mean, you don't have to do it right this second. I don't know what to do with it. All right. Well, then I guess we'll end the call and know that this will get merged. Today. And then everyone else. Including Tom, if y'all come back and have updates for it, then. You can do a pull pull request or open. And you know, add new user stories and use cases. Would be great as well. Thanks. Thanks y'all. Thank you.