The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] RE: Multi-vendor in MPLS domain
MPLS as a technology as not as premature as it is being
made out to be. Moreover, most of the features are PE centric. There are very
few features that would need close interaction between the P & PE devices.
I personally feel that if you have PEs from one vendor and
the P devices from one vendor, the risks are minimized to a large extent. The
only risks that are not mitigated are:
1. OSPF Opaque LSAs.
2. RSVP-TE (Some features like fast
Reroute)
3. LDP
4. Multicast Global (as of today for mVRF in absence of
P2MP LSPs)
Keeping in mind that the 1, 3 & 4 are pretty much
standard and have been working for a long time now and that RSVP-TE would not be
required till the PE devices. Things might change when we talk of inter-area TE,
but that also in all likelihood would be a ABR functionality than anything else.
There are commercial implementations of multi-vendor MPLS
networks in the world. So I do not think that this should be an issue. Moreover
the vendor space would also make sure that to survive in the industry, they have
enough interop testing done.
Regards
Harpreet Singh
From: Thamir M.Al Hammad [mailto:thammad@stc.com.sa] Sent: Sunday, April 03, 2005 8:25 PM To: mpls-ops@mplsrc.com Subject: [MPLS-OPS]: Multi-vendor in MPLS domain Hi,
I want to know your opinion
regarding running MPLS from multi-vendors, is it practical? I mean the PE from
vendor and the P from other vendor or mix of PEs and Ps from different vendors? Specially, in NGN environment where no doubt about TE, QoS, L2VPN
& multicasting. I am afraid about this
because I think any of these technologies still draft in IETF and there are
different philosophies from different vendors. Do you know any case which
successful or failed? Any white paper? What is the
possible risk? Br,
Thamir Alhammad
|
|