Hello, EnvoyCon. I'm Harvey Tuch, and I work at Google. I am the TL of the Envoy platform team. And today I'm going to be co-presenting with Mark Roth, a colleague of mine who leads the GRPC C++ efforts at Google. And we're going to be talking about the future of XDS, and in particular some of the changes around versioning and XDS transport, which are going to be landing over the coming year. This talk is going to be in two parts. The first part, we're going to look at XDS transport evolution, and the next part will be on versioning. So getting going with transport evolution. I want to start the talk by exploring some of the limitations in the XDS transports that exist today, and in particular, when we want to address some of the more sophisticated use cases that are coming down the pipe. But before I do so, I'd like to point out that actually the XDS transport is pretty remarkable in that it's brought huge improvements to how Envoy receives its configuration from control planes. Going back to 2017, all we had was polling-based rest for XDS delivery. And that had significant issues with performance on control planes, scalability, and also for latency of updates. And the versions XDS transport for essentially a version pump sub scheme, which we introduced since then, has brought about huge improvements. And it's working incredibly well today. And so we want to evolve this forward incrementally without breaking the world and without affecting anyone who's using it today, but at the same time, we want to address some of these limitations, which I'm going to talk about. So what are these limitations? So the first of these is that there's actually issues around cacheability of XDS. And so this impacts XDS as we want to scale it up to many, many different endpoints. And this could be, for example, in Envoy Mobile, as depicted on this slide, where we might have millions or tens or hundreds of millions of endpoints. We need a good story for how XDS resources can be distributed and found out. And there is this project on XDS relay, which I was just checking out, which basically is building the first steps of this. But to do this kind of caching and relay, there are issues. And let's go through some of these. The first is that the XDS resource names that exist today are just opaque strings. And they're not really a unique cache key because they don't include a bunch of useful contextual information, which includes things like node ID or metadata, which are actually provided in the XDS stream, but out of band with the XDS resource names. So if you're trying to cache just on XDS resource name, that's not sufficient. And as a result, even if you want to use something like traditional CDNs with the XDS HTTP transport, things don't work particularly well today. The next major sort of next-gen use case is federation. And this is when you want to have multiple control planes managing XDS. And today we have some limited support for having more than one control plane with Envoy. But it's at a very coarse granularity. And you can't, for example, delegate a single route configuration to a different server and this kind of thing. So in this world, we want to think about where we've got multiple XDS servers. There might be in different clusters. There might be in different clouds. There might be on-premise and so on. We want to be able to provide fine-grained delegation of authority over resources and failover between servers as resources as they come and go. And ultimately, what folks want to do probably, as they scale up, is disaggregate the control plane into a number of microservices, which is sort of form of federation supports. So today, as I mentioned before, we kind of lack some of this support. We have no explicit notion of what an authority is and sort of what a node in this graph that's where a drawing looks like. Resource names, not only they are opaque and uncashable, but they're also global. And there's no way to qualify them by specific authorities or have each authority manage its own resource namespace. There's no support for redirection or failover alternatives. And our existing conflict sources are pretty coarse-grained. OK. Then there is the issue of collections. So XDS today really doesn't have a great distinction between singleton and collection resources. So we would like there to be a better way of thinking about this. And a lot of the issues around this was surface, while GRPC and Marks had a great talk on GRPC adopting XDS, we're switching to XDS. And in this effort, it became clear that there's a lot of strangeness about the corner cases that XDS makes around collections, which we would like to resolve and make work better. And this really feeds into my final slide, which is that we have quite a bit of a curated technical data in XDS, which some of these things made sense at that time. But as we've gone to sort of stretch and test the parameters of XDS transport and its use, I became apparent that there really are issues here which need some mitigation. And then we want to do this to simplify control planes, make things easier, to implement, make it more robust and reliable. And there are all these surprises I mentioned before, the weird treatment of collections for LDS and XDS. There's also the fact that we have multiple wire protocols effectively now for the state of the world in Delta. We have this issue with cynical aliases, which we usually do especially with the HDS. So our proposal, and I have links to the proposal in the final slide of this talk, goes about systematically addressing all of these. And we're 100 things over now to Mark, who's gonna talk about one of the core concepts which really is fundamental to do this. And that is an idea of a structured resource name which takes the form of a URL and has this UDPA schema. So I'll have things over to Mark at this point. So the key to addressing the limitations that Harvey spoke about is this new naming scheme for XDS resources in which resource names are represented as a UDPA URI. So let's talk about the anatomy of a UDPA URI. The first part of the URI that's interesting is the authority. This indicates who's authoritative for the resource which is not necessarily the same as the XDS server that's used by the client. The client's bootstrap file will indicate what server or servers to use to access resources for a given authority which might or might not be the same as the actual name of the XDS server, right? And so an example of a case where you might want them to be different is in a large distributed infrastructure. If you've got for scalability reasons, you might have sort of a local caching XDS proxy in each data center that has clients and you might have those clients access the data through the local caching proxy even though the authority is still some centralized single point that is centralized across the entire global infrastructure. The authority acts as a global namespace for resource names. So if you have resources in, if you have an authority that has a bunch of resources in it, you can feel free to organize them however you want and you're not gonna have any naming conflicts with anything that anyone, any resources that anyone has created in other authorities. The authority is an optional part of the URI.  In the future, the authority might be used to authenticate the resources themselves using some sort of signing mechanism. That's not something we actually have today, but it's a possible future direction that we could go in here. The next part of the URI is the resource type, which is listener cluster route configuration, that sort of thing. The ID is essentially the path part of the URI. It can be any string that you want. It's totally up to you as an authority owner as to how you wanna lay out your resource names. Context params are similar to query params in an HTTP URI. They provide a way to serve multiple variants of the same resource and we'll talk more about that in a minute. And the final part of the URI is the directive. This is similar to the fragment in an HTTP URI. It's a directive for how the client should interpret or use some part of the resource, but it's never actually sent to the server. It's only interpreted on the client. Next slide, please. So here are some examples of UDPA URIs. First, we have an example of a fairly basic URI. It's got authority xds.example.com. And so Envoy would look in its bootstrap file to determine which server to query for this authority. The resource type here is listener and the ID is service mesh slash sidecar. And again, this can be any path that you want. This is just sort of one arbitrary example of what you could put in here. The second example shows the use of context params. In this case, the context params is node type equals front end. Note that the context params are actually part of the resource name. They're part of the unique identity of the resource. So from the xds perspective, two resource names that vary only by content params. For example, you had another one that was node type equals back end. From the xds perspective, that's actually a different resource. From the human perspective, in practice, usually if you have a resource that varies only based on the context params, that's usually two variants of the same basic resource. It's telling the client to do the same thing, but in slightly different ways for slightly different scenarios. Context params do actually come from different places, not just from the UI, the URI. There are some additional sources of params that can get added on when requests are made to the xds server, excuse me. And we'll talk more about that in a minute. The final example here shows use of a directive. In this case, there's a directive called ALT, which specifies a fallback resource. So when the primary resource doesn't exist or the server can't be reached, the client can sort of know to fall back to this alternative resource. Next slide. All right, so let's talk more about context parameters. As mentioned earlier, the purpose is to allow servers to provide multiple variants of the same resource. This is the key to making all kinds of information a first class part of the cache key for resources. Context params come from multiple places, so we'll talk about these in order. First, there are node identity parameters, which can be populated from the node message in the bootstrap file. These are prefixed with the string udpa.node. This is a key part of replacing the wildcard queries in LDS and CDS that Harvey mentioned earlier. The idea here is to use these context params to encode things that used to live in the node message only. So instead of the server looking at the client's node identity to decide which resources to return, the client can explicitly ask for what it wants in a flexible way. Next, the second source of context parameters are the ones encoded in the URI themselves. So this is like the example I showed earlier of node type equals front end. You can have any prefix. There's no restrictions on what the content is. And it is applied after the node identity params, so it can actually override them. So you could actually specify something in the URI that's udpa.node.something and it would override whatever comes from the bootstrap file. Next is the third source of context params is client features. These use the prefix udpa.client feature. These are not user controlled. They're added automatically by the implementation. Unlike the client features that exist on the node message today, these client features are resource specific. So a client feature that is specific to, for example, EDS will only be added to requests for EDS resources. And this prevents unnecessarily polluting caches with duplicate copies of the same resource, which is what would occur if the same CDS resource was accessed by two different clients that had different values for a client feature that is relevant only to EDS, right? You wouldn't wanna have to make two copies of that. So this avoids that. Next, the final source of context parameters is per resource type attributes. These use the prefix udpa.resource. Just like client features, these are not user defined. They're added automatically by the implementation and they're defined for each resource type as needed. The one concrete example here is for VHDS, we plan to use this to allow the client to request the specific virtual host that the client wants. So this would be the thing that would replace that aliases mechanism that Harvey mentioned earlier. Next slide. Now, another thing that we're introducing is first class support for collections. There are two types of collections, list collections and glob collections. A list collection is a resource that contains a collection of resources of a particular type. The collection resource itself will have its own type. So for example, a resource of type listener collection is a resource that contains a collection of listeners. A resource of type cluster collection is a resource that contains a collection of clusters. As indicated by those examples, this is another key part of replacing the wildcard queries for LDS and CDS. Now each resource in a collection can be either an inlined resource or a UDP-A-U-R-I referring to another resource which the client must fetch separately. So here in this example, we have a listener collection resource with name xs.example.com, listener collection, sidecar one, just an arbitrary name that, you know, as far as the ID goes anyway, just an arbitrary name that I made it for the example. And in this case, the collection contains three resources. There's one inline listener for Part 80. There's another inline listener for Part 443. And then there's a reference to an external listener resource which the client would have to go and fetch separately. Note that for the inline resources, there are names that are sort of attached to them. These names can be used in a entry directive on the client to refer to one of the inline resources in the collection. Next slide. The other type of collections that we're gonna support are glob collections. These are an alternative to list collections for cases that need additional scalability. So the way this works is the client requests a resource where the last component of the ID is star, and it works basically like a simple shell glob pattern. The server will return all resources in this quote unquote directory. The client will then know what resources in the response match this request by virtue of them all being in this requested directory. So it's sort of a path prefix match sort of thing. The reason that this is more scalable than a list collection is that in the case of a list collection, let's say you have a list collection with a whole bunch of inline entries and any one of them changes, you have to resend the entire list collection. But in a case like, so one of the limitations we've had in EDS is that EDS has all of the endpoints listed in it. And we know that there are cases where there are really large numbers of endpoints and then one of them changes and you have to resend the whole thing which uses a lot of bandwidth and is not really the way we want things to work. So with glob collections, we're going to be able to build something that we're gonna call LEDS, the Locality Endpoint Discovery Service, which will be based on glob collections and will allow each individual endpoint to be updated to the client independently of each other. Next slide. Next, let's talk about different ways that you can use UDPA URIs to address various Federation scenarios. There are three different ways for a resource from one authority to sort of delegate to resources in another authority. First, the delegation can happen at the normal handoff point between resources. We know that listener resources can tell the client what route configuration to request via RDS. So that RDS resource can actually be in a different resource, sorry, in a different authority than the listener resource was. So that's one way of sort of handing off. Next, the second type of authority delegation is redirection. So this is similar to an HTTP redirect. The client will request a specific resource and the server then tells it to use a different resource instead and that resource can be in a different authority. So this is a way for one authority to sort of say, I wanna delegate this particular resource to some other authority. Next, so the final form of authority delegation is having a list collection that includes references to resources in a different authority. So in this example, we have a listener collection in the authority xds.example.com but it's redirecting inside of it, it's referencing inside of it, resources in other.com and mumble.com. Next slide, please. Now, a different type of authority handoff is a failover. This is where we use that alt directive that we talked about earlier, but in this case, the alt directive points to a resource in a different authority than the original resource was. This sort of thing can be useful in cases where you wanna like fall back to a different configuration from a local xds server when the remote xds server is not reachable. Next slide. And let me hand back to Harvey at this point. Thanks, Mac. Okay. So in summary, like the real win here is we've got the ability to cash xds resources, we can delegate and failover for authorities, we've got better support for collections and we've eliminated a bunch of technical debt and we're now ready to go, I think for things like federations. So this is like all pretty exciting. Now, in terms of the implementation roadmap, we've just started to do this and we have the first three, I guess items in that roadmap underway, but at very early stages. We're planning Q4 and landing probably one through four at least in this list. And then I think once we've landed that, which is basically support for the core UDPA URLs and the glob collections, the rest of the implementation to be added somewhat incrementally, it's sort of distributed amongst other folks who are interested in contributing, but this is the current plan and we'll be working on this in the coming months. In the second part of this talk, I'm kind of looking at XTS versioning and I know this has been a source of considerable friction in the ongoing community in the past year. So I'm hoping that this plan that I present has sort of reflected some of the feedback that we've received and is providing us path forward to achieving the best properties of versioning while still being thoughtful and mindful of the costs that control point operators bear when implementing some of these schemes. So let's just start with a recap of versioning in Envoy and you know, you may even ask, this takes us back to last year's Envoy card, but like one of the first things to ask is like, why are we even doing versioning? And the basic reason is that we were previously had just a single unversion API, which people would randomly remove fields from, which doesn't work as a stable API. If you're a control plane operator, if you're implementing Envoy as an XTS client, and you're not Envoy XTS as a, if you're an XTS client and you're not Envoy, these things are problematic features and we really needed to have a pretty serious strategy for not breaking the API. So we introduced major versioning, which would actually allow us to, you know, turn down and tire APIs and bring up new ones. And we were planning on doing this initially on a yearly cadence with V2 in 2019, which was the Extends API, V3 in 2020, which we did roll out and deprecate V2. And then in 2021, we're planning on introducing V4, removing V2, et cetera, and one per year. And that was problematic. We decided to stop the clock right there because it turned out that there's just too much control plane operator developer pay, which I'll go into. I have a mini retrospective in the next few slides, but that's essentially where the situation we're in today. We're not getting rid of major versions, but we're not gonna issue one per year. And we're gonna come up with a more incremental approach towards versioning, which I'll explore in the next few slides. So a quick retrospective, the good, the bad, the ugly, while good things is major versioning did solve our breaking change problem within major versions. We built sophisticated tooling in Envoy to automate most of the upgrades. So it was a lot smoother than it would have been if we'd done it manually. I mean, there were a bunch of technical improvements in V3 over V2, which were made possible by the ability to break the API over the version bug. What went badly? Well, we had a fair bit of code sharing. That's not too bad, though. We didn't finish basal integration. So there's this generated API shadow thing that you may be familiar with. If you're an Envoy developer and you need to un-fix format for, we didn't have all parts of V3 ready to go on day zero and there's some complexity around handling versioning in Envoy. Now, the really ugly parts are control playing developers and operators had a lot of pain and they didn't have the same tooling in libraries that we had in Envoy. There was a lot of confusion. They weren't ready on day zero for upgrades and documentation. And some of this, I would say, reflected the lack of interest in control playing operators and what we were doing while we were putting together this proposal and socializing the Envoy community. But some of it we probably should have been better prepared for and ready to go at day zero. There was also a performance overheads of upgrading resources from V2 to V3 inside of Envoy and internally operates a V3 and there's quite a few people and there's a lot of conflation over what is a transport and a resource version and so on amongst the Envoy community and confusion as a result. Okay, so what's the actual new plan? Well, we're gonna slow down major versions. We're not gonna not do a major version in the future we're not gonna do one until the benefit really outweighs their identified costs and there's been a useful learning experience to capture that. We're gonna switch to a scheme called minor and patch versioning to make things more incremental. And so, you know, borrowing from the sort of the semantic versioning terminology or this isn't semantic versioning. Major versions are gonna be when we wanna break the world, they happen rarely and we can actually remove fields from the API. Minor versions are gonna occur once per year and what's gonna occur at these clock ticks is nothing's gonna be removed from the API but XDS clients can remove support for deprecated features at these clock ticks and finally we'll have patch versioning which will basically change in every API change and this will let you know exactly what version of the API a client is at which is useful for feature discovery. Okay, so Matt's got a very detailed plan of record around this and I recommend checking this out if you're interested. There was the details and Adi, who's a Googler who is gonna be working on this in Q4 he's gonna be looking at things like how do we do version negotiation and feature negotiation which are really important to coordinating XDS clients and control planes in this world. Okay, now what are the implications? Well, if you're a control plane operator you're gonna have to state a policy and support one around which minor versions you support. If you're a control plane developer you need to support a range of minor versions and support negotiation of features and version. XDS client developers need to pretty much do the same and anyone who wants to is willing to put in the work of being an API shepherd can join in the process of deciding what gets deprecated and when to help guide these minor version changes. Okay, so the new version of a roadmap kind of looks like the first two points of 2019, 2020 are the same. Next year on Q1 we're kind of introducing 3.1.0 minor version and we will remove V2. That is going away. So if you are still alive V2 you should be moving to V3 because that is going from the onboard code base. And then each year from then on we're gonna start introducing minor versions and deprecating things which are more than at least a year which I've had deprecations of at least a year.  If you download the slides and click through them you can follow up on them. At this point I think we're done with the presentation part of this talk and we're happy to take questions. Thank you. Hello. All right, so should we tackle the one about the collections including collections? Like I think that's something we could support. I'm not sure. We'd have to look at the use cases and make sure there's no implications but it seems on just first thinking about it it sort of seems like we could do that. Yeah, for this collection is sure. I mean, we already have the XDS clients going back and forth to the server multiple times when fetching a collection. And so this is essentially just adding a bit of hierarchy there. So there's no reason we can't support it. I guess we would just need to understand the use case for that first because it's, I mean, like looking at the existing proposal we already have a fair bit of conceptual complexity around the collections around where these list collections and then we also need these clock collections for performance and scalability. So ideally we have, we land these first and then we add some sort of notion of nested collections, yeah. Yeah. I mean, I think the nice thing about it is that it wouldn't, you know, this would sort of just be a change to the data model for list collections because list collections are just a resource, right? So it doesn't really have any transport protocol implications, which is nice. But yeah, I agree. Let's do the basic stuff first. And then, you know, we can see where we go from there. Okay. Yeah. I think that makes sense. I think so we had another question around how are we managing trust amongst authorities and things like SPIFI and so on. So right now, I think this actually ties into another sort of related concern that is how do you actually like sign and attest to the integrity of XDS resources. That doesn't really exist today, but it seems that at the resource level, it would make sense to introduce some sort of notion of signing. So you can have an idea of who was responsible for producing this resource and is it in the actual original, you know, intended condition. And tied into that would then be some idea of like what is an authority and how do we actually identify them using, you know, certs and that kind of thing. So I think like we have an idea that this is where we want to head and there's various points in the API where it makes sense. If you look at the proposal under the conflict sources, essentially what identifies and maps an abstract idea of an authority down to the concrete transport, it seems that would be a good place to also attach certificate information as well. And the XDS resource objects themselves are now in a wrapper object and that is where essentially the signature would go. But this scheme has not been fully designed yet. We're at the stage in which we understand how we would probably go about building this. And I think like anyone's actually interested in helping to drive that will be very interesting because I think that's a really important part of making this work for real in a situation where you have mutually untrusting parties and that kind of thing. Yeah, I think one of the challenges with the whole signing thing that we're gonna have to think about when we really start looking at signing in detail is that sort of thing I think could work fairly well if what we're signing is the XDS resources themselves. But if you've got some sort of control plane infrastructure behind the management server that what users actually configure is not that form but a different form and then it gets converted then there's this whole chain of trust thing through that whole workflow that makes things a little bit more complicated depending on how much you're mutating the data. I guess back to the original point on this idea like a disaggregated control plane. So today control planes are like just a single or monolithic so it's just probably fine while they're simple but you can think about breaking up the control plane and even amongst those who let's say we're fronting their control plane with go control plane they probably have a pretty sophisticated configuration pipeline behind that which runs in a different servers and that kind of thing. Okay, I think we have one minute if there are any other questions or we can end the minute back to the next session. Once, twice, twice. Okay. Thank you. Thank you. Thank you.


