So, I guess we can start. Thanks for being here. So, I'm François Le Marchand. I'm responsible for SDN product management in Ericsson. And I will present today with Alain Cavana, that is responsible for most of the open SAC architecture and cloud architecture in Ericsson. So in that presentation, the ambition is to cover a bit this virtual enterprise gate to architecture and what we mean by that because there is, of course, many different, proposal, blueprints, product sketch of what it could be. But this is really like Ericsson vision on how we are building it and how we think it should be built. And a bit open the discussion on what are the things in Open SAC that we have to focus on, what is the impact on Open SAC architecture. And Alain is going to open a bit more on that front on the technical side. So first, we thought it would be good maybe to start with some of the basics. So sorry, I know some of you in the room will be very bored. But I think it's very mixed audience with a lot of people from enterprise and so on. So I just wanted to touch base on our definition of SDN, our definition of FNV because we are going to use that across the rest of the slides. So SDN, I spare you this whole architectural slide. But basically what it is is splitting control plane from forwarding plane, or that was at the core initially of it, which means, for instance, you have an SDN controller that will run a control plane for a network. And then the nodes will simply be forwarding element that are like substantive to that SDN controller. So this whole system will act as one logical box, right? One logical box. Then of course, SDN is much more than that, right? I mean, when the definition knows being extended, including like a lot of overlap with NFV, I'm going to touch on that. And then of course, the value of SDN is much more than simply splitting the control plane that's also about API extension and flexibility you can bring on the network. So there is much more to SDN, but really at the core it is that. And if we look at the early, let's say, use case for SDN, including data center, that was really that, right? That was basically controller using OpenFlow to drive like an Ethernet switch. That has been one of the first and core usage of SDN. So what's the relationship with cloud and OpenStack? Well, again, the first application that has been subtend, let the SDN controller drive the underlay, the infrastructure, the network infrastructure of the data center or the Ethernet switch. And basically, the role of SDN, why it's software defined, what value does it bring, is that you get a network that can be reprogrammed very dynamically. And then again, using API, like a neutron API northbound of the SDN controller could be a way to do that. Then this allows the cloud, when you create dynamically virtual network, virtual machines, and so on, to basically drive the reconfiguration, the dynamic reconfiguration of the network under NECET, right? So it's basically SDN driving like physical box to implement dynamic networking on behalf of the cloud demands, right? And then those little like floppy disks, I get a lot of bad price. They usually upgrade to USB at least. But they are supposed to be software image, so they are supposed to be VMs, right? That's the meaning of that icon. So then those VM pops up, and then we automate the connectivity. Then what about NFV then? Well, I think things start to get a bit more complex when we intersect cloud and SDN, right? When we intersect the actual network functions with the actual virtualization together. And at this intersection, I think there is basically two menus' case. And I draw this dotted line to say, first, you may have, let's say, network functions. So virtualize network function. And if you take a physical switch and you virtualize it. But part of the infrastructure, that's your v-switch, right? That's your v-switch when you build an overlay. And that can be controlled like this, controlled by the asian controller, similar to the underlay, right? So you have both of either or model. Or actually, many operators now are going for both model at the same time, right? They can be quite complementary. But that's not really the definition of NFV, right? Because NFV being introduced by carrier, by operators, being defined at Etsy, the goal was not simply to make the infrastructure of data center more flexible. That was really about looking at the existing IP domain and the operator, so meaning all those waters and firewall and BRAS and gateways and box that are running the physical operator network today. And basically, look at a way of virtualizing. And meaning virtualizing, it's basically running on XLE6. I think that's the main intent. Running on general purpose hardware, running on dynamically orchestrated networks so that those resources, they can share a pool of hardware, compute resources. They can be spun out and spun down dynamically. And they will also run on a more generic hardware to reduce cost. And actually, it's more of increased flexibility than cost reduction. So what does it mean? It means, in that case, that's also a virtualization of a network function. But it's not really as part of the infrastructure of the data center, that's part of a hosted application. Then your NFV is more like a hosted application that happened to be itself a network application. So looking at all the functions within Ericsson and the different, let's say, use case for SDN, you can look at the middle that's basically the data center, this SDN controller for the data center that we call the cloud network controller. That's our SDN controller. Then the data center infrastructure and in between a portfolio of NFV services. And I kind of color coded those services because there is two main domains in our view. There is services that are more like network centric, per se, that are focusing on getting connectivity to the end subscribers. So they could be virtual waters, like Enterprise P, providing VPN services and so on. They can be more like gateways, meaning that they have an ocean of subscriber termination, whether it's mobile gateway or whether it's a fixed line gateway or BRAS. And then we have also more like IP services. So all those typically bump in the wire services that you can insert into the path of the traffic in order to create new services or like security or like an N-square or video optimization, I mean, all those do this class of services. And the reason I color coded is that the role of SDN, it could be on one side, could be that SDN will drive or configure those NFV dynamically because then those NFV, they are not part of the data center infrastructure, but they are part of the operator infrastructure. So it's kind of a layered approach in that model. So of course, there is a case where SDN controller role is actually to talk to the NFV layer. But I think on that presentation, we really focus on SDN controller as part of configuring the infrastructure in a data center in order to connect efficiently those NFV features. So it's basically SDN as driver of the infrastructure to provide services to the NFV functions. So concretely, what does it mean?  And that's fairly basic in the typical data center design. But you also need to collect traffic from your access, from your one, from your metro network, and so on. And so the first need of an intelligent SDN controller in the data center is to be able to inter-work in a seamless way, in an efficient way, with the existing one with the existing aggregation and core network equipment of the operators, which means that that SDN controller needs to talk, for instance, IP and PLS, natively. So that's one of the use case where it's not only basic connectivity inside the data center. That's across the data center. But that's also interworking with the existing IP1 domain. I think the second use case, and this is where it was a bit color-coded, the first use case is pretty much pertain on getting traffic in and out and connected to those NFVs, including like very, very simple function that you do today on the router, which is like load balancing, availability, and redundancy, and so on. The second part is more like, OK, what about the services? What's special about this other NFV that are firewalls, and so on, that are service-oriented? I think what's special is that you could, at the very basic way, build service chaining about like bolting different instances of VM using like VLAN or virtual network together. That's the most basic approach. But there is actually, given the nature of those services, a lot more you can do. And a lot more you can do that's being able to identify, for instance, specific subscriber class. So it comes back to policy management, right? And it could be policy management as for enterprise policy management, defining different group of operators or sorry, of users in the virtual enterprise networks. Or that could be policy management, in a sense, or broadband access policy management. What is the class of the user? What are their quotas? What services are eligible to? And based on that policy management, then, for instance, the SDN controller can build a chain in a more, let's say, granular way, or in a more dynamic way that you will do with a simple, let's say, VLAN cross-connect. So SDN is also, if you look outside of the data center, right, that's really like the vision inside data center. But outside of the data center, there is other use case for SDN controller. The same way that an SDN controller can drive the physical data center infrastructure, like Ethernet switches, for instance, using OpenFlow. Then this SDN controller can also be applied to basically change the way the operator are building the actual aggregation network. By saying then, we will do the same thing, centralize the control plane, use simplified forwarding, hardware forwarding elements in the aggregation, and basically drive this whole aggregation from this more central computing point of view. So that's one model where it's more, we call it transport, but we mean transport in a sense of next-gen transport, which mean IP plus optical, which mean packet, which is IP today, IP MPLS, and then optical. Not necessarily transport in a sense of more legacy, TDM, SDH, and so on, of course. But that transport controller could be seen in that model, which is, let's say, the more extreme SDN case where you really centralize all the control plane intelligence. But there is also many use cases for transport where there is not necessarily a strong drive or benefit to basically try to remove the intelligence of the existing box. It may not be at visible in certain circumstances, like in the core network and so on. But in that case, what the SDN controller can do, by being more like network level, he has a more holistic view of the network requirement. Having APIs, it can be connected in a more tight way to the, for instance, the orchestration layer.  So he has much more intelligence about the traffic that is carried in the network than would be a standard router that will lack those type of interfaces. So in that model, the SDN controller, for instance, knows what application needs, knows how the network is actually set up in terms of topology and so on, and then can be used actually to instruct your existing routers how to drive the traffic in a more optimal way inside your network. And then the final point I wanted to point out is that all of this is really, let's say, IP centric. And of course, there is also many use cases on SDN and that's why you saw this rainbow coloring, that means optical. And that's another activity that we're engaged, actually, we know through Open Delight, but also through a new partnership with Ciena, is basically to enhance that network controller, that SDN controller in order to be multi-layered. So control IP layer, but also control the optical layer so that we end up with an optimal, let's say, setup and coordinated setup between those two network layers. So coming to the core of the, sorry, it's a bit long introduction, but coming to the core of the topic, and we are getting back to that end-to-end vision at the end, what is the virtual home gateway or what is the virtual enterprise gateway? And I think that's a very good use case because it's really end-to-end from that perspective. The initial case for the operator were like the maintenance and the management of those home routers. Depending on the region in the world, some people are just buying those routers like directly at Best Buy or whatever, separately from the operator, but more and more, the operator, they want to drive new services like Wi-Fi and so on. They were driven to provide you with that box, part of the subscription, so that they can deliver more advanced services. Then, of course, there is a cost to that. There is a cost of maintaining those hardware elements. And when you talk millions or tens of millions of equipment, then it becomes very complex to manage. Managing upgrades. Software upgrades are already a pain, but then, of course, hardware upgrade becomes very difficult. And you don't want to do truck rolls to tens of millions of locations. That's really crazy. That costs a lot of money, support and so on. So the pain points were really monolithic software saying, okay, we buy a software stack for our physical CPE, and then if you want to add services on the fly and so on, it becomes more and more complex because that whole software is untangled. Then also, those box, they have to be cost optimized, so they typically don't have infinite resources in terms of CPU, memory and so on. So sometimes it's difficult to insert new advanced services. And then that has been the drive for the first virtual home gateway type of concept. And initially, it had nothing to do with cloud. It has nothing to do with SDN. That's a concept that is probably like five-year-old now. But the model was more like network-based. Take the intelligence out of the CPE, out of the customer premises and move it to the network. Move it back to the network because then it's much more flexible and you alleviate all those support problems. Another drive for it is that if you look at a typical, let's say, a gateway, router, whatever, you get one public IP address with IPv4 and then you get some NAT. So basically for the operator, the type of policies you can apply to the end user is basically based on your home, based your online subscription, not based on your individual device or the people that is behind the device. On mobile, it's very different because it's more or less, you can curate the subscriber to the device, to the session, right? So then you can do a one-to-one mapping between who's the subscriber and what policies you want to apply. And you're missing that in a fixed line, right? So I will say so be it, right? I mean, there is no use case and so on. There is more value-added services you can deliver. But to the most part, people were really happy with that. But then there has been more and more, let's say use case, where you may want to differentiate the course across different equipment at home, right? One that is doing video streaming on Netflix, one that is doing web browsing, one that is doing software updates. There's been more and more use case about fixed mobile convergence, let's say offloading through Wi-Fi, for instance, your phone or your 3G tablets, right? And then in that case, offloading through Wi-Fi is nice, but then when you talk about community Wi-Fi, that more about roaming, how you can isolate that given device at home from the rest of the device and handle it efficiently. This is where this virtual gateway is not only like moving intelligence back into network, but in the process, it simplified the aggregation method so that now you get a layer two tunneling between the home domain and the network domain. So then you can do much more functionalities per, again, per device, per subscribers. You also get access to certain functions, like UPnP, for instance, that is not leaving the home boundary today. Now UPnP frames and so on can be broadcasted, right, done to the operator network. You can deliver new value-added UPnP services, UPnP proxy, easy discovery of video resources and so on. So there is many use cases as well that are uncovered with this one, beyond the course control, beyond the mobility, beyond all those functions. So what about enterprise then, right? So what's the difference between virtual home gateway and virtual enterprise gateway? Today, when we talk about enterprise and cloud, the main obvious use case is to say operators or let's say cloud providers in general, will be able to host enterprise IT services. So they will take all the enterprise, whatever, database, backend system and so on, servers and then move that as a virtual payload into data centers. And that has been, let's say, the main and the core, let's say, use case for cloud and enterprise, right, especially for the operators. But then they still leave a lot of network function in the enterprise that are either deployed by the enterprise itself or deployed by the operator in additional element or the CP. And here the problem is worse than on home because there is more services. The enterprise are more picky on the quality of those services, on the type of services, on the brand of firewall, whatever they want. And then the drive to actually simplify this, right, in order of better manageability, faster provisioning time, and cost reduction has been even greater for enterprise than it was for home. So then the model is the same, is to say yes, you're not only virtualizing and hosting the enterprise IT services, but also all the networking function that have been operated by the enterprise, operated by a sort party, let's say manager, or by the operator directly, are moved in that model into the cloud. So it's very similar model than the residential. The gains are a bit similar as well, right? Even though again, there is even more drive for enterprise because more complex services, more personalization is required over there. And then the difference really comes to, I think, two main factors. The baseline is the same, but when you look at an enterprise, typically they will have very different policies from one side to another side, from a group of users to another subgroup of users. Some enterprise, they will want a very specific brand of firewall, for instance. So there will be a lot of difference between two different enterprise or even two different sites of the same enterprise. And then the enterprise want to have a very tight control. The enterprise administrator, security administrator, they want to have a very tight control on those services. So they want to know a lot of things about analytics. They want to know a lot of things about security and get visibility and get fine-grained control on type of ACL, type of policies you want to apply. So there is a big difference which is really on the orchestration layer. And when we talk orchestration, doesn't mean necessarily, for instance, if you compare to OpenStack, doing that part of OpenStack, that can be a service level orchestration that is driven and operated by, for instance, the business people inside the operator, but that needs to interface with OpenStack in order to apply some of those services or drive some of the change in the underlying network. I think the second difference is that now we are talking enterprise application. So we can tunnel those enterprise applications from a CP down to the cloud. But then after that, those sites, right? And typically, we'll do that on smaller sites initially, right? Because the larger site, they will still have like a small data center or server farm or local resources, more probably. So you don't do that for all the sites. And those sites that are centralized in data center, of course, needs to communicate with the rest of the sites, right? You have any to any type of application and so on. So for that model, what you need, this is where you need the IP VPN connectivity, right? And then, of course, you can have different form of VPN, IP sec, and so on. But I think a very strong drive for those services to say, not only use those services in data center, but they are natively inter-work connected to your IP VPN instance in the one. So that's the second aspect. So now there is different way to implement it, right? You can say, okay, I move my services in the cloud and there is two main ways to do it. There is the simple model or basic model, whatever, I don't know how to call it, but it's basically the basic NFV, right? You have a software that runs on CP.  Done, right? So that's very straightforward. I think that's the benefit of it. The second thing is that if you're used to operate your CP using a given management system and so on, there is not a lot of difference on doing that. So that's, I would say, quite easy step to do. Then, of course, what it means is that it means two things. First, you have many instance to handle. Not saying that it's a problem. There is way to solve it, technically. But if you have a million CP, you have a million VM or million containers, right? Or 10 million or 20 million, right? So that still has an impact on your design and operation and so on. The second thing is that you're not getting all the benefit because I was saying you have a monolithic software. You buy from Vendor A. Vendor A is providing you URL filtering, time-based access, DPI, IPS, a number of set of services. Now, if you prefer for one given enterprise or for, let's say, other reasons to change one of these elements, then you have to change the whole stack, right? It's not like you can decouple those services. So our model is rather to say if you want to reap the full benefit, right, of the virtualization in that model, you should not do the simple one-to-one mapping, one virtual CP, one one VM. You should do it with SEN and NNV, meaning that, finally, at the end, that CP is a set of services that are chained by proprietary mechanism inside the box. Now, if you move those services into the cloud, you have to, you can replicate the behavior of a CP, but you replicate that behavior of the CP with different set of software. So all those software, they can be, like, from different Vendor, they can live in different VMs, and they can be desichained, or they can be chained in a different way in order to replicate the same behavior than a CP. But then it's much more flexible because it means you need to have, like, one-to-one model. You can say, for instance, your NAT instance is a big NAT instance that will handle 10,000 customers in one instance. You don't have to have 10,000 individual NAT instance to do that. And for NAT, for instance, it makes a lot of sense, right? Because you may want to share, for instance, for residential multiple subscribers to the same egress IP address, for instance.  For other things, the benefit, you can still use containers for certain services and do, let's say, one instance per subscriber, but at least what you have, you have the choice on how you want to, the lifecycle of that service or what type of service you want to deploy. So we believe that both models are, of course, we see both models in production. The second model is a bit more complex, but it provides you so much more benefit in terms of flexibility in the long run. So that's our target architecture. So I was mentioning you need to change those services, right?  You will want to build chain, depending on the CP, depending on the operator, that will have one or more of those elements, and from one or more of software version, or with one or two or multiple level of software version, or from one or more different vendors that you can offer in your catalog, right? So you have to build a number of chains, and already moving to the cloud, even without very advanced or complex chaining, you, it's already much, much, much better than it is today with physical box for the operator. Because, of course, if you need to build, you know, 50 different chains of service, today is very hard to do, because then it will mean that you have to deal with physical box. You have, sometime, you see the box that is with a red square. It means that you don't want to have, like, so many box instance, becomes very hard to predict, you know, much traffic. You will send to a given box to do, like, all the traffic planning is very hard. It means you have to convert the box differently to isolate subscriber one from the other. So there is a lot of complexity doing that in a physical world. In the virtual world, of course, spanning a VM is a very low cost. So it's making it much easier, right, to build a service chain. Also, you don't have to hardware built and bolt, right, those cables, those villains, whatever configuration of the switch that is all automated, right, through OpenStack and through the SDN controller. So there is a lot of benefit of using cloud, but what we believe is that we need to go beyond that. If you want to get a full benefit, we need to go beyond that. Because even with that model, you still have some issues about dynamicity, for instance. If you say, let's say a site or a site is currently connected on the chain on the top, that has everything, right, the whole enchilada of services. And then the administrator decides to disable one of the services. Say, I disable the URL filtering on that chain, right. Then you say, oh, it's pretty easy. You have some function that will steer that given IP address, that given traffic to a different chain. But then what happened? You have built, let's say, stateful entries on your NAT, on your firewall, on your DPI. You had state, right, layer for state and so on.  So it's not so easy in practice to get that level of dynamicity. Also it's not so easy in practice to say, it's very easy to say that site goes to that chain. When it comes to, oh, that CP goes to that chain, or that group of subscribers goes to that chain, or that given device when you're using your cell phone and you go to Netflix, and it's this time of day, then you actually have to bypass that given element of the chain. That's not something you can provision through static policies and so on. That becomes impossible. Then you need much more dynamicity and much more granularity. So the way we're doing that, we are basically building, rebuilding that service chaining completely controlled by SDN, so that SDN will control at the flow level and the flow can be anything you want. It can be a VLAN, so this is site R goes to chain A, that's very simple, or it can be a given device, or it can be a group of subscribers, or it can be a set of destination IP address. So subscribers or device or group, that could be a way to classify, that could be per destination. Is it, is the traffic staying inside your own autonomous system, or does it cross the boundaries, because then you may have different security policies, you may have different, let's say, charging policies for that domain. It could be OTT specific, of course, with certain limitation, right, in terms of awareness and in terms of URL and so on, but you can do already a lot by figuring out where the traffic is going and applying different policies. And then finally, it can be per application. You can understand that this traffic is a video flow under congestion, you know, let's say a congestion cell, and therefore you decide to redirect that traffic to different instance on the fly. And this could be quite handy in a different set of case. So there is many use case, and of course we are not going through each and every one, but there was some cut and paste of some use case which were related to either like security prevention, right? You detect some dose attack, you want to provide a clean pipe service to your end user or to your VM, and you need to block those dose attack or some of an LC traffic directly from the core. So then use as the end controller to either detect the attack or basically block the attack in an efficient way. That could be based, I was mentioning this network conditions, congestion and so on, then you will change a set of services based on this network congestion. That could be about inserting on demand a vast sort of service that could be again security related, right? You detect that you have certain type of attack, you want to log, redirect, store, do a more advanced parsing of the packets. That could be simply for offloading because some of those services are very high cost per bit. I mean, already you go through x86, so there is kind of high cost per bit if you compare with some hardware accelerated device, but then some of those services, they do a lot of inspection and so on. So they have some bypass function at the VM level, but it's actually much more efficient if you directly bypass from the infrastructure level where you can say this is a Netflix stream, it's going to last for one hour, right, or whatever. Then if you say that DPI has no problem with that, parental control or policy, whatever, agree that you can watch a Netflix film at home or at work at that given time. And then all your security, traffic, whatever, check that this is clean streaming and so on. Why do you want to send each and every packet to your, let's say, video acceleration for the rest of the session? Then you can use those dynamic, again, let's say control to offload the traffic and save a lot of traffic, like all the long live session, all the video flows, all the software updates, so many of them these days. Then you can bypass from your NFV layer and you can optimize a lot. Then there is also operational tool. You say, okay, it's great because I get all of that, but operational tool is great as well. You can say, I want to test a new version of my service, version 1.1, right, and I create that version 1.1, but I don't want to say, okay, I redirect all the traffic to 1.1 because it's not proven yet. So one simple model, you say, I want only to redirect 1% of the traffic. But maybe you have to be smart about what is that 1%, maybe it's a friendly subscriber that are part of the operator or get the service for free. Then when those guys are happy, then you have your basic residential subscriber, the bronze one. Then you get your gold residential subscriber, then you get the enterprise subscribers. So you can be smart about the way you load balance in the network. It's not load balancing based on the operator policy on hashing of IP address and so on. That's load balancing based on policy per subscriber or per enterprise. And then you can easily insert and try out new services and so on in the network. So that's what you mean by intelligent service chaining, right? Or the extension we need to do to get this intelligent service chaining. The second type of enhancement that we need in the cloud, I was mentioning this dynamic connectivity on the outside world, of course, you can choose whatever technology you want inside the data center and kind of automate through a DC gateway or you stitch that to the external world. But that always come with this set of complexity in terms of operation, maintenance, trouble shooting, redundancy and so on. So there is actually a lot of push right now in the operator to say we, if we build a cloud for operator purposes, right? We might as well reuse some of the tool or the network technology that's one we are familiar with, that we understand very well. Two that are very proven and very flexible. They can do point to point, point to multipoint, layer to layer three IPv6, inter-IS, inter-domain, whatever you can, you name it, right? And then so it's flexible, it's proven and they are used to it, right? And by the way, you can optionally, potentially suppress also some level of stitching and so on that create complexity and create cost. That means you run natively some IP MPLS down to the data center. And that is another thing that is not necessarily mandatory, you know, connected to the virtual enterprise gateway, but you see more and more as part of requirement as soon as you run hosted enterprise services for an operator in a telco cloud environment. So in that model, what happened is that you can keep your existing over late type of model, you keep your existing as the end controller. The only difference is that the as the end controller run more like routing protocols. And instead of pushing, let's say simple Mac address or VLAN cross-connect into your V-switch, it will push IP or MPLS feed entries into your feed, right?   You also get for free inter-working with your existing IP one environment. That is very important for those type of applications. And then finally, in terms of value of as the end or one value of as the end identified for that given, let's say use case, there is the application aware transport. I'm not sure is the right marketing them, but what I mean by that is to say, again, what I was saying before, if you have a transport controller, so you see like on both side, you will have two data center, right? Left and right. And in the middle, you have your IP network, standard routers, nothing about SDN or nothing about cloud, right? This is your standard router network in the middle. There is a way with SDN and with OpenStack and with the right level of orchestration to know more about, you know, who owns that VM, right? Or what is the policy I need to apply to that VM? Or who's that subscriber? What type of policies I need to apply to that subscriber? So since you know more of it and you can control more of it, you can control the endpoint, right? Being the V-switch in terms of classification and so on. Then you have the ability now to treat the traffic in a more intelligent way in your network.  Or it could be that you have a lot of resiliency, so you can have a router failure, then you can have like a fiber failure, then you can have multiple failure and see your traffic is up. This can be kind of SLA, that could be about bandwidth. It could be a strict bandwidth guarantee when we talk about course in operator network. Most of the time, say, we give you the right marking and with that at 90.99%, you will be safe, you know, statistically. But some use cases are not safe with the statistical. They want to have real guaranteed bandwidth, something like TDM, which makes it a problem for TDM to IP migration for the operators, because you cannot emulate that. And it becomes quite complex. You can do it in IP today, in IP and PLS router for 10 years actually, but no one does it in a large scale because it's too complex to provision and maintain so many tunnels. Now with ASEAN, you can do it on the ASEAN controller. And then finally, there is also in terms of use case latency, so that you can say to pass not based on the cost, not based on the resiliency, but maybe based on latency. So those are the typical, let's say, parameters you will find. Maybe there is more, of course, parameters you can pass. And the idea of the ASEAN controller in that model, there is a bit of a lot of detail, but maybe I will cut short. But it's basically that when the orchestration is basically sending or creating, let's say, a new VM, a new resource, receive a new policy from the orchestration, it will basically let the SDN controller in the data center know, right? What are the requirements for that application or that flow? Then what we can do, the SDN controller, what you can do first, is to get the VM reachable to the outside, right? So I was mentioning BGP, then you have to tell with BGP, those are the IP address and the labels that you have to use to reach or the IP address that you have to use to reach that VM. But then on top of that, it can actually pass along to the core controller. Basically, you see that other transaction, it can actually request a specific SLA for the services. And when you request that SLA for the services, then this core network controller knows has a holistic view of the network and the topology and it can decide for that group of application, if we want guaranteed bandwidth of those SLA requirements, I am going to select that specific pass in my network and it can make it in a very efficient way because then it will create a given pass ID and of course it will multiplex 100 of thousands of VM or flows or whatever that share somewhat of the same requirement into those aggregate pass. And this is the rule where you see that kind of DC gateway element has to be controlled by this core controller and this is where it will classify and remap the traffic into those core tunnels. But then if you look at your existing core routers, right, in the middle of your network, they don't have to be aware of the existing application. They don't have to have the state for each and every flow in each, every application. So that becomes much more manageable and much more scalable than it used to be before. And you don't have to, you can continue to use your RSVPTE and so on aggregate tunnels. You can also use, let's say, new methods such as segment routing to make that in a more lighter way. So when we put all of these together, virtual enterprise gateway, what would be the typical workflow? This light gray box, that's the data center environment where you can see OpenStack. You can see the Asian controller embedded into OpenStack, the cloud Asian controller, and some infrastructure. I'm seeing a V-switch, of course, is many V-switch or it could be like physical switch as well. The first thing you have to do, you have to create resources, right? Create your VM, create your resources, shared or not, you know, you have the choice. But it has to be, of course, isolated, right, in terms of tenancy. And then the second part you have to do is configure those instances. You have to create them and then you have to configure them. This is already where it becomes a bit more complex. Who's configuring the actual instance? Is it the data center, people operating the data center, data center orchestration, the resource orchestration, or is it the service level orchestration? In many cases, that's another level of orchestration that is responsible of configuring the VM and sometimes about doing the VNF like cycle management. So knowing about when to add new VM, the load of VM, and so on. The second stage, of course, is to, you know, using Neutron typically, but now with extensions, is create the connectivity. But it's not only connectivity in the boundary of the data center, but it's connectivity between data center, outside of the data center. So here we need also, for instance, to look at new extensions to pass along additional information for VPN connectivity. Then I was showing like a dis-line, you know, bandwidth, SLA, reachability, that's BGP, that's PSAP, that could be like a routing protocol in between that you use East-West between the controller. And typically those are different controller instance, different domain, your IP domain, your data center domain operated by different team. But you can have East-West interface and it's very important, of course, if you want to have everything automated and orchestrated and to end. Then once you get that, the transport controller can actually do the proper mapping and reservation and stateful reservation of the flows into your core network. And then the service controller, we'll have to use potentially another SDN controller again or another function inside the SDN controller in order to actually chain the given services, right? And this is the flow you see where this service level SDN controller have to talk about the infrastructure SDN controller. So now you see the complexities that you have a resource level orchestration and then you have a resource level SDN controller but then you have also service level orchestration and service level SDN controller. And we need to define the interfaces between those two layers. And then create the service chain along the line I was explaining before. And then the final piece is that you can have a very simplified CP but in many cases you still want to control some elements of the CP. So for instance, if you want to prioritize certain application on the upstream and you want to be application aware, you can do the DPI in the core network but then you have to remap the course and so on directly on the CP. Or if you want to allow local switchover or not allow local switchover at the CP site, then you can use something like open flow to drive the forwarding table of the CP. So it means the SDN domain is not only in the data center but has to reach maybe the next gen CP on the access. And I just highlighted these little dots, maybe some of the points where we have to redefine in open stack or in the architecture, extension and so on that are required. And I will end over to Alain for this part. Okay, thanks Francois. It's true, French people talk a lot. It's really true. And I have exactly two minutes left but I'm Irish, I can talk really quick. So I'm gonna give you a quick rundown, two minute snapshot of actually what we've actually done to make the virtual enterprise gateway. This is actually a prototype we've built. It's running code. If anybody wants to come to me after the meeting, I can give them a walkthrough on actually what we've actually changed and what we haven't changed, what we've actually used that comes from Trump from OpenStack and what comes from Trump from ODL. So just to give you a quick snapshot, there was a couple of, I need to go to this slide. Okay. So we have built our own service orchestration manager on top and it's already given me a hint to move or we've built our own service orchestration manager on top and what we've actually done is that's where we keep all the business real logic. And in that, what we do is we actually define like in a service catalog, you pick the type of service that you actually want, you go select the service, you define the user groups, the IP address pools and then you define the inline service that you want. When you've got all that done, then basically you actually constrained the logic on actually how you want the actual service chain to be built. When that's actually done, then what we've actually done is we've actually taken OpenStack Neutron and like the OpenStack trunk and then we make API calls all the way down from the service orchestration down to an OpenStack controllers. So what we do that for is basically for statically provisioning the services, instantiating the VMs, pulling the images on the back end from glance, saying this one is a firewall, this one is a router, this one is a low balancer, DPI service, snapbox. And then the parts that we have added, we've added a part called the Flow Network Programmer and that's the enhancements we've actually done to the Neutron-Norperian interface. And the reason why we've done that is actually to dynamically learn when the services are created in Neutron, in ODL of actually what service has been instantiated on what VNIC on what OpenFlow port. So what we've actually done is we take ODL then and ODL is actually the one actually for configuring and instantiating the actual service change rules. So we haven't made any changes in OVS, the switch. We've made some small enhancements in OVS DB. This we're actually going to upstream back to OpenDailer controller. So all going to be open source, nothing we're keeping for ourselves. And what we've done in the prototype, there's a couple of different ways that you can actually use for service tagging. You can use an MPLS LSP, you could use a VXLAN ID. Or what we have used is we've also used the IP TOS. The reason for that is because MPLS LSP labels actually wasn't fully working on OVS, so we actually have to make some quick cuts and work around actually for that. And this gentleman is telling me to get off the table. Summary, Francois, do you want to give it a summary? Okay, I can give you this, okay? So there are some extensions that we had to do. All the extensions that we've done are on Neutron. We're going to upstream all of that. And the idea behind this is that you can actually plug and play different network service types and different vendors, right? So you can imagine you could actually be using vendor A for a firewall or vendor B for a firewall or vendor C, right? The whole idea of the solution that we're actually building is so a service provider and operator can actually swap and actually decide which firewall, which router, which low balance, or which DPI box he actually wants to instance A. And the magic part that we are actually adding that we're still upstreaming back to OpenStack and ODL is actually to figure out like how we're actually going to build a service chain. So how to actually make the flow from VMA to VMB or VMA to VMC to VMB. That's the actual part that we have actually done in our enhancements. And this we're going to upstream back, like I said, like to OpenStack Neutron and also to ODL. So what else can we do? So I think one of the most important parts is also when we talk about SDN and NFE, right? This is not just applicable like for like inline network services. You could actually use in this for redefining like how typical like network boxes are built today, right? So you could actually look at a CPE and you could actually break the CPE out and you could actually say, I want to have my DHCP. I want to have my actual like IPOE or PPPOE termination done in separate VMs, right? So one of the things that you can actually do with the service chaining is actually you can blow out actually how you would actually have a physical box actually defined today and you can use the service chains for redefining what you would actually have done like in a specific vendor lock-in box, swap out the different components that you actually want in that box and then decide how you actually want the flows to actually be connected together. So I really need to get off the stage because the gentleman is actually pointing what appears to be a gun sign to my head. So I need to give out some cards actually to some people. So my colleague here Mahoud has actually collected some papers from some people and we're going to give out some prizes.


