Google Announces WebRTC Technology Roadmap

Google's first integration of WebRTC in the Chrome Dev release released this January was a source of widespread concern. Today, Google published a roadmap for the development of WebRTC technology in its blog.

WebRTC is a technology for real-time video and audio communication inside the browser, and Google acquired a technology in 2010 to acquire Global IP Solutions. The technology is based on the WHATWG protocol, which is designed to provide simple JavaScript in a browser to achieve real-time communication (real-time Communications) capabilities. In 2011, Google opened the source code for the WebRTC architecture to developers under the BSD license agreement.

Chat features based on WebRTC technology

Google says most of the current WebRTC specifications have been shaped and will release the first stable version of the specification later this year. The stable version will include:

1. Jsep

JSEP (JavaScript session Establishment Protocol,javascript Conversation Building protocol) is a signaling API that allows developers to build more powerful applications and increase flexibility in signaling protocol selection. Google will also provide a JavaScript library to reduce the complexity of using the API.

2. Topologies (topology)

Multiple independent peerconnections will be supported, and each peerconnections will be able to send and receive multiple independent media sources.

3. Ice/stun/turn

ICE and STUN are standard ways to establish point-to-point connections on the Internet. Chrome's current stack deviates from official standards, and Google says it is trying to solve the problem. The technology will also support the TURN service so that it can be connected through a firewall, which requires relay forwarding and encapsulation.

4. DTLS-SRTP

Using WebRTC in Chrome will be forced to encrypt, and in the first WebRTC stable version, DTLS-SRTP will be used.

5. VP8, ISAC, ILBC, g.711

In Chrome, video codec support is available through VP8. In terms of audio, ISAC, ILBC, g.711, and DTMF are supported, and the default is ISAC.

future features of Chrome

Google's blog also lists features that will be implemented in future versions of Chrome, including:

• Data API
• Screen sharing
• Peerconnection agent: Allow streaming to third parties
• Recording: Now Google is perfecting the Mediarecorder specification

In addition to Chrome, the future of Firefox will be added based on WebRTC video chat features, Mozilla recently in a beta version of Firefox to demonstrate this feature. As the technology matures, browsers will be more powerful and developers can develop more practical and creative applications.

Google Announces WebRTC Technology Roadmap