- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Dec 2016 12:44:21 +0000
- To: public-webrtc-logs@w3.org
My thinking when I wrote this was that one codec would be referenced from multiple RTPStreams, and that this was the important way to find them. The RTPStreams do have a transport link (and it needs to be the same for all of them, or, as you say, PT will be meaningless). The case I can see is for negotiated codecs (such as CN) which are not currently actively used by any RTPStream (much like the case for candidates that are not in a candidate pair). It seems logical to have the link for that case, with a note that it needs to be consistent with RTPStreams' transport links. isRemote is not a good name, but I agree that it seems reasonable to differentiate between encode-only, encode-decode and decode-only codecs. This property isn't inferrable from the SDP description, but is knowable from the local implementation. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/109#issuecomment-267586730 using your GitHub account
Received on Friday, 16 December 2016 12:44:32 UTC