- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2023 15:36:24 +0000
- To: public-webrtc@w3.org
docfaraday has just created a new issue for https://github.com/w3c/webrtc-stats: == RTCOutboundRtpStreamStats.headerBytesSent/totalPacketSendDelay and RTX seems underspecified == Spec explicitly says that we should be totaling up packetsSent, bytesSent, retransmittedPacketsSent, and retransmittedBytesSent. But what about headerBytesSent/totalPacketSendDelay? [headerBytesSent](https://www.w3.org/TR/webrtc-stats/#dom-rtcoutboundrtpstreamstats-headerbytessent) It seems pretty clear that this should include RTX, since spec says "headerBytesSent + bytesSent equals the number of bytes sent as payload over the transport.", and bytesSent accounts for RTX. [totalPacketSendDelay](https://www.w3.org/TR/webrtc-stats/#dom-rtcoutboundrtpstreamstats-totalpacketsenddelay) This probably ought to account for RTX as well. The only way I can see this metric being useful is by comparing it to packetsSent (over some time window), and packetsSent includes RTX packets. Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/747 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 March 2023 15:36:25 UTC