- From: Philipel-WebRTC via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Jun 2024 12:09:40 +0000
- To: public-webrtc-logs@w3.org
> Conservative me would be more comfortable if RTP sequence number was always set by the platform, and couldn't be changed by the app. AFAIK the recommendation of starting with a random sequence number is not relevant when SRTP is used. I'm certainly not an expert, but I really don't want to bring in limitations based on outdated advice. If the app can't set the sequence number then client-node networks will be limited, no out-of-order forwarding, no stream filtering. We should probably have some form of limitation to avoid breaking encryption and authentication. I think having a window of acceptable sequence numbers and checking that no duplicate is sent within that window should work. -- GitHub Notification of comment by Philipel-WebRTC Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/43#issuecomment-2145031954 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 12:09:41 UTC