MPLS-TP In Multi-Service Packet Network Deployments Tutorial
MPLS-TP in Multi-Service PacketNetwork Deployments TutorialMR-245October 2010
Agenda1. Introduction to the Broadband Forum2. Technology, Market and Business drivers3. MPLS-TP Technology Overview –Architecture, data plane, OAM, control plane,survivability4. MPLS(-TP) Use Cases5. Broadband Forum Applicability6. Network Scenarios7. Summary2
We are the Broadband Forumhttp://www.broadband-forum.org The Broadband Forum is the central organization drivingbroadband solutions and empowering converged packetnetworks worldwide to better meet the needs of vendors,service providers and their customers. We develop multi-service broadband packet networkingspecifications addressing interoperability, architecture andmanagement. Our work enables home, business andconverged broadband services, encompassing customer,access and backbone networks. Disclaimer: this tutorial is provided solely for educationalpurposes. At this point, the applicability of MPLS-TP to BBFarchitectures and solutions is under active study. Optionsshown are examples of potential uses. Implementations andarchitectural requirements are specified in BBF TechnicalReports.3
The BroadbandSuiteGoals and FocusThe BroadbandSuite is broken down into three major domains: BroadbandManagement– Goal – enhance network management capabilities and enable anintelligent, programmable control layer that unifies diverse networks– Focus - empower service providers to deliver and efficiently maintainpersonalized services that enhance the subscriber experience BroadbandNetwork– Goal - establish network architecture specifications to support currentand emerging services and applications– Focus - deliver access, aggregation and core specifications thatprovide inherent interoperability, quality, scalability and resiliencycapabilities from end-to-end BroadbandUser– Goal - Define unified networking standards by establishing a commonset of CPE capabilities within the business, home and mobileenvironments– Focus - Simplify the service delivery process by developing commondevices’ identification, activation, configuration and maintenancespecifications4www.broadband-forum.org
Broadband Forum NTROLFUNCTIONQuality of ExperienceTR-069 (CWMP)Identity, Accounting and PolicyOperations and Network ManagementDSL Quality ManagementTR-126 IPTVQuality of ExperienceIDENTITYTR-069 ACSBILLINGTR-176 DSLProfiles for IPTVOSSCWMPTR-069NetworkTR-144 Multi Service rvice CoreUserP2P E-FTTxContent NetworkIP/MPLSConnectedHome or OfficeTR-101, e NetworkMulti Service Architecture & Requirements5RoutedRouted art GridHome Networking ProtocolsCertification, Test and Interoperability
The Broadband Forum DocumentsThe Broadband Forum uses the following nomenclature for itsDocuments – Technical documents Technical Reports (TRs, TR-nnn) Working Texts (WTs, WT-nnn) Proposed Drafts (PDs, PD-nnn) Marketing documents (white papers and tutorials) Marketing Reports (MRs, MR-nnn) Marketing Drafts (MDs, MD-nnn)TRs and MRs are available via the BBF website http://broadband-forum.org/.WTs, PDs and MDs are works in progress and generally available to membersonly.
Technology, Market andBusiness driversWhy MPLS in transport?Requirements on MPLS
Market drivers for Packet TransportEvolution Fast growing bandwidth demand - driven by newpacket applications/services– IP Video: content downloading/streaming/sharing–––Mobile data: e.g. smart phone applicationsTriple playIP and Ethernet VPNs Network convergence and Technology refresh– Consolidate networks onto common infrastructures– Replace aging legacy networks– Flexibility to adapt to different types of traffic and topologies Cost saving advantages– Flexible data rates– Statistical Multiplexing gains, where needed– Lower operational costs8
IP and Ethernet Services Drive NetworkTransformationMultiple Legacy ine andWirelessAccessAggregationand ernetSONET/SDHDataConverged InfrastructureVoiceEfficientTransportMultiple layers, separate single function networksFewer layers, converged multi-function network“Verticalized”, stovepiped infrastructure“Horizontalized”, more homogenized infrastructureComplicates service and network transformationEnables service and network transformationMultiple single servicesMulti-service, application awareCircuit-based transportConverged packet-enabled transport9
Simplifying Data Services andPacket TransportIP/MPLSLayer 3:IPLayer 2:Ethernet, ATMLayer 1:SONET/SDHFlexibleIP/MPLS/ETHBasedServicesAlready widely deployed for IPVPN’s, L2VPNs, multi-pointservices and service aggregationMPLS PseudowiresDeployed for serviceaggregation, may be optimizedfor transportEfficientTransportMPLS (Transport)Profile of MPLS optimized fortransport enables packettransportLayer 0:DWDMIP-MPLS-Ethernet services over converged packettransport10Underlying layer Networke.g. OTN/WDM, Ethernet,
Case for MPLS in Packet TransportMPLS:IP/MPLStools andoperationsPaceffi ketciencysrtpo risticsneTra ractach Is MultiserviceMPLSMPLS-TPIP/MPLSOptical transporttools and operationsMPLS-TP bridges the gap between thetransport and packet worlds allowingtrue convergence11See RFC5921: A Framework for MPLS in Transport Networks Is carrier-grade Offers connection-orientedoperation with TrafficEngineering capability Is widely deployed in servicerouting and core Enables true convergencebetween transportand packet networks– Capex and Opex savings Can be easily profiled forpacket transport
Requirements on MPLS TransportProfileTransport-Centric Operational ModelNMS Configuration without Control Plane, or fully Dynamic Control PlaneData plane capabilities independent of Control planeProtection SwitchingTriggered by OAM (i.e., not dependent on dynamic signalling or ControlPlane liveliness)Efficient operation for both dense mesh and ring topologiesTransport-Optimized OAMFunctions such as Continuity Check/Verification, Performance Monitoring, Alarm SuppressionNot dependent on IP forwardingConnection-OrientedBidirectional Label Switched Paths (LSPs) are co-routedNo LSP merging; no Equal Cost Multipath (ECMP)Standard MPLS Data-PathMust operate using standard labels, standard push/pop/swap operations(Paraphrased from RFC5654)12
IETF/ITU-T Joint Working Team (1)Consensus on MPLS-TPIETF and ITU-T agreed to work together and bring transport requirements intothe IETF and extend IETF MPLS forwarding, OAM, survivability, networkmanagement, and control plane protocols to meet those requirementsthrough the IETF Standards Process.[RFC5317]1Definition of MPLS “Transport Profile” (MPLS-TP) protocols,based on ITU-T requirementsDerive packet transport requirementsIntegration of IETF MPLS-TP definition into transport networkrecommendationsBBF defines how to apply technologies in broadbandnetworks to allow interoperability and multi-servicessupport.1: [RFC 5317]: Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport Profile, Feb. 2009.13
MPLS-TP Technology OverviewArchitecture, Data plane,OAM, Control plane,Survivability
MPLS-TP Objectives(from RFC5654 and RFC5921) To enable MPLS to be deployed in a transportnetwork and operated in a similar manner to existingtransport technologies (SDH/SONET/OTN). To enable MPLS to support packet transportservices with a similar degree of predictability,reliability and OAM to that found in existing transportnetworksEnable connection-oriented packet transport based on widely deployed MPLSprotocols, with transport-grade performance & operation similar to existingtransport networks; ensure interoperability with IP/MPLS15
Characterising Packet Transport Independence between transport network operation and clientnetworks supported by the service Service guaranteed not to fall below agreed level regardless ofthe behaviour of other transport network clients Control/management plane isolation between networks usingservice and underlying transport network Little or no coordination required between client using serviceand underlying transport network All packets of any client network transparently transported Transport network server layer addressing and topology infohidden from client of packet transport service(Paraphrased from RFC 5921)16
What is MPLS-TP?Existing MPLS RFCsprior to RFC5654MPLSMPLS Transport Profile ECMP MP2P LSP IP forwarding/ dependency17Subset to meet transportnetwork operationalrequirements MPLS forwarding P2MP and P2P LSP MPLS/PWE3 architecture GMPLS/PWE3 controlAdditionalfunctionalitybased on TransportRequirements
Additional Functionality based on TransportRequirementsTransport-like OAM In-band OAM channels Performance monitoring for SLA verification Sub-Path monitoring with multi-level operation Alarms and AISAdditionalfunctionalityTransport-like ResilienceTransport-like Operation Dataplane / control planeindependent Operation through NMS Static provisioning Traffic Engineered Control Sub-50ms protection switching Linear protection Ring protectionAdditional features for standard IP/MPLS routers & Optical Packet Transport equipment;enhanced commonalities between service routing and optical transport18
MPLS-TP architectureNMSClient nodeProtectLSPPEPEClient nodeServer layer : MPLS-TP LSP (Static or Dynamic)Client layer : Pseudowire or any Network LayerClient Signal Foundation for Optical Transport equivalent OAM and protection-switching capabilities A centralized control/management plane with or without support of a distributed controlplane Enables differentiation of specific packets (OAM,Automatic Protection Switching (APS),etc) from user packets Primary constructs are19–––MPLS LSPs for transportation (RFC3031) for Server LayerUses PWE3 architecture (RFC3985) if client Layer of an MPLS-TP LSP uses pseudowiresClient Layer of MPLS-TP LSP can also be ‘any network layer’
MPLS-TP Architecture: Point to Point Serviceusing PWE3MPLS-TPPseudowires (PW) adapt L2 services to MPLS-TP Label Switched Path (LSP)Static or dynamically signalledEthernetATMTDMetc.PWPEPWPPELSPs take strict path in both directions“bidirectional and co-routed”Section between adjacencies at LSP layerStatic or dynamically signalledReuse of MPLS architecture to meet transport requirementsMPLS-TP LSPPW20Section : next higher orderserver layer that providesmultiplexing of MPLS-TPentities such as MPLS-TP LSPsBidirectional MPLS-TP LSPsparing relationship
MPLS-TP Architecture: Point to Point Servicefor a Network Layer ClientPoint to Point Packet transport serviceMPLS-TPIP or MPLS Label Switched Paths (LSP)Service LSP provides encapsulation and service multiplexerStatic or dynamically signalledIP,MPLS PELSPs take strict path in both directions“bidirectional and co-routed”Section between adjacencies at LSP layerStatic or dynamically signalledReuse of MPLS architecture to meet transport requirements21
Domain of MPLS-TPWhere does MPLS-TP end, and client layers begin?PW-basedserviceLabelledservicese.g. L2 private linee.g. backhaul of MPLS trafficPWPayloadS 1PW labelS 0LSP labelPW S 1LabelS 0LSP label*S 0LSP labelIP servicee.g. router interconnectIPS 1IPLSP labelS 0LSP labelClient layerS 1MPLS-TP layerLSP label S-bit follows current MPLS practice i.e., indicates non-MPLS follows Label stacks shown are the smallest number of labels possible*Can be Penultimate Hop Popped22
Enabling Enhanced OAM CapabilitiesThree possibilities for OAM supported by MPLS1.2.3.Hop-by-hop (e.g. control plane based)Out-of-band OAMIn-band OAM similar to transport model selected for MPLS-TPSectionLSPPWRFC5586 – Generic Associated Channel(GACh) generalises Pseudowire ACh to alsoenable OAM on MPLS LSPs & Sections In-band forward and return path Increases range of OAM tools Common tools atPW, LSP and Section levelReuse of MPLS PW OAM architecture to meet transport requirements23
G-ACh Label Stack for an LSPMPLS-TP uses a new alert label to identify packets on the GenericAssociated Channel (G-ACh)– Generic ACh Label (GAL)OAM PacketLabel StackLSP LabelGALACHACH TLVPayload24Generic Associated Channel Label (GAL) Identifies G-ACh packet New reserved label (Value 13) Not needed for PWs — use control wordAssociated Channel Header (ACH) Reuse PW ACH on LSPs ; same format andversion number as is today Channel Type indicates protocol (support forIETF standard and experimental protocol)ACH TLVs (optional — depends on ACh protocol) Intended for src/dst addressing, authentication, etc.G-ACh Packet Payload E.g. OAM, Data Communication (DCC),protection protocols, etc.
Maintenance Domains for MPLS-TP OAM MPLS-TP uses concept of Maintenance Domains beingmanaged/monitored Maintenance End Points (MEPs) are edges of a maintenance domain– OAM of a maintenance domain must not leak beyond correspondingMEP Maintenance Intermediate Points (MIPS) are intermediate elements thatcan be monitored Maintenance Entity Groups (MEGs) comprise all the MEPs and MIPs ona given maintenance domain for a pseudowire, LSP, or section.MEPMIPMIPMIPMEPLSR BLERLSPLERLSR AMaintenance Domains25MPLS-TP introduces transport OAM concepts to MPLSAligns management of packet and circuit based transportMEG
Targeting OAM to a MEP or MIP Verification that OAM message received at targeted MIP/MEP forfurther processing using Destination address For a MEP, GAL exposed when label popped– Ensures OAM does not leak beyond MEPACH push GALLSP LabelTTL 255 swap TTL 254 swap pop LSP label poppedGAL exposedACH processedTTL 253 For a MIP, TTL expires, force OAM packet to be processedACH push GALLSP LabelTTL 2 swap LSP label TTL expiresGAL processedTTL 1ACH processedMPLS-TP uses common MPLS mechanisms to achieve transport-oriented functions26
OAM Function: Requirements RFC 5860 Pro-activemonitoringmonitoringfeaturesfeatures Pro-active Re-active/On-demand ty)(Integrity)– –ContinuityConnectivitysupervisionsupervision– rvision(packet(packetloss)loss)– lencing)– –AlarmSingle-endedmaintenancemaintenance– –Single-ended– Fault localization– Signal quality measurement ions Pro-active Communication channelsFaultmanagementmanagement– –FaultPerformancemonitoringmonitoring– –PerformanceProtectionswitchingswitching– –Protection Throughput Ordering and error Transfer delay and jitter– Protection switching head/tail-endcoordination– Network control and management– Remote node management– Service management IETF approach is to reuse or extend existing tools as far as reasonable or develop newtools when needed Note: the tools meeting the requirements above are still under development in the IETF,and may be discussed in a next version of the tutorial.27
Management and Control for MPLS-TP 28STATICDYNAMIC“MPLS-TP transport paths may be established using static or dynamic configuration.It should be noted that the MPLS-TP network and its transport paths canalways be operated fully in the absence of any control plane.”1The PW control plane is based onthe existing PW control plane (LDP),see [RFC4447].The LSP control plane is based onGeneralized MPLS (GMPLS), see[RFC3945].Plug-and-play SignallingCommunication Channel (SCC) overLSPs or sections for signaling inabsence of native IP support inserver layer Done via managementplane. “Static provisioning MUSTNOT depend on thepresence of any elementof a control plane.”1Plug-and-playManagementCommunication Channel(MCC) over G-ACh cancarry NMS traffic [1]: RFC5654
Data Communication Network using GenericAssociated Channel (G-ACh )Carries Management Communication Channel (MCC) or SignallingCommunication Channel (SCC)NMSNMSSectionLSPLSR ALSR BDCN on LSPLSPGALACHProtocol ID29DCN MessageDCN on SectionSCC or MCCGALACHProtocol IDDCN MessageSCC or MCC
GMPLS for MPLS-TP orforbidirectionalbidirectionalpathspathsBeing extendedto configureMPLS-TP tocols30RSVP-TE msgAChallows theseparation of dataplane and controlplane: out-of bandsignaling in-bandsignalingGALLSP label
LDP for MPLS-TP PW Label Distribution Protocol (LDP) is a protocolLabelDistributionProtocol(LDP)is athroughprotocola networkdefininghow gha networkby mapping network-layer routing ork-layerlayer switchedpaths.information directlyto data-link layer switched paths. LDP associates a Forwarding Equivalence ClassLDPassociatesa ForwardingEquivalence Class(FEC)with eachLSP it creates.(FEC) with each LSP it creates.LDP Universally deployed today for PW Lightweight protocol allows for service scalability Signals binding of PW label to FEC Use enhanced pseudowire addressing withMPLS-TP– Global Identifier Node Prefix AttachmentCircuit Identifier– Allows PW routing scalability with aggregationand domain partitioning31–––––Signaling Pseudowire (PW) StatusPW Status Negotiation ProceduresSetup of PWsEncapsulation negotiationSupports bidirectional, co-routedPWs
MPLS-TP Survivability Objectives Survivability is the network’s ability to restore traffic and recoverfrom “failed” or “degraded” entities (links or nodes). It is critical forthe delivery of reliable services in transport networks. MPLS-TP to support a comprehensive set of recovery mechanismsat different nested levels (i.e., the end-to-end level of a transportpath, a path segment, and an MPLS-TP link) including:– Protection switching mechanisms that are appropriate for transportnetworks, capable of providing the recovery time required to maintaincustomer SLAs, by pre-provisioned active and backup paths.– Network restoration mechanisms controlled by a distributed controlplane or a management plane, allowing to establish a backup pathwhen the failure occurs.32
MPLS-TP SurvivabilityFunctional ElementsRecovery Elements:Control Elements:Support for various recovery triggers,such as: In-band OAM defect or degradationindication Network failure detection Administrator-initiated commands Control plane signaling Etc.Recovery Grades:Support for multiple grades ofrecovery: Dedicated recovery Shared protection Restoration and repair Etc.33Support for various recoverydomains: MPLS-TP link recovery Segment recovery End-to-end path : Support for generic mechanismsapplicable to any topology Support for optimizedmechanisms for specifictopologies (e.g. ring)
MPLS-TP SurvivabilityFunctional ElementsRecovery Elements:Control Elements:Support for various recovery triggers,such as: In-band OAM defect or degradationindication Network failure detectionDifferent combinationsof the Administrator-initiated commandsfunctional elementscanplaneprovide Controlsignaling Etc.different grades ofrecovery.Different recovery grades may beRecovery Grades:used concurrently by a singleSupports for multiple gradesMPLS-TP transport path forof recovery:additional resiliency. Dedicated recovery Shared protection Restoration and repair Etc.34Support for various recoverydomains: MPLS-TP link recovery Segment recovery End-to-end path : Support for generic mechanismsapplicable to any topology Support for optimizedmechanisms for specifictopologies (e.g. ring)
MPLS-TP Survivability MechanismsMultiserviceAccessNMS orASON/GMPLSRingProt.Ethernet,TDM, ATM,Section ProtectionProtection (data plane) 50ms with protection coordinationprotocol triggered by data-plane OAM 1 1, 1:1, 1:N, without extra traffic Unidirectional, Bidirectional Section, LSP, PW Subnetwork Connection (SNCP) Mesh and Ring35PW Restoration (ctrl. and mgmt. plane) GMPLS based restoration for LSP in synergywith other transport network technologies(SONET/SDH, OTN/WDM) PW redundancy LSP fast reroute GMPLS segment and end-to-end protection Pre-planned LSP rerouting restoration Any topology
MPLS-TP Recovery Mechanisms All GMPLS and MPLS mechanisms are applicable in MPLS-TP (forany topology):– MPLS LSP end-to-end protection– PW redundancy (support for dual-homed AC failure, S-PE failure in MSPW, etc.)– GMPLS segment recovery– GMPLS end-to-end recovery– MPLS LSP Fast Reroute (FRR)– Restoration (including pre-planned LSP restoration) The provisioning method should be decoupled from the data planecapability of the above mechanisms.– The management plane is being extended enable the provisioning of theprotection entities and functions.– A data-plane-based protocol (in-band) is being defined to coordinate the protectionstate between the edges of a protection domain, and thus enable bi-directionalprotection switching.36
Data plane: Linear 1 1 protectionPermanent BridgeTransport path: PW, SPME, LSP, TCPBSelector BridgeSBWorking pathRecovery pathLSR LSRPermanent Bridge sends traffic on both working and recovery pathsSelector bridge selects pathApplicable to p2p and p2mp, uni and bi-directionalProtection coordination protocol for bi-directional, to synchronize bothendsSPME: Sub-Path Maintenance EntityTC: Tandem ConnectionPermanent Bridge37Selector bridge
Data plane: Linear 1:1 protectionTransport path: PW, SPME, LSP, TCSelector BridgeSBSelector BridgeSBWorking pathRecovery pathLSRProtection Coordination ProtocolLSR Protection coordination protocol (PCP) for synchronization betweenselector bridges PCP messages are always sent over the recovery path over the G-ACh Upon failure, three control packets sent at 3.3 ms intervals to triggerswitchover in sub-50ms Supports revertive and non-revertive, uni- and bi-directional operation38
Control Plane Based Survivability MPLS-TP uses existing GMPLS and PWcontrol planes Inherits existing control plane basedsurvivability mechanisms applicable to uni/bidirectional paths LSPs: GMPLS recovery mechanisms PWs: PW Redundancy– Correct forwarding if dual-homed AC fails-over– Protection if S-PE fails on MS-PW39
GMPLS Recovery GMPLS defines recovery signaling for– P2P LSPs in [RFC4872], RSVP-TE extensions in supportfor end-to-end GMPLS recovery– and [RFC4873] for GMPLS segment recovery. GMPLS segment recovery provides a superset ofthe function in end-to-end recovery1.– All five of the protection types defined for recovery areapplicable to MPLS-TP. 1 1 bidirectional protection for P2P LSPs 1 1 unidirectional protection for P2MP LSPs 1:n (including 1:1) protection with or without extra traffic Rerouting without extra traffic (sometimes known as softrerouting), including shared mesh restoration Full LSP rerouting1Useof Notify messages to trigger recovery is not required in MPLS-TP as this isexpected to be supported via OAM. However, it's use is not precluded.The restoration priority and The preemption priority are supported40
Regarding Pseudowire RedundancyAttachment Circuit (AC)redundancy protocol drivesforwarding state of PWs/PEsActive/standby state ofLAG/APS sub-groupsreflected in PW statusactive CEPW statusMPLS-TP networkForwarding directiondetermined by PW state CEstandbyAC redundancy:MultiChassis – Automatic Protection Switching(MC-APS)MultiChassis – Link Aggregation (MC-LAG)MPLS-TP component of end-to-end protection against PE/AC failures PE configured with multiple pseudowires per service with multiple end-points Local precedence indicates primary PW for forwarding if multiple PWs are operationally UP PW status exchanged end-to-end to notify PEs of operational state of both PWs &ports/attachment circuits (PW Status Notification). Leverages Associated Channel or T-LDP41
Ring protection: Background Physical rings are prevalent in existing carrier transport networks. P2mp paths are easier to implement in a ring topology. Ongoing work to optimize the protection operation of MPLS-TP inring topologies. Various criteria for optimization are considered inring topologies, such as:– Simplification of ring operation in terms of the number of OAM maintenanceentities that are needed to trigger recovery actions, the number of recoveryelements, the number of management-plane transactions during maintenanceoperations– Optimization of resource consumption around the ring, such as the number oflabels needed for the protection paths that traverse the network, the totalbandwidth required in the ring to ensure path protection42
Variants of Ring ProtectionTypical optionsSteeringWrappingCBACBADEFDEF Protection performed locally by nodes that detect thefault Protection performed by the ring ingress/egress nodesfor the LSPs affected by the fault Does not require knowledge of the path followed by anLSP at the ring ingress/egress nodes Requires knowledge of the path followed by an LSP atthe ring ingress/egress nodes Wrapping adds latency during protection switchingconditions Steering minimizes latency and bandwidth usage duringprotection switching conditions43
QoS for MPLS-TP MPLS-TP data plane is a subset of the existing MPLSdata plane: therefore the QoS capabilities are the same– MPLS based traffic management, e.g., policing, shaping, isapplicable to MPLS-TP for traffic guarantees The Traffic Class bits (aka EXP bits) are used todetermine the QoS for a packet QoS and SLA conformance can be measured using ondemand or pro-active performance monitoring tools The Traffic Class bits to be used per LSP areestablished via– provisioning or– dynamic signaling (GMPLS)44
IETF MPLS-TP Related RFCs Published45RFC 5317JWT Report on MPLS Architectural Considerations for a TransportProfile02/2009RFC 5654MPLS-TP Requirements09/2009RFC 5586MPLS Generic Associated Channel06/2009RFC 5462Multiprotocol Label Switching (MPLS) Label Stack Entry:"EXP" Field Renamed to "Traffic Class" Field02/2009RFC 5718An In-Band Data Communication Network For the MPLSTransport Profile01/2010RFC 5860MPLS-TP OAM Requirements05/2010RFC 5921A Framework for MPLS in Transport Networks07/2010RFC 5960MPLS Transport Profile Data Plane Architecture08/2010For more information, org/wg/ccamp/
IETF MPLS-TP Working Group Documents (1)The following WG documents are work in progress MPLS-TP Identifiersdraft-ietf-mpls-tp-identifiers MPLS-TP Linear Protectiondraft-ietf-mpls-tp-linear-protection Multiprotocol Label Switching Transport Profile Survivability Framework (RFC queue)draft-ietf-mpls-tp-survive-fwk MPLS-TP Control Plane rk MPLS-TP Network Management Framework (RFC queue)draft-ietf-mpls-tp-nm-framework MPLS TP Network Management Requirements (RFC queue)draft-ietf-mpls-tp-nm-req MPLS-TP OAM Analysisdraft-ietf-mpls-tp-oam-analysis MPLS-TP OAM Frameworkdraft-ietf-mpls-tp-oam-framework A Thesaurus for the Terminology used in Multiprotocol Label Switching TransportProfile (MPLS-TP) drafts/RFCs and ITU-T's Transport Network or more information, org/wg/ccamp/
IETF MPLS-TP Working Group Documents (2)The following OAM WG documents are work in progress Proactive Connection Verification, Continuity Check and Remote Defect indication forMPLS Transport Profiledraft-ietf-mpls-tp-cc-cv-rdi MPLS on-demand Connectivity Verification, Route Tracing and Adjacency Verificationdraft-ietf-mpls-tp-on-demand-cv MPLS Fault Management OAMdraft-ietf-mpls-tp-fault LSP-Ping and BFD encapsulation over ACHdraft-ietf-mpls-tp-lsp-ping-bfd-procedures PW Static PW statusdraft-ietf-pwe3-static-pw-status Packet Loss and Delay Measurement for the MPLS Transport Profiledraft-ietf-mpls-tp-loss-delayFor more information, org/wg/ccamp/47
MPLS-TP ITU-T Standards OverviewWork in progress to align with MPLS-TPArchitecture 07/07Interface, hanismsFor more information, ectionprotection02/07Management andControl Plane Arch.48Rec under Arch.09/10approved ted RecRec inprogressRec CNDCN09/10Rec not planned yet
MPLS-TP Use-Cases and BBFApplicability
Use cases Multiple services over MPLS-TP––––EthernetATMTDMIP and/or MPLS (e.g. Router interconnect) Interoperability between MPLS-TP andIP/MPLS MPLS-TP as a client of IP/MPLS (using anIP/MPLS core to tunnel MPLS-TP LSPs)50
Multiple services as a client of MPLS (-TP*)Ethernet(-TP)MPLS SDH/OTNFiber/ wavePDHFiber/CopperMPLSPEMPLS(-TP)TDMPDHPDHCopper / iber/ er51ClientMPLS(-TP)ATMClientClien
transport technologies (SDH/SONET/OTN). ðlTo enable MPLS to support packet transport services with a similar degree of predictability, reliability and OAM to that found in existing transport networks 15 Enable connection-oriented packet transport based on widely deployed MPLS protocols, with transport-grade performance & operation similar to .
slide series thatdescribe the Multiprotocol Label Switching (MPLS) concept . Layer-3 VPNs Layer-2 VPNs MPLS QoS MPLS TE MPLS OAM/MIBs End-to-end Services MPLS Network Services . §MPLS label forwarding and signaling mechanisms Network Infrastructure MPLS Signaling and Forwarding Layer-3 VPNs Layer-2 VPNs
VPN Customer Connectivity—MPLS/VPN Design Choices Summary 11. Advanced MPLS/VPN Topologies Intranet and Extranet Integration Central Services Topology MPLS/VPN Hub-and-spoke Topology Summary 12. Advanced MPLS/VPN Topics MPLS/VPN: Scaling the Solution Routing Convergence Within an MPLS-enabled VPN Network Advertisement of Routes Across the .
MPLS-based VPN services: L3 MPLS VPN and L2 MPLS VPN. MPLS L2VPN has two modes: Virtual Private LAN Service (VPLS) and Virtual Leased Line (VLL). VLL applies to point-to-point networking scenarios, while VPLS supports point-to-multipoint and multipoint-to-multipoint networking. From users' point of view, the whole MPLS network is
QoS Testing In a Live Private IP MPLS Network with CoS Implemented ComSIS Vol. 7, No. 3, June 2010 531 Task Force) Differentiated Service (DiffServ) standard that supports much wider Class of Services (CoS) than MPLS-TE [3]. MPLS DiffServ-TE combine advantages of both MPLS extensions (DiffServ and TE) to achieve .
MPLS PW OAM mechanisms are described next, and a brief look at existing layer 2 OAM mechanisms is provided. The article goes on to describe the relationship between end-to-end fault detection and the segment-based OAM mechanisms. MPLS PW An MPLS PW is the mechanism used to carry layer 2 traffic over MPLS. It is a point-to-point
MPLS OAM Overview MPLS OAM technology provides the MPLS network with a defect-detection tool and a defect-rectification mechanism that are independent of any Layer 3 or Layer 2 protocols. The check function of the CR-LSP forwarding plane is implemented through MPLS OAM and protection switching.
Usetheping sr-mpls fec fec-type igp isis CLIcommandtoexecuteanIS-ISSRpingandtheping sr-mpls fec fec-type bgp CLIcommandtoexecuteaBGPping. switch# ping sr-mpls 11.1.1.3/32 fec-type igp isis Sending 5, 100-byte MPLS Echos to IGP Prefix SID(IS-IS) FEC 11.1.1.3/32, timeout
SDN in Access network, SDN in Optical Layer & MPLS on top Working in orchestration Depends on -Control Plane, SDN Controllers, APIs Communication through Open Interfaces Access SDN SDN to MPLS Control Plane API Function Edge Gate way Programmable MAC/VLAN/PBB & MPLS to MPLS Mapping Ethernet CPRI/dRoF
