Re: [rtcweb] inactive m-lines in draft-ietf-rtcweb-jsep-05

[Martin Thomson <[e-mail]>]

On 29 October 2013 08:05, Paul Kyzivat <[e-mail]> wrote:
> How is this expected to work? Is the browser supposed to do this in the
> absence of a MediaStreamTrack?

As I understand it, and my understanding is probably imperfect [22],
the idea is that at all points where an offer or answer is
constructed, the using application has access to MediaStreamTrack
objects that relate to the various m-lines.  Mostly.

That is, prior to creating an offer, you have the MediaStreamTrack
instances that relate to what you are sending.  And Prior to creating
an answer, you have both the tracks you want to send and the ones that
you want to receive.  Adam has proposed [2] that enabling or disabling
these tracks causes the appropriate a=sendonly/etc. attribute to be
set.

The only case that is a little strange is the one relating to the
received streams when creating an initial offer, where you use the
OfferToReceiveAudio or OfferToReceiveVideo constraint in order to
indirectly control the send/recv attributes.


[22] by which I do not offer as a failing on my part, ...
[2] http://lists.w3.org/Archives/Public/public-webrtc/2013Oct/0058.html