From: Scott Morris (swm@emanon.com)
Date: Fri Nov 18 2005 - 22:53:39 GMT-3
Frame relay MAY be easier for you if you have different connection scenarios
with your MPLS VPN conversion as well. Such as how the internet is going to
be attached. (e.g. through it's own VRF, or injected into a single VRF, or
separately to certain locations)
HDLC and PPP work as well, but give a single-circuit approach.
Realistically, MPLS really doesn't care. It's just a transport. You just
need to look at the business cases for WHY in each choice you make.
Sometimes the "simple support" approach is the only reason why to pick one
over another!
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
David Hoon
Sent: Friday, November 18, 2005 2:34 PM
To: ccielab@groupstudy.com
Subject: OT: MPLS VPN PE-CE encapsulation
Hi,
Sorry for off-topic. I'm now doing a large scale Layer 3 MPLS VPN
deployment design, and stuck with which encapsulation we should use for
PE-CE connection. We have three options now: Cisco HDLC, PPP and Frame
Relay.
Technically, I don't see much different among these encapsulation types.
The provider leans forward to frame relay, with PE as a frame relay DCE
equipment. The reason is easy for migration (we use frame relay now), and fr
can have sub-interfaces. HDLC and PPP has one-byte less header, no big deal.
PPP has authentication, which I doubt we are going to use. Frame relay has
one more parameter (DLCI) to be managed; however, all branches will just
share the same DLCI. QoS are just the same, please correct me if I'm wrong.
I don't see any differents, so for the sake of simple migration, I would go
frame relay. But if this is a new installation, I would go for Cisco HDLC or
PPP, for simple configuration. Running frame relay is make sense but against
my guts. Any recommendation from real world installation?
Thanks a lot.
Best regards,
David Hoon
CCIE #14141
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:07 GMT-3