 Good afternoon, especially the ones who have managed to sort of take the challenge of staying online for four hours versus mingling with us here. So first of all, thank you all for joining. It is, I know there's over 5,600 registered online, so I know travel is still an issue. But for those of you here, we have a stellar cast of speakers. If there's any questions on the web, obviously you can't ask, but feel free to email us. All of us, our emails are on the web, and I think Pano can work that through the registration. But just to get started, for those of you who are not familiar with LF Networking, I'm Arpit Jasper, I head up Open Source Networking and Edge at the Linux Foundation. And what I was going to do is give you an overview of what the next big things are in the world of open source networking. And before we get started, for those of you who are new to Linux Foundation, I'm sure there is a lot more. Some of you might already know this, but we are beyond Linux. We have sub foundations that solve problems within either a technology area or a market. So in the world of security, like open SSF or networking or cloud or automotive, webs, energy, etc. And we have sub foundations with projects that we host to create this open source community. And it has been very active and very well received over the last 20 years of existence. So with that said, this mini-summit or webinar or whatever you want to call it, is part of the open source summit here in lovely Vancouver. Thanks to Telus for keeping the weather good. So I appreciate that. What I was going to cover is LF Networking, which is one of the top three sub foundations, largest sub foundations inside the Linux Foundation. And what its mission is, what we are trying to do there, and in general, what we are seeing globally from the trend's perspective. So the number one feedback and the number one trend that we see is re-aggregation is following disaggregation. So everybody who is in networking will know what SDN is, right? Disaggregating hardware from software, disaggregating control plane from data plane. And then we kept on disaggregating all the way up the stack, out to the edge and access. Now the RAN is going through the same disaggregation. Well, guess what? Someone's got to put it all together. So you sprinkle it open, you put it all together, it's now back to re-aggregation. So what does that mean? That means that if you need to build an end-to-end solution across the telecom service providers, cloud service providers, or enterprises, here's a potential way to do it, right, with a subset of projects that I'm showing here on the screen. Everything from ORAN to edge compute projects all the way into enterprise, into enterprise edge, so user edge and service provider edge through some version of cloud up the stack through a NAS, whether it's Sonic or Dent, into a data plane, DPDK, FDIO, these are again projects. Kubernetes, up through the stack, control plane, you know, open daylight, tungsten fabric, Nefio, Onap, and then all the way up through the applications, whether it's CNFs or EBPF lifecycle management projects like LEAF, which runs most of Walmart's EBPF lifecycle management programs at scale. And then there's projects, every project in the middle. The key message here is these projects, they all work in their own TSC and they work together in what is called a solution. So it's not just projects get developed on their own with software and testing, and then we bring it together in something called 5G Super Blueprints. The other thing I want to emphasize on LEAF networking is five years ago, there was a fight between standards and open source, maybe seven years ago, I don't know. Is standards the right way to do it or is it open source the right way, right, and it was a competing alternative. We have solved that. I'm pleased to report we have solved it completely with LEAF's leadership where we have collaborations with pretty much all the standards organization, very specific MOUs, and the philosophy is very simple. If a standard exists, code it, if it doesn't exist, code it and then upstream it to the standards and people are doing it. And everything from GSMA to Etsy to 3GPP, ORAN and GM and TMF, like every standard organization is working with the LEAF community and LFN particularly to do that. Not only that, we have other open source communities like CNCF, Magma, Edge, ORAN, that have come together to provide solutions and interoperability through working groups and things like that. And then when we move from the core to the edge of the network, there are alliances and consortiums, consortiums that focus on specific industries like automotive or digital twin and things like that. So they work closely also with the open source community. So the good news collaboration has increased. If you see that this is a 100 year old industry, telecommunications, and it was heavily regulated, heavily proprietary, heavy standard based, and we have come a long way in the last five years, I should say. And a lot of other industries are learning from us like the energy industry. So formal collaborations, standard bodies, consistent APIs, models, things like that. And there's a whole list of the Etsy salts that have been coded, or the TMF APIs that have been coded, et cetera. So with that said, what is the re-aggregation looking like? The re-aggregation is looking not just at the org and the open source level, but it also at the solutions level. So if you think of this kind of very simple diagram, where you have the horizontal interoperability of platform, which is what we are calling 5G Super Blueprint, and the five use cases are very simple, right, like on top. Ultra load latency, enhanced mobile broadband, voice network, slicing, private networks, industry format. These level of use cases, macro, they run on that black platform interrupt pipe, like this color here. And then on top, you can have vendor workloads, et cetera, et cetera, and consumed by the various industries. So one of the focus areas for LFN this year is not just the blueprints in the middle blue, but also focus on network as a service, right, as the team is trying to figure out what it means. There's a white paper that came out. There was a demo showed at Open Networking and Ed Summit, et cetera, et cetera. So 5G Super Blueprint, if you're not already participating, it's an open way to bring things together, right? Very important. And I think we'll have a talk at the end of the session on that as well. Now, who uses LFN Super Blueprint? Well, here's one example. I'm not giving you examples of the telcos that are dependent on it, but this is US government. DARPA is a project. They started a project called Ops 5G. Ops stands for Open Programmable and Secure 5G. The US government, through their research, has already shown that open source is the only way to build secure software. So everybody says, why is open source more secure? Oh, more eyes look at it and all that, fine, right, by that. But how do you theoretically prove it? Well, they've proven it. So what that means is every future deployment in Navy or in Army or anywhere in the warfare or civilian, right, is all going to be based on open source. And what open source? LFN. So here's an example that this slide was presented at the, I think, keynote by Tejas at the One Summit. He's the head of DARPA. And here's an example. They want to utilize all these projects. And on top of that, they will put their secret sauce. That is for these use cases. Now, the one thing I want to emphasize, and this is actually a very good learning for people who are new to open source. You can't just consume open source. I mean, you can, but that's not what people like. So you have to contribute back because that is how open source works. Now, how do you contribute back? You either make the changes and put it back in upstream or you participate in these TSCs and in these forums and for documentation or anything. So one example is USC, which is one of US government's research arm at the University of Southern California. Dr. Eric Klein has done research on how do you make the slices in network secure. Extremely amazing algorithms, right? Because they want to make sure that a slice on a 5G network cannot be hacked, period. So they did all this research and then they realized that everybody can benefit on that. So they actually upstreamed that work into OWNAP. So now the whole community benefits. This is an example of contributing back, pushing things in upstream, and everybody benefiting. And of course, there's more. So that's trend number one. Reaggregation of open source components. The second trend is, and I use this word, open sourceification of vertical industry. What that means is, if you have a set of projects, and doesn't matter where they are, core, edge, access, like at the bottom, right? Okay, by the way, they don't have to be LFN projects. They don't have to be LF projects. It's just open source projects, right? They could be Apache, they could be Open Infra, they could be Eclipse, doesn't matter. But let's say these projects bring together some version of an open source pipe. How do you consume it? You consume it through either you are an enterprise or you are a service provider, and I'm calling service providers as both cloud and telecom, or you are an end user like a government, right? Very custom specific. So what we do is, we focus on these use cases that are important to each of these markets. And then, each industry on the top is getting utility and utilizing some of these blueprints for their use case. And by the way, on the top, industrial energy, commerce, retail, that's a linear order of industry on how they are consuming open source. So manufacturing, for example, is the hottest market for open source right now, for edge computing. You know what the use case is? Predictive maintenance, that's it, right? And private lines, or sorry, private networks, which is the LFN use case, right? Energy, et cetera, et cetera. So again, keep in mind these vertical markets are going after, are dependent on a lot of the work that is being done in open source. There used to be time when they would just tell us or a bell or a, or anyone and say, hey, I need an MPLS line. And then that's it, right? And they would be paid on the pipe and then that's it. But these days, the service providers partnering with the cloud service providers, so telecom plus cloud, working very, very closely with these industries so that they can add value added work and charge for them, yeah? And why is this happening? Because digital transformation, which is in the enterprise, which is again, I know it's hard to read, but on the top is like assets, usage and labor, right? So this is attributes of digital transformation and on the y-axis is really the industries, okay? ICT, media, finance, et cetera, oil and gas, et cetera. So you can see that industries which have a lot more digital assets and that are relying a lot more on open source can do digital transformation faster than the others that don't. And in fact, for the very first time, we are starting to see agriculture, which is at the very bottom, coming up the pipe, right? So this slide will look different next time. Okay, so that's number two, right? Which is vertical industries are important. Number three, security is a top priority. Now everybody will say that, but how do you do open source security in a very structured manner, right? And is CVEs just enough? And the answer is no, right? So what we have is we have some research studies done by Harvard and some of the other foundations, including our own research organization and OpenSSF, where everybody uses open source in some form, but only half of them use S-bombs. So S-bombs is software buildup materials, right? So it's knowing where packages come from, okay? And so basically the findings from all these research, right? Everybody tries to do research. I love it, but then I just like to take what the research says and then push it into the community so that we can actually do something about it, right? Because otherwise it just becomes a marketing tool. So what has happened is research is saying, it's not just the CVEs, it's the entire life cycle, it's packaging, it's integration, and the top projects within each community better understand how to do security properly, okay? So what does that mean? That means that you have to do six things, okay? You have to secure, and this is at the LF level, but we have taken it down to the LF networking level and we have said you have to secure the most important critical components, right? A GUI getting hacked with a very solid API that can't be penetrated is not as much of a risk as, you know, a BGP going down and the network getting taken out, right? So difference, so the secure, most critical components are important. Automated tooling is important. You have to train people to get to that level and then of course S-bombs. So how do we do that in LFN, right? So if you go today to the... So first of all, there's... If you can't measure, you don't know how secure you are. So there's a tool called LFX Security. LFX is our platform, open source platform. That's the... LFX is the only tool that is available only to LF projects, right? No other open source foundations have it, but it is a tool to give you insights into the developer community. Same way, it's a tool to give you insights into the security. So you can go to each of these projects, look at the dashboard and how secure they are and where they are in the life cycle. So OpenSSF says, in order to be secure, here's a checklist of 150 things you need to do. And then each of these projects will go in and say, yes, I do this, I don't do this, I do this, here's a plan to do this, right? It's a lot of process work you need to clean up so that you eventually get to 100%. I think this one's showing Open Daylight, for example, one of the projects at 90%, right? So we're almost there, et cetera. So take a look at the dashboard, participate. If you're a security-focused individual, please participate in the security subcommittees and things like that. But security is taken very seriously. Now, if you look at the Linux Foundation, we have the OpenSSF Foundation, SubFoundation, which gives you the framework of security. All the other sub-foundations have to implement those frameworks and LF Networking is leading the way. And the reason LF Networking is leading the way is if there is no connectivity, nothing else matters. And that's what we focus on. So that's kind of why the community takes this very seriously. So that's number three, security. The next one is the merging of the markets, okay? Enterprise Cloud and Telecom are no longer working in isolation. I mean, we have, tell us here, they're heavily working with the Googles of the world, for example, right, or AWS or Microsoft. And these goals are working with the Deutsche Telecom. Telcos and telecoms are no longer competing. They're competing on a different set of things, but they're collaborating heavily on open source and they're collaborating heavily on the new use cases, right? And so this is what gets you the NAS, right? This is what gets you, Network as a Service, right? This is what gets you all these news things that cut across the core and the edge of the network. And I think it's very important that this collaboration happens. Now, the advantage of, okay, so now if you take a quick detour on why the collaboration accelerated, apart from the business reasons, which we are not here to discuss, there's a technology reasons. The technology reason is, Telcos were built very proprietary in the past. With open source, you can modularize it. And then they were built on open stack with VMs, okay? And now, and then the clouds got built on, the new clouds were built on containers and Kubernetes. With Telcos then moving to cloud native and cloud native network function specifically, now there's a common horizontal layer of Kubernetes that runs across these layers, right? So it is very easy to get, and this is just a very simple explanation. I'm sure there's a lot of details behind this, but there's a very, that's one of the reasons why these markets come together. Then there are Kubernetes based edge deployments that can also push containers all the way down and package them correctly. So there's a lot of synergies between our sister foundation CNCF, which hosts Kubernetes and LFN, which kind of holds the networking subsystems, okay? All right. And then finally, the networking community and the board is also focusing on some of the new technologies, and there's about two for now. There's the metaverse, which mostly is about just our piece of the puzzle, which is the intersection of infrastructure and intersection. We're not focusing on the cool stuff for metaverse, if it is at all cool these days, but independent of that, we just want to make sure that the things on the right intent base, AI base, security privacy, all that stuff is taken care of in our infrastructure work, okay? And then the other one is 6G very early, but the community starts looking at it probably over the next three years, okay? So high level then from a trend perspective, right? 2022 was the tipping point. We have seen more deployments of open source last year. I'm not going to present all the use cases. You can go to the LF networking website. There are case studies from Verizon and Bell and sort of Deutsche Telecom and Arange, and everybody is like who has deployed. And then open source is the basis of these verticals, right? And so collaboration has increased tremendously on that, okay? So two, three slides on networking, and then I'll hand it over to Telus to talk about more details. LF networking, we host some of the largest projects. It was formed by the industry collaboration seven years, six years ago, right? China Mobile, AT&T came together with Orange and DT and Bell and others. Verizon, Telus joined last year. So it's the combination of the largest of the large who actually want to change where the market's heading, okay? And output of that is almost a commercial ready ecosystem, right? It's not going to be, you can't just deploy open source, right? But you can get it to enough of an integration where vendors can take it through the last mile, okay? So it is across data plane, control plane, analytics, orchestration, the full set across all three domains, right? And we are the house, as I said, top three foundations inside LFN. And where it's evolving is it's kind of housing projects and integration for multiple other umbrellas as well. Some stats, I think these were pulled probably three months ago, so these must have changed. But it's not trivial to do this in a single vendor system. 182,000 lines of code added weekly. It's a lot of code, okay? I like the deleting part also because, you know, if you add and if you don't delete, then it's a mess. So this is good. Almost 250 companies contributing, you know, the one that bothers me is the 2.1 million email messages, but that's okay. We still use email. And then, of course, multiple projects and domains and things like that, container downloads. Anyway, these stats are available on LFX and sites and things like that. But very active community, good growth. So you can see this in commits. You can see this in code contributors. These are all the elephant projects, right? That have been put. And then I want to sort of talk about one new project that's a year old, which is very interesting and that's called Nephio, which was seeded by Google and it's kind of sitting on top of Kubernetes, right? And then on top is own app, right? And it is doing like CRDs and things like that right on top of CNFs, okay? So what is happening is the community is coming out with a release, first release this month, I think. And it is looking very interesting in terms of simplifying the solutions for an all Kubernetes-based solution, right? Remember, five years ago, or 10 years ago, it was all proprietary. Five years ago, it was all open stack, VM-based. Now it's all Kubernetes, CNFs. There will always be hybrid, but you don't want to pollute the hybrid and the new stuff with the hybrid. So if there are projects and other things that can take care of the VNFs, then you put that and then you take the new one and then over time phase it out, right? That's kind of the model most people use, okay? So on the board, you've got pretty much all the top carriers. AT&T was the chair. A few years then China Mobile was the chair. I believe we have Deutsche Telecom as the chair this time. All the vendors are on the board. Telus is on the board. Ibrahim sits on the board. Verizon, et cetera, et cetera. And then you have a whole bunch of silver members. So that's it. And then all the associate members. So I'm going to wrap up here and say, do you get involved? For those of you who are not participating in LFN. Panna, what is the email? Since there are 2.1 million emails, we can add one more. Is it info at Networking? Okay, so info at LFnetworking.org. Or a joshupariatlenexfoundation.org. Get me an email. But get involved. Get involved is. And this is for the people on the 5, 600 people that registered and didn't want to travel to lovely Vancouver here. And so that's kind of my slide deck. We can take questions from here. We can take questions from the web, correct? Okay. See, that's the penalty for being online. All right. Questions? Yes. Good. Good. Okay. So I'm going to repeat the question because folks won't hear. So what is the vision of bringing everything together? Because there is a lot of projects. So historically, projects can get incubated anywhere in LF, right? That's the fastest path out because every sub foundation has an induction cycle, right? You know, if you do these things, then you are an incubation project. If you do this thing, you're graduated. If you do these things, then, you know, blah, blah, blah. So when a community wants to get started, they just typically put projects directly under the LF instead of moving it under a foundation unless they know that they're incubating within a project itself. Okay. So that's what has happened, right? Where projects have been incubated in under the LF directly. After the first release, typically, the project TSE and the governance, whatever the governance is, looks at finding a proper home based on the interoperability, based on the community. Most important thing is where is the community? If the community is here, then they would probably work to get here. If the community is somewhere else, then they'll go there, right? Because you can park anywhere. If there's no community, it doesn't matter. So what we do is that whole process of kind of aligning. LF works on that after about a year, with all the stakeholders, right? So projects like Nephew or Oran software community or Kamara or Silva or, you know, the ones that are relevant to LF networking, they will work with their governance and their setup and then see what the best options are, right? So that they can move or they can be inducted and all that, right? That's the general process. But keep in mind, the projects still operate autonomously, right? Because TSCs cannot be influenced by the governing board, right? By design, that's how it is set up. Questions or the questions? I mean, you are all LFN, so it's not, like, something that you don't know. So sorry for the reputation if you have not heard, if you have heard me speak about this, but it's always something new comes out. All right, that's it. Okay, thanks. Sana and you next.