From 897a6e776c03034d6695a84bae25e5c19e80949d Mon Sep 17 00:00:00 2001 From: Justin Uberti Date: Fri, 20 Apr 2018 07:41:46 -0700 Subject: [PATCH] Update proxy handling per list discussion --- ip-handling/draft-ietf-rtcweb-ip-handling.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/ip-handling/draft-ietf-rtcweb-ip-handling.xml b/ip-handling/draft-ietf-rtcweb-ip-handling.xml index 82d1662..3ee13aa 100644 --- a/ip-handling/draft-ietf-rtcweb-ip-handling.xml +++ b/ip-handling/draft-ietf-rtcweb-ip-handling.xml @@ -218,11 +218,11 @@ ipr="trust200902"> to hairpin through a NAT, fall back to an application TURN server, or fail altogether, with resulting quality implications. - Force proxy: This is the same as Mode 3, but all WebRTC media - traffic is forced through a proxy, if one is configured. - If the proxy does not support UDP (as is the case - for all HTTP and most SOCKS - proxies), or the WebRTC implementation does + Force proxy: This is the same as Mode 3, but when the application's + HTTP traffic is proxied, WebRTC media traffic MUST also be proxied. + If the proxy does not support UDP (as is the case for all HTTP and + most SOCKS proxies), or the WebRTC + implementation does not support UDP proxying, the use of UDP will be disabled, and TCP will be used to send and receive media through the proxy. Use of TCP will result in reduced media quality, in addition to any performance