Re: [MMUSIC] Bundle-only, Port 0, and other options

[Christer Holmberg <[e-mail]>]

Hi,



>> I don't understand this last point. We are only talking about
>> bundle-only lines that are either going to use the address and port of
>> the bundle (defined elsewhere) or aren't going to be used at all.
>
> What I'm thinking about is something that defines a setup like this:
>
> ...
> a=group:BUNDLE a1 a2
> a=group:BUNDLE v1 v2
> ...
> m=audio ...
> c=IN IP4 1.1.1.1
> a=mid:a1
> ...
> m=audio ...
> c=IN IP4 1.1.1.1
> a=mid:a2
> ...
> m=video ...
> c=IN IP4 2.2.2.2
> a=mid:v1
> ...
> m=video ...
> c=IN IP4 2.2.2.2
> a=mid:v2
> ...
>
> Or, in plain English: we want to two audio streams to be bundled
> together and sent to 1.1.1.1; and the two video streams to be bundled
> together and sent to 2.2.2.2. And now I see what you're saying: if we
> just used 0.0.0.0 in the "bundle only" lines, then you'd get the
> transport address from the non-bundle-only sections in the bundle, just
> like we were proposing to do for the ports.

>
> So, yes, I agree that this would be a potentially viable way to put
> together a line that "won't work" for legacy clients; however, given
> that implementations may not check for "0.0.0.0" as a special value,
> their behavior is likely to be far more difficult to predict than using
> port 0 (which has well-defined, crystal clear semantics in legacy use).



It would have the same semantics also in bundle use - EXCEPT when used in that one initial Offer :)



Regards,



Christer