 Alright, thanks Arpit. Thanks guys for having me. Let me pull out my slides here. Assuming you can see my screen. Yeah, so I've been working as Arpit said in LF Edge for quite a while. I've been actually doing first IoT then Edge computing for the past eight years, starting from the big IoT buzz that happened in 2014. So, undisclosed location 2014. Dr. Ebel is predicting 50 billion devices out there and it didn't quite pan out that way over time. A lot of it's been happening kind of behind the scenes, but what's been challenging is kind of getting past some of the like systemic issues behind IoT. I like to say that we're kind of just now getting out of the AOL stage of IoT. So, if you guys know of AOL like back in the late 90s, you'd get the little CD in the mail and you'd be able to install it and start getting connected online and whatnot. Very locked ecosystem, literally using their keywords to search for things. And then all of a sudden people realize, huh, I can just get on the internet and then AOL comes along and things change. IoT has been very much a progression. It started going vertical before horizontal. It really is about use cases, but a lot of folks were kind of making it about platforms up front. And the top challenges with IoT and also Edge, which we'll talk about here in a minute, they have nothing to do with technology. It's people, you know, stakeholder complexity. That's not my job. That scares me. I don't have the skills, et cetera. And use case. And, you know, so many opportunities, you know, over the past number of years have been kind of stalled by that. And we're going to, we'll see the same with Edge, but it's not to say there is an opportunity, but it's just it's really important to focus on these aspects of these solutions as you go. So, what we've seen is also as a big trend with IoT is people start with what I call cheap edge, easy cloud. I'm starting with a very, very lightweight device, you know, at the Edge. And then I'm going to run with, with, you know, a public cloud offer or maybe some other platform experimenting, developing new types of use cases. And, you know, it's great to go straight to the cloud up front. And that's where we saw a lot of the initial acceleration with IoT. But then you get the bill if you're just mindlessly pumping data there. And that easy button inherently comes with some level of lock-in. And so this is the big trade-off that people have been trying to make within the market is, you know, how do I find the right use case? How do I enable a solution in an easy fashion, but also increasingly, how do I prevent being locked in? The same thing we've seen in kind of general IoT market, we've also been in with the clouds we've been seeing in the industrial space for a long time. You know, why do we have, you know, projects within, you know, LF edge, you know, HX Foundry and Fledge and, you know, we've got a bunch of other, you know, efforts out there. Why do we have the need to consolidate all these protocols into more, you know, consistent communication protocols? Well, we have thousands of communication protocols because everyone created proprietary ones to try to lock you into their ecosystem. You know, all the industrial players, you know, everybody over time, though, what's happening is all of that lower-level functionality is being democratized so that we can get into new business models, and it's really about that at the end, just like how the internet democratized, you know, connectivity for the average person and created this huge economic benefit. And so I use this analogy, so if you know about, like, so, Riptide Current, human nature is to swim upstream, trying to get back straight into the to the shore, and that's when people get tired and they might drown. The right thing to do in a Riptide Current is to swim sideways. And so I like to say, you know, what we're doing with the open-source community is we're helping swim sideways to get out of this mindset that I must kind of lock people in. I need to go after and kind of lock people, you know, customers into my solution. It really is about building an open ecosystem across, you know, the landscape because, you know, starting with IoT and now EDGE, it is really, really complex. There is no single EDGE. There's never going to be one cloud, you know, lots and lots of different devices out there. The closer you get to the physical world, the more complex, you know, everything gets. And so this is where open-source becomes so important, you know, as we continue to see the market evolve from like lock-in to more kind of composable open infrastructure that then you apply the special sauce to. You know, so EDGE continuum, this is from the LFEDGE Taxonomy White Paper that we put out as a community a couple years ago, and we're doing a refresh now, you know, it goes from constrained devices on the far left up to regional data centers on the far right. And there are inherent trade-offs as you go across the spectrum. And the paper goes through that in great detail. When you look at EDGE, you know, and even the relationship to IoT and, of course, AI and 5G and digital twin and, you know, all the different trends, we're seeing a trajectory where we've got kind of the operations world OT or kind of IoT lightweight use cases moving right from kind of the physical world. And we've got sort of the IT principles or cloud principles moving left along this continuum and sort of converging in the middle. OT, IoT up tends to be more kind of lightweight device management, but then maybe I'm evolving into more kind of IT principles and composable applications, software-defined infrastructure, things like that. IT or cloud down, the telcos, you know, very important here as we come down, this is like, how do I extend principles from the data center as far left as I can? I want to extend the public cloud experience as far left as I can where I just think about distributed EDGE resources or compute as just resources until it just breaks and I have to go embed it. This is that kind of trajectory we're seeing, you know, on both end. You've, Gartner refers to it as, you know, cloud in and edge out, but it's the same difference as these two different trajectories coming at it. A lot of people are still kind of learning how to spell EDGE, same thing with IoT, but also we're seeing more and more really valuable use cases pop up. Computer vision is a killer app for edge computing. Raw video data is expensive to send across networks, but a lot of the infrastructure that we're building within the open source community, it really is about how do I go scale it? How do I, you know, be the most effective on the, above that core infrastructure in terms of differentiation? That's where the money is long-term. It's new services, it's new experience, it's not the plumbing, this of course is why open source is so important. Got to have the use case, then people care about kind of those top-line apps and maybe specialize hardware, but then they need that underlying engine and that's so much of it, whether it's the application frameworks we're building in the community or the underlying management and security elements across the different projects. You know, it's those enabling elements that are going to really help people scale. Won't go through all the nuances here, but we're detailing this out on the new white paper. It's another click in from that taxonomy for EDGE. There's kind of four unique paradigms across the spectrum in terms of embedded devices, inherently custom per device given resource constraints and user devices are well-established ecosystems around Apple and Android and Microsoft. Data center we're seeing evolve as it kind of comes left and then there's sort of this in-between distributed EDGE as we see it and that's that convergence point between these paradigms. The open horizon is doing great work with you're kind of leading between distributed EDGE and client devices. Sam even talked a little bit about that. The KISS rule in this case says keep it separate. Infrastructure plane and application plane is super important to keep separate historically with all the different platforms, IOT, hundreds of platforms. Everyone blended everything together and I do everything. What we're doing within the open source community is we're providing tools that allow you to enable both planes to be modular and separate and then you pick and choose the best mix as you go and then you figure out where you want to differentiate on either side of the equation but it's really important to not lock everything together because the odds that you'll have one cloud, one use case, one set of devices, one set of apps going forward as a business are pretty much zero and so you want very very flexible infrastructure that can run any application. We have the projects within LF EDGE and of course we're collaborating with the network and community and CNCF but they're laid out across that infrastructure and application plane. We're working towards how do we harmonize more and build out that ability for developers to leverage components, focus on value. In this market I think you win by merit not lock in going forward and it's about the pace of innovation and we're just helping with that. Know the cloud is not going to get eaten by the edges, people like to say. It's really about this sort of symbiotic relationship between the two. As I mentioned the goal is really how do I extend that cloud experience out to the field, enable rapid development, cloud native development, how do I also still enable legacy support for software. Where you run a workload across the edge to cloud continuum just is going to depend on the balance of security, performance and cost and the best we can do as a community is to enable the plumbing that enables that balance in an open way. Advanced class, you know longer term and you know Alvarium is a project I've been working on where we just got that into Linux Foundation it's complementary to all the other projects. It's about how do I interconnect ecosystems you know across the supply chain or retail crossover into the home or healthcare, you know insurance. All of these different ecosystems starting to build new types of business models and experiences for end users and this notion of trust fabric and how do I bake trust into data. This will never happen. This long-term potential will never happen without open infrastructure. Just like the internet all the economic gain over the years will never happen without open infrastructure and that's where the plumbing we're building today is going to lead us to the future. You know as a business you should focus on some clear use cases just go you know develop something that makes business impact of course today for you but think about how you build today to get to that future of entirely new businesses based on interconnecting all these different ecosystems. So basically you know hey we're getting out of the AOL stage of IoT you know we're seeing convergence from both directions you know it's really about the edge is the last cloud to build how do I get the easy button you know everywhere I just think of resources wherever they are data center out in the field doesn't matter as much as I can and you know and then but we'll also recognize them through different trade-offs you know whether you're latency critical latency sensitive are you in a secure data center are you not these are why we have different tool sets that are similar in principle but necessarily different and eventually this notion of trust fabrics will turn security into a profit center where I can actually make new money based on this this infrastructure so that's my time you know I think I have a couple minutes for for questions but I see a couple I don't know Arpen if you yeah yeah no thank thank you Jason if you can stop sharing then you probably be on the screen there you go okay very good so again as as I said if you have questions for Jason feel free to ask them in the Q&A box on the right I'll get started with with with one question I think your your title of the talk was was quite challenging right that's like it's the hey software it's the world is edge eating the cloud and cloud eating the edge and I think you've set it up correctly because you know right after this we'll have folks from google cloud talking about you know how yeah yeah yeah that's that's cool um no so so one fundamental question is you know we we had confusion on terminology you know because people were using thin edge thick edge far edge near edge cloud edge this edge that edge and I think that terminology was all relative to where you are and your place in the network and I think that has been taken away with the LF edge terminology white paper that kind of you help in the community so so with the terminology now straightforward or at least standardized in terms of you know terms that are unique do you ever see either the access mechanisms or the protocols like the messaging protocols or I mean we can always say that the shape and the form factor of IoT devices are always going to be custom for each vertical right I mean that's a given because of you know healthcare or or automotive or whatever right regulations and and environment but what do you see the future of sort of access mechanisms and the messaging at least a couple of layers down and and if they are going to be separate you know don't you think the relevance of frameworks becomes even more important yeah it's incredibly important I mean the old standards joke is we're going to fix the standards problem with one new standard you know the odds the odds that there's going to be one protocol or even a small set of protocols for communications is one example anytime soon or zero and this is why you know we've been building these interoperability frameworks as I think we're all here because we know that open source is a modern way to drive standards and it really is about frameworks it's about interoperability through APIs and modularity of course also enabling lots and lots of differentiation around the wheel it's you know the whole point with open source is you avoid undifferentiated heavy lifting but you know I also say you have to democratize the south IE connectivity to monetize the north that's where the money is it's in applications it's in services it's all that kind of stuff it's not the plumbing okay but yeah I think the framework approach is extremely important not only for developing things but also how do I make sure I don't get locked into one solution stack got it got it now that's excellent there's a question here which says can you elaborate on on the edge hardware in IoT will that be standardized right and and is there any specific you know standards or organization that we should be looking at well I mean of course we've got open infrastructure foundation and there's other you know elements and there's like really great work happening overall but if you look at the if you look at the continuum from regional data centers to a smart libel or a thermostat or a sensor the hardware inherently gets more and more complex and fragmented you you know like exponentially as you go left I mean every connected device is a different form factor it's customary toasters a little different than a light bulb it's very it's generally consistent as you go through data centers you're going to start seeing some evolution when you get into the telco space in terms of specific telco certifications maybe I need short depth whatever but then once you get into the physical world it gets more and more complex and so I don't believe that hardware depending on where you're at in the data center edges yeah we'll see standardization we already kind of do in the far like kind of the more the IoT physical world we won't see as much standardization on the hardware because of inherent physical characteristics that are required but because of the software capabilities you know Raspberry Pi with 8 gigs of memory like we're getting more and more capable hardware the software frameworks can get can get standardized all the way down to the point where you just can't run Linux anymore and have to go embed it so while the hardware complexity goes like exponentially up this way the software complexity is pretty flat and it goes up and then it goes up when you go to that's the opportunity for us that's when I say extend public cloud experience you down to continuum until you just can't anymore that's based on the resource of the box and those resources they're getting more and more capable we can run cloud native on a raspberry pi that's that's that's the the opportunities to standardize the software frameworks even though the hardware is going to be unique I know we're kind of a time but okay but that's absolutely the perfect segue into our next presentation so thank you for setting it up Jason all right I'm your ethnic man today thank you see y'all later thanks for having me okay all right