draft-ietf-ccamp-otn-tunnel-model-03.txt   draft-ietf-ccamp-otn-tunnel-model-04.txt 
CCAMP Working Group H. Zheng CCAMP Working Group H. Zheng
Internet-Draft A. Guo Internet-Draft A. Guo
Intended status: Standards Track I. Busi Intended status: Standards Track I. Busi
Expires: January 3, 2019 Huawei Technologies Expires: February 11, 2019 Huawei Technologies
A. Sharma A. Sharma
Google Google
R. Rao R. Rao
Infinera Infinera
S. Belotti S. Belotti
Nokia Nokia
V. Lopez V. Lopez
Telefonica Telefonica
Y. Li Y. Li
China Mobile China Mobile
Y. Xu Y. Xu
CAICT CAICT
July 2, 2018 August 10, 2018
OTN Tunnel YANG Model OTN Tunnel YANG Model
draft-ietf-ccamp-otn-tunnel-model-03 draft-ietf-ccamp-otn-tunnel-model-04
Abstract Abstract
This document describes the YANG data model for OTN Tunnels. This document describes the YANG data model for OTN Tunnels.
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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 3, 2019. This Internet-Draft will expire on February 11, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 21 skipping to change at page 2, line 21
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Notations . . . . . . . . . . . . . . . . . . 2 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 2
3. OTN Tunnel Model Description . . . . . . . . . . . . . . . . 3 3. OTN Tunnel Model Description . . . . . . . . . . . . . . . . 3
3.1. Overview of OTN Tunnel Model . . . . . . . . . . . . . . 3 3.1. Overview of OTN Tunnel Model . . . . . . . . . . . . . . 3
3.2. OTN-specific Parameters in Tunnel Model . . . . . . . . . 3 3.2. OTN-specific Parameters in Tunnel Model . . . . . . . . . 4
3.3. OTN Path Compute RPC . . . . . . . . . . . . . . . . . . 4 3.3. OTN Path Compute RPC . . . . . . . . . . . . . . . . . . 4
4. OTN Tunnel YANG Tree . . . . . . . . . . . . . . . . . . . . 4 4. OTN Tunnel YANG Tree . . . . . . . . . . . . . . . . . . . . 4
5. OTN Tunnel YANG Code . . . . . . . . . . . . . . . . . . . . 21 5. OTN Tunnel YANG Code . . . . . . . . . . . . . . . . . . . . 21
6. OTN Types YANG Code . . . . . . . . . . . . . . . . . . . . . 48 6. OTN Types YANG Code . . . . . . . . . . . . . . . . . . . . . 48
7. Security Considerations . . . . . . . . . . . . . . . . . . . 60 7. Security Considerations . . . . . . . . . . . . . . . . . . . 57
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 60 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 58
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 60 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 58
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 61 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 59
11.1. Normative References . . . . . . . . . . . . . . . . . . 61 11.1. Normative References . . . . . . . . . . . . . . . . . . 59
11.2. Informative References . . . . . . . . . . . . . . . . . 62 11.2. Informative References . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 61
1. Introduction 1. Introduction
OTN transport networks can carry various types of client services. OTN transport networks can carry various types of client services.
In many cases, the client signal is carried over an OTN tunnel across In many cases, the client signal is carried over an OTN tunnel across
connected domains in a multi-domain network. These OTN services can connected domains in a multi-domain network. These OTN services can
either be transported or switched in the OTN network. If an OTN either be transported or switched in the OTN network. If an OTN
tunnel is switched, then additional parameters need to be provided to tunnel is switched, then additional parameters need to be provided to
create a Mux OTN service. create a Mux OTN service.
skipping to change at page 3, line 22 skipping to change at page 3, line 22
o Symbols after data node names: "?" means an optional node, "!" o Symbols after data node names: "?" means an optional node, "!"
means a presence container, and "*" denotes a list and leaf-list. means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":"). marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
o More OTN specific terms can be found in
[I-D.ietf-ccamp-otn-topo-yang].
3. OTN Tunnel Model Description 3. OTN Tunnel Model Description
3.1. Overview of OTN Tunnel Model 3.1. Overview of OTN Tunnel Model
The OTN tunnel model is using TE tunnel [I-D.ietf-teas-yang-te] as a The OTN tunnel model is using TE tunnel [I-D.ietf-teas-yang-te] as a
basic model and augment to the TE tunnel with OTN-specific basic model and augment to the TE tunnel with OTN-specific
parameters, including the bandwidth information and label parameters, including the bandwidth information and label
information. It is also worth noting that the OTN tunnel information. It is also worth noting that the OTN tunnel
provisioning is usually based on the OTN topology. Therefore the OTN provisioning is usually based on the OTN topology. Therefore the OTN
tunnel model is usually used together with OTN topology model tunnel model is usually used together with OTN topology model
specified in [I-D.ietf-ccamp-otn-topo-yang]. specified in [I-D.ietf-ccamp-otn-topo-yang]. The OTN tunnel model
also imports a few type modules, including ietf-otn-types, ietf-te-
types and ietf-inet-types.
More scenarios and model applications can be found in More scenarios and model applications can be found in
[I-D.ietf-ccamp-transport-nbi-app-statement] and [I-D.ietf-ccamp-transport-nbi-app-statement] and
[I-D.ietf-teas-actn-yang]. The current model is following the YANG [I-D.ietf-teas-actn-yang]. The current model is following the YANG
language specification as [RFC7950], and the corresponding protocol language specification as [RFC7950], and the corresponding protocol
is recommended to be Netconf protocol in [RFC6241] or RESTconf is recommended to be Netconf protocol in [RFC6241] or RESTconf
protocol in [RFC8040]. protocol in [RFC8040].
The YANG module ietf-otn-tunnel defined in this document conforms to
the Network Management Datastore Architecture (NMDA) defined in
[RFC8342].
3.2. OTN-specific Parameters in Tunnel Model 3.2. OTN-specific Parameters in Tunnel Model
OTN specific parameters have been augmenting to the TE tunnel models. OTN specific parameters have been augmenting to the TE tunnel models.
The attributes on both of the source and destination need to be The attributes on both of the source and destination need to be
configured when setting up the tunnel. Typical parameters, including configured when setting up the tunnel. Typical parameters, including
client signal, TPN, TSG and corresponding tributary slot information, client signal, TPN, TSG and corresponding tributary slot information,
are required in the OTN tunnel model. These parameters are are required in the OTN tunnel model. These parameters are
consistent with the framework in [RFC7062], and the specification in consistent with the framework in [RFC7062], and the specification in
[RFC7138] and [RFC7139]. [RFC7138] and [RFC7139].
skipping to change at page 21, line 30 skipping to change at page 21, line 42
| +--:(generic) | +--:(generic)
| | +--ro generic? rt-types:generalized-label | | +--ro generic? rt-types:generalized-label
| +--:(otn) | +--:(otn)
| +--ro tpn? uint16 | +--ro tpn? uint16
| +--ro tsg? identityref | +--ro tsg? identityref
| +--ro ts-list? string | +--ro ts-list? string
+--ro direction? te-label-direction +--ro direction? te-label-direction
5. OTN Tunnel YANG Code 5. OTN Tunnel YANG Code
<CODE BEGINS>file "ietf-otn-tunnel@2018-06-30.yang" <CODE BEGINS>file "ietf-otn-tunnel@2018-08-10.yang"
module ietf-otn-tunnel { module ietf-otn-tunnel {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-otn-tunnel"; namespace "urn:ietf:params:xml:ns:yang:ietf-otn-tunnel";
prefix "otn-tunnel"; prefix "otn-tunnel";
import ietf-te { import ietf-te {
prefix "te"; prefix "te";
} }
import ietf-otn-types { import ietf-otn-types {
prefix "otn-types"; prefix "otn-types";
} }
import ietf-te-types { import ietf-te-types {
prefix "te-types"; prefix "te-types";
skipping to change at page 22, line 44 skipping to change at page 23, line 8
Editor: Yunbo Li Editor: Yunbo Li
<mailto:liyunbo@chinamobile.com> <mailto:liyunbo@chinamobile.com>
Editor: Yunbin Xu Editor: Yunbin Xu
<mailto:xuyunbin@ritt.cn>"; <mailto:xuyunbin@ritt.cn>";
description description
"This module defines a model for OTN Tunnel Services."; "This module defines a model for OTN Tunnel Services.";
revision "2018-07-02" { revision "2018-08-10" {
description description
"Revision 0.6"; "Revision 0.7";
reference reference
"draft-ietf-ccamp-otn-tunnel-model-03"; "draft-ietf-ccamp-otn-tunnel-model-04";
} }
/* /*
* Groupings * Groupings
*/ */
grouping otn-tunnel-attributes { grouping otn-tunnel-attributes {
description "Parameters for OTN tunnel"; description "Parameters for OTN tunnel";
leaf src-client-signal { leaf src-client-signal {
skipping to change at page 45, line 31 skipping to change at page 45, line 38
type identityref { type identityref {
base te-types:path-metric-type; base te-types:path-metric-type;
} }
default te-types:path-metric-te; default te-types:path-metric-te;
description description
"The tunnel path metric type."; "The tunnel path metric type.";
} }
leaf odu-type { leaf odu-type {
type identityref{ type identityref{
base otn-types:tributary-protocol-type; base otn-types:odu-type;
} }
description "Type of ODU"; description "Type of ODU";
} }
container p2p-primary-paths { container p2p-primary-paths {
description "Set of P2P primary paths container"; description "Set of P2P primary paths container";
list p2p-primary-path { list p2p-primary-path {
key "name"; key "name";
description description
"List of primary paths for this tunnel."; "List of primary paths for this tunnel.";
leaf name { leaf name {
skipping to change at page 47, line 46 skipping to change at page 48, line 4
type string; type string;
description "TE path name"; description "TE path name";
} }
uses p2p-path-ero; uses p2p-path-ero;
} }
} }
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
6. OTN Types YANG Code 6. OTN Types YANG Code
<CODE BEGINS> file "ietf-otn-types@2018-06-30.yang" <CODE BEGINS> file "ietf-otn-types@2018-08-10.yang"
module ietf-otn-types { module ietf-otn-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-otn-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-otn-types";
prefix "otn-types"; prefix "otn-types";
organization organization
"IETF CCAMP Working Group"; "IETF CCAMP Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/ccamp/> "WG Web: <http://tools.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org> WG List: <mailto:ccamp@ietf.org>
skipping to change at page 48, line 48 skipping to change at page 49, line 5
Editor: Yunbo Li Editor: Yunbo Li
<mailto:liyunbo@chinamobile.com> <mailto:liyunbo@chinamobile.com>
Editor: Yunbin Xu Editor: Yunbin Xu
<mailto:xuyunbin@ritt.cn>"; <mailto:xuyunbin@ritt.cn>";
description description
"This module defines OTN types."; "This module defines OTN types.";
revision "2018-06-30" { revision "2018-08-10" {
description description
"Revision 0.6"; "Revision 0.8";
reference reference
"draft-ietf-ccamp-otn-tunnel-model-03"; "draft-ietf-ccamp-otn-tunnel-model-04";
} }
identity tributary-slot-granularity { identity tributary-slot-granularity {
description description
"Tributary slot granularity"; "Tributary slot granularity";
reference reference
"G.709/Y.1331, February 2016: Interfaces for the Optical "G.709/Y.1331, February 2016: Interfaces for the Optical
Transport Network (OTN)"; Transport Network (OTN)";
} }
skipping to change at page 49, line 28 skipping to change at page 49, line 31
base tributary-slot-granularity; base tributary-slot-granularity;
description description
"1.25G tributary slot granularity"; "1.25G tributary slot granularity";
} }
identity tsg-2.5G { identity tsg-2.5G {
base tributary-slot-granularity; base tributary-slot-granularity;
description description
"2.5G tributary slot granularity"; "2.5G tributary slot granularity";
} }
/*
identity tsg-1.25Gand2.5G {
base tributary-slot-granularity;
description
"Both 1.25G and 2.5G tributary slot granularity";
}
*/
/*
Note: suggest to replace the term 'tributary-protocol-type' with
'odu-type', to avoid misleading.
*/
identity tributary-protocol-type {
description
"Base identity for protocol framing used by tributary signals";
}
/*
Note: suggest to remove all the prot-OTUx
*/
identity prot-OTU1 {
base tributary-protocol-type;
description
"OTU1 protocol (2.66G)";
}
/*
identity prot-OTU1e {
base tributary-protocol-type;
description
"OTU1e type (11.04G)";
}
identity prot-OTU1f { identity odu-type {
base tributary-protocol-type;
description
"OTU1f type (11.27G)";
}
*/
identity prot-OTU2 {
base tributary-protocol-type;
description
"OTU2 type (10.70G)";
}
identity prot-OTU2e {
base tributary-protocol-type;
description
"OTU2e type (11.09G)";
}
/*
identity prot-OTU2f {
base tributary-protocol-type;
description
"OTU2f type (11.31G)";
}
*/
identity prot-OTU3 {
base tributary-protocol-type;
description
"OTU3 type (43.01G)";
}
/*
identity prot-OTU3e1 {
base tributary-protocol-type;
description
"OTU3e1 type (44.57G)";
}
identity prot-OTU3e2 {
base tributary-protocol-type;
description
"OTU3e2 type (44.58G)";
}
*/
identity prot-OTU4 {
base tributary-protocol-type;
description
"OTU4 type (111.80G)";
}
identity prot-OTUCn {
base tributary-protocol-type;
description description
"OTUCn type (beyond 100G)"; "Base identity for protocol framing used by tributary signals";
} }
/* identity ODU0 {
Note: suggest to rename the term, remove the prefix 'prot-'. base odu-type;
*/
identity prot-ODU0 {
base tributary-protocol-type;
description description
"ODU0 protocol (1.24G)"; "ODU0 protocol (1.24G)";
} }
identity prot-ODU1 { identity ODU1 {
base tributary-protocol-type; base odu-type;
description description
"ODU1 protocol (2.49G)"; "ODU1 protocol (2.49G)";
} }
/* /*
identity prot-ODU1e { identity ODU1e {
base tributary-protocol-type; base odu-type;
description description
"ODU1e protocol (10.35G)."; "ODU1e protocol (10.35G).";
} }
identity prot-ODU1f { identity ODU1f {
base tributary-protocol-type; base odu-type;
description description
"ODU1f protocol (10.56G)."; "ODU1f protocol (10.56G).";
} }
*/ */
identity prot-ODU2 { identity ODU2 {
base tributary-protocol-type; base odu-type;
description description
"ODU2 protocol (10.03G)"; "ODU2 protocol (10.03G)";
} }
identity prot-ODU2e { identity ODU2e {
base tributary-protocol-type; base odu-type;
description description
"ODU2e protocol (10.39G)"; "ODU2e protocol (10.39G)";
} }
/* /*
identity prot-ODU2f { identity ODU2f {
base tributary-protocol-type; base odu-type;
description description
"ODU2f protocol (10.60G)."; "ODU2f protocol (10.60G).";
} }
*/ */
identity prot-ODU3 { identity ODU3 {
base tributary-protocol-type; base odu-type;
description description
"ODU3 protocol (40.31G)"; "ODU3 protocol (40.31G)";
} }
/* /*
identity prot-ODU3e1 { identity ODU3e1 {
base tributary-protocol-type; base odu-type;
description description
"ODU3e1 protocol (41.77G)."; "ODU3e1 protocol (41.77G).";
} }
identity prot-ODU3e2 { identity ODU3e2 {
base tributary-protocol-type; base odu-type;
description description
"ODU3e2 protocol (41.78G)."; "ODU3e2 protocol (41.78G).";
} }
*/ */
identity prot-ODU4 { identity ODU4 {
base tributary-protocol-type; base odu-type;
description description
"ODU4 protocol (104.79G)"; "ODU4 protocol (104.79G)";
} }
identity prot-ODUFlex-cbr { identity ODUFlex-cbr {
base tributary-protocol-type; base odu-type;
description description
"ODU Flex CBR protocol for transporting constant bit rate "ODU Flex CBR protocol for transporting constant bit rate
signal"; signal";
} }
identity prot-ODUFlex-gfp { identity ODUFlex-gfp {
base tributary-protocol-type; base odu-type;
description description
"ODU Flex GFP protocol for transporting stream of packets "ODU Flex GFP protocol for transporting stream of packets
using Generic Framing Procedure"; using Generic Framing Procedure";
} }
identity prot-ODUCn {
base tributary-protocol-type;
description
"ODUCn protocol (beyond 100G)";
}
/*
Note: suggest to remove the types with 'prot-xGbE'.
*/
identity prot-1GbE {
base tributary-protocol-type;
description
"1G Ethernet protocol";
}
identity prot-10GbE-LAN {
base tributary-protocol-type;
description
"10G Ethernet LAN protocol";
}
identity prot-40GbE {
base tributary-protocol-type;
description
"40G Ethernet protocol";
}
identity prot-100GbE { identity ODUCn {
base tributary-protocol-type; base odu-type;
description description
"100G Ethernet protocol"; "ODUCn protocol (beyond 100G)";
} }
identity client-signal { identity client-signal {
description description
"Base identity from which specific client signals for the "Base identity from which specific client signals for the
tunnel are derived"; tunnel are derived";
} }
/* identity ETH-1Gb {
Note: need to reconsider the prefix 'client-signal'.
Comment 1: need to understand whether for same client-signal, there
should be separate identity for transparent and non-transparent or not?
Comment 2: need to better align the term with other models, like L1CSM.
*/
identity client-signal-1GbE {
base client-signal; base client-signal;
description description
"Client signal type of 1GbE"; "Client signal type of 1GbE";
} }
identity client-signal-10GbE-LAN { identity ETH-10Gb-LAN {
base client-signal; base client-signal;
description description
"Client signal type of 10GbE LAN"; "Client signal type of 10GbE LAN";
} }
identity client-signal-10GbE-WAN { identity ETH-10Gb-WAN {
base client-signal; base client-signal;
description description
"Client signal type of 10GbE WAN"; "Client signal type of 10GbE WAN";
} }
identity client-signal-40GbE { identity ETH-40Gb {
base client-signal; base client-signal;
description description
"Client signal type of 40GbE"; "Client signal type of 40GbE";
} }
identity client-signal-100GbE { identity ETH-100Gb {
base client-signal; base client-signal;
description description
"Client signal type of 100GbE"; "Client signal type of 100GbE";
} }
identity client-signal-OC3_STM1 { identity STM-1 {
base client-signal;
description
"Client signal type of OC3 & STM1";
}
identity client-signal-OC12_STM4 {
base client-signal;
description
"Client signal type of OC12 & STM4";
}
identity client-signal-OC48_STM16 {
base client-signal;
description
"Client signal type of OC48 & STM16";
}
identity client-signal-OC192_STM64 {
base client-signal; base client-signal;
description description
"Client signal type of OC192 & STM64"; "Client signal type of OC3 & STM-1";
} }
identity client-signal-OC768_STM256 { identity STM-4 {
base client-signal; base client-signal;
description description
"Client signal type of OC768 & STM256"; "Client signal type of OC12 & STM-4";
} }
identity client-signal-ODU0 { identity STM-16 {
base client-signal; base client-signal;
description description
"Client signal type of ODU0 (1.24G)"; "Client signal type of OC48 & STM-16";
} }
identity client-signal-ODU1 { identity STM-64 {
base client-signal; base client-signal;
description description
"ODU1 protocol (2.49G)"; "Client signal type of OC192 & STM-64";
} }
identity client-signal-ODU2 { identity STM-256 {
base client-signal; base client-signal;
description description
"Client signal type of ODU2 (10.03G)"; "Client signal type of OC768 & STM-256";
} }
identity client-signal-ODU2e { identity FC-100 {
base client-signal; base client-signal;
description description
"Client signal type of ODU2e (10.39G)"; "Client signal type of Fibre Channel FC-100";
} }
identity client-signal-ODU3 { identity FC-200 {
base client-signal;
description
"Client signal type of ODU3 (40.31G)";
}
/*
identity client-signal-ODU3e2 {
base client-signal;
description
"Client signal type of ODU3e2 (41.78G)";
}
*/
identity client-signal-ODU4 {
base client-signal; base client-signal;
description description
"Client signal type of ODU4 (104.79G)"; "Client signal type of Fibre Channel FC-200";
} }
identity client-signal-ODUflex-cbr { identity FC-400 {
base client-signal; base client-signal;
description description
"Client signal type of ODU Flex CBR"; "Client signal type of Fibre Channel FC-400";
} }
identity client-signal-ODUflex-gfp { identity FC-800 {
base client-signal; base client-signal;
description description
"Client signal type of ODU Flex GFP"; "Client signal type of Fibre Channel FC-800";
} }
identity client-signal-ODUCn { identity FC-1200 {
base client-signal; base client-signal;
description description
"Client signal type of ODUCn (beyond 100G)"; "Client signal type of Fibre Channel FC-1200";
} }
identity client-signal-FC400 { identity FC-1600 {
base client-signal; base client-signal;
description description
"Client signal type of Fibre Channel FC400"; "Client signal type of Fibre Channel FC-1600";
} }
identity client-signal-FC800 { identity FC-3200 {
base client-signal; base client-signal;
description description
"Client signal type of Fibre Channel FC800"; "Client signal type of Fibre Channel FC-3200";
} }
identity client-signal-FICON-4G { identity FICON-4G {
base client-signal; base client-signal;
description description
"Client signal type of Fibre Connection 4G"; "Client signal type of Fibre Connection 4G";
} }
identity client-signal-FICON-8G { identity FICON-8G {
base client-signal; base client-signal;
description description
"Client signal type of Fibre Connection 8G"; "Client signal type of Fibre Connection 8G";
} }
identity client-signal-OTU1 {
base client-signal;
description
"Client signal type of OTU1";
}
identity client-signal-OTU2 {
base client-signal;
description
"Client signal type of OTU2";
}
identity client-signal-OTU2e {
base client-signal;
description
"Client signal type of OTU2e";
}
identity client-signal-OTU3 {
base client-signal;
description
"Client signal type of OTU3";
}
identity client-signal-OTU4 {
base client-signal;
description
"Client signal type of OTU4";
}
identity otn-label-range-type { identity otn-label-range-type {
description description
"Base identity from which specific OTN label "Base identity from which specific OTN label
range types derived"; range types derived";
} }
identity label-range-trib-slot { identity label-range-trib-slot {
base otn-label-range-type; base otn-label-range-type;
description description
"Defines a range of OTN tributary slots"; "Defines a range of OTN tributary slots";
} }
identity label-range-trib-port { identity label-range-trib-port {
base otn-label-range-type; base otn-label-range-type;
description description
"Defines a range of OTN tributary ports"; "Defines a range of OTN tributary ports";
} }
grouping otn-link-bandwidth { grouping otn-link-bandwidth {
description "link bandwidth attributes for OTN";
list odulist { list odulist {
key "odu-type"; key "odu-type";
description description
"OTN bandwidth definition"; "OTN bandwidth definition";
leaf odu-type { leaf odu-type {
type identityref { type identityref {
base otn-types:tributary-protocol-type; base otn-types:odu-type;
} }
description "ODU type"; description "ODU type";
} }
leaf number { leaf number {
type uint16; type uint16;
description "Number of ODUs"; description "Number of ODUs";
} }
} }
} }
grouping otn-path-bandwidth { grouping otn-path-bandwidth {
description "path bandwidth attributes for OTN";
leaf odu-type { leaf odu-type {
type identityref { type identityref {
base otn-types:tributary-protocol-type; base otn-types:odu-type;
} }
description "ODU type"; description "ODU type";
} }
} }
grouping otn-label-restriction { grouping otn-label-restriction {
description "label restriction information for OTN";
leaf range-type { leaf range-type {
type identityref { type identityref {
base otn-types:otn-label-range-type; base otn-types:otn-label-range-type;
} }
description "type for range";
} }
leaf tsg { leaf tsg {
type identityref { type identityref {
base otn-types:tributary-slot-granularity; base otn-types:tributary-slot-granularity;
} }
description "Tributary slot granularity."; description "Tributary slot granularity.";
reference reference
"G.709/Y.1331, February 2016: Interfaces for the "G.709/Y.1331, February 2016: Interfaces for the
Optical Transport Network (OTN)"; Optical Transport Network (OTN)";
} }
leaf priority { leaf priority {
type uint8; type uint8;
description "priority."; description "priority.";
} }
} }
/* Note: Suggest to be changed as otn-label-range;
otn-topology/tunnel also need change */
grouping otn-link-label { grouping otn-link-label {
description "link label information for OTN, for label-start/end";
choice otn-label-type { choice otn-label-type {
description description
"OTN label type"; "OTN label range type, either TPN range or TS range";
case tributary-port { case tributary-port {
leaf tpn { leaf tpn {
type uint16 { type uint16 {
range "1..4095"; range "1..4095";
} }
description description
"Tributary Port Number. Applicable in case of mux services."; "Tributary Port Number. Applicable in case of mux services.";
reference reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving "RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks."; G.709 Optical Transport Networks.";
skipping to change at page 59, line 34 skipping to change at page 56, line 11
description description
"Tributary Slot Number. Applicable in case of mux services."; "Tributary Slot Number. Applicable in case of mux services.";
reference reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving "RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks."; G.709 Optical Transport Networks.";
} }
} }
} }
} }
/* Note: Suggest to be changed as otn-label;
otn-topology/tunnel also need change */
grouping otn-path-label { grouping otn-path-label {
description "label information for OTN, for label-hop";
leaf tpn { leaf tpn {
type uint16 { type uint16 {
range "1..4095"; range "1..4095";
} }
description description
"Tributary Port Number. Applicable in case of mux services."; "Tributary Port Number. Applicable in case of mux services.";
reference reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving "RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks."; G.709 Optical Transport Networks.";
} }
skipping to change at page 60, line 22 skipping to change at page 57, line 4
"A list of available tributary slots ranging "A list of available tributary slots ranging
between 1 and 9999. between 1 and 9999.
For example 1-20,25,50-1000"; For example 1-20,25,50-1000";
reference "RFC 7139: GMPLS Signaling Extensions for Control reference "RFC 7139: GMPLS Signaling Extensions for Control
of Evolving G.709 Optical Transport Networks"; of Evolving G.709 Optical Transport Networks";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
7. Security Considerations 7. Security Considerations
TBD. The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246].
The NETCONF access control model [RFC6536] provides the means to
restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content.
There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability:
/te:te/te:tunnels/te:tunnel /te:te/../te:te-bandwidth/te:technology
/te:te/../te:type/te:label/te:label-hop/te:te-label/te:technology
/te:te/../te:label-restrictions/te:label-restriction/te:label-start/
te:te-label/te:technology /te:te/../te:label-restrictions/te:label-
restriction/te:label-end/te:te-label/te:technology
/te:te/../te:label-restrictions/te:label-restriction/ Editors note:
we are using simplified description by folding similar branches to
avoid repetation.
Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability:
/te:te/../te:type/te:label/te:label-hop/te:te-label/te:technology
Editors note: we are using simplified description by folding similar
branches to avoid repetation.
Some of the RPC operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the
operations and their sensitivity/vulnerability:
+---x otn-te-tunnel-path-compute This path compute RPC provides a
mechanism to enable the client to query and/or subscribe on the
tunnel to be notified whenever it changes. Thus path computation is
only for the client reference, with no real deploy or resource
reservation.
8. IANA Considerations 8. IANA Considerations
TBD. It is proposed that IANA should assign new URIs from the "IETF XML
Registry" [RFC3688] as follows: URI:
urn:ietf:params:xml:ns:yang:ietf-otn-tunnel Registrant Contact: The
IESG XML: N/A; the requested URI is an XML namespace. URI:
urn:ietf:params:xml:ns:yang:ietf-otn-types Registrant Contact: The
IESG XML: N/A; the requested URI is an XML namespace. This document
registers following YANG modules in the YANG Module Names registry
[RFC7950]. name: ietf-otn-tunnel namespace:
urn:ietf:params:xml:ns:yang:ietf-otn-tunnel prefix: otn-tunnel
reference: RFC XXXX name: ietf-otn-types namespace:
urn:ietf:params:xml:ns:yang:ietf-otn-types prefix: otn-types
reference: RFC XXXX
9. Acknowledgements 9. Acknowledgements
TBD. TBD.
10. Contributors 10. Contributors
Dieter Beller Dieter Beller
Nokia Nokia
Email: dieter.beller@nokia.com Email: dieter.beller@nokia.com
skipping to change at page 61, line 19 skipping to change at page 59, line 13
Email: oscar.gonzalezdedios@telefonica.com Email: oscar.gonzalezdedios@telefonica.com
11. References 11. References
11.1. Normative References 11.1. Normative References
[I-D.ietf-ccamp-otn-topo-yang] [I-D.ietf-ccamp-otn-topo-yang]
zhenghaomian@huawei.com, z., Guo, A., Busi, I., Sharma, zhenghaomian@huawei.com, z., Guo, A., Busi, I., Sharma,
A., Liu, X., Belotti, S., Xu, Y., Wang, L., and O. Dios, A., Liu, X., Belotti, S., Xu, Y., Wang, L., and O. Dios,
"A YANG Data Model for Optical Transport Network "A YANG Data Model for Optical Transport Network
Topology", draft-ietf-ccamp-otn-topo-yang-03 (work in Topology", draft-ietf-ccamp-otn-topo-yang-04 (work in
progress), June 2018. progress), July 2018.
[I-D.ietf-ccamp-transport-nbi-app-statement] [I-D.ietf-ccamp-transport-nbi-app-statement]
Busi, I., King, D., zhenghaomian@huawei.com, z., and Y. Busi, I., King, D., zhenghaomian@huawei.com, z., and Y.
Xu, "Transport Northbound Interface Applicability Xu, "Transport Northbound Interface Applicability
Statement", draft-ietf-ccamp-transport-nbi-app- Statement", draft-ietf-ccamp-transport-nbi-app-
statement-01 (work in progress), March 2018. statement-02 (work in progress), July 2018.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and
I. Bryskin, "A YANG Data Model for Traffic Engineering I. Bryskin, "A YANG Data Model for Traffic Engineering
Tunnels and Interfaces", draft-ietf-teas-yang-te-15 (work Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work
in progress), June 2018. in progress), July 2018.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012,
<https://www.rfc-editor.org/info/rfc6536>.
[RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D.,
and K. Pithewan, "GMPLS Signaling Extensions for Control and K. Pithewan, "GMPLS Signaling Extensions for Control
of Evolving G.709 Optical Transport Networks", RFC 7139, of Evolving G.709 Optical Transport Networks", RFC 7139,
DOI 10.17487/RFC7139, March 2014, DOI 10.17487/RFC7139, March 2014,
<https://www.rfc-editor.org/info/rfc7139>. <https://www.rfc-editor.org/info/rfc7139>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
11.2. Informative References 11.2. Informative References
[I-D.ietf-netmod-yang-tree-diagrams] [I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-06 (work in progress), ietf-netmod-yang-tree-diagrams-06 (work in progress),
February 2018. February 2018.
[I-D.ietf-teas-actn-yang] [I-D.ietf-teas-actn-yang]
Lee, Y., zhenghaomian@huawei.com, z., Ceccarelli, D., Lee, Y., zhenghaomian@huawei.com, z., Ceccarelli, D.,
Yoon, B., and S. Belotti, "Applicability of YANG models Yoon, B., and S. Belotti, "Applicability of YANG models
 End of changes. 91 change blocks. 
278 lines changed or deleted 199 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/