On Tue, 7 Aug 2001, Christian Kuhtz wrote:
I really wanted to reply... "Logic says you need to check the facts before posting such nonsense." .. but that would be a flame. Let's try this instead:
So good of you to show restraint. Your awfully assuming that no one else has as much MPLS knowledge and experience as you. Try to maintain the conversation without "asserting yourself" at the beginning of each response.
In an RFC2547(bis) MPLS-VPN, the edge doesn't neccessarily need to see all the routes at all. All the PE does need to know is enough for the two CE's to communicate with each other. This can be a static route, this can be a summary route. So, if you get another, say 3000 routes for 1000 customers, this is really going to be that much of a scaling problem? In fact, if your customers build BGP sessions etc between their CE's, the routes carried by the PE's are very skinny.
"Doesn't neccessarily"..."if"... Scaling is looking ahead and considering how it could grow. Your going to have to do *something* on each PE, I think signalling a tunnel and being done with it is better.
So, you're going to try to tell us next that n^2 tunnels scale better and are less of an operational nightmare at scale than the connectivity provided inside of an MPLS-VPN?
I think so. I'm sure either will work in its element. Obviously you don't agree, we can leave it at that.
Have you ever actually used the code yourself?
"the code"? Assuming you mean have I setup L3 VPNs, yes, but you can refer to my first comment. andy