Re: [rtcweb] draft-roach-mmusic-unified-plan-00 expired

[Iñaki Baz Castillo <[e-mail]>]

2014/1/20 Paul Kyzivat <[e-mail]>:
> What is it that troubles you about this.
>
> I guess from prior comment that you want to add more m-lines in the answer?
>
> But O/A is a negotiation/handshake. If you include extra m-lines in the
> answer then there is no completion to the negotiation of those.

Having two endpoints establshing a media session, the only they need is:

- To decide a transport or transports for sending media one to each other.
- To tell one to each other what it is sending.

SDP is good (enough) in classic and simple communications in which
both endpoints send and receive something similar (i.e. one single
audio track in both directions).

But nowadays we want that endpoint-A can send just one audio track and
one video track and receive 8 audio tracks and 8 video tracks from
endpoint-B. If endpoint-A makes the SDP offer, it "should" include 16
m lines:

- 1 audio line for sending its single audio track and receive *one* of
the remote tracks (a=sendrecv).
- 7 audio tracks just for receiving the rest of the remote audio
tracks (a=recvonly).
- Same for video.

This is completely unnecessary if we skip the SDP tradition. There is
no need at all for endpoint-A to tell endpoint-B "you can send me up
to 8 audio tracks since I have added 8 m audio lines in my SDP offer,
otherwise you can only send me a single audio track, but you can send
me later a re-offer".

This is something that ORTC "fixes".

Regards.



-- 
Iñaki Baz Castillo
<[e-mail]>