draft-ietf-ccamp-transport-nbi-app-statement-08.txt   draft-ietf-ccamp-transport-nbi-app-statement-09.txt 
CCAMP Working Group I. Busi CCAMP Working Group I. Busi
Internet Draft Huawei Internet Draft Huawei
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 1, 2019 Expires: May 2020 November 19, 2019
Transport Northbound Interface Applicability Statement Transport Northbound Interface Applicability Statement
draft-ietf-ccamp-transport-nbi-app-statement-08 draft-ietf-ccamp-transport-nbi-app-statement-09
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 1, line 37 skipping to change at page 1, line 37
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on May 1, 2020. This Internet-Draft will expire on May 19, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
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................................4 1.1. The Scope of this Document................................5
2. Terminology....................................................5 2. Terminology....................................................6
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 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]).
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]).
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-
skipping to change at page 85, line 18 skipping to change at page 85, line 18
} }
} }
B.1.2. JSON Code: mpi1-eth-topology.json B.1.2. JSON Code: mpi1-eth-topology.json
This is the JSON code reporting the ETH Topology @ MPI1: This is the JSON code reporting the ETH Topology @ MPI1:
========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ========== ========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ==========
{ {
"// __LAST_UPDATE__": "October 16, 2019", "// __LAST_UPDATE__": "November 19, 2019",
"// __TITLE__": "ETH Black Topology @ MPI1", "// __TITLE__": "ETH Black Topology @ MPI1",
"// __REFERENCE_DRAFTS__": { "// __REFERENCE_DRAFTS__": {
"ietf-routing-types@2017-12-04": "rfc8294", "ietf-routing-types@2017-12-04": "rfc8294",
"ietf-te-types@2019-07-05": "draft-ietf-teas-yang-te-types-10", "ietf-te-types@2019-07-05": "draft-ietf-teas-yang-te-types-10",
"ietf-network@2018-02-26": "rfc8345", "ietf-network@2018-02-26": "rfc8345",
"ietf-network-topology@2018-02-26": "rfc8345", "ietf-network-topology@2018-02-26": "rfc8345",
"ietf-te-topology@2019-02-07": "draft-ietf-teas-yang-te-topo-22", "ietf-te-topology@2019-02-07": "draft-ietf-teas-yang-te-topo-22",
"ietf-eth-tran-types@2019-03-27": "draft-ietf-ccamp-client-signa\ "ietf-eth-tran-types@2019-03-27": "draft-ietf-ccamp-client-signa\
\l-yang-00", \l-yang-00",
"ietf-eth-te-topology@2019-07-08": "draft-zheng-ccamp-client-top\ "ietf-eth-te-topology@2019-11-18": "draft-zheng-ccamp-client-top\
\o-yang-06" \o-yang-08"
}, },
"// __MISSING_ATTRIBUTES__": true, "// __MISSING_ATTRIBUTES__": true,
"ietf-network:networks": { "ietf-network:networks": {
"network": [ "network": [
{ {
"network-id": "providerId/201/clientId/300/topologyId/eth-bl\ "network-id": "providerId/201/clientId/300/topologyId/eth-bl\
\ack-topology", \ack-topology",
"network-types": { "network-types": {
"ietf-te-topology:te-topology": { "ietf-te-topology:te-topology": {
"ietf-eth-te-topology:eth-tran-topology": {} "ietf-eth-te-topology:eth-tran-topology": {}
} }
}, },
"ietf-te-topology:te-topology-identifier": { "ietf-te-topology:te-topology-identifier": {
"provider-id": 201, "provider-id": 201,
"client-id": 300, "client-id": 300,
"te-topology-id": "eth-black-topology" "topology-id": "eth-black-topology"
}, },
"// __COMMENT__ ietf-te-topology:te": "presence container re\ "// __COMMENT__ ietf-te-topology:te": "presence container re\
\quires: provider-id, client-id and te-topology-id", \quires: provider-id, client-id and te-topology-id",
"ietf-te-topology:te": { "ietf-te-topology:te": {
"name": "ETH Black Topology @ MPI1" "name": "ETH Black Topology @ MPI1"
}, },
"ietf-network:node": [ "ietf-network:node": [
{ {
"// __NODE__:__DESCRIPTION__": { "// __NODE__:__DESCRIPTION__": {
"name": "AN1", "name": "AN1",
skipping to change at page 86, line 22 skipping to change at page 86, line 22
"type": "Abstract Node", "type": "Abstract Node",
"physical node(s)": "The whole network domain 1" "physical node(s)": "The whole network domain 1"
}, },
"node-id": "10.0.0.1", "node-id": "10.0.0.1",
"ietf-te-topology:te-node-id": "10.0.0.1", "ietf-te-topology:te-node-id": "10.0.0.1",
"// __COMMENT__ supporting-node": "Not used because topo\ "// __COMMENT__ supporting-node": "Not used because topo\
\logy hierarchy is outside the scope of this JSON example", \logy hierarchy is outside the scope of this JSON example",
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-node-attributes": { "te-node-attributes": {
"name": "AN11", "name": "AN11",
"is-abstract": {}, "is-abstract": "",
"admin-status": "up" "admin-status": "up"
}, },
"oper-status": "up", "oper-status": "up",
"// __NOT-PRESENT__ tunnel-termination-point": "ETH Ac\ "// __NOT-PRESENT__ tunnel-termination-point": "ETH Ac\
\cess Links only (no ETH TE switching)" \cess Links only (no ETH TE switching)"
}, },
"ietf-network-topology:termination-point": [ "ietf-network-topology:termination-point": [
{ {
"// __DESCRIPTION__:__LTP__": { "// __DESCRIPTION__:__LTP__": {
"name": "AN1-1 LTP", "name": "AN1-1 LTP",
skipping to change at page 96, line 27 skipping to change at page 96, line 27
} }
} }
B.2.3. JSON Code: mpi1-epl-service-config.json B.2.3. JSON Code: mpi1-epl-service-config.json
This is the JSON code reporting the EPL service configuration @ MPI: This is the JSON code reporting the EPL service configuration @ MPI:
========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ========== ========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ==========
{ {
"// __LAST_UPDATE__": "October 16, 2019", "// __LAST_UPDATE__": "November 19, 2019",
"// __TITLE__": "EPL Configuration @ MPI1", "// __TITLE__": "EPL Configuration @ MPI1",
"// __REFERENCE_DRAFTS__": { "// __REFERENCE_DRAFTS__": {
"ietf-routing-types@2017-12-04": "rfc8294", "ietf-routing-types@2017-12-04": "rfc8294",
"ietf-te-types@2019-07-05": "draft-ietf-teas-yang-te-types-10", "ietf-te-types@2019-07-05": "draft-ietf-teas-yang-te-types-10",
"ietf-eth-tran-types@2019-03-27": "draft-ietf-ccamp-client-signa\ "ietf-eth-tran-types@2019-03-27": "draft-ietf-ccamp-client-signa\
\l-yang-00", \l-yang-00",
"ietf-eth-tran-service@2019-03-27": "draft-ietf-ccamp-client-sig\ "ietf-eth-tran-service@2019-03-27": "draft-ietf-ccamp-client-sig\
\nal-yang-00" \nal-yang-00"
}, },
"// __MISSING_ATTRIBUTES__": true, "// __MISSING_ATTRIBUTES__": true,
skipping to change at page 97, line 23 skipping to change at page 97, line 23
"topology-id": "eth-black-topology" "topology-id": "eth-black-topology"
}, },
"etht-svc-end-points": [ "etht-svc-end-points": [
{ {
"// __COMMENT__": "10GE Service End-Point at the access \ "// __COMMENT__": "10GE Service End-Point at the access \
\interface (S3-1 -> AN1-1)", \interface (S3-1 -> AN1-1)",
"etht-svc-end-point-name": "mpi1-epl-an1-1-service-end-p\ "etht-svc-end-point-name": "mpi1-epl-an1-1-service-end-p\
\oint", \oint",
"etht-svc-end-point-descr": "Ethernet Service End-Point \ "etht-svc-end-point-descr": "Ethernet Service End-Point \
\at S3-1 (AN1-1) access link", \at S3-1 (AN1-1) access link",
"service-classification-type": "ietf-eth-tran-types:port\
\-classification",
"etht-svc-access-points": [ "etht-svc-access-points": [
{ {
"// __COMMENT__": "10GE Service Access Point at the \ "// __COMMENT__": "10GE Service Access Point at the \
\access interface (S3-1 -> AN1-1)", \access interface (S3-1 -> AN1-1)",
"etht-svc-end-point-name": "mpi-epl-an1-1-service-ac\ "access-point-id": "mpi-epl-an1-1-service-access-poi\
\cess-point", \nt",
"// __COMMENT__ access-node-id": "AN1 NODE-ID", "// __COMMENT__ access-node-id": "AN1 NODE-ID",
"access-node-id": "10.0.0.1", "access-node-id": "10.0.0.1",
"// __COMMENT__ access-ltp-id": "AN1-1 LTP-ID", "// __COMMENT__ access-ltp-id": "AN1-1 LTP-ID",
"access-ltp-id": 1 "access-ltp-id": 1
} }
] ]
} }
], ],
"service-classification-type": "ietf-eth-tran-types:port-cla\
\ssification",
"// __COMMENT__ ingress-egress-bandwidth-profile": "Outside \ "// __COMMENT__ ingress-egress-bandwidth-profile": "Outside \
\the scope of this JSON example", \the scope of this JSON example",
"// __NOT-PRESENT__ vlan-operations": "Transparent VLAN oper\ "// __NOT-PRESENT__ vlan-operations": "Transparent VLAN oper\
\ations", \ations",
"etht-svc-tunnels": [ "etht-svc-tunnels": [
{ {
"// __COMMENT__ tunnel-name": "ODU2 Head Tunnel Segment \ "// __COMMENT__ tunnel-name": "ODU2 Head Tunnel Segment \
\@ MPI1", \@ MPI1",
"tunnel-name": "mpi1-odu2-tunnel" "tunnel-name": "mpi1-odu2-tunnel"
} }
 End of changes. 14 change blocks. 
15 lines changed or deleted 29 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/