All things related to multicast

["David Farmer" <>]

What a hornets nest I stirred up, but I'm going to stir more. :)

On 25 Feb 00, David Meyer wrote:

> 
>  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.

Not sure of the details, but I think yes, basically I want to know if you 
could express different policies for unicast and for the reverse path 
used for multicast, or if they had to be the same policy.   
 
> > I would propose:

The rest of this is all mute.  I was under the impression that Multicast 
on Abilene didn't have a COU, AUP, or what ever you want to call it.

In working Group meeting I was told I was wrong, Abilene enforces 
the same prefix list on Multicast as it does on Unicast, with the 
addition peering at the MIX (provided by NREN currently, Abilene 
will peer directly at the MIX in the future) and a multicast default 
route is provided pointing at the MIX(the default route can go away 
some day). 

This policy has the following consequences:  Internet2 and 
Internet1(from the MIX only) multicast sources are provided to 
Abilene connectors.  Only Internet2 sources are accepted from  
connectors, and will be provided to then MIX.

Steve and Dave is this a correct interpretation of how things are 
working?     

I was under the mistaken impression that Internet1 sources from 
local peers of connectors could be accepted by Abilene, this is my 
definition of no Multicast COU.  Below I was trying to work out how 
to make this work without making a lot of work for everyone 
including the Abilene NOC.  

In the Meeting I asked that people no longer say Abilene has no 
Multicast COU, and that the policy be explicitly stated. I hope 
someone can do a better job than I did above.

I now have a few questions and comments:

1. Should Abilene connectors be allowed give Internet2 multicast 
routes to non-Internet2 peers?  I hope yes, what do other think?
If no, is there anyway to enforce such a policy?

2. If yes to 1, should connectors give non-Internet2 peers routes 
from the MIX?  I hope not, what do others think? If no, is there 
anyway to enforce it?   Since I don't think it can be enforced by 
Abilene, what can be done to make it easy for people to do the right 
thing?  Maybe a community marking routes from the MIX.

3.  I don't think forcing all non-Internet2 Multicast sources to come in 
from the MIX is a good idea.  Internet2 claims to be promoting 
Multicast, or to own the technology by some readings, but we're only 
willing to peer with other non-Internet2 Multicast networks at the MIX. 
 Which means we will only peer with big ISPs and smaller west 
coast ISPs. What about smaller ISPs in other parts of the country.  
Yes, this could be a lot of work, but I think having connectors 
provide Internet2 multicast sources and accept multicast sources 
from Local and Regional ISPs for delivery to Internet2 receivers 
would really be promoting Multicast.  

I'd almost be willing to suggest that if we're not willing to make 
peering happen in other parts of the country then we shouldn't even 
peer at the MIX, we should have exactly the same policy for 
Multicast as Unicast.

If the amount of work involved is the issue, then I think proper use of 
registries and communities could make it manageable.  But yes, 
there  will be real work involved. 

> > 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 



==================================================================
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
==================================================================