﻿<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>

<rfc category="info" docName="draft-chen-unified-control-architecture-00" ipr="trust200902">

  <front >
    <title>Unified Control Architecture for Optical Transport Networks</title>
    <author fullname="Haoran Chen" initials="H" role="editor" surname="Chen">
      <organization abbrev="bupt">Beijing University of Posts and Telecommunications</organization>
      <address>
        <postal>
          <street>Xitucheng Road</street>
          <city>Beijing</city>
          <region>Haidian Dist</region>
          <code>100876</code>
          <country>China</country>
        </postal>
        <phone></phone>
        <facsimile></facsimile>
        <email>haoran1860@163.com</email>
      </address>
    </author>
    
    <date></date>
    <area>Operations and Management</area>
    <keyword>unified control</keyword>
    
    <abstract>
      <t>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.</t>
    </abstract>
  </front>


  <middle>
    <section title="Introduction">
      <t>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.</t><!--可以进行故障定位，动态参数调整，预测器件老化，跨层优化-->
    </section>
    
    <section title="Requirements Language">
      <t>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 <xref target="RFC2119"/>.
      </t>
    </section>
    
    <section title="Terminology">
    </section>
    

    <section title="Motivation and Goals">
      <!--这部分主要讲分层设计的不足，SDN如何提供了一个平台，物理层设备标准如何统一-->
      <t> 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. </t>
      <t>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.</t>
      
      <section title="Architecture">
        <t>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.</t>
      </section>
      
    </section>


    <section title="Architectural Considerations of Unified Control Architecture">
      <section title="Data Report">
        <!--需要决定上报的数据类型，数据的初步整合方案，上报间隔等等。-->
      </section>
      
      <section title="Data Filter">
        <!--有些数据在设备发生某些变动以后，就不再适用了。此时应该有某种节点级别的判断机制，节点能够主动上报给EPC-->
      </section>
    
    </section>

    <section title="Security Considerations"></section>
    
    <section title="Acknowledgments"></section>
      
    <section title="Contributors"></section>
      
  </middle>


  <back>
    <references title="Normative References">
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
    </references>  
<!--    <references title="Informative References">
      
    </references>-->
    
  </back>
  
  
</rfc>