Capitalizing on New Standards for ATM to MPLS Convergence

John Sax, CTO, Data Networking Group, Lucent Technologies

Dr. Kireeti Kompella, Distinguished Engineer, Juniper Networks

Mark Bieberich, Program Manager, The Yankee Group

2

• CAPEX and OPEX constraints necessitate phased migration to a converged IP/MPLS network.

– Wholesale replacement of Layer 2 Edge is not economically feasible.

• Carriers must sustain profitable FR/ATM service revenue during the IP/MPLS core consolidation process.

– Today’s FR/ATM service customers require QoS and SLAs to remain intact as traffic migrates to IP/MPLS core.

• Carriers must achieve operational parity between ATM and MPLS network domains.

– Layer 2 service provisioning and management processes must be preserved in an IP/MPLS network environment.

• Inherent reliability characteristics of ATM must remain intact as traffic migrates to the IP/MPLS core.

– ATM signaling and protection mechanisms remain essential to service and network reliability.

Market Drivers for ATM to MPLS Interworking Standards

3

IP/MPLS Convergence ATM - MPLS Interworking Occurs in Phase II

Phase I

Announcement of IP/MPLS consolidation plan

Initial investment in IP/MPLS core begins; first phase of core POPs upgraded or deployed

New enterprise, residential IP-based services targeted

2003 – 1H04 1H04 – 1H06 1H06 – 2008

Phase II

Core expansion continues; edge investment accelerates

Targeted services from Phase I experience high

revenue growth

Limited number of legacy routers and switches

decommissioned

INITIATION SERVICE PROFIT ADOPTION REALIZATION

Phase III

Critical mass of traffic from overlay networks now converged to IP/MPLS core

Enterprise and residential IP-based services proliferate

Profitability goals of IP-based services achieved

4

Layer 2 Traffic Migration to IP/MPLS CoreAccelerating the Need for ATM to MPLS Interworking

• Recent Yankee Group Research:

– Aggressive service providers plan to migrate up to 50 percent of their FR/ATM service traffic to the IP/MPLS Core in the next 3 years.

4%

14%

27%

0

5

10

15

20

25

30

2004 2005 2006

Rate of Traffic Migration From ATM to MPLS Core*

*taken from an ’04 Yankee Group survey of 15 top service providers worldwide

*taken from an ’04 Yankee Group survey of 15 top service providers worldwide

5

• Plans for IP/MPLS network consolidation must embrace standards that protect growing, profitable revenue streams.

ATM to MPLS Interworking Standards Requirement for Protecting Profitable Services

0

2,000

4,000

6,000

8,000

10,000

12,000

14,000

2004 2005 2006 2007 2008

Rev

enu

e in

mill

ion

s o

f $U

S

ATM Service Revenue

FR Service Revenue

North America FR/ATM Service Revenue Forecast Source: the Yankee Group, 2004

6

A. Minimizing CAPEX and OPEX while consolidating networks

B. Sustaining profitable FR/ATM service revenue with QoS

C. Achieving operational parity between ATM and MPLS network domains

D. Preserving network reliability characteristics of ATM as traffic migrates to MPLS

Poll #1: Which business driver is most important to your plans for adopting standards-based ATM to MPLS interworking?

7

Together, Lucent and Juniper Drive for standardized, scalable ATM to MPLS Interworking

• Lucent - Juniper Multiservice MPLS Core solution, jointly developed, implements MPLS standards to deliver ATM over MPLS interworking:

– Standards-based, dynamic interworking between ATM and MPLS

– Scalable methods to distribute ATM routing information across the MPLS network

• Lucent and Juniper contributions to the MPLS/FR Alliance efforts build upon our joint Multiservice MPLS Core Solution (Releases 1 and 2)

MPLS/FR Alliance progress:

• Distributed Model for ATM to MPLS Interworking

• Virtual Trunks for scaling ATM networks across an MPLS core

• Multi-protocol Border Gateway Protocol (MP-BGP) for ATM address reachability information

8

• Router performs both ATM routing and signaling and MPLS path setup.

