A YANG Data Model for requesting Path Computation in an Optical Transport Network (OTN)
draft-gbb-ccamp-otn-path-computation-yang-01
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
|
|
|---|---|---|---|
| Authors | Italo Busi , Aihua Guo , Sergio Belotti | ||
| Last updated | 2022-07-10 | ||
| Replaced by | draft-ietf-ccamp-otn-path-computation-yang | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-gbb-ccamp-otn-path-computation-yang-01
CCAMP Working Group I. Busi
Internet-Draft Huawei Technologies
Intended status: Standards Track A. Guo
Expires: 11 January 2023 Futurewei Technologies
S. Belotti
Nokia
10 July 2022
A YANG Data Model for requesting Path Computation in an Optical
Transport Network (OTN)
draft-gbb-ccamp-otn-path-computation-yang-01
Abstract
This document describes a YANG data model for a Remote Procedure
Calls (RPC) to request Path Computation in an Optical Transport
Network (OTN).
The YANG data models defined in this document conforms to the Network
Management Datastore Architecture (NMDA).
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). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on 11 January 2023.
Copyright Notice
Copyright (c) 2022 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 (https://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
Busi, et al. Expires 11 January 2023 [Page 1]
Internet-Draft YANG for OTN Path Computation July 2022
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology and Notations . . . . . . . . . . . . . . . . 3
1.2. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Prefix in Data Node Names . . . . . . . . . . . . . . . . 3
2. YANG Data Model for OTN Path Computation . . . . . . . . . . 4
2.1. YANG Model Overview . . . . . . . . . . . . . . . . . . . 4
2.2. Bandwidth Augmentation . . . . . . . . . . . . . . . . . 5
2.3. Label Augmentations . . . . . . . . . . . . . . . . . . . 5
3. OTN Path Computation Tree Diagram . . . . . . . . . . . . . . 5
4. YANG Model for OTN Path Computation . . . . . . . . . . . . . 10
5. Manageability Considerations . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . 17
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 18
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction
[I-D.ietf-teas-yang-path-computation] describes key use cases, where
a client needs to request underlying SDN controllers for path
computation. In some of these use cases, the underlying SDN
controller can control an Optical Transport Network (OTN).
This document defines a YANG data model, which augment the generic
Path Computation RPC defined in
[I-D.ietf-teas-yang-path-computation], with OTN technology-specific
augmentations required to request path computation to an underlying
OTN SDN controller. These models allow a client to delegate path
computation tasks to the underlying SDN controller without having to
obtain OTN detailed information from the controller and performing
feasible path computation itself.
The YANG data model defined in this document conforms to the Network
Management Datastore Architecture [RFC8342].
Busi, et al. Expires 11 January 2023 [Page 2]
Internet-Draft YANG for OTN Path Computation July 2022
1.1. Terminology and Notations
Refer to [I-D.ietf-ccamp-otn-topo-yang] and
[I-D.ietf-ccamp-layer1-types] for the OTN specific terms used in this
document.
The following terms are defined in [RFC7950] and are not redefined
here:
* client
* server
* augment
* data model
* data node
The following terms are defined in [RFC6241] and are not redefined
here:
* configuration data
* state data
The terminology for describing YANG data models is found in
[RFC7950].
1.2. Tree Diagram
A simplified graphical representation of the data model is used in
Section 3 of this document. The meaning of the symbols in these
diagrams is defined in [RFC8340].
1.3. Prefix in Data Node Names
In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1.
Busi, et al. Expires 11 January 2023 [Page 3]
Internet-Draft YANG for OTN Path Computation July 2022
+==========+===========================+===========+
| Prefix | YANG module | Reference |
+==========+===========================+===========+
| l1-types | ietf-layer1-types | [RFCYYYY] |
+----------+---------------------------+-----------+
| te | ietf-te | [RFCZZZZ] |
+----------+---------------------------+-----------+
| te-pc | ietf-te-path-computation | [RFCKKKK] |
+----------+---------------------------+-----------+
| otn-pc | ietf-otn-path-computation | RFCXXXX |
+----------+---------------------------+-----------+
Table 1: Prefixes and corresponding YANG modules
RFC Editor Note: Please replace XXXX with the RFC number assigned to
this document. Please replace YYYY with the RFC number assigned to
[I-D.ietf-ccamp-layer1-types]. Please replace ZZZZ with the RFC
number assigned to [I-D.ietf-teas-yang-te]. Please replace KKKK with
the RFC number assigned to [I-D.ietf-teas-yang-path-computation].
Please remove this note.
2. YANG Data Model for OTN Path Computation
2.1. YANG Model Overview
The YANG data model for requesting OTN path computation is defined as
an augmentation of the generic Path Computation RPC defined in
[I-D.ietf-teas-yang-path-computation], as shown in Figure 1.
+--------------------------+ o: augment
TE generic | ietf-te-path-computation |
+--------------------------+
o
|
|
|
+---------------------------+
OTN | ietf-otn-path-computation |
+---------------------------+
Figure 1: Relationship between OTN and TE path computation models
Busi, et al. Expires 11 January 2023 [Page 4]
Internet-Draft YANG for OTN Path Computation July 2022
The entities and Traffic Engineering (TE) attributes, such as
requested path and tunnel attributes, defined in
[I-D.ietf-teas-yang-path-computation], are still applicable when
requesting OTN path computation and the models defined in this
document only specifies the additional OTN technology-specific
attributes/information, using the attributes defined in
[I-D.ietf-ccamp-layer1-types].
The YANG module ietf-otn-path-computation defined in this document
conforms to the Network Management Datastore Architecture (NMDA)
defined in [RFC8342].
2.2. Bandwidth Augmentation
The OTN path computation model augments all the occurrences of the
te-bandwidth container with the OTN technology-specific attributes
using the otn-link-bandwidth and otn-path-bandwidth groupings defined
in [I-D.ietf-ccamp-layer1-types].
2.3. Label Augmentations
The OTN path computation model augments all the occurrences of the
label-restriction list with OTN technology-specific attributes using
the otn-label-range-info grouping defined in
[I-D.ietf-ccamp-layer1-types].
Moreover, the model augments all the occurrences of the te-label
container with the OTN technology-specific attributes using the otn-
label-start-end, otn-label-hop and otn-label-step groupings defined
in [I-D.ietf-ccamp-layer1-types].
3. OTN Path Computation Tree Diagram
Figure 2 below shows the tree diagram of the YANG data model defined
in module ietf-otn-path-computation.yang.
module: ietf-otn-path-computation
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:te-bandwidth/te-pc:technology:
+--:(otn)
+-- otn
+-- odu-type? identityref
+-- (oduflex-type)?
+--:(generic)
| +-- nominal-bit-rate
| l1-types:bandwidth-scientific-notation
+--:(cbr)
Busi, et al. Expires 11 January 2023 [Page 5]
Internet-Draft YANG for OTN Path Computation July 2022
| +-- cbr-client-type identityref
+--:(gfp-n-k)
| +-- gfp-n uint8
| +-- gfp-k? gfp-k
+--:(flexe-client)
| +-- flexe-client flexe-client-rate
+--:(flexe-aware)
| +-- flexe-aware-n uint16
+--:(packet)
+-- opuflex-payload-rate
l1-types:bandwidth-scientific-notation
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:tunnel-attributes/te-pc:te-bandwidth
/te-pc:technology:
+--:(otn)
+-- otn
+-- odu-type? identityref
+-- (oduflex-type)?
+--:(generic)
| +-- nominal-bit-rate
| l1-types:bandwidth-scientific-notation
+--:(cbr)
| +-- cbr-client-type identityref
+--:(gfp-n-k)
| +-- gfp-n uint8
| +-- gfp-k? gfp-k
+--:(flexe-client)
| +-- flexe-client flexe-client-rate
+--:(flexe-aware)
| +-- flexe-aware-n uint16
+--:(packet)
+-- opuflex-payload-rate
l1-types:bandwidth-scientific-notation
augment /te:tunnels-path-compute/te:output/te:path-compute-result
/te-pc:response/te-pc:computed-paths-properties
/te-pc:computed-path-properties/te-pc:path-properties
/te-pc:te-bandwidth/te-pc:technology:
+--:(otn)
+--ro otn
+--ro odu-type? identityref
+--ro (oduflex-type)?
+--:(generic)
| +--ro nominal-bit-rate
| l1-types:bandwidth-scientific-notation
+--:(cbr)
| +--ro cbr-client-type identityref
+--:(gfp-n-k)
| +--ro gfp-n uint8
Busi, et al. Expires 11 January 2023 [Page 6]
Internet-Draft YANG for OTN Path Computation July 2022
| +--ro gfp-k? gfp-k
+--:(flexe-client)
| +--ro flexe-client flexe-client-rate
+--:(flexe-aware)
| +--ro flexe-aware-n uint16
+--:(packet)
+--ro opuflex-payload-rate
l1-types:bandwidth-scientific-notation
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:path-in-segment
/te-pc:label-restrictions/te-pc:label-restriction:
+-- otn-label-range
+-- range-type? otn-label-range-type
+-- tsg? identityref
+-- odu-type-list* identityref
+-- priority? uint8
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:path-out-segment
/te-pc:label-restrictions/te-pc:label-restriction:
+-- otn-label-range
+-- range-type? otn-label-range-type
+-- tsg? identityref
+-- odu-type-list* identityref
+-- priority? uint8
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:optimizations/te-pc:algorithm
/te-pc:metric/te-pc:optimization-metric
/te-pc:explicit-route-exclude-objects
/te-pc:route-object-exclude-object/te-pc:type/te-pc:label
/te-pc:label-hop/te-pc:te-label/te-pc:technology:
+--:(otn)
+-- otn
+-- tpn? otn-tpn
+-- tsg? identityref
+-- ts-list? string
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:optimizations/te-pc:algorithm
/te-pc:metric/te-pc:optimization-metric
/te-pc:explicit-route-include-objects
/te-pc:route-object-include-object/te-pc:type/te-pc:label
/te-pc:label-hop/te-pc:te-label/te-pc:technology:
+--:(otn)
+-- otn
+-- tpn? otn-tpn
+-- tsg? identityref
+-- ts-list? string
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:explicit-route-objects-always
Busi, et al. Expires 11 January 2023 [Page 7]
Internet-Draft YANG for OTN Path Computation July 2022
/te-pc:route-object-exclude-always/te-pc:type/te-pc:label
/te-pc:label-hop/te-pc:te-label/te-pc:technology:
+--:(otn)
+-- otn
+-- tpn? otn-tpn
+-- tsg? identityref
+-- ts-list? string
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:explicit-route-objects-always
/te-pc:route-object-include-exclude/te-pc:type
/te-pc:label/te-pc:label-hop/te-pc:te-label
/te-pc:technology:
+--:(otn)
+-- otn
+-- tpn? otn-tpn
+-- tsg? identityref
+-- ts-list? string
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:path-in-segment
/te-pc:label-restrictions/te-pc:label-restriction
/te-pc:label-start/te-pc:te-label/te-pc:technology:
+--:(otn)
+-- otn
+-- (range-type)?
+--:(trib-port)
| +-- tpn? otn-tpn
+--:(trib-slot)
+-- ts? otn-ts
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:path-in-segment
/te-pc:label-restrictions/te-pc:label-restriction
/te-pc:label-end/te-pc:te-label/te-pc:technology:
+--:(otn)
+-- otn
+-- (range-type)?
+--:(trib-port)
| +-- tpn? otn-tpn
+--:(trib-slot)
+-- ts? otn-ts
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:path-in-segment
/te-pc:label-restrictions/te-pc:label-restriction
/te-pc:label-step/te-pc:technology:
+--:(otn)
+-- otn
+-- (range-type)?
+--:(trib-port)
| +-- tpn? otn-tpn
Busi, et al. Expires 11 January 2023 [Page 8]
Internet-Draft YANG for OTN Path Computation July 2022
+--:(trib-slot)
+-- ts? otn-ts
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:path-out-segment
/te-pc:label-restrictions/te-pc:label-restriction
/te-pc:label-start/te-pc:te-label/te-pc:technology:
+--:(otn)
+-- otn
+-- (range-type)?
+--:(trib-port)
| +-- tpn? otn-tpn
+--:(trib-slot)
+-- ts? otn-ts
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:path-out-segment
/te-pc:label-restrictions/te-pc:label-restriction
/te-pc:label-end/te-pc:te-label/te-pc:technology:
+--:(otn)
+-- otn
+-- (range-type)?
+--:(trib-port)
| +-- tpn? otn-tpn
+--:(trib-slot)
+-- ts? otn-ts
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:path-request/te-pc:path-out-segment
/te-pc:label-restrictions/te-pc:label-restriction
/te-pc:label-step/te-pc:technology:
+--:(otn)
+-- otn
+-- (range-type)?
+--:(trib-port)
| +-- tpn? otn-tpn
+--:(trib-slot)
+-- ts? otn-ts
augment /te:tunnels-path-compute/te:input/te:path-compute-info
/te-pc:synchronization/te-pc:exclude-objects
/te-pc:excludes/te-pc:type/te-pc:label/te-pc:label-hop
/te-pc:te-label/te-pc:technology:
+--:(otn)
+-- otn
+-- tpn? otn-tpn
+-- tsg? identityref
+-- ts-list? string
augment /te:tunnels-path-compute/te:output/te:path-compute-result
/te-pc:response/te-pc:computed-paths-properties
/te-pc:computed-path-properties/te-pc:path-properties
/te-pc:path-route-objects/te-pc:path-route-object
Busi, et al. Expires 11 January 2023 [Page 9]
Internet-Draft YANG for OTN Path Computation July 2022
/te-pc:type/te-pc:label/te-pc:label-hop/te-pc:te-label
/te-pc:technology:
+--:(otn)
+--ro otn
+--ro tpn? otn-tpn
+--ro tsg? identityref
+--ro ts-list? string
Figure 2: OTN path computation tree diagram
4. YANG Model for OTN Path Computation
<CODE BEGINS> file "ietf-otn-path-computation@2022-07-10.yang"
module ietf-otn-path-computation {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-otn-path-computation";
prefix "otn-pc";
import ietf-te-path-computation {
prefix "te-pc";
revision-date "2021-09-06";
reference
"I-D.ietf-teas-yang-path-computation-14: Yang model
for requesting Path Computation.";
}
import ietf-te {
prefix "te";
revision-date "2021-02-20";
reference
"I-D.ietf-teas-yang-te-19: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces. ";
}
import ietf-layer1-types {
prefix "l1-types";
reference
"I-D.ietf-ccamp-layer1-types:
A YANG Data Model for Layer 1 Types. ";
}
organization
"IETF CCAMP Working Group";
contact
"WG Web: <https://datatracker.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org>
Editor: Aihua Guo
Busi, et al. Expires 11 January 2023 [Page 10]
Internet-Draft YANG for OTN Path Computation July 2022
<mailto:aihuaguo.ietf@gmail.com>
Editor: Italo Busi
<mailto:italo.busi@huawei.com>
Editor: Sergio Belotti
<mailto:sergio.belotti@nokia.com>";
description
"This module defines a model for requesting
OTN Path Computation.
The model fully conforms to the Network Management
Datastore Architecture (NMDA).
Copyright (c) 2022 IETF Trust and the persons
identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Revised BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision "2022-07-10" {
description
"Initial version.";
reference
"RFC XXXX: YANG Model for OTN and Optical Path Computation";
// RFC Ed.: replace XXXX with actual RFC number, update date
// information and remove this note
}
/*
* Data nodes
*/
/*
* Augment TE bandwidth
*/
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:te-bandwidth/te-pc:technology" {
description
Busi, et al. Expires 11 January 2023 [Page 11]
Internet-Draft YANG for OTN Path Computation July 2022
"Augment TE bandwidth of the requested path.";
case otn {
uses l1-types:otn-path-bandwidth;
}
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:tunnel-attributes/te-pc:te-bandwidth/"
+ "te-pc:technology" {
description
"Augment TE bandwidth of the requested tunnel attributes.";
case otn {
uses l1-types:otn-path-bandwidth;
}
}
augment "/te:tunnels-path-compute/te:output/"
+ "te:path-compute-result/te-pc:response/"
+ "te-pc:computed-paths-properties/"
+ "te-pc:computed-path-properties/te-pc:path-properties/"
+ "te-pc:te-bandwidth/te-pc:technology" {
description
"Augment TE bandwidth of the computed path properties.";
case otn {
uses l1-types:otn-path-bandwidth;
}
}
/*
* Augment TE label range information
*/
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:path-in-segment/"
+ "te-pc:label-restrictions/te-pc:label-restriction" {
description
"Augment TE label range information for the ingress segment
of the requested path.";
uses l1-types:otn-label-range-info;
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:path-out-segment/"
+ "te-pc:label-restrictions/te-pc:label-restriction" {
description
"Augment TE label range information for the egress segment
of the requested path.";
uses l1-types:otn-label-range-info;
Busi, et al. Expires 11 January 2023 [Page 12]
Internet-Draft YANG for OTN Path Computation July 2022
}
/*
* Augment TE label.
*/
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:optimizations/te-pc:algorithm/"
+ "te-pc:metric/te-pc:optimization-metric/"
+ "te-pc:explicit-route-exclude-objects/"
+ "te-pc:route-object-exclude-object/te-pc:type/te-pc:label/"
+ "te-pc:label-hop/te-pc:te-label/te-pc:technology" {
description
"Augment TE label hop for the optimization of the explicit
route objects excluded by the path computation of the requested
path.";
case otn {
uses l1-types:otn-label-hop;
}
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:optimizations/te-pc:algorithm/"
+ "te-pc:metric/te-pc:optimization-metric/"
+ "te-pc:explicit-route-include-objects/"
+ "te-pc:route-object-include-object/te-pc:type/te-pc:label/"
+ "te-pc:label-hop/te-pc:te-label/te-pc:technology" {
description
"Augment TE label hop for the optimization of the explicit
route objects included by the path computation of the requested
path.";
case otn {
uses l1-types:otn-label-hop;
}
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:explicit-route-objects-always/"
+ "te-pc:route-object-exclude-always/te-pc:type/te-pc:label/"
+ "te-pc:label-hop/te-pc:te-label/te-pc:technology" {
description
"Augment TE label hop for the explicit route objects always
excluded by the path computation of the requested path.";
case otn {
uses l1-types:otn-label-hop;
}
}
Busi, et al. Expires 11 January 2023 [Page 13]
Internet-Draft YANG for OTN Path Computation July 2022
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:explicit-route-objects-always/"
+ "te-pc:route-object-include-exclude/te-pc:type/"
+ "te-pc:label/te-pc:label-hop/te-pc:te-label/"
+ "te-pc:technology" {
description
"Augment TE label hop for the explicit route objects included
or excluded by the path computation of the requested path.";
case otn {
uses l1-types:otn-label-hop;
}
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:path-in-segment/"
+ "te-pc:label-restrictions/te-pc:label-restriction/"
+ "te-pc:label-start/te-pc:te-label/te-pc:technology" {
description
"Augment TE label range start for the ingress segment
of the requested path.";
case otn {
uses l1-types:otn-label-start-end;
}
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:path-in-segment/"
+ "te-pc:label-restrictions/te-pc:label-restriction/"
+ "te-pc:label-end/te-pc:te-label/te-pc:technology" {
description
"Augment TE label range end for the ingress segment
of the requested path.";
case otn {
uses l1-types:otn-label-start-end;
}
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:path-in-segment/"
+ "te-pc:label-restrictions/te-pc:label-restriction/"
+ "te-pc:label-step/te-pc:technology" {
description
"Augment TE label range step for the ingress segment
of the requested path.";
case otn {
uses l1-types:otn-label-step;
}
}
Busi, et al. Expires 11 January 2023 [Page 14]
Internet-Draft YANG for OTN Path Computation July 2022
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:path-out-segment/"
+ "te-pc:label-restrictions/te-pc:label-restriction/"
+ "te-pc:label-start/te-pc:te-label/te-pc:technology" {
description
"Augment TE label range start for the egress segment
of the requested path.";
case otn {
uses l1-types:otn-label-start-end;
}
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:path-out-segment/"
+ "te-pc:label-restrictions/te-pc:label-restriction/"
+ "te-pc:label-end/te-pc:te-label/te-pc:technology" {
description
"Augment TE label range end for the egress segment
of the requested path.";
case otn {
uses l1-types:otn-label-start-end;
}
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:path-request/te-pc:path-out-segment/"
+ "te-pc:label-restrictions/te-pc:label-restriction/"
+ "te-pc:label-step/te-pc:technology" {
description
"Augment TE label range end for the egress segment
of the requested path.";
case otn {
uses l1-types:otn-label-step;
}
}
augment "/te:tunnels-path-compute/te:input/te:path-compute-info/"
+ "te-pc:synchronization/te-pc:exclude-objects/"
+ "te-pc:excludes/te-pc:type/te-pc:label/te-pc:label-hop/"
+ "te-pc:te-label/te-pc:technology" {
description
"Augment TE label hop for the explicit route objects to always
exclude from synchronized path computation.";
case otn {
uses l1-types:otn-label-hop;
}
}
Busi, et al. Expires 11 January 2023 [Page 15]
Internet-Draft YANG for OTN Path Computation July 2022
augment "/te:tunnels-path-compute/te:output/"
+ "te:path-compute-result/te-pc:response/"
+ "te-pc:computed-paths-properties/"
+ "te-pc:computed-path-properties/te-pc:path-properties/"
+ "te-pc:path-route-objects/te-pc:path-route-object/"
+ "te-pc:type/te-pc:label/"
+ "te-pc:label-hop/te-pc:te-label/te-pc:technology" {
description
"Augment TE label hop for the route object of the computed
path.";
case otn {
uses l1-types:otn-label-hop;
}
}
}
<CODE ENDS>
Figure 3: OTN path computation YANG module
5. Manageability Considerations
TBD.
6. Security Considerations
<Add any security considerations>
7. IANA Considerations
This document registers the following URIs in the "ns" subregistry
within the "IETF XML registry" [RFC3688].
URI: urn:ietf:params:xml:ns:yang:ietf-otn-path-computation
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
This document registers the following YANG module in the "YANG Module
Names" registry [RFC7950].
name: ietf-otn-path-computation
namespace: urn:ietf:params:xml:ns:yang:ietf-otn-path-computation
prefix: otn-pc
reference: this document
8. References
8.1. Normative References
Busi, et al. Expires 11 January 2023 [Page 16]
Internet-Draft YANG for OTN Path Computation July 2022
[I-D.ietf-ccamp-layer1-types]
Zheng, H. and I. Busi, "A YANG Data Model for Layer 1
Types", Work in Progress, Internet-Draft, draft-ietf-
ccamp-layer1-types-13, 8 April 2022,
<https://www.ietf.org/archive/id/draft-ietf-ccamp-layer1-
types-13.txt>.
[I-D.ietf-teas-yang-path-computation]
Busi, I., Belotti, S., Dios, O. G. D., Sharma, A., and D.
Ceccarelli, "A YANG Data Model for requesting path
computation", Work in Progress, Internet-Draft, draft-
ietf-teas-yang-path-computation-18, 22 March 2022,
<https://www.ietf.org/archive/id/draft-ietf-teas-yang-
path-computation-18.txt>.
[I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V. P., Bryskin, I.,
and O. G. D. Dios, "A YANG Data Model for Traffic
Engineering Tunnels, Label Switched Paths and Interfaces",
Work in Progress, Internet-Draft, draft-ietf-teas-yang-te-
29, 7 February 2022, <https://www.ietf.org/archive/id/
draft-ietf-teas-yang-te-29.txt>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
[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>.
8.2. Informative References
Busi, et al. Expires 11 January 2023 [Page 17]
Internet-Draft YANG for OTN Path Computation July 2022
[I-D.ietf-ccamp-otn-topo-yang]
Zheng, H., Busi, I., Liu, X., Belotti, S., and O. G. D.
Dios, "A YANG Data Model for Optical Transport Network
Topology", Work in Progress, Internet-Draft, draft-ietf-
ccamp-otn-topo-yang-14, 7 March 2022,
<https://www.ietf.org/archive/id/draft-ietf-ccamp-otn-
topo-yang-14.txt>.
[I-D.ietf-teas-actn-poi-applicability]
Peruzzini, F., Bouquier, J., Busi, I., King, D., and D.
Ceccarelli, "Applicability of Abstraction and Control of
Traffic Engineered Networks (ACTN) to Packet Optical
Integration (POI)", Work in Progress, Internet-Draft,
draft-ietf-teas-actn-poi-applicability-07, 10 July 2022,
<https://www.ietf.org/archive/id/draft-ietf-teas-actn-poi-
applicability-07.txt>.
Acknowledgments
The authors of this document would like to thank the authors of
[I-D.ietf-teas-actn-poi-applicability] for having identified the gap
and requirements to trigger this work.
This document was prepared using kramdown.
Contributors
Daniel King
Old Dog Consulting
Email: daniel@olddog.co.uk
Authors' Addresses
Italo Busi
Huawei Technologies
Email: italo.busi@huawei.com
Aihua Guo
Futurewei Technologies
Email: aihuaguo.ietf@gmail.com
Sergio Belotti
Nokia
Email: sergio.belotti@nokia.com
Busi, et al. Expires 11 January 2023 [Page 18]