w3c/webrtc-stats Issues

Last updated May 17, 2024, 5:59:06 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

13 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#62	Additional ICE metrics for pacing STUN packets	❌	7.7 years	7.6 years
#572	Security considerations need to mention portscanning as an issue	❌	4 years	4 years
#593	bytesReceived for local inbound could have a clearer definition	❌	3.3 years	3.3 years
#642	guidelines for getStats() results caching/throttling are a bit vague	❌	1.9 years	1.9 years
#665	remoteTimestamp does not specify how to derive the RTCP SR NTP timestamp	❌	1.7 years	1.7 years
#674	Codec stats reveal hardware information which could be used for fingerprinting	❌	1.7 years	1.7 years
#768	Stats example uses confusing variable names	❌	9.2 months	9 months
#770	Exposing audio interruption metrics to JavaScript	❌	7.3 months	7 months
#771	Define a mechanism for setting the trigger duration for a video freeze	❌	7.3 months	7 months
#783	raddr+rport can be set for peer-reflexive candidates as well	❌	2.7 months	2.5 months
#784	Should RTCRtptransceiver.stop() cause inbound-rtp stats to disappear?	❌	2.6 months	2.4 months
#785	RTCCodecStats.clockRate - media sampling rate or the codec clock rate?	❌	2.5 months	2.3 months
#786	RTCStats.timestamp - fingerprinting and since epoch	❌	2.3 months	2.1 months