Skip to content

Commit

Permalink
Clarify ROQ_EXPECTATION_UNMET usage
Browse files Browse the repository at this point in the history
  • Loading branch information
mengelbart committed May 3, 2024
1 parent 94d18d0 commit dd40c78
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion draft-ietf-avtcore-rtp-over-quic.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit dd40c78

Please sign in to comment.