Escolar Documentos
Profissional Documentos
Cultura Documentos
Agenda
1. T-MPLS Rationale
2. T-MPLS Features
3. T-MPLS Standard Status & Perspectives 4. T-MPLS Applications 5. Conclusions
T-MPLS Rationale
Transport network evolution (min cost) with (max carrier-class Reliability, availability, & flexibility) OAM in service delivery
Packet Transport Network: Requirements Being client-agnostic (able to carry L3, L2, L1) Being strictly connection-oriented Implementing strong OAM capabilities, similar to those available in existing transport networks (e.g., SDH) Implementing both service and line resilience mechanisms, similar to those available in existing transport networks (e.g., SDH) Allowing for network provisioning either via a centralized management tool and/or a distributed CP Allowing for homogeneous and/or unified management and control of transport network when different layers are present at the same time
Management Plane Control Plane Data Plane Survivability (Protection, Restoration) OAM
Common multilayer operations, survivability, control and management paradigms for packets, circuits & photonics
6 | Transport MPLS Rationale and Features | February 2007 All Rights Reserved Alcatel-Lucent 2006, 21407
T-MPLS features
Transport MPLS (T-MPLS) in Brief Transport MPLS is a connection-oriented packet transport technology, based on MPLS frame formats. It reuses the most widespread label swapping paradigm existing in telecom.
It inherits all IETF definition activity in terms of server and client encapsulation rules.
It profiles MPLS so that it avoids the complexity and need for IP routing capability. Transport MPLS defines powerful OAM capabilities that enable status & performance reports, in such a way that they remain confined within the T-MPLS layer and do not require deeper packet inspection. It allows for guaranteed SLAs. It defines protection switching and restoration.
T-MPLS
OAM
MPLS frame, forwarding, encapsulation Circuit frame, forwarding, encapsulation (SDH, OTH)
No penultimate hop popping Is not in line with an L2 confined OAM No merging Would not allow an L2 confined OAM per connection No equal cost multipath (ECMP) Would imply frame re-ordering Adds bidirectional LSPs Typically used in transport contexts
9 | Transport MPLS Rationale and Features | February 2007
TMPLS is: Strictly connection-oriented Strictly L2-bound (it does not need any IP for data plane, e.g. OAM) Homogeneous with other transport layers (SDH, OTH) as regards basic network features, i.e. OAM, protection, (optional) control plane, management plane
T-MPLS equipment (switching capability either at circuit or path layer) Client A Client D
Client A Client D
Client B Client C
Clients: in T-MPLS it can be any L2, using mapping options defined by IETF for PWE3: Ethernet, ATM, FR ) or IP/MPLS (so far only Ethernet formally defined in ITU)
Logical connection: in T-MPLS TMPLS two two networking networking layers are under definition: circuit (equivalent to IETF PWE3) and path (equivalent to IETF MPLS tunnel)
Physical connection: in T-MPLS it can be any L1 (Ethernet, SDH, OTN+WDM ); moreover in T-MPLS an optional section layer is under definition, in order to support OAM if not otherwise available
Client C
Client B
T-MPLS Survivability
T-MPLS Client Equipment
Circuit & Path Protection Ring Protect DNI
Client Equipment
Section Protection
T-MPLS OAM
Transport service functional model Client
Client
Non-intrusive monitoring integrity check connectivity check quality check Client-server adaptation forward defect indication
Termination Like non-intrusive mon. + backward integrity info backward quality info Connection forwarding grooming
Logical Connection
Client-server adaptation forward defect indication Termination Like non-intrusive mon. + backward integrity info backward quality info
All Rights Reserved Alcatel-Lucent 2006, 21407
Physical Connections
T-MPLS OAM
Simplified network model & basic OAM tools
Client Logical Connection Physical Connection
Protection
Fiber
Integrity
Connection
Integrity
Connection
Quality
Quality
Remote integrity Remote quality
Maintenance
Integrity
Connection
Quality
Silencing
Integrity
Congruence Connection Quality Remote integrity Remote quality
Integrity
Congruence Connection Quality
Silencing
Integrity
Congruence Connection
Quality
Remote integrity Remote quality
Quality Measurement
Integrity
Connection
Quality Integrity
Connection
Integrity Connection Quality Integrity Connection Quality Remote integr. Remote quality
All Rights Reserved Alcatel-Lucent 2006, 21407
Quality
T-MPLS OAM
Standardized
On demand
Loopback Link Trace (ffs)
OAM primitives
Integrity Connectivity
Continuous
FFD, CV FFD
Ongoing
Quality
PM (carried by FFD)
BDI FDI
Fiber (i)
FFD FFD (via TTSId) PM BDI
Client specific Client specific Client specific CV, FFD Link Trace PM Silencing CV, FFD CV, FFD PM BDI Remote quality CV, FFD CV, FFD PM
Server specific
Server specific
Server specific
Server specific Server specific
Maintenance
FDI
Server specific Server specific Server specific Server specific Server specific
Quality Measurement
T-MPLS Control Plane (ASON/GMPLS) GMPLS is a single, generalized distributed control plane that can be used in common for multiple networking technologies, including packets, TDM and photonics GMPLS defines: UNI concept (thus easing overlay dynamic approach) I(nternal)-NNI concept (the only supported in MPLS CP) E(xternal)-NNI concept (thus allowing for interworking among different vendors/operators) Bidirectional paths GMPLS allows for separation of data plane and control plane Only control interfaces are used to flood control information GMPLS allows for horizontal scalability in routing domains (thanks to separation of data plane and control plane and recursive topology) GMPLS allows for vertical scalability (same control plane across different layers)
GMPLS is the ideal control plane for multilayered networks
16 | Transport MPLS Rationale and Features | February 2007 All Rights Reserved Alcatel-Lucent 2006, 21407
T-MPLS Equipment Functional Blocks G.8121 Architecture of T-MPLS Layer Network G.8110.1
TMPLS Framework
OAM Y.17tom
T-MPLS standard status Version 1 approved Amend. 1 (p2mp, extended OAM) to be consented Mar-Jun07 Version 1 approved Amend. 1 (p2mp) to be consented Mar-Jun07 Y.1711 approved Y.17tom (ext. OAM, TC) to be consented Apr07 Version 1 approved Amend. 1 (p2mp, protection) to be consented Mar-Jun07 Y.1720 approved G.8131 v1 (adaptation to T-MPLS) consented Amend. 1 (ring) to be consented Jun07
SDH
Network Architecture
G.803
G.872
----
----
Equipment
G.783
G.798
G.8121 (G.mplseq)
G.806
Linear Protection
G.841
G.873.1
G.8131 (Y.1720)
G.808.1
Ring Protection
G.873.2 (frozen)
G.8132
G.808.2 (frozen)
T-MPLS Applications
Inner T-switch
Outer T-switch
Client PDH, STM E-line E-LAN (802.1ad) E-LAN (VPLS-like) MPLS (tunnel) MPLS (PW) CP None None STP None LDP, RSVP, OSPF, IS-IS (MS)-LDP p2p, mp2mp p2p p2p mp2mp mp2mp mp2mp mp2mp DP technology ODU SONET, SDH T-MPLS Ethernet CP technology GMPLS (or NM) GMPLS (or NM) GMPLS (or NM) GMPLS (or NM) STP (NM, GMPLS)
(PE)
(P)
(PE)
T-MPLS Network
1:1
1:1
1:N
Y.17tom
Y.17tom
3G Node B 2G BTS
N x E1 TDM
Mobile backhauling applications typically require the coexistence of TDM (E1, T1) streams along with L2 (ATM, Ethernet) streams on the same aggregation network
Mobile Controller Center
BACKBONE
BS
FE
Agnostic network with packet Aggregation network transport evolving to T-MPLS (e.g. UTRAN)
MSC
RNC N x E1 TDM
2G BTS
3G Node B
BS BS
Migration towards T-MPLS allows for QoS, traffic engineering, OAM, protection and statistical multiplexing under a common operation paradigm with the other transport layers.
T-MPLS Network
MPLS PW
MPLS PW
1:1
MPLS tunnel
1:1
MPLS tunnel
1:N
Y.17tom
PE(P)
T-switch
T-switch
PE(P)
T-MPLS
DP: MPLS CP: MPLS OAM: MPLS Protection: MPLS DP: MPLS CP: MPLS OAM: MPLS Protection: MPLS
MPLS tunnel with MPLS label swap T-MPLS path with T-MPLS label swap
26 | Transport MPLS Rationale and Features | February 2007
T-MPLS is an overlay network with respect to MPLS PE-P routers are aware of border T-switch only The interface between a border T-switch and a PE-P router is a MPLS interface Two different MPLS/GMPLS interworking solutions can be defined, trusted and not trusted
T-MPLS Network
Client
MPLS tunnel
MPLS tunnel
MPLS tunnel MPLS tunnel T-MPLS circuit T-MPLS path T-MPLS path
MPLS tunnel
1:1
1:1
1:N
Y.17tom
Conclusions
Conclusions The Transport Network doesnt change role over time Scalability, multiservice, quality, and lowest-cost-per-bit are invariable requirements, always
Transformation to all-IP service model calls for a comprehensive Packet Transport Networking technology
T-MPLS is carrier-grade, purpose-designed for Packet Transport Networking Synthesis of excellence from the two worldwide authorities on packets (IETF) and transport (ITU) MPLS-based, but transport-oriented (OAM-friendly) Client-independent, medium-independent (multiservice) Cost-effective (comprehensive operations, IP-free)
www.alcatel-lucent.com