%% You should probably cite draft-ietf-ccamp-transport-nbi-use-cases instead of this I-D. @techreport{tnbidt-ccamp-transport-nbi-use-cases-03, number = {draft-tnbidt-ccamp-transport-nbi-use-cases-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-tnbidt-ccamp-transport-nbi-use-cases/03/}, author = {Italo Busi and Daniel King}, title = {{Transport Northbound Interface Applicability Statement and Use Cases}}, pagetotal = 28, year = 2017, month = sep, day = 20, abstract = {Transport network domains, including Optical Transport Network (OTN) and Wavelength Division Multiplexing (WDM) networks, are typically deployed based on a single vendor or technology platforms. They are often managed using proprietary interfaces to dedicated Element Management Systems (EMS), Network Management Systems (NMS) and increasingly Software Defined Network (SDN) controllers. A well-defined open interface to each domain management system or controller is required for network operators to facilitate control automation and orchestrate end-to-end services across multi-domain networks. These functions may be enabled using standardized data models (e.g. YANG), and appropriate protocol (e.g., RESTCONF). This document describes the key use cases and requirements for transport network control and management. It reviews proposed and existing IETF transport network data models, their applicability, and highlights gaps and requirements.}, }