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

Hi,


>>  8. Overloading connection-address would be dicey, since it ruins the
>>     ability to send different streams to different places. While WebRTC
>>     might not care too much about these use cases, they *are* important
>>     in other contexts.
>
> 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.
>
> IMO we *could* use an invalid address (pick one) as the indicator if the
> port number is a problem.


0.0.0.0


Regards,


Christer


> In summary: of the above options, the strongest option still seems to be
> "port," followed (perhaps) by "proto." We could probably force "media"
> or "addrtype" to work, but these would be pretty messy. I think "number
> of ports" and "nettype" are at high risk of being ignored by non-bundle
> implementations (i.e., they won't trigger the failure we want), and we
> need to maintain the existing meanings for "fmt" and "connection-address".
>
> Even more tersely: if we don't want to port zero, I think the only other
> realistic option is registering new "proto" values.
>
> /a
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic