<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.kaplan-rtcweb-api-reqs" target="https://datatracker.ietf.org/doc/html/draft-kaplan-rtcweb-api-reqs-01">
   <front>
      <title>API Requirements for WebRTC-enabled Browsers</title>
      <author initials="H." surname="Kaplan" fullname="Hadriel Kaplan">
         <organization>Acme Packet</organization>
      </author>
      <author initials="N." surname="Stratford" fullname="Neil Stratford">
         <organization>Voxeo</organization>
      </author>
      <author initials="T." surname="Panton" fullname="Tim Panton">
         <organization>PhoneFromHere.com</organization>
      </author>
      <date month="October" day="31" year="2011" />
      <abstract>
	 <t>   This document discusses the advantages and disadvantages of several
   proposed approaches to what type of API and architectural model
   WebRTC Browsers should expose and use.  The document then defines
   the requirements for an API that treats the Browser as a library and
   interface as opposed to a self-contained application agent.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-kaplan-rtcweb-api-reqs-01" />
   
</reference>
