Optical Control Plane Standardization OIF IETF ITU

1
Optical Control Plane Standardization - OIF /
IETF / ITU

• Lyndon Ong, Director, Network Control
  Architecture
• Ciena Corporation
• Lyong_at_ciena.com

2
Agenda

• What is the OIF NNI?
• Where does it fit within GMPLS, ASON, etc.?
• What do we learn from the NNI Demo?
• Where does it go from here?

3
NNI Goals

• Assumptions
• Carriers networks have multiple domains
• Multi-vendor or multi-technology networks
• Administrative/management controls
• Different choices for intra-domain protocol
• An Inter-Domain interface is needed the NNI
• Goals of the NNI Demo
• Demonstrate NNI Concepts
• Domain Interoperability
• Domain abstraction/isolation
• Hierarchy
• Implement pre-standard NNI protocols

4
NNI Demo Network
Routing Controller
NNI
UNI
Abstracted Topology
Actual Topology
5
Relationship with GMPLS

• GMPLS Generalized MultiProtocol Label Switching
• A set of IETF standards for Sub-IP Control Plane
• Signaling RSVP-TE and CR-LDP
• Routing OSPF-TE and ISIS
• Link Management
• Current limitations
• Restricted to single routing area limited scope
• Limited support of hierarchy or abstraction
• Future
• Multi-area extensions

6
Relationship with ASON

• ASON Automatic Switched Optical Networks
• A set of ITU-T standards for Optical control
  plane
• G.8080 ASON architecture
• G.7712, 7713, 7714, 7715 ASON requirements
• G.7713.1/2/3 and G.7714.1 protocol specs
• Top-down design
• Carrier-based requirements
• Multi-domain model
• Alignment with NNI
• Signaling aligned
• Routing tbd

7
What we can learn

• What can be done practically now?
• RSVP-based NNI signaling
• OSPF-TE (or ISIS)-based NNI routing
• What needs to be done?
• Multi-level hierarchy
• Domain support (redundancy, abstraction)
• Call identifier/end-to-end capabilities
• Where are there potential interoperability
  issues?
• Provisioning of control plane addresses/identifier
  s
• Interpretation of end-to-end objects (e.g., ERO)
• Etc.

8
Where do we go from here?

• The NNI Demo provides a proof-of-concept
• Protocol extensions to meet carrier needs
• Implementation of GMPLS/ASON across domains
• Software that can evolve to NNI standards
• Running code
• Target outputs
• Observations from the Demo documentation
• Feedback into IETF and ITU-T standards work
• ?Standards-based OIF NNI Interoperability
  Agreement(s)