Open Bug 1307996 Opened 4 years ago Updated 3 months ago

Implement the RTCDtlsTransport interface

Categories

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

defect

Tracking

()

Tracking Status
firefox52 --- wontfix
Blocking Flags:

People

(Reporter: drno, Assigned: mjf)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-needed, Whiteboard: [spec-compliance])

Per latest webrtc spec we are missing the RTCDtlsTransport interface.
https://w3c.github.io/webrtc-pc/#rtcdtlstransport-interface

At least partially implementing this interface, specifically the |state| attribute and |onstatechange| event, would allow WebRTC site to detect for the first time if something went wrong with DTLS. Implementing these two should be easy as it only means we would expose internal variables of the transportlayerdtls code.

Allowing to fetch the remote certificate and getting a handle to the RTCIceTransport (bug 1307994) is probably a little bit more effort.
backlog: --- → webrtc/webaudio+
Rank: 20
Whiteboard: [spec-compliance]
Mass wontfix for bugs affecting firefox 52.
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Blocks: 1278299
Blocks: 1258411

We had to disable some stuff over in wpt (bug 1517444) for this recently.

See Also: → 1517444

Is this still on the roadmap?

With RTCDtlsTransport API: getRemoteCertificates the networking stack used by js-ipfs (js-libp2p) should be able to let WebRTC handle encryption & stream muxing in the browser, improving overall performance.

Roughly speaking, this is on the roadmap after get/setParameters is brought up to spec.

Assignee: nobody → mfroman
You need to log in before you can comment on or make changes to this bug.