- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Fri, 14 Aug 2015 17:51:12 +0000
- To: Cullen Jennings <fluffy@cisco.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Aug 14, 2015, at 08:06, Cullen Jennings <fluffy@cisco.com> wrote: > > There are two things here - the first (which you point out above) is UI to show active speaker in real time. I think this would be very good to have. > > The second is the audio levels attribute send in the RTP extension from the browser to switch. I think that is critical to have. Without that there is no way to start to enable conferences without keys and I think the WG should prioritize things that helps with privacy - this is one of them. [BA] The client-mixer extension (RFC 6464) is indeed very useful, which is why support is mandated in RTP-Usage Section 5.2.2. However the Mixer-Client extension (RFC 6465) is optional in RTP-Usage Section 5.2.3, and the API depends on that to provide audio levels for CSRCs.
Received on Friday, 14 August 2015 17:51:41 UTC