All things related to multicast

[ken lindahl <>]

just last week, i learned of an IOS issue where (S,G) state is maintained
even after the sender has left the group (or even shutdown for that matter).
the uc berkeley msdp-peer that mark listed is running a version of IOS that
displays this behavior. i'm about 98% confident that the same is true
for the stanford msdp-peer. right now, the uc berkeley peer is announcing
529 unique senders, of which 147 aren't currently reachable. i'm willing
to be that many of the remaining 382 senders are not currently active in
any groups. so, i'll be upgrading IOS on the uc berkeley router asap,
tomorrow morning if not sooner.

even so, i too would like to see general consensus on which of these
groups is appropriate to restrict to campus and which are appropriate to
announce.

>224.2.3.4 78     ??

i'll have to look into that one. there are currently 69 sources for this
group, 66 of which are berkeley hosts. all of the berkeley hosts are on
two subnets in the CS dept here. this has the look of a local group that
should be using a 239/8 address.

ken

On Tue, 13 Jul 1999, Mark Fullmer 
<>
 wrote:
>Top 5 groups for 128.32.0.224 (Berkeley)
>-----------------------------
>
>224.0.1.22 261   SVRLOC.MCAST.NET
>224.0.1.35 254   SVRLOC-DA.MCAST.NET
>224.0.1.24 84    MICROSOFT-DS.MCAST.NET
>224.2.3.4 78     ??
>224.0.1.32 21    MTRACE.MCAST.NET
>
>Top 5 groups for 171.64.0.71 (Stanford)
>-----------------------------
>
>224.0.1.35 205   SVRLOC-DA.MCAST.NET
>224.0.1.22 158   SVRLOC.MCAST.NET
>224.0.1.2 120    SGI-DOG.MCAST.NET
>224.0.1.60 59    HP-DEVICE-DISC.MCAST.NET
>224.0.1.24 46    MICROSOFT-DS.MCAST.NET