Introduction To MPLS

RST-130
2926_05_2001_c2 © 2001, Cisco Systems, Inc. All rights reserved. 1
Copyright © 2001, Cisco Systems, Inc. All rights reserved. Printed in USA.
Presentation_ID.scr
Introduction to MPLS
Session RST-130
RST-130
Agenda
• Background and Business Case

• Technology Basics
What Is MPLS? Where Is It Used?
• Label Distribution in MPLS Networks
LDP, RSVP, BGP
• Building MPLS-based Services
IP+ATM Integration
VPNs
Traffic Engineering (FRR and Protection)
• Conclusions
RST-130
Presentation_ID.scr
MPLS Key Drivers
Business Drivers
Technology Drivers
RST-130
Evolution of MPLS
• From tag switching

• Proposed in IETF—Later combined with other
proposals from IBM (ARIS), Toshiba (CSR)
Cisco MPLS
MPLS Croup
Croup Cisco
Cisco Ships
Ships Traffic
Traffic Engineering
Cisco Calls
Calls aa Engineering
BOF Formally
Formally Chartered
Chartered MPLS
MPLS TE Deployed
BOF at
at IETF
IETF to
to TE Deployed
Standardize by
by IETF
IETF
Standardize
Tag
Tag Switching
Switching Cisco
Cisco Ships
Ships MPLS
MPLS VPN
VPN Large
Large Scale
Scale
MPLS
MPLS (Tag
(Tag Deployed
Deployed Deployment
Deployment
Switching)
Switching)
1996 1997 1998 1999 2000 2001

Time
RST-130
Presentation_ID.scr
MPLS as a Foundation for Value
Added Services
Provider Any
Traffic IP+Optical
Provisioned IP+ATM Transport
Engineering GMPLS
VPNs Over MPLS
MPLS
Network Infrastructure
RST-130
European PTT Deployment Plans

European PTT Deployment Plans
(% of total planning to deploy by 2001)
Web Caching
VPNs
MPLS
1st Qtr
0 20 40 60 80 100 120
Infonetics European PTT deployment plans by 2001
RST-130
Presentation_ID.scr
In-House or Outsourced VPNs
100% Outsourced
Owned
90%
80%
70%
60% Build
Customer
50% Base Now to
Seize Future
40%
Growth
30%
20%
10%
0%
1998 1999 2000 2001 2002 2003
Source: Cahners Instat

RST-130
US VPN Spending
2000
1800 Cisco
1600
1400
1200 30000
VPN Products
1000 25000 VPN Services
800 20000
600 15000
400 10000
200 5000
0 0 VPN Products
1997 1998 1999 2000 2001 2002 1999 2000 2001 2002 2003
Yankee Group Predictions for VPN Spending Infonetics VPN Spend Projections in
($US Millions) ($US Millions)
RST-130
Presentation_ID.scr
The Service Provider Challenge
• Generate new services

• Protect existing Infrastructure—ATM/FR
• Combine private data services with
Internet services
• Move into rapid deployment
RST-130
Technology Basics
RST-130
Presentation_ID.scr
MPLS Concept
• At Edge: • In Core:
Classify packets Forward using labels
Label them (as opposed to IP addr)
Label indicates service
class and destination
Edge Label
Switch Router
(ATM Switch or Label Switch
Router) Router (LSR)
Router
ATM switch + Tag
Label Distribution Switch Controller
Protocol (LDP)
• Enable ATM switches to act as routers

• Create new IP capabilities via flexible classification
RST-130
MPLS Operation
1a. Existing routing protocols (e.g. OSPF, IS-IS) 4. Edge LSR at egress
establish reachability to destination networks removes label and
delivers packet
1b. Label Distribution Protocol (LDP)
establishes label to destination
network mappings
2. Ingress Edge LSR receives packet,

performs Layer 3 value-added 3. LSR switches packets using
services, and “labels” packets label swapping
RST-130
Presentation_ID.scr
Encapsulations
ATM Cell Header GFC

