What is Covered in the Draft? 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 IETF 79 - Beijing
Application Scenario Example1 backbone MAN AS x MAN AS y Province Network AS9808 O&M server Backbone router Province router In order to deploy MPLS VPN with entire network, there is a strong demand to support inter-AS connection and E2E O&M ASO&M backbone network Public AS: 9808 headquarte r province network Private AS: x province Headquarter O&M Province O&M
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 cant be achieved by them We hope to use single AS to solve E2E O&M problem based on the original multiple ASs network
Inter-AS VPN E2E O&M Solutions AS #1 AS #2 AS #3 AS #2 AS #1 A B AS #3 AS #2 AS #4 AS #1 Virtual Router Solution ASolution BSolution C Goal of the Solutions: Transfer inter-AS to Single AS Inter-ASSingle AS A B Expand backbone AS with new routers Expand backbone AS with virtual routers Build new AS with multiple-topology
CMnet backbone Province A Province B Router with default topology Inter-AS VPN E2E O&M Router with VPN topology CMnet backbone AS #1 AS #2 AS #3 AS #2 AS #4 AS #1 Province A Province B O&M server Headquarter 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
Analysis Most of Existing network routers cant support the virtual router by software update. Its also a high cost solution because of substituting the hardware and software Multiple-Topology Virtual Router New Construction is simple and reliable. But the high cost and the inefficient use of existing network resources are not preferable New Construction Considering cost and scalability, utilization and evolution of the existing network, Multiple-Topology may be the preferable solution 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
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 dont share the common links and nodes.
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