From 8eb7f49e0c6b33f2392057a6f3b145285472592b Mon Sep 17 00:00:00 2001
From: Taylor Brandstetter <deadbeef@google.com>
Date: Fri, 4 Nov 2016 14:49:33 -0700
Subject: [PATCH] Removing incorrect statement related to IP leaking issue.

The incorrect statement is "Applications can avoid exposing IP
addresses... by not signalling non-relay ICE candidates."

However, simply not signaling candidates is not enough to prevent IP
addresses from leaking. These candidates will still be gathered and used
to form candidate pairs, which means connectivity checks will be sent
leaking the server reflexive address for every network interface.
---
 webrtc.html | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/webrtc.html b/webrtc.html
index a6a34244b..136b4d377 100644
--- a/webrtc.html
+++ b/webrtc.html
@@ -3367,9 +3367,7 @@ <h2>Attributes</h2>
                   communicating party, either temporarily or permanently, by
                   forcing the <a>ICE Agent</a> to report only relay candidates
                   via the <code>iceTransportPolicy</code> member of
-                  <code><a>RTCConfiguration</a></code>, or by not signalling
-                  non-relay ICE candidates (e.g. until the user has accepted to
-                  share media).</p>
+                  <code><a>RTCConfiguration</a></code>.</p>
                   <p>To limit the IP addresses exposed to the application
                   itself, browsers can offer their users different policies
                   regarding sharing local IP addresses, as defined in