Why openflow sdn can succeed where gmpls failed
This presentation is the property of its rightful owner.
Sponsored Links
1 / 11

Why OpenFlow /SDN Can Succeed Where GMPLS Failed PowerPoint PPT Presentation


  • 107 Views
  • Uploaded on
  • Presentation posted in: General

Why OpenFlow /SDN Can Succeed Where GMPLS Failed. Saurav Das , Guru Parulkar , Nick McKeown. MPLS. a mechanism for forwarding packets for any network protocol. d evelopment: originally developed in the late 1990s to provide faster packet forwarding for IP routers

Download Presentation

Why OpenFlow /SDN Can Succeed Where GMPLS Failed

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


Why openflow sdn can succeed where gmpls failed

Why OpenFlow/SDN Can Succeed Where GMPLS Failed

Saurav Das , Guru Parulkar ,

Nick McKeown


Why openflow sdn can succeed where gmpls failed

MPLS

  • a mechanism for forwarding packets for any network protocol.

  • development:

    • originally developed in the late 1990s to provide faster packet forwarding for IP routers

    • the de-facto standard for many carrier and service provider networks

    • deployment scenarios continue to grow


Why openflow sdn can succeed where gmpls failed

MPLS

  • illustration:


Gmpls

GMPLS

  • conceptually similar to MPLS

  • difference from MPLS:

    • some physical property of the received data stream is used to deduce which LSP it belongs to

  • the most commonly used schemes

    • Timeslot

      -on a Time Division Multiplexed (TDM) link

    • Wavelength

      -on a Wavelength Division Multiplexed (WDM) link

    • fiber or port


Sdn based unified control architecture

SDN based Unified Control Architecture


Why openflow sdn can succeed where gmpls failed

  • The common-map abstraction:

    • provides full visibility into both packet and circuit switched networks

    • abstracting away the complexity of state-dissemination from applications

  • The common-flow abstraction :

    • flow-tables that take the form of lookup-tables in packet switches and cross-connect tables in circuit switches.


Gmpls vs sdn

GMPLS vs SDN

  • Shortcomings of GMPLS and Advantages of the SDN

    • Control plane complexity

    • Lack of the common map-abstraction

    • Lack of a gradual adoption path


Control plane complexity

Control plane complexity

  • GMPLS:

    • The amount of extensions that have gone into the protocols

    • RSVP:

      • IntServ+ MPLS-TE + GMPLS +UNI interface

  • SDN:

    • Use switch-API,network-OS replace :

      • protocols like OSPF,RSVP

      • interface like the uni

      • vendor proprietary islands and interface


Lack of the common map abstraction

Lack of the common map-abstraction

  • As a result

    • a) services available to IP network are limited to the exact service-level definitions defined

    • b) the distributed implementation of network-functions across packets and circuits require lots of glue-code, and patchwork to existing protocol.


Lack of a gradual adoption path

Lack of a gradual adoption path


R eference

Reference

  • www.openflow.org/wk/images/4/40/Abstract.pdf‎

  • SDN Based Unified Control Architecture Saurav Das, Guru Parulkar and Nick McKeown

  • http://network-technologies.metaswitch.com/mpls/what-is-mpls-and-gmpls.aspx


  • Login