1

Joe Whitehouse

OTN Control Plane, PCE, & Software

Defined Networking

2Control Plane Demand

OTN Deployments = Control Plane Deployments

32012 OIF Interoperability (ASON/GMPLS Control Plane)

AccomplishmentsGMPLS for OTNE-NNI 2.0 / UNI 2.0Multi-layerMulti-vendorMulti-carrier

Full details: http://www.oiforum.com/public/OIF_at_OFC2012.html

4A More Detailed (Realistic) View

Domain C

UNI E-NNI

Domain A Domain B

E-NNI

Client Client

I-NNI I-NNI I-NNI

UNI User Network InterfaceI-NNI Internal Network-Network InterfaceE-NNI External Network-Network InterfaceCP Control Plane

I-NNI CP can not see outside its domain

E-NNI shows abstracted topologies for interdomain networking

OSS/NMS

CP requests likely to be NMS driven, not UNI

Domain could mean vendor, carrier, network, and/or layer homogeneity

5Interdomain Networking & PCE

Sometimes an “abstracted topology” is not enoughAbstractions may not provide optimal e2e pathTopology sharing concerns

Enter: Path Computation Element (PCE)

Provides optimal and secure interdomain networkingFully customizableImproved price/performance ratioSimplified operationsIdeal for complex routing decisions (i.e. WDM)IETF standard

PCE also provides a path to the cloud & SDN!

6PCE: An Evolutionary Approach to SDN [for Telcos]

PCE separates control and data planesIn a way telcos can tolerate

PCE opens control of the networkEnables customization of path set up

PCE simplifies operationsModifications/upgrades to a centralized COTS server

Not a network element

PCE improves pri

ce/performance ratioAdd processing power to a COTS serverAdd PCEs, hierarchical PCEs as needed

All the same attributes which are driving SDN momentum.

7

Joe.whitehouse@metaswitch.com

Thank You

http://network-technologies.metaswitch.com/