GFC VPI
VPI VCI
VCI PTI
PTI CLP
CLP HEC
HEC DATA
DATA
Label
Label
PPP Header
PPP
PPP Header
Header Label
Label Header
Header Layer
Layer 33 Header
Header
(Packet over SONET/SDH)
LAN MAC Label Header MAC

MAC Header
Header Label
Label Header
Header Layer
Layer 33 Header
Header
RST-130
Label Header for Packet Media
00 11 22 33
00 11 22 33 44 55 66 77 88 99 00 11 22 33 44 55 66 77 88 99 00 11 22 33 44 55 66 77 88 99 00 11
Tag COS S TTL
Label = 20 bits COS/EXP = Class of Service, 3 bits

S = Bottom of Stack, 1 bit TTL = Time to Live, 8 bits
• Can be used over Ethernet, 802.3, or PPP links

• Uses two new Ethertypes/PPP PIDs
• Contains everything needed at forwarding time
• One word per label
RST-130
Presentation_ID.scr
Label Distribution
in MPLS Networks
RST-130
Label Distribution Protocol
• Defined in RFC 3036 and 3037

• Used to distribute labels in a MPLS network
• Forwarding equivalence class
How packets are mapped to LSPs (Label
Switched Paths)
• Advertise labels per FEC

Reach destination a.b.c.d with label x
• Neighbor discovery
Basic and extended discovery
RST-130
Presentation_ID.scr
Label Distribution Protocol
• Label merge
Done by default for packet networks—unique
label advertised per FEC
Requires VC merge for ATM networks
RST-130
TDP and LDP
• Tag Distribution Protocol

Pre-cursor to LDP
Used for Cisco tag switching
• TDP and LDP supported on the same box

Per neighbor/link basis
Per target basis
RST-130
Presentation_ID.scr
RSVP and Label Distribution
• Used in MPLS traffic engineering

• Additions to RSVP signaling protocol
• Leverage the admission control mechanism
of RSVP
• Label requests are sent in PATH messages and
binding is done with RESV messages
• EXPLICT-ROUTE object defines the path over which
setup messages should be routed
• Using RSVP has several advantages
RST-130
BGP-Based Label Distribution
• Used in the context of MPLS VPNs

• Need multi-protocol extensions to BGP
• Routers need to be BGP peers
Works in both RR and non-RR environment
• Label mapping info carried as part of NLRI
(Network Layer Reachability Information)
RST-130
Presentation_ID.scr
Router Example: Forwarding Packets
Address I/F Address I/F Address I/F

Prefix Prefix Prefix
128.89 1 128.89 0 128.89 0

171.69 1 171.69 1
… … … …
0 128.89
0
1
128.89.25.4 Data
0 128.89.25.4 Data
1
128.89.25.4 Data 128.89.25.4 Data
Packets Forwarded 171.69

Based on IP Address
RST-130
MPLS Example: Routing Information
In Address Out Out In Address Out Out In Address Out Out

Label Prefix I’face Label Label Prefix I’face Label Label Prefix I’face Label
128.89 1 128.89 0 128.89 0

171.69 1 171.69 1
… … … … … …
0 128.89
0
1
You Can Reach 128.89 Thru

Me
You Can Reach 128.89 and 1
171.69 Thru Me
Routing Updates You Can Reach 171.69 Thru 171.69

(OSPF, EIGRP, …) Me
RST-130
Presentation_ID.scr
MPLS Example: Assigning Labels

- 128.89 1 4 4 128.89 0 9 9 128.89 0 -

- 171.69 1 5 5 171.69 1 7
… … … … … … … … … … … …
0 128.89
0
1
Use Label 9 for 128.89

Use Label 4 for 128.89 and 1
Use Label 5 for 171.69
Label Distribution 171.69

Protocol (LDP) Use Label 7 for 171.69
(downstream allocation)
RST-130
MPLS Example: Forwarding Packets

- 128.89 1 4 4 128.89 0 9 9 128.89 0 -

- 171.69 1 5 5 171.69 1 7
… … … … … … … … … … … …
0 128.89
0
1
128.89.25.4 Data
9 128.89.25.4 Data
1
128.89.25.4 Data 4 128.89.25.4 Data
Label Switch Forwards

