Re: [MMUSIC] Simulcast worries: Fallback in the a=rid language

[Peter Thatcher <[e-mail]>]

But if you have max-goats and max-dogs and max-cats and the answerer
supports max-dogs but not max-goats or max-cats,  how can it structure it
to offer all the combinations of what might work and what might not?

On Wed, Oct 21, 2015 at 11:35 AM, Martin Thomson <[e-mail]>
wrote:

> On 21 October 2015 at 06:57, Harald Alvestrand <[e-mail]>
> wrote:
> > 1 - Toss all RIDs that it cannot parse fully
>
> This.
>
> If you were able to handle options that didn't limit goats, then you
> can add an alternative profile that doesn't include any max-goats
> constraints:
>
> a=rid:1 recv max-goats=47;max-fr=50
> a=rid:2 recv max-goats=22;max-fr=20
> a=rid:3 send max-goats=44;max-fr=20
> a=rid:4 send max-goats=22;max-fr=10
> a=rid:5 recv max-fr=10
> a=rid:6 recv max-fr=5
> a=rid:7 send max-fr=10
> a=rid:8 send max-fr=5
> a=simulcast: send rid=3;4,7;8 recv rid=1;2,5;6
>
> (I've probably gotten the syntax off here, but I hope that this is clear
> enough.
>
> _______________________________________________
> mmusic mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mmusic
>