- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Oct 2017 14:07:40 +0000
- To: public-webrtc-logs@w3.org
The following commits were just pushed by aboba to https://github.com/w3c/webrtc-pc: * Describe how transport objects are assigned to senders/receivers. As decided in the June virtual interim, DTLS/ICE transport objects will only be created as a result of setting a local description. Also, applying an answer may change the mapping between media descriptions and transports (according to the rules in BUNDLE), which may result in `sender.transport` (for example) pointing to a different object than before. This PR puts the actual responsibility for figuring out the media/ transport mapping on BUNDLE, using the "media transport" term, which in this case is something that encapsulates the pair of ICE and DTLS transports. Note that BUNDLE itself does not use that term (yet), but it will, optimistically, if https://github.com/cdh4u/draft-sdp-bundle/pull/19 is merged. Note that this PR does not yet handle rollbacks, or RTCP mux negotiation. by Taylor Brandstetter https://github.com/w3c/webrtc-pc/commit/69ee2cdd9fad86bda16e470ba35fda252742f510 * Note that creating a transceiver doesn't create the transport objects. by Taylor Brandstetter https://github.com/w3c/webrtc-pc/commit/a212628da97d3853e241e68dbbcd475f4a638541 * Merge pull request #1623 from taylor-b/issue_1178_transport_creation Describe how transport objects are assigned to senders/receivers. by Bernard Aboba https://github.com/w3c/webrtc-pc/commit/da266a1928b74b8ec601056813e958fc9c840fd4
Received on Thursday, 19 October 2017 14:07:51 UTC