Based on Label
RST-130
Presentation_ID.scr
ATM MPLS Example: Requesting Labels
In Address Out Out In In Address Out Out In In Address Out Out

label Prefix I’face label label I/F Prefix I’face label label I/F Prefix I’face label
128.89 1 128.89 0 128.89 0
171.69 1 171.69 1
... ... ... ... ... ...
1 0 128.89
1 0
2
I need a label for 128.89
I need another label for 128.89
I need a label for 128.89 3
1
I need a label for 171.69 I need a label for 171.69
Label Distribution I need a label for 128.89

Protocol (LDP) 171.69
(downstream allocation on demand)
RST-130
ATM MPLS Example: Assigning Labels

- 128.89 1 4 4 2 128.89 0 9 9 1 128.89 0 -
- 171.69 1 5 8 3 128.89 0 10 10 1 128.89 0 -

... ... 5 2 171.69 1 7 ... ...
1 0 128.89
1 0
2
Use label 9 for 128.89
Use label 10 for 128.89
Use label 4 for 128.89 3
1
Use label 5 for 171.69 Use label 7 for 171.69
Use label 8 for 128.89 171.69
RST-130
Presentation_ID.scr
ATM MPLS Example: Packet Forwarding

- 128.89 1 4 4 2 128.89 0 9 9 1 128.89 0 -
- 171.69 1 5 8 3 128.89 0 10 10 1 128.89 0 -

... ... 5 2 171.69 1 7 ... ...
1 0 128.89
0
2
128.89.25.4 Data
1
9 128.89.25.4 Data
128.89.25.4 Data 1
4 128.89.25.4 Data
Label Switch forwards 171.69

based on label
RST-130
Why Multiple Labels with ATM?
In In Address Out Out

Label I/F Prefix I’face Label
1 5 128.89 0 3
2 8 128.89 0 3
Cells … … … … …
55 Help!
55 55
Packet
Packet 55 1
0
128.89
2 33 33 33 33 33 33
Packet
Packet 88 88
88 88
• If we didn’t allocate multiple labels:

Cells of different packets would have same label
(VPI/VCI)
Egress router can’t reassemble packets
RST-130
Presentation_ID.scr
Multiple Labels

1 5 128.89 0 3
2 8 128.89 0 7
Cells … … … … …
55 Much Better!
55 55
Packet
Packet 55 1
0
128.89
2 77 33 77 33 77 33
Packet
Packet 88 88
88 88
• Multiple labels enables edge router to

reassemble packets correctly
RST-130
VC Merge

1 5 128.89 0 3
2 8 128.89 0 7
Cells … … … … …
55
55 55
Packet
Packet 55 1
0
128.89
2 77 77 77 33 33 33
Packet
Packet 88 88
88 88
• With ATM switch that can merge VC’s:

Can reuse outgoing label
Hardware prevents cell interleave
Fewer labels required
For very large networks
RST-130
Presentation_ID.scr
MPLS Forwarding
Destination- Explicit
Resource Multicast Virtual
based IP Class Reservation Routing and Private
Unicast of Service Static
(eg RSVP) (PIM v2) Networks
Routing Routes
Label Information Base (LIB)
Per-Label Forwarding, Queuing, and Multicast Mechanisms
• Key: Separation of control plane and forwarding plane

Basic MPLS: destination-based unicast
Labels divorce forwarding from IP address
Many additional options for assigning labels
Labels define destination and service
RST-130
Label Stacking
• Arrange labels in a stack

• Inner labels can be used to designate services/ FECs, etc.
E.g. VPNs, fast re-route
• Outer label used to route/switch the MPLS packets in

the network
Outer Label
• Allows building services such as
MPLS VPNs TE Label
Traffic engineering and fast re-route IGP Label

