W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2017

[webrtc-pc] Pull Request: Describe how transport objects are assigned to senders/receivers.

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Tue, 10 Oct 2017 02:48:09 +0000
To: public-webrtc@w3.org
Message-ID: <pull_request.opened-145588128-1507603674-sysbot+gh@w3.org>
taylor-b has just submitted a new pull request for https://github.com/w3c/webrtc-pc:

== Describe how transport objects are assigned to senders/receivers. ==
Fixes #1178.

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.

See https://github.com/w3c/webrtc-pc/pull/1623
Received on Tuesday, 10 October 2017 02:48:01 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:52 UTC