Teachers from across the region met this morning at the East Kentucky Expo Center for the opening of the Title I educational conference. Pike County School Superintendent Reid Adkins says it is very important for Eastern Kentucky teachers to have access to professional development resources right here in Pike County. We started off the morning talking about the economic situation in Eastern Kentucky and how important our educators are to our students. Right now they're the most important group of people we deal with. During the two-day conference educators from across Eastern Kentucky are able to share experiences and network with other teachers as well as attend breakout sessions on topics that hit close to home. So they're able to adapt it in ways to meet our needs and our classrooms here in Eastern Kentucky just learning the resources we can use how we can expose these to our students that's what I like it's a down-home professional development that really connects for us as Eastern Kentucky teachers. With a downturn of the coal industry creating challenges for thousands of Eastern Kentucky residents educators know the children are being affected which was another reason Superintendent Adkins and his staff wanted to bring local teachers together to figure out ways to combat the problems unique to this area. You can get quality professional development Central Kentucky in several different areas we try to bring good quality PD to Eastern Kentucky. The conference titled preparing for excellence will wrap up tomorrow afternoon reporting in Pikeville for EKB news I'm Shannon Deskins.


To team keep it clean welcome to another episode of NFL questions from subscribers And this has been like literally forever since we've been able to do one of these because Ravens have had So much going on over the past not even just a couple of weeks But they just been having a lot going on But what question from subscribers is come short a lot of y'all forgot about that But what that is is a series where you can ask me any NFL question And we answered in the video just like this night if you want to be a part of it You can either send me an email to team keep it clean at gmail.com or for the patrons Appreciate y'all patrons by the way all the team keep it clean patrons You can just send it directly on Patreon if you want to become a team keep it clean patron you can go to patreon.com slash engraving vids. If not, that's fine We got some great questions like we always do. Thank you all for being so patient With questions from subs because again, like I said, it has been forever almost forgot how to do it But since I finally did remember let's go ahead and jump into it first question came from my boy daddy gaming He said my boy engraving. I hope you in the squad are doing all right got another question for you I thought very deeply about this one And I think it could be something us Ravens fans really need to keep a close eye on Wink Martindale getting hired by the Giants is huge for us The reason why I say that is because imagine if he flushes there and puts together an even better defense than he had here Maybe even better than Mike McDonald's that would make hardball look real bad and keep in mind But shawty got his eyes closed on him now You know why because in his recent statement about hiring Sasha Brown He mentioned how now the president GM and head coach all have to report to the shawty It wasn't like that previously. They reported that cast That they reported to cast the majority of the time things are shaping up and if wink puts together a better defense than us Hobbes Hobbes might skedaddle much love. I hope it ain't too long. Yeah, well now. That's all good Um, I don't really think so. I don't I don't really think if I think if if wink puts together a really good defense It would just all depend on how it comes together. I don't really think that will do much for John Harbaugh at all Because the the Ravens, they wouldn't be worried about the Giants defense. They will be worried about the Ravens defense Now if the Ravens defense is coming up short, that's all gonna be on Mike McDonald and if the Ravens defense is doing a great job and Despite what winks do I don't think wink has any bearing on The Ravens at all. I really don't work except when the Ravens play the Giants But I don't really think anything that wink does has any bearing on John Harbaugh or Mike McDonald at all People will compare of course cuz it's Ravens previous defensive coordinator compared to that new defensive coordinator But I don't think it'll have any impact. Next question came from my boy that hit man John He said at the time I'm writing this this morning. So good morning, lol Well, but when the time that I'm answering this is also the morning. So good morning back to you my friend He said will Lamar Jackson ever become a championship caliber quarterback under John Harbaugh and Greg Roman In my opinion the Ravens coaching staff should be embarrassed that Joe Burrow a second-year quarterback with a rookie number one wide receiver Just took over the AFC He also took over the AFC North with ease. I understand we were injured But wow we could only win one game without Lamar You're telling me that this team couldn't win two or three games in like an eight game stretch to make the playoffs without Lamar How many years has it been since we had a decent pass rush and after all these years We still don't have a consistent wide receiver one Sorry for the ramp, but you were right on your previous videos Ravens. Let John off the hook. Oh Man, yeah, the Bengals on Bengals put Ravens on notice for sure Because they said hey, we're here Hey What's up? We in the Super Bowl and the Ravens like man we like four years and we haven't even come close to the Super Bowl and You can even even if you take out this year with the injuries. Okay, take out this year. What about 2020? What about 2019? And even 2009 even if you take out even if you take out 2018 But like I know I'm always a rookie that year. He only started the last one seven eight games of the year Oh, take that out, too 2019 to 2020 the years where the Ravens rosters were most consistent Didn't even come close We thought I was short. I was like I just knew oh man Super Bowl about to be in Miami and Ravens about to be in there, too After that 14 and 2 so But will they ever be a championship caliber team under John Harbaugh and Greg Roman Mmm. Oh, that is something that's scary to think about I was just on a podcast the other day I mean and this question was asked as well I think they can be if a lot of philosophies get changed I think that with um With Greg Roman and John Harbaugh if they change a lot of the stuff that they didn't see that's the thing I Feel like John Harbaugh I feel like he could he would have a greater chance of being able to change a lot of his ways rather than Greg Roman Greg Roman is an offensive coordinator So that means he was hired with a particular style of his offense that the Ravens had in mind where they were like All right. Yeah, we think this could work out. We think you can do some good things here and he did He was a nice introductory offensive coordinator for Lamar Jackson amazing great job But it just seems as if it has gone stale, but since the Ravens they they're gonna stick with it. It's like, okay. Well pressures on them pressures on but if I Feel like they would have to like in order for them to really be a championship team under Harbaugh and Greg Roman They're gonna have to dish out some some of the responsibilities that those guys currently have especially Greg Roman to some other people like me I Don't know man. It's It's just it's scary to think about It's really scary for me personally to think about like man Like can they get over the hump with those two? It's because I just feel like the offense from the 20 to the 20. I feel okay. Cool. Yeah Oh, yeah, yeah, yeah, they're gonna get that y'all it's but Inside the 20 is like oh man And I just cuz I just feel like this team they just rely on so much on Lamar's athleticism and It's kind of something.  Ah, it's straight. Oh Yeah, this ain't my best play call But yeah, hey if it don't work Lamar would just take off like hello, don't you get it? So that's something that scares me And I just I would love to see and again, this is nothing new from me This is nothing new from me. I just want to see The uh the play calling the passing game especially just evolved from where it was in 2019 I said this after that year after we went 14 and 2 Um after the playoff game. I said, okay. Well, what's next? What's next and even before the playoff game? I said, what's next because With with that playoff game. It's like, okay, they went 14 and 2. All right, but then they they went They they went directly away from what got them there again One of my biggest issues with greg roman is that he gets away from the floor of the game He gets away from the floor of the game I used to hate when people would say, oh man, like the announcers the analysts thought oh, man You can't run your way to a Super Bowl And it would be so frustrating because it'd be like man, like the ravens never even tried They never even tried Because in that playoff game where they broke all in the year where they broke all those russian records They literally ran a ball nine times what they're running back nine times nine times You had an engine mark angrily And what he got either six or three or six carries. I forget And then Gus Edwards had either the other three or six I forgot which one of them got three and which one got six They had nine carries what they're running back and it's like Gus Edwards was healthy He was healthy and he had been doing this thing in that that year along with mark angrily But you ran the ball six either three or six times with him And and it's like They just gave up on it And they were not down big either. They gave up on a run game.  Nope, not doing it not doing it And it's like what how why what for what? again the the the flow of the game for greg roman the flow of the game And it just At that point I was like, what's what's next? Well, what's what's it gonna be? What's what's what's gonna be next for this team for this offense specifically? What's gonna be next? What's gonna go down now? And we still got some questions now this year they they were the passing game It was taking another step. It did still have some times where it'd be like what is going on It would be with the playcaller now. Lamar wasn't perfect either. So don't get me wrong. He was not perfect at all neither were the wire receivers But it everything starts from the beginning everything starts With the playcaller itself And when you saw some of these situational play like it'd be one thing if they drew up this fire play and sometimes they did It'd be one thing where if they drew up this fire play and it's like, oh man, Lamar just missed him Oh, man, the wire receiver dropped it. Oh, man, the offensive line ain't blocked and Lamar got sacked He got hurried and had to throw it away or something like that and those things happened But far too many times you will see where the situational play calling It's like what are we doing? What is going on? Who is thinking of these things that the ravens are running? crucial third down third and long Oh Why receive a screen? And and and a lot of the the the playco third and long Oh QB draw qb power design qb run And it would be like How why why? When plays fail And and not to say that g-roll or offense got to be perfect Because they don't have to be But they have to be better. They have to be so much better They have got to be When players fail I would love it It it should be on the players It should be on execution It should be on execution It it shouldn't be where oh like like where the ravens even if a play would have worked That oh man, they still wouldn't got it anyway Oh that that was designing it wasn't even to get a first down That play design it was it didn't even it wasn't even designed to get a couple yards Like so much of the situational play calling last year had just been outright bad And we see that too many times too many times That's what scares me moving forward with the team That's what scares me because I just I hate that is and I had heard this a lot But then I was like, uh, well, I don't know But when you watch it it seems like oh man, that might be the case where it seems like On offense, they just rely on Lamar's ability so much To sort of build him out To sort of get them out of about oh, okay. If all those fails. Okay. Lamar will just run. You know what? Even if all else doesn't fail. We're just designed to play for Lamar to run We'll do that and it's like what and The the and then there will be those option plays It's like, oh, I hated those so much. Y'all know anybody that watched the games with us Oh, my goodness.  We know Ronnie Stanley was out too But the way that they, um Since jk and guston justice hill, they were all out for the year All right, you got the vante free militarius marion. They they weren't anything special in the beginning of the year We know that But then even what you got you got this other guy Who was with the team last year?  No, we don't know tyson.  Guess what? You had an explosive runner sitting right there all year all year All year long and you decided no nope We're not gonna use that guy.   So to answer your question, um Will it can lemar be a championship quarterback under john hardball and giro? It's possible But a lot would have to change so much would have to change Will they make those changes? I can hope so I can hope so But I don't know I don't know I I hope this team Just starts heading in another direction When it comes to their philosophy And like I've said plenty of times all right hardball new year. Let's see We know what history says About hardball. We know what history says about g we know what history says about both of those guys But let's see And again lamar got improvements that he got to make too The hero ball that got to go man You got to live to see another down throw that ball away He got to improve on that that that short passing game Because there will be times where sometimes he will lead or receive it too far or he'll throw it behind him Uh, and it just won't be on the money with that short passing game So that that's what he got to make another improvement He also got to do a better job of seeing seeing the field because it's it's great because that's something that he did a great job at That's something that he had he had done a great job of that but He got to do a better job of seeing the field and finding this guys Another thing that he could do. Oh, it will make such a big difference. We've been talking about this for a while too We'll beat him timing routes. Oh He can start working on those that that's what I would love for lamar to work on this off season timing routes To where he don't got to just throw to the open guy, but he can throw the guy open That would be great And and we we know with the tight window throws that's lamar all day That he got that already. We ain't worried about that um but I think he also got to do a better job of gaining big trust with other people too He got to build his big trust up with his other guys too Because you know, hey mark angels could have three people on them. Hollywood could have four people on them and the mall would be like I trust him boys. I trust him to make something happen to throw it to him And hey, sometimes it works sometimes it doesn't Uh, but you got to build up big trust for other people too. Got to give other people more opportunities as well So it's not just all john hardball and giro. There's a little more too everybody got to step it up everybody And then we could talk about everybody else too, but those those are the main three guys every cost of two now every cost of like last year He did a great job of building this team But then you got to think about the draft picks now last year's draft picks. It's still early And the early ones they they definitely had an impact like rasha baitman when he did play when he actually did get an opportunity to Uh die for your way He had impact he he started off real hot Then he kind of slowed up a little bit got a little quiet then he would go like up and down It's a rookie. He was a rookie And also he was a rookie in this defense Well in that defense because now it's mike mcdonald's defense. So it's different now um But every the cost of drafts got to be better. They got to be more impactful They got to be more impactful and that's that's on eric the costa and john hardball and greg roman and mike mcdonald because they have to increase horton too, but more so, uh greg roman and mike mcdonald because Though guys have to be used to their strengths. They have to be used to the best of their abilities But in the beginning they have to be used Not asking everybody to be a starter. Everybody's not a starter but These drafts got to be more impactful They got to be They have to be It's important that you get more playmakers Difference makers It's it's so important. Don't just draft. Just okay. We we drafted this guy that No, and the hoarding of the picks It got to be quality over quantity. It has to be in my opinion It should be quality over quantity You got what nine 10 picks 14 have as much picks they got I would rather them have six or seven great draft picks Rather than 10 11 Okay, or even good draft picks I would rather them have six or seven great ones Because that would mean that they got some players that can come in make a difference making impact And again, everybody don't got to be starters. Not everybody's gonna be a startup But the project players no Don't draft projects. You don't do well with projects. This is not a science fair. It's not It's not a science fair Don't draft projects draft guys that are ready to come in And play right away No projects No Because if a guy's a project, especially if you draft him late, then you're gonna be like, uh, well, he's just a project Anyway, our expectations are low form So it is what it is if he plays well cool if he doesn't cool But uh, it is what it no, you're not gonna care that much You're not gonna be as invested in him and I know it's a big difference between investment in like a first round pick Versus a fifth or sixth round pick. I I get that But if you look at a guy like a project Then you're gonna treat him like a project If you look at a guy like oh, this guy could be a potential star You're gonna possibly treat him like a potential star Don't do the projects So anyway, um To answer your question again Yeah, I feel like some things will have to change. Um, if if lamar is going to be a championship quarterback Under john harbaugh and greg roman next question came from my boy marco. He said engraving my brother. What's good? I was thinking what if harb's makes giro and tt co-offensive coordinators with giro focusing only on run game And t focus on on a passing game giro could still be the play caller But each of them focuses on the area of their strength. Let me know what you think That would be interesting. I think yeah, my guy skeptic gold. He had uh, he had brought that out in one of those little twitter spaces the other day um That would be something right there. Uh, if they had like co-offensive coordinator roles Um, but that would basically be the ravens sort of pushing giro out the door eventually because giro was hired as The offensive coordinator um and the ravens then uh after a couple years they brought in Y receiver coaches and pass game coordinators to help him with his job where he was struggling that So that already kind of lets you know like, okay. Hey, you struggling with this. You need some help so then if they had They took a guy who was a wide receiver coach and made him the co-offensive coordinator Then that would be the writing on the wall that giro would be getting ready to be gigo Uh, because you don't you don't bring somebody in to help somebody with their job where they're struggling at And then you give them the same, uh, exact job title Like, oh, this or this is our offensive coordinator. This is our Assistant an offensive coordinator or co-offensive coordinator. That's that's the beginning of the end So if they did that, I wouldn't be mad. I wouldn't be mad Uh, they would it would take a lot of humility right there to do that Like that's like imagine that imagine you at your job And you all right.  Uh, next question came from my guy adrian He said Fully healthy next season Where do you see us ending our season? Um, next year with no bias, uh, I think we could win a super bowl if And only if our offense is 65 passing and 35 running He put in all he put in all caps. No qb design runs If we do only one per game Hey I love it. Um I would say uh right now Based off of pending free agents because it's it's very early We haven't even got like even if they do get fully healthy next year Um, it's a lot of guys that are pending free agents. Um, they got to get through the draft free agency bringing back some of their own um But right now I would say um I can say afc championship maybe, um I just wouldn't be fully convinced yet Uh that this team would be ready for a super bowl I it would just I would have to see how they are in the regular season And if they really like take that jump if they really take a significant jump as a team, um, they again They were making a jump this year They certainly were but it was still the a lot of situational stuff that was like Uh But fully healthy Uh, this team would be a lot different than the way that they were last year Obviously more toward the end of the season. Uh when they lost more and more guys Mainly, uh, lemar jackson But if if you have lemar jackson in there, I think they were easily in the playoffs easily easily Like those last six games even if you get dog walked by the bingles again There's no way lemar jackson lose no five games six games. There is no way no way um But yeah, right now I would say maybe afc championship Uh, I can't say super bowl right now until we see that product on the field consistent


