- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Mar 2017 21:15:24 +0000
- To: public-webrtc-logs@w3.org
Related: I worry about this writeup a bit because the use case of a single CSRC has turned out to be important (I thought it would be an edge case). The problem is that when there's a single CSRC present, the text isn't clear about whether the SSRC, the CSRC or both are present in the list; when there is no CSRC, the SSRC is present (and has a computed volume); when there are two CSRCs, the CSRCs are present (and volume is null when not presented by an RTP extension). When there is one CSRC, there is .... what? One solution might be to pull the RTCRtpContributingSource information for the SSRC (which will always have a volume) out into a separate attribute, and never have it present in the ContributingSources. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1090#issuecomment-288221071 using your GitHub account
Received on Tuesday, 21 March 2017 21:15:31 UTC