– Label Edge Router (LER) must scale 1,000’s of ATM VPs into MPLS Pseudowire, only one opportunity to aggregate services.

– Separate network management systems must be integrated.

Existing ATM Network

MPLS Network

Label Edge Router (LER)

Label Edge Router

(LER)

LER AggregatesATM VPs

ATM SwitchATM Switch

Pseudowire PSN Tunnel

Existing ATM Network

Combined management ofATM and MPLS networks

ATM to MPLS Interworking StandardsMPLS/FR Alliance - Integrated Model, Option #1

9

• Adds a third network element – a hybrid that combines both switching and routing.

– Requires a router in the core of the network.

– Three box solution, requires significant incremental investment.

– Separate network management systems must be integrated.

Label Edge Router (LER)Existing ATM

Network

ATM Switch

MPLS Network

Label Edge Router

(LER)

ATM Switch

Existing ATM Network

160G+ New Hybrid Network Element

Three Boxes Needed in Network

ATM to MPLS Interworking StandardsMPLS/FR Alliance - Integrated Model, Option #2

10

ATM to MPLS Interworking Standards MPLS/FR Alliance Distributed Model, Option #3Based on Lucent - Juniper Multiservice MPLS Solution, Available Today

• Distributed functionality on existing ATM switches, and Routers - allows service provider to leverage existing assets with minimal incremental investment.

– Preserves ATM functions on the ATM switch (requires limited software upgrades to existing switches), and the routing functions on the router.

• MPLS router (LER) is not needed to support ATM signaling and routing, or interwork individual VCs or VPs.

• ATM switches aggregate VPs into a Virtual Trunk before sending to MPLS router .

MPLS Network

ATM Switches aggregate connections

Virtual Trunk

Aggregation Point #1

Aggregation Point #2

MPLS

Router

(LER)

MPLS Router

(LER)

Administrative separationbetween ATM and MPLS

Existing ATM Network

ATM Switch

Existing ATM Network

ATM Switch

11

Issue: 1:1 VC/VP to LSP Mapping

• 1:1 VP to LSP association requires interworking each ATM VP with a single MPLS path.

• Creates signaling and data plane scalability issues.

ATM to MPLS Interworking Standards: Signaling and Data Plane Scaling IssuesExisting Networks

1 mbps

5 mbps

10 mbps

30 mbps

ATM InterfaceOn Switch

POS Interface on Router

Requires interworking each ATM VP with each MPLS path

LSP

CBR VP

VBR rt VP

VBR nrt VP

UBR VP

12

Solution:

• Perform VP bundling to aggregate ATM VPs into an ATM Virtual Trunk before sending to the LER.

• Simplify scaling of ATM VPs across MPLS core.

• Groom 1000’s of VCs into virtual trunks for transport across MPLS core.

ATM to MPLS Interworking Standards: Solving Signaling ScalabilityNew Standards Progress with Virtual Trunks

New Standards progress:

Virtual Trunk Concept

1 mbps

5 mbps

10 mbps

30 mbps

ATM InterfaceOn Switch

POS Interface on Router

Aggregation of 1000’s VPs into Virtual trunks with automatic provisioning

LSPVirtual Trunk

CBR VP

VBR rt VP

VBR nrt VP

UBR VP

13

Lucent/Juniper Multiservice MPLS Core SolutionDelivering ATM QoS and SLAs

– Bundles ATM QoS priorities into single Trunk VPN label/Pseudo Wire

– QoS treatment of traffic Emulates ATM

– Facilitates bandwidth sharing amongst service classes

– Maintains cell loss priority

Queues

CBR

VBR rt

VBR nrt

ABR/UBR

QoS Flows BasedQoS Flows Basedon EXP Bitson EXP Bits

POS Interface (Router)

PE to PE E-LSPs(PSN Tunnel)

Trunk VPN Label(Pseudo Wire)

MPLS LabelMPLS Label

LABEL Exp S TTL

32 bits = 4 bytes (octets)

20 3 1 8

14

ATM to MPLS Interworking Standards: Routing Scaling IssuesExisting Networks Require Full Mesh ATM Routing Across MPLS Core