Welcome, I welcome you all to this lecture in the course Sandhi in Paninian Grammar. In this lecture, we continue studying the Visarga Sandhi, Visarga Sandhi is part of the Panchasandhi prakarana that we are studying in this course right from the beginning. So we studied at Sandhi first, then we studied Hal Sandhi and we studied various types within those Sandhi and several instances and various examples illustrating all those instances and types. Now currently we are engaged with the study of Visarga Sandhi, we said that Visarga Sandhi is the Sandhi that takes place of the Visarga, Visarga is the substituent and the substitute that is stated by various sutras in the form of either Shri or Jibha Mooliya or Upadmaniya or Sir or Zero Substitute all these they are called Visarga Sandhi. So what is a Visarga Sandhi once again, Visarga Sandhi is a Sandhi in place of a Visarga where Visarga is a substituent and in its place sounds like Sir himself or Sir or Zero deletion they are the substitutions. So Visarga is the input and all these which are represented here by the letter X they are the outputs. This is what is Visarga Sandhi and here are the sutras which state the Visarga Sandhi. This is the second set of sutras. The first set of sutras consisted of Kharavasanayur Visarjaniyaha, then Visarjaniyasya Saha, then Sharpare Visarjaniyaha, then Vaashari. In this context we also studied another Vartika which says Kharpare Shari, Vaavisargalopavaktavyaha and then Kupo Kapavucha. This is the first set of sutras dealing with Visarga Sandhi. In this second set we have following sutras. All these sutras we have studied in the previous lecture. Now in this coming lecture we are going to study the remaining sutras in this particular set. They are Isusos Samarthi, A344, Nithyam Samasai Anuttaravadasthasya, A345, Atakh Krukami Kamsa Kumbha Patra Kusha Karini Svanavya Yasiya, A346, Adhas Shirasi Padhe, A347 and finally Kaskadishucha, A348. Let us study the sutras on the right hand side one by one. Let us take up the first sutra, Isusos Samarthi for study. Isusos Samarthi, A344 has got two padhas, Isusoho and Samarthi. Isusoho is 6 slash 2 of Isus.  So Isusoho refers to part of Isus. So this refers to the Visarjaniya which is part of Is or Us. The other word is Samarthi which is 7 slash 1 which in this case indicates the meaning in. So in the semantic relatedness, so this is an exceptional rule which is indicating some semantic relatedness as the input for this particular sandhi. Otherwise in this sandhi chapter we have noticed that by default meaning has no role to play at all as far as the sandhi is concerned. It is only the juxtaposition or the close proximity of the sounds which brings about the modification in either one of the sounds be it earlier or be it later or in both the sounds purva as well as para. But this is a peculiar case which says that semantic relatedness is extremely important for this sandhi to take place. The other words continued in the sutra are Visarjaniya Sya, Kuppoho, Shaha and Anyatarasyaam. Visarjaniya Sya is 6 slash 1 of Visarjaniya which means in place of or Visarjaniya. This indicates the substituent which is a Visarjaniya, Kuppoho is 7 slash 2 of Kuppoho, Shaha is 1 slash 1 of Sya that is sound Sya and this is our substitute. Anyatarasyaam means optionally. So in place of a Visarjaniya or a Visarga substitute Sya. This is the meaning of this particular sutra. This Visarjaniya should be part of is or us and then these two words the one which has got is and the one which begins with K they should be semantically related. In that case, Sya will be the substitute which will substitute the Visarjaniya and that too optionally. So the meaning of the sutra is this. In the environment of semantic relatedness in the sentence immediately before Ku and Pu in place of a Visarjaniya substitute Sya optionally. I repeat in the environment of semantic relatedness in the sentence that is Samarthya immediately before Ku and Pu Kuppoho in place of a Visarjaniya, Visarjaniya Sya substitute Sya optionally. Anyatarasyaam. So this is an example. Surface plus Karoti. So the word surface is semantically related with Karoti. Karoti means he or she or it does. Surface refers to Ghee and this is the accusative dual Ditiya Ekavachanam of Surface. The sentence meaning is somebody either he or she or it, they are doing the Ghee. Surface Karoti. So Surface is semantically related or linked with the action of doing denoted by the verbal root Kru in Karoti. And so Surface has got S which is immediately preceded by E. So this is S, semantically a part of Surface which is semantically related to Karoti at the beginning of which is K and so now Isoso Samarthya has got all its conditions fulfilled. So it applies over here and substitutes this Visarjaniya in Sarpihi into Siv by Siv. So Sarpihi Karoti is substituted by Sarpish Karoti and finally we get Sarpish Karoti as the output generated which is an optional output. So we also have Sarpihi Karoti. Here is the case with Dhanush Karoti. So either we have Dhanush Karoti or Dhanu Karoti that is the optional form. Next we go to the Sutra Nityam Samase Anuttarapadasthasya. This Sutra has got three padas Nityam Samase and Anuttarapadasthasya. Sam means obligatorily Samase is 7 slash 1 of Samasa meaning in the compound Anuttarapadasthasya is 6 slash 1 of Anuttarapadasthha which means not a part of the Uttarapada. Uttarapada refers to the final component of a compound. Uttarapada is a technical term defined by the later Paninian grammatical tradition as the final component of a compound. The words continued are Isussoho 6 slash 2 of Isus, Visarjaniya in place of the Visarjaniya, Kuppoho 7 slash 2 of Kuppu and Shah 1 slash 1 of Sher meaning sound Sher. So Visarjaniya is the substituent and Sher is the substitute. This Visarjaniya should be part of Is or Us and this Ku or Pu is part of the subsequent padha. Now this is an Us should not be part of the Uttarapada and the two padhas one having Is or Us and the other one having Ku or Pu they should be both part of the Samasa in which case the substitution Sher takes place obligatorily and not optionally. So the meaning of the sutra is the following. In a compound Samasa, immediately before Ku and Pu, Kuppoho in place of Visarjaniya, Visarjaniya which is part of Is and Us, Isussoho and which is not part of the Uttarapada of the compound, Anuttarapada sthasya substitute Sher, Shah obligatorily, Nityam. I repeat in a compound Samasa, immediately before Ku and Pu, Kuppoho in place of Visarjaniya, Visarjaniya which is part of Is and Us, Isussoho and which is not part of the Uttarapada, Anuttarapada sthasya substitute Sher, Shah obligatorily, Nityam. So we have Sher, Pis plus Kundika and this is a compound and so, Sher is the Purvapada, Kundika is the Uttarapada. So this Sher is appearing in the Purvapada. Now in place of this Sher we have Ruh as the first substitute then Visarjaniya as the next substitute. So we have Sher, Pihi plus Kundika. Now this Visarjaniya is part of Is, this Visarjaniya is not part of the Uttarapada, this is part of the Purvapada and it is followed by K. So all the conditions are fulfilled and so this Visarjaniya gets substituted by Sher obligatorily, there is no option and so we get the form Sher, Pis, Kundika finally derived and similarly we can also derive the forms Dhanush Kapalakam in the same manner with all the conditions fulfilling for Nityam, Samasaya, Anuttarapada sthasya to apply 8345. Let us proceed further. Let us study the next sutra, atah kru kamikamsa kumbha patra kushakarni ishu anavvayasya 8346. This sutra has got 3 padas, atah which is 5 slash 1 of at referring to short a and ataha means immediately after short a, kru kamikamsa kumbha patra kushakarni ishu. This is 7 slash 3 of kru kamikamsa kumbha patra kushakarni and so this word kru kamikamsa kumbha patra kushakarni ishu means immediately before all these elements. The other words continued are anavvayasya 6 slash 1 not being a part of an indeclinable which is part of this sutra, nityam is continued which means obligatorily, visarjanyasya continues that which means in place of the visarjanyasya, kupu oho continues that is immediately before kupu sahha continues which is 1 slash 1 of sir which means sound sir, samase continues which means in the compound and anuttrapada sthasya also continues which means not a part of the uttrapada. So in this case visarjanyasya is the substituent and sir is the substitute. The other environments are a which should come immediately before sir and kupu oho in that case kru kamikamsa kumbha patra kushakarni these should be the following words and this should also be a samase and the visarjanyasya should not be part of the uttrapada. If all these conditions are fulfilled the visarjanyasya is to be substituted by sir and that too not optionally but obligatorily. So the meaning of the sutra is the following. In a compound immediately before kru kamikamsa kumbha patra kushakarni etcetera in place of a visarjanyasya which comes immediately after shot oh and which is not a part of an indeclinable and which is not part of an uttrapada substitutes a obligatorily which can be presented in the form of an equation like this. If this is the pada and visarga comes at the end of the pada preceded immediately by shot oh followed by kru kamikamsa etcetera then in this case this visarga is obligatorily substituted by sir there is no option and so utt plus visarga plus kru if this is the input utt plus sir plus kru is the output generated by this particular sutra. Here are the examples ayaha plus kāraha kāra is derived from the verbal root kru by adding the suffix an. So we have ayaha plus kāraha. Now this visarga is at the end of the word is this is not an indeclinable is is purvapada and it is followed by kru so all the conditions are fulfilled and so this visarga is now substituted by sir following this particular sutra atakh kru kamik. So we get the output ayaha kāraha similarly ayaha plus kāraha and we get ayaha kāraha then ayaha plus kamsaha and we get ayas kamsaha and finally ayaha plus kumbhāha and we get ayas kumbhāha in all these cases ayaha is the purvapada visarga is part of the purvapada it is not part of an indeclinable anabhiyajasya and it is followed by kāma, kamsa and kumbha and therefore all the conditions required for atakh kru kamik to apply are fulfilled and so this sutra applies itself and the output generated is ayas kāraha, ayas kāmaha, ayas kamsaha and ayas kumbhāha in all these four cases. Finally we have ayaha plus patram and the output generated is ayas patram and ayaha plus kusha and the output generated is ayas kusha. Finally ayaha plus karni and the output generated is ayas karni. Now let us look at the next sutra, A347, adhashirasi pade, adhashirasi pade. This sutra has got two padhas, adhashirasi and pade, adhashirasi is one slash two of adhas and shiras, adhashiras. So adhashiras is made up of adhash and shiras which indicates that adhash and shiras are the two padhas and of course this one slash two will be converted into six slash two which will mean part of adhash and shiras. Pade, pade is seven slash one of padha which means immediately before. The words continued are visharjani yasya that is in place of sahā, sahā is one slash one of sir which means sound sir and this is the substitute, samasai which means in the compound anuttarapadasthasya which means not a part of the uttarapada of the compound. So here we come to know that visharjani yasya is the substituent and sir is the substitute. This visharjani yasya has to be a part of adhash and shiras and the environment should be that of the word padha and then this visharjani yasya is substituted by sir. Here are the examples, adhas plus padham and then this sir is substituted by visharga and this visharga is substituted by sir and so we have adhashpadham as the finally derived form. Similarly, shiras plus padham and sir is substituted by a visharga which in its turn is substituted by sir following this particular sutra. Otherwise, this visharga could have been substituted by an upadbhānyya by the sutra kūpukha pāucha that does not happen and the visharga is substituted by sir and so we get shiras padham as the output generated. Similarly, let us look at this sutra, kāskādishu ca which refers to a bag of words and this bag of words is referred to as ākṛti gana, ākṛti gana is an open ended list which is kept open for inclusion in the course of time. So, this sutra has got two padhas, kāskādishu and ca. So, kāskādishu is 7 slash 3 of kāskādhi, so kāskādishu means in the words beginning with kāskā, there is a list of words which begin with kāskā and ca means end. So, visharjani yas here is 6 slash 3 which means in place of the visharjani here, saha is 1 slash 1 referring to the sound sir which means the substitute, kūpvoho is the 7 slash 2 of kupu which means immediately before kupu and anyatrasyam which means optionally. So, here we know that visharjani here is the substituent, sir is the substitute and if the word is placed in this particular list called kāskādhi then a visharjani here is substituted by sir when kū or pu follow. This substitution is optional, so the meaning of the sutra is the following and in the list of words beginning with kāskā, kāskādishu ca immediately before kū and kū, kupuho in place of a visharjani here, visharjani yas here substitutes saha optionally, anyatrasyam I repeat and in the list of words beginning with kāskā, kāskādishu ca immediately before kū and pu in place of a visharjani here substitutes optionally. So, if we have kaha plus kaha where this is the visharga followed by kū and this is part of this list and so this visharga gets substituted by sir and we get the finally derived form kāskā that is kāskaha similarly kautaha and kutaha so visharga is substituted by sir and we get the form kautas kutaha these are the outputs generated by this particular sutra. As we said before, this is an open-ended list. If there are other words in which a visharga is seen substituted by sir, all those words and all such words can be included in this list of words called kāskādi. To summarize, we studied a peculiar type of sandhi in the form of substitutions in place of a visharga. This is the feature of visharga sandhi. The substitutions that we studied are sir, sir, jivāmulīya and upadbhāṇīya. We also noted the zero substitute stated by a particular vārtika. These substitutions apply in various environments, sometimes very general and sometimes very specific. We also noted that by default meaning is not directly stated to be an input for these rules to apply and these substitutions to take place there are exceptions which prove this particular by default statement which is also a feature of sandhi in general. Now we study another chapter which is related to the visharga sandhi namely the swādi sandhi this we do in the next lecture. Thank you for your patience.


