$SSO\LQJ#03/6#LQ

931V/#4R6#DQG
7UDIILF#(QJLQHHULQJ

Moderated by: Dr. John McQuillan

 :KDW#EHQHILWV#GRHV
:KDW#EHQHILWV#GRHV
03/6#RIIHU#LQ#D#931
03/6#RIIHU#LQ#D#931
FRQWH[W#EH\RQG#PHUH
FRQWH[W#EH\RQG#PHUH
WXQQHOLQJ"
WXQQHOLQJ"
 :K\#ZRXOG#\RX#QHHG
:K\#ZRXOG#\RX#QHHG
03/6#IRU#4R6#DQG#LV
03/6#IRU#4R6#DQG#LV
DQ\ERG\#UHDOO\#XVLQJ#LW
DQ\ERG\#UHDOO\#XVLQJ#LW
WKDW#ZD\"
WKDW#ZD\"
:KDW#LV#WUDIILF
:KDW#LV#WUDIILF
HQJLQHHULQJ"
HQJLQHHULQJ"
 :KLFK#WUDIILF
:KLFK#WUDIILF
HQJLQHHULQJ#SUREOHP+V,
HQJLQHHULQJ#SUREOHP+V,
VKRXOG#03/6#KHOS#VROYH"
VKRXOG#03/6#KHOS#VROYH"
:K\#LV#03/6#D#EHWWHU
:K\#LV#03/6#D#EHWWHU
VROXWLRQ#WKDQ#$70/#)5
VROXWLRQ#WKDQ#$70/#)5
RU#RWKHU#DYDLODEOH
RU#RWKHU#DYDLODEOH
RSWLRQV#IRU#WKHVH#WKUHH
RSWLRQV#IRU#WKHVH#WKUHH
FKDOOHQJHV"
FKDOOHQJHV"
 )RU#4R6=

0U1#3HWHU#*1#-R\
3URGXFW#0DUNHWLQJ/#,QWHU1HWZRUNLQJ
6\VWHPV
/XFHQW#7HFKQRORJLHV
 Applying MPLS – VPNs, QoS,
Traffic Engineering

Peter Joy, Product Marketing

InterNetworking Systems

Lucent Technologies
Bell Labs Innovations
1st Generation IP Networks Lucent Technologies
Bell Labs Innovations

All Routed Network

With Heavy Traffic

IP

O Lack of QoS leads to uncontrolled congestion

O Result: large and unpredictable delays in the network
O Welcome to the World Wide Wait!
Current Generation IP Networks Lucent Technologies
Bell Labs Innovations

Multiservice Switched Core with an Optical Backbone

IP
ATM
Optical
ATM
Backbone

O Uses an Optical Core Backbone with Dense WDM

O Multiple OC-12, OC-48, OC-192 trunks at the core
O Future could expand to OC-768 and above
New services are driving
Lucent Technologies

the need to scale IP Networks Bell Labs Innovations

• Packet
Forwarding
• Packet Filtering
• Policing
• IP Flow MPLS:
Classification Multiservice
• BGP Peering
• IGP Scaling
IP + ATM
• Multicast Scaling
• Policy Scaling
• Virtual Routing
• New services
Next Generation - Lucent Technologies
Bell Labs Innovations

Multiservice Switching with MPLS

Initial Layer 3
lookup to
Multiservice QoS core
determine pre-
established route
IP

Fast Layer 2 switching

along quality of
service connection

O Multiservice IP, Frame Relay or ATM

O Based on MPLS
What Problem does MPLS Solve? Lucent Technologies
Bell Labs Innovations

O Less overhead: Eliminate IP address look-ups at

transit nodes, reducing the data handling burden
O More control: Allows for explicitly engineered
flows to balance traffic on the network
O More services: Differentiates traffic for QoS and
VPNs
Invisible ATM Lucent Technologies
Bell Labs Innovations

O ATM will be the technology of choice for new

Quality IP networks
O However, ATM will usually not be exposed as
direct user interfaces
O Edge IP interfaces will map onto Quality of
Service ATM core
O Can be used “passively” by MPLS, or “actively”
by “IP Signaling”
Point vs. Path Control Lucent Technologies
Bell Labs Innovations

O Point (Routed)
X Relative priority and queuing enforced independently at
each node in the network
X Problems - Point QoS can’t anticipate resources form
the network as a whole, no end-to-end queuing, no call
admission control
O Path (Switched)
X Uses end-to-end QoS features embedded in ATM
X Anticipates overall network resources and allocates
bandwidth appropriately
The Spectrum of QoS Lucent Technologies
Bell Labs Innovations

o S
QoS LEVEL Q
e
o lut
Guaranteed s End-to-End
Ab End-to-End
Connections Call-by-Call
Call-by-Call
Guaranteed
Guaranteed
Provisioned
Provisioned
QoS Connections
e Connections
Priority a tiv
l
Re
TOS-Based
TOS-Based
Relative
r ay Relative
P Priorities
Priorities
d &
n
Se Internet
Internet
Best Today
Today
Efforts
Basic Browsing Premium Real-Time Application
Access/E-Mail Access Voice/Video Specified
APPLICATION TYPE
Traffic Engineering Lucent Technologies
Bell Labs Innovations

O Made easier with a connection oriented core

“Invisible ATM” Example:
Lucent Technologies
“Toll-Quality” VoIP Bell Labs Innovations

ATM Core

Simple IP
Interface Edge-to-edge
“invisible”
ATM connection

IP maps directly to ATM connection, and triggers

automatic SVC creation through ATM core
 MPLS VPNs Lucent Technologies
Bell Labs Innovations

Independent logical maps for each Virtual Private Network

The
Physical Network
Topology
PHYSICAL

LOGICAL

VPN
VPN 11 VPN
VPN 22 VPN
VPN 33 VPN
VPN 44
 Lucent Technologies
MPLS VPNs with Virtual IP Routing Bell Labs Innovations

Customer A Customer B
Boston San Jose
VR 172.160/24
172.150/16
VR
VR
VPN B
Customer A
NYC VR
IP Navigator Internet
VR
172.150/16 VPN A

Customer B VR
Customer A
NYC Wash., D.C.
172.160/24
172.150/16
O Separate route tables per VPN at edge of network
O Allows use of valuable private IP address space
O Subscriber: QoS and bandwidth guarantees per VPN for quality IP
O Provider: Higher revenue for premium paths, lower for best efforts
 )RU#931V=

