W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2023

Re: [webrtc-pc] Why is RTCIceCandidatePairStats.totalRoundTripTime mandatory to implement, but not responsesReceived? (#2819)

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Tue, 21 Feb 2023 16:51:12 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1438801336-1676998271-sysbot+gh@w3.org>
smoothedRoundTripTime is a SCTP-level equivalent of the [RTCP RTT](https://w3c.github.io/webrtc-stats/#dom-rtcremoteinboundrtpstreamstats-totalroundtriptime). Note that we don't ask for totalRoundTripTime on remote-inbound-rtp as MTI either.

These RTTs are a layer up from ICE in the stack and may differ if you have a middlebox that terminates ICE but does not (fully, there are opinions) terminate RTCP. In that case you have the STUN RTT between browser and middlebox while the RTCP RTT is between both browsers. See [this video](https://youtu.be/K8PNRB9J20I?t=240) which I think compares STUN RTT (on one leg of the call) to the E2E RTT for the whole call.

However, even if this is not MTI, web developers may start dropping support for browsers which do not support features such as this one.

GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2819#issuecomment-1438801336 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 February 2023 16:51:14 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:20:00 UTC