Transport Northbound Interface Applicability Statement
draft-ietf-ccamp-transport-nbi-app-statement-02
CCAMP Working Group I. Busi
Internet Draft Huawei
Intended status: Informational D. King
Lancaster University
H. Zheng
Huawei
Y. Xu
CAICT
Expires: January 2019 July 2, 2018
Transport Northbound Interface Applicability Statement
draft-ietf-ccamp-transport-nbi-app-statement-02
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), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 2, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
Busi, King, et al. Expires January 2, 2019 [Page 1]
Internet-Draft Transport NBI Applicability-Statement July 2018
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) 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.
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 analyses the applicability of the YANG models being
defined by IETF (TEAS and CCAMP WGs in particular) to support OTN
single and multi-domain scenarios.
Table of Contents
1. Introduction...................................................4
1.1. Scope of this document....................................4
1.2. Assumptions...............................................5
2. Terminology....................................................6
3. Conventions used in this document..............................6
3.1. Topology and traffic flow processing......................6
3.2. JSON code.................................................7
4. Scenarios Description..........................................8
4.1. Reference Network.........................................8
4.1.1. Single-Domain Scenario..............................11
4.1.2. Multi-Domain Scenario...............................11
4.2. Topology Abstractions....................................11
4.3. Service Configuration....................................13
4.3.1. ODU Transit.........................................14
Busi, King, et al. Expires January 2, 2019 [Page 2]
Internet-Draft Transport NBI Applicability-Statement July 2018
4.3.2. EPL over ODU........................................15
4.3.3. Other OTN Clients Services..........................16
4.3.4. EVPL over ODU.......................................17
4.3.5. EVPLAN and EVPTree Services.........................18
4.3.6. Dynamic Service Configuration.......................19
Show full document text