Upload
waqas-ali-khan
View
215
Download
0
Embed Size (px)
Citation preview
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
1/47
$SSO\LQJ#03/6#LQ$SSO\LQJ#03/6#LQ
931V/#4R6#DQG931V/#4R6#DQG
7UDIILF#(QJLQHHULQJ7UDIILF#(QJLQHHULQJ
Moderated by: Dr. John McQuillanModerated by: Dr. John McQuillan
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
2/47
:KDW#EHQHILWV#GRHV03/6#RIIHU#LQ#D#931FRQWH[W#EH\RQG#PHUH
WXQQHOLQJ"
:KDW#EHQHILWV#GRHV:KDW#EHQHILWV
#GRHV03/6#RIIHU#LQ#D#93103/6#RIIHU#LQ#D#931
FRQWH[W#EH\RQG#PHUHFRQWH[W#EH\RQG#PHUHWXQQHOLQJ"WXQQHOLQJ"
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
3/47
:K\#ZRXOG#\RX#QHHG03/6#IRU#4R6#DQG#LVDQ\ERG\#UHDOO\#XVLQJ#LW
WKDW#ZD\"
:K\#ZRXOG#\RX#QHHG:K\#ZRXOG
#\RX
#QHHG03/6#IRU#4R6#DQG#LV03/6#IRU#4R6#DQG#LV
DQ\ERG\#UHDOO\#XVLQJ#LWDQ\ERG\#UHDOO\#XVLQJ#LWWKDW#ZD\"WKDW#ZD\"
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
4/47
:KDW#LV#WUDIILFHQJLQHHULQJ"
:KDW#LV#WUDIILF:KDW#LV#WUDIILFHQJLQHHULQJ"HQJLQHHULQJ"
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
5/47
:KLFK#WUDIILFHQJLQHHULQJ#SUREOHP+V,
VKRXOG#03/6#KHOS#VROYH"
:KLFK#WUDIILF:KLFK#WUDIILFHQJLQHHULQJ#SUREOHP+V,HQJLQHHULQJ#SUREOHP+V,
VKRXOG#03/6#KHOS#VROYH"VKRXOG#03/6#KHOS#VROYH"
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
6/47
:K\#LV#03/6#D#EHWWHU
VROXWLRQ#WKDQ#$70/#)5RU#RWKHU#DYDLODEOH
RSWLRQV#IRU#WKHVH#WKUHHFKDOOHQJHV"
:K\#LV#03/6#D#EHWWHU:K\#LV#03/6#D#EHWWHU
VROXWLRQ#WKDQ#$70/#)5VROXWLRQ#WKDQ#$70/#)5RU#RWKHU#DYDLODEOHRU#RWKHU#DYDLODEOH
RSWLRQV#IRU#WKHVH#WKUHHRSWLRQV#IRU#WKHVH#WKUHHFKDOOHQJHV"FKDOOHQJHV"
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
7/47
0U1#3HWHU#*1#-R\0U1#3HWHU#*1#-R\3URGXFW#0DUNHWLQJ/#3URGXFW#0DUNHWLQJ/#,QWHU1HWZRUNLQJ,QWHU1HWZRUNLQJ
6\VWHPV6\VWHPV/XFHQW#7HFKQRORJLHV/XFHQW#7HFKQRORJLHV
)RU#4R6=)RU#4R6=
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
8/47
Lucent Technologies Bell Labs Innovations
Applying MPLS VPNs, QoS,
Traffic Engineering
Peter Joy, Product Marketing
InterNetworking Systems
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
9/47
Lucent Technologies Bell Labs Innovations1st Generation IP Networks
O Lack of QoS leads to uncontrolled congestion
O Result: large and unpredictable delays in the networkO Welcome to the World Wide Wait!
All Routed Network
IP
With Heavy Traffic
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
10/47
Lucent Technologies Bell Labs Innovations
ATM
Current Generation IP Networks
O Uses an Optical Core Backbone with Dense WDM
O Multiple OC-12, OC-48, OC-192 trunks at the coreO Future could expand to OC-768 and above
Multiservice Switched Core with an Optical Backbone
ATM
IP
OpticalBackbone
OpticalBackbone
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
11/47
Lucent Technologies Bell Labs InnovationsNew services are drivingthe need to scale IP Networks
PacketPacket
ForwardingForwarding
Packet FilteringPacket Filtering PolicingPolicing
IP FlowIP Flow
ClassificationClassification BGP PeeringBGP Peering
IGP ScalingIGP Scaling
Multicast ScalingMulticast Scaling
Policy ScalingPolicy Scaling
Virtual RoutingVirtual Routing
New servicesNew services
MPLS:
MultiserviceIP + ATM
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
12/47
Lucent TechnologiesBell Labs Innovations
O Multiservice IP, Frame Relay or ATM
O Based on MPLS
IP
Initial Layer 3Initial Layer 3
lookup tolookup todetermine pre-determine pre-
established routeestablished route
Fast Layer 2 switchingFast Layer 2 switching
along quality ofalong quality of
service connectionservice connection
Multiservice QoS core
Next Generation -Multiservice Switching with MPLS
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
13/47
Lucent TechnologiesBell Labs InnovationsWhat Problem does MPLS Solve?
O Less overhead: Eliminate IP address look-ups attransit nodes, reducing the data handling burden
O More control: Allows for explicitly engineeredflows to balance traffic on the network
O More services: Differentiates traffic for QoS andVPNs
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
14/47
Lucent Technologies Bell Labs InnovationsInvisible ATM
O ATM will be the technology of choice for newQuality IP networks
O However, ATM will usually not be exposed as
direct user interfacesO Edge IP interfaces will map onto Quality of
Service ATM core
O Can be used passively by MPLS, or activelyby IP Signaling
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
15/47
Lucent Technologies Bell Labs InnovationsPoint vs. Path Control
O Point (Routed)
X Relative priority and queuing enforced independently at
each node in the network
X Problems - Point QoS cant anticipate resources formthe network as a whole, no end-to-end queuing, no call
admission controlO Path (Switched)
X Uses end-to-end QoS features embedded in ATM
X Anticipates overall network resources and allocatesbandwidth appropriately
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
16/47
Lucent Technologies Bell Labs Innovations
Abso
luteQ
oS
Relativ
eQoS
Send
&Pra
y
The Spectrum of QoS
APPLICATION TYPE
QoS LEVEL
Basic
Access/E-Mail
Premium
Access
Browsing Real-Time
Voice/Video
BestEfforts
Priority
GuaranteedConnections
Application
Specified
InternetToday
InternetInternetTodayToday
TOS-BasedRelativePriorities
TOS-BasedTOS-BasedRelativeRelativePrioritiesPriorities
ProvisionedConnections
ProvisionedProvisionedConnectionsConnections
End-to-End
Call-by-CallGuaranteed
End-to-EndEnd-to-EndCall-by-CallCall-by-CallGuaranteedGuaranteed
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
17/47
Lucent Technologies Bell Labs InnovationsTraffic Engineering
O Made easier with a connection oriented core
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
18/47
Lucent Technologies Bell Labs InnovationsInvisible ATM Example:
Toll-Quality VoIP
ATM Core
Simple IPSimple IP
InterfaceInterface Edge-to-edgeEdge-to-edgeinvisibleinvisible
ATM connectionATM connection
IP maps directly to ATM connection, and triggersautomatic SVC creation through ATM core
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
19/47
Lucent Technologies Bell Labs InnovationsMPLS VPNs
Independent logical maps for each Virtual Private Network
VPN 1VPN 1VPN 1 VPN 4VPN 4VPN 4VPN 3VPN 3VPN 3VPN 2VPN 2VPN 2
PHYSICAL
LOGICAL
ThePhysical NetworkTopology
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
20/47
Lucent Technologies Bell Labs InnovationsMPLS VPNs with Virtual IP Routing
OSeparate route tables per VPN at edge of network
OAllows use of valuable private IP address space
OSubscriber: QoS and bandwidth guarantees per VPN for quality IPOProvider: Higher revenue for premium paths, lower for best efforts
VPN B
VPN A
IP Navigator Internet
Customer ABoston
172.150/16
Customer ANYC
172.150/16
Customer BNYC
172.160/24
Customer BSan Jose
172.160/24
Customer AWash., D.C.
172.150/16
VR
VRVR
VR
VR
VR
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
21/47
0U1#,DQ#510U1#,DQ#51#0DVKLWHU0DVKLWHU)RXQGHU#)#3UHVLGHQW)RXQGHU#)#3UHVLGHQW
(QQRYDWH(QQRYDWH#1HWZRUNV1HWZRUNV
)RU#931V=)RU#931V=
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
22/47
03/6#IRU#931V#"
(QQRYDWH#1HWZRUNV(QQRYDWH#1HWZRUNV(QQRYDWH#1HWZRUNV(QQRYDWH#1HWZRUNV
,DQ#0DVKLWHU##0#3UHVLGHQW,DQ#0DVKLWHU##0#3UHVLGHQW,DQ#0DVKLWHU##0#3UHVLGHQW,DQ#0DVKLWHU##0#3UHVLGHQWLDQ#HQQRYDWHQHWZRUNV1FRPLDQ#HQQRYDWHQHWZRUNV1FRPLDQ#HQQRYDWHQHWZRUNV1FRPLDQ#HQQRYDWHQHWZRUNV1FRPZZZ1HQQRYDWHQHWZRUNV1FRPZZZ1HQQRYDWHQHWZRUNV1FRPZZZ1HQQRYDWHQHWZRUNV1FRPZZZ1HQQRYDWHQHWZRUNV1FRP
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
23/47
:KDW#LI#"
&XVWRPHUV#FRXOG#FRQVXPH#GDWDVHUYLFHV#LQ#WKH#VDPH#ZD\#WKDW#WKH\FRQVXPH#YRLFH#VHUYLFHV#"
&DUULHUV#FRXOG#JHQHUDWH#QHZ#VHUYLFHV
DV#HDVLO\#DV#WKH\#GR#IRU#YRLFH+FXVWRP#FDOOLQJ#VHUYLFHV,#"
,3#LV#WKH#YHKLFOH#WR#HQDEOH#WKLV,3#LV#WKH#YHKLFOH#WR#HQDEOH#WKLV
931#LV#WKH#IRXQGDWLRQ#VHUYLFH#RQ#ZKLFK
WKH#QHZ#,3#VHUYLFHV#ZLOO#EH#EXLOW
931#LV#WKH#IRXQGDWLRQ#VHUYLFH#RQ#ZKLFK
WKH#QHZ
#,3#VHUYLFHV
#ZLOO
#EH#EXLOW
:L G L W N WL K OO "
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
24/47
:LUHG#LQWR#D#PDUNHWLQJ#FKDOOHQJH#"
07KH#931#FRQIXVLRQ07KH#ZRQGHUIXO#WKLQJ#DERXW#931#LV#WKDW#LWV#P\ULDGGHILQLWLRQV#JLYH#HYHU\#FRPSDQ\#D#IDLU#FKDQFH#WR#FODLP
WKDW#LWV
#H[LVWLQJ
#SURGXFW
#LV
#DFWXDOO\
#D#931
1
:LUHG#0DJD]LQH
%XW#QR#PDWWHU#ZKDW#GHILQLWLRQ#\RX#FKRRVH/#WKH#QHWZRUNLQJ#EX]]0SKUDVH#GRHVQW#PDNH#VHQVH1#
7KH#LGHD#LV#WR#FUHDWH#D#SULYDWH#QHWZRUN#YLD#WXQQHOLQJ#DQG#RU#HQFU\SWLRQ#RYHU#WKH#SXEOLF#LQWHUQHW1
6XUH/#LWV#D#ORW#FKHDSHU#WKDQ#XVLQJ#\RXU#RZQ#)UDPH#UHOD\
#FRQQHFWLRQV/#EXW#LW#ZRUNV#DERXW#DV#ZHOO#DV#VWLFNLQJ#FRWWRQ#LQ#\RXU#HDUV#LQ#7LPHV#6TXDUH#DQG#SUHWHQGLQJ#QRERG\#HOVH#LV#DURXQG1
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
25/47
6LWH#WR#VLWH#931V#EXLOW#RYHU#IDVW/#UHOLDEOH#&DUULHU#%DFNERQHV6LWH#WR#VLWH#931V#EXLOW#RYHU#IDVW/#UHOLDEOH#&DUULHU#%DFNERQHV6LWH#WR#VLWH#931V#EXLOW#RYHU#IDVW/#UHOLDEOH#&DUULHU#%DFNERQHV6LWH#WR#VLWH#931V#EXLOW#RYHU#IDVW/#UHOLDEOH#&DUULHU#%DFNERQHV$ERXW#
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
26/47
+RZ#GR#\RX#EXLOG#6LWH0WR06LWH
,3#931V"#7KH#JUHDW#KRD[#
03/6#LV#DVWDQGDUG#ZD\#RIEXLOGLQJ#931V
2XU#931#VWUDWHJ\#LVWR#XVH#03/6
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
27/47
+RZ#GR#\RX#LGHQWLI\#PHPEHUV#RI#WKH#931"
+RZ#GR#\RX#GHWHUPLQH#HQG#SRLQWVO 931#OD\HU#$53"
+RZ#GR#\RX#DGYHUWLVH#UHDFKDELOLW\
+URXWLQJ,O $QG#FRQVWUDLQ#LW#DSSURSULDWHO\"$#+([WUDQHW,
+RZ#GR
#\RX
#FRQILJXUH
#DQG
#SURYLVLRQTXLFNO\#DQG#HIIHFWLYHO\"
#931#7HFKQLFDO#&KDOOHQJHV
Does MPLS Help Here? Afraid Not !!
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
28/47
:KDW#GRHV#03/6#KHOS#ZLWK#"
7XQQHOLQJ#+HQFDSVXODWLQJ,O 1HFHVVDU\#WR#KLGH#SULYDWH#DGGUHVVHV1
83(#RI#SULYDWH#QHWZRUNV#XVH#QRQ#JOREDOO\#XQLTXHDGGUHVV#VSDFH1
O 2WKHU#$OWHUQDWLYHV#0#,32,3/#$70
$SSURSULDWH#VHFXULW\O 0DNHV#,3#VHFXUH#OLNH#)UDPH#5HOD\
O 1R#QHHG#IRU#HQFU\SWLRQ#$
4XDOLW\#RI#6HUYLFHO $OORZV#FRQQHFWLRQOHVV#,3#WR#ORRN#OLNH#FRQQHFWLRQ0
RULHQWHG
6 O L K 3 L $GG
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
29/47
IP - add a new (unique) header
Data DA SA DA SA
Data DA SA
Label technologies - add label
Data DA SA VCI/VPI
Data DA SA
Data DA SA
DLCI
LSP
6ROYLQJ#WKH#3ULYDWH#$GGUHVV3UREOHP
0#(QFDSVXODWLRQ
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
30/47
7KHUH#LV#QR#VWDQGDUGV#EDVHG#931VROXWLRQ#+03/6#RU#RWKHUZLVH,
7KHUH#LVQW#HYHQ#D#ZRUNLQJ#JURXSO 9RFDOO\#RSSRVHG#DW#WKH#2UODQGR#,(7)
03/6#ZLOO#EH#KHOSIXOO %XW#RQO\#VROYHV#VRPH#RI#WKH#SUREOHPV
0DQ\#SURSULHWDU\#VROXWLRQVO &LVFR/#$VFHQG/#1RUWHO/#1HZEULGJHO 7KH\#XVH#WZR#GLIIHUHQW#PRGHOV
6WDWH#RI#WKH#QDWLRQ
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
31/47
6ROYLQJ#WKH#5RXWLQJ#3UREOHP+7ZR#GLIIHUHQW#DSSURDFKHV,
0DNH#WKH#FRUH#DZDUH#RI#WKH#SUREOHP
O 3HHU#PRGHOO 0RGLI\#FRUH#URXWLQJ#SURWRFROV11
O ([HPSOLILHG#E\#&LVFRV#%*3#EDVHG#VROXWLRQ
O ,QYHVWPHQW#ULVN#"#2#5HJXODWRU\#ULVN#"
,QVXODWH#+LVRODWH,#WKH#FRUHO
6HUYLFH#RYHUOD\
O /HDYH#WKH#H[LVWLQJ#FRUH#WHFKQRORJ\#LQWDFW
O 6WDELOLW\/#VFDODELOLW\/#VLPSOLFLW\
O /HYHUDJHV#FRUH#HTXLSPHQW#LQYHVWPHQW
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
32/47
7KH#XVH#RI#%*3#LQ#,3#931V
%*3#LV#WKH#LQWHU0GRPDLQ#SURWRFROO
8VHG#E\#,63V#WR#FRQQHFW#WR#RWKHU#,63V 3UREOHPV#ZLWK#%*3#LQFOXGH
O VFDODELOLW\/#FRQYHUJHQFH/#VWDELOLW\
&LVFR#LV#XVLQJ#%*3#WR#FDUU\#931
PHPEHUVKLS#LQIRUPDWLRQ
:+$76#%*3#*27#72#'2#:,7+931V#""
6 % G 931
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
33/47
VPN control planeVPN routingVPN routing
protocolsprotocolsVPN routingVPN routing
protocolsprotocols
6HUYHU#%DVHG#931V+6HUYLFH#2YHUOD\#0RGHO,
ServiceDeployment
Platforms
ServiceDeployment
Platforms
Transport- ATM/Frame/IP/MPLS
Routing - OSPF, IS-IS, PNNI
Multiple Virtual Routers
Flow Classification
IP QoS
Isolation
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
34/47
'HOLYHULQJ#,3#931#VHUYLFHV
WRGD\0DQ\#WHFKQLFDO#FKDOOHQJHV#WR#VROYH
O
1R#VWDQGDUG#VROXWLRQO 1R#ZRUNLQJ#JURXS
03/6#ZLOO#EH#LPSRUWDQW#LQ#EXLOGLQJ
931V#EXW#LW#LV#RQO\#D#SDUW /HWV#DJUHH#RQ#WKH#931#PRGHO
O
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
35/47
3URSRVHG#,3#931#0RGHO
Network
Virtual Router
VPN USERS
Wide Area
Connection
Application
Hosting
Network Services
DNS/DHCP
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
36/47
0U1#/RXLV#$10U1#/RXLV#$1#0DPDNRV0DPDNRV'LUHFWRU#RI#*OREDO#6WUDWHJLF'LUHFWRU#RI#*OREDO#6WUDWHJLF
7HFKQRORJ\7HFKQRORJ\881(7#7HFKQRORJLHV/#,QF1881(7#7HFKQRORJLHV/#,QF1
)RU#7UDIILF#(QJLQHHULQJ=)RU#7UDIILF#(QJLQHHULQJ=
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
37/47
Louis Mamakos
Director, Global Strategic [email protected]
Applying MPLS in VPNs, QoS
and Traffic Engineering (or not?)
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
38/47
MPLS and the public Internet
The MPLS hammer, and what nailsdo we want to pound with it?
This perspective from a large
Internet backbone operator
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
39/47
MPLS and Traffic Engineering
Traffic Engineering is the killerapp for MPLS
Permits L2 VC-style capabilities
in same platform as traditional L3
routers
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
40/47
Traffic Engineering
Identify traffic flows betweeninfrastructure end points
Then: Map pair-wise traffic flows onto
transmission resources
Monitor bandwidth use of trafficflows
Rinse and repeat (and do capacity
planning)
T ffi E i i i i
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
41/47
Traffic Engineering important in
ISP backbones
UUNETs been using a L2/L3hybrid architecture for years toimplement traffic engineering
Traffic Engineering is done onlarge, aggregated flows and notmicroflows (not TCP connections)
MPLS another mechanism to maplogical traffic flows to transmission
resources
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
42/47
UUNET Global backbone evolution
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
43/47
MPLS and Traffic Engineering
Requires constraint-based routingsupport to place MPLS LSPs extensions to the IGP routing
protocols (OSPF, IS-IS) to carryconstraint information
signalling protocol to provision LSPs
in network
T ffi E i i i t
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
44/47
Traffic Engineering requirements
for MPLS
A flow is mapped to an MPLS LSP Ideally, the LSP is dynamicallyinstantiated (and recovered) based
on a set of constraint attributes(e.g., available bandwidth, delay,color or administrative
preferences) per-LSP utilization monitored for
capacity planning
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
45/47
MPLS and VPNs
Non-starter for implementation inISP backbones - NOT SCALABLE
network core aware of all VPN LSPs,
grows linearly with number of
customers (see above)
Presumes MPLS domain extendsend-to-end from Customer to
Customer
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
46/47
MPLS and QoS
MPLS and QoS are orthogonal. You might use MPLS to implement
different paths per DiffServ class to
distinguish between paths with differentcharacteristics (e.g., terrestrial vs.
satellite).
LSP very likely not end-to-end, but
contained within network infrastructure.
8/7/2019 Applying_MPLS_in_VPNs,_QoS_and_Traffic_Engineering
47/47
Conclusion
MPLS - another tool in our tool-kit to
solve engineering problems.