- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Jun 2024 10:38:42 +0000
- To: public-webrtc-logs@w3.org
@tonyherre "the exact value sent on the wire": for a potential "Use Case 3: RTP Forwarding", would the "sequence number" be defined as the 16-bit value in the RTP header or RFC 3711's "packet index": 2^16 * ROC + SEQ? One concern about allowing the application to set SEQ arbitrarily is the potential for the sender and receiver ROC to get out of sync, or for the "packet index" to be set outside the rekey window, causing SRTP decryption failures on the receiver. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/43#issuecomment-2144864369 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 10:38:42 UTC