Open
Bug 1278299
Opened 6 years ago
Updated 3 years ago
Implement RTCSctpTransport and RTCPeerConnection.sctp
Categories
(Core :: WebRTC: Networking, task, P3)
Core
WebRTC: Networking
Tracking
()
NEW
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
Reporter | ||
Comment 1•6 years ago
|
||
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.
Updated•6 years ago
|
Rank: 25
Priority: -- → P2
Comment 2•6 years ago
|
||
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)?
Reporter | ||
Comment 3•6 years ago
|
||
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).
Comment 4•5 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Comment 5•5 years ago
|
||
FYI, this is the PR for the shim in adapter: https://github.com/webrtc/adapter/pull/702
Updated•4 years ago
|
Depends on: RTCDtlsTransport
Comment 6•3 years ago
•
|
||
Now https://github.com/webrtcHacks/adapter/pull/702 I believe.
Updated•3 years ago
|
Type: defect → task
You need to log in
before you can comment on or make changes to this bug.
Description
•