seamless mpls draft leymann mpls seamless mpls 01 txt n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Seamless MPLS draft-leymann-mpls-seamless-mpls-01.txt PowerPoint Presentation
Download Presentation
Seamless MPLS draft-leymann-mpls-seamless-mpls-01.txt

Loading in 2 Seconds...

play fullscreen
1 / 7

Seamless MPLS draft-leymann-mpls-seamless-mpls-01.txt - PowerPoint PPT Presentation


  • 210 Views
  • Uploaded on

Seamless MPLS draft-leymann-mpls-seamless-mpls-01.txt. Nicolai Leymann , Thomas Beckhaus (Deutsche Telekom) Bruno Decraene (France Telecom) Dirk Steinberg (Steinberg Consulting) 77th IETF, Anaheim, California. Structure (and Agenda) draft-leymann-seamless-mpls-01. Motivation Use Cases

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Seamless MPLS draft-leymann-mpls-seamless-mpls-01.txt' - john


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
seamless mpls draft leymann mpls seamless mpls 01 txt

Seamless MPLSdraft-leymann-mpls-seamless-mpls-01.txt

Nicolai Leymann, Thomas Beckhaus (Deutsche Telekom)

Bruno Decraene (France Telecom)

Dirk Steinberg (Steinberg Consulting)

77th IETF, Anaheim, California

structure and agenda draft leymann seamless mpls 01
Structure (and Agenda)draft-leymann-seamless-mpls-01
  • Motivation
  • Use Cases
  • Architecture
  • Deployment Scenarios
  • Moving Forward
motivation
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

Redundancy in the access

Redundancy in the access

PW for Business P2P Service

AN

AN

AGN

ABR

ABR

AGN

CoreNetwork

PW towards SC for RC

PW towards SC for RC

Service Creation for Residential Customers

Service Creation for Residential Customers

Use Cases

Description of general use cases, which has to be realized by end to end MPLS platform.

Use Case #1

architecture deployment scenarios
Architecture/ 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 BGP

static

Routing

static default

NH self

NH unchanged

Seamless MPLS

AGS

ABR

ABR

ISIS Level 1

AGS

DSLAM

DSLAM

ISIS Level 1

ISIS Level 2

Label Distribution

Labeled BGP

LDPDownstream on Demand

LDP DoD

LDP

1.000

10.000

100.000

moving forward
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
Thanks for the Contribution of
  • Clarence Filsfils (Cisco)
  • Kireeti Kompella (Juniper)
  • Wim Henderickx (Alcatel)