[c-nsp] Internet in VRF

[Phil Bedard]

If you have the BGP free core already built, I’d definitely do 6PE.  We’ve been doing it for many years now with no issues at all.  

As for RSVP-TE we run that as well, but for definite reasons.  We forward different CoS over different LSPs, use it for traffic engineering, use FRR, and need support for SRLGs since we operate all layers of the network.  Juniper should have SR support early next year as people are driving them to it.  ALU has it in their very recent 13.0 release, but I believe it’s still labeled as not for production just yet.  SR doesn’t do everything RSVP-TE does in a distributed control-plane, but I could see it replacing LDP.  

We don’t run Internet in a VRF, we have no real use cases where we can’t control what we need through policy.  Our core infrastructure isn’t accessible from our customers or the Internet, but it does require using the right infrastructure ACLs. If I was doing a greenfield build may do it but having the complexity of putting different transits, peers, etc. in their own VRFs is kind of overkill IMHO.  

Phil 



-----Original Message-----
From: Saku Ytti
Date: Monday, May 4, 2015 at 05:13
To: <cisco-nsp at puck.nether.net>, Nathan Ward
Subject: Re: [c-nsp] Internet in VRF

>On (2015-05-04 10:53 +0200), Mark Tinka wrote:
>
>> But when I first deployed IPv6 back in 2005, the choice of 6PE vs.
>> native was an easy one... Never looked back since.
>
>Why not? To me 6PE is easy, if you run MPLS, you want 6PE. After all, it's
>nothing but IPv6 in VRF, which I'd want in IPv4 as well, if I can figure out
>good brown-field migration to it.
>Day1 you get to benefit of all of the MPLS goodness. And in your case, as you
>run BGP free IPV4 core, it feels like sentimental choice of not running 6PE.
>
>Why must there exist coupling between core signalling and edge services? Less
>coupling, less complexity.
>
>-- 
>  ++ytti
>_______________________________________________
>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/