All things related to multicast

[Alan Crosswell <>]

In http://www.abilene.iu.edu/content.cgi?page=mc-cookbook it says:

>This is the multicast-boundary list we presently use in Abilene, and
>there have been some suggestions for additional values for which we're
>soliciting feedback/consensus from the I2 community. The expressions
>below block sending RP announce and discovery packets and set the
>accepted administrative scoping to block 'local' multicast.
>
>        ip access-list standard multicast-boundary
>         deny   224.0.1.39
>         deny   224.0.1.40
>         deny   239.0.0.0 0.255.255.255
>         permit any

Is there a more up-to-date list of recommended groups to drop at the
boundary? For example, I noticed I am getting NTP from about 8 sources.

This is my current boundary which I just updated to include 239/8:

Standard IP access list 15 (Compiled)
    deny   224.0.1.39 (5 matches)
    deny   224.0.1.40 (5 matches)
    deny   239.0.0.0, wildcard bits 0.255.255.255 check=29
    permit any (24 matches)

And this is what I have on outbound msdp:

    deny ip any host 224.0.1.35 (692530 matches)
    deny ip any host 224.0.1.22 (761960 matches)
    deny ip any host 224.0.1.24 (797676 matches)
    deny ip any host 224.0.1.60 (45019 matches)
    deny ip any host 224.0.1.2 (744 matches)
    deny ip any host 224.0.1.3
    deny ip any host 224.0.2.2 (459 matches)
    deny ip any host 239.0.0.0
    deny ip any host 224.0.1.39
    deny ip any host 224.0.1.40
    deny ip any host 229.55.150.208 (16282890 matches)
    permit ip any any (2216884757 matches)

I think that last one is Norton Ghost, which I am currently receiving from
a couple of sources at Tel Aviv and Ben Gurion Universities....

/a