All things related to multicast

[Greg Shepherd <>]

On Wed, May 6, 2009 at 8:16 AM, George Bray 
<>
 wrote:
> On Wed, May 6, 2009 at 9:42 PM, Greg Shepherd 
> <>
>  wrote:
>> Can you send your source address so that I may at least check RPF to
>> see why I don't have your SAs?
>
> The machine putting it on the wire is 150.203.164.103

Thanks!

We found an MSDP peering session down which is why we don't have the
SA for your source.

BUT this illuminates an important question. If someone is sourcing
one-to-many content, even if not using the SSM group range,
couldn't/shouldn't the SDP file still contain the source address? If
so, any application with IGMPv3 support (or AMT) could join the SPT
without depending on MSDP. I'm guessing the SDP file was created
automatically by the streaming device/software and is strictly
following the ASM service model (even if it does support SSM). Until
the streaming vendors begin offering this as a feature, the sdp file
could still be hacked manually to add src.

Time for a thread on mmusic.

Greg


> --
> George Bray, The Australian National University, Canberra, Australia.
>