VPNs over traffic engineered core VPN Label
Any transport over MPLS
Inner Label IP Header
RST-130
Presentation_ID.scr
MPLS-Based Services
RST-130
IP+ATM
RST-130
Presentation_ID.scr
IP+ATM Network Model
1. Packet Transport
Today’s service revenue
2. IP VPNs (1)
Growth through new value-
added services IP+ATM Network-Based
(2) IP VPNs
3. IP-Enabled Transport
(4)
ATM for transport aggregation
IP-Enabled for service delivery:
any-to-any connectivity
Leased
4. IP Service Communities ATM Frame DSL Wireless
Lines
Intranets/Extranets with (3)
applications and content hosting
RST-130
BGP MPLS VPNs
RST-130
Presentation_ID.scr
What Is a VPN?
• VPN is a set of sites which are allowed to

communicate with each other
• VPN is defined by a set of administrative policies
Policies determine both connectivity and QoS
among sites
Policies established by VPN customers
Policies could be implemented completely by VPN
service providers
Using BGP/MPLS VPN mechanisms
RST-130
What Is a VPN? (Cont.)
• Flexible inter-site connectivity

Ranging from complete to partial mesh
• Sites may be either within the same or in different

organizations
VPN can be either intranet or extranet
• Site may be in more than one VPN

VPNs may overlap
• Not all sites have to be connected to the same

service provider
VPN can span multiple providers
RST-130
Presentation_ID.scr
IP VPN Taxonomy
IP VPNs
DIAL DEDICATED
Client- NAS - IP Virtual Network-

Initiated Initiated Tunnel Circuit Based VPNs
Security Router FR ATM RFC 2547 Virtual

Appliance Router
RST-130
IP-VPN Architectural Framework

Encryption
IPsec
MPLS
QoS, Traffic Engineering
RST-130
Presentation_ID.scr
VPN Services and Architectures
Service Architecture Technology

Access VPN Client–Initiated CPE and Network-based
IPsec, L2TP, PPTP
NAS–Initiated
Dial, ISDN, DSL, Cable
Intranet VPN IP Tunnel CPE and Network-based

IPsec, GRE
Virtual Circuit
FR, ATM
MPLS
IP or IP + ATM
Extranet VPN IP Tunnel CPE and Network-based

IPsec, GRE
Virtual Circuit
FR, ATM
MPLS
IP or IP + ATM
RST-130
MPLS-based IP-VPN Architecture
• Scalable VPNs
VPN Membership-
• IP QoS and traffic Based on Logical Port
engineering
VPN A
• Easy to manage and No VPN A Site 3
VC provisioning required Site 2
MPLS
• Provides a level of Network
Security equivalent to Corp A Corp B
MPLS VPN Renault
Frame-relay and ATM Site 1 Site 2
MPLS VPN Bankcorp
• Supports the deployment
of new value-added
applications Corp B
Site 1
• Customer IP address Corp B
Site 3 Traffic Separation at Layer 3
freedom
Each VPN Has Unique RD
RST-130
Presentation_ID.scr
Using Labels to Build an IP VPN
Cust A
A A
Cust A ----
---
----
----
---
----
B
----
---
----
Cust A
B
Cust B
----
---
----
MPLS
Network
Cust B
• The network distributes labels to each VPN

Only labels for other VPN members are distributed
Each VPN is provisioned automatically by IP routing
• Privacy and QoS of ATM without tunnels or encryption
Each network is as secure as a Frame Relay connection
• One mechanism (labels) for QoS and VPNs—no tradeoffs
RST-130
Service Provider Benefits

of MPLS-Based VPNs
VPN B VPN A VPN C
VPN C VPN B
Multicast
Hosting
Intranet
VPN A
VoIP Extranet
VPN A
VPN B
VPN C VPN C
VPN A VPN B
• Overlay VPN • MPLS-based VPNs
Pushes content outside the network Enables content hosting inside the
Costs scale exponentially network
Transport dependent “Flat” cost curve
Groups endpoints, not groups Transport independent
Complex overlay with QoS, tunnels, IP Easy grouping of users and services
Enables QoS inside the VPNs
RST-130
Presentation_ID.scr
Key Features
• No constraints on addressing plans used by

