From 7f9bb150555606230f00b2caa0894243859f19d8 Mon Sep 17 00:00:00 2001 From: Johan Sternerup Date: Mon, 3 May 2021 10:45:42 +0200 Subject: webrtcbin: Expose SCTP Transport Being able to access the SCTP Transport object from the application means the application can access the associated DTLS Transport object and its ICE Transport object. This means we can observe the ICE state also for a data-channel-only session. The collated ice-connection-state on webrtcbin only includes the ICE Transport objects that resides on the RTP transceivers (which is exactly how it is specified in https://w3c.github.io/webrtc-pc/#rtciceconnectionstate-enum). For the consent freshness functionality (RFC 7675) to work the ICE state must be accessible and consequently the SCTP transport must be accessible for enabling consent freshness checking for a data-channel-only session. Part-of: --- docs/plugins/gst_plugins_cache.json | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'docs') diff --git a/docs/plugins/gst_plugins_cache.json b/docs/plugins/gst_plugins_cache.json index dd166e491..86dd1c5bf 100644 --- a/docs/plugins/gst_plugins_cache.json +++ b/docs/plugins/gst_plugins_cache.json @@ -227981,6 +227981,17 @@ "type": "GstWebRTCSessionDescription", "writable": false }, + "sctp-transport": { + "blurb": "The WebRTC SCTP Transport", + "conditionally-available": false, + "construct": false, + "construct-only": false, + "controllable": false, + "mutable": "null", + "readable": true, + "type": "GstObject", + "writable": false + }, "signaling-state": { "blurb": "The signaling state of this element", "conditionally-available": false, -- cgit v1.2.1