- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Jun 2017 20:54:54 +0000
- To: public-ortc@w3.org
aboba has just created a new issue for https://github.com/w3c/ortc: == Behavior when calling send() or receive() again == Currently, both the send() and receive() methods allow those methods to be called multiple times with the same RtpSender/RtpReceiver object. However, the specification is not very clear about the expected behavior. For example, statements such as "have the sender switch to sending using withParameters" are a bit vague: 1. If send() specifies new SSRCs, this will also imply a new sequence number space, which the receiver would need to be prepared for. Does calling receive() again prepare the receiver for such a sequence number discontinuity? 2. If new SSRCs are not specified, does this imply that the SSRC is unchanged from the previous send() method call, or that the browser should choose a different SSRC and a new sequence number space? Does the remote peer need to call receive() again to be prepared for this? Please view or discuss this issue at https://github.com/w3c/ortc/issues/713 using your GitHub account
Received on Thursday, 15 June 2017 20:55:00 UTC