Transport Northbound Interface Applicability Statement and Use Cases
draft-tnbidt-ccamp-transport-nbi-use-cases-03

Document Type Replaced Internet-Draft (candidate for ccamp WG)
Last updated 2017-09-25 (latest revision 2017-09-20)
Replaced by draft-ietf-ccamp-transport-nbi-use-cases
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-ccamp-transport-nbi-use-cases
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-tnbidt-ccamp-transport-nbi-use-cases-03.txt

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.

Authors

Italo Busi (italo.busi@huawei.com)
Daniel King (d.king@lancaster.ac.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)