From c1a051abf72a6b406a5e0d1459f9b6410b84fe49 Mon Sep 17 00:00:00 2001
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Fri, 24 Jan 2020 10:57:47 -0800
Subject: [PATCH] Distinguishing between various RTCIceTransports

Fix for Issue https://github.com/w3c/webrtc-ice/issues/13
---
 index.html | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 8d642ff..fa4fde4 100644
--- a/index.html
+++ b/index.html
@@ -80,7 +80,13 @@ <h2>Terminology</h2>
   <section id="rtcicetransport*">
     <h2><code>RTCIceTransport</code> Extensions</h2>
     <p>The <code><a>RTCIceTransport</a></code> extensions allow construction of
-    an <code><a>RTCIceTransport</a></code> without offer/answer.</p>
+    an <code><a>RTCIceTransport</a></code> without offer/answer. This specification
+    differs from the approach taken in [[ORTC]] in that it does not define a distinct
+    <code>RTCIceGatherer</code> object, instead adding methods for control of ICE
+    candidate gathering to <code><a>RTCIceTransport</a></code>. As a result, an
+    application can test for support of this specification by checking for the
+    <code><a>RTCIceTransport</a>.start()</code> method, and the absence of
+    an <code>RTCIceGatherer</code> object.</p>
     <section id="rtciceparameters*">
     <h3><dfn>RTCIceParameters</dfn> Dictionary</h3>
       <p>The <code>RTCIceParameters</code> dictionary includes the ICE username