 Hello, my name is Trevor Cooper. I'm with Intel and I work on cloud native infrastructure technologies for 5G and Edge. I'm very excited to be here today with my colleagues Fuchiao, Mark and Pierre for the launch of Anaket. I've been a long time contributor to OPNFE, I've been a TSE and on the TSE project technical lead and I've seen how OPNFE has a unique capability to solve problems, do integration deployment and testing. On the CNTT side, I believe that the specifications that CNTT is developing are going to help solve very significant operational challenges to simplify deployment and make cloud native technologies much easier to consume to help accelerate the adoption of 5G and Edge. And I think by bringing together the two communities are going to create a real virtuous cycle of developing specifications and implementing them in real time to improve those specifications. Mark, how about you? Thank you, I'm Mark Byrell from Canonical and I've been involved in OPNFE since only about 2016 which is close to the beginning but not the beginning. The thing that I found the most interesting and loved about OPNFE is how as a community we all pull together and we're able to share knowledge and strengthen the various projects that were inside of OPNFE. One of the main purposes of OPNFE was to take telco requirements and essentially work upstream to ensure those requirements have been met. In addition to that, we also have a continuous pipeline to ensure that we can prove that the requirements have been met, that they are functioning as expected, as well as to add in case any inadvertent regression happens in the future. The heritage of testing inside of OPNFE is a wonderful aspect of how we were working together and as CNTT came around we started coming up with requirements and specifications for interoperability between the different NFVI vendors or virtual function vendors and the different platforms and trying to really reduce the matrix of combinations of different open stack providers with different technologies and only certain VFs worked with that. Once I started looking at that and OPNFE it really made sense to me that OPNFE starts taking its requirements from this CNTT project and now we're really closely aligning and forming a new project called a new kit which I think is going to bring tremendous benefit to the ecosystem. Fuchiao, what are your thoughts on this? I was involved in the OPNFE community ever since it's beginning in 2014 and also I was involved in the funding of the CNTT community. From my understanding these two communities actually represent two aspects of the NFV involvement which can never success without each other. CNTT actually provides the guidance and requirements and the direction and then OPNFE provides the capability to try real new things and take actions. So that's why we're pushing these two communities together. So that's in the years when OPNFE first founded the focus more on the carrier bridge features improvement for the platform like OpenStack. These years although NFV has been deployed in the cloud in operators there are still problems that operators or vendors cannot solve all by ourselves. OpenSource community is still crucial in defining the de facto standard and interface and also provide us this reference. So far from my understanding operators only actually virtualize the network but the cost and the SOT are still huge challenges for us. So with the involvement of the network virtualization interoperability integration and the need of continuous implement and pass and delivery of the network of the new services do are quite important to us. So we're expecting that this new community indicate to help us to provide more input on this. So what about your soft care on the standard side? Well I think the combination is very interesting. My name is Pierre Lynch. I'm from Keysight Technologies but I also chair the TST working group at Etsy or ETSI NFV. So we build the specifications behind the NFV architecture but also from my perspective we're very interested in OPNFE and CNTT from the beginning. We're participating in both of those communities as the TST chair in representing what we do there but also it's been a very successful two way collaboration in the past with input of real implementations and not just document specifications into Etsy which helps us greatly and then we reciprocated with our knowledge into the communities as well. I love the fact that they're merging into Anaket. I think that's an exciting development to have the modeling architecture and then implementation and testing all in the same organization and everybody collaborating and then we'll keep I will keep participating going forward as the Etsy NFV representative into the CDC the compliance and verification committee and see how we can again two way collaborate going forward within that and to move the actual compliance testing forward for the Anaket specifications. So no, I think it's super exciting I'm going to keep going with this and I think it's a great way to move forward especially with cloud native technologies which is something that we're working on as well. So with that in mind, I think with the crowd that's assembled here, a bunch of veterans any final thoughts or anybody for going forward with Anaket? I'd like to extend a warm welcome to everyone who wants to join us. Welcome to Anaket. We're a friendly crowd. Come and join us. Thank you.