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

Re: 'remoteTrackId' added to transceiver

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Mon, 11 Sep 2017 06:50:06 +0000
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
CC: WebRTC WG <public-webrtc@w3.org>
Message-ID: <HE1PR07MB09700D979F0426C9B67D2B00C9680@HE1PR07MB0970.eurprd07.prod.outlook.com>
On 01/09/17 16:08, Cullen Jennings (fluffy) wrote:
> I do not understan what this is or how it relates to the MSID information in the SDP.  I doubt I will have any objection to adding this, it just seems to need some more information about what it is. Does JSEP need to say more about this ?

I just filed https://github.com/w3c/webrtc-pc/issues/1588 to keep track 
of this.

//Stefan

> 
> 
>> On Sep 1, 2017, at 3:27 AM, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:
>>
>> Hi all,
>>
>> yesterday we merged a PR [1] that introduced a 'remoteTrackId' readonly
>> attribute on the RTCRtpTransceiver. This property is intended to reflect
>> the id signaled in the (latest) SDP exchange for the received track (if
>> any) on the RTCRtpTransceiver. As you know the application can nowadays
>> create an RTCRtpTransceiver, which in turn has an RTCRtpReceiver with a
>> track, before any SDP exchanges. That track has an 'Id', which does (of
>> course) not reflect what is eventually signaled in the SDP, and since
>> the Id of a track is immutable it can't be updated once SDPs are exchanged.
>>
>> The 'remoteTrackId' can be viewed in context at [2].
>>
>> While we think this addition make a lot of sense we realize that we may
>> have acted a bit quickly here. Please let us know if you think more
>> discussion is needed.
>>
>> Stefan
>>
>> [1] https://github.com/w3c/webrtc-pc/pull/1567
>> [2]
>> https://rawgit.com/w3c/webrtc-pc/master/webrtc.html#rtcrtptransceiver-interface
>>
> 
> 
Received on Monday, 11 September 2017 06:50:33 UTC

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