RE: Advancing the Protocol and Morin Drafts,

[snoopdogg at valhalla.clue.be]

>From: "RAMACHANDRAN, PRASANNA, ATTOPS" <prasanna at att.com>
>
>I vote NO.
>Being in AT&T Advanced Tier support group and having supported the MVPN
>core for the last 2 years, I can clearly say that we need a solution
>such as PIM-BiDir that can reduce the number of multicast states in the
>PEs to be able to scale the Groups X Sources x OILs explosion for our

Hold up, wait a minute.

How does PIM-BiDir fix any of this? In mVPN, the number of PIM 
adjacencies does not scale in any large network. How is this better when 
each individual PE router must establish a PIM adjacency to every OTHER 
single PE router per VPN in a network?

PIM constantly squawking away every 60 seconds on each of those adjacencies 
is nothing to write home about. Why have that when you can solve this with 
a BGP session transported in TCP?

>very large Enterprise customers.   We definitely do not want to tweak a
>crucial protocol like BGP of which our scale is 2 Million VPNV4 routes
>in the US alone.

First, I think AT&T is contradicting itself. Just a few months ago a draft was put 
forward to allow for a router to accept a BGP update with its own originator or 
next-hop. 

This behavior, which is a very important part of freaking loop prevention was 
now becoming optional. I'd say thats a pretty big fundamental tweak in comparison 
to what is going on here.

Secondly, BGP is the right place to address scale of this nature. Just like 
you mentioned, BGP handles millions of routes today. Though I wonder, is that 
all on a single route reflector? My guess is, those 2 million VPNv4 routes are 
spread across multiple routers. The same design could apply here where you could 
have separate routers just handling mVPN information.

>"This email and any files transmitted with it are AT&T property, are

You probably want to turn that off when sending to a mailing list.


As for my vote, I support it just like I support Obama.


Calvin "Snoop" Broadus Jr.
     =Still G.R.E.=