Hello, my name is Dr. Valerie Nicotakis-Woojack. I am an attending pediatrician at Hackensack Meridian Health. I started residency in 1987 at Columbia Presbyterian and then was offered a position on the faculty practice, began my position at the faculty practice in 1990 and have been a practicing pediatrician ever since then. I really look forward to going to work because I love working with the babies and the children. Babies and children are really our future. They are little bundles of potential. They are fresh and enthusiastic and it's just so fun and exciting to go to work each day when you know that that's what you're going to be doing. It's also amazing to watch them grow and develop and to become part of their families and it's just incredible to watch a child that you've followed since a newborn through all of their toddler years and their school age years and then through adolescence and then off to college and it's just an incredible experience to be part of all of it with them. Children are our future. If we can just really maximize their health and their development, the whole world is in a better place.


Rule number one, join the recession proof industry. Some industries are going downturn during recession, but some industries they provide very stable services regardless economics going up or down. For example the health care industry actually is hiring a lot of people right now and we have seen like Google partner manager join health tech companies as we're speaking. And educational companies also good one for you to check out right now because when people are laying off they think about how to upscale themselves so not going to get laid off again in the future. I would also check out some type of fintech companies for example Intuit.  Everybody pay taxes and you have to file taxes and so it's a resource everybody have to use regardless economical up or down. Like can subscribe and watch the next video for more product management tips.


