Open Bug 1278299 Opened 4 years ago Updated 1 year ago

Implement RTCSctpTransport and RTCPeerConnection.sctp

Categories

(Core :: WebRTC: Networking, task, P3)

task

Tracking

()

People

(Reporter: sheppy, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: dev-doc-needed)

We need to add the sctp property to RTCPeerConnection and implement RTCSctpTransport, per:

http://w3c.github.io/webrtc-pc/#rtcpeerconnection-interface-extensions
http://w3c.github.io/webrtc-pc/#rtcsctptransport-interface
For what it's worth, I've written the overview page for this interface as currently specced:

https://developer.mozilla.org/en-US/docs/Web/API/RTCSctpTransport

The rest of the work will wait until it's implemented.
Rank: 25
Priority: -- → P2
Looks to me like we first need to implement the RTCDtlsTransport before implementing RTPSctpTransport. Do we have a ticket for RTCDtlsTransport already (I only found bug 1258411, which refers "only" to documenting it)?
Probably not then. I filed my bugs for tracking docs work on these interfaces not realizing they weren't implemented yet. You'll probably want a bug for that. I can file it if you wish, or you guys can do it (which may make more sense, but up to you).
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
FYI, this is the PR for the shim in adapter: https://github.com/webrtc/adapter/pull/702
Depends on: 1307996
Type: defect → task
You need to log in before you can comment on or make changes to this bug.