All things related to multicast

[David Meyer <>]

        David

> 1. Can we use IRRd to hold Multicast source routing information 
> and policy?  Should we put Multicast info in an Internet2 Registry?

        You mean unicast routes used for RPF (AFI = IPv4, SAFI = 1 or 2),
        correct? If so, then yes.

> I would propose:
> 
> A. Advertising of AS10888 sources and the default be limited 
> Abilene participants, primary or secondary.

        What is an AS10888 source? Do mean avertising to AS10888
        of sources? If so, then of course, you only advertise your
        own prefixes (our should).

> B. A new Abilene Community be created to mark Multicast routes 
> learned from potentially commercial sources.  The routes learned 
> form AS10888 and the default Multicast route be marked with this 
> community. GigaPOPs and/or Abilene should mark Multicast 
> routes learned from non-Internet2 sources with this community.

        AS10888 does transit some multicast NLRI, but I want
        to stop doing this. Likely I would only give you default.
        You should get other prefixes from the orginators (you'll
        be on the MIX; I have a GSR on order for you guys for 
        the MIX).

> C. A new Abilene Community be created to mark Multicast routes
> learned form Internet2 peer networks that do not want to be 
> advertised to non-Internet2 participants.

        This seems reasonable, but debugging this will be a mess
        when it breaks.

> D. GigaPOPs only advertise Multicast routes marked with the 
> communities in B and C to Abilene primary and secondary 
> participants. And, not advertise them to other peers.
> 
> I think this would prevent potentially commercial sources from 
> being received by commercial receivers.  But would allow Internet2 
> and some peer sources to be view by commercial receivers.

        What is a "commercial source"? Do you mean transiting
        either (a) a GP, or (b) Abilene? 

        BTW, I have to say you're setting up for something complex 
        here (IMHO), with a large window for creating black-holes.

> I think there are probably MSDP issues I am over looking here 
> since MSDP doesn't have communities like MBGP, but I don't 
> think they are a major problem.

        :-) cf. Black holes.


> I bring this up be cause I think GigaPOPs could help promote 
> Multicast outside strict Internet2 borders, by providing Internet2 
> multicast content to non-Internet2 entities and even regional 
> commercial ISPs.  

        What content? Be careful. Last press release from I2
        that had anything to do with mulitcast called MSDP, MBGP,
        PIM-SM and IP/TV "Internet2 Technologies"; as the press release
        stated, "I2 multicast technology to be used at NANOG" 
        approximately...pretty humiliating for I2 (if you didn't notice).

        Dave