Skip to main content

Recursively Encapsulated TURN (RETURN) for Connectivity and Privacy in WebRTC

Document Type Replaced Internet-Draft (rtcweb WG)
Expired & archived
Authors Benjamin M. Schwartz , Justin Uberti
Last updated 2015-10-14 (Latest revision 2015-04-07)
Replaced by draft-ietf-rtcweb-return
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-rtcweb-return
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:


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.


Benjamin M. Schwartz
Justin Uberti

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)