WebRTC JavaScript Object API Rationale
draft-raymond-rtcweb-webrtc-js-obj-api-rationale-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Robin Raymond , Erik Lagerway , Inaki Castillo , Roman Shpount | ||
| Last updated | 2014-01-07 (latest revision 2013-07-06) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-raymond-rtcweb-webrtc-js-obj-api-rationale-01.txt
Abstract
This document describes the reasons why a JavaScript Object Model approach is a far better solution than using SDP [RFC4566] as a surface API for interfacing with WebRTC. The document outlines the issues and pitfalls as well as use cases that are difficult (or impossible) with SDP with offer / answer [RFC3264], and explains the benefits and goals of an alternative JavaScript object model approach.
Authors
Robin Raymond
(robin@hookflash.com)
Erik Lagerway
(erik@hookflash.com)
Inaki Castillo
(ibc@aliax.net)
Roman Shpount
(rshpount@turbobridge.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)