 Good afternoon. It's late in the day on a Friday. I'll try and keep the pace up and I'm here to talk about the future of ORTC with WebRTC and I'd like to thank Justin and Serge for fabulous segue that they gave me to To this subject now if I can get the clicker going here. I'll be golden I'm good here so Just a little bit about hook flash and who we are Hook flashes the founder chair and editor of ORTC. We're kind of the guilty party for Causing some of the confusion that has existed around this, but we thought it was a critically important issue and We're We've been focused on it for I Probably the better part of the last two years We're a distributed virtual team of developers and engineers with guys currently in US Canada and Serbia our technology focus is very predominantly on ORTC and We also have done extensive work on new web RTC signaling security and identity protocol with a Technology we have called open peer We work with large enterprise customers technology service providers and carriers on The new buzzword in enterprises digital transformation with real-time communications and Before I jumped into the remarks I needed to speak to you know What in fact is ORTC and if you go to ORTC org and as you heard from Google Justin and and Serge earlier ORTC is essentially an evolution of the web RTC API and and the definition is here at from ORTC.org But the way I wanted to share it with you was really in a top 10 format of 10 of the top Benefits that the developer community and customers will potentially enjoy as we we get the ORTC lie library finished and available to the world at large so there's a lot of text on these slides But I promise we'll get through it quickly and and have Bernard our guests from Microsoft join us We'll make this content available through cranky geek and web RTC hacks and whoever else wants Hook flash and ORTC or dot org So the number I'll start at number 10 and count down to our number one So the the number 10 benefit is it enhances direct program or control over the media pipeline So it gives the developers a greater degree of control Justin did a great job of speaking to access at the object level and you'll see a lot of the benefits kind of flow from that Number nine signaling flexibility. So ORTC does not require Offer answer exchange to be repeated every time you change the media it allows you to Not not deal with a round-trip exchange every time that a transaction takes place and this is valuable to an increasing number of companies and developers who are innovating away from SIP for over-the-top applications media forking is Really just allows ORTC to use the same set of ports and that'll that'll be a benefit We'll see with ORTC One of the number seven one of the core attributes of ORTC of ORTC and really the architect fundamental to the architecture is It's it can be asymmetric. So web RTC is originally Conceived was one mic and camera to one mic and camera and as we see the evolution of the standard We're opening up Symmetric applications. So you can imagine multi-cameras multi-mics multi real-time Media from one end without having to have symmetric connections on the other Number six simulcasting and scalable video coding native To the new ORTC application number five Capabilities exchange so this allows remote side to essentially, it's polling and interrogation So that I can get a clear Vision and understanding of what the other side of my peer-to-peer Connection is doing and you could imagine the valuable applications that we'll see with that kind of Mm-hmm capabilities exchange number four SDS SRTP transport and It that's really all around easier integration of legacy devices Number three IPv6 and mobile networks and this is Already available in Chrome. Thanks the kind of progress that Google shared with us in the previous session and It is also available to you in the ORTC library That is underway and and partially available now and as we get to the top the last couple of benefits and The Google guys referred to them It's obviously an incredibly mobile centric world and our ability to leverage something as exciting and powerful as web RTC for mobile is Incredibly important and the the founding vision around The work on ORTC has has been to optimize it for mobile to the highest degree possible So the ORTC SDKs for iOS Android and win RT are Optimized for things like backgrounding and all the challenges you have in mobile network conditions and Finally What my co-founder partner Eric logger way? I think is most excited about and is is The capabilities on mobile network handoff in ORTC and I've highlighted the ORTC live as a new technology called continuous nomination which allows for that really dynamic network management as as you're roaming between a variety of cellular infrastructure and Wi-Fi as You can certainly appreciate the complexities of Moving across networks on a mobile device and maintaining live real-time Communications and there's some incredibly exciting progress on ORTC relative to those kind of issues It's been great to hear the tone today and and there was some wonderful progress at the W3C meetings in Redmond this week and The industry has come together to try and collectively help address this question Do are there are these somehow competing standards? Are they in conflict? Do I have to choose and That web RTC ORTC road map is really getting increasingly clearer Hopefully you leave here today with that Clear understanding that that this is evolution and integration. I wanted to quote Justin updated this for us today. We had a similar quote the better part of a year ago. I think So web RTC 1 1 is our proposal for how we can accomplish the following two things new set of API's for direct control based on ORTC and Integration with the existing web RTC so that we maintain Backwards compatibility as an evolution of the existing API We consider web RTC at the time of the quote. It was one one. I understand now. It's nv Which yeah kind of like nv is good. So but you know the point here we see commitment and endorsement of This road map by Google In June of this year the W3C invited hook flash co-founder Eric loggerway to co-chair the W3C standards work and Their public announcement relative to Eric joining the W3C bore working group was As the new charter sets the path for convergence started in the ORTC community group We expect Eric essentially to deliver as much progress on possible as possible on the path to convergence So we see Google we see the W3C working toward Convergence of the valuable pieces of both these standards and and it's now I'm very pleased to introduce our friend from Redmond Bernard a Boba principal architect at Microsoft Skype to speak to Microsoft's work around ORTC. Thanks chat See if we can get Bernard here Yeah, oh, do you want me to turn the slides and I can So I'll do a do the screen share Yeah Okay, hold on Hopefully I can make it do that There we go, cool All right, so I'd like to talk to you a little bit about the Edge platform and the roadmap for that. Hopefully you can see the slide Okay, thanks Chad, I think we just found the screen sharing bug Okay, we've got to slide up where I understand you've had a busy week out there Bernard Yeah So let me let me just talk a little bit about the I platform So the dev.modern.ie website lists all of the features for the roadmap of Edge and Let me just talk through the way you can interpret this and also the way you can get access To the features as they become available So everything on that site that uses the term supported means that that feature has already Shipped within Edge on Windows 10 some of them are also supported down level on Internet Explorer But everything that says supported is in fact supported in Edge So if you get a copy of Windows 10 and Edge, you can use those features today Now where a feature says it's in development such as ORTC What that means is that feature will become available Initially through the Windows Insider Preview program And so if you're signed up for that program and I'll give you a URL for that You can get builds of Win 10 that contain all the features that are listed in development That includes currently ORTC as well as BP9 which Justin talked about so One question I've gotten is when will those individual features become available and so the answer is they become available When the features are merged from the private builds Into the main Win 10 build and then that build is in in turn pushed out through the Windows Insider Preview program ORTC has been merged into the main build So it shouldn't be too long before you will see that in the Windows Insider Preview program. I'm not exactly sure when BP9 whether it has been merged or will be urged But at some point you will see that also in the Windows Insider Preview program And then eventually in Windows 10 as those features get released So let me talk a little bit about what's in ORTC and what you should expect there so back in October in 2014. We actually had a blog Entry and you can look that up also on dev.modern.ie which talked about the features that we had committed to Back then and we've gotten most of that work done particularly on the audio side So in that blog we talked about supporting G711, G722 and Opus And so we have all of those codecs checked in in addition We talked about other basic audio things that are in the WebRTC audio requirements things like comfort noise And DTMF and that is there as well on the video side in that blog We talked about supporting H264 And we still have that is one thing that you will not see in the preview program interoperable H264 Because we still have more work to do to to get some of the basic video elements of the platform in However, we do have support for something we call H264UC Which is an implementation of RPC 6190 Which is H264 with scalable video coding and this is a codec that supports both spatial scalability Sorry spatial simulcast and temporal scalability Through H264SVC So that's kind of the basic video codec that's in there that you will see in the preview program And we will continue work on interoperable H264 so that we can interoperate with Mozilla and Chrome Going forward and that will require a little bit of more work on the video platform as well as On the video codec transport itself So I know there's going to be questions about VP9 So I just wanted to Clarify a few things. There is a blog that I'll give you a point or two that describes exactly what will you will see in the Windows Insider preview program as far as VP9 support That is currently a decoder Oriented towards streaming media. So it goes along with the the dash support And streaming support that you've seen in Windows 10 already So that's what will be there. There is not currently a support for VP9 encoder And the focus is on streaming media So you will not see VP9 supported within the preview program in ORTC But basically the decoder and the streaming support is there You will see it for VP9 Come out in the windows insider preview program, although i'm not exactly sure what what build that will be in And whether it'll be in the same build is the one in which you'll see ORTC so Also a few other little things. I think this has already been mentioned Get use of media did ship in windows 10 rtm And that is already supported in adapter.js. So you should be able to run all the Examples on github the web rtc samples and they should run at edge And if there are any bugs you can let me know or other folks And uh, we did have a skype blog a while back about skype for web And that basically currently depends on a plugin, but we'll be moving towards plug-in free support over time And so you keep your eyes peeled there probably will be something along those lines talking about Support for that as well I thought I would open it up basically to questions now and and try to answer the things that are on your mind Yeah, so um, yeah, so keep your eyes peeled Basically, our plan is when we release major new features it through the windows insider preview program There's typically a blog that goes along with it kind of giving developers an introduction to the feature what's there What's not there, etc And we already have posted blogs on Media capture functionality in may and then more recently on vp9 With respect to the support there are kind of clarifying what you'll see And what you should expect as a developer And I would expect a blog entry for or to see when when that is Coming out in the preview program as well We have you back up on the big screen now bernard. Okay. I think if you're ready It will start to uh, we'll take some some questions from the audience. Okay. We go out and we'll ask Trent to uh to To repeat for you if necessary UN interpreter Yeah, happy health. Thanks chat Questions for bernard or or for Trent Justin Uh bernard, do you have any sense you mentioned that vp9 won't be supported in webRTC? In this new preview, but is there any sort of sense when that would be supported? Yeah, so I think I heard the question about vp9 So, um, so let me talk a little bit about uh, the work that needs to be done to support h264 Interoperable issues who store because it's a lot of the same work that would be needed for any additional codec So basically what we have today is what we call the h264 you see Um, and that includes support for a number of feedback messages. For example, uh, but not all the ones which you would need for for good interoperability um, there's also, uh, with the work done in the video platform for things like bandwidth estimation um, and So forth and so basically we'd need to put that foundation in place Before we could have interoperability really with any codecs And so that the first evidence of that work having been done with the h264 and once we've kind of got that Then we would be able to add more potential video codecs on top of that The other thing is because I mentioned that we had a decoder in vp9 is obviously You would you would need to have an encoder as well. And then there are issues of the hardware support and so forth so That's kind of another element is supporting, uh hardware acceleration We do have that for h264 you see And so i'm assuming that won't be a huge work item for h264 But but that would be another thing we generally like to have hardware acceleration when we release codecs so that everything runs smoothly But I I have no idea when all of that work would Get done. We basically have to make the platform Functional before any additional codecs would come in Um, and we don't have a we don't have a plan for all of that work right now. So Um, I'm not giving any dates even for h264 Other questions I wonder if you could clarify just the overall time frame for The edge browser with a completely running web rtc already for developers, you know, what kind of time frame are we looking at? well for the for the windows insider preview like as I've said rtc has been integrated into the main windows 10 build so it's kind of more of an issue of Of build packaging and putting it up on the website and so forth. So I'm not going to have a bedding pool as to which day or a week, but uh, I there's no Particular reason for the delay which has anything to do with anything going on in in rtc land so I It's not I would not expect a long wait. Let me put it that way Other questions Fippo, I know you have questions Yeah, so while we're waiting for a question, I'll give an answer that maybe is to a question some people have been asking about but or maybe not Um, so one thing people ask is what are to see objects have we've been working on and the answer is the the core objects That are in 1o that you will be seeing hopefully in a 1o spec the ice transports the sender the receiver The dtls transport are all supported. We have something called the ice gather, which is a little bit unique to orgc And that is there as well So basically the core objects of orgc which are in both the orgc spec and Our rtc 1o for the ones that we've been focusing on Thanks Bernard Okay, um, so actually this is more of a general question for both the chrome parfox and internet explorer teams Just browser interoperability in general and kind of a commitment to that Like another is like i'm going to be an adapter jas and others have been on everyone's writing the same Files to make the you know, their particular app work across all the different browsers But uh, you know, I guess now the internet explorer is on board as well Like what is the commitment there to make it work well between all the browsers? Yeah, so I heard the basic question which was about adapter jas support so as Justin mentioned there is work Going on and I think that work is you could say it's largely successful Forget user media, but it is still work in progress for Uh rtc and I guess I don't want to predict the full outcome of that. I certainly hope it all works There may be some bugs here and there But I think basically keep your eyes peeled once the insider preview was out And people have had a chance to look at it work on a little bit more We'll get a sense of how how well We've got adapter jas working on top of rtc and if there are any issues of bugs or or not But I I do think that's an active area that a lot of people are interested in and so we'll have to see how it well It works Any comments from nils or justin or anyone? So that was a little question for all the browser vendors Uh generally speaking While we are trying to uh, you know snap everything to like the latest specifications adapter is a very good way To make sure you always get kind of the the spec behavior Even when the the implementations are not necessarily up to date So like for example, you can now use promises In web rtc and even though chrome hasn't been updated yet if you use adapter because adapter gives you that promise So I expect adapters still be You know sort of front and center and something you should be using in your apps to make sure you have like You know equivalent support across browsers and hopefully it'll work for Edge, you know just as well yeah, I guess I think Theoretically if we get like a 1.0 spec and everyone implements that one spec And the spec is actually accurate then we no longer need to adapt to jas Um, but that's probably like still some time out I would guess and especially if we add like or tc to it that will add like another variant to it So we're probably stuck with adapter jas for some time Um, but on the other hand if we if we don't then that probably also would mean that we don't have any new development going on anymore So Thanks I think we're we're running out of time. Thank you so much for for joining us bernard It's really helpful And thank you trend Thank you. Thanks very much chat Okay, thanks. Thank you