 Hey Ed, I have to finish a couple things in order to get this webinar all set up for an hour from now. So can you drive the meeting? I certainly can. Cool. And I'll see if I can find the link for it as well so we can tell people where to find it if they are interested in showing up. That would be very, very good, because I would actually like to come along for that as well. Yeah, we're supposed to have Bobby there as well. I was having a little bit of trouble getting a hold of him this past couple days, hoping things are okay. He's usually on par with or not. He's usually very responsive to things. I think a lot of people took a longer weekend this weekend. One of the things that this has been publicized is that Cisco basically told everyone to take Friday off to recharge. And so between that and Monday, it's been a nice long weekend. Yeah, that's what I figure probably happened. So, all right, cool. So for folks who are perhaps watching the video, these usually we start about five minutes after. I'll link in the chat if folks go please add themselves to the participants list on the meeting minutes that would be great. And do keep in mind these meetings are recorded and they will be posted to YouTube. Also keep in mind that also if there's anyone on the call who would be willing to share the agenda that would be most appreciated. I posted the link both in the chat and on the agenda as well. Okay, so we'll probably get going in a couple and about a minute here. There's a link in the chat for the meeting minutes so folks could have themselves as attendees on the agenda that would be fantastic. And if someone would be willing to share the agenda that would be also great. Okay, so let's go ahead and get going. Can everyone see the agenda. Yes. Fantastic. So, and there should be a link in the chat please do go at your socials the attendees. So we got it sort of our normal standing agenda. So what I draw your attention to some recurring events, not, you know, that they go out of addition to the normal network service mesh meetings. So, you know, our network service mesh meetings do happen every week on Tuesday we've got a issue PR meeting that happens at 730 and Pacific time. And we have this meeting that's the community meeting that happens at 8am Pacific time. Are we still running China friendly meetings. Does anyone know. I haven't been joining for the last month or so. Okay. Okay. All right. And then in addition to that we have some recurring meetings. The CNCF telecom user group meets the first and third Mondays of every month. And then CNCF sync network meets the first and third Thursday of every month at 11am Pacific. And so those are also good things for folks to attend. So, moving on to major events. So, cube con China has been canceled. We do have cloud native zero. So we're just going on literally today at the top of the hour. And we have a link here to that webinar where are very on Frederick and, you know, Bobby will be talking about zero trust based authentication with spiffy inspire and SM at Opa, which is very exciting. The cube con cloud native Europe that will be happening on the 17th of the 20th. And that will include the SM con you that event will be happening as a collocated event. I need to go track down the events people to get all the details about the virtual event but it will definitely be happening. Awesome. So the OES is also occurring September 28 to 29. I don't think that's actually happening in Los Angeles. I think it's, well, actually it's currently on the schedule in Los Angeles. They've not yet announced going virtual so they may not. OES Europe has been postponed. Cloud con cloud native North America is still scheduled for Boston. And that CFP is currently open. It closes June 12. So I would strongly urge folks to get network service mesh related toxin. We did very well with cube con Europe in terms of folks getting their NSM toxin. So it would be very good to get a whole full raft of them here as well. And that is what I've got here for events are there other events folks would like to draw attention to. Just a quick update actually the China event is virtual now. It's not canceled. It's canceled as physical event but it's going to be a virtual. Ah, would you be willing to fill in some of those details in the agenda for next time? Yeah, I will. Many thanks. Cool. So do we have anyone here from our social media team? Okay, I do note that we, they did update for today. So we're now to 762 followers plus one from last week. 2302 following plus five from last week and 1300 tweets or retweets plus 15 from last week. We had call reminders that went out on Twitter and no the social media last week's video recap from the meetings, the CNCF weekly webinars, various of other events, and some general things around networking and that we're being retreated. And then for LinkedIn stats were to 162 following plus four from last week. We got a link to bandwagon a little bit later, and the content is the same as the original Twitter content. And then the current plan is retweets contributor podcast and the various NSM, con EU 2020 to promote registration prospectus etc. Awesome. Anything else on the social media stuff. So I want to draw folks attention to the fact that we now have our annual review document up for network service mesh. So this is something that as a CNCF sandbox project we do annually. And so this has been posted up for review. It has a bunch about the progress we've made in the last year, I would actually strongly recommend that folks go take a look because I was actually kind of shocked and how much we've accomplished in the last year and I've been here for it. And so you can go take a look at that document. And again, any suggestions for improvements as with any PR are very much welcome. Cool. So additionally, there's discussion going on in the VL three spec. That's starting to deer in the direction of IPAM. So this is a document I think we've talked about before. Do you want to go ahead and talk a little bit about the IPAM stuff that you've added here Denise. So yes, I just put ideas on how we can implement a pump for the first step. So please take a look. Any comments are welcome. Yep. And just to be clear this would just be the IPAM for the VL three network service endpoint in network service mesh IPAM comes from the network service and points. I know it however makes sense to them, but we do need to sort of solve this problem for the virtual layer three and I see that's being built. And so we definitely wanted to get some broader discussion here of how to approach the problem. And I know we've got a bunch of folks in the community who have sort of broad experience with these things. So it's always good to get, you know, experienced hands involved with part of the discussion. Cool. Any other questions on that discussion. So the last thing I wanted to draw attention to and certainly I'm interested in other folks people or things people are interested in is there's a discussion that's starting up around the registry API and perhaps simplifying it. Going forward, we've sort of been stubbing our toes on some of its over complexity as we've been going. And so there's a whole discussion around that that's occurring right now. And this is one of those things where the more voices involved the better. And so it would be really, really helpful if you if you've got some interest in this, please go ahead and get involved. Anything else that folks would like to add to the agenda. It's, I think a little bit of a light week because we've, there's been a long weekend here and cool. So if it's anything else that folks would like to discuss before we conclude today. Otherwise I'm inclined to yield back the time. All right, excellent. Thank you all for coming and we'll see you next week.