1 / 9

IETF 79 - Beijing

MPLS Multiple Topology Applicability and Requirements draft-li-mpls-mt-applicability-requirement-00 . IETF 79 - Beijing. What is Covered in the Draft?. IETF 79 - Beijing. There are a few scenarios described in this draft: Simplified Data-plane ； Automation of inter-layer interworking ；

nardo
Download Presentation

IETF 79 - Beijing

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. MPLS Multiple Topology Applicability and Requirementsdraft-li-mpls-mt-applicability-requirement-00 IETF 79 - Beijing

  2. What is Covered in the Draft? IETF 79 - Beijing • There are a few scenarios described in this draft: • Simplified Data-plane； • Automation of inter-layer interworking； • Migration without service disruption； • Protection using MT； • Service Separation； • Load Balancing • Two categories of requirements are presented in the draft: • Service Requirements • Provider requirements

  3. Application Scenario Example1 Headquarter O&M backbone AS9808 AS y AS x Province O&M Province Network MAN MAN MAN MAN In order to deploy MPLS VPN with entire network, there is a strong demand to support inter-AS connection and E2E O&M Backbone router O&M server Province router

  4. Solution for Inter-AS MPLS VPN Three mature mechanisms have been used to Inter-AS MPLS VPN Optioin A Option B Option C • Option A/B/C can build inter-AS connection of MPLS VPN, but E2E O&M can’t be achieved by them • We hope to use single AS to solve E2E O&M problem based on the original multiple ASs network

  5. Inter-AS VPN E2E O&M Solutions Goal of the Solutions: Transfer inter-AS to Single AS Inter-AS Single AS Solution A Solution B Solution C • Virtual Router Expand backbone AS with virtual routers Build new AS with multiple-topology Expand backbone AS with new routers AS #1 AS #1 AS #1 B B AS #4 A A AS #3 AS #3 AS #2 AS #3 AS #2 AS #2

  6. Inter-AS VPN E2E O&M • Build New AS for MPLS VPN Using MPLS Multiple Topology • Use multiple-topology to create a new AS which merges virtual topologies from backbone and province ASs together • Backbone can achieve E2E O&M within the new AS CMnet backbone Headquarter O&M CMnet backbone Headquarter O&M AS #1 AS #1 AS #4 AS #3 AS #3 AS #2 Province A AS #2 Province A Province B Province B Router with VPNtopology O&M server Router with default topology

  7. Analysis Considering cost and scalability, utilization and evolution of the existing network, Multiple-Topology may be the preferable solution Multiple-Topology Virtual Router New Construction New Construction is simple and reliable. But the highcost and the inefficient use of existing network resources are not preferable Most of Existing network routers can’t support the virtual router by software update. It’s also a high cost solution because of substituting the hardware and software Multiple-Topology is an easy way to deploy by software update. With MT existing network resources could be efficiently used and the network can be of resilent expansion. But the standard is not mature enough

  8. Application Scenario Example 2: End-to-End P2MP backup LSP The primary P2MP LSP set up in the red topology is backed up by the secondary P2MP LSP setup in the blue topology, where the red topology and blue topology don’t share the common links and nodes.

  9. Next Steps • We would like to identify more application scenarios and identify more detailed requirements in the next version of the draft. • We would like to get more feed back from the working group for this draft. IETF 79 - Beijing

More Related