Re: [MMUSIC] RFC 5576 is da answah

[Paul Kyzivat <[e-mail]>]

On 11/21/12 11:50 AM, Jonathan Lennox wrote:

>> [BA] While the advice above seems generally sensible, the meaning of
>> "prepared to receive" isn't very clear.  Implementations may differ in
>> how they respond if they don't receive any a=ssrc attributes.   For
>> example, an implementation might only be able to deal with a single
>> undeclared source or perhaps not at all.  So being "prepared to
>> receive" isn't enough to be able to deal with an RTP translator, for
>> example.
>
> Yes, you'd need a way to explain what you're prepared to receive;
> max-ssrc could handle this.

It doesn't help me very much to know you are "prepared to receive" a 
bunch of media streams unless there is also a way to negotiate what they 
are for. You may be prepared to receive streams for purposes 
incompatible with the streams I am prepared to transmit.

Using a=ssrc it is possible to negotiate things about each stream. For 
those that aren't negotiated that way, ISTM that there must be some 
other mechanism for negotiating semantics. This could be SDP signaling 
that indicated "all otherwise unspecified streams are ...", or the 
semantics could be conveyed via some other protocol (e.g. CLUE) or by 
prior agreement.

	Thanks,
	Paul