Network Working Group H. Chen, Ed.
Internet-Draft bupt
Intended status: Informational June 16, 2017
Expires: December 18, 2017

Unified Control Architecture for Optical Transport Networks


This memo specifies a unified control architecture for Optical Transport Network (OTN) based on Software Defined Networking (SDN). The architecture can be applied over multi-domain multi-vendor networks.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on December 18, 2017.

Copyright Notice

Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

1. Introduction

This memo introduce an Software Defined Networking (SDN) based architecture to monitor and analyse physical parameters on various types of network equipments, and control the adjustable part of whole parameters. SDN is a programmable networks approach that supports the separation of control and forwarding plane via standardized interfaces, and make equipments foolish while centralizing control function on a logical entity named Controller. The controller can achieve rapid and accurate fault location, dynamic parameter adjustment, device aging forecast, and cross-layer optimization via this memo.

2. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

3. Terminology

4. Motivation and Goals

In order to support various cloud services which are remote and geographically distributed, we need a high-capacity, high-reliability and high-flexibility network. Optical network, as a strong candidate, could provide energy-efficiency, dynamic control, and recent technology advancements including software defined network (SDN) support. Software defined optical network (SDON), which allows carriers to control the optical network using software running on a network operating system, leads to a more flexible control manner.

On the other hand, in today’s commercial optical transport networks (OTN), different domains, especially equipment of different vendors, are separately operated without dynamic interaction, which leads to low network efficiency, high OPEX and CAPAX. In light of this, some latest activities have tried to apply SDON/Openflow to multi-domain optical networks. This results in a lack of universality for promoting a unified control manner for multi-vendor multi-domain OTN.

4.1. Architecture

The unified control orchestrator (UCO) architecture for multi-vendor multi-domain OTN is illustrated. The architecture aims to achieve the port discovery, resources collection, routing path computing, OTN connection creation, and connection deletion. 4 layers are presented for the required functions.

5. Architectural Considerations of Unified Control Architecture

5.1. Data Report

5.2. Data Filter

6. Security Considerations

7. Acknowledgments

8. Contributors

9. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.

Author's Address

Haoran Chen (editor) Beijing University of Posts and Telecommunications Xitucheng Road Beijing, Haidian Dist 100876 China EMail: