[webrtc-rtptransport] Sequence number: constraints? (#43)

aboba has just created a new issue for https://github.com/w3c/webrtc-rtptransport:

== Sequence number: constraints?  ==
Are there any constraints on the value of sequence numbers that can be set?  For example: 

1. In RTP, [initial sequence numbers SHOULD be unpredictable](https://datatracker.ietf.org/doc/html/rfc3550#section-5.1).  Can an application set the initial sequence number, or is this provided by the browser? 

2. Subsequently, can an application set the sequence number to an arbitrary value, or are there constraints that need to be obeyed?  For example: 
     a. Is it possible to set the sequence number to a previous (duplicate) value without the ROC having incremented? 
     b. Can the sequence number be set to an arbitrary value or need it be set within a window?

Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/43 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 3 June 2024 01:50:28 UTC