html5-img
1 / 5

MPLS-TP Pseudowire Configuration using OpenFlow 1.3

MPLS-TP Pseudowire Configuration using OpenFlow 1.3. draft-medved-pwe3-of-config-02. J.Medved A.McLachlan D.Meyer. Draft Summary. This draft is aimed 2 main area: Provisioning of Pseudowires in the MPLS-TP environment. (We are not covering the Transport LSP at this point)

mirit
Download Presentation

MPLS-TP Pseudowire Configuration using OpenFlow 1.3

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MPLS-TP Pseudowire Configuration using OpenFlow 1.3 draft-medved-pwe3-of-config-02 J.Medved A.McLachlan D.Meyer

  2. Draft Summary • This draft is aimed 2 main area: • Provisioning of Pseudowires in the MPLS-TP environment. (We are not covering the Transport LSP at this point) • OAM setup over the data path for the Pseudowireswe are configuring.

  3. Method Summary • A PW is to be configured between an ingress and an egress attachment circuit. • Using an external OpenFlow Controller we provision the PW between the 2 end points. • Using OpenFlow rules we direct the desired packets into this PW. • Also using Open Flow rules we direct the OAM packets into the OAM Engine, or return them if they require, echo-mode bfd for example. • Redundancy uses the OpenFlow Group port as a fast-fail mechanism.

  4. Thoughts behind it • Why have we considered OpenFlow for this? • We wanted to enhance the programmatic operations of an MPLS-TP element. • OpenFlow can work well in this environment, due to its ability to program switching elements. • As it is an Open Standard it seems to fit well as part of an SDN approach for configuring PWs in the MPLS-TP environments.

  5. What issues does this draft address? • Some carriers have expressed a desire to have an open non-vendor specific provisioning. Neither CLI driven nor a vendor related provisioning platform. • OAM was a key requirement: • As OpenFlow 1.3 does not include OAM, we wanted to show how we can use OF rules to direct OAM packets to an independent OAM engine.

More Related