Recursively Encapsulated TURN (RETURN) for Connectivity and Privacy in WebRTC
draft-ietf-rtcweb-return-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Benjamin M. Schwartz , Justin Uberti | ||
| Last updated | 2015-11-14 (Latest revision 2015-05-13) | ||
| Replaces | draft-schwartz-rtcweb-return | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In the context of WebRTC, the concept of a local TURN proxy has been suggested, but not reviewed in detail. WebRTC applications are already using TURN to enhance connectivity and privacy. This document explains how local TURN proxies and WebRTC applications can work together.
Authors
Benjamin M. Schwartz
Justin Uberti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)