<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-rtcweb-security-arch" target="https://datatracker.ietf.org/doc/html/draft-ietf-rtcweb-security-arch-02">
   <front>
      <title>RTCWEB Security Architecture</title>
      <author initials="E." surname="Rescorla" fullname="Eric Rescorla">
         </author>
      <date month="June" day="5" year="2012" />
      <abstract>
	 <t>   The Real-Time Communications on the Web (RTCWEB) working group is
   tasked with standardizing protocols for enabling real-time
   communications within user-agents using web technologies (e.g
   JavaScript).  The major use cases for RTCWEB technology are real-time
   audio and/or video calls, Web conferencing, and direct data transfer.
   Unlike most conventional real-time systems (e.g., SIP-based soft
   phones) RTCWEB communications are directly controlled by some Web
   server, which poses new security challenges.  For instance, a Web
   browser might expose a JavaScript API which allows a server to place
   a video call.  Unrestricted access to such an API would allow any
   site which a user visited to &quot;bug&quot; a user&#x27;s computer, capturing any
   activity which passed in front of their camera.  [I-D.ietf-rtcweb-
   security] defines the RTCWEB threat model.  This document defines an
   architecture which provides security within that threat model.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-rtcweb-security-arch-02" />
   
</reference>
