Transport objects should be added to the specification

[dontcallmedom]

Originally reported on W3C Bugzilla ISSUE-27224 Mon, 03 Nov 2014 20:33:59 GMT
Reported by Harald Alvestrand
Assigned to

Reference presentation:

https://www.w3.org/2011/04/webrtc/wiki/images/6/6c/WebRTC_RTCSender-Receiver%2C_TPAC_2014.pdf slide 9

This has been presented to the WG, and won support, but needs to be reviewed in detail before integrating.

[alvestrand]

Closed by merging RTPSender/Receiver in #175

[dontcallmedom]

@alvestrand I think this one is about interfaces that haven't been added yet to the document (pasting from the referenced slide):

partial interface RTCRtpSender  {
  readonly  attribute RTCDtlsTransport  transport;
};
partial interface RTCRtpReceiver  {
  readonly attribute RTCDtlsTransport  transport;
};
interface RTCDtlsTransport  {
  readonly attribute RTCIceTransport transport; // the associated ICE transport
  readonly attribute RTCDtlsTransportState state; // current DTLS state (e.g. connected, failed)
  sequence<ArrayBuffer> getRemoteCertificates(); // the certs in use by the remote side
  attribute EventHandler? onstatechange;
};
interface RTCIceTransport {
  readonly attribute RTCIceConnectionState state; // the current ICE state
  RTCIceCandidatePair? getSelectedCandidatePair(); // the currently active candidate pair  
  attribute EventHandler? onstatechange;
  attribute EventHandler? onselectedcandidatepairchange;
};

[alvestrand]

We have different bugs for those - #188 is specific to DTLSTransport / IceTransport.
Github doesn't seem to have a "merged to issue" mechanism.

[dontcallmedom]

wfm