So for this [INAUDIBLE] network transformation, let's look into how this standard development organizations are contributing to that, and then also number of open source technologies in different open source projects, complimentary to that. For this, I will use Visual, coming from Linux Foundation, being one of the major umbrella organizations for a number of those open source projects, and one of the white papers that nicely visualized how this traditional methodology look like for standards development, where a lot of vendors and leading communications service providers will go and define the standards, implement in some products, get to detailed requirements, get to the architectures out of that, and then feed it into the furthest standard. So this is how the typical standards of organization look is going on. And this is based on the design principles of this vertical. And sometimes it can really take quite long cycles to get some new, innovative revenue making services. So what you are looking for here is how to complement this thing with the open source principle, where this is heavily based on the contributions of the [INAUDIBLE] and the architectures and designs. So here we have, on the right side of it, is suction and roll methodology, with contributions into the open source components. They are being built into the reference platforms out of that architecture. So the finds and use cases are being implemented. From that, we see what are the next component is required. And this is how this loop is going on. So the ideal situation for standards developments in open source is, standard developments are defining some of these requirements, and open-source are really contribution based, implementing that fast. So here, it's another diagram, representing how the different layers in different projects fit together. It's a point of view from the foundation. But it's very visual and representative. So I'll use it here. And layers are coming in the infrastructure management, control, and the services. So starting from the bottom, there is this segregated model of hard-wired number of projects, like open compute projects, and telecom infrastructure projects. So defining that. Then we have, for I/O obstruction and data pods, projects like data plan development kits is packet processing library, in software used for running networking workloads on commons servers. And there we have, for example, if the I/O is another one of related projects, OVS is, Open Virtual Speech is one of those, virtual speeches being used. So operating systems, open one is, obviously, open source is Linux. And then we have a few for the networking. And then we have network control, very popular ones. For example, [INAUDIBLE] fabric, which was called Open Contrail until recently. It's the limitation of Contrail. And then we have Open Daylight and Onos there. So cloud and virtualization management, the major one is OpenStack. And for orchestration, we have projects like [? own ?] [? up ?] and Open Source Mono. For the network data analytics, it's Panda, inside Linux foundation. And then we have, on top, we have this education layer. So there is also, for continuous integration and delivery, there is this OPNFV, focusing on various aspects of this integration and Automation And then we have, from Cloud Native World, we have Cloud Native Computing Foundation. So they are also focusing on a number of those layers in normally containerized, decomposed cloud [INAUDIBLE]. So this is an overview. a number of vendors and comm service providers will have heavier investment in some of them, lighter in the other ones. But its also good picture to also think about, which of these are mature enough, at a given point in time, to be used as either fundamentals of the platform, or somewhere higher in the layers. And also, it's good to think about, where from do we derive more value, if we invest in mustering one or the other one of those open source projects in the implementation from the vendors, and which one would be the wrong one to pick for such an investment?
