- From: Varun Singh via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Jun 2019 15:18:14 +0000
- To: public-webrtc-logs@w3.org
RTCP cannot be disabled. Or do you mean it’s not implemented? On Fri, 14 Jun 2019 at 17.27, henbos <notifications@github.com> wrote: > inbound-rtp.fractionLost is based on the interval between sent RTCP > packets per RFC3550 Appendix A.3 > <https://tools.ietf.org/html/rfc3550#appendix-A.3>. It is not clear what > to do if RTCP is disabled. Chrome currently does "since last call to > getStats" which is clearly wrong. > > Considering this does not seem very useful outside of RTCP, and we already > have packetsLost on the inbound-rtp, I propose fractionLost should be > undefined in this case. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webrtc-stats/issues/446?email_source=notifications&email_token=AAC5LEX25PIKZ7YQQJIIRILP2OTETA5CNFSM4HYIMESKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZSHZVA>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAC5LERQTSINVTE5IHHXIL3P2OTETANCNFSM4HYIMESA> > . > -- Sent from Gmail Mobile -- GitHub Notification of comment by vr000m Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/446#issuecomment-502149683 using your GitHub account
Received on Friday, 14 June 2019 15:18:15 UTC