VPNs—A VPN customer may:
Use globally unique and routable/non-routable
addresses
Use private addresses (RFC1918)
• Security:
Basic security is comparable to that provided by
FR/ATM-based VPNs without requiring data encryption
VPN customer may use IPSec-based mechanisms
E.g., CE—CE IPSec-based encryption
RST-130
MPLS Based IP-VPN Security
Cisco MPLS based VPNs:

Equivalent to the Security
of Frame Relay and ATM
Security
Miercom, March 30, 2001
http://www.mier.com/reports/cisco/MPLS-VPNs.pdf
RST-130
Presentation_ID.scr
Validating Cisco MPLS Based IP-VPN
as a Secure Network
Miercom independent testing POS 2/0

LONDON
GSR12008
confirmed Cisco MPLS VPN is OC3 POS

100.200.110.1
POS 1/1
100.200.106.1
100.200.200.107
POS 1/0
100.200.103.1 OC3 POS
secure: POS 1/0

100.200.106.2
GLASCOW
7206
100.200.200.106
POS 1/0
100.200.112.1
OXFORD
7206
100.200.200.103 POS 2/0
? Customers network topology is not

100.200.103.2
OC3 POS
SER 5/0:0 ATM 1/0 Ser 5/0:0 Ser 3/0
100.200.104.1 100.200.105.1 DOVER 100.200.101.1 100.200.102.1
Si
7505 Si
100.200.200.112
POS 2/1/0
revealed to the outside world T1 FR

dlci 104
pvc 1/1
OS PF
ATM1/0
SER 1/0/1:0
100.200.110.1
100.200.112.2
T1 FR
dlci 101
T1 FR
dlci 102
eBGP AS72
RIP v2 100.200.105.2 Si ATM2/0/0 OSPF
? Customers can maintain own

SER 1/0:0 100.200.111.1
100.200.104.2 SER 1/0/0:0 Ser0/0
100.200.109.1 Ser0
100.200.101.2 100.200.102.2
T1 FR
dlci 109
T1 FR
10.5.5.5 dlci 110 RIP v2 pvc 0/11
addressing plans and the freedom 3.4.4.4 BLUE-Glascow

3640
Static
Ser 0
100.200.109.2
eBGP AS71
ATM1/0
100.200.111.2 10.4.4.4
Ser 1/0
to use either public or private

100.200.200.105
RED-Glascow 100.200.110.2
2611 BLUE-Oxford 10.4.4.4
100.200.200.104 1750
BLUE-Dover 3.5.5.5 100.200.200.101
10.3.3.3
address space
2611
100.200.200.110 RED-Dover YELLOW-Oxford
1750 YELLOW-Dover 3640
10.3.3.3 3640 100.200.200.102
100.200.200.109 100.200.200.111
? Attackers cannot gain access into Test Network Topology

VPNs or Service Provider’s network Security
? Impossible for attacker to insert

“spoofed” label into a Cisco MPLS
network and thus gain access to a
VPN or the MPLS core
RST-130
Key Features (Cont.)
• Quality of Service:
Flexible and scaleable support for a CoS-
based networks
• Scalability:
Total capacity of the system isn’t bounded by
the capacity of an individual component
Scale to virtually unlimited number of VPNs
per VPN Service Provider and scale to
thousands of sites per VPN
RST-130
Presentation_ID.scr
Key Features (Cont.)
• Connectivity to the Internet:

VPN service providers may also provide connectivity
to the Internet to its VPN customers
Common infrastructure is used for both VPN and the
Internet connectivity services
• Simplifies operations and management for VPN
service providers:
No need for VPN service providers to set up and
manage a separate backbone or “virtual backbone”
for each VPN
RST-130
BGP/MPLS VPN—Summary
• Supports large scale VPN service

• Increases value add by the VPN service
provider
• Decreases service provider cost of
providing VPN services
• Mechanisms are general enough to enable
VPN service provider to support a wide
range of VPN customers
RST-130
Presentation_ID.scr
MPLS Traffic Engineering
RST-130
What Is MPLS Traffic Engineering?
• Process of routing data traffic in order to

