[c-nsp] IS-IS as PE-CE protocol

[Aaron Gould]

The only place I run bgp on pe-ce is for internet uplinks… (junos)

I use a few options to make it work…
- peer-as 123
- local-as 456
- local-as private
- local-as no-prepend-global-as

That works for me.

 

-Aaron

 

From: Nathan Lannine [mailto:nathan.lannine at gmail.com] 
Sent: Thursday, March 21, 2019 8:11 AM
To: Aaron Gould
Cc: Michael Hallgren; Mark Tinka; Cisco-nsp
Subject: Re: [c-nsp] IS-IS as PE-CE protocol

 

On Thu, Mar 21, 2019 at 9:02 AM Aaron Gould <aaron1 at gvtc.com> wrote:

Which reminds me... I recall if pe-ce is bgp, then redis into l3vpn is natural and automatic.... true ?

-Aaron

 

As an implementer of MPLS/L3VPN in the enterprise, this is very interesting to me because I am all IGP internally.  I sort of assumed that in the provider space that L3VPNs would be accomplished the same way, with an IGP as PE-CE protocol for L3VPN, but here we are.  So, in the case of BGP as PE-CE protocol and a small client AS, do you all in the provider space require multiple private ASNs per VPN?  I mean (blatant free training request here) how does this get handled by the VPN customer?

 

Just navel gazing here, but I am wondering if there would be any benefit to me running BGP as my own PE-CE protocol.

 

Thank you,

Nathan