Attention Bear Valley residents. This is a community notification of a new sexually violent predator in your area. Please stay tuned to the following short program for more information. Hi I'm technician Ron Hackett with the Denver Police Department. The sex offender registration and compliance unit at DPD is responsible for the registration monitoring and tracking of all registered sex offenders and sexually violent predators who live in the city and county of Denver. Here's a brief history of sex offender legislation in Colorado. Our state laws trickle down from federal government mandates. In 1994 we had the Jacob Wetterling Act which mandated that states would establish a sex offender list. Magans law of 1996 said that the public would have access to those sex offender registration lists. The Pam Litchner Act of 1996 stated that some offenders might have to have lifetime registrations. In the Adam Walsh Act of 2006 unified sex offender laws across a country. In Colorado the legislature has determined that sexually violent predators by definition pose a higher risk to the community at large and therefore mandated that upon their release from the Department of Corrections the community must be notified. Sex offender notification in Colorado happens in two ways. The first is passive and ongoing through the sex offender registration process which is a list maintained by local police department. The second way is active via community notification for those offenders determined to be sexually violent predators by the courts or by the parole board. Most sex offenders in Colorado are supervised by the criminal justice system in our communities. Most sex offenders engage in crossover behavior which means they may have been arrested for one type of crime but be apt to commit another.  There is no typical sex offender but all tend to be deceptive, manipulative and secretive. 80 to 93% of sex offenses are committed by someone known to the victim. Sexual deviancy begins in mid to late adolescence. Sex offenses are not impulsive.  The community has a vested interest in helping offenders to be successfully managed in the community. Sex offenders have the same need for housing and employment as any other citizen.  There are approximately 16,500 registered sex offenders in the state of Colorado. About 65% of convicted sex offenders are placed in the community on probation. The remainder are in the Department of Corrections or Community Corrections. Offenders may be caught for one type of offense but be at a high risk to commit another type. Crime of conviction is only one indicator of risk.  The offender's residents must be verified quarterly by the Denver Police Department. The full sex offender registration list is available by calling the Denver Police Department Identification Bureau at<PHONE_NUMBER>. Convicted felons and those with multiple convictions are posted online at denvergov.org slash police.   Now, here's a look at the newest sexually violent predator living in Denver. Here's an overview of the registered sex offenders currently living in Denver. There are 2,636 total living within city limits. In Denver Police District 4, there are 481. Precinct 423 has 129 registered sex offenders. Of those, 92 have felony convictions and 37 have misdemeanor convictions. Joseph Arthur Mock Jr. is a sexually violent predator currently living in Denver. He's 62 years old and was born on March 30, 1959.  He's currently living at 2715 South J Street in the Bear Valley neighborhood of Denver. Schools located within one mile of this offender include John F. Kennedy High School at 2855 South Lamar Street, Summit Academy Middle School and High School at 5590 West Evans Avenue, Denver School of Science and Technology Henry Middle School and Bear Valley International School, both at 3,005 South Golden Way, Trailer Academy at 2,900 South Ivan Way, Zion Evangelical Lutheran School at 2,600 South Wadsworth Boulevard, Notre Dame Catholic School at 2,165 South Zenovia Street. Parks located within one mile of this offender include Bates and Hobart Park, Bear Creek Park, Lakewood Estates Park. Bus routes located within one mile of this offender include Route 30 West Dartmouth Avenue in South Lamar Street and West Dartmouth Avenue in South Ingalls Way. Route 51 South Sheridan Boulevard and West Yale Avenue. Route 76 South Wadsworth Boulevard and West Yale Avenue. A brief history of charges against this offender. Sexual assault on a child. He's currently on parole and registered with the Denver Police Department on April 13, 2021 to 2715 South J Street in the Bear Valley neighborhood of Denver. Past charges against this offender include menacing, intent to deliver marijuana. Joseph Arthur Mock Jr. has been determined as sexually violent predator after meeting the following criteria. Criteria one, age 18 or older on the date of the offense or under 18 and tried as an adult. The offender was age 40 at the time of the offense. Criteria two, the crime must have been committed honor after July 1, 1997 and convicted honor after July 1, 1999.  The offender was convicted on December 9, 1999 for sexual assault on a child. Criteria three, the relationship to the victim was one of the following. Victim was a stranger to the offender or the offender established or promoted a relationship with the victim primarily for the purpose of sexual victimization. The victim was a 14 year old female. The offender was known to the victim. Criteria four, positive results are the passing of a risk assessment instrument administered by probation parole staff and a qualified treatment evaluator. Positive results include an assessment for the presence of a mental abnormality, a level of denial regarding the offense, treatment appropriateness and motivation, presence of sexual deviant interests. The offender was evaluated by the Colorado State Board of Parole with positive results, determining him to be a sexually violent predator.


