NGN and MPLS

Monique Morrow
mmorrow@cisco.com
Distinguished Consulting Engineer
November 22 2005
MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

1

AGENDA• Why NGN: The Problem• MPLS Technology Set as an NGN Service Enabler• NGN Service Architecture with GMPLS• NGN and Future Direction with GriD
• Conclusions

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

2

Why NGN: The Problem

MPLS 2005 Japan© 2005 Cisco Systems, Inc. All rights reserved.

3

Converging the Networks

Business
IP/MPLS

L1/L2

MPLS Japan 2005ConsumerVoice© 2005 Cisco Systems, Inc. All rights reserved.

4Converge services onto one networkIntelligent
Edge
L3VPN

L2VPN
MetroEthernet

IP/MPLS
Core

VoIP

FirewallVideo•••••••

Virtualization
Service flexibility
Scalability
Continuous operation
Management
Investment protection
Security

FR/ATM/LL

One Network, Many Services
MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

5

Convergence to Single Network?

Transponder
Transponder

OpticalIPTV

Private IP

Public IP

Transponder
Transponder

Transponder
TransponderCore

Peering

Peer

Peer

Peer

Peer

Distribution
Services
Edge
Access /Aggregation

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

6

Traditional Multi-Layer PoP Design:
Operational Complexity, Limited Flexibility & Scale

OpticalTransponder Transponder

CorePeering

Peer

Peer

Distribution
Services
Edge
Access /Aggregation
Residential
MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

Business• Multiple systems toprovision, manage, &upgrade• Inefficient use ofcapital: Empty slots,
unused capacity• Many intra-PoP links
to implement &maintain• Multiple software
streams to qualify• Difficult to scale, add
new services• Industry moving
towards Core/Edgeconvergence
7

MPLS Technology Set asan NGN Service Enabler

MPLS 2005 Japan© 2005 Cisco Systems, Inc. All rights reserved.

8

MPLS-Related Standards and Alignment withNGN

P Router
CPE (CE)
DevicePE Router

PE Router

MPLS Backbone

CPE (CE)
Device•RFC2547bis (BGP/MPLS VPN)
•Pseudowires and Pseudowire Multi- hop constructs•MPLS- xInterworking (ATM, FR, Ethernet…)•Interprovider QoS•MPLS NM/OAM/MIBs•Multicast VPN•MPLS Security•DiffServ- enabled MPLS Traffic Engineering•Fast Network Protection with MPLS TE fast Reroute•MPLS Performance/Reliability/QoS•GMPLS Protection/Restoration
MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

9MPLS Services and Transport
Network Management for NGN

ScaleMSE

Programmable
Interface

ATM/FR Legacy
FeatureParityPerformance
Connection
Management
L2/L3 + Optical

L3VPN
L3VPN
Instrumentation

Low End Edge
Evolution from TodayManaging CPE

Provisioning
OAM andTroubleshooting
AToM

Multicast VPN
TrafficEngineering

Traffic Eng

Interworking
L2TPv3L2VPN

VLAN
Management

L2 Switch
Management

MAC Address
Management

Metro E

Layer 2/3 Management Essentials:
IP/MPLS Routing, QoS, TE, OAM, HA

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

10

Multicast in NGN Architecture
Three Key Service Trends

Multicast ComponentBroadband Consumer Service Enablement

YES

Triple-play, gaming, content delivery

Video component in Triple Play
service is 90% Multicast Video

Peer-to-Peer Applications
Mass delivery of customized services
Flexible Service bundlingMulticast Games: Half-Life, CounterStrike
Peer-to-Peer : Multicast Kazaa, BitTorrent

Evolution of current SP offerings to Enterprises

YES

L1 bandwidth, L2VPN, L3VPN with value-added services

Multicast VPN as a L3VPN Service for
IPv4 and IPv6

Improving OPEX associated with delivery of ATM, FR ..

Multicast over ATOM, VPLS, PWS

Customized Service delivery and bundling
Converged Wireless and Wire line Services

YES

Enhanced mobility between fixed and wireless services

Multicast and Mobile IP Integration :Department of Defense, Emergency
Services, Hospitals

IMS, 2G transition to 3G & Integration of Fixed & Mobile

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

