 Hello, I'm Cédric Olivier, working for Orange as an OpenStack Expert as a network automation expert. I'm project technical leader of OP and AV from Test, part of AnuCAD TSC and part of LFN Board as a developer representative. So I'm here to contribute to AnuCAD because we do also our command cloud infrastructure issues. We are creating AnuCAD for the same reason why we created OP and AV many years ago, mostly to ease the NFV journey. So we are focusing now on a few common reference architecture as opposed to OP and AV as a beginning. And we are switching from basic enterprise testing to true performance where I'm contributing and Orange is expecting great results. So it's a big change compared to the classical OP and AV release model. But we are closer to our end user needs now, whatever it's about the operators and the vendors and the different actors. So Thomas, what's your thought and your whole in your company? Thank you Cédric for that introduction. Yes, my name is Thomas Fred Burton, I work for Ericsson as a cloud infrastructure architect. And in AnuCAD, I come from the CNTT part of the reference model where we are sort of developing the input for the different reference architectures for opens back into the medicine source. And for us as a vendor, it means a lot to be able to tap into what the different operators want to have out of their cloud infrastructure, as well as the alignment they are seeking amongst the different virtualized functions. But it's a good opportunity for us to speak with the operators, have an aligned view amongst our vendors to make it simpler to consume in a cloud way. And we're thrilled that AnuCAD is now more bringing CNTT into a regular operation instead of the sort of the task force as it started. But we're really welcome to that. My name is Uli Kliber, I'm working for Huawei as a standardization expert. So we feel that one of the big challenges now in our industry is to bring together telecom needs and cloud native architectures. So the basis for this effort is the NFV technology with its definition of an NFBI infrastructure. The virtualization and virtualized infrastructure management and also the whole MANO stack. So CNTT did a lot of work for the NFBI infrastructure. And now with AnuCAD, the testing and conformance work of OPNFB gets closer to that. So this provides a really great opportunity to better align the understanding for the NFBI infrastructure and evolve the existing technologies in telecom networks to better adopt cloud native and telecom needs. So I think this opportunity will provide a very good step forward with AnuCAD now. With that, I hand over to Lincoln. Thank you, Uli. So I'm Lincoln Lavoie with the University of New Hampshire Interoperability Lab and I'm a TFC member in the AnuCAD project. From my perspective, seeing the growth that the community has undertaken in the development of the combination of CNTT and OPNFB to form AnuCAD is instrumental. As the old adage goes, you know, for those of us that have been around a while, it's always the same clowns in the different circus, right? So what we've done is we've been building the bigger circus, pulling everybody together. And it really is, you know, uniting the communities that are responsible from the service providers perspective with, you know, specifications and what they want that cloud infrastructure to be, you know, all the way through to, you know, reference implementation to then, you know, testing and validating those implementations. And that bringing the community together like that and kind of trying to shortcut those feedback loops and stuff like that I think is what really, you know, and is going to empower us to, you know, kind of take this to the next level and solve some of the cloud problems and challenges that everybody's talked about. So I don't know if you guys agree with that or if I'm jumping the mark on that but that's definitely my perspective of what we're, you know, facing next. Yeah. Now, totally we and so Rick is on mute. Yes. Yes, I fully, fully, fully agree. So we'll see how the community grows in the next week. The scope is very, very huge. We have to fix all our issues. And I would say one of our next key challenge is to agree on KPR and to integrate more benchmarking as well. That's a true, a true need and also to quickly bootstrap the VNF and CNF onboarding performance suites. So the current tests are not that bad. Very good. You could already run them. It gives confidence, but I'm waiting for the next VNF and CNF onboarding performance suites. Yeah, agree with that. And I think one of the challenges there will be to take what we already have with a good conformance suites and combine that with all the new technologies and the big challenge there is to bring in all the cloud native and container work and running the same tests. Now, it's not just a simple step to go, but it's really necessary and will make the work of Anokat very valuable, I think. So go ahead, Lincoln. I was going to say, I think Cedric had on kind of a key point of looking at like the KPIs and stuff like that, because that's going to be a conversation that has to exist between, you know, all sets of the community right so it's going to need to exist from both the operators perspective of like what their expectations are on that infrastructure and that that need and also, you know, the vendors, you know, with helping kind of set that of what they're they're able to deliver today and what they're going to be looking to deliver tomorrow right and like, we have to get kind of all those things aligned in the proverbial clouds, you know, to make this all go. And I think that another challenge that we're going to be facing soon as well is is the inflow of new type of accelerators that's going to make it harder both for the different reference architectures as well as for the testing that that needs to be done, because it becomes more heterogeneous and the ability to handle that both of the software as well as for all the testing suites and so on so forth will be key to success here. And that comes in other for us like Iran is also for that definitely would meet those accelerators to succeed. I will add as a key change also the automation part of being able to deploy and test everything from scratch to the network services. So that's something we start we started in a new kind of entity and we can leverage existing tools but that that would be one of the key challenges as well to run the from scratch to the network services automatically for the next steps. And it asks for pipeline with different actors so it's not as simple but I'm very happy to see that in our specification as well. So at the end of the day I think we've you know this is a huge step forward. I'm excited to see what the next year brings for many many reasons obviously with you know where we've come from in 2020 so see seeing you know this starting at the 21 is that I think a great kickoff for the year. Yes, we'll agree. Maybe that's on a good note to end it all as well. And thank you for this time. Yeah, thank you all. Thank you. Thank you. Okay yeah, I think that actually it was probably about a minute longer than ideal but it actually was pretty good timing. It seemed to flow well are y'all happy with that that take do you want to do another one are you happy with that take. Happy with it. Yeah, I know when I do recordings my first take, as long as I don't make a huge error is often my best because I've kind of got the right energy going on. Yeah, I'm happy with it. Right. All right, also through Brandon and see if he's happy with it. Yep, I will send it to him. And yeah so I will stop recording right now.