What is the file picker? In this video we're going to explore Moodle's file picker and how you can use it. You might see the file picker if you upload a file using the activity chooser or if you're in the text editor and want to add an image through the image icon or a media file such as sound or video by clicking the Moodle media icon. If we click to add a file, on the next screen when we scroll down to content we can access the file picker by clicking the add button. What you see on the left side are links which are known as repositories and each of these are places where you can retrieve files to display on your course. The one you'll use most often is upload a file. This will allow you to access your documents from your computer or USB drive. Server files are the other files in other courses which you have access to as a teacher. So for instance if you're teaching grade 1 English in one course and you wanted to add a file that you had used in grade 2 English, a different course you go to server files to locate it. Recent files shows you the last few files that you've uploaded and it's context sensitive. This means that Moodle knows if you want to upload an image through the image icon it will only show you images. If you want to upload a sound file using the media icon it will only show you media files. Private files allows you to retrieve files you have previously uploaded in your personal private file space which we'll look at in a separate video. URL downloader allows you to add a web link and it will download for you the images on that web page. Other links or repositories will appear according to what your administrator has enabled. So in this site for example you could go to wikimedia if you wanted to find an image which you could search for with a particular size. You could retrieve files from your Google Drive, Dropbox or Microsoft OneDrive account. The files in the file picker can be displayed in three different ways and if we click recent files you can see how this works. If you look at the far right files are displayed like a tree. The middle button displays them with details of their size, type when they were last modified and the third button shows them as icons displaying what type of file they are. So for instance we can easily see that this is a PDF file and this is a Word document.


So, this is a passage from the Rastarangini, where two women are comparing notes on how many compliments they receive from their men, and the first one is like, oh my guy thinks I'm the most beautiful woman he's ever seen.  Does your man give you as many compliments?   My lover has never seen or thought of or even dreamt of another woman. Who is he to compare me with? You know what, great response. I love it. I love the self-confidence that goes with it. But it also gets me thinking that we as women have always been taught to compete with each other. We've never been taught how to stand up for each other, but what's worse? We compete over the men. We grade ourselves according to how our men treat us, and that becomes like our status. And you know exactly what I mean. The woman whose husband or boyfriend supports her or stands up for her, we treat her with more respect. And the woman who has to stand up for herself, instead of seeing her as stronger, as worthier, we give her less respect. You know, as women, we have such an incredible capacity for loyalty that if we were to stand together, we would be undefeatable. And I guess maybe that's why we've been taught to compete with each other, because otherwise we'd just be too powerful. It's time to change the story. Next time you want to get competitive with another woman, especially over a man, hold out your hand to her instead. Think of how much more in the long run her friendship will mean to you, because we all know exactly how important women are in our lives. Make the change, because frankly, you're the only one who can.


