[j-nsp] MPLSoMPLS - horrible?

[Dale Shaw]

Hi all,

I'm pondering my first production use of MPLS and I'm looking for some
free advice.

I'm looking at building a new 'enterprise' network - an extranet of
sorts - *on top of* a NSP's L3VPN service. It's all Ethernet. I'd like
to be able to build my own pseudowires and create my own L3VPNs on top
of the NSP's platform and without their involvement. In effect, my CE
routers (from the NSP's perspective) become PE routers to *my*
customers (3rd parties, e.g. business partners and suppliers).

I suppose this means doing MPLSoMPLS, and actually depending on the
upper layers in the protocol stack, it could end up looking pretty
scary if you looked at what was being shifted around in the NSP's core
:-)  (over and above MPLS, I'm thinking about how the stack looks when
further encapsulation, such as IPSec, is used.)

So, noting the protocol stack size and potential MTU issues, is anyone
doing this? How are you distributing labels?

Is it too horrible to even contemplate?

I'd be looking at using J and/or SRX as the "CE-pseudo-PE" devices.

Any pointers would be appreciated. I've only just embarked on this
little adventure and I'm still relative new to Juniper platforms.

Cheers,
Dale