W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2016

[webrtc-pc] RTCP is mandatory, but not always implemented in legacy systems

From: Varun Singh via GitHub <sysbot+gh@w3.org>
Date: Fri, 25 Nov 2016 12:46:01 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-191695417-1480077960-sysbot+gh@w3.org>
vr000m has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== RTCP is mandatory, but not always implemented in legacy systems ==
The IETF draft rtp-usage mandates RTCP, although there are several 
middleboxes that send: no RTCPs, only RTCP Sender Reports, or only 
RTCP Receiver Reports,  when handling bi-directional media.

Is the expectation that any of these cases should work?

>From the API perspective, it is likely that these systems do not 
support mux-ing, and will set the `negotiate` flag in 
RTCRtcpMuxPolicy, however, they may not receive any RTCP. Are the 
stacks robust to this?

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/951 using your GitHub account
Received on Friday, 25 November 2016 12:46:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:49 UTC