Hi everybody it's Sam at Mixed Up Crowd, thank you for watching today. I'm going to be making a small desk calendar, now I made one last year which was an A4 size and I loved it, I used it all the time but I did find it was a bit too big to have on my desk, so this is a smaller version. Now this is already a store brought one which I purchased from Muji which is a Japanese store but I'll share all the links. You can buy inexpensive calendars from many many stores so you might have some that you've got for Christmas that you've got lying around so I wanted to make this look a bit more fun and eye-catching it was very dull. So I've pulled all the actual you know month pages out and I'm just going now and cutting them down and my final size is six and three eighths of an inch by five and a quarter, sorry six and three quarters by five and a quarter and you can see them just you know cut them all down so they're all the same size. Then I'm bringing in the eight by eight forever free pack and I use the full eight by eight sheet, I don't lose any of that print and I don't cut into it at all so you can see there I'm just playing around just to see how that's going to look. Now rather than just sticking them directly onto the paper which looks nice those sheets although they're thick they did show through some of the darker images on the papers so I end up going along and you can see now matting them on a matching just plain it was just copy paper but just coloured copy paper. You can see now I'm just sticking them down just giving it a small little frame so you just want to make you know cut this just slightly larger than that actual month sheet there that I've got month calendar sorry and then just trim down all of the sizes all of the sizes I'm not talking right at all today all of the sides so you get a nice equal border and now you can see when I sit that down against that eight by eight paper it just yeah just looks nice so again sticking that one down and then I just go through all of my months and do that on every single one so I pulled out 12 different decorative papers from that forever free 12 by 12 and eight by eight paper pack and yeah it was just a nice way to use up papers you might have a lot lying around and you get to appreciate all the prints for the next year so I thought it was quite nice you can see that I've done all of mine with just different backgrounds and and mats and stuff so looks really good so next I am just going to work out where I want to put my ring binder ring binders binder hoops these are one and a half inches and again I'll share all the links in my blog so I'm just looking across there and I end up coming in at two and a quarter inches from both sides so two and a quarter in there from the right and two and a quarter in from the left and I come down three quarters of an inch and just roughly see that with the ruler but three quarters of an inch down I've got the little dot there that I've just created with my biro and then I'm just going to go along and hole punch over those little markers and then rather than measuring every single one all you got to do is grab the next one line it up with the one that you've already hole punched and you're just basically tracing those holes then pop that one to one side and then use that one to do the next one and just work through that way and it's much much easier so now you can see I'm just going through just a check that they all line up nicely just putting those rings through and there you can see it's starting to come together so I'm really pleased so far next I want to just make sure it's nice and strong because it's obviously going to be used for the next year so I'm just using some white eyelets and I've got my pliers there and I'm just squashing them on and it's just a night it just finishes the product so I mean if you did want to sell these or give them as a nice gift to a friend by doing these little extras I think just makes it look a little bit more special so I just go through now and do all of those and it just thickens the whole top part and you can see they're the white against all those patterns looks really nice and yeah it was all coming together really nicely so now I'm going to make the base so this is a piece of eight by a four length so it's eleven and three quarters eleven and five eights and you're basically going to score it eight then you're going to score it nine and a half and then you're going to score it eleven okay then you will need to fold it over so you've got a mountain then a valley and then a mountain so you're basically having that shape there okay then you'll need another piece which is eight by eight and a half and you're going to score eight and just burnish over that fold and that's what we're going to use to connect them together and this is going to make us stand so it's a stand that's just like the one that I shot brought so I've just made it bigger so along the bottom of that one with the mountain and valley folds you just want to add some glue to that it's almost like a half inch tab and stick it to the end where you don't have that folded part on that other piece of cardstock so you can see there I'm just sticking it down so that's creating the base which you can see there and then that tab at the top now on that other piece that we scored and cut you just again want to pop your glue along that half inch tab and then fold in the bottom and fold the whole thing down so you've got your two eight by eight pieces kind of you know marrying up perfectly together and there's your stand really really easy to do and this is very similar to the stand that I made last year and I will link in that calendar because again I did really like that one now I want to create the holes again so I'm just tracing over the ones that we'd already done that way you know that you're going to get it exactly the same and then with a little bit more force because you've got to go through two bits this is strong cardstock this is 300 gsm so it's really strong to work as a stand and then just start popping them all back on again that is it it's finished it's such a quick very easy thing to do you just need obviously those ring binders most of the stuff is from your stash you don't have to put the eyelets on there if you don't want to you can see now just finishing it off fasten them all and there is my 2019 desk calendar that honestly I took me about an hour just because I had to go through and cut you know all the paper the mats really that was probably the more time consuming part because all the papers were eight by eight so it just comes straight from the pack so it was really really quick and I love it so hopefully I've inspired you it's not too late to do these I think they look great you can see there it's just a nice way to appreciate I say before you get all these lovely papers in paper packs and sometimes don't like to cut into them this is another nice project to just enjoy them you know see them for what they are and each month you're obviously going to have a different one you can obviously specialise it to the months have Halloween theme papers valentine's themed Christmas themed I haven't I just wanted it to just be just nice and bright for 2019 so yeah that's my this year's desk calendar so a little bit smaller but I think this one's going to work a bit better for me hope you've enjoyed it and if you have please give me a thumbs up and subscribe to my channel to see more thanks for watching bye


My name's Hailey Bell. I'm the founder of women riders world relay We wanted to start with a bit of background about what we're doing and why we all look like Across the world looking to unite women and showcase what women can do on a motorcycle You know, we aren't timid We can ride Hello! Welcome! Thank you! She did everything that is the preventive service Okie dokie! Good morning! If that party has to reach its destination always We're from Morelia and we're going to Oaxaca to deliver it over there Ready to go, any state, I'll tell you Ah, I got the mission Exactly My story, I know it's very common Like all the girls, you grow up in a family where they tell you You have to learn how to cook for when you get married and you have a husband and you learn how to cook You grow up with a chip that tells you what you have to do The guy with whom I didn't see my boyfriend for a while He taught me how to ride on a motorcycle This relationship ends And I said, now I'm not going to do anything because I'm not with him anymore It's six o'clock in the morning Sleep, I want to sleep I saw the amateurs They look like you, so cute It's time to get out of here, let's go all the way to our formation Especially first, your safety When you sit in the motorcycles, in the ride We'll have to take care of our speed I think there's an energy in each family That the ancestors are wanting them to keep going Experimenting and breaking certain paradigms And I think Kareana came to break all those paradigms I'm super excited to be a part of the U.S. team Kareana Baton I'm gonna follow you You're gonna follow me? I'll follow you Let me talk to him I haven't done that yet, and I need to do that I'm still waiting to get the final This is what it is So until we get that, I'm optimistic You know what I'm saying? Nobody has an expiration date I'm kind of a huckstable kid I grew up in a middle-class family I think people gave me the dream of being a lawyer But it was never really my dream You can be great at doing something But if it's not your passion, you're just wasting time I am very happy that I'm self-employed You know, I don't have a big house That's not wealth to me Being able to go to the beach on a Wednesday At three o'clock and not have to worry about Whether or not I'm taking too long of a lunch That's wealth Best part is yet to come We still gotta go to Vegas This beautifully hand-carved case Is a beautifully hand-carved baton And we've been through some adventures With this thing, haven't we? We've been through tropical monsoons We've had bikes down, we've had riders down We've had tears, we've had laughter We've had everything in between Give yourselves a massive round of applause There's a couple different ways to go We need fuel, stop Twenty-two Road Grand Junction Cool Marcia, are you freezing yet? I know Cool, cool, cool Hey, Daddy, how are you feeling? Yeah I wanted to check with you I knew that there was still some pending information Okay That's for the lunch that's on your lungs Yeah Okay But you're not in any pain, are you okay? I love you too, Daddy Super cool Morning, ladies I've got an extra jacket liner If you'd like to use it You know what? I'm a California girl So 27 degrees, yeah That's tough, man Portia, you're starting out lead Do you have the baton? I do So you guys ready to settle up? Get on the road It's been such a go A lot of conversations While I'm on the bike to my dad Making sure he's okay I don't know when those conversations are going to end But if I sit and I ride Now I'm not afraid Katie brings us the gift of music Jerry gives the gift of engineering Maul gives the gift of food Maul feeds us What gift do you bring, mommy? Give the gift of love I feel like paying my nails, I'm paying my debt Paying to work, coming home, taking Caitlyn Extramudals, coming back I'll be Katie with her home I'm always busy When I was 40 I changed careers Got a degree Started riding a bike People, because like, they see me Menopause, what's going on with you, I said I don't care what society feels I'm scared I'm not confident But if I'm not a good example to Caitlyn And I don't want to be scared of stuff So fake it No matter how many women you ride with Riding is a single, solitary action But when you stop And you get off the bike And that's where it becomes community again Honest to God, you can leave me It's perfect Nah, nah, nah, we're too close Better than me catching up We're too close to the end And we're not going to leave you by yourself On a dark road I got some good music going We're going to take our time And we'll get there, okay? I got it Oh, youngest warrior To ride on my bike For the past eight years Mom would always say Not today, not today I think my mom is always brave and courageous Because she knew we were watching And she didn't want us to be scared of anything But maybe she was scared But she just didn't show But he's just holding our fragileness together And we're all trying to be strong For the next person Most people thought I was an 11-year-old It was a simple science fair idea But I knew that if I could get this to work I could help to never see another Flint water crisis again