Hey guys! We are here to film Cindy Utter's January 2017 art challenge. In this month's challenge, she challenged us to use coloring book pages on our art journals, and I thought that was a really interesting idea. I'm taking it a little bit out until I feel this time, not super far out, but I do have these little... I don't know what you call them. They're little coloring book bits and pieces. I got them at Tuesday morning quite a while ago, and I've kind of never done anything with them. They came in a big random assortment pack, and I thought I'd take a few of them, and I don't know if I'm even gonna color them in. I actually have some ideas for using them on the page, so I think that... I think I know what we're gonna do. We're gonna give it a shot and see what happens, and I'm gonna speed through the process. I'll be, of course, back at the end. Okay, so this is my take on Cindy's prompt for this month. Use your coloring book pages or elements from a coloring book as maybe a doodle prompt or doodle start on a journal page. That's what I did. That was the idea I had, especially if you have a lot of them laying around that aren't even colored in yet, which I do. And then I just pulled one element or in this case word out of what I'd created on the page and that I colored in and made stand out from the background. I love this page. It was simple, it was quick, it was easy, and it was a lot of fun. Turn up the music and just start doodling. Have fun. If you can't support my channel, please do that. You can go to the YouTube channel's main page and hit that fan funding button, or better yet go shop over in my Etsy shop. The link's in the description below. Above all, have a great day. Do something nice for yourself because you deserve it and I'll see you later. Bye, guys.