balance the traffic load on the various
links, routers, and switches in the network
• Key in most networks where multiple
parallel or alternate paths are available
RST-130
Presentation_ID.scr
Why Traffic Engineering?
• Congestion in the network due to changing traffic
patterns
Election news, online trading, major sports events
• Better utilization of available bandwidth

Route on the non-shortest path
• Route around failed links/nodes
Fast rerouting around failures, transparently to users
Like SONET APS (Automatic Protection Switching)
• Build new services—Virtual leased line services

VoIP toll-bypass applications, point-to-point bandwidth guarantees
• Capacity planning
TE improves aggregate availability of the network
RST-130
IP Routing and the Fish
R3
R4
R8 R5
R2
R1
R6 R7
IP (Mostly) Uses Destination-Based Least-Cost Routing

Flows from R8 and R1 Merge at R2 and Become Indistinguishable
From R2, Traffic to R3, R4, R5 Use Upper Route
Alternate Path Under -Utilized

RST-130
Presentation_ID.scr
Applications of MPLS TE
Link and Node Protection R9
R8
R3
R4
R2
R1 R5
R6 R7
Mimic SONET APS
Reroute in 50ms or Less
• Multiple hops can be by-passed. R2 swaps the label which

R4 expects before pushing the label for R6
• R2 locally patches traffic onto the link with R6
RST-130
DiffServ Aware TE Virtual Leased Line

Class 5
Legacy
PSTN— switches
Traditional TDM
Traditional Central Network Central Traditional
Telephony Office Office Telephony
MPLS
Network
VoIP Toll Bypass VoIP
Voice
Voice Trunking
Trunking Gateway Gateway
PE GB
Tunnel PE
PE PE
CE Regular TE CE
Enterprise Tunnel Enterprise
LAN LAN
PE PE
GB-TE Tunnel
VPN
VPN Service
Service Regular TE Tunnel
Physical Link
Internet
Internet Service
Service Enterprise Internet Internet Enterprise
LAN Access Router Access Router LAN
RST-130
Presentation_ID.scr
MPLS TE Summary
• Useful for rerouting traffic in congested

environments
• Build innovative services like virtual
leased line
• Build protection solutions using
MPLS FRR
RST-130
Summary
RST-130
Presentation_ID.scr
MPLS: The Key Technology for IP
Service Delivery
ATM
ATM IP
IP
Services Services
Services Services
• IP+ATM: MPLS brings IP and ATM together

IP
IP
Eliminates IP “over” ATM overhead and complexity
PNNI
PNNI MPLS
MPLS One network for Internet, Business IP VPNs, and transport
IP+ATM
IP+ATM Switch
Switch
• Network-based VPNs with MPLS:

a foundation for value-added service delivery
Flexible user and service grouping (biz-to-biz)
Flexibility of IP and the QoS and privacy of ATM
Enables application and content hosting inside each VPN
Transport independent
Low provisioning costs enable affordable managed services
RST-130

Service Delivery
• MPLS traffic engineering

Provides routing on diverse paths to avoid congestion
Better utilization of the network
Better availability using protection solution (FRR)
• Guaranteed bandwidth services

Combine MPLS traffic engineering and QoS
Deliver point-to-point bandwidth guaranteed pipes
Leverage the capability of traffic engineering
Build solution like virtual leased line and toll trunking
RST-130
Presentation_ID.scr
Service Delivery
Optical
Optical IP
IP
Services Services
Services Services • IP+ATM: MPLS brings IP and ATM together
Eliminates IP “over” optical complexity
IP
IP Uses MPLS as a control plane for setting up lightpaths
(wavelengths)
O-UNI
O-UNI MPLS
MPLS
One control plane for Internet, business IP VPNs, and
IP+Optical
optical transport
IP+Optical Switch
Switch
Frame
Frame
Relay
• Any transport over MPLS
Relay
Transport ATM, FR, Ethernet, PPP over MPLS
Provide services to existing installed base
Protect Investment in the installed gear
Leverage capabilities of the packet core
ATM Combine with other packet-based services such as
MPLS VPNs
RST-130
End-to-End Solution
VPN and Traffic Engineering Combined
to Provide End-to-End Services
5 Mbps
VPN HQ
HQ1 1 Mbps
Back-up
MPLS TE
MPLS VPN
RST-130
Presentation_ID.scr
References
• Sessions at Networkers
RST-230 - Deploying Large Scale VPN with MPLS
RST-231 - Deploying MPLS for Traffic Engineering
RST-330 – Troubleshooting MPLS for Traffic Engineering
RST-331 – Troubleshooting ATM MPLS Networks
RST-430 – Advanced Developments & concepts in MPLS
PS-542 – MPLS – Technology, Options and Applications
• Books and IETF

