[c-nsp] OSPF design

[danger will]

First of all most of the mpls providers dont even support ospf as routing protocol between the CE and the PE (and the CE most of the times is managed by the ISP too contrary to the popular belief) . The reason why is very debatable and there are good arguments on both sides both the ISP and customer but wont get into them.
You probably could run ospf between your router and the CE but you will have issues with the backup. if you dont have any backup then its fine.
I have also given this a lot of thought and the answer is just run bgp thats the only real solution at the moment.

O.

--- On Sat, 10/23/10, Heath Jones <hj1980 at gmail.com> wrote:

From: Heath Jones <hj1980 at gmail.com>
Subject: Re: [c-nsp] OSPF design
To: "Robert Crowe (rocrowe)" <rocrowe at cisco.com>
Cc: cisco-nsp at puck.nether.net
Date: Saturday, October 23, 2010, 2:05 AM

> Just remember
> that you cannot summarize (today) your main Loopback used for your
> LDP/BGP ID as there needs to be a full LSP from ingress-to-egress PE
> across areas, if you providing L2/L3VPN services.

Is this because the lsp is label in label (outer being pe, inner being
customer route)?
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/