1 module ietf-te-packet-types {
3 namespace "urn:ietf:params:xml:ns:yang:ietf-te-packet-types";
4 prefix te-packet-types;
6 /* Import TE generic types */
11 "RFC 8776: Common YANG Data Types for Traffic Engineering";
15 "IETF Traffic Engineering Architecture and Signaling (TEAS)
18 "WG Web: <https://datatracker.ietf.org/wg/teas/>
19 WG List: <mailto:teas@ietf.org>
22 <mailto:tsaad@juniper.net>
25 <mailto:rgandhi@cisco.com>
27 Editor: Vishnu Pavan Beeram
28 <mailto:vbeeram@juniper.net>
31 <mailto:xufeng.liu.ietf@gmail.com>
34 <mailto:i_bryskin@yahoo.com>";
36 "This YANG module contains a collection of generally useful YANG
37 data type definitions specific to MPLS TE. The model fully
38 conforms to the Network Management Datastore Architecture
41 Copyright (c) 2020 IETF Trust and the persons identified as
42 authors of the code. All rights reserved.
44 Redistribution and use in source and binary forms, with or
45 without modification, is permitted pursuant to, and subject to
46 the license terms contained in, the Simplified BSD License set
47 forth in Section 4.c of the IETF Trust's Legal Provisions
48 Relating to IETF Documents
49 (https://trustee.ietf.org/license-info).
51 This version of this YANG module is part of RFC 8776; see the
52 RFC itself for full legal notices.";
56 "Latest revision of TE MPLS types.";
58 "RFC 8776: Common YANG Data Types for Traffic Engineering";
65 typedef te-bandwidth-requested-type {
69 "Bandwidth is explicitly specified.";
73 "Bandwidth is automatically computed.";
77 "Enumerated type for specifying whether bandwidth is
78 explicitly specified or automatically computed.";
81 typedef te-class-type {
84 "Diffserv-TE Class-Type. Defines a set of Traffic Trunks
85 crossing a link that is governed by a specific set of
86 bandwidth constraints. Class-Type is used for the purposes
87 of link bandwidth allocation, constraint-based routing, and
90 "RFC 4124: Protocol Extensions for Support of Diffserv-aware
91 MPLS Traffic Engineering";
99 "Diffserv-TE bandwidth constraints as defined in RFC 4124.";
101 "RFC 4124: Protocol Extensions for Support of Diffserv-aware
102 MPLS Traffic Engineering";
105 typedef bandwidth-kbps {
109 "Bandwidth values, expressed in kilobits per second.";
112 typedef bandwidth-mbps {
116 "Bandwidth values, expressed in megabits per second.";
119 typedef bandwidth-gbps {
123 "Bandwidth values, expressed in gigabits per second.";
126 identity backup-protection-type {
128 "Base identity for the backup protection type.";
131 identity backup-protection-link {
132 base backup-protection-type;
134 "Backup provides link protection only.";
137 identity backup-protection-node-link {
138 base backup-protection-type;
140 "Backup offers node (preferred) or link protection.";
143 identity bc-model-type {
145 "Base identity for the Diffserv-TE Bandwidth Constraints
148 "RFC 4124: Protocol Extensions for Support of Diffserv-aware
149 MPLS Traffic Engineering";
152 identity bc-model-rdm {
155 "Russian Dolls Bandwidth Constraints Model type.";
157 "RFC 4127: Russian Dolls Bandwidth Constraints Model for
158 Diffserv-aware MPLS Traffic Engineering";
161 identity bc-model-mam {
164 "Maximum Allocation Bandwidth Constraints Model type.";
166 "RFC 4125: Maximum Allocation Bandwidth Constraints Model for
167 Diffserv-aware MPLS Traffic Engineering";
170 identity bc-model-mar {
173 "Maximum Allocation with Reservation Bandwidth Constraints
176 "RFC 4126: Max Allocation with Reservation Bandwidth
177 Constraints Model for Diffserv-aware MPLS Traffic Engineering
178 & Performance Comparisons";
181 grouping performance-metrics-attributes-packet {
183 "Contains PM attributes.";
184 uses te-types:performance-metrics-attributes {
185 augment "performance-metrics-one-way" {
186 leaf one-way-min-delay {
191 "One-way minimum delay or latency in microseconds.";
193 leaf one-way-min-delay-normality {
194 type te-types:performance-metrics-normality;
197 "One-way minimum delay or latency normality.";
199 leaf one-way-max-delay {
204 "One-way maximum delay or latency in microseconds.";
206 leaf one-way-max-delay-normality {
207 type te-types:performance-metrics-normality;
210 "One-way maximum delay or latency normality.";
212 leaf one-way-delay-variation {
217 "One-way delay variation in microseconds.";
219 "RFC 5481: Packet Delay Variation Applicability
220 Statement, Section 4.2";
222 leaf one-way-delay-variation-normality {
223 type te-types:performance-metrics-normality;
226 "One-way delay variation normality.";
228 "RFC 7471: OSPF Traffic Engineering (TE) Metric
230 RFC 7823: Performance-Based Path Selection for
231 Explicitly Routed Label Switched Paths (LSPs) Using
233 RFC 8570: IS-IS Traffic Engineering (TE) Metric
236 leaf one-way-packet-loss {
239 range "0..50.331642";
242 "One-way packet loss as a percentage of the total traffic
243 sent over a configurable interval. The finest precision
244 is 0.000003%, where the maximum is 50.331642%.";
246 "RFC 8570: IS-IS Traffic Engineering (TE) Metric
247 Extensions, Section 4.4";
249 leaf one-way-packet-loss-normality {
250 type te-types:performance-metrics-normality;
253 "Packet loss normality.";
255 "RFC 7471: OSPF Traffic Engineering (TE) Metric
257 RFC 7823: Performance-Based Path Selection for
258 Explicitly Routed Label Switched Paths (LSPs) Using
260 RFC 8570: IS-IS Traffic Engineering (TE) Metric
264 "PM one-way packet-specific augmentation for a generic PM
267 augment "performance-metrics-two-way" {
268 leaf two-way-min-delay {
274 "Two-way minimum delay or latency in microseconds.";
276 leaf two-way-min-delay-normality {
277 type te-types:performance-metrics-normality;
280 "Two-way minimum delay or latency normality.";
282 "RFC 7471: OSPF Traffic Engineering (TE) Metric
284 RFC 7823: Performance-Based Path Selection for
285 Explicitly Routed Label Switched Paths (LSPs) Using
287 RFC 8570: IS-IS Traffic Engineering (TE) Metric
290 leaf two-way-max-delay {
296 "Two-way maximum delay or latency in microseconds.";
298 leaf two-way-max-delay-normality {
299 type te-types:performance-metrics-normality;
302 "Two-way maximum delay or latency normality.";
304 "RFC 7471: OSPF Traffic Engineering (TE) Metric
306 RFC 7823: Performance-Based Path Selection for
307 Explicitly Routed Label Switched Paths (LSPs) Using
309 RFC 8570: IS-IS Traffic Engineering (TE) Metric
312 leaf two-way-delay-variation {
318 "Two-way delay variation in microseconds.";
320 "RFC 5481: Packet Delay Variation Applicability
321 Statement, Section 4.2";
323 leaf two-way-delay-variation-normality {
324 type te-types:performance-metrics-normality;
327 "Two-way delay variation normality.";
329 "RFC 7471: OSPF Traffic Engineering (TE) Metric
331 RFC 7823: Performance-Based Path Selection for
332 Explicitly Routed Label Switched Paths (LSPs) Using
334 RFC 8570: IS-IS Traffic Engineering (TE) Metric
337 leaf two-way-packet-loss {
340 range "0..50.331642";
344 "Two-way packet loss as a percentage of the total traffic
345 sent over a configurable interval. The finest precision
348 leaf two-way-packet-loss-normality {
349 type te-types:performance-metrics-normality;
352 "Two-way packet loss normality.";
355 "PM two-way packet-specific augmentation for a generic PM
358 "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
359 RFC 7823: Performance-Based Path Selection for
360 Explicitly Routed Label Switched Paths (LSPs) Using
362 RFC 8570: IS-IS Traffic Engineering (TE) Metric
368 grouping one-way-performance-metrics-packet {
370 "One-way packet PM throttle grouping.";
371 leaf one-way-min-delay {
377 "One-way minimum delay or latency in microseconds.";
379 leaf one-way-max-delay {
385 "One-way maximum delay or latency in microseconds.";
387 leaf one-way-delay-variation {
393 "One-way delay variation in microseconds.";
395 leaf one-way-packet-loss {
398 range "0..50.331642";
402 "One-way packet loss as a percentage of the total traffic
403 sent over a configurable interval. The finest precision is
408 grouping two-way-performance-metrics-packet {
410 "Two-way packet PM throttle grouping.";
411 leaf two-way-min-delay {
417 "Two-way minimum delay or latency in microseconds.";
419 leaf two-way-max-delay {
425 "Two-way maximum delay or latency in microseconds.";
427 leaf two-way-delay-variation {
433 "Two-way delay variation in microseconds.";
435 leaf two-way-packet-loss {
438 range "0..50.331642";
442 "Two-way packet loss as a percentage of the total traffic
443 sent over a configurable interval. The finest precision is
448 grouping performance-metrics-throttle-container-packet {
450 "Packet PM threshold grouping.";
451 uses te-types:performance-metrics-throttle-container {
452 augment "throttle/threshold-out" {
453 uses one-way-performance-metrics-packet;
454 uses two-way-performance-metrics-packet;
456 "PM threshold-out packet augmentation for a
459 augment "throttle/threshold-in" {
460 uses one-way-performance-metrics-packet;
461 uses two-way-performance-metrics-packet;
463 "PM threshold-in packet augmentation for a
466 augment "throttle/threshold-accelerated-advertisement" {
467 uses one-way-performance-metrics-packet;
468 uses two-way-performance-metrics-packet;
470 "PM accelerated advertisement packet augmentation for a