diff --git a/draft-ietf-avtcore-rtp-over-quic.html b/draft-ietf-avtcore-rtp-over-quic.html
index a20a2cf..b3435be 100644
--- a/draft-ietf-avtcore-rtp-over-quic.html
+++ b/draft-ietf-avtcore-rtp-over-quic.html
@@ -2728,17 +2728,10 @@ <h3 id="name-impact-of-connection-migrat">
 RTCP is used for RTT measurements, may cause spikes in observed delays.
 Application layer congestion control mechanisms (and also packet repair schemes
 such as retransmissions) need to be prepared to cope with such spikes.<a href="#section-12.1-1" class="pilcrow">¶</a></p>
-<p id="section-12.1-2">If a QUIC connection is established via a signaling channel, this signaling
-may have involved Interactive Connectivity Establishment (ICE) exchanges to
-determine and choose suitable (IP address, port number) pairs for the QUIC
-connection.  Subsequent address change events may be noticed by QUIC via its
-connection migration handling and/or at the ICE or other application layer,
-e.g., by noticing changing IP addresses at the network interface.  This may
-imply that the two signaling and data "layers" get (temporarily) out of sync.<a href="#section-12.1-2" class="pilcrow">¶</a></p>
 <ul class="normal ulEmpty">
-<li class="normal ulEmpty" id="section-12.1-3.1">
-            <p id="section-12.1-3.1.1"><strong>Editor's Note:</strong> It may be desirable that the API provides an indication
-of connection migration event for either case.<a href="#section-12.1-3.1.1" class="pilcrow">¶</a></p>
+<li class="normal ulEmpty" id="section-12.1-2.1">
+            <p id="section-12.1-2.1.1"><strong>Editor's Note:</strong> It may be desirable that the API provides an indication
+of connection migration event for either case.<a href="#section-12.1-2.1.1" class="pilcrow">¶</a></p>
 </li>
         </ul>
 </section>
diff --git a/draft-ietf-avtcore-rtp-over-quic.txt b/draft-ietf-avtcore-rtp-over-quic.txt
index 1269705..c268b24 100644
--- a/draft-ietf-avtcore-rtp-over-quic.txt
+++ b/draft-ietf-avtcore-rtp-over-quic.txt
@@ -1563,15 +1563,6 @@ Table of Contents
    congestion control mechanisms (and also packet repair schemes such as
    retransmissions) need to be prepared to cope with such spikes.
 
-   If a QUIC connection is established via a signaling channel, this
-   signaling may have involved Interactive Connectivity Establishment
-   (ICE) exchanges to determine and choose suitable (IP address, port
-   number) pairs for the QUIC connection.  Subsequent address change
-   events may be noticed by QUIC via its connection migration handling
-   and/or at the ICE or other application layer, e.g., by noticing
-   changing IP addresses at the network interface.  This may imply that
-   the two signaling and data "layers" get (temporarily) out of sync.
-
       *Editor's Note:* It may be desirable that the API provides an
       indication of connection migration event for either case.
 
diff --git a/index.html b/index.html
index a790ee8..9152877 100644
--- a/index.html
+++ b/index.html
@@ -70,7 +70,7 @@ <h2>Preview for branch <a href="futures">futures</a></h2>
       <tr>
         <td><a href="futures/draft-ietf-avtcore-rtp-over-quic.html" class="html draft-ietf-avtcore-rtp-over-quic" title="RTP over QUIC (RoQ) (HTML)">RTP over QUIC (RoQ)</a></td>
         <td><a href="futures/draft-ietf-avtcore-rtp-over-quic.txt" class="txt draft-ietf-avtcore-rtp-over-quic" title="RTP over QUIC (RoQ) (Text)">plain text</a></td>
-        <td>same as main</td>
+        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://mengelbart.github.io/rtp-over-quic-draft/draft-ietf-avtcore-rtp-over-quic.txt&amp;url_2=https://mengelbart.github.io/rtp-over-quic-draft/futures/draft-ietf-avtcore-rtp-over-quic.txt" class="diff draft-ietf-avtcore-rtp-over-quic">diff with main</a></td>
       </tr>
     </table>
     <h2>Preview for branch <a href="draft-ietf-avtcore-rtp-over-quic-08">draft-ietf-avtcore-rtp-over-quic-08</a></h2>