Multicast support for 3G chipset in11CDMABringing MPLS-TE to Multicast

ControlPlane

FRR
Link Protection

TE P2MPLSP

TE P2PLSP

P2MP RSVP-TE replaces PIM forconstructing and maintaining“MPLS Multicast” states in thecore.
Fast ReRoute can be combinedwith P2MP LSP to minimize
packet loss during link failure.

IP Multicast
ForwardingPlane

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

12

Pseudo-Wire Emulation Edge to Edge andNGN
Emulated VirtualCircuit
SE =IP or MPLS
Backbone

Service-Edgerouter or switch

Attached VC
PE
Pseudo-Wire

L2 Network
PE =L2 Network

Pseudo-wireEdge

CPE Router, FRAD

CPE Router, FRAD

L2transport over IP = L2TPext / L2TP-eth
L2transport over MPLS = pwe3-ethernet / pwe3-mpls-cp
MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

13

NGN Service Architecturewith GMPLS

MPLS 2005 Japan© 2005 Cisco Systems, Inc. All rights reserved.

14

IP+Optical NGN Evolution
IP VPN

Ethernet
VPNInternet
IPv4/v6

Drivers:• Service Virtualization using LR/VR• BW Guarantee, BW protection• Multi- Layer TE for IP+Optical• P2MP TE• MPLS/GMPLS Interworking• IPv4, IPv6 unicast and multicast Services

IP/MPLS/GMPLS

IP VPN

IP VPN

Ethernet
VPN

Ethernet
VPN

SDH/SONET

IPv4/v6

Optical Core Network(OXC and GMPLS)

IPv4/v6

Optical

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

15

Next Generation IP+Optical Networks: A Vision• PCE for :• Inter- AS/Area Path Computation• MPLS/GMPLS Interworking• Multi- Layer TE• P2MP path calculation• LSM for: v4/v6 Multicast overArea-0(G)MPLS- TE• LR/VR: Service Virtualization• Border Model: Logical separationof IP & Optical admin. Boundaries• 6PE/6VPE for IPv6 over GMPLS
Area-0PCC
PCE/
Border RouterService Network 4(e.g., L2VPN)

LR1/
VR1(e.g., L2VPN)
VR0/
LR0

VR3/
LR3

VR0/
LR0

VR0/
LR0
PCE/ BorderRouterService Network 3(e.g., L3VPN)

G-MPLS based
OpticalTransport
NetworkPCE/
Border RouterService Network 2(e.g., L3VPN)
VR4/
LR4VR2/LR2

MPLS Japan 2005

Service Network 1

Area-0FA- LSP

VR0/LR0PCC

PCE / BorderRouter

GMPLS (Optical) tunnel

RSVP Signaling messages

MPLS tunnel

Path request/reply messages (PCE)© 2005 Cisco Systems, Inc. All rights reserved.

16

NGN and Future Direction
with GriD

MPLS 2005 Japan© 2005 Cisco Systems, Inc. All rights reserved.

17

The GRID Network• Were is the GRID?
• How do we build it? Own, lease, share,..
• Multiple Fiber bundles, Lambdas……big BW !!
• Fast provisioning• High flexibility• Scalable• BW on demand• Large investment - what is the business case?

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

18

Grid based EMS/NMS/OSS and AbstractInterfaces• NBI: An EMS or a device (routers, switches) may provide north-boundmanagement interfaces to be used by NMS/OSS or other applications
C&P: Configuration & Provisioning
P&F: Performance & Fault Management
NM NBI: Network Management North-Bound Interfaces
GM-GA: Grid Middleware (OGSA/WSRF based) Serving Grid Applications
Abstracted Interfaces, Resources: OGSA/WSRF based; Needed to hide
network details from GM-GA
GM-GA

P&F

Grid Applications
Grid NetworkC&P

NMApplications• While the NBI exposes much more information,
the information exposed via the abstractinterfaces (A-I) are abstracted and restricted• Example, NBI may provide detail interfaces for
MPLS VPN configuration, such as VRF, MPBGP, hub-and-spoke configurations, but A-I will
provide only interfaces like “join/leave vpn”
• NBI may provide routing related interfaces, suchas for configuring OSPF, but A-I will not

Grid Resources

SP/IT L4-7 Network

Abstracted Resources

