1 / 9

Unified MPLS Framework draft- martinotti -mpls-unified-mpls- fwk

Explore interworking options between IP/MPLS and MPLS-TP architectures to maximize OAM benefits, ensuring a unified framework. Deep dive into interworking possibilities and compatibility between different MPLS packages and protocols.

chism
Download Presentation

Unified MPLS Framework draft- martinotti -mpls-unified-mpls- fwk

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unified MPLS Frameworkdraft-martinotti-mpls-unified-mpls-fwk Loa Andersson Riccardo Martinotti

  2. “The problem” • Interworking MPLS • Maximize the benefits of the OAM work done in the MPLS-TP project • Keep the MPLS architecture “unified”

  3. IP/MPLS and Interworking • We started to look at how we can interwork IP/MPLS and MPLS-TP • This was the scope of the earlier draft-martinotti • Answers were not right • IP/MPLS is not the right context for interworking • Deep dive • All the standard track RFCs • What works with what? • Packages and Aggregate Packages • Interworking options

  4. MPLS Packages Package 1 Package 2 Package 3 Package 4 LDP OSPF LDP IS-IS RSVP-TE ISIS-TE RSVP-TE OSPF-TE

  5. Aggregate Packages Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb

  6. Aggregate Packages Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Package Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb Aaaa bbbb

  7. Aggregate Packages MPLS-TE Traffic Engineered MPLS MPLS TD Topology Driven MPLS MPLS-TP MPLS Transport Profile

  8. In Scope and assumptions • It will be easier to set up an LSPs that crosses the between two MPLS packages within an Aggregate Package, than if an Aggregate Package border is traversed. • Look at the applicability for MPLS-TP OAM for LSPs within MPLS packages, between MPLS Packages and between Aggregate Packages • One architecture

  9. Next steps • More comments … • More contributors / industry intiative • … it also time start the process to make this a working document • BTW, Riccardo and I do not know of any IPRs that is relevant for this draft

More Related