What's good Josh boros back again with another video, so I had to make this video man I didn't plan on Recording this video. I plan on potentially recording another reaction. I had lined up, but this is literally the topic of Tonight is probably gonna be the topic for the next few days man for those who didn't see John Moxley versus a CM punk on AEW Dynamite for the unification of the AEW World Heavyweight Championship You didn't miss much because the match was only like three minutes long Shout out to everyone that was with me watching live on on YouTube I was doing live stream reaction and shout out to everyone that was in the chat But I'm so confused and perplexed on the decision that they made For this match to happen and for it to go the way that it did now. I want to put this out there I'm all for Long-term booking interesting storytelling and I'm all for giving time for a story to grow and develop But I am not for the story that's being told Being a detriment to either a match of this caliber This is not just a regular championship match This is without a doubt in my mind and I think a lot of people's mind potentially the biggest if not the biggest AEW World Heavyweight Championship match because this is a unification of the titles interim champion versus the actual champion Coming together to see who's gonna be the undisputed AEW World Heavyweight Champion This is not something that you take lightly if you're trying to build up this company now when they Initially moved it up from instead of it being at all out to moving it up to this week I was very confused on that but I figured it's probably storyline wise either way It had me excited to want to see the show No, I got a stream that John Mosley versus Sam punk on free TV I know there's gonna be some commercial breaks involved probably but it's just a unification match and that promo they had last week Was fantastic granted. This is only one week of build But hey, I think people were just gonna be excited to see it just off the strength of them going at it man, I was I was looking forward to it and Then we get to the show And it was announced that it was gonna be at the top of the eight o'clock hour Although I want to say it was the nine o'clock hour. I want to say I'm not sure No, it was the eight o'clock hour for my time zone It was the eight o'clock hours gonna be at the top of the eight o'clock hour and I'm like that can't be right This is the main event. This this is a main event match This is not a match you have in the middle of a free television show Hell, you don't have this match on free television. You have this at the pay-per-view, but you having this at the middle of the show I'm like, oh Something's not right about that.  It's gonna be entertaining. I'm willing to bet they're gonna put on a great show Well, and to give them a benefit of the doubt that this match is gonna be one of the matches that we talk about hopefully all Through the rest of the week, right? They're doing their intros or what not Everybody's hyped up Obviously John boxes is gonna get more of a baby face reaction. He was in his home state See I'm punk definitely was getting his booze, you know Seem fine walking out there fine, whatever match begins There have there, you know, you know, it starts off as I expected or what not? Big fight atmosphere next thing I know see a punk goes for a kick But he ends up grabbing his other leg leg that he kicked with wasn't I believe the injured leg I believe the leg that he was planted on was the leg that he went to grab as it as an injury, obviously That's more storyline storyline driven. He was selling that so I kind of figured that and then all of a sudden John Moxley just goes into attack mode and Within a few minutes John Moxley dispatches see him punk sound like he was nothing now I get it They're going with the injury storyline here But once again, I think you could have possibly drawn that out and make that better in a sense because People have been wanting to see this match. I was excited about this match only for me to be Involved in the match for three minutes three minutes. I got you for three minutes three minutes of play time Let me know comment down below. Let me know what movie is that from oh My god, bro. I it just didn't make any sense, bro Like I am so confused by that for the simple fact of this was Promoted as easily the biggest match in a WWE history only To last for three minutes because I trying to still tell a better story a bigger story What are we doing? I'm sorry. I just that don't make sense to me. It they don't I know people are probably gonna be like you may I'll just be patient. That just doesn't make sense. That doesn't make sense at all See him punk legit got squashed Sometimes we we use that as hyperbole. Oh, someone got squashed. No, he got squashed now granted do the injury But no whether never he really got squashed. He barely got any offense Now I get it they were selling it. He's walking up the ramp with the help of officials He's looking back seeing John Moxley celebrate. That's a good image. That's that's a good visual of him turning heel I'm for it But you're telling me we can only get a three-minute match unless He was actually legit injured and couldn't really go that long in a match from to begin with so they cut the match short but even then That literally brought it for me when I think of the summer of punk and how he got ruined because of the injury That literally kind of just made everything that see him punk went through everything that he achieved so far in AEW It meant to me. It made him mean a whole lot less Because he ended up going against the guy that was front-running AEW when it started He ended up going against him and got sent to the gulags like that It's again because of a storyline injury, but it just it just made it feel like see him punk's rise to the title Wasn't it? It really went nowhere. It went nowhere after Adam hangman page Got injured and then that was it and got got squashed by John Moxley That I don't know man I'm just I'm not feeling this booking decision And I've said this on stream if he's injured if he was already injured they shouldn't have booked this match This match should not have happened if he was already injured if there's some backstage politics and this is Tony cons way of punishing see him punk. I don't think that is the case, but I wouldn't be surprised Maybe if there was the case who knows But all I know is For me and a lot of people that was in the chat and people I've seen on on social media. This wasn't it, bro I'm willing to agree to disagree with someone. This was not it. I Was severely let down and wanting to see this match Now I'm sure they'll probably have a rematch. Maybe at some point. Maybe it'll happen at all out But I just feel like What was the point? What was the point to get the titles off of CM Punk? Then why have an interim champion? You could have had CM Punk vacate.  That would have been cool You could still pull off the heel turn on his return Like you can pull it off the heel turn like when he comes back if you wanted to I feel like there's just so many Different avenues they could have took but instead you have the main event of possibly your biggest World championship match in their company's history and it only lasted three minutes For shock value and for people to talk about like me. I'm talking about it now I'm making a whole separate video about this because obviously this is gonna be the talk of the town for the rest of the weekend There's gonna probably be reports was this storyline wise was this because Tony Khan wanted to punish CM Punk You see him punk now leaving. I've been seeing people say that I don't know all about that I'm not gonna get into that. We'll figure out what happens over the weekend and also This is clearly was a rating boost They decided to put this match at that time slot to get people hyped up to want to stay around for the show honestly My opinion they could have just had this at the end of the show But now knowing how they planned on booking the show It made sense they didn't put it at the end because it would have just been that would have been super anti-climactic To put that at the end of show so I get why it was put at the middle of the show, but Overall, I think They're trying to do some fancy storytelling here and it really It hurt the show in my opinion The hype of the show it hurt last week's promo they had last week's promo doesn't mean nothing I'm just be honest with you the promo they had CM Punk John Moxley means nothing now It meant nothing because of what they did here at least with the MJF and the CM Punk promos They meant something in that feud that they had fantastic view The CM Punk MJF you meant something you can go back and watch the promos Segments because they mean something they built to something greater that promo We got between John Moxley and CM Punk now seeing what we got here in the main of the coal main event Now seeing the three-minute championship match unification match.  This is this is one of those situations where it's like, bro I'm just so confused and perplexed and I don't know what they do here They don't even now have a world championship match for all out So I'm sure they will find a way to get that match to happen And I'm like if you have all out in Chicago, you gotta have CM Punk So we'll see what will happen, but I did not like how they got the championship on John Moxley I want to put this out there. I don't have a problem with John Moxley winning I think John Moxley winning is a cool way, you know, that's that's that's a cool pick Especially if you're able to potentially turn CM Punk Hill, I'm all for it I just did not like the execution of the actual match because literally It was three minutes and it was done and we're moving on to mid card segments right after AEW World Heavyweight Championship unification match. We're going to mid card segments Does that not compute with y'all? Does that not make sit like does that does that make sense to some of y'all like world championship match big implications of the future of the World Heavyweight Championship Mid card segments Here here I don't know coming up alone. Let me know what's your thoughts on this whole situation. Did you guys Enjoy that three-minute match Are you guys in favor with what Tony Khan is doing booking wise? Do you guys agree with the match outcome or are you guys not really sure what the hell is going on and You're kind of disliking how things were set up for this unification Just let me know down below what your thoughts and opinions on all of this because this is just insane, man But I appreciate all the love and support on the channel row to a Honey, okay. Appreciate talking to you