SP/IT L3/2/1 NetworkSP/ITNM NBI
SP/IT
Grid-based(OGSA/WSRF)
EMS/
NMS/OSS
MPLS Japan 2005

Abstracted
Interfaces

C&P

L4-7 Resources

P&F
L3/2/1 Resources© 2005 Cisco Systems, Inc. All rights reserved.

19

Abstraction Example: Path and QoS Abstraction• Path (in Operator/SP/Carrier domains): Concatenation of any combination offollowing:• Segments on Edge links• Tunnel/Circuit/LSP in the core
• QoS: Example, Platinum QoS, which can be any of (depending on support)• DiffServ EF• Relevant IntServ QoS• Priority queue + DS-TE tunnel + FRR protection
GRID
MachineGRIDGRIDSite 2Machine
ABC[MPLS VPN
Site 2][G]MPLS TE LSP/Sonet/SDH/Lamda Circuit
GRID
Site 1ABCP1

P4PE2PE1
GRIDMiddleware

Edge Path Segment
P2GRIDMiddleware

P3Internet

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

20

Why Abstracted, Restricted Resource Exposure –Network Technology Angle• Grid Middleware components serving typical Grid Applications should not
be dependent on underlying wide varieties of networking technologies• Either abstract or hide details• For example, Abstract or hide details of• Path: ATM PVC, MPLS LSP, GMPLS LSP, Sonet/SDH Circuit or a Lightpath• VPN: L2VPN, L3VPN• QoS: DiffServ, IntServ, MPLS, etc.

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

21

Conceptual View of Grid Infrastructures
http://forge.gridforum.org/projects/ogsa-wg

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

22

Some Grid Applications• HEP
Today 1 PetaByte per sec
Tens of PetaByte 2008
1 ExaByte 2015

• Distributed Visualization
http://www.evl.uic.edu/cavern/optiputer/
http://www.evl.uic.edu/cavern/continuum/indexmain.html• 3D visualization tools are used• Key tools needed to process & analyze
approximately 64 Tbyte of data by 2008

• Remote screening- Mammography

Continuum - Enhanced Distributed Collaboration
http://www.evl.uic.edu/cavern/continuum/indexmain.html
GeoWall2 (NSF) - GeoScience Advanced Visualization
http://www.evl.uic.edu/cavern/optiputer/geowall2.html

Digitized image results 75MB
Radiologist performs 100 patient readings per day(1 image every 30sec)
16 images per patient results in 16 * 75MByte =1.2GByte
100 patients screened remotely means 1.2 Gbyte
data every 30 sec
MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

23

Future Needs• Change form processor centric to BW dominated computing
http://www.calit2.net/news/2002/9- 25- optiputer.html
Around 2010 Grid applications will require an International Distributed Cyber
Infrastructure based on
Petascale computing, exabyte storage, and terabit networks• Terabit challenge
http://www.cmf.nrl.navy.mil/CCS/
Terabit global Large Data SOA
Integrate federated, distributed computational grids, realtime sensors, and digital
historical information
Scalable to support exponentially increasing dataPrivacy, authenticity and security demands: InfoAssured
Affordable … highly available … E2E QoS/QoP flows
Legacy and rapidly evolving technology integration
Perf, NetOps, Information Assurance tools/sensors

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

24

IETF GMPLS / Peer
http://www.ietf.org/html.charters/ccamp-charter.html••

GMPLS control plane supports multiple
switching and forwarding planes
Introduces new functions to accommodate
circuit-oriented optical network regimes

GMPLS = MPLS + MPλS + N• where N is MPLS control of new switching planes• draft-ietf-ccamp-gmpls-architecture-07.txt
MPLS TERSVP TE

GMPLS Control
Plane
IP Routing Protocols

Label Distribution Protocols
CR LDP, RSVP TE

With Extensions
OSPF, ISISSONETSDH NE

RouterRouterOXC

TE GMPLSPath

TE GMPLS
PathRouter

RouterSONET
SDH NESONETSDH NESONETSDH NE

OXC

OTN

OXC

GMPLS
DomainRouterRouterForwarding Plane
MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

25

ITU-T G.ASON / Overlay
http://www.itu.int/ITU-T/
Internal Network-Node Interface (II-NNI)
NNI
Carries signaling messages between
OCCs within a single domain
Either single operator or subnetwork

