%% You should probably cite draft-raymond-rtcweb-webrtc-js-obj-api-rationale-01 instead of this revision. @techreport{raymond-rtcweb-webrtc-js-obj-api-rationale-00, number = {draft-raymond-rtcweb-webrtc-js-obj-api-rationale-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-raymond-rtcweb-webrtc-js-obj-api-rationale/00/}, author = {Robin Raymond and Erik Lagerway and Inaki Baz Castillo and Roman Shpount}, title = {{WebRTC JavaScript Object API Rationale}}, pagetotal = 29, year = 2013, month = jun, day = 26, abstract = {This document describes the reasons why a JavaScript Object API 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 API approach.}, }