webrtcbin: Expose SCTP Transport
authorJohan Sternerup <johast@axis.com>
Mon, 3 May 2021 08:45:42 +0000 (10:45 +0200)
committerGStreamer Marge Bot <gitlab-merge-bot@gstreamer-foundation.org>
Wed, 25 Aug 2021 13:20:22 +0000 (13:20 +0000)
commit7f9bb150555606230f00b2caa0894243859f19d8
treeeec31554c802562b38dbb57d3a527d8e6ed5c191
parent67a49be61fadaf264daf08619d66e92d86d9a333
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: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/2214>
docs/plugins/gst_plugins_cache.json
ext/webrtc/gstwebrtcbin.c