RTCWEB Considerations for NATs, Firewalls and HTTP proxies

Document Type Expired Internet-Draft (individual)
Authors Thomas Stach  , Andrew Hutton  , Justin Uberti 
Last updated 2014-07-24 (latest revision 2014-01-20)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document describes mechanism to enable media stream establishment for Real-Time Communication in WEB-browsers (WebRTC) in the presence of network address translators, firewalls and HTTP proxies. HTTP proxy and firewall deployed in many private network domains introduce obstacles to the successful establishment of media stream via WebRTC. This document examines some of these deployment scenarios and specifies requirements on WebRTC enabled web browsers designed to provide the best possible chance of media connectivity between WebRTC peers.


Thomas Stach (thomas.stach@unify.com)
Andrew Hutton (andrew.hutton@unify.com)
Justin Uberti (justin@uberti.name)

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