Frame/ATM Frame/ATM EdgeEdge

Frame/ATM Frame/ATM EdgeEdge

Frame/ATMFrame/ATMEdgeEdge

Frame/ATM Edge

Frame/ATM Frame/ATM EdgeEdge

Frame/ATM EdgeFrame/ATM Edge

Frame/ATM Frame/ATM EdgeEdge

Frame/ATM Frame/ATM EdgeEdge

IP/MPLS CoreIP/MPLS Core

Issue: Connecting large numbers of ATM sub networks over an MPLS core.

• Must transport ATM routing information through an MPLS network.

• ATM switches need to maintain routing adjacencies with all other ATM switches through MPLS core.

ATM switches support a limited number of adjacencies, limiting scalability.

15

Solution: Use Multiprotocol-Border Gateway Protocol (MP-BGP) for ATM address reachability information

• Enables ATM network to import and export ATM address information through the MPLS core by exchanging information with a single edge router

• Increases scalability by reducing ATM adjacencies without sacrificing full connectivity

• Utilizes MP-BGP’s proven scalability for IP VPNs and Internet routing

• Simplifies administration by leveraging one protocol (BGP) for multiple services

ATM to MPLS Interworking Standards:Solving Routing Scaling IssuesNew Standards Progress with MP-BGP

New Standards progress: MP-BGP to distribute ATM routing information

Frame/ATM Frame/ATM EdgeEdge

Frame/ATMFrame/ATMEdgeEdge

Frame/ATM Frame/ATM EdgeEdge

Frame/ATM EdgeFrame/ATM Edge

Frame/ATM Frame/ATM EdgeEdge

Frame/ATM Frame/ATM EdgeEdge

IP/MPLS CoreIP/MPLS Core

MP-BGP distributes ATM address Information

Frame/ATM Edge

Frame/ATM Frame/ATM EdgeEdge

16

Lucent OSS Software

Lucent –Juniper Standards Based ATM to MPLS Interworking

M/E

FR, ATM Services

CBX 500

IP Services

EthernetServices

IP Services

M/E

FR, ATM Services

T-series M320

CBX 3500

CBX 500

GX 550

Distributed Architecture

MP-BGP for ATM routing information

T-series

EthernetServices

Virtual Trunk

MPLS/FR Alliance Distributed Model for ATM to MPLS Interworking increases scalability and manageability by:

– Separating ATM signaling from the MPLS network to achieve higher scalability

– Giving providers a solution for aggregating ATM traffic over the MPLS network

– Distributing ATM address information in a scalable fashion

Release 2 of Multiservice MPLS Solution architected to fully realize ATM to MPLS interworking standards

– Solution also allows service providers to maintain standard ATM and MPLS service restoration and fault management tools

Lucent and Juniper together will promote progress to other standards bodies including IETF, ITU-T for adoption

Lucent - Juniper Partnership Unified Standards Efforts, Unified Solutions

17

A. Preserving quality of service over the MPLS core

B. Scaling ATM connections over the MPLS core

C. Dynamic signaling between the ATM and MPLS networks

D. Preserving network reliability end to end

Poll #2: What is your top concern with respect to deploying standards-based ATM to MPLS?

18

•Standards minimize OPEX by preserving established network management processes; reduces incremental CAPEX

– MPLS/FR Alliance Distributed Model maximizes the utility of existing assets and separates ATM and MPLS operational boundaries.

•Standards maintains QoS in a scalable fashion through the IP/MPLS core; preserves operational parity between ATM and IP/MPLS domains

– Use of Virtual Trunks improves network scalability and simplifies the provisioning process.

•Standards ensure reliable control plane operations by standardizing on a common protocol for address distribution

– Advancements in standards such as MP-BGP solve routing scalability issues.

Standards Enable Convergence Today Converge the Best of Both Worlds to ProfitToday and Tomorrow

Questions & Answers

John Sax, CTO, Data Networking Group, Lucent TechnologiesDr. Kireeti Kompella, Distinguished Engineer, Juniper NetworksMark Bieberich, Program Manager, The Yankee Group