Network Management Interfaces(NMI-A & NMI-T)
NMI-A between Management
System and Control Plane
NMI-T between Management
System and Transport Plane

Connection Controller Interface (CCI)
Instructs switches to make connections
across ports
Some topology information may be carriedUser Network Interface (UNIUNI)
Carries signaling between the Userand the OCC (Control Plane)

Management
Plane
NMI-A

ASON Control Plane

NetworkManagement
Systems

OCC
NMI-T

UNI
OIF/IETF
Signaling

Client Datae.g. IP,ATM, TDM
MPLS Japan 2005

OCC

OCC

OCC

E-NNI

I-NNI
IETF GMPLS
CCIIETF GSMPExternal Network-Node Interface (EE-NNI)
NNIcarries signaling information between
separate domains

Transport Plane
OCC – Optical Connection Controller© 2005 Cisco Systems, Inc. All rights reserved.

26

GUNI - Grid User Network Interface
GMPLS and OUNI Extensions
GUNI Functionality

Details

Direct service invocation

User/client requests a specific Grid service
Client directly attached to the transport network and is member of the service signaling process.
Client implements the signaling and the neighbor discovery functions

Indirect service invocation

User/client requests a specific Grid service through an agent
Client invokes transport network services using proxy signaling
Integration of UNI based services without UNI based functionality in each client

Optical transport format for control
messages

Circuit/wavelength/frame switching with out of band signaling
Flow/burst/packet switching with signaling packets or control bursts
Hybrid switching

Flexible bandwidth allocation

Allows for wavelengths, sub-wavelengths, wavelengths bundle allocation
Includes multi homing, dual homing, OVPN, Ethernet and G.709

Claim of existing agreements

Allows for wavelengths, sub-wavelengths, wavelengths bundle allocation
Includes multi homing, dual homing, OVPN, Ethernet and G.709

Automatic, timely light-path setup

Automatic neighbor discovery
Automatic service discovery
Might be related to agreement covering future time interval

Fault detection, protection, restoration

Necessary to support variety of Grid service requirements and sensitivity levels
Support of different protection and restoration signaling schemes

Propagation of service agreements andrelated events

Asynchronous event support for adaptive application services
Ability to notify requester about events causing service provisioning problems

Traffic classification, grooming,
shaping, transmission entity

Mapping of data traffic to transmission entities like bursts at physical (data) layer
Mapping of control messages for in-band signaling

Control and data plane security

Control plane security credentials and policy information
Data plane transport security

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

27

Network Scaling
2005
Today

0-2Years

3-5Years

5 - 15Years

Optical Streams

1- 10
Gbps

10- 40Gbps

120- 640
Gbps

1- 10
Tbps

Optical Ctrl Plane

STATIC
Provisioned

DYNAMICGMPLS

DYNAMIC
Burst/JIT
GMPLS

DYNAMIC
Burst/Flow
GMPLS

Control PlaneSTATICTunnel

DYNAMICSIPSIP
QoS / QoPLAN / WAN
Technology

IPv410GE
OC124xSDR IB

IPv610GE
4x/12x SDR/DDR
IB

IPv6100GE
12xQDR IB
64- 128 IB

All Optical
SystemInterconnect

Security Devices

1.0G IPv4FW, K5, 3DES,CBs, KGs,
NTAM

10G KGs
HAIPEs, CAC,
FEON, PKI,NTAM

40G HAIPE
Scalable GFP
Encrypter

640G HAIPE
GFP Encrypter

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

28

Conclusions

MPLS 2005 Japan© 2005 Cisco Systems, Inc. All rights reserved.

29

Conclusions• MPLS technology as innovative foundation for NGN• Technology is evolving to facilitate convergence andservice creation• Optical and GMPLS can become key NGN service
architecture foundation• Moving to the future MPLS and Optical very relevant toGriD applications

MPLS Japan 2005

© 2005 Cisco Systems, Inc. All rights reserved.

30

Domo Arigato!

Presentation_ID
MPLS Japan 2005©
Cisco Systems,Systems, Inc.
Inc. AllAll rights
rights reserved.
reserved.
© 2003,2005 Cisco

3131