Thanks to visit codestin.com
Credit goes to github.com

Skip to content

data channel ids are set before SCTP init is exchanged #3071

@fippo

Description

@fippo

w3c/webrtc-stats#805 (comment)

I am a bit surprised that no actual DTLS negotiation is required but that seems consistent across browsers?
https://w3c.github.io/webrtc-pc/#sctp-transport-connected might need to be updated as it currently says

Once an SCTP transport is connected, meaning the SCTP association of an RTCSctpTransport has been established

but as https://jsfiddle.net/fippo/gLs015hm/6 shows the SCTP transport exists without packets being exchanged.
The specification is safer as it since it avoids my potential (theoretical?) concern about role conflicts but browsers behave differently and seem to determine the odd/even based on the DTLS role negotiated in the SDP (which seems ok)

I can volunteer a WPT but from the screenshot looks like implementations agree.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions