Re: [MMUSIC] What is an m-line?

[Martin Thomson <[e-mail]>]

On 15 May 2013 04:02, Colin Perkins <[e-mail]> wrote:
>> 1. an m-line represents a single RTP session
>>    (or at least the part of the session that touches the client)
>>    This appears to be consistent with the Plan B approach
>
> This is closest to my understanding, although an RTP session is defined by a shared SSRC space that can span multiple transport connections, so I don't think it's quite right. Perhaps "an m-line refers to one transport endpoint of a single RTP session"?

That's why I said "at least the part of the session that touches the
client", but this is probably more correct given that the same session
can have multiple transport endpoints on the same endpoint, described
in the same SDP as different m-lines.

> (For example, in a simple two-party voice-only call with RTCP there are distinct m-lines, with different transport endpoints, in the offer and the answer. But, since there is a shared SSRC space across the sending and receiving RTP flows - which there has to be for RTCP to work - you have one RTP session.)

This is a good point.  In offer/answer, this can clearly be two things
(as dictated by a=sendrecv).

I'd like to know how well this offer/answer usage scales.  Does this
extend to a three-party RTP session with the same characteristics?