-
Notifications
You must be signed in to change notification settings - Fork 0
/
ietf-otn-path-computation.yang
292 lines (258 loc) · 9.31 KB
/
ietf-otn-path-computation.yang
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
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:[email protected]>
Editor: Aihua Guo
<mailto:[email protected]>
Editor: Italo Busi
<mailto:[email protected]>
Editor: Sergio Belotti
<mailto:[email protected]>";
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-09-12" {
description
"Initial version.";
reference
"RFC XXXX: A YANG Data Model for requesting Path Computation
in an Optical Transport Network (OTN)";
// 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
"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;
}
/*
* 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;
}
}
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;
}
}
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;
}
}
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;
}
}
}