- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Thu, 07 Aug 2025 13:58:37 +0000
- To: public-webrtc-logs@w3.org
> For SCTP requiring that the `dataChannelIdentifier` is set should work with the caveat that negotiated channels show up early.
I agree for non-`{negotiated: true}` data channels obviously, since the `dataChannelIdentifier` is set going back to `"stable".
But https://jsfiddle.net/jib1/2qk9as1n/21/ shows adding `{negotiated: true, id: 7}` does not expose `"data-channel"` stats any earlier in Chrome and Safari today. I would not force the Firefox behavior on Chrome and Safari here only in this case, as this seems unnecessarily complicated.
> In practice, ... the existence and ID of datachannels has to live where the SCTP protocol engine lives
I'm supportive of of this interpretation. We should clarify the spec to say the [monitored object](https://w3c.github.io/webrtc-stats/#dfn-monitored-object) for these stats is the [underlying data transport](https://w3c.github.io/webrtc-pc/#dfn-data-transport) and not the `RTCDataChannel` JS object. It also seems consistent with exposure on going `"stable"`.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/805#issuecomment-3164324441 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 August 2025 13:58:37 UTC