Motivation MPLS is a mature technology, deployed for over 10 years in backbone networks world wide –stable, well known and flexible MPLS already moved from typical backbone deployments towards aggregation networks, e.g. many metro networks are based on MPLS technology delivering Ethernet based services –Nevertheless, even using the same technology very often the different part of the network are not part of a common MPLS domain Some SP wish to integrate Access, Aggregation and Backbone into a single MPLS domain Building a very huge seamless MPLS platform, needs to make some important design decisions in using the well established protocols. –Multiple options are possible. It would be easier for the whole industry if we collaborate to select a single preferred solution, to be implemented, scaled for and deployed. –Especially for access nodes which may not (want to) implement all the possible capabilities of the whole MPLS feature set This should be done by this draft. This draft does not change any existing protocol.
Use Cases PW for Business P2P Service Core Network Use Case #1 Redundancy in the access AN Service Creation for Residential Customers AN PW towards SC for RC AGN ABR Description of general use cases, which has to be realized by end to end MPLS platform.
Architecture/ Deployment Scenarios AGS DSLAM ABR AGS DSLAM ISIS Level 2 ISIS Level 1 static static default NH self NH unchanged LDP LDP Downstream on Demand LDP DoD Labeled BGP Routing Label Distribution Seamless MPLS 1.000 10.000100.000 Section Architecture should describe the general topics. Section DS describes special network implementations. As Albert Einstein, we have started with the special case.
Moving Forward Ask for feedback and discussion on the MPLS Mailing List –Update (-02) planned for IETF78 Open –Multicast for Seamless MPLS –Security Considerations –Architecture section –…
Thanks for the Contribution of Clarence Filsfils (Cisco) Kireeti Kompella (Juniper) Wim Henderickx (Alcatel)