Archive | IETF RSS for this section

ORTC Interview: webrtchacks’ Chad Hart & Robin Raymond #webrtc

webrtcH4cKS: ~ ORTC is not the “Other” RTC: Q&A with ORTC CG Chair Robin Raymond

Char Hart of webrtchacks.com interviewed ORTC Chair – Robin Raymond on a range of topics. Excerpt:

Biggie vs. Tupac. Gates vs. Jobs. Apple vs. Samsung.  Nothing catches people’s attention for no legitimate reason like a feud. Unfortunately this isn’t just a celebrity phenomenon. Feuds have been endemic even to real communications as well. From the very beginning, Elisha Gray’s dispute with Alexander Graham Bell over the original telephone patent showed the industry has a propensity for squabbles…

Read the rest here…

2014 WebRTC & ORTC Events – Fall / Winter Schedule

September

  • Sept 30 – Oct 2 / Chicago – IIT Real-time Communications Conference
    (For me, this is “the” objective gathering of the brightest technical minds in the RTC space.) Robin Raymond will be speaking on ORTC / WebRTC 1.1 and also Cloud + P2P Communications.

October

  • 30-31 Oct / Santa Clara – W3C TPAC / WebRTC WG Meeting
    (W3C Technical Plenary / Advisory Committee Meetings Week which includes WebRTC Working Group meetings. This should be a rather interesting set of meetings for the WebRTC WG, for a variety of reasons.)

(tba) Oct ? / Web – W3C ORTC Community Group Meeting

November

December

ORTC CG Meeting – 5

A few more changes to be made before we call for implementations, very, very close now. Should happen in next couple of weeks with new Editor’s draft.

Google Chrome 38-39 to ship with ORTC / WebRTC 1.1 APIs

For those who missed it, Chrome 38-39 looks like it will be shipping with ORTC 1.1 RTPSender / Receiver APIs as announced by Justin Uberti at Google I/O 2014. This really should not come as any surprise as RTPSender / Receiver APIs are now on track for WebRTC 1.0 integration as well, as per the last W3C WebRTC WG Interim meeting.

ORTC in Chrome 38-39

 

ORTC API Editor’s Draft – Last Call & WebRTC WG

ORTC - Object RTC

The W3C ORTC Community Group has published an Editor’s Draft update to the ORTC API and is also asking for last call comments on the draft…

We are nearing completion of the ORTC specification for our initial ORTC community group draft. We are asking for last call feedback at this time. Some comments to explain some of the changes are still pending but all issues are tracked here and on github. If you would like to make comment, please have a read through and make comment either on this list or as part of our next CG meeting coming up.

There are a few outstanding areas which are “pending” synchronization with WebRTC, e.g. stats, data channel, and IdP. As these have dependencies on WebRTC 1.0, we will attempt to complete the our specification as best we can but those areas will be subject to synchronization should updates come out of the WebRTC community group.

Now is the time to have a read through for final review as the next stage will be to build implementations for implementation feedback.
So what does that mean?

Well, likely the most important takeaway is the fact that this spec now looks to be in a form where it could be implemented. The ORTC Libs (https://github.com/openpeer/ortc-lib) have been in stasis while the CG worked on getting the spec further along. Now that the CG is very close to a public draft on the API spec, that work will resume.

Something else that may be of interest is the direct reference to the W3C WebRTC Working Group in this draft and the issue tracker. There are a few components that require progress in the WebRTC WG before the ORTC CG can implement them. Now there seems to be a direct correlation between the work being done in the ORTC CG and the WebRTC WG, which should really not come as any great surprise to anyone.

At the last meeting, the CG discussed “What is the ORTC CG end game?” The resulting conversation equated to an answer that sounded something like, “Let’s create an implementable API, then if the WebRTC WG is interested in seeing the work being done in the ORTC CG merged into the WG then we should be happy to explore that.”  There was no definite objection apart from, “let’s make sure the timing is right and it makes sense to do that”.

So if you are fuzzy on where the ORTC CG is headed, you should really check out that video clip.

ORTC CG Meeting Video – Hookflash, Jitsi.org, Microsoft, Google and others.

Very productive CG call today, here is the entire 1 hour and 40 minutes. Plenty of great feedback coming from Bernard Aboba (Microsoft), Shijun Sun (Microsoft), Justin Uberti (Google), Emil Ivov (Jitsi.org) and Robin Raymond (Hookflash).

Looks like we are shooting for a Public Draft (with sample code) by end of June, we’ll see if that is achievable (there are quite a few question marks remaining) but at least we have a target.

If you are interested in joining the ORTC Community Group, you can do that here.

Read More…

%d bloggers like this: