Re: [webrtc-stats] Map out implementation status of getStats and make a plan (#595)

I've updated the [report mentioned above](https://w3c.github.io/webrtc-interop-reports/webrtc-stats-report.html) with data collected from the WPT test run.

In the end, the following stats seems to have no implementation (or at least no implementation detected by the test):
* unimplemented stats types:
  * csrc
  * transceiver
  * sender
  * receiver
  * sctp-transport
   * ice-server
* unimplemented stats fields:
  * codec:
    * codecType
  * inbound-rtp:
    * packetsDiscarded
    * packetsRepaired
    * burstPacketsLost
    * burstPacketsDiscarded
    * burstLossCount
    * burstDiscardCount
    * burstLossRate
    * burstDiscardRate
    * gapLossRate
    * gapDiscardRate
    * partialFramesLost
    * fullFramesLost
    * frameBitDepth
    * voiceActivityFlag
    * averageRtcpInterval
    * packetsFailedDecryption
    * packetsDuplicated
    * perDscpPacketsReceived
    * sliCount
    * totalProcessingDelay
    * estimatedPlayoutTimestamp
    * totalSamplesDecoded
    * samplesDecodedWithSilk
    * samplesDecodedWithCelt
  * outbound-rtp:
    * senderId
    * rid
    * lastPacketSentTimestamp
    * packetsDiscardedOnSend
    * bytesDiscardedOnSend
    * fecPacketsSent
    * targetBitrate
    * frameBitDepth
    * framesDiscardedOnSend
    * totalSamplesSent
    * samplesEncodedWithSilk
    * samplesEncodedWithCelt
    * voiceActivityFlag
    * averageRtcpInterval
    * qualityLimitationDurations
    * perDscpPacketsSent
    * sliCount
  * remote-inbound-rtp:
    * packetsDiscarded
    * packetsRepaired
    * burstPacketsLost
    * burstPacketsDiscarded
    * burstLossCount
    * burstDiscardCount
    * burstLossRate
    * burstDiscardRate
    * gapLossRate
    * gapDiscardRate
    * framesDropped
    * partialFramesLost
    * fullFramesLost
    * totalRoundTripTime
    * fractionLost
    * reportsReceived
    * roundTripTimeMeasurements
  * remote-outbound-rtp:
    * transportId
    * codecId
    * reportsSent
  * media-source:
    * relayedSource
    * echoReturnLoss
    * echoReturnLossEnhancement
    * bitDepth
    * frames
  * peer-connection:
    * dataChannelsRequested
    * dataChannelsAccepted
  * transport:
    * rtcpTransportStatsId
    * iceRole
    * iceLocalUsernameFragment
    * iceState
    * tlsGroup
  * candidate-pair:
    * packetsSent
    * packetsReceived
    * firstRequestTimestamp
    * lastRequestTimestamp
    * lastResponseTimestamp
    * availableIncomingBitrate
    * circuitBreakerTriggerCount
    * retransmissionsReceived
    * retransmissionsSent
    * consentExpiredTimestamp
    * packetsDiscardedOnSend
    * bytesDiscardedOnSend
    * requestBytesSent
    * consentRequestBytesSent
    * responseBytesSent
  * local-candidate:
    * url
    * relayProtocol
  * remote-candidate:
    * url
    * relayProtocol
  * certificate:
    * issuerCertificateId

A good next steps would be to map these gaps with implementations plans (e.g. related bugs in browser trackers); I also suspect some additional semantic grouping of the fields above might help move forward some of the conversations.

-- 
GitHub Notification of comment by dontcallmedom
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/595#issuecomment-777557331 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 11 February 2021 15:08:55 UTC