1. 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. Market Drivers for ATM to MPLS Interworking Standards
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.

3. IP/MPLS Convergence ATM - MPLS Interworking Occurs in Phase II
INITIATION SERVICE PROFIT ADOPTION REALIZATION
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
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
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
2003 – 1H H04 – 1H H06 – 2008

4. Rate of Traffic Migration From ATM to MPLS Core*
Layer 2 Traffic Migration to IP/MPLS Core Accelerating 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.
Rate of Traffic Migration From ATM to MPLS Core* 30
27% 25 20
14% 15 10 4% 5
*taken from an ’04 Yankee Group survey of 15 top service providers worldwide
2004
2005
2006

5. ATM to MPLS Interworking Standards Requirement for Protecting Profitable Services
Plans for IP/MPLS network consolidation must embrace standards that protect growing, profitable revenue streams.
North America FR/ATM Service Revenue Forecast Source: the Yankee Group, 2004
2,000
4,000
6,000
8,000
10,000
12,000
14,000
2004
2005
2006
2007
2008
Revenue in millions of $US
ATM Service Revenue
FR Service Revenue

6. Poll #1: Which business driver is most important to your plans for adopting standards-based ATM to MPLS interworking?
Minimizing CAPEX and OPEX while consolidating networks
Sustaining profitable FR/ATM service revenue with QoS
Achieving operational parity between ATM and MPLS network domains
Preserving network reliability characteristics of ATM as traffic migrates to MPLS

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. Label Edge Router (LER)
ATM to MPLS Interworking Standards MPLS/FR Alliance - Integrated Model, Option #1
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 Aggregates
ATM VPs
ATM Switch
Pseudowire
PSN Tunnel
Combined management of
ATM and MPLS networks
Both models use an interworking function --Pseudowire Service Interface—to link ATM network to the MPLS network
Client Control Plane is linked to the Pseudowire control plane
Client control plane manages client service requests in the ATM network
Pseudowire control plane sets up, tears down, and maintains the pseudowires that transport the services through the MPLS core

9. Label Edge Router (LER) 160G+ New Hybrid Network Element
ATM to MPLS Interworking Standards MPLS/FR Alliance - Integrated Model, Option #2
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.
Three Boxes Needed in
Network
Label Edge Router (LER)
Label Edge Router
(LER)
Existing ATM
Network
ATM Switch
Both models use an interworking function --Pseudowire Service Interface—to link ATM network to the MPLS network
Client Control Plane is linked to the Pseudowire control plane
Client control plane manages client service requests in the ATM network
Pseudowire control plane sets up, tears down, and maintains the pseudowires that transport the services through the MPLS core
Existing ATM
Network
MPLS Network
ATM Switch
160G+ New Hybrid Network Element

10. ATM to MPLS Interworking Standards MPLS/FR Alliance Distributed Model, Option #3 Based 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
Point #2
MPLS
Router
(LER)
MPLS Router
Administrative separation
between ATM and MPLS
Existing ATM
Network
ATM Switch
Both models use an interworking function --Pseudowire Service Interface—to link ATM network to the MPLS network
Client Control Plane is linked to the Pseudowire control plane
Client control plane manages client service requests in the ATM network
Pseudowire control plane sets up, tears down, and maintains the pseudowires that transport the services through the MPLS core

11. ATM to MPLS Interworking Standards: Signaling and Data Plane Scaling Issues Existing Networks
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.
Requires interworking each ATM VP with each MPLS path
CBR VP
1 mbps
VBR rt VP
5 mbps
VBR nrt VP
10 mbps
30 mbps
UBR VP
LSP
ATM Interface
On Switch
POS Interface on Router

12. ATM to MPLS Interworking Standards: Solving Signaling Scalability New Standards Progress with Virtual Trunks
New Standards
progress:
Virtual Trunk Concept
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.
Aggregation of 1000’s VPs into Virtual trunks with automatic provisioning
CBR VP
1 mbps
VBR rt VP
5 mbps
VBR nrt VP
10 mbps
30 mbps
UBR VP
Virtual
Trunk
LSP
ATM Interface
On Switch
POS Interface on Router

13. Lucent/Juniper Multiservice MPLS Core Solution Delivering 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
MPLS Label
QoS Flows Based
on EXP Bits
CBR 20 3 1 8
VBR rt
LABEL
Exp S
TTL
- Added these interfaces (ATM and POS) are on routers
VBR nrt
32 bits = 4 bytes (octets)
Trunk VPN Label
(Pseudo Wire)
ABR/UBR
PE to PE E-LSPs
(PSN Tunnel)
Queues
POS Interface (Router)

14. ATM to MPLS Interworking Standards: Routing Scaling Issues Existing Networks Require Full Mesh ATM Routing Across MPLS Core
ATM switches support a limited number of adjacencies, limiting scalability.
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.
Frame/ATM Edge
Frame/ATM Edge
IP/MPLS Core

15. ATM to MPLS Interworking Standards: Solving Routing Scaling Issues New Standards Progress with MP-BGP
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
New Standards progress:
MP-BGP to distribute
ATM routing information
Frame/ATM Edge
Frame/ATM Edge
IP/MPLS Core
MP-BGP distributes
ATM address
Information

16. Lucent –Juniper Standards Based ATM to MPLS Interworking
Lucent - Juniper Partnership Unified Standards Efforts, Unified Solutions
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 Standards Based ATM to MPLS Interworking
MP-BGP for ATM
routing information
Distributed Architecture
FR, ATM Services
FR, ATM Services
Virtual Trunk
T-series
T-series
CBX 500
M320
CBX 500
M/E
M/E
CBX 3500
GX 550
IP Services
IP Services
Ethernet Services
Ethernet Services
Lucent OSS Software

17. Poll #2: What is your top concern with respect to deploying standards-based ATM to MPLS?
Preserving quality of service over the MPLS core
Scaling ATM connections over the MPLS core
Dynamic signaling between the ATM and MPLS networks
Preserving network reliability end to end

18. Standards Enable Convergence Today Converge the Best of Both Worlds to Profit Today and Tomorrow
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.

19. Questions & Answers
John Sax, CTO, Data Networking Group, Lucent Technologies Dr. Kireeti Kompella, Distinguished Engineer, Juniper Networks Mark Bieberich, Program Manager, The Yankee Group