Media API Requirements for Real-Time Interoperation of Web User Agents
draft-thomson-rtcweb-api-reqs-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Martin Thomson , Dr. Bernard D. Aboba | ||
Last updated | 2013-01-10 (Latest revision 2012-07-09) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Direct, real-time communications between web user agents (browsers) requires two points of standardization. The first describes the on- the-wire protocol that is used. The second is the API that controls and configures what gets put on the wire and how. The capabilities of the protocol determines the nature of the API. This document outlines how the constraints imposed upon the API by the protocol.
Authors
Martin Thomson
Dr. Bernard D. Aboba
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)