W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2016

[webrtc-pc] What is the appropriate behavior when a new track is added using and old trackid?

From: José Antonio Santos Cadenas via GitHub <sysbot+gh@w3.org>
Date: Mon, 22 Aug 2016 13:58:02 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-172459285-1471874280-sysbot+gh@w3.org>
jcaden has just created a new issue for 

== What is the appropriate behavior when a new track is added using 
and old trackid? ==
Imagine he have this sdp:

a=ssrc:1234 msid:stream_id_1 track_id_1
a=ssrc:1234 mslabel:stream_id_1
a=ssrc:1234 label:track_id_1
and then after a re-negotiation we have:


and then:

a=ssrc:4321 msid:stream_id_1 track_id_1
a=ssrc:4321 mslabel:stream_id_1
a=ssrc:4321 label:track_id_1

Note that a new m-line has been added with the same msid as the 
previous one, because the track used to generate the media si the 
same. Previous m-line has become inactive.

My first question is: Is this situation possible?

If it is possible. As the first remote track has become inactive 
because it has been removed, it can't emit media, but there should be 
an active track with the same msid. Should the receiver create a new 
track associated with the same id? Should it reject the negotiation 
containing the same track? or should it just drop the media because 
the track is already ended.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/754 using your GitHub account
Received on Monday, 22 August 2016 13:58:09 UTC

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