Hawaii night in Park Rapids as they hosted Crosby-Irenton Volleyball, first set Ranger strike first, Bailey Potter wins the joust after the errant pass. Still in the first set, Panthers lead 21-13, Caitlin Weaver does it herself, dumps it over, they take set one, switch sides, second set, the back set to Kaley Brightwesser, pounds it down, Park Rapids wins set two, 25-6, and they would cruise in this one in straight sets. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


So there's three things that we wanted to accomplish with the very early product realization tools we developed. One is help our scientists communicate their new discoveries and phenomena to soldiers better. The second thing was to engage soldiers to give us critical feedback that they like, what they don't like, what the application space they might see that we didn't think of could be. And the third thing is to vector the technology towards a capability that is likely going to be very successful and vector away from capabilities that are not going to have very much impact or exploit the technology strategically. Those are the three things we set out to accomplish and I think they might help other federal laboratories because we did have to adapt some of these tools which are commonly used in industry like minimum viable products to a federal laboratory. We operate differently and we accept that, you know. And so we exploit what our strengths are in this context. With this effort we wanted to be a little more innovative in our commercialization with the technology. We wanted to transfer it as well to our soldiers in a quicker way. To do that we worked across DEVCOM, our soldier center and Army Research Laboratory to move it from discovery to commercialization. The current challenge in DOD is we have a centralized procurement arrangement which really inhibits the ability to do minimum viable products and do very quick turns on technology maturation. Whereas best practices in industry are very adept at trying to meet early product needs. Industry innovation comes from early and frequent collaboration across the S&T ecosystem. Those partnerships are really important and things like the ARL regional offices, technology incubators and accelerators and other innovation hubs bring together people that can work together and then develop technologies that are important for the warfighter. The diversity of this team and the intensity over a summer enabled this minimum viable product to happen quickly and bring together a product at the end through that diversification of effort and the intensity. Mandel galvanic powder developed by Army Research Lab over the past several years was ideally suited for tactical applications where you have the ability to mix gray water or black water with this powder to generate hydrogen, which then in turn can be used by a hydrogen fuel cell to create power for tactical batteries, tactical radios, tactical communication devices. It was identified that that entire combination of fuel cell and reaction chamber was a little too large to fit in a backpack but really ideally suited for mounted or robotic applications that may be following the dismounted soldier in the squad associated with them. We were able to successfully develop a series of minimum viable products first the discovery phase then at the productization and systems level phase and we discovered different things cumulatively and working as a team of teams that information was critical and it was complete. It allowed us to make better decisions about how to vector this technology. The other thing I can't emphasize enough it was a team effort and involved the Army Research Lab working with the soldier center. It also involved working with soldiers from different parts of the Army and involved working with small companies and a university including a cadet Spencer Tess from the Worcester Poly Tech.


