Design consideration for inactive SSRCs and inactive transports about webrtc-stats HOT 3 CLOSED

Copying my comment from the issue #68:

With the frozen timestamps, an app can filter out the older candidates, assuming the app has some idea about how often it queries or when it last queried the stats.

Although one concern I do have (and perhaps could be solved in a different way) is if the ice candidate is currently inactive and was active in the past, we do not really know when it was last active. We perhaps need a lastPacketSentTimestamp, lastPacketReceivedTimestamp or similar

from webrtc-stats.

Would this timestamp be valid for only local candidates, or would we also update the remote candidate of a pair? Or perhaps it's on candidate pairs? (a candidate can't be active without being part of a pair).

from webrtc-stats.

I will add the timestamps to the candidate pair stats.

from webrtc-stats.