diff --git a/draft-ietf-avtcore-rtp-over-quic.md b/draft-ietf-avtcore-rtp-over-quic.md
index 58de9c0..b04a78d 100644
--- a/draft-ietf-avtcore-rtp-over-quic.md
+++ b/draft-ietf-avtcore-rtp-over-quic.md
@@ -1191,6 +1191,29 @@ The "rtp-mux-quic" string identifies RoQ:
 
 --- back
 
+# List of optional QUIC Extensions
+
+The following is a list of QUIC protocol extensions that might be beneficial for
+RoQ, but are not required by RoQ.
+
+* *An Unreliable Datagram Extension to QUIC* {{?RFC9221}}. Without support for
+  unreliable datagrams, RoQ cannot use the encapsulation specified in
+  {{quic-datagrams}}, but can still use QUIC streams as specified in
+  {{quic-streams}}.
+* A version of QUIC receive timestamps can be helpful for improved jitter
+  calculations and congestion control.
+  * *Quic Timestamps For Measuring One-Way Delays*
+    {{?I-D.draft-huitema-quic-ts}}
+  * *QUIC Extension for Reporting Packet Receive Timestamps*
+    {{?I-D.draft-smith-quic-receive-ts}}
+* *QUIC Acknowledgement Frequency* {{?I-D.draft-ietf-quic-ack-frequency}} can
+  be used by a sender to optimize the acknowledgement behaviour of the receiver,
+  e.g., to optimize congestion control.
+* *Signaling That a QUIC Receiver Has Enough Stream Data*
+  {{?I-D.draft-thomson-quic-enough}} would allow an RoQ receiver to use an offset
+  in STOP\_SENDING, to tell the RoQ sender which media frame does not need to be
+  retransmitted.
+
 # Experimental Results
 
 An experimental implementation of the mapping described in this document can be