3MotivationMPLS is a mature technology, deployed for over 10 years in backbone networks world widestable, well known and flexibleMPLS already moved from typical backbone deployments towards aggregation networks, e.g. many metro networks are based on MPLS technology delivering Ethernet based servicesNevertheless, even using the same technology very often the different part of the network are not part of a common MPLS domainSome SP wish to integrate Access, Aggregation and Backbone into a single MPLS domainBuilding 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 setThis should be done by this draft. This draft does not change any existing protocol.
4Use CasesDescription of general use cases, which has to be realized by end to end MPLS platform.Use Case #1Redundancy in the accessRedundancy in the accessPW for Business P2P ServiceCore NetworkAGNABRAGNANANPW towards SC for RCService Creation for Residential Customers
5Architecture/ Deployment Scenarios Section „Architecture” should describe the general topics. Section DS describes special network implementations. As Albert Einstein, we have started with the special case.Labeled BGPstaticRoutingstatic defaultNH selfNH unchangedSeamless MPLSAGSABRABRISIS Level 1AGSDSLAMDSLAMISIS Level 1ISIS Level 2Label DistributionLabeled BGPLDP Downstream on DemandLDP DoDLDP1.00010.000
6Moving ForwardAsk for feedback and discussion on the MPLS Mailing ListUpdate (-02) planned for IETF78OpenMulticast for Seamless MPLSSecurity ConsiderationsArchitecture section…
7Thanks for the Contribution of Clarence Filsfils (Cisco)Kireeti Kompella (Juniper)Wim Henderickx (Alcatel)