From dd40c785239ed0e332ef048bd23af9543f276afc Mon Sep 17 00:00:00 2001 From: Mathis Engelbart Date: Fri, 3 May 2024 18:21:52 +0200 Subject: [PATCH] Clarify ROQ_EXPECTATION_UNMET usage --- draft-ietf-avtcore-rtp-over-quic.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-avtcore-rtp-over-quic.md b/draft-ietf-avtcore-rtp-over-quic.md index d68379f..0fd6f3c 100644 --- a/draft-ietf-avtcore-rtp-over-quic.md +++ b/draft-ietf-avtcore-rtp-over-quic.md @@ -666,7 +666,7 @@ credits it will have to provide to the sending peer, and how rapidly it must pro Senders can also transmit RTP packets in QUIC DATAGRAMs, using a QUIC extension described in {{!RFC9221}}. DATAGRAMs can only be used if the use of the DATAGRAM extension was successfully negotiated during the QUIC handshake. -If the QUIC extension was negotiated using a signaling protocol, but that extension was not negotiated during the resulting QUIC handshake, an endpoint MAY close the connection with the ROQ\_EXPECTATION\_UNMET error code. +If the DATAGRAM extension was negotiated using a signaling protocol, but was not also negotiated during the resulting QUIC handshake, an endpoint can close the connection with the ROQ\_EXPECTATION\_UNMET error code. DATAGRAMs preserve application frame boundaries. Thus, a single RTP packet can be mapped to a single DATAGRAM without additional framing.