MPLS VPN Architecture – Jim Guichard and Ivan Pepelnjak –
Cisco Press
IETF – http://www.ietf.org
Cisco Web site – http://www.cisco.com/go/mpls
RST-130
Questions?
RST-130
Presentation_ID.scr
Introduction to MPLS
Session RST-130
RST-130
Please Complete Your

Evaluation Form
Session RST-130
RST-130
Presentation_ID.scr
RST-130
Presentation_ID.scr

Introduction To MPLS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Introduction To MPLS

Uploaded by

Copyright:

Available Formats

RST-130

2926_05_2001_c2 © 2001, Cisco Systems, Inc. All rights reserved. 1

• Background and Business Case

• From tag switching

1996 1997 1998 1999 2000 2001

European PTT Deployment Plans

Infonetics European PTT deployment plans by 2001

Source: Cahners Instat

• Generate new services

• Enable ATM switches to act as routers

2. Ingress Edge LSR receives packet,

ATM Cell Header GFC

LAN MAC Label Header MAC

Label Header for Packet Media

Tag COS S TTL

Label = 20 bits COS/EXP = Class of Service, 3 bits

• Can be used over Ethernet, 802.3, or PPP links

Label Distribution Protocol

• Defined in RFC 3036 and 3037

• Advertise labels per FEC

TDP and LDP

• Tag Distribution Protocol

• TDP and LDP supported on the same box

• Used in MPLS traffic engineering

BGP-Based Label Distribution

• Used in the context of MPLS VPNs

Address I/F Address I/F Address I/F

128.89 1 128.89 0 128.89 0

128.89.25.4 Data 128.89.25.4 Data

Packets Forwarded 171.69

MPLS Example: Routing Information

In Address Out Out In Address Out Out In Address Out Out

128.89 1 128.89 0 128.89 0

You Can Reach 128.89 Thru

Routing Updates You Can Reach 171.69 Thru 171.69

In Address Out Out In Address Out Out In Address Out Out

- 128.89 1 4 4 128.89 0 9 9 128.89 0 -

Use Label 9 for 128.89

Label Distribution 171.69

MPLS Example: Forwarding Packets

In Address Out Out In Address Out Out In Address Out Out

- 128.89 1 4 4 128.89 0 9 9 128.89 0 -

128.89.25.4 Data 4 128.89.25.4 Data

Label Switch Forwards

In Address Out Out In In Address Out Out In In Address Out Out

128.89 1 128.89 0 128.89 0

Label Distribution I need a label for 128.89

ATM MPLS Example: Assigning Labels

In Address Out Out In In Address Out Out In In Address Out Out

- 128.89 1 4 4 2 128.89 0 9 9 1 128.89 0 -

- 171.69 1 5 8 3 128.89 0 10 10 1 128.89 0 -

Use label 8 for 128.89 171.69

In Address Out Out In In Address Out Out In In Address Out Out

- 128.89 1 4 4 2 128.89 0 9 9 1 128.89 0 -

- 171.69 1 5 8 3 128.89 0 10 10 1 128.89 0 -

Label Switch forwards 171.69

Why Multiple Labels with ATM?

In In Address Out Out

• If we didn’t allocate multiple labels:

In In Address Out Out

• Multiple labels enables edge router to

In In Address Out Out

• With ATM switch that can merge VC’s: