Media API Requirements for Real-Time Interoperation of Web User Agents
draft-thomson-rtcweb-api-reqs-00

 
Document
Type Expired Internet-Draft (individual)
Last updated 2013-01-10 (latest revision 2012-07-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-thomson-rtcweb-api-reqs-00.txt

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 (martin.thomson@skype.net)
Bernard Aboba (Bernard_Aboba@hotmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)