All things related to multicast

["David Farmer" <>]

I'd like to bring up two Items, that kind of overlap with the Routing 
WG.

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

2. Multicast Peering Policy for Internet2, it is my understanding 
that there in none?  Give the discussion in Florida about AS10888 
and a default multicast route, I think it might be time to start 
thinking about a simple Multicast peering policy.

I would propose:

A. Advertising of AS10888 sources and the default be limited 
Abilene participants, primary or secondary.

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.

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.

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.

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.

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.  While at the same time provide Internet2 
participants with access to as much Multicast content as possible.
But I think there needs to be some basic controls. I think this 
proposal lives up to the goals of Internet2.

Sorry, I didn't get this out sooner, but most of this didn't gel until 
last night.

PS. I planing on participating via phone, someone get paul love or 
Kevin to call me from SB.
 

==================================================================
David Farmer                            Email:  

Networking and Telecommunications Services          

University of Minnesota
2221 University Ave. SE, Suite 145      Phone:  612-626-0815
Minneapolis, MN 55414-3074              FAX:    612-626-1002
==================================================================