All things related to multicast

[Hugh LaMaster <>]

On Wed, 7 Jul 1999, Bill Fenner wrote:

> 
> >> a) MSDP could be configured for a minimum TTL required before
> >>    sending an SA
> >
> >It can, at least in Cisco's implementation.  "ip msdp
> >ttl-threshold <neighbor> <threshold>".
> 
> I'm fairly sure this only controls what packets are allowed to be
> forwarded inside SA encapsulation, not whether or not SA messages are
> sent at all.
> 
> You're right that discovery protocols mesh poorly with sparse mode
> (particularly if they try to do expanding-ring searches).  You effectively
> need to have a PIM domain per smallest administrative area.

I confess I'm a little confused about this SVRLOC traffic.

I read RFC2608, which says that the multicast address to be used 
is address 239.255.255.253  port 427.  Yet, the address
table shows 224.0.1.22 as assigned to "SVRLOC", and, indeed, there
is increasing traffic on that group, to port 427.

239.255.255.253 makes sense to me, since that will normally
stay inside the most restrictive administrative scope 
boundary.  But, 224.0.1.22 makes no sense to me.

Can anyone shed any light on this?  Apparently, software is 
shipping using 224.0.1.22.  

What am I missing?



--
 Hugh LaMaster, M/S 233-21,    ASCII Email: 

 NASA Ames Research Center     Or:          

 Moffett Field, CA 94035-1000  No Junkmail: USC 18 section 2701
 Phone: 650/604-1056           Disclaimer:  Unofficial, personal *opinion*.