EFNN, The Tiger, Financial News Network, News Update. After what? Basil Chapman here on this Wednesday, 13th of July, Dow's down 342 points, so the CPI data coming out very high, 30,632 on the Dow. This is really a very important moment when I was actually interviewed with Tom yesterday. But I said, got to be a little careful with this particular pattern where it forms a rectangle within that you get an arch formation. You do not want to take out this left side low, in this case the low of the 5th of July of 30,000, or what was it, 30,355. Actually we went pretty low this morning, we went to 30,806, so 30,587. We'll see where we close today. There are going to be people that are wanting to buy, saying that the news CPI data is already history and that I'm looking at it that way. I think it is history, but I need to see action. I need to see the Dow get back to the 9 and 14 p and moving averages around about 31,000 and at least do that within the next couple of days without going down much further. Looking at the S&P, S&P right now is trading down 41 at 37,77, it too needs to hold certainly above the 37,40s between now and tomorrow, or maybe even now on Friday, and try its best to get back to the 38,30s level and that's going to be important. Q, Q, Q, they take a dive, but it's green right now, even though it's down almost three points at 283,30, the Invesco Trust Q, Q, Q, which is the NDX100 trading vehicle. The 9 is just crossed under the 14 period moving average. You have the whole day in which it needs to get back to try to stay green, the 9 above the 14 period moving average, you're looking at the IWM, also very weak down almost two at 169. This is going to be very interesting because gold is down just a little down two at 1723 and the dollar, I've got the dollar right now at an area where this is where you've got to be a little careful because it's in the leg E in the Chathamway methodology. Made a new recovery high today, a 105.58. I'm watching the explosive all on to take a little bit off it yesterday, but let's see what happens. Looking at the crude oil, crude oil is in fact just about unchanged and the TLT, I'll talk about them from the return for the Tiger Tricks, TLT is down a little funny here. I'll be back in a moment. I hope you can see. Check out my performance at the end of the day.