0U1#,DQ#51#0DVKLWHU
)RXQGHU#)#3UHVLGHQW
(QQRYDWH#1HWZRUNV
(QQRYDWH#1HWZRUNV

03/6#IRU#931V#"
,DQ#0DVKLWHU##0#3UHVLGHQW
LDQ#HQQRYDWHQHWZRUNV1FRP
ZZZ1HQQRYDWHQHWZRUNV1FRP
 :KDW#LI««#"
&XVWRPHUV#FRXOG#FRQVXPH#GDWD
VHUYLFHV#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
‡931#LV#WKH#IRXQGDWLRQ#VHUYLFH#RQ#ZKLFK
WKH#QHZ#,3#VHUYLFHV#ZLOO#EH#EXLOW
WKH#QHZ#,3#VHUYLFHV#ZLOO#EH#EXLOW
:LUHG#LQWR#D#PDUNHWLQJ#FKDOOHQJH#"
07KH#931#FRQIXVLRQ0
7KH#ZRQGHUIXO#WKLQJ#DERXW#931#LV#WKDW#LWV#P\ULDG
GHILQLWLRQV#JLYH#HYHU\#FRPSDQ\#D#IDLU#FKDQFH#WR#FODLP
WKDW#LWV#H[LVWLQJ#SURGXFW#LV#DFWXDOO\#D#9311

%XW#QR#PDWWHU#ZKDW#GHILQLWLRQ#\RX#FKRRVH/#
WKH#QHWZRUNLQJ#EX]]0SKUDVH#GRHVQ·W#PDNH#VHQVH1#
7KH#LGHD#LV#WR#FUHDWH#D#SULYDWH#QHWZRUN#YLD#WXQQHOLQJ
#DQG#RU#HQFU\SWLRQ#RYHU#WKH#SXEOLF#LQWHUQHW1
6XUH/#LW·V#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
:LUHG#0DJD]LQH
 7KH#1HZ#&RUSRUDWH#:$1
7ZR#931V
5RDG#:DUULRU
,17(51(7
)DFWRU\
&DUULHU#
%DFNERQH

5HWDLO#2XWOHW
2IILFH

‡6LWH#WR#VLWH#931V#EXLOW#RYHU#IDVW/#UHOLDEOH#&DUULHU#%DFNERQHV
6LWH#WR#VLWH#931V#EXLOW#RYHU#IDVW/#UHOLDEOH#&DUULHU#%DFNERQHV
‡$ERXW#<3(#RI#LQWHU#FRPSDQ\#WUDIILF
$ERXW#<3(#RI#LQWHU#FRPSDQ\#WUDIILF
‡5HPRWH#$FFHVV#931V#EXLOW#RYHU#WKH#,QWHUQHW
5HPRWH#$FFHVV#931V#EXLOW#RYHU#WKH#,QWHUQHW
+RZ#GR#\RX#EXLOG#´6LWH0WR06LWHµ
,3#931V"
³#7KH#JUHDW#KRD[#³
2XU#931#VWUDWHJ\#LV 03/6#LV#D
WR#XVH#03/6 VWDQGDUG#ZD\#RI
EXLOGLQJ#931V
 #931#7HFKQLFDO#&KDOOHQJHV
À +RZ#GR#\RX#LGHQWLI\#PHPEHUV#RI#WKH#931"
À +RZ#GR#\RX#GHWHUPLQH#¶HQG#SRLQWV·
O 931#OD\HU#$53"
À +RZ#GR#\RX#DGYHUWLVH#UHDFKDELOLW\
+URXWLQJ,
O $QG#FRQVWUDLQ#LW#DSSURSULDWHO\"$#+([WUDQHW,
À +RZ#GR#\RX#FRQILJXUH#DQG#SURYLVLRQ
TXLFNO\#DQG#HIIHFWLYHO\"
Does MPLS Help Here? Afraid Not !!
:KDW#GRHV#03/6#KHOS#ZLWK#"
À 7XQQHOLQJ#+HQFDSVXODWLQJ,
O 1HFHVVDU\#WR#KLGH#SULYDWH#DGGUHVVHV1
Î 83(#RI#SULYDWH#QHWZRUNV#XVH#QRQ#JOREDOO\#XQLTXH
DGGUHVV#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#6HUYLFH
O $OORZV#FRQQHFWLRQOHVV#,3#WR#ORRN#OLNH#FRQQHFWLRQ0
RULHQWHG
 6ROYLQJ#WKH#3ULYDWH#$GGUHVV
3UREOHP
0#(QFDSVXODWLRQ
IP - add a new (unique) header

Data DA SA

Data DA SA DA SA

Label technologies - add label

Data DA SA VCI/VPI

Data DA SA DLCI

Data DA SA LSP
 6WDWH#RI#WKH#QDWLRQ
À 7KHUH#LV#QR#VWDQGDUGV#EDVHG#931
VROXWLRQ#+03/6#RU#RWKHUZLVH,
À 7KHUH#LVQ·W#HYHQ#D#ZRUNLQJ#JURXS
O 9RFDOO\#RSSRVHG#DW#WKH#2UODQGR#,(7)
À 03/6#ZLOO#EH#KHOSIXO
O %XW#RQO\#VROYHV#VRPH#RI#WKH#SUREOHPV
À 0DQ\#SURSULHWDU\#VROXWLRQV
O &LVFR/#$VFHQG/#1RUWHO/#1HZEULGJH
O 7KH\#XVH#WZR#GLIIHUHQW#PRGHOV
 6ROYLQJ#WKH#5RXWLQJ#3UREOHP
+7ZR#GLIIHUHQW#DSSURDFKHV,

… 0DNH#WKH#FRUH#DZDUH#RI#WKH#SUREOHP
O ¶3HHU·#PRGHO
O 0RGLI\#FRUH#URXWLQJ#SURWRFROV«11
O ([HPSOLILHG#E\#&LVFR·V#%*3#EDVHG#VROXWLRQ
O ,QYHVWPHQW#ULVN#"#2#5HJXODWRU\#ULVN#"
† ,QVXODWH#+LVRODWH,#WKH#FRUH
O 6HUYLFH#RYHUOD\
O /HDYH#WKH#H[LVWLQJ#FRUH#WHFKQRORJ\#LQWDFW
O 6WDELOLW\/#VFDODELOLW\/#VLPSOLFLW\
O /HYHUDJHV#FRUH#HTXLSPHQW#LQYHVWPHQW
7KH#XVH#RI#%*3#LQ#,3#931V
À %*3#LV#WKH#LQWHU0GRPDLQ#SURWRFRO
O 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#""
 6HUYHU#%DVHG#931V
+6HUYLFH#2YHUOD\#0RGHO,
VPN control plane
VPN routing Transport- ATM/Frame/IP/MPLS VPN routing
protocols protocols
Routing - OSPF, IS-IS, PNNI

Service Service
Deployment Deployment
Platforms Platforms

→Multiple Virtual Routers

→Flow Classification
→IP QoS
→Isolation
'HOLYHULQJ#,3#931#VHUYLFHV
WRGD\
À 0DQ\#WHFKQLFDO#FKDOOHQJHV#WR#VROYH
O 1R#VWDQGDUG#VROXWLRQ
O 1R#ZRUNLQJ#JURXS
À 03/6#ZLOO#EH#LPSRUWDQW#LQ#EXLOGLQJ
931V#EXW#LW#LV#RQO\#D#SDUW
À /HW·V#DJUHH#RQ#WKH#931#PRGHO
 3URSRVHG#,3#931#0RGHO
Network Services
DNS/DHCP
Application
Hosting

Network

Virtual Router

Wide Area
Connection

VPN USERS
 )RU#7UDIILF#(QJLQHHULQJ=

0U1#/RXLV#$1#0DPDNRV
'LUHFWRU#RI#*OREDO#6WUDWHJLF
7HFKQRORJ\
881(7#7HFKQRORJLHV/#,QF1
Applying MPLS in VPNs, QoS
and Traffic Engineering (or not?)
Louis Mamakos
Director, Global Strategic Technology
louie@uu.net
MPLS and the public Internet

• The MPLS hammer, and what nails

do we want to pound with it?
• This perspective from a large
Internet backbone operator
MPLS and Traffic Engineering

• Traffic Engineering is the “killer

app” for MPLS
• Permits L2 “VC”-style capabilities
in same platform as traditional L3
routers
 Traffic Engineering

• Identify traffic flows between

infrastructure end points
• Then:
– Map pair-wise traffic flows onto
transmission resources
– Monitor bandwidth use of traffic
flows
– Rinse and repeat (and do capacity
planning)
Traffic Engineering important in
ISP backbones

• UUNET’s been using a L2/L3

hybrid architecture for years to
implement traffic engineering
• Traffic Engineering is done on
large, aggregated flows and not
microflows (not TCP connections)
• MPLS another mechanism to map
logical traffic flows to transmission
resources
UUNET Global backbone evolution
MPLS and Traffic Engineering

• Requires constraint-based routing

support to place MPLS LSPs
– extensions to the IGP routing
protocols (OSPF, IS-IS) to carry
constraint information
– signalling protocol to provision LSPs
in network
Traffic Engineering requirements
for MPLS

• A flow is mapped to an MPLS LSP

• Ideally, the LSP is dynamically
instantiated (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
 MPLS and VPNs

• Non-starter for implementation in

ISP backbones - NOT SCALABLE
– network core aware of all VPN LSPs,
grows linearly with number of
customers (see above)
• Presumes MPLS domain extends
end-to-end from Customer to
Customer
 MPLS and QoS

• MPLS and QoS are orthogonal.

• You might use MPLS to implement
different paths per DiffServ class to
distinguish between paths with different
characteristics (e.g., terrestrial vs.
satellite).
– LSP very likely not end-to-end, but
contained within network infrastructure.
 Conclusion

MPLS - another tool in our tool-kit to

solve engineering problems.