Transport Northbound Interface Applicability Statement
draft-ietf-ccamp-transport-nbi-app-statement-10
CCAMP Working Group I. Busi
Internet Draft Huawei
Intended status: Informational D. King
Old Dog Consulting
H. Zheng
Huawei
Y. Xu
CAICT
Expires: May 2020 November 19, 2019
Transport Northbound Interface Applicability Statement
draft-ietf-ccamp-transport-nbi-app-statement-10
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 May 19, 2020.
Busi, King, et al. Expires May 19, 2020 [Page 1]
Internet-Draft Transport NBI Applicability-Statement November 2019
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
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
This document provides an analysis of the applicability of the YANG
models defined by the IETF (Traffic Engineering Architecture and
Signaling (TEAS) moreover, Common Control and Measurement Plane
(CCAMP) WGs in particular) to support ODU transit services,
Transparent client services and EPL/EVPL Ethernet services over OTN
single and multi-domain network scenarios.
This document also describes how existing YANG models can be used
through a number of worked examples and JSON fragments.
Table of Contents
1. Introduction...................................................4
1.1. The Scope of this Document................................4
2. Terminology....................................................5
3. Conventions Used in this Document..............................8
3.1. Topology and Traffic Flow Processing......................8
3.2. JSON code.................................................9
4. Scenarios Description.........................................10
4.1. Reference Network........................................10
4.2. Topology Abstractions....................................15
4.3. Service Configuration....................................16
4.3.1. ODU Transit.........................................17
4.3.2. EPL over ODU........................................18
4.3.3. Transparent Client Services.........................19
4.3.4. EVPL over ODU.......................................20
4.4. Multi-function Access Links..............................21
Busi, King, et al. Expires May 19, 2020 [Page 2]
Internet-Draft Transport NBI Applicability-Statement November 2019
4.5. Protection and Restoration Configuration.................22
4.5.1. Linear Protection (end-to-end)......................23
4.5.2. Segmented Protection................................24
4.6. Notification.............................................25
4.7. Path Computation with Constraints........................25
5. YANG Model Analysis...........................................26
5.1. YANG Models for Topology Abstraction.....................26
5.1.1. Domain 1 Black Topology Abstraction.................28
5.1.2. Domain 2 Black Topology Abstraction.................32
5.1.3. Domain 3 White Topology Abstraction.................33
5.1.4. Multi-domain Topology Merging.......................34
Show full document text