Security Considerations for RTC-Web
draft-ietf-rtcweb-security-03
| The information below is for an old version of the document | |||||
|---|---|---|---|---|---|
| Document | Type | Expired Internet-Draft (rtcweb WG) | |||
| Last updated | 2012-12-07 (latest revision 2012-06-05) | ||||
| Replaces | draft-rescorla-rtcweb-security | ||||
| Stream | IETF | ||||
| Intended RFC status | (None) | ||||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||||
| Reviews | |||||
| Additional URLs |
|
||||
| Stream | WG state | WG Document | |||
| Document shepherd | None | ||||
| IESG | IESG state | Expired | |||
| Consensus Boilerplate | Unknown | ||||
| Telechat date | |||||
| Responsible AD | (None) | ||||
| Send notices to | (None) | ||||
https://www.ietf.org/archive/id/draft-ietf-rtcweb-security-03.txt
Abstract
The Real-Time Communications on the Web (RTC-Web) working group is tasked with standardizing protocols for real-time communications between Web browsers. The major use cases for RTC-Web 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) RTC-Web 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 "bug" a user's computer, capturing any activity which passed in front of their camera. This document defines the RTC-Web threat model and defines an architecture which provides security within that threat model.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)