draft-ietf-ccamp-transport-nbi-app-statement-09.txt   draft-ietf-ccamp-transport-nbi-app-statement-10.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Intended status: Informational D. King Intended status: Informational D. King
Old Dog Consulting Old Dog Consulting
H. Zheng H. Zheng
Huawei Huawei
Y. Xu Y. Xu
CAICT CAICT
Expires: May 2020 November 19, 2019 Expires: May 2020 November 19, 2019
Transport Northbound Interface Applicability Statement Transport Northbound Interface Applicability Statement
draft-ietf-ccamp-transport-nbi-app-statement-09 draft-ietf-ccamp-transport-nbi-app-statement-10
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 35 skipping to change at page 2, line 35
(CCAMP) WGs in particular) to support ODU transit services, (CCAMP) WGs in particular) to support ODU transit services,
Transparent client services and EPL/EVPL Ethernet services over OTN Transparent client services and EPL/EVPL Ethernet services over OTN
single and multi-domain network scenarios. single and multi-domain network scenarios.
This document also describes how existing YANG models can be used This document also describes how existing YANG models can be used
through a number of worked examples and JSON fragments. through a number of worked examples and JSON fragments.
Table of Contents Table of Contents
1. Introduction...................................................4 1. Introduction...................................................4
1.1. The Scope of this Document................................5 1.1. The Scope of this Document................................4
2. Terminology....................................................6 2. Terminology....................................................5
3. Conventions Used in this Document..............................8 3. Conventions Used in this Document..............................8
3.1. Topology and Traffic Flow Processing......................8 3.1. Topology and Traffic Flow Processing......................8
3.2. JSON code.................................................9 3.2. JSON code.................................................9
4. Scenarios Description.........................................10 4. Scenarios Description.........................................10
4.1. Reference Network........................................10 4.1. Reference Network........................................10
4.2. Topology Abstractions....................................15 4.2. Topology Abstractions....................................15
4.3. Service Configuration....................................16 4.3. Service Configuration....................................16
4.3.1. ODU Transit.........................................17 4.3.1. ODU Transit.........................................17
4.3.2. EPL over ODU........................................18 4.3.2. EPL over ODU........................................18
4.3.3. Transparent Client Services.........................19 4.3.3. Transparent Client Services.........................19
skipping to change at page 4, line 26 skipping to change at page 4, line 26
domains are critical for a wide range of applications and services, domains are critical for a wide range of applications and services,
including data center and LAN interconnects, Internet service including data center and LAN interconnects, Internet service
backhauling, mobile backhaul and enterprise Carrier Ethernet backhauling, mobile backhaul and enterprise Carrier Ethernet
services. A clear goal of operators is to automate the setup of services. A clear goal of operators is to automate the setup of
these connectivity services across multiple transport network these connectivity services across multiple transport network
domains, that may utilize different technologies. domains, that may utilize different technologies.
A well-defined common open interface to each domain controller or a A well-defined common open interface to each domain controller or a
management system is required for network operators to control management system is required for network operators to control
multi-vendor and multi-domain networks and also enable coordination multi-vendor and multi-domain networks and also enable coordination
and automation of service provisioning. This is facilitated A
well-defined common open interface to each domain controller or a
management system is required for network operators to control
multi-vendor and multi-domain networks and also enable coordination
and automation of service provisioning. This is facilitated by using
standardized data models (e.g., YANG models), and an appropriate
protocol (e.g., RESTCONF [RFC8040]).
A well-defined common open interface to each domain controller or a
management system is required for network operators to control
multi-vendor and multi-domain networks and also enable coordination
and automation of service provisioning. This is facilitated by using and automation of service provisioning. This is facilitated by using
standardized data models (e.g., YANG models), and an appropriate standardized data models (e.g., YANG models), and an appropriate
protocol (e.g., RESTCONF [RFC8040]). protocol (e.g., RESTCONF [RFC8040]).
by using standardized data models (e.g., YANG models), and an
appropriate protocol (e.g., RESTCONF [RFC8040]).
This document examines the applicability of the YANG models being This document examines the applicability of the YANG models being
defined by IETF (Traffic Engineering Architecture and Signaling defined by IETF (Traffic Engineering Architecture and Signaling
(TEAS) moreover, Common Control and Measurement Plane (CCAMP) WGs in (TEAS) moreover, Common Control and Measurement Plane (CCAMP) WGs in
particular) to support Optical Transport Networks (OTN) single and particular) to support Optical Transport Networks (OTN) single and
multi-domain scenarios. multi-domain scenarios.
1.1. The Scope of this Document 1.1. The Scope of this Document
This document assumes a reference architecture, including This document assumes a reference architecture, including
interfaces, based on the Abstraction and Control of Traffic- interfaces, based on the Abstraction and Control of Traffic-
 End of changes. 4 change blocks. 
17 lines changed or deleted 3 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/