ietf-shadow.jpgRelated to the RTCWEB BOF coming up at IETF 80 at the end of the month, Cullen Jennings at Cisco just submitted an interesting Internet-Draft:

http://tools.ietf.org/html/draft-jennings-rtcweb-api

The abstract is:

Internet browsers and other software applications are enabling support for real time interactive voice and video. This draft outlines a set of IETF protocols that can be used for this purpose and describes the overall architecture. It also identifies the requirements for an application programming interface to control these protocols.

Cullen then offers this overview:

This draft describes two models of how this would work, which are referred to as the advertisement proposal (AdProp) model and the offer answer (OffAns) model. Both of these models are useful in various situations, and they involve very similar code development efforts. This draft proposes an API and protocol set standardization that supports both models.

He provides a couple of use cases and then dives down into establishing a set of requirements:

The section defines the set of protocols and selected subset profiles of these protocols that a browser would need to implement, and forms the requirements for the API to control these protocols. At a high level we split this into connection management, transports for real time media such as audio and video, transports for non media data, codecs support, and signaling protocols.

Cullen then goes on to walk through a number of different protocol proposals, security issues and much more.

As I mentioned before, the RTCWEB initiative is a very important one in terms of ensuring that we do wind up with a standard way for browsers to connect to services using protocols such as SIP. I’d encourage you to take a look at his draft and send comment back either directly to Cullen and/or to the RTCWEB mailing list.

Originally from Voxeo Blogs