We'll first introduce Latta. So Latta Balasundaram is a lead physiotherapist at Fernandez Foundation in Hyderabad, India. She has a master's degree in physical therapy in pediatric and adult neurology, but over the years developed a passion in the area of women's health. She's also a Lamas certified childbirth educator and a lactation counselor. Coming from a country where cesarean section rates and unnecessary medical intervention rates are high, she feels strongly about educating, expecting couples with information that could help them make informed decisions in their birthing process. Over the last 14 years of clinical work experience, she has worked with helping women with pain, optimal fetal position techniques in mal-positioned babies, alternate birth positions for women with muscle skeletal issues and pelvic floor rehabilitation in women dealing with pain and incontinence. She works passionately in these areas with the hope of helping and empowering women on their journey leading to pregnancy birth and beyond. So Latta, I am going to hand over to you now, the controls so that you can begin your presentation. You should be able to... Yes, thank you, Latta. Welcome, Latta. Take it away. Thanks, Red, for that introduction and it's a pleasure to be on this platform of the IDM today. I also would like to wish all the midwives a happy international day of midwife. And coming straight to my topic today, I'll be presenting about the success of implementing exercises in turning beach babies and increasing normal vaginal birth rates. Yes, so my aims and objectives. This study has two primary objectives. One is to check the impact of optimal people positioning exercises on beach presentation. And the second being to see the incidence of normal vaginal birth rates in women whose babies have successfully turned. The background in India, particularly and also everywhere else, up to primarily after the beach trial 2000, plans of the hidden sections really have become the model for women who presented with beach. And before we actually set this pathway up in Fernandez Hospital, the women who came to us were offered external septic washing and if failed, then they were offered the Cezarean section. But all public hospitals and public institutions in India, 100% rates of Cezarean sections because that was the only option given to women presenting with beach at term. Now, as we know, we do have a lot of contributing factors to buy, sorry, we did start the structure pathway primarily in 2018 February after Tammy Ryan, the trainer for spinning babies, came and did a wonderful three-day workshop and opened up this entire world of spinning babies and optimal people positioning for us. We were a group of mixed physiotherapists, childbirth educators, doulas, myth bites and obstetricians who actually took part from all over India who came for this three-day workshop. The philosophy of a lot of reference goes to spinning babies and therefore the philosophy of spinning babies is actually balancing the soft tissues of the body by using gravity and specific movements to enable the uterus to align better for optimal people positioning and also easier labor. So we learned techniques in pregnancy as well as in the interpartum phase. Then we came up from March 2018 into this structured protocol which if a mom presents with Breach at 32 weeks scan, then she's offered the spinning babies exercise techniques if she does and body balance techniques. If she does accept, then we recheck the presentation at 37 weeks and if the baby has done, then regular antenatal care is provided to this mother and she has a trial for her mom with our children. And if this mom's baby does not choose to turn and continues to remain in Breach, then she is counseled for external catholic version. And the women who accept external catholic version and are successful in that, again, go ahead in having regular antenatal care and try for vaginal birth and the unsuccessful ones along with the ones who decline ECBs are both counseled for Breach vaginal births and C-sections. So this was the pathway we followed. The methodology being a retrospective analysis of 340 mothers taken from March 2018 to December 2020. We did have very clear inclusion criteria being singleton fetus and any pre-presentation between 32 weeks up to 37 weeks gestation booked with us. We did have very defined exclusion criteria since we have a wide spectrum of mothers from low risk to high risk coming to us and we wanted it to be safe. We did exclude these 10 criteria that you can see. We also did not include any twin pregnancies in this. Now coming to the results, the first thing is to see the success of the exercises that we did. Since we did have an entire year, a little over a year of pandemic, we did lose around 12 of them, which around 3% of them lost to follow-up since some of them decided to birth at their own place in their hometowns so that was lost there. But 62% of them, that is 211 babies turned Catholic and the remaining 35% remained in Breach. Now from all the 211 who turned into Catholic, we had 53% 111 going on to have a normal vaginal birth and the ones who did not set into labor, lot of them declined and requested for a C-section. This came up to around 17% of them. This was because of failed inductions or not consenting for induction. And 22% which is 35 of them went on to have an emergency C-section for presumed fetal compromise. We also did offer ECVs for the ones who continued to remain in Breach, 14 of them accepted, seven of them successfully had ECVs and went on to have a trial for vaginal births. The ones who didn't, which is seven of them, five accepted and consented for Breach vaginal births and three went ahead to have success with Breach vaginal births. Now, as already discussed from the term Breach trial, like hundred C-section sections are the only option in public health sectors in India. And even in the private health sectors, very few really, absolutely very few offer ECVs or any specific exercises as a structured program. They have many contributing factors to Breach positioning that can influence Breach positioning and which could be external or internal, but we are not gonna talk about the internal factors that we really have more control over. We are going to talk in a little more detail about the soft tissue surrounding and supporting the uterus. And when you come to the soft tissue surrounding the uterus, we do have primarily these ligaments that we talk about which are the broad ligament which completely comes from the natural walls and goes into the center of the uterus. It does support the entire weight anteriorly of the uterus. We do talk about the uterus sacral ligaments which inserts into the sacrum and also the round ligament which supports the uterus going through the inguinal canal into the mons pubis and labia. So these are primarily the ligaments which surround and support the uterus that we actually work on through what we see in our exercises. These are some of the muscles, the major group of muscles which influence the symmetry of the pelvis, therefore influencing the fetal position. You're looking at this orange muscle which is a very important source muscle coming and inserting into the hip and this almost literally swaddles the uterus. You also have the quadratus lumborum which attaches or connects the posterior superior and iliac crest and the lower ribs. And you also have the green muscle as you can see which is the pelvic floor muscles which support it inferiorly. You do have the small triangular muscle which we call piriformis muscle which contributes a lot to the hip and pelvic mobility. And when you look at all these muscles they are connecting the spine, the pelvis, the hip and therefore any asymmetry in the left to right or any type, excessive tightness, phasom, twisting, triggers all of this can cause asymmetry in the pelvis which again influences the way the uterus actually lies. And here is another image just showing how beautifully the muscles and the ligaments are intertwined and how they form this entire support in structure to the uterus. Importance of body balance is very important to understand here since we've designed the structure based on this. As you can see here you've got a perfectly balanced and square pelvis and you do have a proximal and distal joints which are also very well balanced. When you look at the pelvis here it is not symmetrical and you can see how it influences the spine to curve how the proximal joints have asymmetry and also the distal joints have asymmetry. So this just goes to say when you want to work and you want to work on a better outcome you just don't work on just the pelvis but the body as a whole it would be nice to look at the body as a whole since it is a closed kinematic chain complex. So very early like from 16 weeks onwards we encourage as many of mothers that come to us to enroll in our regular antenatal classes our childbirth education classes out of which they do practice these body balance exercises and we just look at comfort and your body balance and better biomechanics and better postural corrections, things like that. And here we just addressing the calf muscle the hamstring muscle, the back muscle, the chest muscle just some simple exercises that they do. They do come in with their partners and here you can see our classes where they are exercising with their very involved and interested partners. We do also have importance is given also not just on flexibility or yoga but a strength and flexibility balance as you can see the mums first image they are stretching out second image they are strengthening. We do have these mums not just like I said flexibility but some tone important muscles that need strength are the gluteal muscles and you can see the core muscles which we also address and work on in our group classes. Coming to now though we do expect all these women to come as early as possible be interested in exercise, be more aware, all of that but we don't get all of them coming in and that is why let's say they do come to us at around 32 weeks with a rich presentation then we do take some of the body balance exercises which are focused on the primary muscles which as you can see the first image is the suaas muscle being stretched. The second is the adductor and the hip muscle being stretched, the rotators. Here you see the spine increased mobility exercises. This is commonly called the caten cow and it is amazing to improve the symmetry of the spine and the pelvic mobility along with strengthening the core as well. So we include these four exercises if they do come in at 32 weeks and have no clue about exercises because if you give them these entire list they've never come earlier to do it very likely that they may not be compliant to all the exercises we give them. So to ensure that we keep it short and limited we give them these four and then from the spinning babies we do give them the three sisters of balance. Now what are the three sisters of balance? The three sisters of balance are one of the abdominal shifting exercise and I'll tell you how this is relevant. You'll be used at the gozo and we encircle entirely the abdomen we lift it gently up and use small shifting hand motions almost like a micro massage effect. It gives to the broad ligament that we just looked at amongst the ligaments supporting the uterus and the entire abdominal fascia as such. You know when you have a woman on her feet all day and let's say that uterus is tilted anteriorly a lot more you'll know that the broad ligament gets strained and tight and this can cause pain. A lot of times in women abdominal lateral pains as well as decreased pain can be a reason why they can be spasm and again decreased room for the baby. So we just address that with abdominal shifting. It is very relaxing for the mother. You do have forward lean inversions it's done in three steps. The first and the last is this kneeling position and the middle one is head down. Now this uses two philosophies one is the use of gravity. The gravity acts on the heaviest part of the baby which is the head and the spine therefore easily turning the baby around giving more chance for the baby to flip around. And when you come back into this position it repositions that Pupus sacral and Pupus cervical ligaments that we see which can become tight and twisted and influence the way that of the uterus. Therefore when you untwist this and make more room in the lower part it realigns the uterus when you come back into kneeling position. So this is the two ways it works. And then you also have the sideline release it's not just about lying onto the side but it is a lot to do with stacking the hips, stacking the pelvis, the shoulders, the lower leg locking it in dorsiflexion and they're just dropping the top leg down to relax. It works largely on the perineal area and the lateral hip musculature.  There is a lot of perineal tightness present there as well. So this is something which is excellent for those moms. So if you look at those four body balance and these three sisters of balance you know that the crucial room makers that we are looking at are the soas muscle, the dorsal lumbar musculature, the broad ligament of course, the round ligament, the Pupus cervical and the uterus cervical ligaments and inferiorly the pelvic floor. These are definitely the primary contributors. So when a mother walks in, it's just a quick view of how the mother is walking. First you know, is she walking with the anterior tilt? Is she walking with the posterior tilt? Is she walking wide-based and like a duck? All this gives us an insight of what to work on because then you know that the gluteal muscle is important to strengthen, it's weak or the abdominal muscle or the core is weak or there's severe tightness in the hamstring. So this generally gives us that idea. Then we go ahead to check that by checking the muscle length and like I already said, a good balance of the strength and flexibility. So it's important also to reconfirm that assessment of posture by checking the strength of the muscles. And when you do have any asymmetry caused like the level of the shoulders, the alignment of the spine, the level of the hips, this also goes, should not go unaddressed. And sometimes a mum can come with severe scoliosis or a limb length discrepancy where we do have to give some footwear modification. So this is also important to address. Now pain is a huge contributing factor to decreased room for the baby and particular postures. Definitely the room makers we talked about are largely influenced by pain because the piriformis muscle or the sacro tubular sligament that we talked about or the perineal muscles when they are in pain and the lower back, the quadratus lumborum muscle when they are too much in pain, it forms spasm and contracts pulling the pelvis and the spine in different positions of asymmetry. Sometimes when you simply work with relaxing those muscles with soft tissue release with your hands and some heat, it just relaxes them and creates a lot more room and your outcome to your exercises is a lot better. We also have to train the mother on how sensitive she is to the position and the movements of the baby. So we just try to educate her on, if you have small cluttering movements, it could be the hands, if you had cross movements, it could be more of the limbs and if you have a bulge which is movable, it's the head, if it's not, it is the bum and on the left and right side of the abdomen, if you have a little bit of the bulge which is more on one side, it could be the spine of the baby. Things like that where the mom knows and she's sensitive that, yes, my baby is moving a lot more now and she's positive that the baby will spontaneously get into the position of head down soon. It is also very, very important. See, she may be exercising just for 15 minutes or 20 minutes at the max or half an hour, but when you look at her everyday activities, if she's a mom who's sitting in a chair in the desk job or if she's a mom who needed to constantly be on her feet and these kind of things, if she's not having symmetry in that and if she, let's say, reclines in a recliner most of the day if she's at home, then your carryover of the exercises is not that effective. Therefore, we do need to consider what her everyday activities and occupation is to just give her good postural advice. If you have a mom who's reclining most of the time, she's definitely gonna have a lot more perennial tightness. You want to give her some forward lean positions that will enhance the baby to be in a better fetal position. Simple examples of what we could do just as an advisory for the mother. Therefore, just covering up what we just talked about, as early as possible to encourage these moms into body balance exercises from 16-week converts. If they don't or if they are not compliant or still do come with babies in bridge, after 32 weeks or so, anytime between 30 to 37, we give them a few of the body balance and the three sisters of balance. We also give them activity modification advice on economics and occupation and their everyday activity. Therefore, the conclusion is that we do recommend offering specific exercises for automated positioning to help these big bridge babies turn. And also, as we can see, we did have 62% success rates. We did also introduce, by introducing these structural exercises, we definitely have reduced the rate of cesarean sections for bridge presentation by 53%. In general public hospitals, it is where it is 100%. So this is the conclusion. And these are some of the references. Spinning babies being a big reference, we do also have some references for bridge positioning and what influences it, as well as a lot of detail into the biomechanics of the pelvis, the anatomy of the abdomen of the pelvic in net and outlet, and positions for labor and birth. And also how ribosal techniques can influence fetal positioning. And thank you so much. I am here for questions. Over to you, Red. Thank you. What a wonderful presentation. Lot that we can really see how well you prepared and also how well you know the subject matter. So it's just being a little bit familiar with Fernanda's hospital there in Hyderabad myself. I just see that it's so, so wonderful that you are really empowering the women there with these exercises where they can take charge of their situation a little bit prenatally and also to see the belly mapping that you're doing. So also teaching them how to palpate and understand where their position, the baby is positioned in their body. It's just such wonderful empowering work that you're doing there. So congratulations. And yeah, so we can take, we have some time we to take some questions from the audience. So please feel free to type. Let's go up to the top and see if we missed anything up here. There are some people here in the presentation including Catherine who's hearing about spinning babies for the first time. So that's really wonderful. I can see for myself as a midwife, it's really been an absolute game changer in my practice to have an understanding of these ligaments of these muscles, how they affect babies positioning and to be able to empower our mamas with the information. Beautiful pictures. Let's see, such informed work to help with muscle relaxation towards physiological birth. Okay, so people are amazed by your work and your presentation, it seems like. It's great to see that you also have, I know Fernandez is such a busy hospital there that you were able to get such a great number in your studies at 340 women. That's really awesome. And those success rates of 62% of turning that's also really, really interesting to see. I did have a question about are all the midwives there trained in understanding these techniques or is it usually that like for yourself the physiotherapists come in for this part? We did have three of our midwives as a part of this training program. And then when we came up to the structure of a program from the physiotherapy aspect, we did tell them about the quick things to assess. And if they have any more queries, we are always available in the hospital. So they give us a quick call saying that can you do a detailed assessment? I feel there's something which I'm missing and then we are there. But yes, three of the four of our midwives in fact are also trained and we have them across our units. So in every unit we have one midwife who is trained with spilling babies. And yes, they are as aware as what I just talked about. Okay, yeah, this is great. And I was also curious, I wasn't sure from your presentation, you said you started from about 32 weeks. I was wondering are generally all the moms who are coming there, are they educated with the three sisters of balance and the different balancing exercises to do or is it specifically the information just given to those who have a breech baby at 32 weeks? No, it's the three sisters of balance is specific to a baby who comes in with, a mother who comes in with breech. But the body balance exercises that I talked about from 16 weeks onwards, that is given to most for our general group sessions for months, with or without breech, yeah. That's great to see, amazing. And do you find that there's a good success rate in the moms who are also taking that responsibility and like doing the exercises at home? Yes, definitely, I feel the more compliant, the more belief they have in what they do, I think we have seen, we can't really say just because of that. Sometimes we just have to say, well, your baby doesn't want to turn and we have to accept that if your baby doesn't. Yeah, but there's better compliance is definitely a better outcome and better carry over to the exercises. Being constantly aware of our posture is one of the huge contributing factors to also how the baby has room and opportunity to turn. Yes. We have a question here. I hope that I pronounce this right. Bonsane Bonsiano. She's asking the assessment maneuvers, including your recommendation. What considerations do we have for mothers with physical disabilities?  So yes, here definitely a physiotherapist would have to see this mother to assess the body better. The considerations that we have is, so far we have seen mothers with severe structural scoliosis for sure. We have seen mothers with, you know, heavy parishes, like, you know, maybe they had a mild form of a parishes on one side of the body and that causes a lot of imbalance. So then if that's why these mothers with the history of this are referred to us early, then we work on actually building that symmetry as much as we can, and then which would give the baby more opportunity to turn. So the considerations would be definitely early recommendation for a visit for assessment and also working on this mother to as far as possible, you know, if it's structural, we can only work on the soft tissue. We can't manipulate the bones in pregnancy, definitely. We don't usually encourage to do that. So these are the two considerations we would give the men with specific physical disabilities. We also give a lot of alternate birthing positions for these mothers with physical disabilities so that they do have a trial for vaginal birth and not just going for the C-section because they had polio or because they have some other physical disability. This is really informative. Thank you. Any other questions for Latta? We have a few minutes remaining. Don't be shy. Curious to hear in the chat how many midwives out there are currently using these spinning babies techniques. Is this something that you use in your practice? Is it being used in your setting? Or is this the first time you're hearing about this? You know, for me, like I said, it's been a real, it's definitely been a real game changer to just be able to understand more about the ligaments and the muscles and how everything works together and how we can really avoid, help women to avoid those C-sections for breach. We do also use them a lot in birth, in birth. Oh, yeah, nice. Yeah, so that's interesting. It's wonderful to see how it works actually with the OP baby, for example, or some other who's having engagement issues that we do see or a slow labor. We really love to use them. That's an interesting question. That's an important ad. Thank you for adding that in. I see that as well, even for changing, shifting a baby from posterior to anterior. There's so many ways that we can use these exercises to help baby to get in that really optimal positioning. Anne-Marie is saying we use three sisters of balance as well as yoga in our birth center in India and also the ECV. That was one question. I'm not sure if you can answer this, Latta, but I was just curious about for the ECVs there in your setting, is it the midwives that are performing them or is it the obstetricians who perform the ECVs? A little bit off topic. The obstetricians perform the ECVs, right? There are a few obstetricians who train and attend who perform it. Right, okay, got it. That's great. Well, it looks like maybe we are at a conclusion here. So last chance, any one of you want to chime in here with Latta, with a question or to share your experience. And otherwise, thank you so much, Latta, for sharing your time with us. It's so nice to see how progressive Fernandez Hospital is that they also have you, for example, a physiotherapist on board on the team to really help optimize the experience for mamas and babies there. So that's so wonderful to see it happening. And of course, we know that in India there, you are all in quite a epicenter right now also with COVID. So we just want to just know that all of us around the world are sending you so much love and good health as well there. And we hope you move through this very quickly there.


