Understand WebRTC basics to maximize deployment and adoption
A comprehensive collection of articles, videos and more, hand-picked by our editors
WebRTC is already fully enabled in the Google Chrome and Mozilla Firefox Web browsers, although these are prestandard implementations today. Other companies are also embracing it, most notably TenHands for video conferencing through Facebook, and AddLive for simple video conferencing.
Enterprise WebRTC opportunities: Direct customer engagement
One of the most promising aspects of WebRTC is customer engagement on websites. Companies running websites often look for ways to engage visitors through pop-up chat windows and other methods. With WebRTC, visitors can click a button to call or video chat with a call center agent immediately -- no more waiting.
Potential impact on the network
From a Web developer's perspective, being able to add call or chat features to the front end of the application means that someone sitting at their desk can call a co-worker with a browser-to-browser connection. The call no longer needs to route through the phone system, so calls could require fewer hops; they also lack the quality control or security policies normally associated with enterprise voice calls.
From a network perspective, this might sound scary. "This is one of the most interesting considerations for the enterprise: potential battles between those running networks and those running applications," said Irwin Lazar, vice president and service director for Nemertes Research.
WebRTC will lead to cool and interesting experimentation and innovation, Lazar said. "But we may see a bit of a battle between those who want to control it and those who want to leverage it to its fullest potential," he added.
If companies decide to use WebRTC as a centralized initiative, and as all of these WebRTC-enabled applications pop up within other applications, it may become difficult to control quality, performance and the impact on the network.
The Web Real-Time Communications Group is focusing on how to embed WebRTC into a Web browser, what the job description should look like and how to define the different capabilities.
IEFT is defining the back-end details necessary for all WebRTC-enabled Web browsers to be able to talk to one another -- such as codecs, security mechanisms for encryption, standards to bring a third person into a conversation and how to establish participants' identities.
"The biggest outstanding issue in the standards world right now is that no one has agreed on which video codec to use," Lazar said.
Video calls made through WebRTC need to be encapsulated, and so far there's no consensus about which video codec to use for this encapsulation.
"There's a very well established codec, H.264, which nearly every video conferencing system in the world uses. But using it requires a license. If you embed this capability into the Web browser, who pays that license fee? Today, video conferencing companies pay and pass the cost along," Lazar said.
Google created its own video codec, VP8, but hasn't released all of the details about how it works. And Microsoft has already said it has no plans to use VP8 on Internet Explorer.
Moving forward with WebRTC
Awareness of WebRTC will expand in 2013, and many more applications should go mainstream. Right now, only about 15 companies are delivering small-scale WebRTC applications.
"All of the larger unified communications vendors -- Avaya, Cisco and Microsoft -- are working on WebRTC within their platforms, which they'll likely roll out by the end of this year," Lazar said. "Nailing down standards for the one video codec should help speed things along, but a lot could depend on whether or not Apple makes a move to embrace the technology."