ORTC CG Meeting 8 will be held on May 13 at 10am – Pacific Daylight Time.
- Review Bugs:
- Review current draft
- Stefan requested we comment on this…
- CG alignment with 1.0
Vancouver is one of the hotbeds for IP communication technology and is home to many developers. With the advent of WebRTC, integration of voice and video chat into almost any application is within reach but as always, there are always pitfalls. Sounds like a great reason to start a WebRTC meetup in Vancouver!
As of today Vancouver now has its own WebRTC meetup group. If you are interested in linking up and talking to like-minded RTC geeks implementing real time comm using WebRTC please join and let’s get together. We will also be looking for meetup facilities & sponsors (snacks, drinks etc.).
I am thinking our first meetup will be in May sometime, not sure on exact dates yet.
Agenda and topic for the first meeting is wide open. Topics like, “WebRTC 101” or “Dos and Don’ts” come to mind, but we can decide on that when we have heard from some active members.
We will also be bringing in some live guests from time to time via what else, WebRTC!
Hope to see you soon!
Hookflash is now providing WebRTC and ORTC Consulting services.
Professional Services Pack
For organizations looking for an expert ORTC / WebRTC developer to provide assistance or become a part of their teams for specific projects. Depending on your needs, the Hookflash subject matter expert can help with any aspect of your project, including consulting, design, development, and QA. The PSP (Professional Services Pack) is available in increments of 40 hours. We have streamlined the engagement process for the PSP to enable a quick start.
Complete Project Development
For companies needing specific development expertise or staff augmentation, we offer complete life cycle development services, including use-case definition, requirements specification, estimates, project planning, design, development, QA, and app store deployment.
Where we shine: C++ (low level, client and server), Assembler (eg. CODEC enhancement), Mobile development: Objective-C (iOS) , Java (android) and Server: Node.js
For more information please visit Hookflash or call 1.855.HOOKFLASH (466.5352) ext.2
22 January 2015 Editor’s draft:
Changes from the October 14 Editor’s Draft:
WebRTC 1.0 compatibility
- Statistics API Update (Issue 85)
- H.264 parameters update (Issue 158)
- Support for maxptime (Issue 160)
- RTCRtpUnhandledEvent update (Issue 163)
- Support for RTCIceGatherer.state (Issue 164)
Update: There is now some healthy conversation in the IETF WG around what “compliant” and “compatible” actually mean. More on this as it unfolds.
We are now in the final throes of a consensus call in the IETF around which video codec should be made mandatory for those building WebRTC apps, services et al, who wish to be considered “WebRTC Compliant”. The codec contenders are VP8 and H.264, in many forms and combinations.
This latest consensus call is for both codecs to be mandated for all WebRTC endpoints, or “dual MTI codec”. I am sure I will catch hell from someone on language but that is the essence of it. As one might expect, there are some that are in favor and some that are against a dual MTI video codec. Those in favor seem motivated to accept this based on the promise of interoperability that might follow and other reasons. As one might expect, we are all quite eager to put this debate to bed so we could get on with other work.
This is not a decision that should be made lightly. Let’s consider the implications. Imposing a dual MTI suggests that every developer that wishes to produce a WebRTC compliant app must implement both codecs.
I find it difficult to agree to mandate a dual MTI codec knowing that there are a great many developers who will not want or will be in a position to implement both codecs. Yes, many WebRTC SDK vendors will support both. Even if both codecs and their transports are provided as part or could be easily added to the application at compile time it doesn’t mean that every developer will want to implement or ship both codecs.
Bottom line is, according this consensus, if developers do not implement/ship both codecs they are not considered WebRTC compliant. To me, this seems like a rather unreasonable expectation. Developers should be able to choose which codec they ship, and not be forced to do 2x the work to become compliant.
I would love to hear from other developers on this. Do you plan on implementing both VP8 and H.264 in your apps?
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…
- 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.
- 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
- Nov 4-6 / Santa Clara – Cloud Expo / WebRTC Summit
(One of the bigger events, plenty more happening here than just WebRTC.) Erik Lagerway will be speaking on Real-time Communications, PaaS & Cloud Communications.)
- Nov 9-14 / Honolulu – IETF Meeting 91 / RTCWEB WG Meetings
- Nov 18-20 / San Jose – WebRTCworld Conference West
- Dec 16-18 / Paris – WebRTC Conference Expo Paris