Welcome to this talk about identity-based encryption for fair anonymity applications, defining, implementing, and applying randomizable RCCA secure IBE for Asia Crypt 2021. I'm Yi Wang, and this is a joint work with Rong Maocheng, Xing Yi Huang, Jian Tinglin, Baosheng Wang, and Moutin Yang. In this talk, we many concern the applications of fair anonymity. For example, in the scenario of anonymous communication, users in the anonymity set communicate with each other in an anonymous manner. Once someone abuses the anonymity service for illegal activities, we hope there is a trusted authority that can revoke the anonymity of malicious users. So, the fair anonymity aims to achieve a balance of individual privacy and societal safety. Obviously, identity-based encryption, namely IBE, is a natural candidate for such a setting. IBE was introduced by Shamir in the 1980s, and the first efficient realization was proposed by Bonin and Franklin in 2001. In IBE, IBE encrypts messages with the identity of Bob. For example, email address and Bob can degrade the self-attached with secret key, SKBob, which is generated by the key generation center, namely KGC. So, the KGC can check any self-attached generated by the users and play the role of trusted authority in previous scenery. Apart from the fair anonymity, the other properties of such anonymous communication put some extra constraints on the underlying encryption scheme. First, the scheme should support the randomization of several texts so that the server can hide the connections of incoming and outgoing several texts. In particular, the randomization of several texts does not change the underlying identity and the plan text, so Bob can still obtain the correct plan text from several texts C' Besides, it is desirable that the randomization of several texts does not involve any public parameters. Second, the server text should be anonymous and do not reveal any information about the identity of the receiver. Otherwise, the attacker can correlate several texts with respect to underlying identity, as the randomization of several texts does not change the identity. Third, the encryption scheme should be secure against active attacker who can probe the server with malicious self-attached. A combination of those constraints points at re-randomizability, receiver anonymity, and RCCA security. In particular, RCCA security is a meaningful relaxation of CCA security for public key encryption and it is compatible with randomizability. So we turn to study how to achieve those properties in the context of IBE simultaneously. Here are our main results. First, we define a new security notion called anonymous identity-based RCCA security for IBE. Then we implement a concrete IBE scheme that satisfies anonymous ID RCCA security and re-randomizability. Finally, we apply this IBE scheme to build identity-based universal mixnet with fair anonymity. Now we introduce the definition of anonymous ID RCCA security first. In fact, Gantry has defined the notion of anonymous ID RCCA security already at EuroCrypt 2006. It is a combination of ID RCCA security and receiver anonymity. In the security game, adversary first chooses two identities ID0, ID1, and two plaintexts M0, M1 after receiving the public parameters generated by the challenger. And then it is required to guess the identity IDB and the plaintext MC of challenge self-attached C-START generated by the challenger. During the whole game, the adversary is granted access to key generation and decryption oracles. We imitate the definition of RCCA security to formalize the notion of anonymous ID RCCA security. The main difference between anonymous ID CCA and ID RCCA security lies in the decryption oracle. Specifically, in the decryption oracle of anonymous ID RCCA security, if identity ID is equal to either ID0 or ID1, the challenger would decrypt the self-attached C with both SKID0 and SKID1 and check whether the decryption results intersect the plaintext picked by the adversary. Otherwise, the challenger decrypts C with SKID only and check whether M is equal to either M0 or M1. Anyway, those additional actions prevent the adversary from winning the game trivially. Next, we introduce how to build a randomizable IBZ with anonymous ID RCCA security. At the core of our construction is the double-strand paradigm. In the Ergama-based universal cryptosystem, the self-attached of plaintext M is composed of two strands of Ergama encryption, EYM and EY1. By the homomorphic properties of the Ergama encryption, strand EY1 can be used to re-randomize both EYM and itself correctly. So, the double-strand paradigm offers an elegant way to re-encrypt self-attached without any public parameters. However, this paradigm cannot be applied to the well-known game tree IBZ. As IDCCA security contradicts to the homomorphic property, to overcome this issue, we describe the game tree IBZ scheme briefly. Let E be the symmetric bilinear map, P be the random generator of G, A in brackets denotes AP, and A in brackets T denotes EPP to the A. The self-attached of game tree IBZ consists of three parts, key self-attached, data self-attached, and validity checking. During the decryption procedure, the validity checking part is used to test the validity of self-attached, while the key self-attached is decrypted to obtain the session key for recovering the plain text from data self-attached. In particular, the value of vector beta in X4 changes with X1 to X3, so re-encrypting self-attached EIDM with EID1 would not get a valid self-attached. Consider that re-encryption does not change the plain text M. We modify vector beta in X4 to vector mu and obtain a variant of game tree IBZ. The vector mu includes the hash value of plain text M. Now, we can obtain a game tree IBZ-based universal crypto system by applying the variant of game tree IBZ to the double-strand paradigm. However, this construction does not satisfy anonymous IDRCCA security because the adversary in the security game can guess the plain text and re-encrypt strand EIDM by performing the explanation with it and verifying the guess by curing the decryption oracle. So, we have to restrict the manner of randomization. To defend against previous attack, we introduce extra components in the validity checking part of both strands and perturb the randomness S in strand EIDM with C0 and Z1. However, the adversary is still able to re-randomize EIDM by performing multiplication with public parameter identity and plain text. To restrict the randomization minor further, we mask the validity checking part with the secret value U and encapsulate U with another two strands, E'IDU and E'ID1. The random value U, short among those four strands, prevents adversary from obtaining valid self-attest by mixing strands from different self-attest or randomizing strands with public parameters. Now, there is only one way to re-randomize the self-attest. To prove the anonymous IDRCCA security of our construction, we make negligible modifications to the simulation of security game step by step. First, the setup and extraction algorithms are modified to generate secret keys without master key. Then, the challenge plan self-attest is computed using alternative encryption algorithm such that the distribution of self-attest is independent of the underlying identity IDB and plain text MC. Finally, the challenger answers all the decryption queries via a time-unbounded decryption algorithm that uses public parameters and the challenge self-attest only to decrypt self-attest. At this time, the extraction and decryption queries do not provide extra information about master key and secret keys to the adversary, and the challenge self-attest perfectly hides the identity and plain text. So, the advantage of adversary is zero. Finally, we present an ID-based universal mixnet based on such IBG. Universal mixnet is usually constructed for providing anonymous communication among parties. An ID-based universal mixnet consists of a bulletin board, a trusted authority, a set of senders, receivers, and mix nodes. For simplicity, we assume there are own senders, own receivers, and three mix nodes. In the initialization stage, the trusted authorities play the role of key generation center and generate secret keys for each user's and mix nodes. In the package generation stage, suppose every sender SI intends to send messages MI to a receiver R5I, where function phi is a projection that depicts the relationship between senders and receivers. The package P1I generated by sender SI is composed of two parts. One is the symmetric self-attest of messages, and the other is IBE self-attest of symmetric keys. All the packets are uploaded to the bulletin board. Then, the first mix node M1 downloads all the packets and performs mixing operations. In particular, it decrypts the first IBE self-attest in packet P1I to obtain symmetric key, K1I, and then decrypts the symmetric self-attest with K1I. Finally, mix node M1 randomizes the rest of IBE self-attest and generates a new packet P2I and uploads all the new packets to the bulletin board in random orders. Similarly, mix node M2 downloads packets from bulletin board and performs same mixing operations and uploads all the packets P3I to the bulletin board in random order. After mix node M3 completing the mixing operation, the receiver can download all the packets from bulletin board and decrypt every IBE self-attest to retrieve symmetric key and decrypt the corresponding symmetric self-attest to retrieve messages. Compared with previous universal mix node, our identity-based universal mix node achieves fair anonymity. The trusted authority can revoke the anonymity upon abuse. Also, due to the anonymous ID and CCA security of IBE scheme, our mix node enjoys stronger unlinkability. Finally, the IBE eliminates the public certificate management and our mix node can provide more covert communication for the sender and this is all the main results of our work. Okay, that's all. Thank you.


When it comes to looking at the world, it's as much about where you stand as what you see and for that comes a foundation built with you and nature in mind. From nature stems an icon that has overcome all limits the elements working together as one, woven with culture rooted in all of us. A stage where everything's possible, a window to the world you just can't ignore. A place where the air is crisp and the stars are in your grasp. An idea so grand, it needed one vision to build it. A vision with a new point of view. So that when you look at the world, the world will now look back at you. The Tower, the new icon of Dubai Creek Harbour. Thanks for watching. Drop a like. Leave a comment. Please don't forget to subscribe our channel, Design Hysterics. Get more updated videos from now. Click on the bell button below to get notified. See you people in the next video. Till then, it's a bye from Design Hysterics team.