 We're here with Open Interconnect Consortium, and who are you? My name is David McCall, I work with Intel, I've been part of the Open Interconnect Consortium since it got started. Is this new? It got formed in July of 2014, so it's been around since then. It's like a year, just a bit more than a year. So we were here at CES last year and we were basically talking about what our plans were and how we were going to have devices by this time. And actually we do have devices and we're going to be demoing them at a suite in the Palazzo on Wednesday and Thursday. What companies are making devices? We've got Samsung, we've got AdMail, we've got Honeywell, we've got... So it says something about IoT connectivity? Yeah. So what we're really trying to solve a key problem with the Internet of Things, a lot of people are very excited about the potential of the Internet of Things and I think there's now a general agreement that the real value of the Internet of Things is going to be delivered by the applications and services that run on the richer devices and up in the cloud. The problem is that the people who are supposed to develop those applications and services don't necessarily know how to talk to all of the things and there are a huge variety of ways to talk to those different devices and get that data and reach down and control those things and also to handle security. So asking the developers to learn all of that variety, left over new standards, is a really tall order. We're trying to make it really simple. So we've got a standard for those layers that the software developers would talk to and we'll define how those layers would talk down to the multiple different radios. We've also got translation layers to talk to other non-OIC devices. So basically a developer and application provider only really needs to learn one thing and that's the OIC interface. We're not just providing a standard either, we've got an associated open source project which is an activity. This is an open source project run by the Linux Foundation sponsored by the Open-Inch Connect Consortium and it actually delivers code. So the developers aren't just being given a document with a spec, they're being given code that runs on multiple different platforms. So in consortium you have these companies right now? Well we've got over 110, that's just a small sampling. Lots of companies agree that this is important? Yes, definitely. I mean when I make videos about IoT, I see lots of different groups and stuff. Are people trying to do this in different ways also? Like different consortiums? I think what you're seeing is a lot of groups are running really hard to try and make in that if things happen. As some of those groups started up or other groups that these existed looked at what they need to do with the Internet of Things, there are alliances being formed. Also just the end of November OIC announced that we're actually basically merging in some way with the UPMP. So they've been doing some work on the Internet of Things and they looked at what we were doing and we looked at what they were doing and said this is kind of similar and we should probably just have one thing rather than two things. So all of the UPMP assets are actually being transferred into OIC. We're going to keep their old standards, existing standards running. People can certify that according to those what they're traditionally known for but the Internet of Things stuff is now all being done within OIC. I think that's probably one of the first big coming together of two large organizations. So you're probably going to see more of that as time goes on. There's a mother in here. These are liaisons that we have with other groups. You can see we've got liaisons with DLNA and Ocean, HDMI, HCI, HyperCat, OIC, E-Bus, Ipso, 1M2M, Thread. So where is ARM not on this paper yet? Well, we talk to ARM and I think it's really a question of priorities and what they've got going on and how much resource they have to devote to things. Are they doing this in another way? Not that I'm aware of, no. So there's no conflict, right? It's like the whole world should be part of this? Oh, absolutely. And it's free, no license? To join OIC there is a membership fee but to actually the specs of public and the open source, that's under Apache 2.0 license. You can go to that site. You can go to OIC site, the openinterconnect.org, download the specs, you can go to iotivity.org and download the code. You can use the code royalty free. It's got good patent coverage and you can contribute fixes or adjust changes without being a member. What is Google doing with this? Google isn't doing anything with this at the moment. They've got their own thing going on with Brillo and Weave which is really just a site to emerge. So we're keeping an eye on that but they haven't been involved with OIC.