diff --git a/draft-ietf-avtcore-rtp-over-quic.md b/draft-ietf-avtcore-rtp-over-quic.md
index f2977da..d00a37c 100644
--- a/draft-ietf-avtcore-rtp-over-quic.md
+++ b/draft-ietf-avtcore-rtp-over-quic.md
@@ -602,17 +602,6 @@ to unintentionally skipping one or more frames.
 > STOP\_SENDING, because STOP\_SENDING does not include an offset which would
 > allow signaling where retransmissions should continue.
 
-> **Editor's note:** Instead of using RESET\_STREAM and STOP\_SENDING frames,
-> RoQ senders and receivers might benefit from negotiating the use of the QUIC
-> extensions defined in {{?I-D.draft-ietf-quic-reliable-stream-reset-01}} and
-> {{?I-D.draft-thomson-quic-enough-00}}. These extensions provide two new frame
-> types, the CLOSE\_STREAM and the ENOUGH frame, equivalent to RESET\_STREAM and
-> STOP\_SENDING, respectively, but with an additional offset. The offset
-> indicates the point to which data will be reliably retransmitted, while
-> everything following might be dropped. Using CLOSE\_STREAM and ENOUGH instead
-> of RESET\_STREAM and STOP\_SENDING could prevent accidentally stopping
-> retransmissions for preceding frames.
-
 A translator that translates between two endpoints, both connected via QUIC,
 MUST forward RESET\_STREAM frames received from one end to the other unless it
 forwards the RTP packets on QUIC datagrams.