You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the use case where a client acts as a node in a network (receiving + forwarding) it is important to preserve sequence number gaps in case of loss. Currently the sender has no way of controlling the outgoing RTP sequence number.
The text was updated successfully, but these errors were encountered:
The assumptions is that a client can create RTP packets, but if we want to reuse a packet for forwarding (avoid copying it) then having mutable fields is probably necessary.
In the use case where a client acts as a node in a network (receiving + forwarding) it is important to preserve sequence number gaps in case of loss. Currently the sender has no way of controlling the outgoing RTP sequence number.
The text was updated successfully, but these errors were encountered: