3. 2012 OIF Interoperability (ASON/GMPLS Control Plane)
Accomplishments
GMPLS for OTN
E-NNI 2.0 / UNI 2.0
Multi-layer
Multi-vendor
Multi-carrier
Full details: http://www.oiforum.com/public/OIF_at_OFC2012.html
4. A More Detailed (Realistic) View
Domain could mean
vendor, carrier, network, and/or layer
homogeneity
CP requests likely to be
E-NNI shows abstracted topologies
NMS driven, not UNI
for interdomain networking
OSS/NMS
Domain A Domain B Domain C
Client Client
UNI E-NNI E-NNI
I-NNI I-NNI I-NNI
I-NNI CP can not see
outside its domain
UNI User Network Interface
I-NNI Internal Network-Network Interface
E-NNI External Network-Network Interface
CP Control Plane
5. Interdomain Networking & PCE
Sometimes an “abstracted topology” is not enough
Abstractions may not provide optimal e2e path
Topology sharing concerns
Enter: Path Computation
Element (PCE)
Provides optimal and secure
interdomain networking
Fully customizable
Improved price/performance ratio
Simplified operations
Ideal for complex routing decisions
(i.e. WDM)
IETF standard
PCE also provides a path to the cloud & SDN!
6. PCE: An Evolutionary Approach to SDN [for Telcos]
PCE separates control and data planes
In a way telcos can tolerate
PCE opens control of the network
Enables customization of path set up
PCE simplifies operations
Modifications/upgrades to a centralized COTS server
Not a network element
PCE improves pri
ce/performance ratio
Add processing power to a COTS server
Add PCEs, hierarchical PCEs as needed
All the same attributes which are driving SDN momentum.
