diff --git a/drafts/te-types-update/diffs/te-pkt-types/model-diff-spaces.txt b/drafts/te-types-update/diffs/te-pkt-types/model-diff-spaces.txt index 52b68aa..81972b6 100644 --- a/drafts/te-types-update/diffs/te-pkt-types/model-diff-spaces.txt +++ b/drafts/te-types-update/diffs/te-pkt-types/model-diff-spaces.txt @@ -33,31 +33,33 @@ < the license terms contained in, the Simplified BSD License set --- > the license terms contained in, the Revised BSD License set - 51,52c61,80 + 51,52c61,82 < This version of this YANG module is part of RFC 8776; see the < RFC itself for full legal notices."; --- > This version of this YANG module is part of RFC XXXX > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself > for full legal notices."; - > revision 2024-01-25 { + > revision 2024-02-16 { > description - > "Added common TE packet identities: + > "This revision adds the following new identities: > - bandwidth-profile-type; - > - path-metric-loss; - > - path-metric-delay-variation. + > - link-metric-delay-variation; + > - link-metric-loss; + > - path-metric-delay-variation; + > - path-metric-loss. > - > Added common TE packet groupings: + > This revision adds the following new groupings: > - te-packet-path-bandwidth; > - te-packet-link-bandwidth. > - > Updated module description."; + > This revision provides also few editorial changes."; > reference > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; > } > // RFC Editor: replace XXXX with actual RFC number, update date > // information and remove this note - 61c89,187 + 61c91,196 < /** --- > /* @@ -106,65 +108,72 @@ > Marker with Efficient Handling of in-Profile Traffic"; > } > - > // CHANGE NOTE: The identity path-metric-loss below has - > // been added in this module revision - > // RFC Editor: remove the note above and this note - > identity path-metric-loss { - > base te-types:path-metric-type; - > description - > "The path loss (as a packet percentage) metric type - > encodes a function of the unidirectional loss metrics of all - > links traversed by a P2P path. - > - > The basic unit is 0.000003%, - > where (2^24 - 2) or 50.331642% is the maximum value of the - > path loss percentage that can be expressed. - > - > Values that are larger than the maximum value SHOULD be - > encoded as the maximum value."; - > reference - > "RFC8233: Extensions to the Path Computation Element - > Communication Protocol (PCEP) to Compute Service-Aware Label - > Switched Paths (LSPs); + > // CHANGE NOTE: The identity link-metric-delay-variation + > // below has been added in this module revision + > // RFC Editor: remove the note above and this note + > identity link-metric-delay-variation { + > base te-types:link-metric-type; + > description + > "The Unidirectional Delay Variation Metric, + > measured in units of microseconds."; + > reference + > "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + > section 4.3 > - > RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; + > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + > section 4.3"; + > } > - > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - > } + > // CHANGE NOTE: The identity link-metric-loss below has + > // been added in this module revision + > // RFC Editor: remove the note above and this note + > identity link-metric-loss { + > base te-types:link-metric-type; + > description + > "The Unidirectional Link Loss Metric, + > measured in units of 0.000003%."; + > reference + > "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + > section 4.4 > - > // CHANGE NOTE: The identity path-metric-delay-variation below has - > // been added in this module revision - > // RFC Editor: remove the note above and this note - > identity path-metric-delay-variation { - > base te-types:path-metric-type; - > description - > "The path delay variation encodes the sum of the unidirectional - > delay variation metrics of all links traversed by a P2P path. - > - > The path delay variation metric unit is in microseconds, where - > (2^24 - 1) or 16,777,215 microseconds (16.777215 sec) is the - > maximum value of the path delay variation that can be - > expressed. - > - > Values that are larger than the maximum value SHOULD be - > encoded as the maximum value."; - > reference - > "RFC8233: Extensions to the Path Computation Element - > Communication Protocol (PCEP) to Compute Service-Aware Label - > Switched Paths (LSPs); + > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + > section 4.4"; + > } > - > RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; + > // CHANGE NOTE: The identity path-metric-delay-variation + > // below has been added in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-delay-variation { + > base te-types:path-metric-type; + > description + > "The Path Delay Variation Metric, + > measured in units of microseconds."; + > reference + > "RFC8233: Extensions to the Path Computation Element + > Communication Protocol (PCEP) to Compute Service-Aware Label + > Switched Paths (LSPs), section 3.1.2"; + > } > - > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - > } + > // CHANGE NOTE: The identity path-metric-loss below has + > // been added in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-loss { + > base te-types:path-metric-type; + > description + > "The Path Loss Metric, measured in units of 0.000003%."; + > reference + > "RFC8233: Extensions to the Path Computation Element + > Communication Protocol (PCEP) to Compute Service-Aware Label + > Switched Paths (LSPs), section 3.1.3"; + > } > > /* - 180a307,310 + 180a316,319 > /* > * Groupings > */ > - 472a603,672 + 472a612,681 > } > } > diff --git a/drafts/te-types-update/diffs/te-pkt-types/model-diff.txt b/drafts/te-types-update/diffs/te-pkt-types/model-diff.txt index fe0b68b..3b1bd4a 100644 --- a/drafts/te-types-update/diffs/te-pkt-types/model-diff.txt +++ b/drafts/te-types-update/diffs/te-pkt-types/model-diff.txt @@ -33,31 +33,33 @@ < the license terms contained in, the Simplified BSD License set --- > the license terms contained in, the Revised BSD License set -51,52c61,80 +51,52c61,82 < This version of this YANG module is part of RFC 8776; see the < RFC itself for full legal notices."; --- > This version of this YANG module is part of RFC XXXX > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself > for full legal notices."; -> revision 2024-01-25 { +> revision 2024-02-16 { > description -> "Added common TE packet identities: +> "This revision adds the following new identities: > - bandwidth-profile-type; -> - path-metric-loss; -> - path-metric-delay-variation. +> - link-metric-delay-variation; +> - link-metric-loss; +> - path-metric-delay-variation; +> - path-metric-loss. > -> Added common TE packet groupings: +> This revision adds the following new groupings: > - te-packet-path-bandwidth; > - te-packet-link-bandwidth. > -> Updated module description."; +> This revision provides also few editorial changes."; > reference > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; > } > // RFC Editor: replace XXXX with actual RFC number, update date > // information and remove this note -61c89,187 +61c91,196 < /** --- > /* @@ -106,65 +108,72 @@ > Marker with Efficient Handling of in-Profile Traffic"; > } > -> // CHANGE NOTE: The identity path-metric-loss below has -> // been added in this module revision -> // RFC Editor: remove the note above and this note -> identity path-metric-loss { -> base te-types:path-metric-type; -> description -> "The path loss (as a packet percentage) metric type -> encodes a function of the unidirectional loss metrics of all -> links traversed by a P2P path. -> -> The basic unit is 0.000003%, -> where (2^24 - 2) or 50.331642% is the maximum value of the -> path loss percentage that can be expressed. -> -> Values that are larger than the maximum value SHOULD be -> encoded as the maximum value."; -> reference -> "RFC8233: Extensions to the Path Computation Element -> Communication Protocol (PCEP) to Compute Service-Aware Label -> Switched Paths (LSPs); +> // CHANGE NOTE: The identity link-metric-delay-variation +> // below has been added in this module revision +> // RFC Editor: remove the note above and this note +> identity link-metric-delay-variation { +> base te-types:link-metric-type; +> description +> "The Unidirectional Delay Variation Metric, +> measured in units of microseconds."; +> reference +> "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, +> section 4.3 > -> RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; +> RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, +> section 4.3"; +> } > -> RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; -> } +> // CHANGE NOTE: The identity link-metric-loss below has +> // been added in this module revision +> // RFC Editor: remove the note above and this note +> identity link-metric-loss { +> base te-types:link-metric-type; +> description +> "The Unidirectional Link Loss Metric, +> measured in units of 0.000003%."; +> reference +> "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, +> section 4.4 > -> // CHANGE NOTE: The identity path-metric-delay-variation below has -> // been added in this module revision -> // RFC Editor: remove the note above and this note -> identity path-metric-delay-variation { -> base te-types:path-metric-type; -> description -> "The path delay variation encodes the sum of the unidirectional -> delay variation metrics of all links traversed by a P2P path. -> -> The path delay variation metric unit is in microseconds, where -> (2^24 - 1) or 16,777,215 microseconds (16.777215 sec) is the -> maximum value of the path delay variation that can be -> expressed. -> -> Values that are larger than the maximum value SHOULD be -> encoded as the maximum value."; -> reference -> "RFC8233: Extensions to the Path Computation Element -> Communication Protocol (PCEP) to Compute Service-Aware Label -> Switched Paths (LSPs); +> RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, +> section 4.4"; +> } > -> RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; +> // CHANGE NOTE: The identity path-metric-delay-variation +> // below has been added in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-delay-variation { +> base te-types:path-metric-type; +> description +> "The Path Delay Variation Metric, +> measured in units of microseconds."; +> reference +> "RFC8233: Extensions to the Path Computation Element +> Communication Protocol (PCEP) to Compute Service-Aware Label +> Switched Paths (LSPs), section 3.1.2"; +> } > -> RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; -> } +> // CHANGE NOTE: The identity path-metric-loss below has +> // been added in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-loss { +> base te-types:path-metric-type; +> description +> "The Path Loss Metric, measured in units of 0.000003%."; +> reference +> "RFC8233: Extensions to the Path Computation Element +> Communication Protocol (PCEP) to Compute Service-Aware Label +> Switched Paths (LSPs), section 3.1.3"; +> } > > /* -180a307,310 +180a316,319 > /* > * Groupings > */ > -472a603,672 +472a612,681 > } > } > diff --git a/drafts/te-types-update/diffs/te-pkt-types/model-updates.txt b/drafts/te-types-update/diffs/te-pkt-types/model-updates.txt index 52b68aa..81972b6 100644 --- a/drafts/te-types-update/diffs/te-pkt-types/model-updates.txt +++ b/drafts/te-types-update/diffs/te-pkt-types/model-updates.txt @@ -33,31 +33,33 @@ < the license terms contained in, the Simplified BSD License set --- > the license terms contained in, the Revised BSD License set - 51,52c61,80 + 51,52c61,82 < This version of this YANG module is part of RFC 8776; see the < RFC itself for full legal notices."; --- > This version of this YANG module is part of RFC XXXX > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself > for full legal notices."; - > revision 2024-01-25 { + > revision 2024-02-16 { > description - > "Added common TE packet identities: + > "This revision adds the following new identities: > - bandwidth-profile-type; - > - path-metric-loss; - > - path-metric-delay-variation. + > - link-metric-delay-variation; + > - link-metric-loss; + > - path-metric-delay-variation; + > - path-metric-loss. > - > Added common TE packet groupings: + > This revision adds the following new groupings: > - te-packet-path-bandwidth; > - te-packet-link-bandwidth. > - > Updated module description."; + > This revision provides also few editorial changes."; > reference > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; > } > // RFC Editor: replace XXXX with actual RFC number, update date > // information and remove this note - 61c89,187 + 61c91,196 < /** --- > /* @@ -106,65 +108,72 @@ > Marker with Efficient Handling of in-Profile Traffic"; > } > - > // CHANGE NOTE: The identity path-metric-loss below has - > // been added in this module revision - > // RFC Editor: remove the note above and this note - > identity path-metric-loss { - > base te-types:path-metric-type; - > description - > "The path loss (as a packet percentage) metric type - > encodes a function of the unidirectional loss metrics of all - > links traversed by a P2P path. - > - > The basic unit is 0.000003%, - > where (2^24 - 2) or 50.331642% is the maximum value of the - > path loss percentage that can be expressed. - > - > Values that are larger than the maximum value SHOULD be - > encoded as the maximum value."; - > reference - > "RFC8233: Extensions to the Path Computation Element - > Communication Protocol (PCEP) to Compute Service-Aware Label - > Switched Paths (LSPs); + > // CHANGE NOTE: The identity link-metric-delay-variation + > // below has been added in this module revision + > // RFC Editor: remove the note above and this note + > identity link-metric-delay-variation { + > base te-types:link-metric-type; + > description + > "The Unidirectional Delay Variation Metric, + > measured in units of microseconds."; + > reference + > "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + > section 4.3 > - > RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; + > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + > section 4.3"; + > } > - > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - > } + > // CHANGE NOTE: The identity link-metric-loss below has + > // been added in this module revision + > // RFC Editor: remove the note above and this note + > identity link-metric-loss { + > base te-types:link-metric-type; + > description + > "The Unidirectional Link Loss Metric, + > measured in units of 0.000003%."; + > reference + > "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + > section 4.4 > - > // CHANGE NOTE: The identity path-metric-delay-variation below has - > // been added in this module revision - > // RFC Editor: remove the note above and this note - > identity path-metric-delay-variation { - > base te-types:path-metric-type; - > description - > "The path delay variation encodes the sum of the unidirectional - > delay variation metrics of all links traversed by a P2P path. - > - > The path delay variation metric unit is in microseconds, where - > (2^24 - 1) or 16,777,215 microseconds (16.777215 sec) is the - > maximum value of the path delay variation that can be - > expressed. - > - > Values that are larger than the maximum value SHOULD be - > encoded as the maximum value."; - > reference - > "RFC8233: Extensions to the Path Computation Element - > Communication Protocol (PCEP) to Compute Service-Aware Label - > Switched Paths (LSPs); + > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + > section 4.4"; + > } > - > RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; + > // CHANGE NOTE: The identity path-metric-delay-variation + > // below has been added in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-delay-variation { + > base te-types:path-metric-type; + > description + > "The Path Delay Variation Metric, + > measured in units of microseconds."; + > reference + > "RFC8233: Extensions to the Path Computation Element + > Communication Protocol (PCEP) to Compute Service-Aware Label + > Switched Paths (LSPs), section 3.1.2"; + > } > - > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - > } + > // CHANGE NOTE: The identity path-metric-loss below has + > // been added in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-loss { + > base te-types:path-metric-type; + > description + > "The Path Loss Metric, measured in units of 0.000003%."; + > reference + > "RFC8233: Extensions to the Path Computation Element + > Communication Protocol (PCEP) to Compute Service-Aware Label + > Switched Paths (LSPs), section 3.1.3"; + > } > > /* - 180a307,310 + 180a316,319 > /* > * Groupings > */ > - 472a603,672 + 472a612,681 > } > } > diff --git a/drafts/te-types-update/diffs/te-types/model-diff-spaces.txt b/drafts/te-types-update/diffs/te-types/model-diff-spaces.txt index 4ad695f..b5e0441 100644 --- a/drafts/te-types-update/diffs/te-types/model-diff-spaces.txt +++ b/drafts/te-types-update/diffs/te-types/model-diff-spaces.txt @@ -21,61 +21,134 @@ < the license terms contained in, the Simplified BSD License set --- > the license terms contained in, the Revised BSD License set - 65,66c75,113 + 65,66c75,164 < This version of this YANG module is part of RFC 8776; see the < RFC itself for full legal notices."; --- > This version of this YANG module is part of RFC XXXX > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself > for full legal notices."; - > revision 2024-01-29 { + > revision 2024-02-16 { > description - > "Added: - > - base identity lsp-provisioning-error-reason; - > - identity association-type-diversity; - > - identity tunnel-admin-state-auto; - > - identity lsp-restoration-restore-none; - > - identity restoration-scheme-rerouting; - > - base identity path-computation-error-reason and - > its derived identities; - > - base identity protocol-origin-type and - > its derived identities; - > - base identity svec-objective-function-type and its derived - > identities; - > - base identity svec-metric-type and its derived identities; - > - grouping encoding-and-switching-type. - > - > Updated: - > - description of the base identity objective-function-type; - > - description and reference of identity action-exercise; - > - typedef te-node-id to support also 16 octects TE identifiers. - > - > Obsoleted: - > - identity of-minimize-agg-bandwidth-consumption; - > - identity of-minimize-load-most-loaded-link; - > - identity of-minimize-cost-path-set; - > - identity lsp-protection-reroute-extra; - > - identity lsp-protection-reroute. - > - > Container explicit-route-objects-always renamed as - > explicit-route-objects."; + > "This revision adds the following new identities: + > - lsp-provisioning-error-reason; + > - association-type-diversity; + > - tunnel-admin-state-auto; + > - lsp-restoration-restore-none; + > - restoration-scheme-rerouting; + > - path-metric-optimization-type; + > - link-path-metric-type; + > - link-metric-type and its derived identities; + > - path-computation-error-reason and its derived identities; + > - protocol-origin-type and its derived identities; + > - svec-objective-function-type and its derived identities; + > - svec-metric-type and its derived identities. + > + > This revision adds the following new data types: + > - path-type; + > - te-gen-node-id. + > + > This revision adds the following new groupings: + > - encoding-and-switching-type; + > - te-generic-node-id. + > + > This revision updates the following identities: + > - objective-function-type; + > - action-exercise; + > - path-metric-type; + > - path-metric-te; + > - path-metric-igp; + > - path-metric-hop; + > - path-metric-delay-average; + > - path-metric-delay-minimum; + > - path-metric-residual-bandwidth; + > - path-metric-optimize-includes; + > - path-metric-optimize-excludes; + > - te-optimization-criterion. + > + > This revision updates the following data types: + > - te-node-id. + > + > This revision updates the following groupings: + > - explicit-route-hop: + > - adds the following leaves: + > - node-id-uri; + > - link-tp-id-uri; + > - updates the following leaves: + > - node-id; + > - link-tp-id; + > - record-route-state: + > - adds the following leaves: + > - node-id-uri; + > - link-tp-id-uri; + > - updates the following leaves: + > - node-id; + > - link-tp-id; + > - optimization-metric-entry: + > - updates the following leaves: + > - metric-type; + > - tunnel-constraints; + > - adds the following leaves: + > - network-id; + > - path-constraints-route-objects: + > - updates the following containers: + > - explicit-route-objects-always; + > - generic-path-metric-bounds: + > - updates the following leaves: + > - metric-type; + > - generic-path-optimization + > - adds the following leaves: + > - tiebreaker; + > - deprecate the following containers: + > - tiebreakers. + > + > This revision obsoletes the following identities: + > - of-minimize-agg-bandwidth-consumption; + > - of-minimize-load-most-loaded-link; + > - of-minimize-cost-path-set; + > - lsp-protection-reroute-extra; + > - lsp-protection-reroute. + > + > This revision provides also few editorial changes."; > reference > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; > } > // RFC Editor: replace XXXX with actual RFC number, update date > // information and remove this note - 351a399,401 + 70c168 + < "Latest revision of TE types."; + --- + > "Initial Version of TE types."; + 86a185 + > + 92a192 + > + 93a194 + > + 111a213 + > + 155a258 + > + 158a262 + > + 263a368 + > + 264a370 + > + 269a376 + > + 351a459,461 > // CHANGE NOTE: The typedef te-node-id below has been > // updated in this module revision > // RFC Editor: remove the note above and this note - 353c403,406 + 353c463,466 < type yang:dotted-quad; --- > type union { > type yang:dotted-quad; > type inet:ipv6-address-no-zone; > } - 357,358c410,414 + 357,358c470,474 < The identifier is represented as 4 octets in dotted-quad < notation. --- @@ -84,7 +157,7 @@ > dotted-quad notation or 16 octets in full, mixed, shortened, > or shortened-mixed IPv6 address notation. > - 362,363c418,421 + 362,363c478,481 < Router ID TLV described in Section 4.3 of RFC 5305, or the < TE Router ID TLV described in Section 3.2.1 of RFC 6119. --- @@ -92,13 +165,17 @@ > Router ID TLV described in Section 3.2.1 of RFC 6119, or the > IPv6 TE Router ID TLV described in Section 4.1 of RFC 6119. > - 368a427 + 368a487 + > + 370a490 + > + 371a492 > - 370a430 + 519a641 > - 371a432 + 537a660 > - 545a607,647 + 545a669,709 > // CHANGE NOTE: The typedef path-type below has been > // added in this module revision > // RFC Editor: remove the note above and this note @@ -140,7 +217,7 @@ > "Generic type that identifies a node in a TE topology."; > } > - 606a709,716 + 606a771,778 > // CHANGE NOTE: The base identity lsp-provisioning-error-reason > // has been added in this module revision > // RFC Editor: remove the note above and this note @@ -149,7 +226,7 @@ > "Base identity for LSP provisioning errors."; > } > - 982a1093,1110 + 982a1155,1172 > // CHANGE NOTE: The identity association-type-diversity below has > // been added in this module revision > // RFC Editor: remove the note above and this note @@ -159,7 +236,7 @@ > "Association Type diversity used to associate LSPs whose > paths are to be diverse from each other."; > reference - > "RFC8800: Path Computation Element Communication Protocol + > "RFC 8800: Path Computation Element Communication Protocol > (PCEP) Extension for Label Switched Path (LSP) Diversity > Constraint Signaling"; > } @@ -168,45 +245,92 @@ > // objective-function-type has been updated > // in this module revision > // RFC Editor: remove the note above and this note - 985c1113 + 985c1175 < "Base objective function type."; --- - > "Base identity for path objective function type."; - 1015a1144,1146 + > "Base identity for path objective function types."; + 1015a1206,1208 > // CHANGE NOTE: The identity of-minimize-agg-bandwidth-consumption > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1017a1149 + 1017a1211 > status obsolete; - 1020c1152 + 1020c1214,1218 < consumption."; --- - > consumption."; - 1023c1155 + > consumption. + > + > This identity has been obsoleted: the + > 'svec-of-minimize-agg-bandwidth-consumption' identity SHOULD + > be used instead."; + 1023c1221 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; - 1025a1158,1160 + 1025a1224,1226 > // CHANGE NOTE: The identity of-minimize-load-most-loaded-link > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1027a1163 + 1027a1229 > status obsolete; - 1030c1166 + 1030c1232,1236 < is carrying the highest load."; --- - > is carrying the highest load."; - 1033c1169 + > is carrying the highest load. + > + > This identity has been obsoleted: the + > 'svec-of-minimize-load-most-loaded-link' identity SHOULD + > be used instead."; + 1033c1239 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; - 1035a1172,1174 + 1035a1242,1244 > // CHANGE NOTE: The identity of-minimize-cost-path-set > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1037a1177 + 1037a1247 > status obsolete; - 1216a1357,1368 + 1039c1249,1253 + < "Objective function for minimizing the cost on a path set."; + --- + > "Objective function for minimizing the cost on a path set. + > + > This identity has been obsoleted: the + > 'svec-of-minimize-cost-path-set' identity SHOULD + > be used instead."; + 1049a1264,1266 + > // CHANGE NOTE: The reference of the identity path-locally-computed + > // below has been updated in this module revision + > // RFC Editor: remove the note above and this note + 1056,1057c1273,1274 + < "RFC 3272: Overview and Principles of Internet Traffic + < Engineering, Section 5.4"; + --- + > "RFC 9522: Overview and Principles of Internet Traffic + > Engineering, Section 4.4"; + 1059a1277,1280 + > // CHANGE NOTE: The reference of the identity + > // path-externally-queried below has been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + 1071c1292 + < "RFC 3272: Overview and Principles of Internet Traffic + --- + > "RFC 9522: Overview and Principles of Internet Traffic + 1072a1294 + > + 1076a1299,1302 + > // CHANGE NOTE: The reference of the identity + > // path-explicitly-defined below has been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + 1085c1311,1312 + < RFC 3272: Overview and Principles of Internet Traffic + --- + > + > RFC 9522: Overview and Principles of Internet Traffic + 1216a1444,1455 > // CHANGE NOTE: The identity tunnel-admin-state-auto below > // has been added in this module revision > // RFC Editor: remove the note above and this note @@ -219,7 +343,7 @@ > when it is not used by the client layer."; > } > - 1321a1474,1482 + 1321a1561,1569 > // CHANGE NOTE: The identity lsp-restoration-restore-none > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -229,7 +353,7 @@ > "No LSP affected by a failure is restored."; > } > - 1339a1501,1515 + 1339a1588,1602 > // CHANGE NOTE: The identity restoration-scheme-rerouting > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -245,13 +369,13 @@ > for Generalized Multi-Protocol Label Switching (GMPLS)"; > } > - 1383a1560,1562 + 1383a1647,1649 > // CHANGE NOTE: The identity lsp-protection-reroute-extra > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1385a1565 + 1385a1652 > status obsolete; - 1387c1567,1571 + 1387c1654,1658 < "'(Full) Rerouting' LSP protection type."; --- > "'(Full) Rerouting' LSP protection type. @@ -259,13 +383,13 @@ > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; - 1392a1577,1579 + 1392a1664,1666 > // CHANGE NOTE: The identity lsp-protection-reroute > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1394a1582 + 1394a1669 > status obsolete; - 1396c1584,1588 + 1396c1671,1675 < "'Rerouting without Extra-Traffic' LSP protection type."; --- > "'Rerouting without Extra-Traffic' LSP protection type. @@ -273,46 +397,327 @@ > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; - 1628a1821,1824 + 1628a1908,1911 > // CHANGE NOTE: The description and reference of the > // identity action-exercise have been updated in this module > // revision > // RFC Editor: remove the note above and this note - 1632,1633c1828,1830 + 1632,1633c1915,1917 < "An action that starts testing whether or not APS communication < is operating correctly. It is of lower priority than any --- > "An action that starts testing whether or not Automatic > Protection Switching (APS) communication is operating > correctly. It is of lower priority than any - 1636,1637c1833,1834 + 1636,1637c1920,1921 < "RFC 4427: Recovery (Protection and Restoration) Terminology < for Generalized Multi-Protocol Label Switching (GMPLS)"; --- > "ITU-T G.808.1 v4.0 (05/2014): Generic protection switching - > Linear trail and subnetwork protection"; - 1916a2114,2116 - > // CHANGE NOTE: The description of the identity path-metric-type - > // has been updated in this module revision + 1917c2201,2204 + < identity path-metric-type { + --- + > // CHANGE NOTE: The path-metric-optimization-type base identity + > // has been added in this module revision > // RFC Editor: remove the note above and this note - 1919c2119,2122 + > identity path-metric-optimization-type { + 1919c2206,2207 < "Base identity for the path metric type."; --- - > "Base identity for the path metric type. - > - > Derived identities SHOULD describe the unit and maximum value - > of the path metric types they define."; - 1939a2143,2145 - > // CHANGE NOTE: The reference for the identity path-metric-hop + > "Base identity used to define the path metric optimization + > types."; + 1922,1923c2210,2213 + < identity path-metric-te { + < base path-metric-type; + --- + > // CHANGE NOTE: The link-path-metric-type base identity > // has been added in this module revision > // RFC Editor: remove the note above and this note - 1943a2150,2152 - > reference - > "RFC5440: Path Computation Element (PCE) Communication - > Protocol (PCEP)"; - 1945a2155 + > identity link-path-metric-type { + 1925,1928c2215,2221 + < "TE path metric."; + < reference + < "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a + < second MPLS Traffic Engineering (TE) Metric"; + --- + > "Base identity used to define the link and the path metric + > types. + > + > The unit of the path metric value is interpreted in the + > context of the path metric type and the derived identities + > SHOULD describe the unit of the path metric types they + > define."; + 1931,1938c2224,2232 + < identity path-metric-igp { + < base path-metric-type; + < description + < "IGP path metric."; + < reference + < "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a + < second MPLS Traffic Engineering (TE) Metric"; + < } + --- + > // CHANGE NOTE: The link-metric-type base identity + > // and its derived identities + > // have been added in this module revision + > // RFC Editor: remove the note above and this note + > identity link-metric-type { + > base link-path-metric-type; + > description + > "Base identity for the link metric types."; + > } + 1940,1944c2234,2240 + < identity path-metric-hop { + < base path-metric-type; + < description + < "Hop path metric."; + < } + --- + > identity link-metric-te { + > base link-metric-type; + > description + > "Traffic Engineering (TE) Link Metric."; + > reference + > "RFC 3630: Traffic Engineering (TE) Extensions to OSPF + > Version 2, section 2.5.5 + 1946,1952c2242,2244 + < identity path-metric-delay-average { + < base path-metric-type; + < description + < "Average unidirectional link delay."; + < reference + < "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; + < } + --- + > RFC 5305: IS-IS Extensions for Traffic Engineering, + > section 3.7"; + > } + 1954,1960c2246,2253 + < identity path-metric-delay-minimum { + < base path-metric-type; + < description + < "Minimum unidirectional link delay."; + < reference + < "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; + < } + --- + > identity link-metric-igp { + > base link-metric-type; + > description + > "Interior Gateway Protocol (IGP) Link Metric."; + > reference + > "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric + > as a second MPLS Traffic Engineering (TE) Metric"; + > } + 1962,1972c2255,2266 + < identity path-metric-residual-bandwidth { + < base path-metric-type; + < description + < "Unidirectional Residual Bandwidth, which is defined to be + < Maximum Bandwidth (RFC 3630) minus the bandwidth currently + < allocated to LSPs."; + < reference + < "RFC 3630: Traffic Engineering (TE) Extensions to OSPF + < Version 2 + < RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; + < } + --- + > identity link-metric-delay-average { + > base link-metric-type; + > description + > "Unidirectional Link Delay, measured in units of + > microseconds."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.1 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.1"; + > } + 1974,1979c2268,2279 + < identity path-metric-optimize-includes { + < base path-metric-type; + < description + < "A metric that optimizes the number of included resources + < specified in a set."; + < } + --- + > identity link-metric-delay-minimum { + > base link-metric-type; + > description + > "Minimum unidirectional Link Delay, measured in units of + > microseconds."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.2 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.2"; + > } + 1981,1986c2281,2425 + < identity path-metric-optimize-excludes { + < base path-metric-type; + < description + < "A metric that optimizes to a maximum the number of excluded + < resources specified in a set."; + < } + --- + > identity link-metric-delay-maximum { + > base link-metric-type; + > description + > "Maximum unidirectional Link Delay, measured in units of + > microseconds."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.2 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.2"; + > } > - 2110a2321,2724 + > identity link-metric-residual-bandwidth { + > base link-metric-type; + > description + > "Unidirectional Residual Bandwidth, measured in units of + > bytes per second. + > + > It is defined to be Maximum Bandwidth minus the bandwidth + > currently allocated to LSPs."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.5 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.5"; + > } + > + > // CHANGE NOTE: The base and the description of the + > // path-metric-type identity + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-type { + > base link-path-metric-type; + > base path-metric-optimization-type; + > description + > "Base identity for the path metric types."; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-te identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-te { + > base path-metric-type; + > description + > "Traffic Engineering (TE) Path Metric."; + > reference + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.8"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-igp identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-igp { + > base path-metric-type; + > description + > "Interior Gateway Protocol (IGP) Path Metric."; + > reference + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.8"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-hop identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-hop { + > base path-metric-type; + > description + > "Hop Count Path Metric."; + > reference + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.8"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-delay-average identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-delay-average { + > base path-metric-type; + > description + > "The Path Delay Metric, measured in units of + > microseconds."; + > reference + > "RFC8233: Extensions to the Path Computation Element + > Communication Protocol (PCEP) to Compute Service-Aware + > Label Switched Paths (LSPs), section 3.1.1"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-delay-minimum identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-delay-minimum { + > base path-metric-type; + > description + > "The Path Min Delay Metric, measured in units of + > microseconds."; + > reference + > "I-D.ietf-pce-sid-algo: Carrying SR-Algorithm information + > in PCE-based Networks, section 3.5.1"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-residual-bandwidth identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-residual-bandwidth { + > base path-metric-type; + > description + > "The Path Residual Bandwidth, defined as the minimum Link + > Residual Bandwidth all the links along the path. + > + > The Path Residual Bandwidth can be seen as the path + > metric associated with the Maximum residual Bandwidth Path + > (MBP) objective function."; + > reference + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; + > } + > + > // CHANGE NOTE: The base of the path-metric-optimize-includes + > // identity has been updated in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-optimize-includes { + > base path-metric-optimization-type; + > description + > "A metric that optimizes the number of included resources + > specified in a set."; + > } + > + > // CHANGE NOTE: The base of the path-metric-optimize-excludes + > // identity has been updated in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-optimize-excludes { + > base path-metric-optimization-type; + > description + > "A metric that optimizes to a maximum the number of excluded + > resources specified in a set."; + > } + 2049a2489,2492 + > // CHANGE NOTE: The reference of the identity + > // te-optimization-criterion below has been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + 2054c2497 + < "RFC 3272: Overview and Principles of Internet Traffic + --- + > "RFC 9522: Overview and Principles of Internet Traffic + 2110a2554,2994 > // CHANGE NOTE: The base identity path-computation-error-reason > // and its derived identities below have been > // added in this module revision @@ -328,8 +733,8 @@ > "Path computation has failed because of an unspecified > reason."; > reference - > "Section 7.5 of RFC5440: Path Computation Element (PCE) - > Communication Protocol (PCEP)"; + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.5"; > } > > identity path-computation-error-no-topology { @@ -349,7 +754,13 @@ > a Backward-Recursive Path Computation (BRPC) downstream > PCE or a child PCE."; > reference - > "RFC5441, RFC8685"; + > "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + > Procedure to Compute Shortest Constrained Inter-Domain + > Traffic Engineering Label Switched Paths + > + > RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture"; > } > > identity path-computation-error-pce-unavailable { @@ -360,10 +771,11 @@ > It corresponds to bit 31 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5440: Path Computation Element (PCE) Communication - > Protocol (PCEP); + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP) > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-inclusion-hop { @@ -382,9 +794,12 @@ > It corresponds to bit 19 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-resource { @@ -396,9 +811,12 @@ > It corresponds to bit 20 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-child-pce-unresponsive { @@ -410,9 +828,12 @@ > It corresponds to bit 21 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-domain-unknown { @@ -424,9 +845,12 @@ > It corresponds to bit 22 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-p2mp { @@ -438,9 +862,12 @@ > It corresponds to bit 24 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8306; + > "RFC 8306: Extensions to the Path Computation Element + > Communication Protocol (PCEP) for Point-to-Multipoint + > Traffic Engineering Label Switched Paths > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-migration { @@ -452,9 +879,12 @@ > It corresponds to bit 26 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5557; + > "RFC 5557: Path Computation Element Communication Protocol + > (PCEP) Requirements and Protocol Extensions in Support of + > Global Concurrent Optimization > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-solution { @@ -466,9 +896,12 @@ > It corresponds to bit 25 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5557; + > "RFC 5557: Path Computation Element Communication Protocol + > (PCEP) Requirements and Protocol Extensions in Support of + > Global Concurrent Optimization > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-pks-expansion { @@ -480,9 +913,12 @@ > It corresponds to bit 27 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5520; + > "RFC 5520: Preserving Topology Confidentiality in + > Inter-Domain Path Computation Using a Path-Key-Based + > Mechanism > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-brpc-chain-unavailable { @@ -494,9 +930,12 @@ > It corresponds to bit 28 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5441; + > "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + > Procedure to Compute Shortest Constrained Inter-Domain + > Traffic Engineering Label Switched Paths > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-source-unknown { @@ -508,10 +947,11 @@ > It corresponds to bit 29 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-unknown { @@ -523,10 +963,11 @@ > It corresponds to bit 30 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-server { @@ -535,10 +976,11 @@ > "Path computation has failed because path computation > server is unavailable."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > // CHANGE NOTE: The base identity protocol-origin-type and @@ -563,7 +1005,7 @@ > "Protocol origin is Path Computation Engine Protocol > (PCEP)."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP)"; > } > @@ -571,7 +1013,7 @@ > base protocol-origin-type; > description > "Protocol origin is Border Gateway Protocol (BGP)."; - > reference "RFC9012"; + > reference "RFC 9012"; > } > > // CHANGE NOTE: The base identity svec-objective-function-type @@ -582,8 +1024,8 @@ > description > "Base identity for SVEC objective function type."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-agg-bandwidth-consumption { @@ -592,8 +1034,8 @@ > "Objective function for minimizing aggregate bandwidth > consumption (MBC)."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-load-most-loaded-link { @@ -602,8 +1044,8 @@ > "Objective function for minimizing the load on the link that > is carrying the highest load (MLL)."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-cost-path-set { @@ -612,8 +1054,8 @@ > "Objective function for minimizing the cost on a path set > (MCC)."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-common-transit-domain { @@ -622,9 +1064,9 @@ > "Objective function for minimizing the number of common > transit domains (MCTD)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation - > Element (H-PCE) Architecture."; + > Element (H-PCE) Architecture"; > } > > identity svec-of-minimize-shared-link { @@ -633,7 +1075,7 @@ > "Objective function for minimizing the number of shared > links (MSL)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -644,7 +1086,7 @@ > "Objective function for minimizing the number of shared > Shared Risk Link Groups (SRLG) (MSS)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -655,7 +1097,7 @@ > "Objective function for minimizing the number of shared > nodes (MSN)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -668,35 +1110,35 @@ > description > "Base identity for SVEC metric type."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - > identity svec-metric-cumul-te { + > identity svec-metric-cumulative-te { > base svec-metric-type; > description > "Cumulative TE cost."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - > identity svec-metric-cumul-igp { + > identity svec-metric-cumulative-igp { > base svec-metric-type; > description > "Cumulative IGP cost."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - > identity svec-metric-cumul-hop { + > identity svec-metric-cumulative-hop { > base svec-metric-type; > description > "Cumulative Hop path metric."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-aggregate-bandwidth-consumption { @@ -704,8 +1146,8 @@ > description > "Aggregate bandwidth consumption."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-load-of-the-most-loaded-link { @@ -713,15 +1155,29 @@ > description > "Load of the most loaded link."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - 2506a3121,3123 + 2221,2225c3105,3111 + < "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions + < RFC 7823: Performance-Based Path Selection for Explicitly + < Routed Label Switched Paths (LSPs) Using TE Metric + < Extensions + < RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + --- + > "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensionsù + > + > RFC 7823: Performance-Based Path Selection for Explicitly + > Routed Label Switched Paths (LSPs) Using TE Metric + > Extensions + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + 2506a3393,3395 > // CHANGE NOTE: The explicit-route-hop grouping below has been > // updated in this module revision > // RFC Editor: remove the note above and this note - 2514a3132,3140 + 2514a3404,3412 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; @@ -731,9 +1187,9 @@ > description > "The identifier of a node in the topology."; > } - 2517d3142 + 2517d3414 < mandatory true; - 2566a3192,3202 + 2566a3464,3474 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description @@ -745,30 +1201,34 @@ > description > "Link Termination Point (LTP) identifier."; > } - 2569d3204 + 2569d3476 < mandatory true; - 2574a3210,3214 + 2574a3482,3486 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } - 2577d3216 + 2577d3488 < mandatory true; - 2646a3286,3289 + 2631a3543,3545 + > // CHANGE NOTE: The explicit-route-hop grouping below has been + > // updated in this module revision + > // RFC Editor: remove the note above and this note + 2646a3561,3564 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; > } - 2648a3292,3296 + 2648a3567,3571 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } - 2651d3298 + 2651d3573 < mandatory true; - 2696a3344,3354 + 2696a3619,3629 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description @@ -780,44 +1240,103 @@ > description > "Link Termination Point (LTP) identifier."; > } - 2699d3356 + 2699d3631 < mandatory true; - 2704a3362,3366 + 2704a3637,3641 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } - 2968a3631,3635 + 2881a3819,3821 + > // CHANGE NOTE: The grouping optimization-metric-entry below has + > // been updated in this module revision + > // RFC Editor: remove the note above and this note + 2887c3827 + < base path-metric-type; + --- + > base path-metric-optimization-type; + 2964a3905,3907 + > // CHANGE NOTE: The grouping tunnel-constraints below has + > // been updated in this module revision + > // RFC Editor: remove the note above and this note + 2968a3912,3916 > leaf network-id { > type nw:network-id; > description > "The network topology identifier."; > } - 2977c3644,3647 + 2972a3921,3923 + > // CHANGE NOTE: The grouping path-constraints-route-objects below + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + 2977c3928 < container explicit-route-objects-always { --- - > // CHANGE NOTE: The explicit-route-objects container below has - > // been updated in this module revision - > // RFC Editor: remove the note above and this note > container explicit-route-objects { - 2979c3649 + 2979c3930 < "Container for the 'exclude route' object list."; --- > "Container for the explicit route object lists."; - 3124,3126c3794,3800 + 3101a4053,4055 + > // CHANGE NOTE: The grouping generic-path-metric-bounds below + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + 3107c4061 + < "TE path metric bounds container."; + --- + > "Top-level container for the list of path metric bounds."; + 3111c4065,4073 + < "List of TE path metric bounds."; + --- + > "List of path metric bounds, which can apply to link and + > path metrics. + > + > TE paths which have at least one path metric which + > exceeds the specified bounds MUST NOT be selected. + > + > TE paths that traverse TE links which have at least one + > link metric which exceeds the specified bounds MUST NOT + > be selected."; + 3114c4076 + < base path-metric-type; + --- + > base link-path-metric-type; + 3124,3126c4086,4092 < "Upper bound on the end-to-end TE path metric. A zero < indicates an unbounded upper limit for the specific < 'metric-type'."; --- - > "Upper bound on the end-to-end TE path metric. + > "Upper bound on the specified 'metric-type'. > > A zero indicates an unbounded upper limit for the - > specific 'metric-type'. + > specificied 'metric-type'. > > The unit of is interpreted in the context of the - > path-metric-type."; - 3379c4053,4112 + > 'metric-type' identity."; + 3131a4098,4100 + > // CHANGE NOTE: The grouping generic-path-metric-bounds below + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + 3154c4123,4127 + < "Container for the list of tiebreakers."; + --- + > "Container for the list of tiebreakers. + > + > This container has been obsoleted by the tiebreaker + > leaf."; + > status deprecated; + 3189a4163,4171 + > leaf tiebreaker { + > type identityref { + > base path-tiebreaker-type; + > } + > default "te-types:path-tiebreaker-random"; + > description + > "The tiebreaker criteria to apply on an equally favored set + > of paths, in order to pick the best."; + > } + 3379c4361,4420 < } \ No newline at end of file --- @@ -836,7 +1355,7 @@ > description > "LSP encoding type."; > reference - > "RFC3945"; + > "RFC 3945"; > } > leaf switching-type { > type identityref { @@ -845,7 +1364,7 @@ > description > "LSP switching type."; > reference - > "RFC3945"; + > "RFC 3945"; > } > } > diff --git a/drafts/te-types-update/diffs/te-types/model-diff.txt b/drafts/te-types-update/diffs/te-types/model-diff.txt index f183150..30984c3 100644 --- a/drafts/te-types-update/diffs/te-types/model-diff.txt +++ b/drafts/te-types-update/diffs/te-types/model-diff.txt @@ -21,61 +21,134 @@ < the license terms contained in, the Simplified BSD License set --- > the license terms contained in, the Revised BSD License set -65,66c75,113 +65,66c75,164 < This version of this YANG module is part of RFC 8776; see the < RFC itself for full legal notices."; --- > This version of this YANG module is part of RFC XXXX > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself > for full legal notices."; -> revision 2024-01-29 { +> revision 2024-02-16 { > description -> "Added: -> - base identity lsp-provisioning-error-reason; -> - identity association-type-diversity; -> - identity tunnel-admin-state-auto; -> - identity lsp-restoration-restore-none; -> - identity restoration-scheme-rerouting; -> - base identity path-computation-error-reason and -> its derived identities; -> - base identity protocol-origin-type and -> its derived identities; -> - base identity svec-objective-function-type and its derived -> identities; -> - base identity svec-metric-type and its derived identities; -> - grouping encoding-and-switching-type. -> -> Updated: -> - description of the base identity objective-function-type; -> - description and reference of identity action-exercise; -> - typedef te-node-id to support also 16 octects TE identifiers. -> -> Obsoleted: -> - identity of-minimize-agg-bandwidth-consumption; -> - identity of-minimize-load-most-loaded-link; -> - identity of-minimize-cost-path-set; -> - identity lsp-protection-reroute-extra; -> - identity lsp-protection-reroute. -> -> Container explicit-route-objects-always renamed as -> explicit-route-objects."; +> "This revision adds the following new identities: +> - lsp-provisioning-error-reason; +> - association-type-diversity; +> - tunnel-admin-state-auto; +> - lsp-restoration-restore-none; +> - restoration-scheme-rerouting; +> - path-metric-optimization-type; +> - link-path-metric-type; +> - link-metric-type and its derived identities; +> - path-computation-error-reason and its derived identities; +> - protocol-origin-type and its derived identities; +> - svec-objective-function-type and its derived identities; +> - svec-metric-type and its derived identities. +> +> This revision adds the following new data types: +> - path-type; +> - te-gen-node-id. +> +> This revision adds the following new groupings: +> - encoding-and-switching-type; +> - te-generic-node-id. +> +> This revision updates the following identities: +> - objective-function-type; +> - action-exercise; +> - path-metric-type; +> - path-metric-te; +> - path-metric-igp; +> - path-metric-hop; +> - path-metric-delay-average; +> - path-metric-delay-minimum; +> - path-metric-residual-bandwidth; +> - path-metric-optimize-includes; +> - path-metric-optimize-excludes; +> - te-optimization-criterion. +> +> This revision updates the following data types: +> - te-node-id. +> +> This revision updates the following groupings: +> - explicit-route-hop: +> - adds the following leaves: +> - node-id-uri; +> - link-tp-id-uri; +> - updates the following leaves: +> - node-id; +> - link-tp-id; +> - record-route-state: +> - adds the following leaves: +> - node-id-uri; +> - link-tp-id-uri; +> - updates the following leaves: +> - node-id; +> - link-tp-id; +> - optimization-metric-entry: +> - updates the following leaves: +> - metric-type; +> - tunnel-constraints; +> - adds the following leaves: +> - network-id; +> - path-constraints-route-objects: +> - updates the following containers: +> - explicit-route-objects-always; +> - generic-path-metric-bounds: +> - updates the following leaves: +> - metric-type; +> - generic-path-optimization +> - adds the following leaves: +> - tiebreaker; +> - deprecate the following containers: +> - tiebreakers. +> +> This revision obsoletes the following identities: +> - of-minimize-agg-bandwidth-consumption; +> - of-minimize-load-most-loaded-link; +> - of-minimize-cost-path-set; +> - lsp-protection-reroute-extra; +> - lsp-protection-reroute. +> +> This revision provides also few editorial changes."; > reference > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; > } > // RFC Editor: replace XXXX with actual RFC number, update date > // information and remove this note -351a399,401 +70c168 +< "Latest revision of TE types."; +--- +> "Initial Version of TE types."; +86a185 +> +92a192 +> +93a194 +> +111a213 +> +155a258 +> +158a262 +> +263a368 +> +264a370 +> +269a376 +> +351a459,461 > // CHANGE NOTE: The typedef te-node-id below has been > // updated in this module revision > // RFC Editor: remove the note above and this note -353c403,406 +353c463,466 < type yang:dotted-quad; --- > type union { > type yang:dotted-quad; > type inet:ipv6-address-no-zone; > } -357,358c410,414 +357,358c470,474 < The identifier is represented as 4 octets in dotted-quad < notation. --- @@ -84,7 +157,7 @@ > dotted-quad notation or 16 octets in full, mixed, shortened, > or shortened-mixed IPv6 address notation. > -362,363c418,421 +362,363c478,481 < Router ID TLV described in Section 4.3 of RFC 5305, or the < TE Router ID TLV described in Section 3.2.1 of RFC 6119. --- @@ -92,13 +165,17 @@ > Router ID TLV described in Section 3.2.1 of RFC 6119, or the > IPv6 TE Router ID TLV described in Section 4.1 of RFC 6119. > -368a427 +368a487 +> +370a490 +> +371a492 > -370a430 +519a641 > -371a432 +537a660 > -545a607,647 +545a669,709 > // CHANGE NOTE: The typedef path-type below has been > // added in this module revision > // RFC Editor: remove the note above and this note @@ -140,7 +217,7 @@ > "Generic type that identifies a node in a TE topology."; > } > -606a709,716 +606a771,778 > // CHANGE NOTE: The base identity lsp-provisioning-error-reason > // has been added in this module revision > // RFC Editor: remove the note above and this note @@ -149,7 +226,7 @@ > "Base identity for LSP provisioning errors."; > } > -982a1093,1110 +982a1155,1172 > // CHANGE NOTE: The identity association-type-diversity below has > // been added in this module revision > // RFC Editor: remove the note above and this note @@ -159,7 +236,7 @@ > "Association Type diversity used to associate LSPs whose > paths are to be diverse from each other."; > reference -> "RFC8800: Path Computation Element Communication Protocol +> "RFC 8800: Path Computation Element Communication Protocol > (PCEP) Extension for Label Switched Path (LSP) Diversity > Constraint Signaling"; > } @@ -168,45 +245,92 @@ > // objective-function-type has been updated > // in this module revision > // RFC Editor: remove the note above and this note -985c1113 +985c1175 < "Base objective function type."; --- -> "Base identity for path objective function type."; -1015a1144,1146 +> "Base identity for path objective function types."; +1015a1206,1208 > // CHANGE NOTE: The identity of-minimize-agg-bandwidth-consumption > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1017a1149 +1017a1211 > status obsolete; -1020c1152 +1020c1214,1218 < consumption."; --- -> consumption."; -1023c1155 +> consumption. +> +> This identity has been obsoleted: the +> 'svec-of-minimize-agg-bandwidth-consumption' identity SHOULD +> be used instead."; +1023c1221 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; -1025a1158,1160 +1025a1224,1226 > // CHANGE NOTE: The identity of-minimize-load-most-loaded-link > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1027a1163 +1027a1229 > status obsolete; -1030c1166 +1030c1232,1236 < is carrying the highest load."; --- -> is carrying the highest load."; -1033c1169 +> is carrying the highest load. +> +> This identity has been obsoleted: the +> 'svec-of-minimize-load-most-loaded-link' identity SHOULD +> be used instead."; +1033c1239 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; -1035a1172,1174 +1035a1242,1244 > // CHANGE NOTE: The identity of-minimize-cost-path-set > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1037a1177 +1037a1247 > status obsolete; -1216a1357,1368 +1039c1249,1253 +< "Objective function for minimizing the cost on a path set."; +--- +> "Objective function for minimizing the cost on a path set. +> +> This identity has been obsoleted: the +> 'svec-of-minimize-cost-path-set' identity SHOULD +> be used instead."; +1049a1264,1266 +> // CHANGE NOTE: The reference of the identity path-locally-computed +> // below has been updated in this module revision +> // RFC Editor: remove the note above and this note +1056,1057c1273,1274 +< "RFC 3272: Overview and Principles of Internet Traffic +< Engineering, Section 5.4"; +--- +> "RFC 9522: Overview and Principles of Internet Traffic +> Engineering, Section 4.4"; +1059a1277,1280 +> // CHANGE NOTE: The reference of the identity +> // path-externally-queried below has been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +1071c1292 +< "RFC 3272: Overview and Principles of Internet Traffic +--- +> "RFC 9522: Overview and Principles of Internet Traffic +1072a1294 +> +1076a1299,1302 +> // CHANGE NOTE: The reference of the identity +> // path-explicitly-defined below has been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +1085c1311,1312 +< RFC 3272: Overview and Principles of Internet Traffic +--- +> +> RFC 9522: Overview and Principles of Internet Traffic +1216a1444,1455 > // CHANGE NOTE: The identity tunnel-admin-state-auto below > // has been added in this module revision > // RFC Editor: remove the note above and this note @@ -219,7 +343,7 @@ > when it is not used by the client layer."; > } > -1321a1474,1482 +1321a1561,1569 > // CHANGE NOTE: The identity lsp-restoration-restore-none > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -229,7 +353,7 @@ > "No LSP affected by a failure is restored."; > } > -1339a1501,1515 +1339a1588,1602 > // CHANGE NOTE: The identity restoration-scheme-rerouting > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -245,13 +369,13 @@ > for Generalized Multi-Protocol Label Switching (GMPLS)"; > } > -1383a1560,1562 +1383a1647,1649 > // CHANGE NOTE: The identity lsp-protection-reroute-extra > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1385a1565 +1385a1652 > status obsolete; -1387c1567,1571 +1387c1654,1658 < "'(Full) Rerouting' LSP protection type."; --- > "'(Full) Rerouting' LSP protection type. @@ -259,13 +383,13 @@ > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; -1392a1577,1579 +1392a1664,1666 > // CHANGE NOTE: The identity lsp-protection-reroute > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1394a1582 +1394a1669 > status obsolete; -1396c1584,1588 +1396c1671,1675 < "'Rerouting without Extra-Traffic' LSP protection type."; --- > "'Rerouting without Extra-Traffic' LSP protection type. @@ -273,46 +397,327 @@ > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; -1628a1821,1824 +1628a1908,1911 > // CHANGE NOTE: The description and reference of the > // identity action-exercise have been updated in this module > // revision > // RFC Editor: remove the note above and this note -1632,1633c1828,1830 +1632,1633c1915,1917 < "An action that starts testing whether or not APS communication < is operating correctly. It is of lower priority than any --- > "An action that starts testing whether or not Automatic > Protection Switching (APS) communication is operating > correctly. It is of lower priority than any -1636,1637c1833,1834 +1636,1637c1920,1921 < "RFC 4427: Recovery (Protection and Restoration) Terminology < for Generalized Multi-Protocol Label Switching (GMPLS)"; --- > "ITU-T G.808.1 v4.0 (05/2014): Generic protection switching - > Linear trail and subnetwork protection"; -1916a2114,2116 -> // CHANGE NOTE: The description of the identity path-metric-type -> // has been updated in this module revision +1917c2201,2204 +< identity path-metric-type { +--- +> // CHANGE NOTE: The path-metric-optimization-type base identity +> // has been added in this module revision > // RFC Editor: remove the note above and this note -1919c2119,2122 +> identity path-metric-optimization-type { +1919c2206,2207 < "Base identity for the path metric type."; --- -> "Base identity for the path metric type. -> -> Derived identities SHOULD describe the unit and maximum value -> of the path metric types they define."; -1939a2143,2145 -> // CHANGE NOTE: The reference for the identity path-metric-hop +> "Base identity used to define the path metric optimization +> types."; +1922,1923c2210,2213 +< identity path-metric-te { +< base path-metric-type; +--- +> // CHANGE NOTE: The link-path-metric-type base identity > // has been added in this module revision > // RFC Editor: remove the note above and this note -1943a2150,2152 -> reference -> "RFC5440: Path Computation Element (PCE) Communication -> Protocol (PCEP)"; -1945a2155 +> identity link-path-metric-type { +1925,1928c2215,2221 +< "TE path metric."; +< reference +< "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a +< second MPLS Traffic Engineering (TE) Metric"; +--- +> "Base identity used to define the link and the path metric +> types. +> +> The unit of the path metric value is interpreted in the +> context of the path metric type and the derived identities +> SHOULD describe the unit of the path metric types they +> define."; +1931,1938c2224,2232 +< identity path-metric-igp { +< base path-metric-type; +< description +< "IGP path metric."; +< reference +< "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a +< second MPLS Traffic Engineering (TE) Metric"; +< } +--- +> // CHANGE NOTE: The link-metric-type base identity +> // and its derived identities +> // have been added in this module revision +> // RFC Editor: remove the note above and this note +> identity link-metric-type { +> base link-path-metric-type; +> description +> "Base identity for the link metric types."; +> } +1940,1944c2234,2240 +< identity path-metric-hop { +< base path-metric-type; +< description +< "Hop path metric."; +< } +--- +> identity link-metric-te { +> base link-metric-type; +> description +> "Traffic Engineering (TE) Link Metric."; +> reference +> "RFC 3630: Traffic Engineering (TE) Extensions to OSPF +> Version 2, section 2.5.5 +1946,1952c2242,2244 +< identity path-metric-delay-average { +< base path-metric-type; +< description +< "Average unidirectional link delay."; +< reference +< "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; +< } +--- +> RFC 5305: IS-IS Extensions for Traffic Engineering, +> section 3.7"; +> } +1954,1960c2246,2253 +< identity path-metric-delay-minimum { +< base path-metric-type; +< description +< "Minimum unidirectional link delay."; +< reference +< "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; +< } +--- +> identity link-metric-igp { +> base link-metric-type; +> description +> "Interior Gateway Protocol (IGP) Link Metric."; +> reference +> "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric +> as a second MPLS Traffic Engineering (TE) Metric"; +> } +1962,1972c2255,2266 +< identity path-metric-residual-bandwidth { +< base path-metric-type; +< description +< "Unidirectional Residual Bandwidth, which is defined to be +< Maximum Bandwidth (RFC 3630) minus the bandwidth currently +< allocated to LSPs."; +< reference +< "RFC 3630: Traffic Engineering (TE) Extensions to OSPF +< Version 2 +< RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; +< } +--- +> identity link-metric-delay-average { +> base link-metric-type; +> description +> "Unidirectional Link Delay, measured in units of +> microseconds."; +> reference +> "RFC 7471: OSPF Traffic Engineering (TE) Metric +> Extensions, section 4.1 +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric +> Extensions, section 4.1"; +> } +1974,1979c2268,2279 +< identity path-metric-optimize-includes { +< base path-metric-type; +< description +< "A metric that optimizes the number of included resources +< specified in a set."; +< } +--- +> identity link-metric-delay-minimum { +> base link-metric-type; +> description +> "Minimum unidirectional Link Delay, measured in units of +> microseconds."; +> reference +> "RFC 7471: OSPF Traffic Engineering (TE) Metric +> Extensions, section 4.2 +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric +> Extensions, section 4.2"; +> } +1981,1986c2281,2425 +< identity path-metric-optimize-excludes { +< base path-metric-type; +< description +< "A metric that optimizes to a maximum the number of excluded +< resources specified in a set."; +< } +--- +> identity link-metric-delay-maximum { +> base link-metric-type; +> description +> "Maximum unidirectional Link Delay, measured in units of +> microseconds."; +> reference +> "RFC 7471: OSPF Traffic Engineering (TE) Metric +> Extensions, section 4.2 +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric +> Extensions, section 4.2"; +> } > -2110a2321,2724 +> identity link-metric-residual-bandwidth { +> base link-metric-type; +> description +> "Unidirectional Residual Bandwidth, measured in units of +> bytes per second. +> +> It is defined to be Maximum Bandwidth minus the bandwidth +> currently allocated to LSPs."; +> reference +> "RFC 7471: OSPF Traffic Engineering (TE) Metric +> Extensions, section 4.5 +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric +> Extensions, section 4.5"; +> } +> +> // CHANGE NOTE: The base and the description of the +> // path-metric-type identity +> // has been updated in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-type { +> base link-path-metric-type; +> base path-metric-optimization-type; +> description +> "Base identity for the path metric types."; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-te identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-te { +> base path-metric-type; +> description +> "Traffic Engineering (TE) Path Metric."; +> reference +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP), section 7.8"; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-igp identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-igp { +> base path-metric-type; +> description +> "Interior Gateway Protocol (IGP) Path Metric."; +> reference +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP), section 7.8"; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-hop identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-hop { +> base path-metric-type; +> description +> "Hop Count Path Metric."; +> reference +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP), section 7.8"; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-delay-average identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-delay-average { +> base path-metric-type; +> description +> "The Path Delay Metric, measured in units of +> microseconds."; +> reference +> "RFC8233: Extensions to the Path Computation Element +> Communication Protocol (PCEP) to Compute Service-Aware +> Label Switched Paths (LSPs), section 3.1.1"; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-delay-minimum identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-delay-minimum { +> base path-metric-type; +> description +> "The Path Min Delay Metric, measured in units of +> microseconds."; +> reference +> "I-D.ietf-pce-sid-algo: Carrying SR-Algorithm information +> in PCE-based Networks, section 3.5.1"; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-residual-bandwidth identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-residual-bandwidth { +> base path-metric-type; +> description +> "The Path Residual Bandwidth, defined as the minimum Link +> Residual Bandwidth all the links along the path. +> +> The Path Residual Bandwidth can be seen as the path +> metric associated with the Maximum residual Bandwidth Path +> (MBP) objective function."; +> reference +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; +> } +> +> // CHANGE NOTE: The base of the path-metric-optimize-includes +> // identity has been updated in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-optimize-includes { +> base path-metric-optimization-type; +> description +> "A metric that optimizes the number of included resources +> specified in a set."; +> } +> +> // CHANGE NOTE: The base of the path-metric-optimize-excludes +> // identity has been updated in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-optimize-excludes { +> base path-metric-optimization-type; +> description +> "A metric that optimizes to a maximum the number of excluded +> resources specified in a set."; +> } +2049a2489,2492 +> // CHANGE NOTE: The reference of the identity +> // te-optimization-criterion below has been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +2054c2497 +< "RFC 3272: Overview and Principles of Internet Traffic +--- +> "RFC 9522: Overview and Principles of Internet Traffic +2110a2554,2994 > // CHANGE NOTE: The base identity path-computation-error-reason > // and its derived identities below have been > // added in this module revision @@ -328,8 +733,8 @@ > "Path computation has failed because of an unspecified > reason."; > reference -> "Section 7.5 of RFC5440: Path Computation Element (PCE) -> Communication Protocol (PCEP)"; +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP), section 7.5"; > } > > identity path-computation-error-no-topology { @@ -349,7 +754,13 @@ > a Backward-Recursive Path Computation (BRPC) downstream > PCE or a child PCE."; > reference -> "RFC5441, RFC8685"; +> "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) +> Procedure to Compute Shortest Constrained Inter-Domain +> Traffic Engineering Label Switched Paths +> +> RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture"; > } > > identity path-computation-error-pce-unavailable { @@ -360,10 +771,11 @@ > It corresponds to bit 31 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5440: Path Computation Element (PCE) Communication -> Protocol (PCEP); +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP) > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-inclusion-hop { @@ -382,9 +794,12 @@ > It corresponds to bit 19 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8685; +> "RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-resource { @@ -396,9 +811,12 @@ > It corresponds to bit 20 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8685; +> "RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-child-pce-unresponsive { @@ -410,9 +828,12 @@ > It corresponds to bit 21 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8685; +> "RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-domain-unknown { @@ -424,9 +845,12 @@ > It corresponds to bit 22 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8685; +> "RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-p2mp { @@ -438,9 +862,12 @@ > It corresponds to bit 24 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8306; +> "RFC 8306: Extensions to the Path Computation Element +> Communication Protocol (PCEP) for Point-to-Multipoint +> Traffic Engineering Label Switched Paths > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-migration { @@ -452,9 +879,12 @@ > It corresponds to bit 26 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5557; +> "RFC 5557: Path Computation Element Communication Protocol +> (PCEP) Requirements and Protocol Extensions in Support of +> Global Concurrent Optimization > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-solution { @@ -466,9 +896,12 @@ > It corresponds to bit 25 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5557; +> "RFC 5557: Path Computation Element Communication Protocol +> (PCEP) Requirements and Protocol Extensions in Support of +> Global Concurrent Optimization > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-pks-expansion { @@ -480,9 +913,12 @@ > It corresponds to bit 27 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5520; +> "RFC 5520: Preserving Topology Confidentiality in +> Inter-Domain Path Computation Using a Path-Key-Based +> Mechanism > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-brpc-chain-unavailable { @@ -494,9 +930,12 @@ > It corresponds to bit 28 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5441; +> "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) +> Procedure to Compute Shortest Constrained Inter-Domain +> Traffic Engineering Label Switched Paths > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-source-unknown { @@ -508,10 +947,11 @@ > It corresponds to bit 29 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5440: Path Computation Element (PCE) Communication +> "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-unknown { @@ -523,10 +963,11 @@ > It corresponds to bit 30 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5440: Path Computation Element (PCE) Communication +> "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-server { @@ -535,10 +976,11 @@ > "Path computation has failed because path computation > server is unavailable."; > reference -> "RFC5440: Path Computation Element (PCE) Communication +> "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > // CHANGE NOTE: The base identity protocol-origin-type and @@ -563,7 +1005,7 @@ > "Protocol origin is Path Computation Engine Protocol > (PCEP)."; > reference -> "RFC5440: Path Computation Element (PCE) Communication +> "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP)"; > } > @@ -571,7 +1013,7 @@ > base protocol-origin-type; > description > "Protocol origin is Border Gateway Protocol (BGP)."; -> reference "RFC9012"; +> reference "RFC 9012"; > } > > // CHANGE NOTE: The base identity svec-objective-function-type @@ -582,8 +1024,8 @@ > description > "Base identity for SVEC objective function type."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-agg-bandwidth-consumption { @@ -592,8 +1034,8 @@ > "Objective function for minimizing aggregate bandwidth > consumption (MBC)."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-load-most-loaded-link { @@ -602,8 +1044,8 @@ > "Objective function for minimizing the load on the link that > is carrying the highest load (MLL)."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-cost-path-set { @@ -612,8 +1054,8 @@ > "Objective function for minimizing the cost on a path set > (MCC)."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-common-transit-domain { @@ -622,9 +1064,9 @@ > "Objective function for minimizing the number of common > transit domains (MCTD)."; > reference -> "RFC8685: Path Computation Element Communication Protocol +> "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation -> Element (H-PCE) Architecture."; +> Element (H-PCE) Architecture"; > } > > identity svec-of-minimize-shared-link { @@ -633,7 +1075,7 @@ > "Objective function for minimizing the number of shared > links (MSL)."; > reference -> "RFC8685: Path Computation Element Communication Protocol +> "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -644,7 +1086,7 @@ > "Objective function for minimizing the number of shared > Shared Risk Link Groups (SRLG) (MSS)."; > reference -> "RFC8685: Path Computation Element Communication Protocol +> "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -655,7 +1097,7 @@ > "Objective function for minimizing the number of shared > nodes (MSN)."; > reference -> "RFC8685: Path Computation Element Communication Protocol +> "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -668,35 +1110,35 @@ > description > "Base identity for SVEC metric type."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > -> identity svec-metric-cumul-te { +> identity svec-metric-cumulative-te { > base svec-metric-type; > description > "Cumulative TE cost."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > -> identity svec-metric-cumul-igp { +> identity svec-metric-cumulative-igp { > base svec-metric-type; > description > "Cumulative IGP cost."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > -> identity svec-metric-cumul-hop { +> identity svec-metric-cumulative-hop { > base svec-metric-type; > description > "Cumulative Hop path metric."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-aggregate-bandwidth-consumption { @@ -704,8 +1146,8 @@ > description > "Aggregate bandwidth consumption."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-load-of-the-most-loaded-link { @@ -713,15 +1155,29 @@ > description > "Load of the most loaded link."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > -2506a3121,3123 +2221,2225c3105,3111 +< "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions +< RFC 7823: Performance-Based Path Selection for Explicitly +< Routed Label Switched Paths (LSPs) Using TE Metric +< Extensions +< RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; +--- +> "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensionsù +> +> RFC 7823: Performance-Based Path Selection for Explicitly +> Routed Label Switched Paths (LSPs) Using TE Metric +> Extensions +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; +2506a3393,3395 > // CHANGE NOTE: The explicit-route-hop grouping below has been > // updated in this module revision > // RFC Editor: remove the note above and this note -2514a3132,3140 +2514a3404,3412 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; @@ -731,9 +1187,9 @@ > description > "The identifier of a node in the topology."; > } -2517d3142 +2517d3414 < mandatory true; -2566a3192,3202 +2566a3464,3474 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description @@ -745,30 +1201,34 @@ > description > "Link Termination Point (LTP) identifier."; > } -2569d3204 +2569d3476 < mandatory true; -2574a3210,3214 +2574a3482,3486 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } -2577d3216 +2577d3488 < mandatory true; -2646a3286,3289 +2631a3543,3545 +> // CHANGE NOTE: The explicit-route-hop grouping below has been +> // updated in this module revision +> // RFC Editor: remove the note above and this note +2646a3561,3564 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; > } -2648a3292,3296 +2648a3567,3571 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } -2651d3298 +2651d3573 < mandatory true; -2696a3344,3354 +2696a3619,3629 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description @@ -780,44 +1240,103 @@ > description > "Link Termination Point (LTP) identifier."; > } -2699d3356 +2699d3631 < mandatory true; -2704a3362,3366 +2704a3637,3641 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } -2968a3631,3635 +2881a3819,3821 +> // CHANGE NOTE: The grouping optimization-metric-entry below has +> // been updated in this module revision +> // RFC Editor: remove the note above and this note +2887c3827 +< base path-metric-type; +--- +> base path-metric-optimization-type; +2964a3905,3907 +> // CHANGE NOTE: The grouping tunnel-constraints below has +> // been updated in this module revision +> // RFC Editor: remove the note above and this note +2968a3912,3916 > leaf network-id { > type nw:network-id; > description > "The network topology identifier."; > } -2977c3644,3647 +2972a3921,3923 +> // CHANGE NOTE: The grouping path-constraints-route-objects below +> // has been updated in this module revision +> // RFC Editor: remove the note above and this note +2977c3928 < container explicit-route-objects-always { --- -> // CHANGE NOTE: The explicit-route-objects container below has -> // been updated in this module revision -> // RFC Editor: remove the note above and this note > container explicit-route-objects { -2979c3649 +2979c3930 < "Container for the 'exclude route' object list."; --- > "Container for the explicit route object lists."; -3124,3126c3794,3800 +3101a4053,4055 +> // CHANGE NOTE: The grouping generic-path-metric-bounds below +> // has been updated in this module revision +> // RFC Editor: remove the note above and this note +3107c4061 +< "TE path metric bounds container."; +--- +> "Top-level container for the list of path metric bounds."; +3111c4065,4073 +< "List of TE path metric bounds."; +--- +> "List of path metric bounds, which can apply to link and +> path metrics. +> +> TE paths which have at least one path metric which +> exceeds the specified bounds MUST NOT be selected. +> +> TE paths that traverse TE links which have at least one +> link metric which exceeds the specified bounds MUST NOT +> be selected."; +3114c4076 +< base path-metric-type; +--- +> base link-path-metric-type; +3124,3126c4086,4092 < "Upper bound on the end-to-end TE path metric. A zero < indicates an unbounded upper limit for the specific < 'metric-type'."; --- -> "Upper bound on the end-to-end TE path metric. +> "Upper bound on the specified 'metric-type'. > > A zero indicates an unbounded upper limit for the -> specific 'metric-type'. +> specificied 'metric-type'. > > The unit of is interpreted in the context of the -> path-metric-type."; -3379c4053,4112 +> 'metric-type' identity."; +3131a4098,4100 +> // CHANGE NOTE: The grouping generic-path-metric-bounds below +> // has been updated in this module revision +> // RFC Editor: remove the note above and this note +3154c4123,4127 +< "Container for the list of tiebreakers."; +--- +> "Container for the list of tiebreakers. +> +> This container has been obsoleted by the tiebreaker +> leaf."; +> status deprecated; +3189a4163,4171 +> leaf tiebreaker { +> type identityref { +> base path-tiebreaker-type; +> } +> default "te-types:path-tiebreaker-random"; +> description +> "The tiebreaker criteria to apply on an equally favored set +> of paths, in order to pick the best."; +> } +3379c4361,4420 < } \ No newline at end of file --- @@ -836,7 +1355,7 @@ > description > "LSP encoding type."; > reference -> "RFC3945"; +> "RFC 3945"; > } > leaf switching-type { > type identityref { @@ -845,7 +1364,7 @@ > description > "LSP switching type."; > reference -> "RFC3945"; +> "RFC 3945"; > } > } > diff --git a/drafts/te-types-update/diffs/te-types/model-updates.txt b/drafts/te-types-update/diffs/te-types/model-updates.txt index 4ad695f..b5e0441 100644 --- a/drafts/te-types-update/diffs/te-types/model-updates.txt +++ b/drafts/te-types-update/diffs/te-types/model-updates.txt @@ -21,61 +21,134 @@ < the license terms contained in, the Simplified BSD License set --- > the license terms contained in, the Revised BSD License set - 65,66c75,113 + 65,66c75,164 < This version of this YANG module is part of RFC 8776; see the < RFC itself for full legal notices."; --- > This version of this YANG module is part of RFC XXXX > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself > for full legal notices."; - > revision 2024-01-29 { + > revision 2024-02-16 { > description - > "Added: - > - base identity lsp-provisioning-error-reason; - > - identity association-type-diversity; - > - identity tunnel-admin-state-auto; - > - identity lsp-restoration-restore-none; - > - identity restoration-scheme-rerouting; - > - base identity path-computation-error-reason and - > its derived identities; - > - base identity protocol-origin-type and - > its derived identities; - > - base identity svec-objective-function-type and its derived - > identities; - > - base identity svec-metric-type and its derived identities; - > - grouping encoding-and-switching-type. - > - > Updated: - > - description of the base identity objective-function-type; - > - description and reference of identity action-exercise; - > - typedef te-node-id to support also 16 octects TE identifiers. - > - > Obsoleted: - > - identity of-minimize-agg-bandwidth-consumption; - > - identity of-minimize-load-most-loaded-link; - > - identity of-minimize-cost-path-set; - > - identity lsp-protection-reroute-extra; - > - identity lsp-protection-reroute. - > - > Container explicit-route-objects-always renamed as - > explicit-route-objects."; + > "This revision adds the following new identities: + > - lsp-provisioning-error-reason; + > - association-type-diversity; + > - tunnel-admin-state-auto; + > - lsp-restoration-restore-none; + > - restoration-scheme-rerouting; + > - path-metric-optimization-type; + > - link-path-metric-type; + > - link-metric-type and its derived identities; + > - path-computation-error-reason and its derived identities; + > - protocol-origin-type and its derived identities; + > - svec-objective-function-type and its derived identities; + > - svec-metric-type and its derived identities. + > + > This revision adds the following new data types: + > - path-type; + > - te-gen-node-id. + > + > This revision adds the following new groupings: + > - encoding-and-switching-type; + > - te-generic-node-id. + > + > This revision updates the following identities: + > - objective-function-type; + > - action-exercise; + > - path-metric-type; + > - path-metric-te; + > - path-metric-igp; + > - path-metric-hop; + > - path-metric-delay-average; + > - path-metric-delay-minimum; + > - path-metric-residual-bandwidth; + > - path-metric-optimize-includes; + > - path-metric-optimize-excludes; + > - te-optimization-criterion. + > + > This revision updates the following data types: + > - te-node-id. + > + > This revision updates the following groupings: + > - explicit-route-hop: + > - adds the following leaves: + > - node-id-uri; + > - link-tp-id-uri; + > - updates the following leaves: + > - node-id; + > - link-tp-id; + > - record-route-state: + > - adds the following leaves: + > - node-id-uri; + > - link-tp-id-uri; + > - updates the following leaves: + > - node-id; + > - link-tp-id; + > - optimization-metric-entry: + > - updates the following leaves: + > - metric-type; + > - tunnel-constraints; + > - adds the following leaves: + > - network-id; + > - path-constraints-route-objects: + > - updates the following containers: + > - explicit-route-objects-always; + > - generic-path-metric-bounds: + > - updates the following leaves: + > - metric-type; + > - generic-path-optimization + > - adds the following leaves: + > - tiebreaker; + > - deprecate the following containers: + > - tiebreakers. + > + > This revision obsoletes the following identities: + > - of-minimize-agg-bandwidth-consumption; + > - of-minimize-load-most-loaded-link; + > - of-minimize-cost-path-set; + > - lsp-protection-reroute-extra; + > - lsp-protection-reroute. + > + > This revision provides also few editorial changes."; > reference > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; > } > // RFC Editor: replace XXXX with actual RFC number, update date > // information and remove this note - 351a399,401 + 70c168 + < "Latest revision of TE types."; + --- + > "Initial Version of TE types."; + 86a185 + > + 92a192 + > + 93a194 + > + 111a213 + > + 155a258 + > + 158a262 + > + 263a368 + > + 264a370 + > + 269a376 + > + 351a459,461 > // CHANGE NOTE: The typedef te-node-id below has been > // updated in this module revision > // RFC Editor: remove the note above and this note - 353c403,406 + 353c463,466 < type yang:dotted-quad; --- > type union { > type yang:dotted-quad; > type inet:ipv6-address-no-zone; > } - 357,358c410,414 + 357,358c470,474 < The identifier is represented as 4 octets in dotted-quad < notation. --- @@ -84,7 +157,7 @@ > dotted-quad notation or 16 octets in full, mixed, shortened, > or shortened-mixed IPv6 address notation. > - 362,363c418,421 + 362,363c478,481 < Router ID TLV described in Section 4.3 of RFC 5305, or the < TE Router ID TLV described in Section 3.2.1 of RFC 6119. --- @@ -92,13 +165,17 @@ > Router ID TLV described in Section 3.2.1 of RFC 6119, or the > IPv6 TE Router ID TLV described in Section 4.1 of RFC 6119. > - 368a427 + 368a487 + > + 370a490 + > + 371a492 > - 370a430 + 519a641 > - 371a432 + 537a660 > - 545a607,647 + 545a669,709 > // CHANGE NOTE: The typedef path-type below has been > // added in this module revision > // RFC Editor: remove the note above and this note @@ -140,7 +217,7 @@ > "Generic type that identifies a node in a TE topology."; > } > - 606a709,716 + 606a771,778 > // CHANGE NOTE: The base identity lsp-provisioning-error-reason > // has been added in this module revision > // RFC Editor: remove the note above and this note @@ -149,7 +226,7 @@ > "Base identity for LSP provisioning errors."; > } > - 982a1093,1110 + 982a1155,1172 > // CHANGE NOTE: The identity association-type-diversity below has > // been added in this module revision > // RFC Editor: remove the note above and this note @@ -159,7 +236,7 @@ > "Association Type diversity used to associate LSPs whose > paths are to be diverse from each other."; > reference - > "RFC8800: Path Computation Element Communication Protocol + > "RFC 8800: Path Computation Element Communication Protocol > (PCEP) Extension for Label Switched Path (LSP) Diversity > Constraint Signaling"; > } @@ -168,45 +245,92 @@ > // objective-function-type has been updated > // in this module revision > // RFC Editor: remove the note above and this note - 985c1113 + 985c1175 < "Base objective function type."; --- - > "Base identity for path objective function type."; - 1015a1144,1146 + > "Base identity for path objective function types."; + 1015a1206,1208 > // CHANGE NOTE: The identity of-minimize-agg-bandwidth-consumption > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1017a1149 + 1017a1211 > status obsolete; - 1020c1152 + 1020c1214,1218 < consumption."; --- - > consumption."; - 1023c1155 + > consumption. + > + > This identity has been obsoleted: the + > 'svec-of-minimize-agg-bandwidth-consumption' identity SHOULD + > be used instead."; + 1023c1221 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; - 1025a1158,1160 + 1025a1224,1226 > // CHANGE NOTE: The identity of-minimize-load-most-loaded-link > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1027a1163 + 1027a1229 > status obsolete; - 1030c1166 + 1030c1232,1236 < is carrying the highest load."; --- - > is carrying the highest load."; - 1033c1169 + > is carrying the highest load. + > + > This identity has been obsoleted: the + > 'svec-of-minimize-load-most-loaded-link' identity SHOULD + > be used instead."; + 1033c1239 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; - 1035a1172,1174 + 1035a1242,1244 > // CHANGE NOTE: The identity of-minimize-cost-path-set > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1037a1177 + 1037a1247 > status obsolete; - 1216a1357,1368 + 1039c1249,1253 + < "Objective function for minimizing the cost on a path set."; + --- + > "Objective function for minimizing the cost on a path set. + > + > This identity has been obsoleted: the + > 'svec-of-minimize-cost-path-set' identity SHOULD + > be used instead."; + 1049a1264,1266 + > // CHANGE NOTE: The reference of the identity path-locally-computed + > // below has been updated in this module revision + > // RFC Editor: remove the note above and this note + 1056,1057c1273,1274 + < "RFC 3272: Overview and Principles of Internet Traffic + < Engineering, Section 5.4"; + --- + > "RFC 9522: Overview and Principles of Internet Traffic + > Engineering, Section 4.4"; + 1059a1277,1280 + > // CHANGE NOTE: The reference of the identity + > // path-externally-queried below has been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + 1071c1292 + < "RFC 3272: Overview and Principles of Internet Traffic + --- + > "RFC 9522: Overview and Principles of Internet Traffic + 1072a1294 + > + 1076a1299,1302 + > // CHANGE NOTE: The reference of the identity + > // path-explicitly-defined below has been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + 1085c1311,1312 + < RFC 3272: Overview and Principles of Internet Traffic + --- + > + > RFC 9522: Overview and Principles of Internet Traffic + 1216a1444,1455 > // CHANGE NOTE: The identity tunnel-admin-state-auto below > // has been added in this module revision > // RFC Editor: remove the note above and this note @@ -219,7 +343,7 @@ > when it is not used by the client layer."; > } > - 1321a1474,1482 + 1321a1561,1569 > // CHANGE NOTE: The identity lsp-restoration-restore-none > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -229,7 +353,7 @@ > "No LSP affected by a failure is restored."; > } > - 1339a1501,1515 + 1339a1588,1602 > // CHANGE NOTE: The identity restoration-scheme-rerouting > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -245,13 +369,13 @@ > for Generalized Multi-Protocol Label Switching (GMPLS)"; > } > - 1383a1560,1562 + 1383a1647,1649 > // CHANGE NOTE: The identity lsp-protection-reroute-extra > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1385a1565 + 1385a1652 > status obsolete; - 1387c1567,1571 + 1387c1654,1658 < "'(Full) Rerouting' LSP protection type."; --- > "'(Full) Rerouting' LSP protection type. @@ -259,13 +383,13 @@ > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; - 1392a1577,1579 + 1392a1664,1666 > // CHANGE NOTE: The identity lsp-protection-reroute > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1394a1582 + 1394a1669 > status obsolete; - 1396c1584,1588 + 1396c1671,1675 < "'Rerouting without Extra-Traffic' LSP protection type."; --- > "'Rerouting without Extra-Traffic' LSP protection type. @@ -273,46 +397,327 @@ > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; - 1628a1821,1824 + 1628a1908,1911 > // CHANGE NOTE: The description and reference of the > // identity action-exercise have been updated in this module > // revision > // RFC Editor: remove the note above and this note - 1632,1633c1828,1830 + 1632,1633c1915,1917 < "An action that starts testing whether or not APS communication < is operating correctly. It is of lower priority than any --- > "An action that starts testing whether or not Automatic > Protection Switching (APS) communication is operating > correctly. It is of lower priority than any - 1636,1637c1833,1834 + 1636,1637c1920,1921 < "RFC 4427: Recovery (Protection and Restoration) Terminology < for Generalized Multi-Protocol Label Switching (GMPLS)"; --- > "ITU-T G.808.1 v4.0 (05/2014): Generic protection switching - > Linear trail and subnetwork protection"; - 1916a2114,2116 - > // CHANGE NOTE: The description of the identity path-metric-type - > // has been updated in this module revision + 1917c2201,2204 + < identity path-metric-type { + --- + > // CHANGE NOTE: The path-metric-optimization-type base identity + > // has been added in this module revision > // RFC Editor: remove the note above and this note - 1919c2119,2122 + > identity path-metric-optimization-type { + 1919c2206,2207 < "Base identity for the path metric type."; --- - > "Base identity for the path metric type. - > - > Derived identities SHOULD describe the unit and maximum value - > of the path metric types they define."; - 1939a2143,2145 - > // CHANGE NOTE: The reference for the identity path-metric-hop + > "Base identity used to define the path metric optimization + > types."; + 1922,1923c2210,2213 + < identity path-metric-te { + < base path-metric-type; + --- + > // CHANGE NOTE: The link-path-metric-type base identity > // has been added in this module revision > // RFC Editor: remove the note above and this note - 1943a2150,2152 - > reference - > "RFC5440: Path Computation Element (PCE) Communication - > Protocol (PCEP)"; - 1945a2155 + > identity link-path-metric-type { + 1925,1928c2215,2221 + < "TE path metric."; + < reference + < "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a + < second MPLS Traffic Engineering (TE) Metric"; + --- + > "Base identity used to define the link and the path metric + > types. + > + > The unit of the path metric value is interpreted in the + > context of the path metric type and the derived identities + > SHOULD describe the unit of the path metric types they + > define."; + 1931,1938c2224,2232 + < identity path-metric-igp { + < base path-metric-type; + < description + < "IGP path metric."; + < reference + < "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a + < second MPLS Traffic Engineering (TE) Metric"; + < } + --- + > // CHANGE NOTE: The link-metric-type base identity + > // and its derived identities + > // have been added in this module revision + > // RFC Editor: remove the note above and this note + > identity link-metric-type { + > base link-path-metric-type; + > description + > "Base identity for the link metric types."; + > } + 1940,1944c2234,2240 + < identity path-metric-hop { + < base path-metric-type; + < description + < "Hop path metric."; + < } + --- + > identity link-metric-te { + > base link-metric-type; + > description + > "Traffic Engineering (TE) Link Metric."; + > reference + > "RFC 3630: Traffic Engineering (TE) Extensions to OSPF + > Version 2, section 2.5.5 + 1946,1952c2242,2244 + < identity path-metric-delay-average { + < base path-metric-type; + < description + < "Average unidirectional link delay."; + < reference + < "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; + < } + --- + > RFC 5305: IS-IS Extensions for Traffic Engineering, + > section 3.7"; + > } + 1954,1960c2246,2253 + < identity path-metric-delay-minimum { + < base path-metric-type; + < description + < "Minimum unidirectional link delay."; + < reference + < "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; + < } + --- + > identity link-metric-igp { + > base link-metric-type; + > description + > "Interior Gateway Protocol (IGP) Link Metric."; + > reference + > "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric + > as a second MPLS Traffic Engineering (TE) Metric"; + > } + 1962,1972c2255,2266 + < identity path-metric-residual-bandwidth { + < base path-metric-type; + < description + < "Unidirectional Residual Bandwidth, which is defined to be + < Maximum Bandwidth (RFC 3630) minus the bandwidth currently + < allocated to LSPs."; + < reference + < "RFC 3630: Traffic Engineering (TE) Extensions to OSPF + < Version 2 + < RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; + < } + --- + > identity link-metric-delay-average { + > base link-metric-type; + > description + > "Unidirectional Link Delay, measured in units of + > microseconds."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.1 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.1"; + > } + 1974,1979c2268,2279 + < identity path-metric-optimize-includes { + < base path-metric-type; + < description + < "A metric that optimizes the number of included resources + < specified in a set."; + < } + --- + > identity link-metric-delay-minimum { + > base link-metric-type; + > description + > "Minimum unidirectional Link Delay, measured in units of + > microseconds."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.2 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.2"; + > } + 1981,1986c2281,2425 + < identity path-metric-optimize-excludes { + < base path-metric-type; + < description + < "A metric that optimizes to a maximum the number of excluded + < resources specified in a set."; + < } + --- + > identity link-metric-delay-maximum { + > base link-metric-type; + > description + > "Maximum unidirectional Link Delay, measured in units of + > microseconds."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.2 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.2"; + > } > - 2110a2321,2724 + > identity link-metric-residual-bandwidth { + > base link-metric-type; + > description + > "Unidirectional Residual Bandwidth, measured in units of + > bytes per second. + > + > It is defined to be Maximum Bandwidth minus the bandwidth + > currently allocated to LSPs."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.5 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.5"; + > } + > + > // CHANGE NOTE: The base and the description of the + > // path-metric-type identity + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-type { + > base link-path-metric-type; + > base path-metric-optimization-type; + > description + > "Base identity for the path metric types."; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-te identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-te { + > base path-metric-type; + > description + > "Traffic Engineering (TE) Path Metric."; + > reference + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.8"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-igp identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-igp { + > base path-metric-type; + > description + > "Interior Gateway Protocol (IGP) Path Metric."; + > reference + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.8"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-hop identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-hop { + > base path-metric-type; + > description + > "Hop Count Path Metric."; + > reference + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.8"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-delay-average identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-delay-average { + > base path-metric-type; + > description + > "The Path Delay Metric, measured in units of + > microseconds."; + > reference + > "RFC8233: Extensions to the Path Computation Element + > Communication Protocol (PCEP) to Compute Service-Aware + > Label Switched Paths (LSPs), section 3.1.1"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-delay-minimum identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-delay-minimum { + > base path-metric-type; + > description + > "The Path Min Delay Metric, measured in units of + > microseconds."; + > reference + > "I-D.ietf-pce-sid-algo: Carrying SR-Algorithm information + > in PCE-based Networks, section 3.5.1"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-residual-bandwidth identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-residual-bandwidth { + > base path-metric-type; + > description + > "The Path Residual Bandwidth, defined as the minimum Link + > Residual Bandwidth all the links along the path. + > + > The Path Residual Bandwidth can be seen as the path + > metric associated with the Maximum residual Bandwidth Path + > (MBP) objective function."; + > reference + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; + > } + > + > // CHANGE NOTE: The base of the path-metric-optimize-includes + > // identity has been updated in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-optimize-includes { + > base path-metric-optimization-type; + > description + > "A metric that optimizes the number of included resources + > specified in a set."; + > } + > + > // CHANGE NOTE: The base of the path-metric-optimize-excludes + > // identity has been updated in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-optimize-excludes { + > base path-metric-optimization-type; + > description + > "A metric that optimizes to a maximum the number of excluded + > resources specified in a set."; + > } + 2049a2489,2492 + > // CHANGE NOTE: The reference of the identity + > // te-optimization-criterion below has been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + 2054c2497 + < "RFC 3272: Overview and Principles of Internet Traffic + --- + > "RFC 9522: Overview and Principles of Internet Traffic + 2110a2554,2994 > // CHANGE NOTE: The base identity path-computation-error-reason > // and its derived identities below have been > // added in this module revision @@ -328,8 +733,8 @@ > "Path computation has failed because of an unspecified > reason."; > reference - > "Section 7.5 of RFC5440: Path Computation Element (PCE) - > Communication Protocol (PCEP)"; + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.5"; > } > > identity path-computation-error-no-topology { @@ -349,7 +754,13 @@ > a Backward-Recursive Path Computation (BRPC) downstream > PCE or a child PCE."; > reference - > "RFC5441, RFC8685"; + > "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + > Procedure to Compute Shortest Constrained Inter-Domain + > Traffic Engineering Label Switched Paths + > + > RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture"; > } > > identity path-computation-error-pce-unavailable { @@ -360,10 +771,11 @@ > It corresponds to bit 31 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5440: Path Computation Element (PCE) Communication - > Protocol (PCEP); + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP) > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-inclusion-hop { @@ -382,9 +794,12 @@ > It corresponds to bit 19 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-resource { @@ -396,9 +811,12 @@ > It corresponds to bit 20 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-child-pce-unresponsive { @@ -410,9 +828,12 @@ > It corresponds to bit 21 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-domain-unknown { @@ -424,9 +845,12 @@ > It corresponds to bit 22 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-p2mp { @@ -438,9 +862,12 @@ > It corresponds to bit 24 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8306; + > "RFC 8306: Extensions to the Path Computation Element + > Communication Protocol (PCEP) for Point-to-Multipoint + > Traffic Engineering Label Switched Paths > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-migration { @@ -452,9 +879,12 @@ > It corresponds to bit 26 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5557; + > "RFC 5557: Path Computation Element Communication Protocol + > (PCEP) Requirements and Protocol Extensions in Support of + > Global Concurrent Optimization > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-solution { @@ -466,9 +896,12 @@ > It corresponds to bit 25 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5557; + > "RFC 5557: Path Computation Element Communication Protocol + > (PCEP) Requirements and Protocol Extensions in Support of + > Global Concurrent Optimization > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-pks-expansion { @@ -480,9 +913,12 @@ > It corresponds to bit 27 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5520; + > "RFC 5520: Preserving Topology Confidentiality in + > Inter-Domain Path Computation Using a Path-Key-Based + > Mechanism > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-brpc-chain-unavailable { @@ -494,9 +930,12 @@ > It corresponds to bit 28 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5441; + > "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + > Procedure to Compute Shortest Constrained Inter-Domain + > Traffic Engineering Label Switched Paths > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-source-unknown { @@ -508,10 +947,11 @@ > It corresponds to bit 29 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-unknown { @@ -523,10 +963,11 @@ > It corresponds to bit 30 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-server { @@ -535,10 +976,11 @@ > "Path computation has failed because path computation > server is unavailable."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > // CHANGE NOTE: The base identity protocol-origin-type and @@ -563,7 +1005,7 @@ > "Protocol origin is Path Computation Engine Protocol > (PCEP)."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP)"; > } > @@ -571,7 +1013,7 @@ > base protocol-origin-type; > description > "Protocol origin is Border Gateway Protocol (BGP)."; - > reference "RFC9012"; + > reference "RFC 9012"; > } > > // CHANGE NOTE: The base identity svec-objective-function-type @@ -582,8 +1024,8 @@ > description > "Base identity for SVEC objective function type."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-agg-bandwidth-consumption { @@ -592,8 +1034,8 @@ > "Objective function for minimizing aggregate bandwidth > consumption (MBC)."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-load-most-loaded-link { @@ -602,8 +1044,8 @@ > "Objective function for minimizing the load on the link that > is carrying the highest load (MLL)."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-cost-path-set { @@ -612,8 +1054,8 @@ > "Objective function for minimizing the cost on a path set > (MCC)."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-common-transit-domain { @@ -622,9 +1064,9 @@ > "Objective function for minimizing the number of common > transit domains (MCTD)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation - > Element (H-PCE) Architecture."; + > Element (H-PCE) Architecture"; > } > > identity svec-of-minimize-shared-link { @@ -633,7 +1075,7 @@ > "Objective function for minimizing the number of shared > links (MSL)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -644,7 +1086,7 @@ > "Objective function for minimizing the number of shared > Shared Risk Link Groups (SRLG) (MSS)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -655,7 +1097,7 @@ > "Objective function for minimizing the number of shared > nodes (MSN)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -668,35 +1110,35 @@ > description > "Base identity for SVEC metric type."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - > identity svec-metric-cumul-te { + > identity svec-metric-cumulative-te { > base svec-metric-type; > description > "Cumulative TE cost."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - > identity svec-metric-cumul-igp { + > identity svec-metric-cumulative-igp { > base svec-metric-type; > description > "Cumulative IGP cost."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - > identity svec-metric-cumul-hop { + > identity svec-metric-cumulative-hop { > base svec-metric-type; > description > "Cumulative Hop path metric."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-aggregate-bandwidth-consumption { @@ -704,8 +1146,8 @@ > description > "Aggregate bandwidth consumption."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-load-of-the-most-loaded-link { @@ -713,15 +1155,29 @@ > description > "Load of the most loaded link."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - 2506a3121,3123 + 2221,2225c3105,3111 + < "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions + < RFC 7823: Performance-Based Path Selection for Explicitly + < Routed Label Switched Paths (LSPs) Using TE Metric + < Extensions + < RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + --- + > "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensionsù + > + > RFC 7823: Performance-Based Path Selection for Explicitly + > Routed Label Switched Paths (LSPs) Using TE Metric + > Extensions + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + 2506a3393,3395 > // CHANGE NOTE: The explicit-route-hop grouping below has been > // updated in this module revision > // RFC Editor: remove the note above and this note - 2514a3132,3140 + 2514a3404,3412 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; @@ -731,9 +1187,9 @@ > description > "The identifier of a node in the topology."; > } - 2517d3142 + 2517d3414 < mandatory true; - 2566a3192,3202 + 2566a3464,3474 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description @@ -745,30 +1201,34 @@ > description > "Link Termination Point (LTP) identifier."; > } - 2569d3204 + 2569d3476 < mandatory true; - 2574a3210,3214 + 2574a3482,3486 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } - 2577d3216 + 2577d3488 < mandatory true; - 2646a3286,3289 + 2631a3543,3545 + > // CHANGE NOTE: The explicit-route-hop grouping below has been + > // updated in this module revision + > // RFC Editor: remove the note above and this note + 2646a3561,3564 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; > } - 2648a3292,3296 + 2648a3567,3571 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } - 2651d3298 + 2651d3573 < mandatory true; - 2696a3344,3354 + 2696a3619,3629 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description @@ -780,44 +1240,103 @@ > description > "Link Termination Point (LTP) identifier."; > } - 2699d3356 + 2699d3631 < mandatory true; - 2704a3362,3366 + 2704a3637,3641 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } - 2968a3631,3635 + 2881a3819,3821 + > // CHANGE NOTE: The grouping optimization-metric-entry below has + > // been updated in this module revision + > // RFC Editor: remove the note above and this note + 2887c3827 + < base path-metric-type; + --- + > base path-metric-optimization-type; + 2964a3905,3907 + > // CHANGE NOTE: The grouping tunnel-constraints below has + > // been updated in this module revision + > // RFC Editor: remove the note above and this note + 2968a3912,3916 > leaf network-id { > type nw:network-id; > description > "The network topology identifier."; > } - 2977c3644,3647 + 2972a3921,3923 + > // CHANGE NOTE: The grouping path-constraints-route-objects below + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + 2977c3928 < container explicit-route-objects-always { --- - > // CHANGE NOTE: The explicit-route-objects container below has - > // been updated in this module revision - > // RFC Editor: remove the note above and this note > container explicit-route-objects { - 2979c3649 + 2979c3930 < "Container for the 'exclude route' object list."; --- > "Container for the explicit route object lists."; - 3124,3126c3794,3800 + 3101a4053,4055 + > // CHANGE NOTE: The grouping generic-path-metric-bounds below + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + 3107c4061 + < "TE path metric bounds container."; + --- + > "Top-level container for the list of path metric bounds."; + 3111c4065,4073 + < "List of TE path metric bounds."; + --- + > "List of path metric bounds, which can apply to link and + > path metrics. + > + > TE paths which have at least one path metric which + > exceeds the specified bounds MUST NOT be selected. + > + > TE paths that traverse TE links which have at least one + > link metric which exceeds the specified bounds MUST NOT + > be selected."; + 3114c4076 + < base path-metric-type; + --- + > base link-path-metric-type; + 3124,3126c4086,4092 < "Upper bound on the end-to-end TE path metric. A zero < indicates an unbounded upper limit for the specific < 'metric-type'."; --- - > "Upper bound on the end-to-end TE path metric. + > "Upper bound on the specified 'metric-type'. > > A zero indicates an unbounded upper limit for the - > specific 'metric-type'. + > specificied 'metric-type'. > > The unit of is interpreted in the context of the - > path-metric-type."; - 3379c4053,4112 + > 'metric-type' identity."; + 3131a4098,4100 + > // CHANGE NOTE: The grouping generic-path-metric-bounds below + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + 3154c4123,4127 + < "Container for the list of tiebreakers."; + --- + > "Container for the list of tiebreakers. + > + > This container has been obsoleted by the tiebreaker + > leaf."; + > status deprecated; + 3189a4163,4171 + > leaf tiebreaker { + > type identityref { + > base path-tiebreaker-type; + > } + > default "te-types:path-tiebreaker-random"; + > description + > "The tiebreaker criteria to apply on an equally favored set + > of paths, in order to pick the best."; + > } + 3379c4361,4420 < } \ No newline at end of file --- @@ -836,7 +1355,7 @@ > description > "LSP encoding type."; > reference - > "RFC3945"; + > "RFC 3945"; > } > leaf switching-type { > type identityref { @@ -845,7 +1364,7 @@ > description > "LSP switching type."; > reference - > "RFC3945"; + > "RFC 3945"; > } > } > diff --git a/drafts/te-types-update/draft-ietf-teas-rfc8776-update.md b/drafts/te-types-update/draft-ietf-teas-rfc8776-update.md index 1c1efc9..c51a456 100644 --- a/drafts/te-types-update/draft-ietf-teas-rfc8776-update.md +++ b/drafts/te-types-update/draft-ietf-teas-rfc8776-update.md @@ -4,7 +4,7 @@ coding: utf-8 title: Common YANG Data Types for Traffic Engineering abbrev: TE Common YANG Types -docname: draft-ietf-teas-rfc8776-update-09 +docname: draft-ietf-teas-rfc8776-update-10 obsoletes: 8776 submissiontype: IETF workgroup: TEAS Working Group @@ -70,7 +70,7 @@ informative: --- abstract -This document defines a collection of common data types and groupings in YANG data modeling language. These derived common types and groupings are intended to be imported by modules that model Traffic Engineering (TE) configuration and state capabilities. This document obsoletes RFC 8776. +This document defines a collection of common data types, identities, and groupings in YANG data modeling language. These derived common types and groupings are intended to be imported by modules that model Traffic Engineering (TE) configuration and state capabilities. This document obsoletes RFC 8776. --- middle @@ -78,15 +78,9 @@ This document defines a collection of common data types and groupings in YANG da YANG {{!RFC6020}} {{!RFC7950}} is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols such as the Network Configuration Protocol (NETCONF) {{!RFC6241}}. The YANG language supports a small set of built-in data types and provides mechanisms to derive other types from the built-in types. -This document introduces a collection of common data types derived from the built-in YANG data types. The derived types and groupings are designed to be the common types applicable for modeling Traffic Engineering (TE) features in model(s) defined outside of this document. +This document introduces a collection of common data types derived from the built-in YANG data types. The derived data types, identities, and groupings are designed to be the common definitions applicable for modeling Traffic Engineering (TE) features in model(s) defined outside of this document. -This document adds few additional common data types, identities, and groupings to both the "ietf-te-types" and the "ietf-te-packet-types" YANG models and obsoletes {{!RFC8776}}. - -For further details, see the revision statements of the YANG modules in Sections X and Y or the summary in Appendix A. - -CHANGE NOTE: These definitions have been developed in {{?I-D.ietf-teas-yang-te}}, {{?I-D.ietf-teas-yang-path-computation}} and {{?I-D.ietf-teas-yang-l3-te-topo}} and are quite mature: {{?I-D.ietf-teas-yang-te}} and {{?I-D.ietf-teas-yang-path-computation}} in particular are in WG Last Call and some definitions have been moved to this document as part of WG LC comments resolution. - -RFC Editor: remove the CHANGE NOTE above and this note +This document adds new common data types, identities, and groupings to both the "ietf-te-types" and the "ietf-te-packet-types" YANG models and obsoletes {{!RFC8776}}. For further details, see the revision statements of the YANG modules in {{te-yang-code}} and {{pkt-yang-code}}, or the summary in {{changes-bis}}. ## Requirements Notation @@ -553,7 +547,195 @@ RFC Editor: Please replace XXXX with the RFC number assigned to this document. # Changes from RFC 8776 -To be added in a future revision of this draft. +This version adds new common data types, identities, and groupings to the YANG modules. It also updates some of the existing data types, identities, and groupings in the YANG modules and fixes few bugs in {{!RFC8776}}. + +The following new identities have been added to the 'ietf-te-types' module: + +- lsp-provisioning-error-reason; + +- association-type-diversity; + +- tunnel-admin-state-auto; + +- lsp-restoration-restore-none; + +- restoration-scheme-rerouting; + +- path-metric-optimization-type; + +- link-path-metric-type; + +- link-metric-type and its derived identities; + +- path-computation-error-reason and its derived identities; + +- protocol-origin-type and its derived identities; + +- svec-objective-function-type and its derived identities; + +- svec-metric-type and its derived identities. + +The following new data types have been added to the 'ietf-te-types' module: + +- path-type; + +- te-gen-node-id. + +The following new groupings have been added to the 'ietf-te-types' module: + +- encoding-and-switching-type; + +- te-generic-node-id. + +The following new identities have been added to the 'ietf-te-packet-types' module: + +- bandwidth-profile-type; + +- link-metric-delay-variation; + +- link-metric-loss; + +- path-metric-delay-variation; + +- path-metric-loss. + +The following new groupings have been added to the 'ietf-te-packet-types' module: + +- te-packet-path-bandwidth; + +- te-packet-link-bandwidth. + +The following identities, already defined in {{!RFC8776}}, have been updated in the 'ietf-te-types' module: + +- objective-function-type (editorial); + +- action-exercise (bug fix); + +- path-metric-type: + + new base identities have been added; + +- path-metric-te (bug fix); + +- path-metric-igp (bug fix); + +- path-metric-hop (bug fix); + +- path-metric-delay-average (bug fix); + +- path-metric-delay-minimum (bug fix); + +- path-metric-residual-bandwidth (bug fix); + +- path-metric-optimize-includes (bug fix); + +- path-metric-optimize-excludes (bug fix); + +- te-optimization-criterion (editorial). + +The following data type, already defined in {{!RFC8776}}, has been updated in the 'ietf-te-types' module: + +- te-node-id; + + The data type has been changed to be a union. + +The following groupings, already defined in {{!RFC8776}}, have been updated in the 'ietf-te-types' module: + +- explicit-route-hop + + The following new leaves have been added to the 'explicit-route-hop' grouping: + + - node-id-uri; + + - link-tp-id-uri; + + The following leaves, already defined in {{!RFC8776}}, have been updated in the 'explicit-route-hop': + + - node-id; + + - link-tp-id. + + The mandatory true statements for the node-id and link-tp-id have been replaced by must statements that requires at least the presence of: + + - node-id or node-id-uri; + + - link-tp-id or link-tp-id-uri. + +- explicit-route-hop + + The following new leaves have been added to the 'explicit-route-hop' grouping: + + - node-id-uri; + + - link-tp-id-uri; + + The following leaves, already defined in {{!RFC8776}}, have been updated in the 'explicit-route-hop': + + - node-id; + + - link-tp-id. + + The mandatory true statements for the node-id and link-tp-id have been replaced by must statements that requires at least the presence of: + + - node-id or node-id-uri; + + - link-tp-id or link-tp-id-uri. + +- optimization-metric-entry: + + The following leaves, already defined in {{!RFC8776}}, have been updated in the 'optimization-metric-entry': + + - metric-type; + + The base identity has been updated without impacting the set of derived identities that are allowed. + +- tunnel-constraints; + + The following new leaf have been added to the 'tunnel-constraints' grouping: + + - network-id; + +- path-constraints-route-objects: + + The following container, already defined in {{!RFC8776}}, has been updated in the 'path-constraints-route-objects': + + - explicit-route-objects-always; + + The container has been renamed as 'explicit-route-objects'. This change is not affecting any IETF standard YANG models since this grouping has not yet been used by any YANG model defined in existing IETF RFCs. + +- generic-path-metric-bounds: + + The following leaves, already defined in {{!RFC8776}}, have been updated in the 'optimization-metric-entry': + + - metric-type; + + The base identity has been updated to: + + - increase the set of derived identities that are allowed and; + + - remove from this set the 'path-metric-optimize-includes' and the 'path-metric-optimize-excludes' identities (bug fixing) + +- generic-path-optimization + + The following new leaf have been added to the 'generic-path-optimization' grouping: + + - tiebreaker; + + The following container, already defined in {{!RFC8776}}, has been deprecated: + + - tiebreakers. + +The following identities, already defined in {{!RFC8776}}, have been obsoletes in the 'ietf-te-types' module for bug fixing: + +- of-minimize-agg-bandwidth-consumption; + +- of-minimize-load-most-loaded-link; + +- of-minimize-cost-path-set; + +- lsp-protection-reroute-extra; + +- lsp-protection-reroute. {: #te-yang-diff} diff --git a/drafts/te-types-update/draft-ietf-teas-rfc8776-update.txt b/drafts/te-types-update/draft-ietf-teas-rfc8776-update.txt index 492aac2..780c2f0 100644 --- a/drafts/te-types-update/draft-ietf-teas-rfc8776-update.txt +++ b/drafts/te-types-update/draft-ietf-teas-rfc8776-update.txt @@ -6,25 +6,25 @@ TEAS Working Group I. Busi Internet-Draft Huawei Obsoletes: 8776 (if approved) A. Guo Intended status: Standards Track Futurewei Technologies -Expires: 1 August 2024 X. Liu +Expires: 20 August 2024 X. Liu Alef Edge T. Saad Cisco Systems Inc. I. Bryskin Individual - 29 January 2024 + 17 February 2024 Common YANG Data Types for Traffic Engineering - draft-ietf-teas-rfc8776-update-09 + draft-ietf-teas-rfc8776-update-10 Abstract - This document defines a collection of common data types and groupings - in YANG data modeling language. These derived common types and - groupings are intended to be imported by modules that model Traffic - Engineering (TE) configuration and state capabilities. This document - obsoletes RFC 8776. + This document defines a collection of common data types, identities, + and groupings in YANG data modeling language. These derived common + types and groupings are intended to be imported by modules that model + Traffic Engineering (TE) configuration and state capabilities. This + document obsoletes RFC 8776. Status of This Memo @@ -41,7 +41,7 @@ Status of This Memo 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 1 August 2024. + This Internet-Draft will expire on 20 August 2024. Copyright Notice @@ -53,9 +53,9 @@ Copyright Notice -Busi, et al. Expires 1 August 2024 [Page 1] +Busi, et al. Expires 20 August 2024 [Page 1] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 This document is subject to BCP 78 and the IETF Trust's Legal @@ -80,19 +80,19 @@ Table of Contents 3.1.2. Protocol Origin . . . . . . . . . . . . . . . . . . . 11 3.2. Packet TE Types Module Contents . . . . . . . . . . . . . 11 4. TE Types YANG Module . . . . . . . . . . . . . . . . . . . . 13 - 5. Packet TE Types YANG Module . . . . . . . . . . . . . . . . . 99 - 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 114 - 7. Security Considerations . . . . . . . . . . . . . . . . . . . 114 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 115 - 8.1. Normative References . . . . . . . . . . . . . . . . . . 115 - 8.2. Informative References . . . . . . . . . . . . . . . . . 117 - Appendix A. Changes from RFC 8776 . . . . . . . . . . . . . . . 125 - A.1. TE Types YANG Diffs . . . . . . . . . . . . . . . . . . . 125 - A.2. Packet TE Types YANG Diffs . . . . . . . . . . . . . . . 144 - Appendix B. Option Considered for updating RFC8776 . . . . . . . 150 - Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 151 - Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 151 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 151 + 5. Packet TE Types YANG Module . . . . . . . . . . . . . . . . . 105 + 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 120 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 121 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 121 + 8.1. Normative References . . . . . . . . . . . . . . . . . . 121 + 8.2. Informative References . . . . . . . . . . . . . . . . . 124 + Appendix A. Changes from RFC 8776 . . . . . . . . . . . . . . . 131 + A.1. TE Types YANG Diffs . . . . . . . . . . . . . . . . . . . 135 + A.2. Packet TE Types YANG Diffs . . . . . . . . . . . . . . . 165 + Appendix B. Option Considered for updating RFC8776 . . . . . . . 171 + Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 172 + Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 172 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 172 1. Introduction @@ -109,32 +109,22 @@ Table of Contents -Busi, et al. Expires 1 August 2024 [Page 2] +Busi, et al. Expires 20 August 2024 [Page 2] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 This document introduces a collection of common data types derived - from the built-in YANG data types. The derived types and groupings - are designed to be the common types applicable for modeling Traffic - Engineering (TE) features in model(s) defined outside of this - document. - - This document adds few additional common data types, identities, and - groupings to both the "ietf-te-types" and the "ietf-te-packet-types" - YANG models and obsoletes [RFC8776]. - - For further details, see the revision statements of the YANG modules - in Sections X and Y or the summary in Appendix A. - - CHANGE NOTE: These definitions have been developed in - [I-D.ietf-teas-yang-te], [I-D.ietf-teas-yang-path-computation] and - [I-D.ietf-teas-yang-l3-te-topo] and are quite mature: - [I-D.ietf-teas-yang-te] and [I-D.ietf-teas-yang-path-computation] in - particular are in WG Last Call and some definitions have been moved - to this document as part of WG LC comments resolution. + from the built-in YANG data types. The derived data types, + identities, and groupings are designed to be the common definitions + applicable for modeling Traffic Engineering (TE) features in model(s) + defined outside of this document. - RFC Editor: remove the CHANGE NOTE above and this note + This document adds new common data types, identities, and groupings + to both the "ietf-te-types" and the "ietf-te-packet-types" YANG + models and obsoletes [RFC8776]. For further details, see the + revision statements of the YANG modules in Section 4 and Section 5, + or the summary in Appendix A. 1.1. Requirements Notation @@ -155,21 +145,6 @@ Internet-Draft TE Common YANG Types January 2024 are prefixed using the standard prefix associated with the corresponding YANG imported modules, as shown in Table 1. - - - - - - - - - - -Busi, et al. Expires 1 August 2024 [Page 3] - -Internet-Draft TE Common YANG Types January 2024 - - +=================+======================+===========+ | Prefix | YANG module | Reference | +=================+======================+===========+ @@ -186,6 +161,15 @@ Internet-Draft TE Common YANG Types January 2024 Table 1: Prefixes and corresponding YANG modules + + + + +Busi, et al. Expires 20 August 2024 [Page 3] + +Internet-Draft TE Common YANG Types February 2024 + + RFC Editor: Please replace XXXX with the RFC number assigned to this document. @@ -219,13 +203,6 @@ Internet-Draft TE Common YANG Types January 2024 Traffic Engineering - - -Busi, et al. Expires 1 August 2024 [Page 4] - -Internet-Draft TE Common YANG Types January 2024 - - DS-TE: Differentiated Services Traffic Engineering @@ -242,6 +219,13 @@ Internet-Draft TE Common YANG Types January 2024 Automatic Protection Switching + + +Busi, et al. Expires 20 August 2024 [Page 4] + +Internet-Draft TE Common YANG Types February 2024 + + SD: Signal Degrade @@ -274,14 +258,6 @@ Internet-Draft TE Common YANG Types January 2024 The "ietf-te-types" module contains the following YANG reusable types and groupings: - - - -Busi, et al. Expires 1 August 2024 [Page 5] - -Internet-Draft TE Common YANG Types January 2024 - - te-bandwidth: A YANG grouping that defines the generic TE bandwidth. The @@ -297,6 +273,15 @@ Internet-Draft TE Common YANG Types January 2024 performance-metrics-attributes: + + + + +Busi, et al. Expires 20 August 2024 [Page 5] + +Internet-Draft TE Common YANG Types February 2024 + + A YANG grouping that defines one-way and two-way measured Performance Metrics (PM) and indications of anomalies on link(s) or the path as defined in [RFC7471], [RFC8570], and [RFC7823]. @@ -330,14 +315,6 @@ Internet-Draft TE Common YANG Types January 2024 te-node-id: - - - -Busi, et al. Expires 1 August 2024 [Page 6] - -Internet-Draft TE Common YANG Types January 2024 - - A type representing the identifier for a node in a TE topology. The identifier is represented as 4 octets in dotted-quad notation. This attribute MAY be mapped to the Router Address TLV described @@ -350,6 +327,17 @@ Internet-Draft TE Common YANG Types January 2024 te-topology-id: + + + + + + +Busi, et al. Expires 20 August 2024 [Page 6] + +Internet-Draft TE Common YANG Types February 2024 + + A type representing the identifier for a topology. It is optional to have one or more prefixes at the beginning, separated by colons. The prefixes can be "network-types" as defined in the @@ -387,13 +375,6 @@ Internet-Draft TE Common YANG Types January 2024 An enumerated type for the different statuses of a recovery action as defined in [RFC4427] and [RFC6378]. - - -Busi, et al. Expires 1 August 2024 [Page 7] - -Internet-Draft TE Common YANG Types January 2024 - - path-attribute-flags: A base YANG identity for supported LSP path flags as defined in @@ -406,6 +387,13 @@ Internet-Draft TE Common YANG Types January 2024 A base YANG identity for supported link protection types as defined in [RFC4872] and [RFC4427]. + + +Busi, et al. Expires 20 August 2024 [Page 7] + +Internet-Draft TE Common YANG Types February 2024 + + restoration-scheme-type: A base YANG identity for supported LSP restoration schemes as @@ -442,14 +430,6 @@ Internet-Draft TE Common YANG Types January 2024 to be used only for path objective functions and a new svec- objective-function-type identity has been added for the Synchronization VECtor (SVEC) objective functions. Therefore the of- - - - -Busi, et al. Expires 1 August 2024 [Page 8] - -Internet-Draft TE Common YANG Types January 2024 - - minimize-agg-bandwidth-consumption, of-minimize-load-most-loaded-link and of-minimize-cost-path-set identities, defined in [RFC5541] and derived from the objective-function-type identity, have been @@ -463,6 +443,13 @@ Internet-Draft TE Common YANG Types January 2024 A base YANG identity for supported TE tunnel types as defined in [RFC3209] and [RFC4875]. + + +Busi, et al. Expires 20 August 2024 [Page 8] + +Internet-Draft TE Common YANG Types February 2024 + + lsp-encoding-types: A base YANG identity for supported LSP encoding types as defined @@ -498,14 +485,6 @@ Internet-Draft TE Common YANG Types January 2024 the path metric type. The derived identities SHOULD describe the unit and maximum value of the path metric types they define. - - - -Busi, et al. Expires 1 August 2024 [Page 9] - -Internet-Draft TE Common YANG Types January 2024 - - For example, the bound of the 'path-metric-loss', defined in 'ietf-te-packet-types', is defined in multiples of the basic unit 0.000003% as described in [RFC7471] and [RFC8570]. @@ -520,6 +499,13 @@ Internet-Draft TE Common YANG Types January 2024 An enumerated type for the different TE link access types as defined in [RFC3630]. + + +Busi, et al. Expires 20 August 2024 [Page 9] + +Internet-Draft TE Common YANG Types February 2024 + + CHANGE NOTE: The module "ietf-te-types" has been updated to add the following YANG identities, types and groupings. @@ -553,15 +539,6 @@ Internet-Draft TE Common YANG Types January 2024 encoding-and-switching-type: - - - - -Busi, et al. Expires 1 August 2024 [Page 10] - -Internet-Draft TE Common YANG Types January 2024 - - This is a common grouping to define the LSP encoding and switching types. @@ -577,6 +554,14 @@ Internet-Draft TE Common YANG Types January 2024 RFC Editor: remove the two CHANGE NOTEs above and this note + + + +Busi, et al. Expires 20 August 2024 [Page 10] + +Internet-Draft TE Common YANG Types February 2024 + + 3.1.1. Path Computation Errors The "ietf-te-types" module contains the YANG reusable identities for @@ -609,15 +594,6 @@ Internet-Draft TE Common YANG Types January 2024 The "ietf-te-packet-types" module (Section 5) covers the common types and groupings that are specific to packet technology. - - - - -Busi, et al. Expires 1 August 2024 [Page 11] - -Internet-Draft TE Common YANG Types January 2024 - - The "ietf-te-packet-types" module contains the following YANG reusable types and groupings: @@ -633,6 +609,15 @@ Internet-Draft TE Common YANG Types January 2024 bc-type: + + + + +Busi, et al. Expires 20 August 2024 [Page 11] + +Internet-Draft TE Common YANG Types February 2024 + + A type that represents Diffserv-TE Bandwidth Constraints (BCs) as defined in [RFC4124]. @@ -665,15 +650,6 @@ Internet-Draft TE Common YANG Types January 2024 te-packet-path-bandwidth - - - - -Busi, et al. Expires 1 August 2024 [Page 12] - -Internet-Draft TE Common YANG Types January 2024 - - A YANG grouping that defines the path bandwidth information and could be used in any Packet TE model (e.g., MPLS-TE topology model) for the path bandwidth representation (e.g., the bandwidth @@ -686,6 +662,18 @@ Internet-Draft TE Common YANG Types January 2024 The Packet TE path bandwidth can be represented by a bandwidth profile as follow: + + + + + + + +Busi, et al. Expires 20 August 2024 [Page 12] + +Internet-Draft TE Common YANG Types February 2024 + + +--:(packet) +--rw bandwidth-profile-name? string +--rw bandwidth-profile-type? identityref @@ -722,14 +710,6 @@ Internet-Draft TE Common YANG Types January 2024 [RFC4736], [RFC6004], [RFC6511], [RFC7139], [RFC7308], [RFC7551], [RFC7571], [RFC7579], and [ITU-T_G.709]. - - - -Busi, et al. Expires 1 August 2024 [Page 13] - -Internet-Draft TE Common YANG Types January 2024 - - CHANGE NOTE: Please focus your review only on the updates to the YANG model: see also Appendix A.1. @@ -742,6 +722,14 @@ Internet-Draft TE Common YANG Types January 2024 prefix te-types; import ietf-inet-types { + + + +Busi, et al. Expires 20 August 2024 [Page 13] + +Internet-Draft TE Common YANG Types February 2024 + + prefix inet; reference "RFC 6991: Common YANG Data Types"; @@ -778,14 +766,6 @@ Internet-Draft TE Common YANG Types January 2024 Editor: Rakesh Gandhi - - - -Busi, et al. Expires 1 August 2024 [Page 14] - -Internet-Draft TE Common YANG Types January 2024 - - Editor: Vishnu Pavan Beeram @@ -798,6 +778,14 @@ Internet-Draft TE Common YANG Types January 2024 "; description "This YANG module contains a collection of generally useful + + + +Busi, et al. Expires 20 August 2024 [Page 14] + +Internet-Draft TE Common YANG Types February 2024 + + YANG data type definitions specific to TE. The model fully conforms to the Network Management Datastore Architecture (NMDA). @@ -821,45 +809,103 @@ Internet-Draft TE Common YANG Types January 2024 This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; - revision 2024-01-29 { - description - "Added: - - base identity lsp-provisioning-error-reason; - - identity association-type-diversity; - - identity tunnel-admin-state-auto; - - identity lsp-restoration-restore-none; - - identity restoration-scheme-rerouting; - - base identity path-computation-error-reason and - its derived identities; - - base identity protocol-origin-type and - its derived identities; - - base identity svec-objective-function-type and its derived - - - -Busi, et al. Expires 1 August 2024 [Page 15] - -Internet-Draft TE Common YANG Types January 2024 - - - identities; - - base identity svec-metric-type and its derived identities; - - grouping encoding-and-switching-type. - - Updated: - - description of the base identity objective-function-type; - - description and reference of identity action-exercise; - - typedef te-node-id to support also 16 octects TE identifiers. - - Obsoleted: - - identity of-minimize-agg-bandwidth-consumption; - - identity of-minimize-load-most-loaded-link; - - identity of-minimize-cost-path-set; - - identity lsp-protection-reroute-extra; - - identity lsp-protection-reroute. - - Container explicit-route-objects-always renamed as - explicit-route-objects."; + revision 2024-02-16 { + description + "This revision adds the following new identities: + - lsp-provisioning-error-reason; + - association-type-diversity; + - tunnel-admin-state-auto; + - lsp-restoration-restore-none; + - restoration-scheme-rerouting; + - path-metric-optimization-type; + - link-path-metric-type; + - link-metric-type and its derived identities; + - path-computation-error-reason and its derived identities; + - protocol-origin-type and its derived identities; + - svec-objective-function-type and its derived identities; + - svec-metric-type and its derived identities. + + This revision adds the following new data types: + - path-type; + - te-gen-node-id. + + This revision adds the following new groupings: + - encoding-and-switching-type; + - te-generic-node-id. + + This revision updates the following identities: + + + +Busi, et al. Expires 20 August 2024 [Page 15] + +Internet-Draft TE Common YANG Types February 2024 + + + - objective-function-type; + - action-exercise; + - path-metric-type; + - path-metric-te; + - path-metric-igp; + - path-metric-hop; + - path-metric-delay-average; + - path-metric-delay-minimum; + - path-metric-residual-bandwidth; + - path-metric-optimize-includes; + - path-metric-optimize-excludes; + - te-optimization-criterion. + + This revision updates the following data types: + - te-node-id. + + This revision updates the following groupings: + - explicit-route-hop: + - adds the following leaves: + - node-id-uri; + - link-tp-id-uri; + - updates the following leaves: + - node-id; + - link-tp-id; + - record-route-state: + - adds the following leaves: + - node-id-uri; + - link-tp-id-uri; + - updates the following leaves: + - node-id; + - link-tp-id; + - optimization-metric-entry: + - updates the following leaves: + - metric-type; + - tunnel-constraints; + - adds the following leaves: + - network-id; + - path-constraints-route-objects: + - updates the following containers: + - explicit-route-objects-always; + - generic-path-metric-bounds: + - updates the following leaves: + - metric-type; + - generic-path-optimization + - adds the following leaves: + - tiebreaker; + - deprecate the following containers: + - tiebreakers. + + + +Busi, et al. Expires 20 August 2024 [Page 16] + +Internet-Draft TE Common YANG Types February 2024 + + + This revision obsoletes the following identities: + - of-minimize-agg-bandwidth-consumption; + - of-minimize-load-most-loaded-link; + - of-minimize-cost-path-set; + - lsp-protection-reroute-extra; + - lsp-protection-reroute. + + This revision provides also few editorial changes."; reference "RFC XXXX: Common YANG Data Types for Traffic Engineering"; } @@ -868,7 +914,7 @@ Internet-Draft TE Common YANG Types January 2024 revision 2020-06-10 { description - "Latest revision of TE types."; + "Initial Version of TE types."; reference "RFC 8776: Common YANG Data Types for Traffic Engineering"; } @@ -885,26 +931,29 @@ Internet-Draft TE Common YANG Types January 2024 description "Administrative group / resource class / color representation in 'hex-string' type. + The most significant byte in the hex-string is the farthest to the left in the byte sequence. Leading zero bytes in the configured value may be omitted for brevity."; reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF - - - -Busi, et al. Expires 1 August 2024 [Page 16] - -Internet-Draft TE Common YANG Types January 2024 - - Version 2 + RFC 5305: IS-IS Extensions for Traffic Engineering + RFC 7308: Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)"; } typedef admin-groups { + + + +Busi, et al. Expires 20 August 2024 [Page 17] + +Internet-Draft TE Common YANG Types February 2024 + + type union { type admin-group; type extended-admin-group; @@ -918,6 +967,7 @@ Internet-Draft TE Common YANG Types January 2024 description "Extended administrative group / resource class / color representation in 'hex-string' type. + The most significant byte in the hex-string is the farthest to the left in the byte sequence. Leading zero bytes in the configured value may be omitted for brevity."; @@ -946,20 +996,20 @@ Internet-Draft TE Common YANG Types January 2024 description "Unknown."; } - - - -Busi, et al. Expires 1 August 2024 [Page 17] - -Internet-Draft TE Common YANG Types January 2024 - - enum normal { value 1; description "Normal. Indicates that the anomalous bit is not set."; } enum abnormal { + + + +Busi, et al. Expires 20 August 2024 [Page 18] + +Internet-Draft TE Common YANG Types February 2024 + + value 2; description "Abnormal. Indicates that the anomalous bit is set."; @@ -970,9 +1020,11 @@ Internet-Draft TE Common YANG Types January 2024 bit not set), abnormal (anomalous bit set), or unknown."; reference "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions + RFC 7823: Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric Extensions + RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; } @@ -1002,18 +1054,18 @@ Internet-Draft TE Common YANG Types January 2024 "In some test mode."; } enum preparing-maintenance { + description + "The resource is disabled in the control plane to prepare + for a graceful shutdown for maintenance purposes."; + reference -Busi, et al. Expires 1 August 2024 [Page 18] +Busi, et al. Expires 20 August 2024 [Page 19] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - description - "The resource is disabled in the control plane to prepare - for a graceful shutdown for maintenance purposes."; - reference "RFC 5817: Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks"; } @@ -1058,18 +1110,18 @@ Internet-Draft TE Common YANG Types January 2024 For the Optical Transport Network (OTN) switching type, a list of integers can be used, such as '0,2,3,1', indicating two ODU0s and one ODU3. ('ODU' stands for 'Optical Data + Unit'.) For Dense Wavelength Division Multiplexing (DWDM), + a list of pairs of slot numbers and widths can be used, + such as '0,2,3,3', indicating a frequency slot 0 with + slot width 2 and a frequency slot 3 with slot width 3. -Busi, et al. Expires 1 August 2024 [Page 19] +Busi, et al. Expires 20 August 2024 [Page 20] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - Unit'.) For Dense Wavelength Division Multiplexing (DWDM), - a list of pairs of slot numbers and widths can be used, - such as '0,2,3,3', indicating a frequency slot 0 with - slot width 2 and a frequency slot 3 with slot width 3. Canonically, the string is represented as all lowercase and in hex, where the prefix '0x' precedes the hex number."; reference @@ -1094,12 +1146,15 @@ Internet-Draft TE Common YANG Types January 2024 description "An identifier to uniquely identify an operator, which can be either a provider or a client. + The definition of this type is taken from RFCs 6370 and 5003. + This attribute type is used solely to provide a globally unique context for TE topologies."; reference "RFC 5003: Attachment Individual Identifier (AII) Types for Aggregation + RFC 6370: MPLS Transport Profile (MPLS-TP) Identifiers"; } @@ -1114,15 +1169,15 @@ Internet-Draft TE Common YANG Types January 2024 "A strict hop in an explicit path."; } } + description -Busi, et al. Expires 1 August 2024 [Page 20] +Busi, et al. Expires 20 August 2024 [Page 21] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - description "Enumerated type for specifying loose or strict paths."; reference "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels, @@ -1170,15 +1225,15 @@ Internet-Draft TE Common YANG Types January 2024 "The explicit route represents an incoming link on a node."; } + enum outgoing { -Busi, et al. Expires 1 August 2024 [Page 21] +Busi, et al. Expires 20 August 2024 [Page 22] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - enum outgoing { description "The explicit route represents an outgoing link on a node."; @@ -1229,9 +1284,10 @@ Internet-Draft TE Common YANG Types January 2024 -Busi, et al. Expires 1 August 2024 [Page 22] + +Busi, et al. Expires 20 August 2024 [Page 23] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 RFC 5305: IS-IS Extensions for Traffic Engineering, @@ -1285,9 +1341,9 @@ Internet-Draft TE Common YANG Types January 2024 -Busi, et al. Expires 1 August 2024 [Page 23] +Busi, et al. Expires 20 August 2024 [Page 24] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 typedef te-recovery-status { @@ -1341,9 +1397,9 @@ Internet-Draft TE Common YANG Types January 2024 -Busi, et al. Expires 1 August 2024 [Page 24] +Busi, et al. Expires 20 August 2024 [Page 25] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 "The recovery domain is recovering from a failure/degrade @@ -1397,9 +1453,9 @@ Internet-Draft TE Common YANG Types January 2024 -Busi, et al. Expires 1 August 2024 [Page 25] +Busi, et al. Expires 20 August 2024 [Page 26] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 // empty string @@ -1411,6 +1467,7 @@ Internet-Draft TE Common YANG Types January 2024 } description "An identifier for a topology. + It is optional to have one or more prefixes at the beginning, separated by colons. The prefixes can be 'network-types' as defined in the 'ietf-network' module in RFC 8345, to help the @@ -1429,6 +1486,7 @@ Internet-Draft TE Common YANG Types January 2024 } description "An identifier for a TE link endpoint on a node. + This attribute is mapped to a local or remote link identifier as defined in RFCs 3630 and 5305."; reference @@ -1448,16 +1506,16 @@ Internet-Draft TE Common YANG Types January 2024 } enum secondary-path { description - "Indicates that the TE path is a secondary path."; - } -Busi, et al. Expires 1 August 2024 [Page 26] +Busi, et al. Expires 20 August 2024 [Page 27] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + "Indicates that the TE path is a secondary path."; + } enum primary-reverse-path { description "Indicates that the TE path is a primary reverse path."; @@ -1504,16 +1562,16 @@ Internet-Draft TE Common YANG Types January 2024 "RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels"; } - feature extended-admin-groups { - description -Busi, et al. Expires 1 August 2024 [Page 27] +Busi, et al. Expires 20 August 2024 [Page 28] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + feature extended-admin-groups { + description "Indicates support for TE link extended administrative groups."; reference @@ -1560,15 +1618,16 @@ Internet-Draft TE Common YANG Types January 2024 // RFC Editor: remove the note above and this note identity lsp-provisioning-error-reason { description - "Base identity for LSP provisioning errors."; - } -Busi, et al. Expires 1 August 2024 [Page 28] +Busi, et al. Expires 20 August 2024 [Page 29] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + + "Base identity for LSP provisioning errors."; + } identity session-attributes-flags { description @@ -1615,16 +1674,16 @@ Internet-Draft TE Common YANG Types January 2024 description "Requests FRR node protection on LSRs, if present."; reference - "RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels"; - } - -Busi, et al. Expires 1 August 2024 [Page 29] +Busi, et al. Expires 20 August 2024 [Page 30] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + + "RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels"; + } identity path-reevaluation-request { base session-attributes-flags; @@ -1671,17 +1730,17 @@ Internet-Draft TE Common YANG Types January 2024 identity boundary-rerouting-desired { base lsp-attributes-flags; - description - "Indicates boundary rerouting behavior for an LSP undergoing - establishment. This MAY also be used to specify -Busi, et al. Expires 1 August 2024 [Page 30] +Busi, et al. Expires 20 August 2024 [Page 31] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + description + "Indicates boundary rerouting behavior for an LSP undergoing + establishment. This MAY also be used to specify segment-based LSP recovery through nested crankback for established LSPs. The boundary Area Border Router (ABR) / Autonomous System Border Router (ASBR) can decide to forward @@ -1727,17 +1786,17 @@ Internet-Draft TE Common YANG Types January 2024 } identity contiguous-lsp-desired { - base lsp-attributes-flags; - description - "Indicates that a contiguous LSP is desired."; -Busi, et al. Expires 1 August 2024 [Page 31] +Busi, et al. Expires 20 August 2024 [Page 32] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + base lsp-attributes-flags; + description + "Indicates that a contiguous LSP is desired."; reference "RFC 5151: Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) @@ -1783,17 +1842,17 @@ Internet-Draft TE Common YANG Types January 2024 identity oob-mapping-flag { base lsp-attributes-flags; - description - "Indicates that signaling of the egress binding information is - out of band (e.g., via the Border Gateway Protocol (BGP))."; -Busi, et al. Expires 1 August 2024 [Page 32] +Busi, et al. Expires 20 August 2024 [Page 33] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + description + "Indicates that signaling of the egress binding information is + out of band (e.g., via the Border Gateway Protocol (BGP))."; reference "RFC 6511: Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths @@ -1839,16 +1898,16 @@ Internet-Draft TE Common YANG Types January 2024 "RFC 7570: Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO) RFC 8001: RSVP-TE Extensions for Collecting Shared Risk - Link Group (SRLG) Information"; - } - -Busi, et al. Expires 1 August 2024 [Page 33] +Busi, et al. Expires 20 August 2024 [Page 34] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + + Link Group (SRLG) Information"; + } identity loopback-desired { base lsp-attributes-flags; @@ -1895,17 +1954,17 @@ Internet-Draft TE Common YANG Types January 2024 identity link-protection-extra-traffic { base link-protection-type; - description - "Extra-Traffic protected link type."; - reference -Busi, et al. Expires 1 August 2024 [Page 34] +Busi, et al. Expires 20 August 2024 [Page 35] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + description + "Extra-Traffic protected link type."; + reference "RFC 4427: Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)"; } @@ -1951,17 +2010,17 @@ Internet-Draft TE Common YANG Types January 2024 identity association-type-recovery { base association-type; - description - "Association type for recovery, used to associate LSPs of the - same tunnel for recovery."; -Busi, et al. Expires 1 August 2024 [Page 35] +Busi, et al. Expires 20 August 2024 [Page 36] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + description + "Association type for recovery, used to associate LSPs of the + same tunnel for recovery."; reference "RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery @@ -2007,19 +2066,19 @@ Internet-Draft TE Common YANG Types January 2024 // RFC Editor: remove the note above and this note identity association-type-diversity { base association-type; - description - "Association Type diversity used to associate LSPs whose - paths are to be diverse from each other."; -Busi, et al. Expires 1 August 2024 [Page 36] +Busi, et al. Expires 20 August 2024 [Page 37] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + description + "Association Type diversity used to associate LSPs whose + paths are to be diverse from each other."; reference - "RFC8800: Path Computation Element Communication Protocol + "RFC 8800: Path Computation Element Communication Protocol (PCEP) Extension for Label Switched Path (LSP) Diversity Constraint Signaling"; } @@ -2030,7 +2089,7 @@ Internet-Draft TE Common YANG Types January 2024 // RFC Editor: remove the note above and this note identity objective-function-type { description - "Base identity for path objective function type."; + "Base identity for path objective function types."; } identity of-minimize-cost-path { @@ -2063,21 +2122,25 @@ Internet-Draft TE Common YANG Types January 2024 // CHANGE NOTE: The identity of-minimize-agg-bandwidth-consumption // below has been obsoleted in this module revision - // RFC Editor: remove the note above and this note - identity of-minimize-agg-bandwidth-consumption { - base objective-function-type; -Busi, et al. Expires 1 August 2024 [Page 37] +Busi, et al. Expires 20 August 2024 [Page 38] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + // RFC Editor: remove the note above and this note + identity of-minimize-agg-bandwidth-consumption { + base objective-function-type; status obsolete; description "Objective function for minimizing aggregate bandwidth - consumption."; + consumption. + + This identity has been obsoleted: the + 'svec-of-minimize-agg-bandwidth-consumption' identity SHOULD + be used instead."; reference "RFC 5541: Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"; @@ -2091,7 +2154,11 @@ Internet-Draft TE Common YANG Types January 2024 status obsolete; description "Objective function for minimizing the load on the link that - is carrying the highest load."; + is carrying the highest load. + + This identity has been obsoleted: the + 'svec-of-minimize-load-most-loaded-link' identity SHOULD + be used instead."; reference "RFC 5541: Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"; @@ -2104,9 +2171,21 @@ Internet-Draft TE Common YANG Types January 2024 base objective-function-type; status obsolete; description - "Objective function for minimizing the cost on a path set."; + "Objective function for minimizing the cost on a path set. + + This identity has been obsoleted: the + 'svec-of-minimize-cost-path-set' identity SHOULD + be used instead."; reference "RFC 5541: Encoding of Objective Functions in the Path + + + +Busi, et al. Expires 20 August 2024 [Page 39] + +Internet-Draft TE Common YANG Types February 2024 + + Computation Element Communication Protocol (PCEP)"; } @@ -2115,24 +2194,23 @@ Internet-Draft TE Common YANG Types January 2024 "Base identity for supported path computation mechanisms."; } + // CHANGE NOTE: The reference of the identity path-locally-computed + // below has been updated in this module revision + // RFC Editor: remove the note above and this note identity path-locally-computed { base path-computation-method; description "Indicates a constrained-path LSP in which the path is computed by the local LER."; reference - "RFC 3272: Overview and Principles of Internet Traffic - - - -Busi, et al. Expires 1 August 2024 [Page 38] - -Internet-Draft TE Common YANG Types January 2024 - - - Engineering, Section 5.4"; + "RFC 9522: Overview and Principles of Internet Traffic + Engineering, Section 4.4"; } + // CHANGE NOTE: The reference of the identity + // path-externally-queried below has been updated + // in this module revision + // RFC Editor: remove the note above and this note identity path-externally-queried { base path-computation-method; description @@ -2144,13 +2222,26 @@ Internet-Draft TE Common YANG Types January 2024 returned by the external source may require further local computation on the device."; reference - "RFC 3272: Overview and Principles of Internet Traffic + "RFC 9522: Overview and Principles of Internet Traffic Engineering + RFC 4657: Path Computation Element (PCE) Communication Protocol Generic Requirements"; } + // CHANGE NOTE: The reference of the identity + // path-explicitly-defined below has been updated + // in this module revision + // RFC Editor: remove the note above and this note identity path-explicitly-defined { + + + +Busi, et al. Expires 20 August 2024 [Page 40] + +Internet-Draft TE Common YANG Types February 2024 + + base path-computation-method; description "Constrained-path LSP in which the path is @@ -2158,7 +2249,8 @@ Internet-Draft TE Common YANG Types January 2024 hops."; reference "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels - RFC 3272: Overview and Principles of Internet Traffic + + RFC 9522: Overview and Principles of Internet Traffic Engineering"; } @@ -2178,14 +2270,6 @@ Internet-Draft TE Common YANG Types January 2024 Protocol Generic Requirements"; } - - - -Busi, et al. Expires 1 August 2024 [Page 39] - -Internet-Draft TE Common YANG Types January 2024 - - identity lsp-metric-absolute { base lsp-metric-type; description @@ -2207,6 +2291,13 @@ Internet-Draft TE Common YANG Types January 2024 Protocol Generic Requirements"; } + + +Busi, et al. Expires 20 August 2024 [Page 41] + +Internet-Draft TE Common YANG Types February 2024 + + identity te-tunnel-type { description "Base identity from which specific tunnel types are derived."; @@ -2234,14 +2325,6 @@ Internet-Draft TE Common YANG Types January 2024 description "Base identity from which specific tunnel action types are derived."; - - - -Busi, et al. Expires 1 August 2024 [Page 40] - -Internet-Draft TE Common YANG Types January 2024 - - } identity tunnel-action-resetup { @@ -2263,6 +2346,14 @@ Internet-Draft TE Common YANG Types January 2024 description "TE tunnel action that switches the tunnel's LSP to use the specified path."; + + + +Busi, et al. Expires 20 August 2024 [Page 42] + +Internet-Draft TE Common YANG Types February 2024 + + } identity te-action-result { @@ -2290,14 +2381,6 @@ Internet-Draft TE Common YANG Types January 2024 } identity tunnel-admin-state-type { - - - -Busi, et al. Expires 1 August 2024 [Page 41] - -Internet-Draft TE Common YANG Types January 2024 - - description "Base identity for TE tunnel administrative states."; } @@ -2319,6 +2402,14 @@ Internet-Draft TE Common YANG Types January 2024 // RFC Editor: remove the note above and this note identity tunnel-admin-state-auto { base tunnel-admin-state-type; + + + +Busi, et al. Expires 20 August 2024 [Page 43] + +Internet-Draft TE Common YANG Types February 2024 + + description "Tunnel administrative auto state. The administrative status in state datastore transitions to 'tunnel-admin-up' when the @@ -2346,14 +2437,6 @@ Internet-Draft TE Common YANG Types January 2024 identity lsp-state-type { description "Base identity for TE LSP states."; - - - -Busi, et al. Expires 1 August 2024 [Page 42] - -Internet-Draft TE Common YANG Types January 2024 - - } identity lsp-path-computing { @@ -2375,6 +2458,14 @@ Internet-Draft TE Common YANG Types January 2024 } identity lsp-state-setting-up { + + + +Busi, et al. Expires 20 August 2024 [Page 44] + +Internet-Draft TE Common YANG Types February 2024 + + base lsp-state-type; description "State is being set up."; @@ -2402,14 +2493,6 @@ Internet-Draft TE Common YANG Types January 2024 base lsp-state-type; description "State is being torn down."; - - - -Busi, et al. Expires 1 August 2024 [Page 43] - -Internet-Draft TE Common YANG Types January 2024 - - } identity lsp-state-down { @@ -2431,6 +2514,14 @@ Internet-Draft TE Common YANG Types January 2024 reference "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels, Section 2.5"; + + + +Busi, et al. Expires 20 August 2024 [Page 45] + +Internet-Draft TE Common YANG Types February 2024 + + } identity path-invalidation-action-teardown { @@ -2458,14 +2549,6 @@ Internet-Draft TE Common YANG Types January 2024 identity lsp-restoration-restore-any { base lsp-restoration-type; - - - -Busi, et al. Expires 1 August 2024 [Page 44] - -Internet-Draft TE Common YANG Types January 2024 - - description "Any LSP affected by a failure is restored."; } @@ -2487,6 +2570,14 @@ Internet-Draft TE Common YANG Types January 2024 // RFC Editor: remove the note above and this note identity restoration-scheme-rerouting { base restoration-scheme-type; + + + +Busi, et al. Expires 20 August 2024 [Page 46] + +Internet-Draft TE Common YANG Types February 2024 + + description "Restoration LSP is computed after the failure detection. @@ -2515,13 +2606,6 @@ Internet-Draft TE Common YANG Types January 2024 for Generalized Multi-Protocol Label Switching (GMPLS)"; } - - -Busi, et al. Expires 1 August 2024 [Page 45] - -Internet-Draft TE Common YANG Types January 2024 - - identity restoration-scheme-presignaled { base restoration-scheme-type; description @@ -2542,6 +2626,14 @@ Internet-Draft TE Common YANG Types January 2024 identity lsp-protection-unprotected { base lsp-protection-type; description + + + +Busi, et al. Expires 20 August 2024 [Page 47] + +Internet-Draft TE Common YANG Types February 2024 + + "'Unprotected' LSP protection type."; reference "RFC 4872: RSVP-TE Extensions in Support of End-to-End @@ -2570,14 +2662,6 @@ Internet-Draft TE Common YANG Types January 2024 // RFC Editor: remove the note above and this note identity lsp-protection-reroute { base lsp-protection-type; - - - -Busi, et al. Expires 1 August 2024 [Page 46] - -Internet-Draft TE Common YANG Types January 2024 - - status obsolete; description "'Rerouting without Extra-Traffic' LSP protection type. @@ -2599,6 +2683,13 @@ Internet-Draft TE Common YANG Types January 2024 Generalized Multi-Protocol Label Switching (GMPLS) Recovery"; } + + +Busi, et al. Expires 20 August 2024 [Page 48] + +Internet-Draft TE Common YANG Types February 2024 + + identity lsp-protection-1-for-1 { base lsp-protection-type; description @@ -2626,14 +2717,6 @@ Internet-Draft TE Common YANG Types January 2024 Generalized Multi-Protocol Label Switching (GMPLS) Recovery"; } - - - -Busi, et al. Expires 1 August 2024 [Page 47] - -Internet-Draft TE Common YANG Types January 2024 - - identity lsp-protection-extra-traffic { base lsp-protection-type; description @@ -2655,6 +2738,14 @@ Internet-Draft TE Common YANG Types January 2024 } identity signal-fail-of-protection { + + + +Busi, et al. Expires 20 August 2024 [Page 49] + +Internet-Draft TE Common YANG Types February 2024 + + base lsp-protection-state; description "The protection transport entity has a signal fail condition @@ -2683,13 +2774,6 @@ Internet-Draft TE Common YANG Types January 2024 for Generalized Multi-Protocol Label Switching (GMPLS)"; } - - -Busi, et al. Expires 1 August 2024 [Page 48] - -Internet-Draft TE Common YANG Types January 2024 - - identity signal-fail { base lsp-protection-state; description @@ -2710,6 +2794,14 @@ Internet-Draft TE Common YANG Types January 2024 for Generalized Multi-Protocol Label Switching (GMPLS)"; } + + + +Busi, et al. Expires 20 August 2024 [Page 50] + +Internet-Draft TE Common YANG Types February 2024 + + identity manual-switch { base lsp-protection-state; description @@ -2738,14 +2830,6 @@ Internet-Draft TE Common YANG Types January 2024 for Generalized Multi-Protocol Label Switching (GMPLS)"; } - - - -Busi, et al. Expires 1 August 2024 [Page 49] - -Internet-Draft TE Common YANG Types January 2024 - - identity failure-of-protocol { base lsp-protection-state; description @@ -2766,6 +2850,14 @@ Internet-Draft TE Common YANG Types January 2024 base protection-external-commands; description "A temporary configuration action initiated by an operator + + + +Busi, et al. Expires 20 August 2024 [Page 51] + +Internet-Draft TE Common YANG Types February 2024 + + command that prevents any switchover action from being taken and, as such, freezes the current state."; reference @@ -2794,14 +2886,6 @@ Internet-Draft TE Common YANG Types January 2024 } identity clear-lockout-of-normal { - - - -Busi, et al. Expires 1 August 2024 [Page 50] - -Internet-Draft TE Common YANG Types January 2024 - - base protection-external-commands; description "An action that clears the active lockout of the @@ -2823,6 +2907,13 @@ Internet-Draft TE Common YANG Types January 2024 for Generalized Multi-Protocol Label Switching (GMPLS)"; } + + +Busi, et al. Expires 20 August 2024 [Page 52] + +Internet-Draft TE Common YANG Types February 2024 + + identity action-forced-switch { base protection-external-commands; description @@ -2850,14 +2941,6 @@ Internet-Draft TE Common YANG Types January 2024 // CHANGE NOTE: The description and reference of the // identity action-exercise have been updated in this module - - - -Busi, et al. Expires 1 August 2024 [Page 51] - -Internet-Draft TE Common YANG Types January 2024 - - // revision // RFC Editor: remove the note above and this note identity action-exercise { @@ -2879,6 +2962,14 @@ Internet-Draft TE Common YANG Types January 2024 protection, forced switchover, manual switchover, WTR state, or exercise command."; reference + + + +Busi, et al. Expires 20 August 2024 [Page 53] + +Internet-Draft TE Common YANG Types February 2024 + + "RFC 4427: Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)"; } @@ -2906,14 +2997,6 @@ Internet-Draft TE Common YANG Types January 2024 "Ethernet Virtual Private Line (EVPL)."; reference "RFC 6004: Generalized MPLS (GMPLS) Support for Metro Ethernet - - - -Busi, et al. Expires 1 August 2024 [Page 52] - -Internet-Draft TE Common YANG Types January 2024 - - Forum and G.8011 Ethernet Service Switching"; } @@ -2935,6 +3018,14 @@ Internet-Draft TE Common YANG Types January 2024 Signaling Functional Description"; } + + + +Busi, et al. Expires 20 August 2024 [Page 54] + +Internet-Draft TE Common YANG Types February 2024 + + identity switching-otn { base switching-capabilities; description @@ -2962,14 +3053,6 @@ Internet-Draft TE Common YANG Types January 2024 Signaling Functional Description"; } - - - -Busi, et al. Expires 1 August 2024 [Page 53] - -Internet-Draft TE Common YANG Types January 2024 - - identity switching-fsc { base switching-capabilities; description @@ -2991,6 +3074,14 @@ Internet-Draft TE Common YANG Types January 2024 base lsp-encoding-types; description "Packet LSP encoding."; + + + +Busi, et al. Expires 20 August 2024 [Page 55] + +Internet-Draft TE Common YANG Types February 2024 + + reference "RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"; @@ -3018,14 +3109,6 @@ Internet-Draft TE Common YANG Types January 2024 base lsp-encoding-types; description "SDH ITU-T G.707 / SONET ANSI T1.105 LSP encoding."; - - - -Busi, et al. Expires 1 August 2024 [Page 54] - -Internet-Draft TE Common YANG Types January 2024 - - reference "RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"; @@ -3047,11 +3130,19 @@ Internet-Draft TE Common YANG Types January 2024 reference "RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"; - } - identity lsp-encoding-fiber { - base lsp-encoding-types; - description + + +Busi, et al. Expires 20 August 2024 [Page 56] + +Internet-Draft TE Common YANG Types February 2024 + + + } + + identity lsp-encoding-fiber { + base lsp-encoding-types; + description "Fiber LSP encoding."; reference "RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) @@ -3074,14 +3165,6 @@ Internet-Draft TE Common YANG Types January 2024 reference "RFC 4328: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks - - - -Busi, et al. Expires 1 August 2024 [Page 55] - -Internet-Draft TE Common YANG Types January 2024 - - Control"; } @@ -3104,6 +3187,13 @@ Internet-Draft TE Common YANG Types January 2024 Ethernet Forum and G.8011 Ethernet Service Switching"; } + + +Busi, et al. Expires 20 August 2024 [Page 57] + +Internet-Draft TE Common YANG Types February 2024 + + identity path-signaling-type { description "Base identity from which specific LSP path setup types @@ -3130,14 +3220,6 @@ Internet-Draft TE Common YANG Types January 2024 "Segment-routing path setup."; } - - - -Busi, et al. Expires 1 August 2024 [Page 56] - -Internet-Draft TE Common YANG Types January 2024 - - identity path-scope-type { description "Base identity from which specific path scope types are @@ -3160,6 +3242,14 @@ Internet-Draft TE Common YANG Types January 2024 "RFC 4873: GMPLS Segment Recovery"; } + + + +Busi, et al. Expires 20 August 2024 [Page 58] + +Internet-Draft TE Common YANG Types February 2024 + + identity route-usage-type { description "Base identity for route usage."; @@ -3186,108 +3276,274 @@ Internet-Draft TE Common YANG Types January 2024 "Excludes SRLGs."; reference "RFC 4874: Exclude Routes - Extension to Resource ReserVation + Protocol-Traffic Engineering (RSVP-TE)"; + } + + // CHANGE NOTE: The path-metric-optimization-type base identity + // has been added in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-optimization-type { + description + "Base identity used to define the path metric optimization + types."; + } + // CHANGE NOTE: The link-path-metric-type base identity + // has been added in this module revision + // RFC Editor: remove the note above and this note + identity link-path-metric-type { + description + "Base identity used to define the link and the path metric + types. + + The unit of the path metric value is interpreted in the + context of the path metric type and the derived identities -Busi, et al. Expires 1 August 2024 [Page 57] + +Busi, et al. Expires 20 August 2024 [Page 59] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - Protocol-Traffic Engineering (RSVP-TE)"; + SHOULD describe the unit of the path metric types they + define."; } - // CHANGE NOTE: The description of the identity path-metric-type - // has been updated in this module revision - // RFC Editor: remove the note above and this note - identity path-metric-type { - description - "Base identity for the path metric type. + // CHANGE NOTE: The link-metric-type base identity + // and its derived identities + // have been added in this module revision + // RFC Editor: remove the note above and this note + identity link-metric-type { + base link-path-metric-type; + description + "Base identity for the link metric types."; + } - Derived identities SHOULD describe the unit and maximum value - of the path metric types they define."; - } + identity link-metric-te { + base link-metric-type; + description + "Traffic Engineering (TE) Link Metric."; + reference + "RFC 3630: Traffic Engineering (TE) Extensions to OSPF + Version 2, section 2.5.5 - identity path-metric-te { - base path-metric-type; - description - "TE path metric."; - reference - "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a - second MPLS Traffic Engineering (TE) Metric"; - } + RFC 5305: IS-IS Extensions for Traffic Engineering, + section 3.7"; + } - identity path-metric-igp { - base path-metric-type; - description - "IGP path metric."; - reference - "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a - second MPLS Traffic Engineering (TE) Metric"; - } + identity link-metric-igp { + base link-metric-type; + description + "Interior Gateway Protocol (IGP) Link Metric."; + reference + "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric + as a second MPLS Traffic Engineering (TE) Metric"; + } - // CHANGE NOTE: The reference for the identity path-metric-hop - // has been added in this module revision - // RFC Editor: remove the note above and this note - identity path-metric-hop { - base path-metric-type; - description - "Hop path metric."; - reference - "RFC5440: Path Computation Element (PCE) Communication - Protocol (PCEP)"; - } + identity link-metric-delay-average { + base link-metric-type; + description + "Unidirectional Link Delay, measured in units of + microseconds."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.1 + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.1"; + } - identity path-metric-delay-average { - base path-metric-type; - description -Busi, et al. Expires 1 August 2024 [Page 58] +Busi, et al. Expires 20 August 2024 [Page 60] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - "Average unidirectional link delay."; - reference - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; - } + identity link-metric-delay-minimum { + base link-metric-type; + description + "Minimum unidirectional Link Delay, measured in units of + microseconds."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.2 - identity path-metric-delay-minimum { - base path-metric-type; - description - "Minimum unidirectional link delay."; - reference - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; - } + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.2"; + } - identity path-metric-residual-bandwidth { - base path-metric-type; - description - "Unidirectional Residual Bandwidth, which is defined to be - Maximum Bandwidth (RFC 3630) minus the bandwidth currently - allocated to LSPs."; - reference - "RFC 3630: Traffic Engineering (TE) Extensions to OSPF - Version 2 - RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; - } + identity link-metric-delay-maximum { + base link-metric-type; + description + "Maximum unidirectional Link Delay, measured in units of + microseconds."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.2 - identity path-metric-optimize-includes { - base path-metric-type; - description - "A metric that optimizes the number of included resources - specified in a set."; - } + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.2"; + } - identity path-metric-optimize-excludes { - base path-metric-type; - description - "A metric that optimizes to a maximum the number of excluded - resources specified in a set."; - } + identity link-metric-residual-bandwidth { + base link-metric-type; + description + "Unidirectional Residual Bandwidth, measured in units of + bytes per second. + + It is defined to be Maximum Bandwidth minus the bandwidth + currently allocated to LSPs."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.5 + + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.5"; + } + + // CHANGE NOTE: The base and the description of the + // path-metric-type identity + // has been updated in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-type { + base link-path-metric-type; + + + +Busi, et al. Expires 20 August 2024 [Page 61] + +Internet-Draft TE Common YANG Types February 2024 + + + base path-metric-optimization-type; + description + "Base identity for the path metric types."; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-te identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-te { + base path-metric-type; + description + "Traffic Engineering (TE) Path Metric."; + reference + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.8"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-igp identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-igp { + base path-metric-type; + description + "Interior Gateway Protocol (IGP) Path Metric."; + reference + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.8"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-hop identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-hop { + base path-metric-type; + description + "Hop Count Path Metric."; + reference + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.8"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-delay-average identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + + + +Busi, et al. Expires 20 August 2024 [Page 62] + +Internet-Draft TE Common YANG Types February 2024 + + + identity path-metric-delay-average { + base path-metric-type; + description + "The Path Delay Metric, measured in units of + microseconds."; + reference + "RFC8233: Extensions to the Path Computation Element + Communication Protocol (PCEP) to Compute Service-Aware + Label Switched Paths (LSPs), section 3.1.1"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-delay-minimum identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-delay-minimum { + base path-metric-type; + description + "The Path Min Delay Metric, measured in units of + microseconds."; + reference + "I-D.ietf-pce-sid-algo: Carrying SR-Algorithm information + in PCE-based Networks, section 3.5.1"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-residual-bandwidth identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-residual-bandwidth { + base path-metric-type; + description + "The Path Residual Bandwidth, defined as the minimum Link + Residual Bandwidth all the links along the path. + + The Path Residual Bandwidth can be seen as the path + metric associated with the Maximum residual Bandwidth Path + (MBP) objective function."; + reference + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; + } + + // CHANGE NOTE: The base of the path-metric-optimize-includes + // identity has been updated in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-optimize-includes { + base path-metric-optimization-type; + + + +Busi, et al. Expires 20 August 2024 [Page 63] + +Internet-Draft TE Common YANG Types February 2024 + + + description + "A metric that optimizes the number of included resources + specified in a set."; + } + + // CHANGE NOTE: The base of the path-metric-optimize-excludes + // identity has been updated in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-optimize-excludes { + base path-metric-optimization-type; + description + "A metric that optimizes to a maximum the number of excluded + resources specified in a set."; + } identity path-tiebreaker-type { description @@ -3298,14 +3554,6 @@ Internet-Draft TE Common YANG Types January 2024 base path-tiebreaker-type; description "Min-Fill LSP path placement."; - - - -Busi, et al. Expires 1 August 2024 [Page 59] - -Internet-Draft TE Common YANG Types January 2024 - - } identity path-tiebreaker-maxfill { @@ -3330,6 +3578,14 @@ Internet-Draft TE Common YANG Types January 2024 identity resource-aff-include-all { base resource-affinities-type; description + + + +Busi, et al. Expires 20 August 2024 [Page 64] + +Internet-Draft TE Common YANG Types February 2024 + + "The set of attribute filters associated with a tunnel, all of which must be present for a link to be acceptable."; @@ -3354,24 +3610,20 @@ Internet-Draft TE Common YANG Types January 2024 description "The set of attribute filters associated with a tunnel, any of which renders a link unacceptable."; - - - -Busi, et al. Expires 1 August 2024 [Page 60] - -Internet-Draft TE Common YANG Types January 2024 - - reference "RFC 2702: Requirements for Traffic Engineering Over MPLS RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels"; } + // CHANGE NOTE: The reference of the identity + // te-optimization-criterion below has been updated + // in this module revision + // RFC Editor: remove the note above and this note identity te-optimization-criterion { description "Base identity for the TE optimization criteria."; reference - "RFC 3272: Overview and Principles of Internet Traffic + "RFC 9522: Overview and Principles of Internet Traffic Engineering"; } @@ -3382,6 +3634,14 @@ Internet-Draft TE Common YANG Types January 2024 } identity cost { + + + +Busi, et al. Expires 20 August 2024 [Page 65] + +Internet-Draft TE Common YANG Types February 2024 + + base te-optimization-criterion; description "Optimized on cost."; @@ -3410,14 +3670,6 @@ Internet-Draft TE Common YANG Types January 2024 "Ignores SRLGs in the path computation."; } - - - -Busi, et al. Expires 1 August 2024 [Page 61] - -Internet-Draft TE Common YANG Types January 2024 - - identity srlg-strict { base path-computation-srlg-type; description @@ -3438,6 +3690,14 @@ Internet-Draft TE Common YANG Types January 2024 // CHANGE NOTE: The base identity path-computation-error-reason // and its derived identities below have been + + + +Busi, et al. Expires 20 August 2024 [Page 66] + +Internet-Draft TE Common YANG Types February 2024 + + // added in this module revision // RFC Editor: remove the note above and this note identity path-computation-error-reason { @@ -3451,8 +3711,8 @@ Internet-Draft TE Common YANG Types January 2024 "Path computation has failed because of an unspecified reason."; reference - "Section 7.5 of RFC5440: Path Computation Element (PCE) - Communication Protocol (PCEP)"; + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.5"; } identity path-computation-error-no-topology { @@ -3466,21 +3726,19 @@ Internet-Draft TE Common YANG Types January 2024 base path-computation-error-reason; description "Path computation has failed because one or more dependent - - - -Busi, et al. Expires 1 August 2024 [Page 62] - -Internet-Draft TE Common YANG Types January 2024 - - path computation servers are unavailable. The dependent path computation server could be a Backward-Recursive Path Computation (BRPC) downstream PCE or a child PCE."; reference - "RFC5441, RFC8685"; + "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + Procedure to Compute Shortest Constrained Inter-Domain + Traffic Engineering Label Switched Paths + + RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture"; } identity path-computation-error-pce-unavailable { @@ -3488,13 +3746,22 @@ Internet-Draft TE Common YANG Types January 2024 description "Path computation has failed because PCE is not available. + + + +Busi, et al. Expires 20 August 2024 [Page 67] + +Internet-Draft TE Common YANG Types February 2024 + + It corresponds to bit 31 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5440: Path Computation Element (PCE) Communication - Protocol (PCEP); + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP) - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-inclusion-hop { @@ -3513,31 +3780,37 @@ Internet-Draft TE Common YANG Types January 2024 It corresponds to bit 19 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-resource { base path-computation-error-reason; description "Path computation has failed because there is no + available resource in one or more domains. + It corresponds to bit 20 of the Flags field of the + NO-PATH-VECTOR TLV."; + reference + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture + https://www.iana.org/assignments/pcep -Busi, et al. Expires 1 August 2024 [Page 63] - -Internet-Draft TE Common YANG Types January 2024 - available resource in one or more domains. +Busi, et al. Expires 20 August 2024 [Page 68] + +Internet-Draft TE Common YANG Types February 2024 - It corresponds to bit 20 of the Flags field of the - NO-PATH-VECTOR TLV."; - reference - "RFC8685; - https://www.iana.org/assignments/pcep/pcep.xhtml"; + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-child-pce-unresponsive { @@ -3549,9 +3822,12 @@ Internet-Draft TE Common YANG Types January 2024 It corresponds to bit 21 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-destination-domain-unknown { @@ -3563,9 +3839,12 @@ Internet-Draft TE Common YANG Types January 2024 It corresponds to bit 22 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-p2mp { @@ -3577,16 +3856,20 @@ Internet-Draft TE Common YANG Types January 2024 It corresponds to bit 24 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8306; + "RFC 8306: Extensions to the Path Computation Element + Communication Protocol (PCEP) for Point-to-Multipoint -Busi, et al. Expires 1 August 2024 [Page 64] +Busi, et al. Expires 20 August 2024 [Page 69] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + + Traffic Engineering Label Switched Paths - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-gco-migration { @@ -3598,9 +3881,12 @@ Internet-Draft TE Common YANG Types January 2024 It corresponds to bit 26 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5557; + "RFC 5557: Path Computation Element Communication Protocol + (PCEP) Requirements and Protocol Extensions in Support of + Global Concurrent Optimization - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-gco-solution { @@ -3612,9 +3898,12 @@ Internet-Draft TE Common YANG Types January 2024 It corresponds to bit 25 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5557; + "RFC 5557: Path Computation Element Communication Protocol + (PCEP) Requirements and Protocol Extensions in Support of + Global Concurrent Optimization - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-pks-expansion { @@ -3625,32 +3914,38 @@ Internet-Draft TE Common YANG Types January 2024 It corresponds to bit 27 of the Flags field of the NO-PATH-VECTOR TLV."; - reference - "RFC5520; - https://www.iana.org/assignments/pcep/pcep.xhtml"; - } - identity path-computation-error-brpc-chain-unavailable { - base path-computation-error-no-dependent-server; - description +Busi, et al. Expires 20 August 2024 [Page 70] + +Internet-Draft TE Common YANG Types February 2024 -Busi, et al. Expires 1 August 2024 [Page 65] - -Internet-Draft TE Common YANG Types January 2024 + reference + "RFC 5520: Preserving Topology Confidentiality in + Inter-Domain Path Computation Using a Path-Key-Based + Mechanism + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; + } + identity path-computation-error-brpc-chain-unavailable { + base path-computation-error-no-dependent-server; + description "Path computation has failed because PCE BRPC chain unavailable. It corresponds to bit 28 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5441; + "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + Procedure to Compute Shortest Constrained Inter-Domain + Traffic Engineering Label Switched Paths - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-source-unknown { @@ -3662,10 +3957,11 @@ Internet-Draft TE Common YANG Types January 2024 It corresponds to bit 29 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP); - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-destination-unknown { @@ -3674,13 +3970,22 @@ Internet-Draft TE Common YANG Types January 2024 "Path computation has failed because destination node is unknown. + + + +Busi, et al. Expires 20 August 2024 [Page 71] + +Internet-Draft TE Common YANG Types February 2024 + + It corresponds to bit 30 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP); - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-server { @@ -3689,18 +3994,11 @@ Internet-Draft TE Common YANG Types January 2024 "Path computation has failed because path computation server is unavailable."; reference - "RFC5440: Path Computation Element (PCE) Communication - - - -Busi, et al. Expires 1 August 2024 [Page 66] - -Internet-Draft TE Common YANG Types January 2024 - - + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP); - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } // CHANGE NOTE: The base identity protocol-origin-type and @@ -3725,15 +4023,22 @@ Internet-Draft TE Common YANG Types January 2024 "Protocol origin is Path Computation Engine Protocol (PCEP)."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP)"; } + + +Busi, et al. Expires 20 August 2024 [Page 72] + +Internet-Draft TE Common YANG Types February 2024 + + identity protocol-origin-bgp { base protocol-origin-type; description "Protocol origin is Border Gateway Protocol (BGP)."; - reference "RFC9012"; + reference "RFC 9012"; } // CHANGE NOTE: The base identity svec-objective-function-type @@ -3744,16 +4049,8 @@ Internet-Draft TE Common YANG Types January 2024 description "Base identity for SVEC objective function type."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; - - - -Busi, et al. Expires 1 August 2024 [Page 67] - -Internet-Draft TE Common YANG Types January 2024 - - + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-agg-bandwidth-consumption { @@ -3762,8 +4059,8 @@ Internet-Draft TE Common YANG Types January 2024 "Objective function for minimizing aggregate bandwidth consumption (MBC)."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-load-most-loaded-link { @@ -3772,8 +4069,8 @@ Internet-Draft TE Common YANG Types January 2024 "Objective function for minimizing the load on the link that is carrying the highest load (MLL)."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-cost-path-set { @@ -3782,19 +4079,26 @@ Internet-Draft TE Common YANG Types January 2024 "Objective function for minimizing the cost on a path set (MCC)."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } + + +Busi, et al. Expires 20 August 2024 [Page 73] + +Internet-Draft TE Common YANG Types February 2024 + + identity svec-of-minimize-common-transit-domain { base svec-objective-function-type; description "Objective function for minimizing the number of common transit domains (MCTD)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation - Element (H-PCE) Architecture."; + Element (H-PCE) Architecture"; } identity svec-of-minimize-shared-link { @@ -3802,16 +4106,8 @@ Internet-Draft TE Common YANG Types January 2024 description "Objective function for minimizing the number of shared links (MSL)."; - - - -Busi, et al. Expires 1 August 2024 [Page 68] - -Internet-Draft TE Common YANG Types January 2024 - - reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture."; } @@ -3822,7 +4118,7 @@ Internet-Draft TE Common YANG Types January 2024 "Objective function for minimizing the number of shared Shared Risk Link Groups (SRLG) (MSS)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture."; } @@ -3833,7 +4129,7 @@ Internet-Draft TE Common YANG Types January 2024 "Objective function for minimizing the number of shared nodes (MSN)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture."; } @@ -3842,46 +4138,47 @@ Internet-Draft TE Common YANG Types January 2024 // its derived identities below have been // added in this module revision // RFC Editor: remove the note above and this note + + + +Busi, et al. Expires 20 August 2024 [Page 74] + +Internet-Draft TE Common YANG Types February 2024 + + identity svec-metric-type { description "Base identity for SVEC metric type."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } - identity svec-metric-cumul-te { + identity svec-metric-cumulative-te { base svec-metric-type; description "Cumulative TE cost."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } - - -Busi, et al. Expires 1 August 2024 [Page 69] - -Internet-Draft TE Common YANG Types January 2024 - - - identity svec-metric-cumul-igp { + identity svec-metric-cumulative-igp { base svec-metric-type; description "Cumulative IGP cost."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } - identity svec-metric-cumul-hop { + identity svec-metric-cumulative-hop { base svec-metric-type; description "Cumulative Hop path metric."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-metric-aggregate-bandwidth-consumption { @@ -3889,17 +4186,25 @@ Internet-Draft TE Common YANG Types January 2024 description "Aggregate bandwidth consumption."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-metric-load-of-the-most-loaded-link { base svec-metric-type; description "Load of the most loaded link."; + + + +Busi, et al. Expires 20 August 2024 [Page 75] + +Internet-Draft TE Common YANG Types February 2024 + + reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } /** @@ -3914,14 +4219,6 @@ Internet-Draft TE Common YANG Types January 2024 type is used for unspecified technologies. The modeling structure can be augmented later for other technologies."; - - - -Busi, et al. Expires 1 August 2024 [Page 70] - -Internet-Draft TE Common YANG Types January 2024 - - container te-bandwidth { description "Container that specifies TE bandwidth. The choices @@ -3953,6 +4250,14 @@ Internet-Draft TE Common YANG Types January 2024 is used."; container te-label { description + + + +Busi, et al. Expires 20 August 2024 [Page 76] + +Internet-Draft TE Common YANG Types February 2024 + + "Container that specifies the TE label. The choices can be augmented for specific data-plane technologies."; choice technology { @@ -3970,14 +4275,6 @@ Internet-Draft TE Common YANG Types January 2024 leaf direction { type te-label-direction; default "forward"; - - - -Busi, et al. Expires 1 August 2024 [Page 71] - -Internet-Draft TE Common YANG Types January 2024 - - description "Label direction."; } @@ -4009,6 +4306,14 @@ Internet-Draft TE Common YANG Types January 2024 leaf topology-id { type te-topology-id; default ""; + + + +Busi, et al. Expires 20 August 2024 [Page 77] + +Internet-Draft TE Common YANG Types February 2024 + + description "When the datastore contains several topologies, 'topology-id' distinguishes between them. If omitted, @@ -4026,21 +4331,15 @@ Internet-Draft TE Common YANG Types January 2024 "Performance Metrics (PM) information in real time that can be applicable to links or connections. PM defined in this grouping are applicable to generic TE PM as well as packet TE - - - -Busi, et al. Expires 1 August 2024 [Page 72] - -Internet-Draft TE Common YANG Types January 2024 - - PM."; reference - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions - RFC 7823: Performance-Based Path Selection for Explicitly - Routed Label Switched Paths (LSPs) Using TE Metric - Extensions - RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensionsù + + RFC 7823: Performance-Based Path Selection for Explicitly + Routed Label Switched Paths (LSPs) Using TE Metric + Extensions + + RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; leaf one-way-delay { type uint32 { range "0..16777215"; @@ -4063,6 +4362,14 @@ Internet-Draft TE Common YANG Types January 2024 reference "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions RFC 7823: Performance-Based Path Selection for Explicitly + + + +Busi, et al. Expires 20 August 2024 [Page 78] + +Internet-Draft TE Common YANG Types February 2024 + + Routed Label Switched Paths (LSPs) Using TE Metric Extensions RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; @@ -4082,14 +4389,6 @@ Internet-Draft TE Common YANG Types January 2024 grouping performance-metrics-one-way-bandwidth { description - - - -Busi, et al. Expires 1 August 2024 [Page 73] - -Internet-Draft TE Common YANG Types January 2024 - - "PM information in real time that can be applicable to links. PM defined in this grouping are applicable to generic TE PM as well as packet TE PM."; @@ -4119,6 +4418,14 @@ Internet-Draft TE Common YANG Types January 2024 } leaf one-way-available-bandwidth { type rt-types:bandwidth-ieee-float32; + + + +Busi, et al. Expires 20 August 2024 [Page 79] + +Internet-Draft TE Common YANG Types February 2024 + + units "bytes per second"; default "0x0p0"; description @@ -4138,14 +4445,6 @@ Internet-Draft TE Common YANG Types January 2024 type rt-types:bandwidth-ieee-float32; units "bytes per second"; default "0x0p0"; - - - -Busi, et al. Expires 1 August 2024 [Page 74] - -Internet-Draft TE Common YANG Types January 2024 - - description "Bandwidth utilization that represents the actual utilization of the link (i.e., as measured in the router). @@ -4175,6 +4474,14 @@ Internet-Draft TE Common YANG Types January 2024 type rt-types:bandwidth-ieee-float32; units "bytes per second"; default "0x0p0"; + + + +Busi, et al. Expires 20 August 2024 [Page 80] + +Internet-Draft TE Common YANG Types February 2024 + + description "Residual bandwidth that subtracts tunnel reservations from Maximum Bandwidth (or link capacity) (RFC 3630) and @@ -4194,14 +4501,6 @@ Internet-Draft TE Common YANG Types January 2024 bundled link, available bandwidth is defined to be the sum of the component link available bandwidths."; } - - - -Busi, et al. Expires 1 August 2024 [Page 75] - -Internet-Draft TE Common YANG Types January 2024 - - leaf one-way-utilized-bandwidth { type rt-types:bandwidth-ieee-float32; units "bytes per second"; @@ -4231,6 +4530,14 @@ Internet-Draft TE Common YANG Types January 2024 description "Grouping for configurable thresholds for measured attributes."; + + + +Busi, et al. Expires 20 August 2024 [Page 81] + +Internet-Draft TE Common YANG Types February 2024 + + uses one-way-performance-metrics; uses two-way-performance-metrics; } @@ -4250,14 +4557,6 @@ Internet-Draft TE Common YANG Types January 2024 uses performance-metrics-one-way-delay-loss; uses performance-metrics-one-way-bandwidth; } - - - -Busi, et al. Expires 1 August 2024 [Page 76] - -Internet-Draft TE Common YANG Types January 2024 - - container performance-metrics-two-way { description "Two-way link performance information in real time."; @@ -4287,6 +4586,14 @@ Internet-Draft TE Common YANG Types January 2024 Routed Label Switched Paths (LSPs) Using TE Metric Extensions RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + + + +Busi, et al. Expires 20 August 2024 [Page 82] + +Internet-Draft TE Common YANG Types February 2024 + + leaf one-way-delay-offset { type uint32 { range "0..16777215"; @@ -4306,14 +4613,6 @@ Internet-Draft TE Common YANG Types January 2024 type uint32; default "0"; description - - - -Busi, et al. Expires 1 August 2024 [Page 77] - -Internet-Draft TE Common YANG Types January 2024 - - "Interval, in seconds, to advertise the extended metric values."; } @@ -4343,6 +4642,14 @@ Internet-Draft TE Common YANG Types January 2024 description "If the measured parameter falls inside an upper bound for all but the minimum-delay metric (or a lower bound + + + +Busi, et al. Expires 20 August 2024 [Page 83] + +Internet-Draft TE Common YANG Types February 2024 + + for the minimum-delay metric only) and the advertised value is not already inside that bound, a 'normal' announcement (anomalous bit cleared) will be triggered."; @@ -4362,14 +4669,6 @@ Internet-Draft TE Common YANG Types January 2024 * TE tunnel generic groupings **/ - - - -Busi, et al. Expires 1 August 2024 [Page 78] - -Internet-Draft TE Common YANG Types January 2024 - - // CHANGE NOTE: The explicit-route-hop grouping below has been // updated in this module revision // RFC Editor: remove the note above and this note @@ -4399,6 +4698,14 @@ Internet-Draft TE Common YANG Types January 2024 type te-hop-type; default "strict"; description + + + +Busi, et al. Expires 20 August 2024 [Page 84] + +Internet-Draft TE Common YANG Types February 2024 + + "Strict or loose hop."; } description @@ -4418,14 +4725,6 @@ Internet-Draft TE Common YANG Types January 2024 description "TE Link Termination Point (LTP) identifier."; } - - - -Busi, et al. Expires 1 August 2024 [Page 79] - -Internet-Draft TE Common YANG Types January 2024 - - leaf hop-type { type te-hop-type; default "strict"; @@ -4455,6 +4754,14 @@ Internet-Draft TE Common YANG Types January 2024 "At least one node identifier and at least one Link Termination Point (LTP) identifier MUST be present."; } + + + +Busi, et al. Expires 20 August 2024 [Page 85] + +Internet-Draft TE Common YANG Types February 2024 + + leaf link-tp-id-uri { type nt:tp-id; description @@ -4474,14 +4781,6 @@ Internet-Draft TE Common YANG Types January 2024 } leaf node-id { type te-node-id; - - - -Busi, et al. Expires 1 August 2024 [Page 80] - -Internet-Draft TE Common YANG Types January 2024 - - description "The identifier of a node in the TE topology."; } @@ -4511,6 +4810,14 @@ Internet-Draft TE Common YANG Types January 2024 leaf as-number { type inet:as-number; mandatory true; + + + +Busi, et al. Expires 20 August 2024 [Page 86] + +Internet-Draft TE Common YANG Types February 2024 + + description "The Autonomous System (AS) number."; } @@ -4530,20 +4837,15 @@ Internet-Draft TE Common YANG Types January 2024 "Label hop type."; uses te-label; } - - - -Busi, et al. Expires 1 August 2024 [Page 81] - -Internet-Draft TE Common YANG Types January 2024 - - description "The label explicit route hop type."; } } } + // CHANGE NOTE: The explicit-route-hop grouping below has been + // updated in this module revision + // RFC Editor: remove the note above and this note grouping record-route-state { description "The Record Route grouping."; @@ -4564,6 +4866,14 @@ Internet-Draft TE Common YANG Types January 2024 "At least one node identifier MUST be present."; } description + + + +Busi, et al. Expires 20 August 2024 [Page 87] + +Internet-Draft TE Common YANG Types February 2024 + + "Numbered node route hop container."; leaf node-id-uri { type nw:node-id; @@ -4586,14 +4896,6 @@ Internet-Draft TE Common YANG Types January 2024 RFC 4561: Definition of a Record Route Object (RRO) Node-Id Sub-Object"; } - - - -Busi, et al. Expires 1 August 2024 [Page 82] - -Internet-Draft TE Common YANG Types January 2024 - - } description "Numbered node route hop."; @@ -4620,6 +4922,14 @@ Internet-Draft TE Common YANG Types January 2024 Node-Id Sub-Object"; } } + + + +Busi, et al. Expires 20 August 2024 [Page 88] + +Internet-Draft TE Common YANG Types February 2024 + + description "Numbered link route hop."; } @@ -4642,14 +4952,6 @@ Internet-Draft TE Common YANG Types January 2024 "TE LTP identifier. The combination of the TE link ID and the TE node ID is used to identify an unnumbered TE link."; - - - -Busi, et al. Expires 1 August 2024 [Page 83] - -Internet-Draft TE Common YANG Types January 2024 - - } leaf node-id-uri { type nw:node-id; @@ -4676,6 +4978,14 @@ Internet-Draft TE Common YANG Types January 2024 "Unnumbered link Record Route hop."; reference "RFC 3477: Signalling Unnumbered Links in Resource + + + +Busi, et al. Expires 20 August 2024 [Page 89] + +Internet-Draft TE Common YANG Types February 2024 + + ReSerVation Protocol - Traffic Engineering (RSVP-TE)"; } description @@ -4698,14 +5008,6 @@ Internet-Draft TE Common YANG Types January 2024 Node-Id Sub-Object"; } } - - - -Busi, et al. Expires 1 August 2024 [Page 84] - -Internet-Draft TE Common YANG Types January 2024 - - description "The label Record Route entry types."; } @@ -4732,6 +5034,14 @@ Internet-Draft TE Common YANG Types January 2024 } leaf index { type uint32; + + + +Busi, et al. Expires 20 August 2024 [Page 90] + +Internet-Draft TE Common YANG Types February 2024 + + description "The index of the label restriction list entry."; } @@ -4754,14 +5064,6 @@ Internet-Draft TE Common YANG Types January 2024 This is the label value if a single label is specified, in which case the 'label-end' attribute is not set."; uses te-label; - - - -Busi, et al. Expires 1 August 2024 [Page 85] - -Internet-Draft TE Common YANG Types January 2024 - - } container label-end { must "(not(../label-start/te-label/direction) and" @@ -4788,6 +5090,14 @@ Internet-Draft TE Common YANG Types January 2024 The label start/end values will have to be consistent with the sign of label step. For example, 'label-start' < 'label-end' enforces 'label-step' > 0 + + + +Busi, et al. Expires 20 August 2024 [Page 91] + +Internet-Draft TE Common YANG Types February 2024 + + 'label-start' > 'label-end' enforces 'label-step' < 0."; choice technology { default "generic"; @@ -4810,14 +5120,6 @@ Internet-Draft TE Common YANG Types January 2024 this attribute is used to specify the positions of the used labels. This is represented in big endian as 'hex-string'. - - - -Busi, et al. Expires 1 August 2024 [Page 86] - -Internet-Draft TE Common YANG Types January 2024 - - The most significant byte in the hex-string is the farthest to the left in the byte sequence. Leading zero bytes in the configured value may be omitted for brevity. @@ -4844,10 +5146,18 @@ Internet-Draft TE Common YANG Types January 2024 description "The label restrictions container."; list label-restriction { - key "index"; - description - "The absence of the label restrictions container implies - that all labels are acceptable; otherwise, only restricted + + + +Busi, et al. Expires 20 August 2024 [Page 92] + +Internet-Draft TE Common YANG Types February 2024 + + + key "index"; + description + "The absence of the label restrictions container implies + that all labels are acceptable; otherwise, only restricted labels are available."; reference "RFC 7579: General Network Element Constraint Encoding @@ -4857,23 +5167,18 @@ Internet-Draft TE Common YANG Types January 2024 } } + // CHANGE NOTE: The grouping optimization-metric-entry below has + // been updated in this module revision + // RFC Editor: remove the note above and this note grouping optimization-metric-entry { description "Optimization metrics configuration grouping."; leaf metric-type { type identityref { - base path-metric-type; + base path-metric-optimization-type; } description "Identifies the 'metric-type' that the path computation - - - -Busi, et al. Expires 1 August 2024 [Page 87] - -Internet-Draft TE Common YANG Types January 2024 - - process uses for optimization."; } leaf weight { @@ -4898,6 +5203,13 @@ Internet-Draft TE Common YANG Types January 2024 } } + + +Busi, et al. Expires 20 August 2024 [Page 93] + +Internet-Draft TE Common YANG Types February 2024 + + grouping common-constraints { description "Common constraints grouping that can be set on @@ -4922,14 +5234,6 @@ Internet-Draft TE Common YANG Types January 2024 type uint8 { range "0..7"; } - - - -Busi, et al. Expires 1 August 2024 [Page 88] - -Internet-Draft TE Common YANG Types January 2024 - - default "7"; description "TE LSP requested setup priority."; @@ -4954,8 +5258,19 @@ Internet-Draft TE Common YANG Types January 2024 description "TE tunnel path signaling type."; } + + + +Busi, et al. Expires 20 August 2024 [Page 94] + +Internet-Draft TE Common YANG Types February 2024 + + } + // CHANGE NOTE: The grouping tunnel-constraints below has + // been updated in this module revision + // RFC Editor: remove the note above and this note grouping tunnel-constraints { description "Tunnel constraints grouping that can be set on @@ -4969,23 +5284,15 @@ Internet-Draft TE Common YANG Types January 2024 uses common-constraints; } + // CHANGE NOTE: The grouping path-constraints-route-objects below + // has been updated in this module revision + // RFC Editor: remove the note above and this note grouping path-constraints-route-objects { description "List of route entries to be included or excluded when performing the path computation."; - // CHANGE NOTE: The explicit-route-objects container below has - // been updated in this module revision - // RFC Editor: remove the note above and this note container explicit-route-objects { description - - - -Busi, et al. Expires 1 August 2024 [Page 89] - -Internet-Draft TE Common YANG Types January 2024 - - "Container for the explicit route object lists."; list route-object-exclude-always { key "index"; @@ -5007,6 +5314,14 @@ Internet-Draft TE Common YANG Types January 2024 ordered-by user; description "List of route objects to include or exclude in the path + + + +Busi, et al. Expires 20 August 2024 [Page 95] + +Internet-Draft TE Common YANG Types February 2024 + + computation."; leaf explicit-route-usage { type identityref { @@ -5034,14 +5349,6 @@ Internet-Draft TE Common YANG Types January 2024 type uint32; description "SRLG value."; - - - -Busi, et al. Expires 1 August 2024 [Page 90] - -Internet-Draft TE Common YANG Types January 2024 - - } } description @@ -5063,6 +5370,14 @@ Internet-Draft TE Common YANG Types January 2024 list route-object-include-object { key "index"; ordered-by user; + + + +Busi, et al. Expires 20 August 2024 [Page 96] + +Internet-Draft TE Common YANG Types February 2024 + + description "List of Explicit Route Objects to be included in the path computation."; @@ -5090,14 +5405,6 @@ Internet-Draft TE Common YANG Types January 2024 leaf index { type uint32; description - - - -Busi, et al. Expires 1 August 2024 [Page 91] - -Internet-Draft TE Common YANG Types January 2024 - - "Route object entry index. The index is used to identify an entry in the list. The order of entries is defined by the user without relying on key values."; @@ -5119,25 +5426,44 @@ Internet-Draft TE Common YANG Types January 2024 } description "Augmentation for a generic explicit route for SRLG + + + +Busi, et al. Expires 20 August 2024 [Page 97] + +Internet-Draft TE Common YANG Types February 2024 + + exclusion."; } } } } + // CHANGE NOTE: The grouping generic-path-metric-bounds below + // has been updated in this module revision + // RFC Editor: remove the note above and this note grouping generic-path-metric-bounds { description "TE path metric bounds grouping."; container path-metric-bounds { description - "TE path metric bounds container."; + "Top-level container for the list of path metric bounds."; list path-metric-bound { key "metric-type"; description - "List of TE path metric bounds."; + "List of path metric bounds, which can apply to link and + path metrics. + + TE paths which have at least one path metric which + exceeds the specified bounds MUST NOT be selected. + + TE paths that traverse TE links which have at least one + link metric which exceeds the specified bounds MUST NOT + be selected."; leaf metric-type { type identityref { - base path-metric-type; + base link-path-metric-type; } description "Identifies an entry in the list of 'metric-type' items @@ -5146,27 +5472,30 @@ Internet-Draft TE Common YANG Types January 2024 leaf upper-bound { type uint64; default "0"; - - - -Busi, et al. Expires 1 August 2024 [Page 92] - -Internet-Draft TE Common YANG Types January 2024 - - description - "Upper bound on the end-to-end TE path metric. + "Upper bound on the specified 'metric-type'. A zero indicates an unbounded upper limit for the - specific 'metric-type'. + specificied 'metric-type'. The unit of is interpreted in the context of the - path-metric-type."; + 'metric-type' identity."; } } + + + +Busi, et al. Expires 20 August 2024 [Page 98] + +Internet-Draft TE Common YANG Types February 2024 + + } } + // CHANGE NOTE: The grouping generic-path-metric-bounds below + // has been updated in this module revision + // RFC Editor: remove the note above and this note grouping generic-path-optimization { description "TE generic path optimization grouping."; @@ -5189,7 +5518,11 @@ Internet-Draft TE Common YANG Types January 2024 /* Tiebreakers */ container tiebreakers { description - "Container for the list of tiebreakers."; + "Container for the list of tiebreakers. + + This container has been obsoleted by the tiebreaker + leaf."; + status deprecated; list tiebreaker { key "tiebreaker-type"; description @@ -5202,17 +5535,17 @@ Internet-Draft TE Common YANG Types January 2024 } description "Identifies an entry in the list of tiebreakers."; + } + } + } -Busi, et al. Expires 1 August 2024 [Page 93] +Busi, et al. Expires 20 August 2024 [Page 99] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - } - } - } } case objective-function { if-feature "path-optimization-objective-function"; @@ -5233,6 +5566,15 @@ Internet-Draft TE Common YANG Types January 2024 } } } + leaf tiebreaker { + type identityref { + base path-tiebreaker-type; + } + default "te-types:path-tiebreaker-random"; + description + "The tiebreaker criteria to apply on an equally favored set + of paths, in order to pick the best."; + } } grouping generic-path-affinities { @@ -5252,21 +5594,21 @@ Internet-Draft TE Common YANG Types January 2024 description "Identifies an entry in the list of value affinity constraints."; - } - leaf value { - type admin-groups; - default ""; - description - "The affinity value. The default is empty."; -Busi, et al. Expires 1 August 2024 [Page 94] +Busi, et al. Expires 20 August 2024 [Page 100] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 } + leaf value { + type admin-groups; + default ""; + description + "The affinity value. The default is empty."; + } } } container path-affinity-names { @@ -5308,20 +5650,20 @@ Internet-Draft TE Common YANG Types January 2024 key "usage"; description "List of SRLG values to be included or excluded."; - leaf usage { - type identityref { - base route-usage-type; - } - description - "Identifies an entry in a list of SRLGs to either -Busi, et al. Expires 1 August 2024 [Page 95] +Busi, et al. Expires 20 August 2024 [Page 101] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + leaf usage { + type identityref { + base route-usage-type; + } + description + "Identifies an entry in a list of SRLGs to either include or exclude."; } leaf-list values { @@ -5364,20 +5706,20 @@ Internet-Draft TE Common YANG Types January 2024 "The type of resource disjointness. When configured for a primary path, the disjointness level applies to all secondary LSPs. When configured for a - secondary path, the disjointness level overrides the level - configured for the primary path."; - } - } - - grouping common-path-constraints-attributes { -Busi, et al. Expires 1 August 2024 [Page 96] +Busi, et al. Expires 20 August 2024 [Page 102] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + + secondary path, the disjointness level overrides the level + configured for the primary path."; + } + } + grouping common-path-constraints-attributes { description "Common path constraints configuration grouping."; uses common-constraints; @@ -5420,20 +5762,20 @@ Internet-Draft TE Common YANG Types January 2024 description "TE path metric accumulative value."; } - } - uses generic-path-affinities; - uses generic-path-srlgs; - container path-route-objects { - description - "Container for the list of route objects either returned by -Busi, et al. Expires 1 August 2024 [Page 97] +Busi, et al. Expires 20 August 2024 [Page 103] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + } + uses generic-path-affinities; + uses generic-path-srlgs; + container path-route-objects { + description + "Container for the list of route objects either returned by the computation engine or actually used by an LSP."; list path-route-object { key "index"; @@ -5469,27 +5811,27 @@ Internet-Draft TE Common YANG Types January 2024 description "LSP encoding type."; reference - "RFC3945"; + "RFC 3945"; } leaf switching-type { type identityref { base te-types:switching-capabilities; } description - "LSP switching type."; - reference - "RFC3945"; - } - } - -Busi, et al. Expires 1 August 2024 [Page 98] +Busi, et al. Expires 20 August 2024 [Page 104] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + "LSP switching type."; + reference + "RFC 3945"; + } + } + // CHANGE NOTE: The typedef te-gen-node-id below has been // added in this module revision // RFC Editor: remove the note above and this note @@ -5531,20 +5873,19 @@ Internet-Draft TE Common YANG Types January 2024 The "ietf-te-packet-types" module imports from the "ietf-te-types" module defined in Section 4 of this document. - CHANGE NOTE: Please focus your review only on the updates to the YANG - model: see also Appendix A.1. - - RFC Editor: remove the CHANGE NOTE above and this note +Busi, et al. Expires 20 August 2024 [Page 105] + +Internet-Draft TE Common YANG Types February 2024 -Busi, et al. Expires 1 August 2024 [Page 99] - -Internet-Draft TE Common YANG Types January 2024 + CHANGE NOTE: Please focus your review only on the updates to the YANG + model: see also Appendix A.1. + RFC Editor: remove the CHANGE NOTE above and this note file "ietf-te-packet-types@2024-01-25.yang" module ietf-te-packet-types { @@ -5589,19 +5930,19 @@ Internet-Draft TE Common YANG Types January 2024 (TE). The model fully conforms to the Network Management Datastore - Architecture (NMDA). - - The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL - NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', - 'MAY', and 'OPTIONAL' in this document are to be interpreted as -Busi, et al. Expires 1 August 2024 [Page 100] +Busi, et al. Expires 20 August 2024 [Page 106] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + + Architecture (NMDA). + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here. @@ -5618,18 +5959,20 @@ Internet-Draft TE Common YANG Types January 2024 This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; - revision 2024-01-25 { + revision 2024-02-16 { description - "Added common TE packet identities: + "This revision adds the following new identities: - bandwidth-profile-type; - - path-metric-loss; - - path-metric-delay-variation. + - link-metric-delay-variation; + - link-metric-loss; + - path-metric-delay-variation; + - path-metric-loss. - Added common TE packet groupings: + This revision adds the following new groupings: - te-packet-path-bandwidth; - te-packet-link-bandwidth. - Updated module description."; + This revision provides also few editorial changes."; reference "RFC XXXX: Common YANG Data Types for Traffic Engineering"; } @@ -5643,6 +5986,14 @@ Internet-Draft TE Common YANG Types January 2024 "RFC 8776: Common YANG Data Types for Traffic Engineering"; } + + + +Busi, et al. Expires 20 August 2024 [Page 107] + +Internet-Draft TE Common YANG Types February 2024 + + /* * Identities */ @@ -5650,14 +6001,6 @@ Internet-Draft TE Common YANG Types January 2024 // CHANGE NOTE: The base identity bandwidth-profile-type and // its derived identities below have been // added in this module revision - - - -Busi, et al. Expires 1 August 2024 [Page 101] - -Internet-Draft TE Common YANG Types January 2024 - - // RFC Editor: remove the note above and this note identity bandwidth-profile-type { description @@ -5697,64 +6040,80 @@ Internet-Draft TE Common YANG Types January 2024 Marker with Efficient Handling of in-Profile Traffic"; } - // CHANGE NOTE: The identity path-metric-loss below has - // been added in this module revision - // RFC Editor: remove the note above and this note - identity path-metric-loss { - base te-types:path-metric-type; - description - "The path loss (as a packet percentage) metric type - encodes a function of the unidirectional loss metrics of all - links traversed by a P2P path. + // CHANGE NOTE: The identity link-metric-delay-variation + // below has been added in this module revision -Busi, et al. Expires 1 August 2024 [Page 102] +Busi, et al. Expires 20 August 2024 [Page 108] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - The basic unit is 0.000003%, - where (2^24 - 2) or 50.331642% is the maximum value of the - path loss percentage that can be expressed. + // RFC Editor: remove the note above and this note + identity link-metric-delay-variation { + base te-types:link-metric-type; + description + "The Unidirectional Delay Variation Metric, + measured in units of microseconds."; + reference + "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + section 4.3 - Values that are larger than the maximum value SHOULD be - encoded as the maximum value."; - reference - "RFC8233: Extensions to the Path Computation Element - Communication Protocol (PCEP) to Compute Service-Aware Label - Switched Paths (LSPs); + RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + section 4.3"; + } - RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; + // CHANGE NOTE: The identity link-metric-loss below has + // been added in this module revision + // RFC Editor: remove the note above and this note + identity link-metric-loss { + base te-types:link-metric-type; + description + "The Unidirectional Link Loss Metric, + measured in units of 0.000003%."; + reference + "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + section 4.4 - RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - } + RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + section 4.4"; + } - // CHANGE NOTE: The identity path-metric-delay-variation below has - // been added in this module revision - // RFC Editor: remove the note above and this note - identity path-metric-delay-variation { - base te-types:path-metric-type; - description - "The path delay variation encodes the sum of the unidirectional - delay variation metrics of all links traversed by a P2P path. + // CHANGE NOTE: The identity path-metric-delay-variation + // below has been added in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-delay-variation { + base te-types:path-metric-type; + description + "The Path Delay Variation Metric, + measured in units of microseconds."; + reference + "RFC8233: Extensions to the Path Computation Element + Communication Protocol (PCEP) to Compute Service-Aware Label + Switched Paths (LSPs), section 3.1.2"; + } - The path delay variation metric unit is in microseconds, where - (2^24 - 1) or 16,777,215 microseconds (16.777215 sec) is the - maximum value of the path delay variation that can be - expressed. + // CHANGE NOTE: The identity path-metric-loss below has + // been added in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-loss { - Values that are larger than the maximum value SHOULD be - encoded as the maximum value."; - reference - "RFC8233: Extensions to the Path Computation Element - Communication Protocol (PCEP) to Compute Service-Aware Label - Switched Paths (LSPs); - RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; - RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - } +Busi, et al. Expires 20 August 2024 [Page 109] + +Internet-Draft TE Common YANG Types February 2024 + + + base te-types:path-metric-type; + description + "The Path Loss Metric, measured in units of 0.000003%."; + reference + "RFC8233: Extensions to the Path Computation Element + Communication Protocol (PCEP) to Compute Service-Aware Label + Switched Paths (LSPs), section 3.1.3"; + } /* * Typedefs @@ -5762,14 +6121,6 @@ Internet-Draft TE Common YANG Types January 2024 typedef te-bandwidth-requested-type { type enumeration { - - - -Busi, et al. Expires 1 August 2024 [Page 103] - -Internet-Draft TE Common YANG Types January 2024 - - enum specified { description "Bandwidth is explicitly specified."; @@ -5803,6 +6154,14 @@ Internet-Draft TE Common YANG Types January 2024 } description "Diffserv-TE bandwidth constraints as defined in RFC 4124."; + + + +Busi, et al. Expires 20 August 2024 [Page 110] + +Internet-Draft TE Common YANG Types February 2024 + + reference "RFC 4124: Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering"; @@ -5818,14 +6177,6 @@ Internet-Draft TE Common YANG Types January 2024 typedef bandwidth-mbps { type uint64; units "Mbps"; - - - -Busi, et al. Expires 1 August 2024 [Page 104] - -Internet-Draft TE Common YANG Types January 2024 - - description "Bandwidth values, expressed in megabits per second."; } @@ -5859,6 +6210,14 @@ Internet-Draft TE Common YANG Types January 2024 "Base identity for the Diffserv-TE Bandwidth Constraints Model type."; reference + + + +Busi, et al. Expires 20 August 2024 [Page 111] + +Internet-Draft TE Common YANG Types February 2024 + + "RFC 4124: Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering"; } @@ -5874,14 +6233,6 @@ Internet-Draft TE Common YANG Types January 2024 identity bc-model-mam { base bc-model-type; - - - -Busi, et al. Expires 1 August 2024 [Page 105] - -Internet-Draft TE Common YANG Types January 2024 - - description "Maximum Allocation Bandwidth Constraints Model type."; reference @@ -5915,7 +6266,15 @@ Internet-Draft TE Common YANG Types January 2024 } description "One-way minimum delay or latency in microseconds."; - } + + + +Busi, et al. Expires 20 August 2024 [Page 112] + +Internet-Draft TE Common YANG Types February 2024 + + + } leaf one-way-min-delay-normality { type te-types:performance-metrics-normality; default "normal"; @@ -5930,14 +6289,6 @@ Internet-Draft TE Common YANG Types January 2024 "One-way maximum delay or latency in microseconds."; } leaf one-way-max-delay-normality { - - - -Busi, et al. Expires 1 August 2024 [Page 106] - -Internet-Draft TE Common YANG Types January 2024 - - type te-types:performance-metrics-normality; default "normal"; description @@ -5971,6 +6322,14 @@ Internet-Draft TE Common YANG Types January 2024 type decimal64 { fraction-digits 6; range "0..50.331642"; + + + +Busi, et al. Expires 20 August 2024 [Page 113] + +Internet-Draft TE Common YANG Types February 2024 + + } description "One-way packet loss as a percentage of the total traffic @@ -5986,14 +6345,6 @@ Internet-Draft TE Common YANG Types January 2024 description "Packet loss normality."; reference - - - -Busi, et al. Expires 1 August 2024 [Page 107] - -Internet-Draft TE Common YANG Types January 2024 - - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions RFC 7823: Performance-Based Path Selection for @@ -6027,6 +6378,14 @@ Internet-Draft TE Common YANG Types January 2024 Explicitly Routed Label Switched Paths (LSPs) Using TE Metric Extensions RFC 8570: IS-IS Traffic Engineering (TE) Metric + + + +Busi, et al. Expires 20 August 2024 [Page 114] + +Internet-Draft TE Common YANG Types February 2024 + + Extensions"; } leaf two-way-max-delay { @@ -6042,14 +6401,6 @@ Internet-Draft TE Common YANG Types January 2024 default "normal"; description "Two-way maximum delay or latency normality."; - - - -Busi, et al. Expires 1 August 2024 [Page 108] - -Internet-Draft TE Common YANG Types January 2024 - - reference "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions @@ -6083,6 +6434,14 @@ Internet-Draft TE Common YANG Types January 2024 TE Metric Extensions RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + + + +Busi, et al. Expires 20 August 2024 [Page 115] + +Internet-Draft TE Common YANG Types February 2024 + + } leaf two-way-packet-loss { type decimal64 { @@ -6098,14 +6457,6 @@ Internet-Draft TE Common YANG Types January 2024 leaf two-way-packet-loss-normality { type te-types:performance-metrics-normality; default "normal"; - - - -Busi, et al. Expires 1 August 2024 [Page 109] - -Internet-Draft TE Common YANG Types January 2024 - - description "Two-way packet loss normality."; } @@ -6139,6 +6490,14 @@ Internet-Draft TE Common YANG Types January 2024 range "0..16777215"; } default "0"; + + + +Busi, et al. Expires 20 August 2024 [Page 116] + +Internet-Draft TE Common YANG Types February 2024 + + description "One-way maximum delay or latency in microseconds."; } @@ -6154,14 +6513,6 @@ Internet-Draft TE Common YANG Types January 2024 type decimal64 { fraction-digits 6; range "0..50.331642"; - - - -Busi, et al. Expires 1 August 2024 [Page 110] - -Internet-Draft TE Common YANG Types January 2024 - - } default "0"; description @@ -6195,6 +6546,14 @@ Internet-Draft TE Common YANG Types January 2024 range "0..16777215"; } default "0"; + + + +Busi, et al. Expires 20 August 2024 [Page 117] + +Internet-Draft TE Common YANG Types February 2024 + + description "Two-way delay variation in microseconds."; } @@ -6211,13 +6570,6 @@ Internet-Draft TE Common YANG Types January 2024 } } - - -Busi, et al. Expires 1 August 2024 [Page 111] - -Internet-Draft TE Common YANG Types January 2024 - - grouping performance-metrics-throttle-container-packet { description "Packet PM threshold grouping."; @@ -6250,6 +6602,14 @@ Internet-Draft TE Common YANG Types January 2024 // added in this module revision // RFC Editor: remove the note above and this note grouping te-packet-path-bandwidth { + + + +Busi, et al. Expires 20 August 2024 [Page 118] + +Internet-Draft TE Common YANG Types February 2024 + + description "Path bandwidth for Packet. "; leaf bandwidth-profile-name { @@ -6266,14 +6626,6 @@ Internet-Draft TE Common YANG Types January 2024 type uint64; units "bits/second"; mandatory true; - - - -Busi, et al. Expires 1 August 2024 [Page 112] - -Internet-Draft TE Common YANG Types January 2024 - - description "Committed Information Rate (CIR)."; } @@ -6306,6 +6658,14 @@ Internet-Draft TE Common YANG Types January 2024 type uint64; units "bytes"; description + + + +Busi, et al. Expires 20 August 2024 [Page 119] + +Internet-Draft TE Common YANG Types February 2024 + + "Peak Burst Size (PBS)."; } } @@ -6322,14 +6682,6 @@ Internet-Draft TE Common YANG Types January 2024 description "Available bandwith value."; } - - - -Busi, et al. Expires 1 August 2024 [Page 113] - -Internet-Draft TE Common YANG Types January 2024 - - } } @@ -6362,6 +6714,14 @@ Internet-Draft TE Common YANG Types January 2024 prefix: te-packet-types reference: RFC XXXX + + + +Busi, et al. Expires 20 August 2024 [Page 120] + +Internet-Draft TE Common YANG Types February 2024 + + RFC Editor: Please replace XXXX with the RFC number assigned to this document. @@ -6375,17 +6735,6 @@ Internet-Draft TE Common YANG Types January 2024 is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446]. - - - - - - -Busi, et al. Expires 1 August 2024 [Page 114] - -Internet-Draft TE Common YANG Types January 2024 - - The Network Configuration Access Control Model (NACM) [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or @@ -6422,6 +6771,13 @@ Internet-Draft TE Common YANG Types January 2024 DOI 10.17487/RFC5440, March 2009, . + + +Busi, et al. Expires 20 August 2024 [Page 121] + +Internet-Draft TE Common YANG Types February 2024 + + [RFC5441] Vasseur, JP., Ed., Zhang, R., Bitar, N., and JL. Le Roux, "A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute Shortest Constrained Inter-Domain @@ -6435,13 +6791,6 @@ Internet-Draft TE Common YANG Types January 2024 DOI 10.17487/RFC5520, April 2009, . - - -Busi, et al. Expires 1 August 2024 [Page 115] - -Internet-Draft TE Common YANG Types January 2024 - - [RFC5541] Le Roux, JL., Vasseur, JP., and Y. Lee, "Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)", RFC 5541, @@ -6476,6 +6825,15 @@ Internet-Draft TE Common YANG Types January 2024 RFC 7950, DOI 10.17487/RFC7950, August 2016, . + + + + +Busi, et al. Expires 20 August 2024 [Page 122] + +Internet-Draft TE Common YANG Types February 2024 + + [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . @@ -6489,15 +6847,6 @@ Internet-Draft TE Common YANG Types January 2024 DOI 10.17487/RFC8294, December 2017, . - - - - -Busi, et al. Expires 1 August 2024 [Page 116] - -Internet-Draft TE Common YANG Types January 2024 - - [RFC8306] Zhao, Q., Dhody, D., Ed., Palleti, R., and D. King, "Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic @@ -6531,6 +6880,16 @@ Internet-Draft TE Common YANG Types January 2024 RFC 8776, DOI 10.17487/RFC8776, June 2020, . + + + + + +Busi, et al. Expires 20 August 2024 [Page 123] + +Internet-Draft TE Common YANG Types February 2024 + + [RFC8800] Litkowski, S., Sivabalan, S., Barth, C., and M. Negi, "Path Computation Element Communication Protocol (PCEP) Extension for Label Switched Path (LSP) Diversity @@ -6544,40 +6903,6 @@ Internet-Draft TE Common YANG Types January 2024 8.2. Informative References - - - - - -Busi, et al. Expires 1 August 2024 [Page 117] - -Internet-Draft TE Common YANG Types January 2024 - - - [I-D.ietf-teas-yang-l3-te-topo] - Liu, X., Bryskin, I., Beeram, V. P., Saad, T., Shah, H. - C., and O. G. de Dios, "YANG Data Model for Layer 3 TE - Topologies", Work in Progress, Internet-Draft, draft-ietf- - teas-yang-l3-te-topo-15, 21 October 2023, - . - - [I-D.ietf-teas-yang-path-computation] - Busi, I., Belotti, S., de Dios, O. G., Sharma, A., and Y. - Shi, "A YANG Data Model for requesting path computation", - Work in Progress, Internet-Draft, draft-ietf-teas-yang- - path-computation-21, 7 July 2023, - . - - [I-D.ietf-teas-yang-te] - Saad, T., Gandhi, R., Liu, X., Beeram, V. P., and I. - Bryskin, "A YANG Data Model for Traffic Engineering - Tunnels, Label Switched Paths and Interfaces", Work in - Progress, Internet-Draft, draft-ietf-teas-yang-te-35, 12 - January 2024, . - [I-D.ietf-teas-yang-te-mpls] Saad, T., Gandhi, R., Liu, X., Beeram, V. P., and I. Bryskin, "A YANG Data Model for MPLS Traffic Engineering @@ -6601,15 +6926,6 @@ Internet-Draft TE Common YANG Types January 2024 Marker", RFC 2698, DOI 10.17487/RFC2698, September 1999, . - - - - -Busi, et al. Expires 1 August 2024 [Page 118] - -Internet-Draft TE Common YANG Types January 2024 - - [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. McManus, "Requirements for Traffic Engineering Over MPLS", RFC 2702, DOI 10.17487/RFC2702, September 1999, @@ -6620,6 +6936,16 @@ Internet-Draft TE Common YANG Types January 2024 Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, . + + + + + +Busi, et al. Expires 20 August 2024 [Page 124] + +Internet-Draft TE Common YANG Types February 2024 + + [RFC3272] Awduche, D., Chiu, A., Elwalid, A., Widjaja, I., and X. Xiao, "Overview and Principles of Internet Traffic Engineering", RFC 3272, DOI 10.17487/RFC3272, May 2002, @@ -6655,17 +6981,6 @@ Internet-Draft TE Common YANG Types January 2024 DOI 10.17487/RFC4090, May 2005, . - - - - - - -Busi, et al. Expires 1 August 2024 [Page 119] - -Internet-Draft TE Common YANG Types January 2024 - - [RFC4115] Aboul-Magd, O. and S. Rabie, "A Differentiated Service Two-Rate, Three-Color Marker with Efficient Handling of in-Profile Traffic", RFC 4115, DOI 10.17487/RFC4115, July @@ -6676,6 +6991,17 @@ Internet-Draft TE Common YANG Types January 2024 DOI 10.17487/RFC4124, June 2005, . + + + + + + +Busi, et al. Expires 20 August 2024 [Page 125] + +Internet-Draft TE Common YANG Types February 2024 + + [RFC4125] Le Faucheur, F. and W. Lai, "Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering", RFC 4125, DOI 10.17487/RFC4125, June 2005, @@ -6714,14 +7040,6 @@ Internet-Draft TE Common YANG Types January 2024 DOI 10.17487/RFC4427, March 2006, . - - - -Busi, et al. Expires 1 August 2024 [Page 120] - -Internet-Draft TE Common YANG Types January 2024 - - [RFC4561] Vasseur, J.-P., Ed., Ali, Z., and S. Sivabalan, "Definition of a Record Route Object (RRO) Node-Id Sub- Object", RFC 4561, DOI 10.17487/RFC4561, June 2006, @@ -6732,6 +7050,14 @@ Internet-Draft TE Common YANG Types January 2024 Requirements", RFC 4657, DOI 10.17487/RFC4657, September 2006, . + + + +Busi, et al. Expires 20 August 2024 [Page 126] + +Internet-Draft TE Common YANG Types February 2024 + + [RFC4736] Vasseur, JP., Ed., Ikejiri, Y., and R. Zhang, "Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched @@ -6771,13 +7097,6 @@ Internet-Draft TE Common YANG Types January 2024 TE)", RFC 5150, DOI 10.17487/RFC5150, February 2008, . - - -Busi, et al. Expires 1 August 2024 [Page 121] - -Internet-Draft TE Common YANG Types January 2024 - - [RFC5151] Farrel, A., Ed., Ayyangar, A., and JP. Vasseur, "Inter- Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) @@ -6788,6 +7107,13 @@ Internet-Draft TE Common YANG Types January 2024 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 2008, . + + +Busi, et al. Expires 20 August 2024 [Page 127] + +Internet-Draft TE Common YANG Types February 2024 + + [RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, @@ -6824,16 +7150,6 @@ Internet-Draft TE Common YANG Types January 2024 DOI 10.17487/RFC6370, September 2011, . - - - - - -Busi, et al. Expires 1 August 2024 [Page 122] - -Internet-Draft TE Common YANG Types January 2024 - - [RFC6378] Weingarten, Y., Ed., Bryant, S., Osborne, E., Sprecher, N., and A. Fulignoli, Ed., "MPLS Transport Profile (MPLS- TP) Linear Protection", RFC 6378, DOI 10.17487/RFC6378, @@ -6844,6 +7160,16 @@ Internet-Draft TE Common YANG Types January 2024 Label Switched Paths", RFC 6511, DOI 10.17487/RFC6511, February 2012, . + + + + + +Busi, et al. Expires 20 August 2024 [Page 128] + +Internet-Draft TE Common YANG Types February 2024 + + [RFC6780] Berger, L., Le Faucheur, F., and A. Narayanan, "RSVP ASSOCIATION Object Extensions", RFC 6780, DOI 10.17487/RFC6780, October 2012, @@ -6881,15 +7207,6 @@ Internet-Draft TE Common YANG Types January 2024 Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, . - - - - -Busi, et al. Expires 1 August 2024 [Page 123] - -Internet-Draft TE Common YANG Types January 2024 - - [RFC7551] Zhang, F., Ed., Jing, R., and R. Gandhi, Ed., "RSVP-TE Extensions for Associated Bidirectional Label Switched Paths (LSPs)", RFC 7551, DOI 10.17487/RFC7551, May 2015, @@ -6901,6 +7218,14 @@ Internet-Draft TE Common YANG Types January 2024 DOI 10.17487/RFC7570, July 2015, . + + + +Busi, et al. Expires 20 August 2024 [Page 129] + +Internet-Draft TE Common YANG Types February 2024 + + [RFC7571] Dong, J., Chen, M., Li, Z., and D. Ceccarelli, "GMPLS RSVP-TE Extensions for Lock Instruct and Loopback", RFC 7571, DOI 10.17487/RFC7571, July 2015, @@ -6935,17 +7260,6 @@ Internet-Draft TE Common YANG Types January 2024 Networks", RFC 8169, DOI 10.17487/RFC8169, May 2017, . - - - - - - -Busi, et al. Expires 1 August 2024 [Page 124] - -Internet-Draft TE Common YANG Types January 2024 - - [RFC8233] Dhody, D., Wu, Q., Manral, V., Ali, Z., and K. Kumaki, "Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched @@ -6957,15 +7271,277 @@ Internet-Draft TE Common YANG Types January 2024 Metric Extensions", RFC 8570, DOI 10.17487/RFC8570, March 2019, . - [RFC9314] Jethanandani, M., Ed., Rahman, R., Ed., Zheng, L., Ed., - Pallagatti, S., and G. Mirsky, "YANG Data Model for - Bidirectional Forwarding Detection (BFD)", RFC 9314, - DOI 10.17487/RFC9314, September 2022, - . -Appendix A. Changes from RFC 8776 - To be added in a future revision of this draft. + + + + +Busi, et al. Expires 20 August 2024 [Page 130] + +Internet-Draft TE Common YANG Types February 2024 + + + [RFC9314] Jethanandani, M., Ed., Rahman, R., Ed., Zheng, L., Ed., + Pallagatti, S., and G. Mirsky, "YANG Data Model for + Bidirectional Forwarding Detection (BFD)", RFC 9314, + DOI 10.17487/RFC9314, September 2022, + . + +Appendix A. Changes from RFC 8776 + + This version adds new common data types, identities, and groupings to + the YANG modules. It also updates some of the existing data types, + identities, and groupings in the YANG modules and fixes few bugs in + [RFC8776]. + + The following new identities have been added to the 'ietf-te-types' + module: + + * lsp-provisioning-error-reason; + + * association-type-diversity; + + * tunnel-admin-state-auto; + + * lsp-restoration-restore-none; + + * restoration-scheme-rerouting; + + * path-metric-optimization-type; + + * link-path-metric-type; + + * link-metric-type and its derived identities; + + * path-computation-error-reason and its derived identities; + + * protocol-origin-type and its derived identities; + + * svec-objective-function-type and its derived identities; + + * svec-metric-type and its derived identities. + + The following new data types have been added to the 'ietf-te-types' + module: + + * path-type; + + * te-gen-node-id. + + + + + +Busi, et al. Expires 20 August 2024 [Page 131] + +Internet-Draft TE Common YANG Types February 2024 + + + The following new groupings have been added to the 'ietf-te-types' + module: + + * encoding-and-switching-type; + + * te-generic-node-id. + + The following new identities have been added to the 'ietf-te-packet- + types' module: + + * bandwidth-profile-type; + + * link-metric-delay-variation; + + * link-metric-loss; + + * path-metric-delay-variation; + + * path-metric-loss. + + The following new groupings have been added to the 'ietf-te-packet- + types' module: + + * te-packet-path-bandwidth; + + * te-packet-link-bandwidth. + + The following identities, already defined in [RFC8776], have been + updated in the 'ietf-te-types' module: + + * objective-function-type (editorial); + + * action-exercise (bug fix); + + * path-metric-type: + + new base identities have been added; + + * path-metric-te (bug fix); + + * path-metric-igp (bug fix); + + * path-metric-hop (bug fix); + + * path-metric-delay-average (bug fix); + + * path-metric-delay-minimum (bug fix); + + + + +Busi, et al. Expires 20 August 2024 [Page 132] + +Internet-Draft TE Common YANG Types February 2024 + + + * path-metric-residual-bandwidth (bug fix); + + * path-metric-optimize-includes (bug fix); + + * path-metric-optimize-excludes (bug fix); + + * te-optimization-criterion (editorial). + + The following data type, already defined in [RFC8776], has been + updated in the 'ietf-te-types' module: + + * te-node-id; + + The data type has been changed to be a union. + + The following groupings, already defined in [RFC8776], have been + updated in the 'ietf-te-types' module: + + * explicit-route-hop + + The following new leaves have been added to the 'explicit-route- + hop' grouping: + + - node-id-uri; + + - link-tp-id-uri; + + The following leaves, already defined in [RFC8776], have been + updated in the 'explicit-route-hop': + + - node-id; + + - link-tp-id. + + The mandatory true statements for the node-id and link-tp-id + have been replaced by must statements that requires at least + the presence of: + + o node-id or node-id-uri; + + o link-tp-id or link-tp-id-uri. + + * explicit-route-hop + + The following new leaves have been added to the 'explicit-route- + hop' grouping: + + - node-id-uri; + + + +Busi, et al. Expires 20 August 2024 [Page 133] + +Internet-Draft TE Common YANG Types February 2024 + + + - link-tp-id-uri; + + The following leaves, already defined in [RFC8776], have been + updated in the 'explicit-route-hop': + + - node-id; + + - link-tp-id. + + The mandatory true statements for the node-id and link-tp-id + have been replaced by must statements that requires at least + the presence of: + + o node-id or node-id-uri; + + o link-tp-id or link-tp-id-uri. + + * optimization-metric-entry: + + The following leaves, already defined in [RFC8776], have been + updated in the 'optimization-metric-entry': + + - metric-type; + + The base identity has been updated without impacting the set of + derived identities that are allowed. + + * tunnel-constraints; + + The following new leaf have been added to the 'tunnel-constraints' + grouping: + + - network-id; + + * path-constraints-route-objects: + + The following container, already defined in [RFC8776], has been + updated in the 'path-constraints-route-objects': + + - explicit-route-objects-always; + + The container has been renamed as 'explicit-route-objects'. + This change is not affecting any IETF standard YANG models + since this grouping has not yet been used by any YANG model + defined in existing IETF RFCs. + + * generic-path-metric-bounds: + + + + +Busi, et al. Expires 20 August 2024 [Page 134] + +Internet-Draft TE Common YANG Types February 2024 + + + The following leaves, already defined in [RFC8776], have been + updated in the 'optimization-metric-entry': + + - metric-type; + + The base identity has been updated to: + + o increase the set of derived identities that are allowed and; + + o remove from this set the 'path-metric-optimize-includes' and + the 'path-metric-optimize-excludes' identities (bug fixing) + + * generic-path-optimization + + The following new leaf have been added to the 'generic-path- + optimization' grouping: + + - tiebreaker; + + The following container, already defined in [RFC8776], has been + deprecated: + + - tiebreakers. + + The following identities, already defined in [RFC8776], have been + obsoletes in the 'ietf-te-types' module for bug fixing: + + * of-minimize-agg-bandwidth-consumption; + + * of-minimize-load-most-loaded-link; + + * of-minimize-cost-path-set; + + * lsp-protection-reroute-extra; + + * lsp-protection-reroute. A.1. TE Types YANG Diffs @@ -6978,6 +7554,14 @@ A.1. TE Types YANG Diffs of the YANG model in Section 4 to the changes compared with the YANG model in [RFC8776]. + + + +Busi, et al. Expires 20 August 2024 [Page 135] + +Internet-Draft TE Common YANG Types February 2024 + + This diff has been generated using the following UNIX commands to compare the YANG module revisions in section 3.1 of [RFC8776] and in Section 4: @@ -6990,18 +7574,6 @@ A.1. TE Types YANG Diffs The output (model-updates.txt) is reported here: - - - - - - - -Busi, et al. Expires 1 August 2024 [Page 125] - -Internet-Draft TE Common YANG Types January 2024 - - 21a22,31 > import ietf-network { > prefix "nw"; @@ -7025,69 +7597,158 @@ Internet-Draft TE Common YANG Types January 2024 < the license terms contained in, the Simplified BSD License set --- > the license terms contained in, the Revised BSD License set - 65,66c75,113 + 65,66c75,164 < This version of this YANG module is part of RFC 8776; see the < RFC itself for full legal notices."; --- > This version of this YANG module is part of RFC XXXX > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself > for full legal notices."; - > revision 2024-01-29 { + > revision 2024-02-16 { > description - > "Added: - > - base identity lsp-provisioning-error-reason; - > - identity association-type-diversity; - > - identity tunnel-admin-state-auto; - > - identity lsp-restoration-restore-none; - > - identity restoration-scheme-rerouting; - > - base identity path-computation-error-reason and - > its derived identities; - > - base identity protocol-origin-type and - > its derived identities; - > - base identity svec-objective-function-type and its derived - > identities; - > - base identity svec-metric-type and its derived identities; - > - grouping encoding-and-switching-type. - > - > Updated: + > "This revision adds the following new identities: + > - lsp-provisioning-error-reason; + > - association-type-diversity; + > - tunnel-admin-state-auto; -Busi, et al. Expires 1 August 2024 [Page 126] +Busi, et al. Expires 20 August 2024 [Page 136] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - > - description of the base identity objective-function-type; - > - description and reference of identity action-exercise; - > - typedef te-node-id to support also 16 octects TE identifiers. + > - lsp-restoration-restore-none; + > - restoration-scheme-rerouting; + > - path-metric-optimization-type; + > - link-path-metric-type; + > - link-metric-type and its derived identities; + > - path-computation-error-reason and its derived identities; + > - protocol-origin-type and its derived identities; + > - svec-objective-function-type and its derived identities; + > - svec-metric-type and its derived identities. + > + > This revision adds the following new data types: + > - path-type; + > - te-gen-node-id. + > + > This revision adds the following new groupings: + > - encoding-and-switching-type; + > - te-generic-node-id. + > + > This revision updates the following identities: + > - objective-function-type; + > - action-exercise; + > - path-metric-type; + > - path-metric-te; + > - path-metric-igp; + > - path-metric-hop; + > - path-metric-delay-average; + > - path-metric-delay-minimum; + > - path-metric-residual-bandwidth; + > - path-metric-optimize-includes; + > - path-metric-optimize-excludes; + > - te-optimization-criterion. + > + > This revision updates the following data types: + > - te-node-id. > - > Obsoleted: - > - identity of-minimize-agg-bandwidth-consumption; - > - identity of-minimize-load-most-loaded-link; - > - identity of-minimize-cost-path-set; - > - identity lsp-protection-reroute-extra; - > - identity lsp-protection-reroute. + > This revision updates the following groupings: + > - explicit-route-hop: + > - adds the following leaves: + > - node-id-uri; + > - link-tp-id-uri; + > - updates the following leaves: + > - node-id; + > - link-tp-id; + > - record-route-state: + > - adds the following leaves: + > - node-id-uri; + > - link-tp-id-uri; + > - updates the following leaves: + + + +Busi, et al. Expires 20 August 2024 [Page 137] + +Internet-Draft TE Common YANG Types February 2024 + + + > - node-id; + > - link-tp-id; + > - optimization-metric-entry: + > - updates the following leaves: + > - metric-type; + > - tunnel-constraints; + > - adds the following leaves: + > - network-id; + > - path-constraints-route-objects: + > - updates the following containers: + > - explicit-route-objects-always; + > - generic-path-metric-bounds: + > - updates the following leaves: + > - metric-type; + > - generic-path-optimization + > - adds the following leaves: + > - tiebreaker; + > - deprecate the following containers: + > - tiebreakers. > - > Container explicit-route-objects-always renamed as - > explicit-route-objects."; + > This revision obsoletes the following identities: + > - of-minimize-agg-bandwidth-consumption; + > - of-minimize-load-most-loaded-link; + > - of-minimize-cost-path-set; + > - lsp-protection-reroute-extra; + > - lsp-protection-reroute. + > + > This revision provides also few editorial changes."; > reference > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; > } > // RFC Editor: replace XXXX with actual RFC number, update date > // information and remove this note - 351a399,401 + 70c168 + < "Latest revision of TE types."; + --- + > "Initial Version of TE types."; + 86a185 + > + 92a192 + > + 93a194 + > + 111a213 + > + 155a258 + > + 158a262 + + + +Busi, et al. Expires 20 August 2024 [Page 138] + +Internet-Draft TE Common YANG Types February 2024 + + + > + 263a368 + > + 264a370 + > + 269a376 + > + 351a459,461 > // CHANGE NOTE: The typedef te-node-id below has been > // updated in this module revision > // RFC Editor: remove the note above and this note - 353c403,406 + 353c463,466 < type yang:dotted-quad; --- > type union { > type yang:dotted-quad; > type inet:ipv6-address-no-zone; > } - 357,358c410,414 + 357,358c470,474 < The identifier is represented as 4 octets in dotted-quad < notation. --- @@ -7096,7 +7757,7 @@ Internet-Draft TE Common YANG Types January 2024 > dotted-quad notation or 16 octets in full, mixed, shortened, > or shortened-mixed IPv6 address notation. > - 362,363c418,421 + 362,363c478,481 < Router ID TLV described in Section 4.3 of RFC 5305, or the < TE Router ID TLV described in Section 3.2.1 of RFC 6119. --- @@ -7104,23 +7765,27 @@ Internet-Draft TE Common YANG Types January 2024 > Router ID TLV described in Section 3.2.1 of RFC 6119, or the > IPv6 TE Router ID TLV described in Section 4.1 of RFC 6119. > - 368a427 + 368a487 + > + 370a490 + > + 371a492 + > + 519a641 > + 537a660 + > + 545a669,709 + > // CHANGE NOTE: The typedef path-type below has been + > // added in this module revision -Busi, et al. Expires 1 August 2024 [Page 127] +Busi, et al. Expires 20 August 2024 [Page 139] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - 370a430 - > - 371a432 - > - 545a607,647 - > // CHANGE NOTE: The typedef path-type below has been - > // added in this module revision > // RFC Editor: remove the note above and this note > typedef path-type { > type enumeration { @@ -7160,16 +7825,8 @@ Internet-Draft TE Common YANG Types January 2024 > "Generic type that identifies a node in a TE topology."; > } > - 606a709,716 + 606a771,778 > // CHANGE NOTE: The base identity lsp-provisioning-error-reason - - - -Busi, et al. Expires 1 August 2024 [Page 128] - -Internet-Draft TE Common YANG Types January 2024 - - > // has been added in this module revision > // RFC Editor: remove the note above and this note > identity lsp-provisioning-error-reason { @@ -7177,7 +7834,15 @@ Internet-Draft TE Common YANG Types January 2024 > "Base identity for LSP provisioning errors."; > } > - 982a1093,1110 + + + +Busi, et al. Expires 20 August 2024 [Page 140] + +Internet-Draft TE Common YANG Types February 2024 + + + 982a1155,1172 > // CHANGE NOTE: The identity association-type-diversity below has > // been added in this module revision > // RFC Editor: remove the note above and this note @@ -7187,7 +7852,7 @@ Internet-Draft TE Common YANG Types January 2024 > "Association Type diversity used to associate LSPs whose > paths are to be diverse from each other."; > reference - > "RFC8800: Path Computation Element Communication Protocol + > "RFC 8800: Path Computation Element Communication Protocol > (PCEP) Extension for Label Switched Path (LSP) Diversity > Constraint Signaling"; > } @@ -7196,53 +7861,108 @@ Internet-Draft TE Common YANG Types January 2024 > // objective-function-type has been updated > // in this module revision > // RFC Editor: remove the note above and this note - 985c1113 + 985c1175 < "Base objective function type."; --- - > "Base identity for path objective function type."; - 1015a1144,1146 + > "Base identity for path objective function types."; + 1015a1206,1208 > // CHANGE NOTE: The identity of-minimize-agg-bandwidth-consumption > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1017a1149 + 1017a1211 > status obsolete; - 1020c1152 + 1020c1214,1218 < consumption."; --- - > consumption."; - 1023c1155 + > consumption. + > + > This identity has been obsoleted: the + > 'svec-of-minimize-agg-bandwidth-consumption' identity SHOULD + > be used instead."; + 1023c1221 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; - 1025a1158,1160 + 1025a1224,1226 > // CHANGE NOTE: The identity of-minimize-load-most-loaded-link > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note + 1027a1229 + > status obsolete; + 1030c1232,1236 -Busi, et al. Expires 1 August 2024 [Page 129] +Busi, et al. Expires 20 August 2024 [Page 141] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - 1027a1163 - > status obsolete; - 1030c1166 < is carrying the highest load."; --- - > is carrying the highest load."; - 1033c1169 + > is carrying the highest load. + > + > This identity has been obsoleted: the + > 'svec-of-minimize-load-most-loaded-link' identity SHOULD + > be used instead."; + 1033c1239 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; - 1035a1172,1174 + 1035a1242,1244 > // CHANGE NOTE: The identity of-minimize-cost-path-set > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1037a1177 + 1037a1247 > status obsolete; - 1216a1357,1368 + 1039c1249,1253 + < "Objective function for minimizing the cost on a path set."; + --- + > "Objective function for minimizing the cost on a path set. + > + > This identity has been obsoleted: the + > 'svec-of-minimize-cost-path-set' identity SHOULD + > be used instead."; + 1049a1264,1266 + > // CHANGE NOTE: The reference of the identity path-locally-computed + > // below has been updated in this module revision + > // RFC Editor: remove the note above and this note + 1056,1057c1273,1274 + < "RFC 3272: Overview and Principles of Internet Traffic + < Engineering, Section 5.4"; + --- + > "RFC 9522: Overview and Principles of Internet Traffic + > Engineering, Section 4.4"; + 1059a1277,1280 + > // CHANGE NOTE: The reference of the identity + > // path-externally-queried below has been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + 1071c1292 + < "RFC 3272: Overview and Principles of Internet Traffic + --- + > "RFC 9522: Overview and Principles of Internet Traffic + 1072a1294 + > + 1076a1299,1302 + > // CHANGE NOTE: The reference of the identity + + + +Busi, et al. Expires 20 August 2024 [Page 142] + +Internet-Draft TE Common YANG Types February 2024 + + + > // path-explicitly-defined below has been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + 1085c1311,1312 + < RFC 3272: Overview and Principles of Internet Traffic + --- + > + > RFC 9522: Overview and Principles of Internet Traffic + 1216a1444,1455 > // CHANGE NOTE: The identity tunnel-admin-state-auto below > // has been added in this module revision > // RFC Editor: remove the note above and this note @@ -7255,7 +7975,7 @@ Internet-Draft TE Common YANG Types January 2024 > when it is not used by the client layer."; > } > - 1321a1474,1482 + 1321a1561,1569 > // CHANGE NOTE: The identity lsp-restoration-restore-none > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -7265,7 +7985,7 @@ Internet-Draft TE Common YANG Types January 2024 > "No LSP affected by a failure is restored."; > } > - 1339a1501,1515 + 1339a1588,1602 > // CHANGE NOTE: The identity restoration-scheme-rerouting > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -7274,14 +7994,6 @@ Internet-Draft TE Common YANG Types January 2024 > description > "Restoration LSP is computed after the failure detection. > - - - -Busi, et al. Expires 1 August 2024 [Page 130] - -Internet-Draft TE Common YANG Types January 2024 - - > This restoration scheme is also known as > 'Full LSP Re-routing.'"; > reference @@ -7289,13 +8001,21 @@ Internet-Draft TE Common YANG Types January 2024 > for Generalized Multi-Protocol Label Switching (GMPLS)"; > } > - 1383a1560,1562 + 1383a1647,1649 + + + +Busi, et al. Expires 20 August 2024 [Page 143] + +Internet-Draft TE Common YANG Types February 2024 + + > // CHANGE NOTE: The identity lsp-protection-reroute-extra > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1385a1565 + 1385a1652 > status obsolete; - 1387c1567,1571 + 1387c1654,1658 < "'(Full) Rerouting' LSP protection type."; --- > "'(Full) Rerouting' LSP protection type. @@ -7303,13 +8023,13 @@ Internet-Draft TE Common YANG Types January 2024 > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; - 1392a1577,1579 + 1392a1664,1666 > // CHANGE NOTE: The identity lsp-protection-reroute > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note - 1394a1582 + 1394a1669 > status obsolete; - 1396c1584,1588 + 1396c1671,1675 < "'Rerouting without Extra-Traffic' LSP protection type."; --- > "'Rerouting without Extra-Traffic' LSP protection type. @@ -7317,54 +8037,383 @@ Internet-Draft TE Common YANG Types January 2024 > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; - 1628a1821,1824 + 1628a1908,1911 > // CHANGE NOTE: The description and reference of the > // identity action-exercise have been updated in this module > // revision > // RFC Editor: remove the note above and this note - 1632,1633c1828,1830 + 1632,1633c1915,1917 < "An action that starts testing whether or not APS communication < is operating correctly. It is of lower priority than any --- > "An action that starts testing whether or not Automatic > Protection Switching (APS) communication is operating > correctly. It is of lower priority than any - 1636,1637c1833,1834 + 1636,1637c1920,1921 + < "RFC 4427: Recovery (Protection and Restoration) Terminology + < for Generalized Multi-Protocol Label Switching (GMPLS)"; + --- + > "ITU-T G.808.1 v4.0 (05/2014): Generic protection switching - + > Linear trail and subnetwork protection"; + 1917c2201,2204 + < identity path-metric-type { + --- -Busi, et al. Expires 1 August 2024 [Page 131] +Busi, et al. Expires 20 August 2024 [Page 144] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - < "RFC 4427: Recovery (Protection and Restoration) Terminology - < for Generalized Multi-Protocol Label Switching (GMPLS)"; - --- - > "ITU-T G.808.1 v4.0 (05/2014): Generic protection switching - - > Linear trail and subnetwork protection"; - 1916a2114,2116 - > // CHANGE NOTE: The description of the identity path-metric-type - > // has been updated in this module revision + > // CHANGE NOTE: The path-metric-optimization-type base identity + > // has been added in this module revision > // RFC Editor: remove the note above and this note - 1919c2119,2122 + > identity path-metric-optimization-type { + 1919c2206,2207 < "Base identity for the path metric type."; --- - > "Base identity for the path metric type. - > - > Derived identities SHOULD describe the unit and maximum value - > of the path metric types they define."; - 1939a2143,2145 - > // CHANGE NOTE: The reference for the identity path-metric-hop + > "Base identity used to define the path metric optimization + > types."; + 1922,1923c2210,2213 + < identity path-metric-te { + < base path-metric-type; + --- + > // CHANGE NOTE: The link-path-metric-type base identity > // has been added in this module revision > // RFC Editor: remove the note above and this note - 1943a2150,2152 - > reference - > "RFC5440: Path Computation Element (PCE) Communication - > Protocol (PCEP)"; - 1945a2155 + > identity link-path-metric-type { + 1925,1928c2215,2221 + < "TE path metric."; + < reference + < "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a + < second MPLS Traffic Engineering (TE) Metric"; + --- + > "Base identity used to define the link and the path metric + > types. + > + > The unit of the path metric value is interpreted in the + > context of the path metric type and the derived identities + > SHOULD describe the unit of the path metric types they + > define."; + 1931,1938c2224,2232 + < identity path-metric-igp { + < base path-metric-type; + < description + < "IGP path metric."; + < reference + < "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a + < second MPLS Traffic Engineering (TE) Metric"; + < } + --- + > // CHANGE NOTE: The link-metric-type base identity + > // and its derived identities + > // have been added in this module revision + > // RFC Editor: remove the note above and this note + > identity link-metric-type { + > base link-path-metric-type; + > description + > "Base identity for the link metric types."; + + + +Busi, et al. Expires 20 August 2024 [Page 145] + +Internet-Draft TE Common YANG Types February 2024 + + + > } + 1940,1944c2234,2240 + < identity path-metric-hop { + < base path-metric-type; + < description + < "Hop path metric."; + < } + --- + > identity link-metric-te { + > base link-metric-type; + > description + > "Traffic Engineering (TE) Link Metric."; + > reference + > "RFC 3630: Traffic Engineering (TE) Extensions to OSPF + > Version 2, section 2.5.5 + 1946,1952c2242,2244 + < identity path-metric-delay-average { + < base path-metric-type; + < description + < "Average unidirectional link delay."; + < reference + < "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; + < } + --- + > RFC 5305: IS-IS Extensions for Traffic Engineering, + > section 3.7"; + > } + 1954,1960c2246,2253 + < identity path-metric-delay-minimum { + < base path-metric-type; + < description + < "Minimum unidirectional link delay."; + < reference + < "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; + < } + --- + > identity link-metric-igp { + > base link-metric-type; + > description + > "Interior Gateway Protocol (IGP) Link Metric."; + > reference + > "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric + > as a second MPLS Traffic Engineering (TE) Metric"; + > } + 1962,1972c2255,2266 + < identity path-metric-residual-bandwidth { + < base path-metric-type; + < description + + + +Busi, et al. Expires 20 August 2024 [Page 146] + +Internet-Draft TE Common YANG Types February 2024 + + + < "Unidirectional Residual Bandwidth, which is defined to be + < Maximum Bandwidth (RFC 3630) minus the bandwidth currently + < allocated to LSPs."; + < reference + < "RFC 3630: Traffic Engineering (TE) Extensions to OSPF + < Version 2 + < RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; + < } + --- + > identity link-metric-delay-average { + > base link-metric-type; + > description + > "Unidirectional Link Delay, measured in units of + > microseconds."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.1 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.1"; + > } + 1974,1979c2268,2279 + < identity path-metric-optimize-includes { + < base path-metric-type; + < description + < "A metric that optimizes the number of included resources + < specified in a set."; + < } + --- + > identity link-metric-delay-minimum { + > base link-metric-type; + > description + > "Minimum unidirectional Link Delay, measured in units of + > microseconds."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.2 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.2"; + > } + 1981,1986c2281,2425 + < identity path-metric-optimize-excludes { + < base path-metric-type; + < description + < "A metric that optimizes to a maximum the number of excluded + < resources specified in a set."; + < } + + + +Busi, et al. Expires 20 August 2024 [Page 147] + +Internet-Draft TE Common YANG Types February 2024 + + + --- + > identity link-metric-delay-maximum { + > base link-metric-type; + > description + > "Maximum unidirectional Link Delay, measured in units of + > microseconds."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.2 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.2"; + > } + > + > identity link-metric-residual-bandwidth { + > base link-metric-type; + > description + > "Unidirectional Residual Bandwidth, measured in units of + > bytes per second. + > + > It is defined to be Maximum Bandwidth minus the bandwidth + > currently allocated to LSPs."; + > reference + > "RFC 7471: OSPF Traffic Engineering (TE) Metric + > Extensions, section 4.5 + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric + > Extensions, section 4.5"; + > } + > + > // CHANGE NOTE: The base and the description of the + > // path-metric-type identity + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-type { + > base link-path-metric-type; + > base path-metric-optimization-type; + > description + > "Base identity for the path metric types."; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-te identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-te { + > base path-metric-type; + > description + + + +Busi, et al. Expires 20 August 2024 [Page 148] + +Internet-Draft TE Common YANG Types February 2024 + + + > "Traffic Engineering (TE) Path Metric."; + > reference + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.8"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-igp identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-igp { + > base path-metric-type; + > description + > "Interior Gateway Protocol (IGP) Path Metric."; + > reference + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.8"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-hop identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-hop { + > base path-metric-type; + > description + > "Hop Count Path Metric."; + > reference + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.8"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-delay-average identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-delay-average { + > base path-metric-type; + > description + > "The Path Delay Metric, measured in units of + > microseconds."; + > reference + > "RFC8233: Extensions to the Path Computation Element + > Communication Protocol (PCEP) to Compute Service-Aware + > Label Switched Paths (LSPs), section 3.1.1"; + > } + > + > // CHANGE NOTE: The description and the reference of the + + + +Busi, et al. Expires 20 August 2024 [Page 149] + +Internet-Draft TE Common YANG Types February 2024 + + + > // path-metric-delay-minimum identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-delay-minimum { + > base path-metric-type; + > description + > "The Path Min Delay Metric, measured in units of + > microseconds."; + > reference + > "I-D.ietf-pce-sid-algo: Carrying SR-Algorithm information + > in PCE-based Networks, section 3.5.1"; + > } + > + > // CHANGE NOTE: The description and the reference of the + > // path-metric-residual-bandwidth identity have been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-residual-bandwidth { + > base path-metric-type; + > description + > "The Path Residual Bandwidth, defined as the minimum Link + > Residual Bandwidth all the links along the path. + > + > The Path Residual Bandwidth can be seen as the path + > metric associated with the Maximum residual Bandwidth Path + > (MBP) objective function."; + > reference + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; + > } + > + > // CHANGE NOTE: The base of the path-metric-optimize-includes + > // identity has been updated in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-optimize-includes { + > base path-metric-optimization-type; + > description + > "A metric that optimizes the number of included resources + > specified in a set."; + > } > - 2110a2321,2724 + > // CHANGE NOTE: The base of the path-metric-optimize-excludes + > // identity has been updated in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-optimize-excludes { + > base path-metric-optimization-type; + > description + > "A metric that optimizes to a maximum the number of excluded + + + +Busi, et al. Expires 20 August 2024 [Page 150] + +Internet-Draft TE Common YANG Types February 2024 + + + > resources specified in a set."; + > } + 2049a2489,2492 + > // CHANGE NOTE: The reference of the identity + > // te-optimization-criterion below has been updated + > // in this module revision + > // RFC Editor: remove the note above and this note + 2054c2497 + < "RFC 3272: Overview and Principles of Internet Traffic + --- + > "RFC 9522: Overview and Principles of Internet Traffic + 2110a2554,2994 > // CHANGE NOTE: The base identity path-computation-error-reason > // and its derived identities below have been > // added in this module revision @@ -7380,20 +8429,12 @@ Internet-Draft TE Common YANG Types January 2024 > "Path computation has failed because of an unspecified > reason."; > reference - > "Section 7.5 of RFC5440: Path Computation Element (PCE) - > Communication Protocol (PCEP)"; + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP), section 7.5"; > } > > identity path-computation-error-no-topology { > base path-computation-error-reason; - - - -Busi, et al. Expires 1 August 2024 [Page 132] - -Internet-Draft TE Common YANG Types January 2024 - - > description > "Path computation has failed because there is no topology > with the provided topology-identifier."; @@ -7409,7 +8450,21 @@ Internet-Draft TE Common YANG Types January 2024 > a Backward-Recursive Path Computation (BRPC) downstream > PCE or a child PCE."; > reference - > "RFC5441, RFC8685"; + + + +Busi, et al. Expires 20 August 2024 [Page 151] + +Internet-Draft TE Common YANG Types February 2024 + + + > "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + > Procedure to Compute Shortest Constrained Inter-Domain + > Traffic Engineering Label Switched Paths + > + > RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture"; > } > > identity path-computation-error-pce-unavailable { @@ -7420,10 +8475,11 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 31 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5440: Path Computation Element (PCE) Communication - > Protocol (PCEP); + > "RFC 5440: Path Computation Element (PCE) Communication + > Protocol (PCEP) > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-inclusion-hop { @@ -7442,19 +8498,22 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 19 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture + > + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; + > } + > -Busi, et al. Expires 1 August 2024 [Page 133] +Busi, et al. Expires 20 August 2024 [Page 152] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - > "RFC8685; - > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; - > } - > > identity path-computation-error-no-resource { > base path-computation-error-reason; > description @@ -7464,9 +8523,12 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 20 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-child-pce-unresponsive { @@ -7478,9 +8540,12 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 21 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-domain-unknown { @@ -7492,20 +8557,23 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 22 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8685; - > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; - > } + > "RFC 8685: Path Computation Element Communication Protocol + > (PCEP) Extensions for the Hierarchical Path Computation + > Element (H-PCE) Architecture > - > identity path-computation-error-p2mp { + > https://www.iana.org/assignments/pcep -Busi, et al. Expires 1 August 2024 [Page 134] +Busi, et al. Expires 20 August 2024 [Page 153] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + > /pcep.xhtml#no-path-vector-tlv"; + > } + > + > identity path-computation-error-p2mp { > base path-computation-error-reason; > description > "Path computation has failed because of P2MP reachability @@ -7514,9 +8582,12 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 24 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC8306; + > "RFC 8306: Extensions to the Path Computation Element + > Communication Protocol (PCEP) for Point-to-Multipoint + > Traffic Engineering Label Switched Paths > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-migration { @@ -7528,9 +8599,12 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 26 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5557; + > "RFC 5557: Path Computation Element Communication Protocol + > (PCEP) Requirements and Protocol Extensions in Support of + > Global Concurrent Optimization > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-solution { @@ -7542,9 +8616,20 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 25 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5557; + > "RFC 5557: Path Computation Element Communication Protocol + > (PCEP) Requirements and Protocol Extensions in Support of + + + +Busi, et al. Expires 20 August 2024 [Page 154] + +Internet-Draft TE Common YANG Types February 2024 + + + > Global Concurrent Optimization > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-pks-expansion { @@ -7554,19 +8639,14 @@ Internet-Draft TE Common YANG Types January 2024 > (PKS) expansion failure. > > It corresponds to bit 27 of the Flags field of the - - - -Busi, et al. Expires 1 August 2024 [Page 135] - -Internet-Draft TE Common YANG Types January 2024 - - > NO-PATH-VECTOR TLV."; > reference - > "RFC5520; + > "RFC 5520: Preserving Topology Confidentiality in + > Inter-Domain Path Computation Using a Path-Key-Based + > Mechanism > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-brpc-chain-unavailable { @@ -7578,9 +8658,12 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 28 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5441; + > "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + > Procedure to Compute Shortest Constrained Inter-Domain + > Traffic Engineering Label Switched Paths > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-source-unknown { @@ -7591,11 +8674,20 @@ Internet-Draft TE Common YANG Types January 2024 > > It corresponds to bit 29 of the Flags field of the > NO-PATH-VECTOR TLV."; + + + +Busi, et al. Expires 20 August 2024 [Page 155] + +Internet-Draft TE Common YANG Types February 2024 + + > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-unknown { @@ -7607,18 +8699,11 @@ Internet-Draft TE Common YANG Types January 2024 > It corresponds to bit 30 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > - - - -Busi, et al. Expires 1 August 2024 [Page 136] - -Internet-Draft TE Common YANG Types January 2024 - - - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-server { @@ -7627,10 +8712,11 @@ Internet-Draft TE Common YANG Types January 2024 > "Path computation has failed because path computation > server is unavailable."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > - > https://www.iana.org/assignments/pcep/pcep.xhtml"; + > https://www.iana.org/assignments/pcep + > /pcep.xhtml#no-path-vector-tlv"; > } > > // CHANGE NOTE: The base identity protocol-origin-type and @@ -7644,6 +8730,14 @@ Internet-Draft TE Common YANG Types January 2024 > > identity protocol-origin-api { > base protocol-origin-type; + + + +Busi, et al. Expires 20 August 2024 [Page 156] + +Internet-Draft TE Common YANG Types February 2024 + + > description > "Protocol origin is via Application Programmable Interface > (API)."; @@ -7655,7 +8749,7 @@ Internet-Draft TE Common YANG Types January 2024 > "Protocol origin is Path Computation Engine Protocol > (PCEP)."; > reference - > "RFC5440: Path Computation Element (PCE) Communication + > "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP)"; > } > @@ -7663,17 +8757,9 @@ Internet-Draft TE Common YANG Types January 2024 > base protocol-origin-type; > description > "Protocol origin is Border Gateway Protocol (BGP)."; - > reference "RFC9012"; + > reference "RFC 9012"; > } > - - - -Busi, et al. Expires 1 August 2024 [Page 137] - -Internet-Draft TE Common YANG Types January 2024 - - > // CHANGE NOTE: The base identity svec-objective-function-type > // and its derived identities below have been > // added in this module revision @@ -7682,8 +8768,8 @@ Internet-Draft TE Common YANG Types January 2024 > description > "Base identity for SVEC objective function type."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-agg-bandwidth-consumption { @@ -7692,18 +8778,26 @@ Internet-Draft TE Common YANG Types January 2024 > "Objective function for minimizing aggregate bandwidth > consumption (MBC)."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-load-most-loaded-link { > base svec-objective-function-type; > description > "Objective function for minimizing the load on the link that + + + +Busi, et al. Expires 20 August 2024 [Page 157] + +Internet-Draft TE Common YANG Types February 2024 + + > is carrying the highest load (MLL)."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-cost-path-set { @@ -7712,8 +8806,8 @@ Internet-Draft TE Common YANG Types January 2024 > "Objective function for minimizing the cost on a path set > (MCC)."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-common-transit-domain { @@ -7721,18 +8815,10 @@ Internet-Draft TE Common YANG Types January 2024 > description > "Objective function for minimizing the number of common > transit domains (MCTD)."; - > reference - - - -Busi, et al. Expires 1 August 2024 [Page 138] - -Internet-Draft TE Common YANG Types January 2024 - - - > "RFC8685: Path Computation Element Communication Protocol + > reference + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation - > Element (H-PCE) Architecture."; + > Element (H-PCE) Architecture"; > } > > identity svec-of-minimize-shared-link { @@ -7741,7 +8827,7 @@ Internet-Draft TE Common YANG Types January 2024 > "Objective function for minimizing the number of shared > links (MSL)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -7752,10 +8838,18 @@ Internet-Draft TE Common YANG Types January 2024 > "Objective function for minimizing the number of shared > Shared Risk Link Groups (SRLG) (MSS)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } + + + +Busi, et al. Expires 20 August 2024 [Page 158] + +Internet-Draft TE Common YANG Types February 2024 + + > > identity svec-of-minimize-shared-nodes { > base svec-objective-function-type; @@ -7763,7 +8857,7 @@ Internet-Draft TE Common YANG Types January 2024 > "Objective function for minimizing the number of shared > nodes (MSN)."; > reference - > "RFC8685: Path Computation Element Communication Protocol + > "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -7776,43 +8870,43 @@ Internet-Draft TE Common YANG Types January 2024 > description > "Base identity for SVEC metric type."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; - - - -Busi, et al. Expires 1 August 2024 [Page 139] - -Internet-Draft TE Common YANG Types January 2024 - - + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - > identity svec-metric-cumul-te { + > identity svec-metric-cumulative-te { > base svec-metric-type; > description > "Cumulative TE cost."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - > identity svec-metric-cumul-igp { + > identity svec-metric-cumulative-igp { > base svec-metric-type; > description > "Cumulative IGP cost."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - > identity svec-metric-cumul-hop { + > identity svec-metric-cumulative-hop { > base svec-metric-type; > description > "Cumulative Hop path metric."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + + + +Busi, et al. Expires 20 August 2024 [Page 159] + +Internet-Draft TE Common YANG Types February 2024 + + + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-aggregate-bandwidth-consumption { @@ -7820,8 +8914,8 @@ Internet-Draft TE Common YANG Types January 2024 > description > "Aggregate bandwidth consumption."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-load-of-the-most-loaded-link { @@ -7829,23 +8923,29 @@ Internet-Draft TE Common YANG Types January 2024 > description > "Load of the most loaded link."; > reference - > "RFC5541: Encoding of Objective Functions in the Path - > Computation Element Communication Protocol (PCEP)."; + > "RFC 5541: Encoding of Objective Functions in the Path + > Computation Element Communication Protocol (PCEP)"; > } > - 2506a3121,3123 - - - -Busi, et al. Expires 1 August 2024 [Page 140] - -Internet-Draft TE Common YANG Types January 2024 - - + 2221,2225c3105,3111 + < "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions + < RFC 7823: Performance-Based Path Selection for Explicitly + < Routed Label Switched Paths (LSPs) Using TE Metric + < Extensions + < RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + --- + > "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensionsù + > + > RFC 7823: Performance-Based Path Selection for Explicitly + > Routed Label Switched Paths (LSPs) Using TE Metric + > Extensions + > + > RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + 2506a3393,3395 > // CHANGE NOTE: The explicit-route-hop grouping below has been > // updated in this module revision > // RFC Editor: remove the note above and this note - 2514a3132,3140 + 2514a3404,3412 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; @@ -7854,10 +8954,18 @@ Internet-Draft TE Common YANG Types January 2024 > type nw:node-id; > description > "The identifier of a node in the topology."; + + + +Busi, et al. Expires 20 August 2024 [Page 160] + +Internet-Draft TE Common YANG Types February 2024 + + > } - 2517d3142 + 2517d3414 < mandatory true; - 2566a3192,3202 + 2566a3464,3474 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description @@ -7869,95 +8977,166 @@ Internet-Draft TE Common YANG Types January 2024 > description > "Link Termination Point (LTP) identifier."; > } - 2569d3204 + 2569d3476 < mandatory true; - 2574a3210,3214 + 2574a3482,3486 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } - 2577d3216 + 2577d3488 < mandatory true; - 2646a3286,3289 + 2631a3543,3545 + > // CHANGE NOTE: The explicit-route-hop grouping below has been + > // updated in this module revision + > // RFC Editor: remove the note above and this note + 2646a3561,3564 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; > } - 2648a3292,3296 + 2648a3567,3571 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } - - - -Busi, et al. Expires 1 August 2024 [Page 141] - -Internet-Draft TE Common YANG Types January 2024 - - - 2651d3298 + 2651d3573 < mandatory true; - 2696a3344,3354 + 2696a3619,3629 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description > "At least one node identifier and at least one Link > Termination Point (LTP) identifier MUST be present."; + + + +Busi, et al. Expires 20 August 2024 [Page 161] + +Internet-Draft TE Common YANG Types February 2024 + + > } > leaf link-tp-id-uri { > type nt:tp-id; > description > "Link Termination Point (LTP) identifier."; > } - 2699d3356 + 2699d3631 < mandatory true; - 2704a3362,3366 + 2704a3637,3641 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } - 2968a3631,3635 + 2881a3819,3821 + > // CHANGE NOTE: The grouping optimization-metric-entry below has + > // been updated in this module revision + > // RFC Editor: remove the note above and this note + 2887c3827 + < base path-metric-type; + --- + > base path-metric-optimization-type; + 2964a3905,3907 + > // CHANGE NOTE: The grouping tunnel-constraints below has + > // been updated in this module revision + > // RFC Editor: remove the note above and this note + 2968a3912,3916 > leaf network-id { > type nw:network-id; > description > "The network topology identifier."; > } - 2977c3644,3647 + 2972a3921,3923 + > // CHANGE NOTE: The grouping path-constraints-route-objects below + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + 2977c3928 < container explicit-route-objects-always { --- - > // CHANGE NOTE: The explicit-route-objects container below has - > // been updated in this module revision - > // RFC Editor: remove the note above and this note > container explicit-route-objects { - 2979c3649 + 2979c3930 < "Container for the 'exclude route' object list."; --- > "Container for the explicit route object lists."; - 3124,3126c3794,3800 + 3101a4053,4055 + > // CHANGE NOTE: The grouping generic-path-metric-bounds below + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + + + +Busi, et al. Expires 20 August 2024 [Page 162] + +Internet-Draft TE Common YANG Types February 2024 + + + 3107c4061 + < "TE path metric bounds container."; + --- + > "Top-level container for the list of path metric bounds."; + 3111c4065,4073 + < "List of TE path metric bounds."; + --- + > "List of path metric bounds, which can apply to link and + > path metrics. + > + > TE paths which have at least one path metric which + > exceeds the specified bounds MUST NOT be selected. + > + > TE paths that traverse TE links which have at least one + > link metric which exceeds the specified bounds MUST NOT + > be selected."; + 3114c4076 + < base path-metric-type; + --- + > base link-path-metric-type; + 3124,3126c4086,4092 < "Upper bound on the end-to-end TE path metric. A zero < indicates an unbounded upper limit for the specific < 'metric-type'."; --- - > "Upper bound on the end-to-end TE path metric. + > "Upper bound on the specified 'metric-type'. > > A zero indicates an unbounded upper limit for the - > specific 'metric-type'. + > specificied 'metric-type'. + > + > The unit of is interpreted in the context of the + > 'metric-type' identity."; + 3131a4098,4100 + > // CHANGE NOTE: The grouping generic-path-metric-bounds below + > // has been updated in this module revision + > // RFC Editor: remove the note above and this note + 3154c4123,4127 + < "Container for the list of tiebreakers."; + --- + > "Container for the list of tiebreakers. + > + > This container has been obsoleted by the tiebreaker + > leaf."; + > status deprecated; + 3189a4163,4171 + > leaf tiebreaker { + > type identityref { + > base path-tiebreaker-type; -Busi, et al. Expires 1 August 2024 [Page 142] +Busi, et al. Expires 20 August 2024 [Page 163] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 - > - > The unit of is interpreted in the context of the - > path-metric-type."; - 3379c4053,4112 + > } + > default "te-types:path-tiebreaker-random"; + > description + > "The tiebreaker criteria to apply on an equally favored set + > of paths, in order to pick the best."; + > } + 3379c4361,4420 < } \ No newline at end of file --- @@ -7976,7 +9155,7 @@ Internet-Draft TE Common YANG Types January 2024 > description > "LSP encoding type."; > reference - > "RFC3945"; + > "RFC 3945"; > } > leaf switching-type { > type identityref { @@ -7985,7 +9164,7 @@ Internet-Draft TE Common YANG Types January 2024 > description > "LSP switching type."; > reference - > "RFC3945"; + > "RFC 3945"; > } > } > @@ -7999,17 +9178,17 @@ Internet-Draft TE Common YANG Types January 2024 > type te-gen-node-id; > description > "The identifier of the node. Can be represented as IP - > address or dotted quad address or as an URI."; - > } - > leaf type { -Busi, et al. Expires 1 August 2024 [Page 143] +Busi, et al. Expires 20 August 2024 [Page 164] -Internet-Draft TE Common YANG Types January 2024 +Internet-Draft TE Common YANG Types February 2024 + > address or dotted quad address or as an URI."; + > } + > leaf type { > type enumeration { > enum ip { > description @@ -8058,293 +9237,297 @@ A.2. Packet TE Types YANG Diffs - - - -Busi, et al. Expires 1 August 2024 [Page 144] - -Internet-Draft TE Common YANG Types January 2024 - - - 11c11 - < "RFC 8776: Common YANG Data Types for Traffic Engineering"; - --- - > "RFCXXXX: Common YANG Data Types for Traffic Engineering"; - 12a13,14 - > // RFC Editor: replace XXXX with actual RFC number - > // and remove this note - 22c24 - < - --- - > - 37,39c39,49 - < data type definitions specific to MPLS TE. The model fully - < conforms to the Network Management Datastore Architecture - < (NMDA). - --- - > data type definitions specific to Packet Traffic Enginnering - > (TE). - > - > The model fully conforms to the Network Management Datastore - > Architecture (NMDA). - > - > The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL - > NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', - > 'MAY', and 'OPTIONAL' in this document are to be interpreted as - > described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, - > they appear in all capitals, as shown here. - 41c51 - < Copyright (c) 2020 IETF Trust and the persons identified as - --- - > Copyright (c) 2024 IETF Trust and the persons identified as - 46c56 - < the license terms contained in, the Simplified BSD License set - --- - > the license terms contained in, the Revised BSD License set - 51,52c61,80 - < This version of this YANG module is part of RFC 8776; see the - < RFC itself for full legal notices."; - --- - > This version of this YANG module is part of RFC XXXX - > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself - > for full legal notices."; - > revision 2024-01-25 { - > description - > "Added common TE packet identities: - > - bandwidth-profile-type; - > - path-metric-loss; - > - path-metric-delay-variation. - - - -Busi, et al. Expires 1 August 2024 [Page 145] - -Internet-Draft TE Common YANG Types January 2024 - - - > - > Added common TE packet groupings: - > - te-packet-path-bandwidth; - > - te-packet-link-bandwidth. - > - > Updated module description."; - > reference - > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; - > } - > // RFC Editor: replace XXXX with actual RFC number, update date - > // information and remove this note - 61c89,187 - < /** - --- - > /* - > * Identities - > */ - > - > // CHANGE NOTE: The base identity bandwidth-profile-type and - > // its derived identities below have been - > // added in this module revision - > // RFC Editor: remove the note above and this note - > identity bandwidth-profile-type { - > description - > "Bandwidth Profile Types"; - > } - > - > identity mef-10-bwp { - > base bandwidth-profile-type; - > description - > "MEF 10 Bandwidth Profile"; - > reference - > "MEF 10.3: Ethernet Services Attributes Phase 3"; - > } - > - > identity rfc-2697-bwp { - > base bandwidth-profile-type; - > description - > "RFC 2697 Bandwidth Profile"; - > reference - > "RFC2697: A Single Rate Three Color Marker"; - > } - > - > identity rfc-2698-bwp { - > base bandwidth-profile-type; - > description - > "RFC 2698 Bandwidth Profile"; - > reference - - - -Busi, et al. Expires 1 August 2024 [Page 146] - -Internet-Draft TE Common YANG Types January 2024 - - - > "RFC2698: A Two Rate Three Color Marker"; - > } - > - > identity rfc-4115-bwp { - > base bandwidth-profile-type; - > description - > "RFC 4115 Bandwidth Profile"; - > reference - > "RFC4115: A Differentiated Service Two-Rate, Three-Color - > Marker with Efficient Handling of in-Profile Traffic"; - > } - > - > // CHANGE NOTE: The identity path-metric-loss below has - > // been added in this module revision - > // RFC Editor: remove the note above and this note - > identity path-metric-loss { - > base te-types:path-metric-type; - > description - > "The path loss (as a packet percentage) metric type - > encodes a function of the unidirectional loss metrics of all - > links traversed by a P2P path. - > - > The basic unit is 0.000003%, - > where (2^24 - 2) or 50.331642% is the maximum value of the - > path loss percentage that can be expressed. - > - > Values that are larger than the maximum value SHOULD be - > encoded as the maximum value."; - > reference - > "RFC8233: Extensions to the Path Computation Element - > Communication Protocol (PCEP) to Compute Service-Aware Label - > Switched Paths (LSPs); - > - > RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; - > - > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - > } - > - > // CHANGE NOTE: The identity path-metric-delay-variation below has - > // been added in this module revision - > // RFC Editor: remove the note above and this note - > identity path-metric-delay-variation { - > base te-types:path-metric-type; - > description - > "The path delay variation encodes the sum of the unidirectional - > delay variation metrics of all links traversed by a P2P path. - > - > The path delay variation metric unit is in microseconds, where - - - -Busi, et al. Expires 1 August 2024 [Page 147] - -Internet-Draft TE Common YANG Types January 2024 - - - > (2^24 - 1) or 16,777,215 microseconds (16.777215 sec) is the - > maximum value of the path delay variation that can be - > expressed. - > - > Values that are larger than the maximum value SHOULD be - > encoded as the maximum value."; - > reference - > "RFC8233: Extensions to the Path Computation Element - > Communication Protocol (PCEP) to Compute Service-Aware Label - > Switched Paths (LSPs); - > - > RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; - > - > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - > } - > - > /* - 180a307,310 - > /* - > * Groupings - > */ - > - 472a603,672 - > } - > } - > - > // CHANGE NOTE: The te-packet-path-bandwidth below has been - > // added in this module revision - > // RFC Editor: remove the note above and this note - > grouping te-packet-path-bandwidth { - > description - > "Path bandwidth for Packet. "; - > leaf bandwidth-profile-name { - > type string; - > description "Name of Bandwidth Profile."; - > } - > leaf bandwidth-profile-type { - > type identityref { - > base bandwidth-profile-type; - > } - > description "Type of Bandwidth Profile."; - > } - > leaf cir { - > type uint64; - > units "bits/second"; - > mandatory true; - > description - > "Committed Information Rate (CIR)."; - - - -Busi, et al. Expires 1 August 2024 [Page 148] - -Internet-Draft TE Common YANG Types January 2024 - - - > } - > leaf cbs { - > type uint64; - > units "bits/second"; - > mandatory true; - > description - > "Committed Burst Size (CBS)."; - > } - > leaf eir { - > type uint64; - > units "bits/second"; - > description - > "Excess Information Rate (EIR)."; - > } - > leaf ebs { - > type uint64; - > units "bytes"; - > description - > "Excess Burst Size (EBS)."; - > } - > leaf pir { - > type uint64; - > units "bits/second"; - > description - > "Peak Information Rate (PIR)."; - > } - > leaf pbs { - > type uint64; - > units "bytes"; - > description - > "Peak Burst Size (PBS)."; - > } - > } - > - > // CHANGE NOTE: The te-packet-path-bandwidth below has been - > // added in this module revision - > // RFC Editor: remove the note above and this note - > grouping te-packet-link-bandwidth { - > description - > "Link Bandwidth for Packet. "; - > leaf packet-bandwidth { - > type uint64; - > units "bits/second"; - > description - > "Available bandwith value."; - - - - - - -Busi, et al. Expires 1 August 2024 [Page 149] - -Internet-Draft TE Common YANG Types January 2024 - +Busi, et al. Expires 20 August 2024 [Page 165] + +Internet-Draft TE Common YANG Types February 2024 + + + 11c11 + < "RFC 8776: Common YANG Data Types for Traffic Engineering"; + --- + > "RFCXXXX: Common YANG Data Types for Traffic Engineering"; + 12a13,14 + > // RFC Editor: replace XXXX with actual RFC number + > // and remove this note + 22c24 + < + --- + > + 37,39c39,49 + < data type definitions specific to MPLS TE. The model fully + < conforms to the Network Management Datastore Architecture + < (NMDA). + --- + > data type definitions specific to Packet Traffic Enginnering + > (TE). + > + > The model fully conforms to the Network Management Datastore + > Architecture (NMDA). + > + > The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + > NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + > 'MAY', and 'OPTIONAL' in this document are to be interpreted as + > described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + > they appear in all capitals, as shown here. + 41c51 + < Copyright (c) 2020 IETF Trust and the persons identified as + --- + > Copyright (c) 2024 IETF Trust and the persons identified as + 46c56 + < the license terms contained in, the Simplified BSD License set + --- + > the license terms contained in, the Revised BSD License set + 51,52c61,82 + < This version of this YANG module is part of RFC 8776; see the + < RFC itself for full legal notices."; + --- + > This version of this YANG module is part of RFC XXXX + > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself + > for full legal notices."; + > revision 2024-02-16 { + > description + > "This revision adds the following new identities: + > - bandwidth-profile-type; + > - link-metric-delay-variation; + > - link-metric-loss; + + + +Busi, et al. Expires 20 August 2024 [Page 166] + +Internet-Draft TE Common YANG Types February 2024 + + + > - path-metric-delay-variation; + > - path-metric-loss. + > + > This revision adds the following new groupings: + > - te-packet-path-bandwidth; + > - te-packet-link-bandwidth. + > + > This revision provides also few editorial changes."; + > reference + > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; + > } + > // RFC Editor: replace XXXX with actual RFC number, update date + > // information and remove this note + 61c91,196 + < /** + --- + > /* + > * Identities + > */ + > + > // CHANGE NOTE: The base identity bandwidth-profile-type and + > // its derived identities below have been + > // added in this module revision + > // RFC Editor: remove the note above and this note + > identity bandwidth-profile-type { + > description + > "Bandwidth Profile Types"; + > } + > + > identity mef-10-bwp { + > base bandwidth-profile-type; + > description + > "MEF 10 Bandwidth Profile"; + > reference + > "MEF 10.3: Ethernet Services Attributes Phase 3"; + > } + > + > identity rfc-2697-bwp { + > base bandwidth-profile-type; + > description + > "RFC 2697 Bandwidth Profile"; + > reference + > "RFC2697: A Single Rate Three Color Marker"; + > } + > + > identity rfc-2698-bwp { + > base bandwidth-profile-type; + > description + + + +Busi, et al. Expires 20 August 2024 [Page 167] + +Internet-Draft TE Common YANG Types February 2024 + + + > "RFC 2698 Bandwidth Profile"; + > reference + > "RFC2698: A Two Rate Three Color Marker"; + > } + > + > identity rfc-4115-bwp { + > base bandwidth-profile-type; + > description + > "RFC 4115 Bandwidth Profile"; + > reference + > "RFC4115: A Differentiated Service Two-Rate, Three-Color + > Marker with Efficient Handling of in-Profile Traffic"; + > } + > + > // CHANGE NOTE: The identity link-metric-delay-variation + > // below has been added in this module revision + > // RFC Editor: remove the note above and this note + > identity link-metric-delay-variation { + > base te-types:link-metric-type; + > description + > "The Unidirectional Delay Variation Metric, + > measured in units of microseconds."; + > reference + > "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + > section 4.3 + > + > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + > section 4.3"; + > } + > + > // CHANGE NOTE: The identity link-metric-loss below has + > // been added in this module revision + > // RFC Editor: remove the note above and this note + > identity link-metric-loss { + > base te-types:link-metric-type; + > description + > "The Unidirectional Link Loss Metric, + > measured in units of 0.000003%."; + > reference + > "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + > section 4.4 + > + > RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + > section 4.4"; + > } + > + > // CHANGE NOTE: The identity path-metric-delay-variation + > // below has been added in this module revision + + + +Busi, et al. Expires 20 August 2024 [Page 168] + +Internet-Draft TE Common YANG Types February 2024 + + + > // RFC Editor: remove the note above and this note + > identity path-metric-delay-variation { + > base te-types:path-metric-type; + > description + > "The Path Delay Variation Metric, + > measured in units of microseconds."; + > reference + > "RFC8233: Extensions to the Path Computation Element + > Communication Protocol (PCEP) to Compute Service-Aware Label + > Switched Paths (LSPs), section 3.1.2"; + > } + > + > // CHANGE NOTE: The identity path-metric-loss below has + > // been added in this module revision + > // RFC Editor: remove the note above and this note + > identity path-metric-loss { + > base te-types:path-metric-type; + > description + > "The Path Loss Metric, measured in units of 0.000003%."; + > reference + > "RFC8233: Extensions to the Path Computation Element + > Communication Protocol (PCEP) to Compute Service-Aware Label + > Switched Paths (LSPs), section 3.1.3"; + > } + > + > /* + 180a316,319 + > /* + > * Groupings + > */ + > + 472a612,681 + > } + > } + > + > // CHANGE NOTE: The te-packet-path-bandwidth below has been + > // added in this module revision + > // RFC Editor: remove the note above and this note + > grouping te-packet-path-bandwidth { + > description + > "Path bandwidth for Packet. "; + > leaf bandwidth-profile-name { + > type string; + > description "Name of Bandwidth Profile."; + > } + > leaf bandwidth-profile-type { + > type identityref { + > base bandwidth-profile-type; + + + +Busi, et al. Expires 20 August 2024 [Page 169] + +Internet-Draft TE Common YANG Types February 2024 + + + > } + > description "Type of Bandwidth Profile."; + > } + > leaf cir { + > type uint64; + > units "bits/second"; + > mandatory true; + > description + > "Committed Information Rate (CIR)."; + > } + > leaf cbs { + > type uint64; + > units "bits/second"; + > mandatory true; + > description + > "Committed Burst Size (CBS)."; + > } + > leaf eir { + > type uint64; + > units "bits/second"; + > description + > "Excess Information Rate (EIR)."; + > } + > leaf ebs { + > type uint64; + > units "bytes"; + > description + > "Excess Burst Size (EBS)."; + > } + > leaf pir { + > type uint64; + > units "bits/second"; + > description + > "Peak Information Rate (PIR)."; + > } + > leaf pbs { + > type uint64; + > units "bytes"; + > description + > "Peak Burst Size (PBS)."; + > } + > } + > + > // CHANGE NOTE: The te-packet-path-bandwidth below has been + > // added in this module revision + > // RFC Editor: remove the note above and this note + > grouping te-packet-link-bandwidth { + > description + + + +Busi, et al. Expires 20 August 2024 [Page 170] + +Internet-Draft TE Common YANG Types February 2024 + + + > "Link Bandwidth for Packet. "; + > leaf packet-bandwidth { + > type uint64; + > units "bits/second"; + > description + > "Available bandwith value."; Appendix B. Option Considered for updating RFC8776 @@ -8387,6 +9570,14 @@ Appendix B. Option Considered for updating RFC8776 YANG model to focus the review only to the updates to the ietf-te- types YANG module proposed by this document. + + + +Busi, et al. Expires 20 August 2024 [Page 171] + +Internet-Draft TE Common YANG Types February 2024 + + Based on the feedbacks from IETF 114 discussion, this version has been restructured to become an RFC8776-bis, with some notes, to be removed before publication, to focus the review only to the updates @@ -8395,13 +9586,6 @@ Appendix B. Option Considered for updating RFC8776 During the Netmod WG session at IETF 114, an alternative process has been introduced: - - -Busi, et al. Expires 1 August 2024 [Page 150] - -Internet-Draft TE Common YANG Types January 2024 - - https://datatracker.ietf.org/meeting/114/materials/slides-114-netmod- ad-topic-managing-the-evolution-of-ietf-yang-modules-00.pdf @@ -8441,6 +9625,15 @@ Authors' Addresses Email: aihuaguo.ietf@gmail.com + + + + +Busi, et al. Expires 20 August 2024 [Page 172] + +Internet-Draft TE Common YANG Types February 2024 + + Xufeng Liu Alef Edge Email: xufeng.liu.ietf@gmail.com @@ -8451,13 +9644,6 @@ Authors' Addresses Email: tsaad.net@gmail.com - - -Busi, et al. Expires 1 August 2024 [Page 151] - -Internet-Draft TE Common YANG Types January 2024 - - Igor Bryskin Individual Email: i_bryskin@yahoo.com @@ -8499,14 +9685,4 @@ Internet-Draft TE Common YANG Types January 2024 - - - - - - - - - - -Busi, et al. Expires 1 August 2024 [Page 152] +Busi, et al. Expires 20 August 2024 [Page 173] diff --git a/drafts/te-types-update/draft-ietf-teas-rfc8776-update.xml b/drafts/te-types-update/draft-ietf-teas-rfc8776-update.xml index ba8ec61..cf519dd 100644 --- a/drafts/te-types-update/draft-ietf-teas-rfc8776-update.xml +++ b/drafts/te-types-update/draft-ietf-teas-rfc8776-update.xml @@ -13,7 +13,7 @@ - + Common YANG Data Types for Traffic Engineering @@ -48,7 +48,7 @@ - + TEAS Working Group @@ -57,7 +57,7 @@ -This document defines a collection of common data types and groupings in YANG data modeling language. These derived common types and groupings are intended to be imported by modules that model Traffic Engineering (TE) configuration and state capabilities. This document obsoletes RFC 8776. +This document defines a collection of common data types, identities, and groupings in YANG data modeling language. These derived common types and groupings are intended to be imported by modules that model Traffic Engineering (TE) configuration and state capabilities. This document obsoletes RFC 8776. @@ -74,15 +74,9 @@ YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols such as the Network Configuration Protocol (NETCONF) . The YANG language supports a small set of built-in data types and provides mechanisms to derive other types from the built-in types. -This document introduces a collection of common data types derived from the built-in YANG data types. The derived types and groupings are designed to be the common types applicable for modeling Traffic Engineering (TE) features in model(s) defined outside of this document. +This document introduces a collection of common data types derived from the built-in YANG data types. The derived data types, identities, and groupings are designed to be the common definitions applicable for modeling Traffic Engineering (TE) features in model(s) defined outside of this document. -This document adds few additional common data types, identities, and groupings to both the "ietf-te-types" and the "ietf-te-packet-types" YANG models and obsoletes . - -For further details, see the revision statements of the YANG modules in Sections X and Y or the summary in Appendix A. - -CHANGE NOTE: These definitions have been developed in , and and are quite mature: and in particular are in WG Last Call and some definitions have been moved to this document as part of WG LC comments resolution. - -RFC Editor: remove the CHANGE NOTE above and this note +This document adds new common data types, identities, and groupings to both the "ietf-te-types" and the "ietf-te-packet-types" YANG models and obsoletes . For further details, see the revision statements of the YANG modules in and , or the summary in .
Requirements Notation @@ -694,37 +688,88 @@ module ietf-te-types { This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; - revision 2024-01-29 { - description - "Added: - - base identity lsp-provisioning-error-reason; - - identity association-type-diversity; - - identity tunnel-admin-state-auto; - - identity lsp-restoration-restore-none; - - identity restoration-scheme-rerouting; - - base identity path-computation-error-reason and - its derived identities; - - base identity protocol-origin-type and - its derived identities; - - base identity svec-objective-function-type and its derived - identities; - - base identity svec-metric-type and its derived identities; - - grouping encoding-and-switching-type. - - Updated: - - description of the base identity objective-function-type; - - description and reference of identity action-exercise; - - typedef te-node-id to support also 16 octects TE identifiers. - - Obsoleted: - - identity of-minimize-agg-bandwidth-consumption; - - identity of-minimize-load-most-loaded-link; - - identity of-minimize-cost-path-set; - - identity lsp-protection-reroute-extra; - - identity lsp-protection-reroute. - - Container explicit-route-objects-always renamed as - explicit-route-objects."; + revision 2024-02-16 { + description + "This revision adds the following new identities: + - lsp-provisioning-error-reason; + - association-type-diversity; + - tunnel-admin-state-auto; + - lsp-restoration-restore-none; + - restoration-scheme-rerouting; + - path-metric-optimization-type; + - link-path-metric-type; + - link-metric-type and its derived identities; + - path-computation-error-reason and its derived identities; + - protocol-origin-type and its derived identities; + - svec-objective-function-type and its derived identities; + - svec-metric-type and its derived identities. + + This revision adds the following new data types: + - path-type; + - te-gen-node-id. + + This revision adds the following new groupings: + - encoding-and-switching-type; + - te-generic-node-id. + + This revision updates the following identities: + - objective-function-type; + - action-exercise; + - path-metric-type; + - path-metric-te; + - path-metric-igp; + - path-metric-hop; + - path-metric-delay-average; + - path-metric-delay-minimum; + - path-metric-residual-bandwidth; + - path-metric-optimize-includes; + - path-metric-optimize-excludes; + - te-optimization-criterion. + + This revision updates the following data types: + - te-node-id. + + This revision updates the following groupings: + - explicit-route-hop: + - adds the following leaves: + - node-id-uri; + - link-tp-id-uri; + - updates the following leaves: + - node-id; + - link-tp-id; + - record-route-state: + - adds the following leaves: + - node-id-uri; + - link-tp-id-uri; + - updates the following leaves: + - node-id; + - link-tp-id; + - optimization-metric-entry: + - updates the following leaves: + - metric-type; + - tunnel-constraints; + - adds the following leaves: + - network-id; + - path-constraints-route-objects: + - updates the following containers: + - explicit-route-objects-always; + - generic-path-metric-bounds: + - updates the following leaves: + - metric-type; + - generic-path-optimization + - adds the following leaves: + - tiebreaker; + - deprecate the following containers: + - tiebreakers. + + This revision obsoletes the following identities: + - of-minimize-agg-bandwidth-consumption; + - of-minimize-load-most-loaded-link; + - of-minimize-cost-path-set; + - lsp-protection-reroute-extra; + - lsp-protection-reroute. + + This revision provides also few editorial changes."; reference "RFC XXXX: Common YANG Data Types for Traffic Engineering"; } @@ -733,7 +778,7 @@ module ietf-te-types { revision 2020-06-10 { description - "Latest revision of TE types."; + "Initial Version of TE types."; reference "RFC 8776: Common YANG Data Types for Traffic Engineering"; } @@ -750,13 +795,16 @@ module ietf-te-types { description "Administrative group / resource class / color representation in 'hex-string' type. + The most significant byte in the hex-string is the farthest to the left in the byte sequence. Leading zero bytes in the configured value may be omitted for brevity."; reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2 + RFC 5305: IS-IS Extensions for Traffic Engineering + RFC 7308: Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)"; } @@ -775,6 +823,7 @@ module ietf-te-types { description "Extended administrative group / resource class / color representation in 'hex-string' type. + The most significant byte in the hex-string is the farthest to the left in the byte sequence. Leading zero bytes in the configured value may be omitted for brevity."; @@ -819,9 +868,11 @@ module ietf-te-types { bit not set), abnormal (anomalous bit set), or unknown."; reference "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions + RFC 7823: Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric Extensions + RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; } @@ -927,12 +978,15 @@ module ietf-te-types { description "An identifier to uniquely identify an operator, which can be either a provider or a client. + The definition of this type is taken from RFCs 6370 and 5003. + This attribute type is used solely to provide a globally unique context for TE topologies."; reference "RFC 5003: Attachment Individual Identifier (AII) Types for Aggregation + RFC 6370: MPLS Transport Profile (MPLS-TP) Identifiers"; } @@ -1197,6 +1251,7 @@ module ietf-te-types { } description "An identifier for a topology. + It is optional to have one or more prefixes at the beginning, separated by colons. The prefixes can be 'network-types' as defined in the 'ietf-network' module in RFC 8345, to help the @@ -1215,6 +1270,7 @@ module ietf-te-types { } description "An identifier for a TE link endpoint on a node. + This attribute is mapped to a local or remote link identifier as defined in RFCs 3630 and 5305."; reference @@ -1718,7 +1774,7 @@ module ietf-te-types { "Association Type diversity used to associate LSPs whose paths are to be diverse from each other."; reference - "RFC8800: Path Computation Element Communication Protocol + "RFC 8800: Path Computation Element Communication Protocol (PCEP) Extension for Label Switched Path (LSP) Diversity Constraint Signaling"; } @@ -1729,7 +1785,7 @@ module ietf-te-types { // RFC Editor: remove the note above and this note identity objective-function-type { description - "Base identity for path objective function type."; + "Base identity for path objective function types."; } identity of-minimize-cost-path { @@ -1768,7 +1824,11 @@ module ietf-te-types { status obsolete; description "Objective function for minimizing aggregate bandwidth - consumption."; + consumption. + + This identity has been obsoleted: the + 'svec-of-minimize-agg-bandwidth-consumption' identity SHOULD + be used instead."; reference "RFC 5541: Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"; @@ -1782,7 +1842,11 @@ module ietf-te-types { status obsolete; description "Objective function for minimizing the load on the link that - is carrying the highest load."; + is carrying the highest load. + + This identity has been obsoleted: the + 'svec-of-minimize-load-most-loaded-link' identity SHOULD + be used instead."; reference "RFC 5541: Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"; @@ -1795,7 +1859,11 @@ module ietf-te-types { base objective-function-type; status obsolete; description - "Objective function for minimizing the cost on a path set."; + "Objective function for minimizing the cost on a path set. + + This identity has been obsoleted: the + 'svec-of-minimize-cost-path-set' identity SHOULD + be used instead."; reference "RFC 5541: Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"; @@ -1806,16 +1874,23 @@ module ietf-te-types { "Base identity for supported path computation mechanisms."; } + // CHANGE NOTE: The reference of the identity path-locally-computed + // below has been updated in this module revision + // RFC Editor: remove the note above and this note identity path-locally-computed { base path-computation-method; description "Indicates a constrained-path LSP in which the path is computed by the local LER."; reference - "RFC 3272: Overview and Principles of Internet Traffic - Engineering, Section 5.4"; + "RFC 9522: Overview and Principles of Internet Traffic + Engineering, Section 4.4"; } + // CHANGE NOTE: The reference of the identity + // path-externally-queried below has been updated + // in this module revision + // RFC Editor: remove the note above and this note identity path-externally-queried { base path-computation-method; description @@ -1827,12 +1902,17 @@ module ietf-te-types { returned by the external source may require further local computation on the device."; reference - "RFC 3272: Overview and Principles of Internet Traffic + "RFC 9522: Overview and Principles of Internet Traffic Engineering + RFC 4657: Path Computation Element (PCE) Communication Protocol Generic Requirements"; } + // CHANGE NOTE: The reference of the identity + // path-explicitly-defined below has been updated + // in this module revision + // RFC Editor: remove the note above and this note identity path-explicitly-defined { base path-computation-method; description @@ -1841,7 +1921,8 @@ module ietf-te-types { hops."; reference "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels - RFC 3272: Overview and Principles of Internet Traffic + + RFC 9522: Overview and Principles of Internet Traffic Engineering"; } @@ -2730,89 +2811,231 @@ module ietf-te-types { Protocol-Traffic Engineering (RSVP-TE)"; } - // CHANGE NOTE: The description of the identity path-metric-type - // has been updated in this module revision + // CHANGE NOTE: The path-metric-optimization-type base identity + // has been added in this module revision // RFC Editor: remove the note above and this note - identity path-metric-type { + identity path-metric-optimization-type { description - "Base identity for the path metric type. - - Derived identities SHOULD describe the unit and maximum value - of the path metric types they define."; + "Base identity used to define the path metric optimization + types."; } - identity path-metric-te { - base path-metric-type; - description - "TE path metric."; - reference - "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a - second MPLS Traffic Engineering (TE) Metric"; - } - - identity path-metric-igp { - base path-metric-type; - description - "IGP path metric."; - reference - "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a - second MPLS Traffic Engineering (TE) Metric"; - } - - // CHANGE NOTE: The reference for the identity path-metric-hop + // CHANGE NOTE: The link-path-metric-type base identity // has been added in this module revision // RFC Editor: remove the note above and this note - identity path-metric-hop { - base path-metric-type; + identity link-path-metric-type { description - "Hop path metric."; - reference - "RFC5440: Path Computation Element (PCE) Communication - Protocol (PCEP)"; + "Base identity used to define the link and the path metric + types. + + The unit of the path metric value is interpreted in the + context of the path metric type and the derived identities + SHOULD describe the unit of the path metric types they + define."; } + // CHANGE NOTE: The link-metric-type base identity + // and its derived identities + // have been added in this module revision + // RFC Editor: remove the note above and this note + identity link-metric-type { + base link-path-metric-type; + description + "Base identity for the link metric types."; + } - identity path-metric-delay-average { - base path-metric-type; - description - "Average unidirectional link delay."; - reference - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; - } + identity link-metric-te { + base link-metric-type; + description + "Traffic Engineering (TE) Link Metric."; + reference + "RFC 3630: Traffic Engineering (TE) Extensions to OSPF + Version 2, section 2.5.5 - identity path-metric-delay-minimum { - base path-metric-type; - description - "Minimum unidirectional link delay."; - reference - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; - } + RFC 5305: IS-IS Extensions for Traffic Engineering, + section 3.7"; + } - identity path-metric-residual-bandwidth { - base path-metric-type; - description - "Unidirectional Residual Bandwidth, which is defined to be - Maximum Bandwidth (RFC 3630) minus the bandwidth currently - allocated to LSPs."; - reference - "RFC 3630: Traffic Engineering (TE) Extensions to OSPF - Version 2 - RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; - } + identity link-metric-igp { + base link-metric-type; + description + "Interior Gateway Protocol (IGP) Link Metric."; + reference + "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric + as a second MPLS Traffic Engineering (TE) Metric"; + } - identity path-metric-optimize-includes { - base path-metric-type; - description - "A metric that optimizes the number of included resources - specified in a set."; - } + identity link-metric-delay-average { + base link-metric-type; + description + "Unidirectional Link Delay, measured in units of + microseconds."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.1 + + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.1"; + } - identity path-metric-optimize-excludes { - base path-metric-type; - description - "A metric that optimizes to a maximum the number of excluded - resources specified in a set."; - } + identity link-metric-delay-minimum { + base link-metric-type; + description + "Minimum unidirectional Link Delay, measured in units of + microseconds."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.2 + + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.2"; + } + + identity link-metric-delay-maximum { + base link-metric-type; + description + "Maximum unidirectional Link Delay, measured in units of + microseconds."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.2 + + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.2"; + } + + identity link-metric-residual-bandwidth { + base link-metric-type; + description + "Unidirectional Residual Bandwidth, measured in units of + bytes per second. + + It is defined to be Maximum Bandwidth minus the bandwidth + currently allocated to LSPs."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.5 + + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.5"; + } + + // CHANGE NOTE: The base and the description of the + // path-metric-type identity + // has been updated in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-type { + base link-path-metric-type; + base path-metric-optimization-type; + description + "Base identity for the path metric types."; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-te identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-te { + base path-metric-type; + description + "Traffic Engineering (TE) Path Metric."; + reference + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.8"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-igp identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-igp { + base path-metric-type; + description + "Interior Gateway Protocol (IGP) Path Metric."; + reference + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.8"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-hop identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-hop { + base path-metric-type; + description + "Hop Count Path Metric."; + reference + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.8"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-delay-average identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-delay-average { + base path-metric-type; + description + "The Path Delay Metric, measured in units of + microseconds."; + reference + "RFC8233: Extensions to the Path Computation Element + Communication Protocol (PCEP) to Compute Service-Aware + Label Switched Paths (LSPs), section 3.1.1"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-delay-minimum identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-delay-minimum { + base path-metric-type; + description + "The Path Min Delay Metric, measured in units of + microseconds."; + reference + "I-D.ietf-pce-sid-algo: Carrying SR-Algorithm information + in PCE-based Networks, section 3.5.1"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-residual-bandwidth identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-residual-bandwidth { + base path-metric-type; + description + "The Path Residual Bandwidth, defined as the minimum Link + Residual Bandwidth all the links along the path. + + The Path Residual Bandwidth can be seen as the path + metric associated with the Maximum residual Bandwidth Path + (MBP) objective function."; + reference + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; + } + + // CHANGE NOTE: The base of the path-metric-optimize-includes + // identity has been updated in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-optimize-includes { + base path-metric-optimization-type; + description + "A metric that optimizes the number of included resources + specified in a set."; + } + + // CHANGE NOTE: The base of the path-metric-optimize-excludes + // identity has been updated in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-optimize-excludes { + base path-metric-optimization-type; + description + "A metric that optimizes to a maximum the number of excluded + resources specified in a set."; + } identity path-tiebreaker-type { description @@ -2876,11 +3099,15 @@ module ietf-te-types { RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels"; } + // CHANGE NOTE: The reference of the identity + // te-optimization-criterion below has been updated + // in this module revision + // RFC Editor: remove the note above and this note identity te-optimization-criterion { description "Base identity for the TE optimization criteria."; reference - "RFC 3272: Overview and Principles of Internet Traffic + "RFC 9522: Overview and Principles of Internet Traffic Engineering"; } @@ -2952,8 +3179,8 @@ module ietf-te-types { "Path computation has failed because of an unspecified reason."; reference - "Section 7.5 of RFC5440: Path Computation Element (PCE) - Communication Protocol (PCEP)"; + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.5"; } identity path-computation-error-no-topology { @@ -2973,7 +3200,13 @@ module ietf-te-types { a Backward-Recursive Path Computation (BRPC) downstream PCE or a child PCE."; reference - "RFC5441, RFC8685"; + "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + Procedure to Compute Shortest Constrained Inter-Domain + Traffic Engineering Label Switched Paths + + RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture"; } identity path-computation-error-pce-unavailable { @@ -2984,10 +3217,11 @@ module ietf-te-types { It corresponds to bit 31 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5440: Path Computation Element (PCE) Communication - Protocol (PCEP); + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP) - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-inclusion-hop { @@ -3006,9 +3240,12 @@ module ietf-te-types { It corresponds to bit 19 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-resource { @@ -3020,9 +3257,12 @@ module ietf-te-types { It corresponds to bit 20 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-child-pce-unresponsive { @@ -3034,9 +3274,12 @@ module ietf-te-types { It corresponds to bit 21 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-destination-domain-unknown { @@ -3048,9 +3291,12 @@ module ietf-te-types { It corresponds to bit 22 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-p2mp { @@ -3062,9 +3308,12 @@ module ietf-te-types { It corresponds to bit 24 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8306; + "RFC 8306: Extensions to the Path Computation Element + Communication Protocol (PCEP) for Point-to-Multipoint + Traffic Engineering Label Switched Paths - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-gco-migration { @@ -3076,9 +3325,12 @@ module ietf-te-types { It corresponds to bit 26 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5557; + "RFC 5557: Path Computation Element Communication Protocol + (PCEP) Requirements and Protocol Extensions in Support of + Global Concurrent Optimization - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-gco-solution { @@ -3090,9 +3342,12 @@ module ietf-te-types { It corresponds to bit 25 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5557; + "RFC 5557: Path Computation Element Communication Protocol + (PCEP) Requirements and Protocol Extensions in Support of + Global Concurrent Optimization - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-pks-expansion { @@ -3104,9 +3359,12 @@ module ietf-te-types { It corresponds to bit 27 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5520; + "RFC 5520: Preserving Topology Confidentiality in + Inter-Domain Path Computation Using a Path-Key-Based + Mechanism - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-brpc-chain-unavailable { @@ -3118,9 +3376,12 @@ module ietf-te-types { It corresponds to bit 28 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5441; + "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + Procedure to Compute Shortest Constrained Inter-Domain + Traffic Engineering Label Switched Paths - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-source-unknown { @@ -3132,10 +3393,11 @@ module ietf-te-types { It corresponds to bit 29 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP); - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-destination-unknown { @@ -3147,10 +3409,11 @@ module ietf-te-types { It corresponds to bit 30 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP); - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-server { @@ -3159,10 +3422,11 @@ module ietf-te-types { "Path computation has failed because path computation server is unavailable."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP); - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } // CHANGE NOTE: The base identity protocol-origin-type and @@ -3187,7 +3451,7 @@ module ietf-te-types { "Protocol origin is Path Computation Engine Protocol (PCEP)."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP)"; } @@ -3195,7 +3459,7 @@ module ietf-te-types { base protocol-origin-type; description "Protocol origin is Border Gateway Protocol (BGP)."; - reference "RFC9012"; + reference "RFC 9012"; } // CHANGE NOTE: The base identity svec-objective-function-type @@ -3206,8 +3470,8 @@ module ietf-te-types { description "Base identity for SVEC objective function type."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-agg-bandwidth-consumption { @@ -3216,8 +3480,8 @@ module ietf-te-types { "Objective function for minimizing aggregate bandwidth consumption (MBC)."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-load-most-loaded-link { @@ -3226,8 +3490,8 @@ module ietf-te-types { "Objective function for minimizing the load on the link that is carrying the highest load (MLL)."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-cost-path-set { @@ -3236,8 +3500,8 @@ module ietf-te-types { "Objective function for minimizing the cost on a path set (MCC)."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-common-transit-domain { @@ -3246,9 +3510,9 @@ module ietf-te-types { "Objective function for minimizing the number of common transit domains (MCTD)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation - Element (H-PCE) Architecture."; + Element (H-PCE) Architecture"; } identity svec-of-minimize-shared-link { @@ -3257,7 +3521,7 @@ module ietf-te-types { "Objective function for minimizing the number of shared links (MSL)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture."; } @@ -3268,7 +3532,7 @@ module ietf-te-types { "Objective function for minimizing the number of shared Shared Risk Link Groups (SRLG) (MSS)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture."; } @@ -3279,7 +3543,7 @@ module ietf-te-types { "Objective function for minimizing the number of shared nodes (MSN)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture."; } @@ -3292,35 +3556,35 @@ module ietf-te-types { description "Base identity for SVEC metric type."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } - identity svec-metric-cumul-te { + identity svec-metric-cumulative-te { base svec-metric-type; description "Cumulative TE cost."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } - identity svec-metric-cumul-igp { + identity svec-metric-cumulative-igp { base svec-metric-type; description "Cumulative IGP cost."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } - identity svec-metric-cumul-hop { + identity svec-metric-cumulative-hop { base svec-metric-type; description "Cumulative Hop path metric."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-metric-aggregate-bandwidth-consumption { @@ -3328,8 +3592,8 @@ module ietf-te-types { description "Aggregate bandwidth consumption."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-metric-load-of-the-most-loaded-link { @@ -3337,8 +3601,8 @@ module ietf-te-types { description "Load of the most loaded link."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } /** @@ -3451,11 +3715,13 @@ module ietf-te-types { grouping are applicable to generic TE PM as well as packet TE PM."; reference - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions - RFC 7823: Performance-Based Path Selection for Explicitly - Routed Label Switched Paths (LSPs) Using TE Metric - Extensions - RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensionsù + + RFC 7823: Performance-Based Path Selection for Explicitly + Routed Label Switched Paths (LSPs) Using TE Metric + Extensions + + RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; leaf one-way-delay { type uint32 { range "0..16777215"; @@ -3887,6 +4153,9 @@ module ietf-te-types { } } + // CHANGE NOTE: The explicit-route-hop grouping below has been + // updated in this module revision + // RFC Editor: remove the note above and this note grouping record-route-state { description "The Record Route grouping."; @@ -4160,12 +4429,15 @@ module ietf-te-types { } } + // CHANGE NOTE: The grouping optimization-metric-entry below has + // been updated in this module revision + // RFC Editor: remove the note above and this note grouping optimization-metric-entry { description "Optimization metrics configuration grouping."; leaf metric-type { type identityref { - base path-metric-type; + base path-metric-optimization-type; } description "Identifies the 'metric-type' that the path computation @@ -4243,6 +4515,9 @@ module ietf-te-types { } } + // CHANGE NOTE: The grouping tunnel-constraints below has + // been updated in this module revision + // RFC Editor: remove the note above and this note grouping tunnel-constraints { description "Tunnel constraints grouping that can be set on @@ -4256,13 +4531,13 @@ module ietf-te-types { uses common-constraints; } + // CHANGE NOTE: The grouping path-constraints-route-objects below + // has been updated in this module revision + // RFC Editor: remove the note above and this note grouping path-constraints-route-objects { description "List of route entries to be included or excluded when performing the path computation."; - // CHANGE NOTE: The explicit-route-objects container below has - // been updated in this module revision - // RFC Editor: remove the note above and this note container explicit-route-objects { description "Container for the explicit route object lists."; @@ -4388,19 +4663,30 @@ module ietf-te-types { } } + // CHANGE NOTE: The grouping generic-path-metric-bounds below + // has been updated in this module revision + // RFC Editor: remove the note above and this note grouping generic-path-metric-bounds { description "TE path metric bounds grouping."; container path-metric-bounds { description - "TE path metric bounds container."; + "Top-level container for the list of path metric bounds."; list path-metric-bound { key "metric-type"; description - "List of TE path metric bounds."; + "List of path metric bounds, which can apply to link and + path metrics. + + TE paths which have at least one path metric which + exceeds the specified bounds MUST NOT be selected. + + TE paths that traverse TE links which have at least one + link metric which exceeds the specified bounds MUST NOT + be selected."; leaf metric-type { type identityref { - base path-metric-type; + base link-path-metric-type; } description "Identifies an entry in the list of 'metric-type' items @@ -4410,18 +4696,21 @@ module ietf-te-types { type uint64; default "0"; description - "Upper bound on the end-to-end TE path metric. + "Upper bound on the specified 'metric-type'. A zero indicates an unbounded upper limit for the - specific 'metric-type'. + specificied 'metric-type'. The unit of is interpreted in the context of the - path-metric-type."; + 'metric-type' identity."; } } } } + // CHANGE NOTE: The grouping generic-path-metric-bounds below + // has been updated in this module revision + // RFC Editor: remove the note above and this note grouping generic-path-optimization { description "TE generic path optimization grouping."; @@ -4444,7 +4733,11 @@ module ietf-te-types { /* Tiebreakers */ container tiebreakers { description - "Container for the list of tiebreakers."; + "Container for the list of tiebreakers. + + This container has been obsoleted by the tiebreaker + leaf."; + status deprecated; list tiebreaker { key "tiebreaker-type"; description @@ -4480,6 +4773,15 @@ module ietf-te-types { } } } + leaf tiebreaker { + type identityref { + base path-tiebreaker-type; + } + default "te-types:path-tiebreaker-random"; + description + "The tiebreaker criteria to apply on an equally favored set + of paths, in order to pick the best."; + } } grouping generic-path-affinities { @@ -4684,7 +4986,7 @@ module ietf-te-types { description "LSP encoding type."; reference - "RFC3945"; + "RFC 3945"; } leaf switching-type { type identityref { @@ -4693,7 +4995,7 @@ module ietf-te-types { description "LSP switching type."; reference - "RFC3945"; + "RFC 3945"; } } @@ -4804,18 +5106,20 @@ module ietf-te-packet-types { This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; - revision 2024-01-25 { + revision 2024-02-16 { description - "Added common TE packet identities: + "This revision adds the following new identities: - bandwidth-profile-type; - - path-metric-loss; - - path-metric-delay-variation. + - link-metric-delay-variation; + - link-metric-loss; + - path-metric-delay-variation; + - path-metric-loss. - Added common TE packet groupings: + This revision adds the following new groupings: - te-packet-path-bandwidth; - te-packet-link-bandwidth. - Updated module description."; + This revision provides also few editorial changes."; reference "RFC XXXX: Common YANG Data Types for Traffic Engineering"; } @@ -4875,57 +5179,64 @@ module ietf-te-packet-types { Marker with Efficient Handling of in-Profile Traffic"; } - // CHANGE NOTE: The identity path-metric-loss below has - // been added in this module revision - // RFC Editor: remove the note above and this note - identity path-metric-loss { - base te-types:path-metric-type; - description - "The path loss (as a packet percentage) metric type - encodes a function of the unidirectional loss metrics of all - links traversed by a P2P path. - - The basic unit is 0.000003%, - where (2^24 - 2) or 50.331642% is the maximum value of the - path loss percentage that can be expressed. - - Values that are larger than the maximum value SHOULD be - encoded as the maximum value."; - reference - "RFC8233: Extensions to the Path Computation Element - Communication Protocol (PCEP) to Compute Service-Aware Label - Switched Paths (LSPs); + // CHANGE NOTE: The identity link-metric-delay-variation + // below has been added in this module revision + // RFC Editor: remove the note above and this note + identity link-metric-delay-variation { + base te-types:link-metric-type; + description + "The Unidirectional Delay Variation Metric, + measured in units of microseconds."; + reference + "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + section 4.3 - RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; + RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + section 4.3"; + } - RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - } + // CHANGE NOTE: The identity link-metric-loss below has + // been added in this module revision + // RFC Editor: remove the note above and this note + identity link-metric-loss { + base te-types:link-metric-type; + description + "The Unidirectional Link Loss Metric, + measured in units of 0.000003%."; + reference + "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + section 4.4 - // CHANGE NOTE: The identity path-metric-delay-variation below has - // been added in this module revision - // RFC Editor: remove the note above and this note - identity path-metric-delay-variation { - base te-types:path-metric-type; - description - "The path delay variation encodes the sum of the unidirectional - delay variation metrics of all links traversed by a P2P path. - - The path delay variation metric unit is in microseconds, where - (2^24 - 1) or 16,777,215 microseconds (16.777215 sec) is the - maximum value of the path delay variation that can be - expressed. - - Values that are larger than the maximum value SHOULD be - encoded as the maximum value."; - reference - "RFC8233: Extensions to the Path Computation Element - Communication Protocol (PCEP) to Compute Service-Aware Label - Switched Paths (LSPs); + RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + section 4.4"; + } - RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; + // CHANGE NOTE: The identity path-metric-delay-variation + // below has been added in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-delay-variation { + base te-types:path-metric-type; + description + "The Path Delay Variation Metric, + measured in units of microseconds."; + reference + "RFC8233: Extensions to the Path Computation Element + Communication Protocol (PCEP) to Compute Service-Aware Label + Switched Paths (LSPs), section 3.1.2"; + } - RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - } + // CHANGE NOTE: The identity path-metric-loss below has + // been added in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-loss { + base te-types:path-metric-type; + description + "The Path Loss Metric, measured in units of 0.000003%."; + reference + "RFC8233: Extensions to the Path Computation Element + Communication Protocol (PCEP) to Compute Service-Aware Label + Switched Paths (LSPs), section 3.1.3"; + } /* * Typedefs @@ -5872,123 +6183,6 @@ Names" registry : - - - - A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces - - Cisco Systems Inc - - - Cisco Systems Inc - - - Alef Edge - - - Juniper Networks - - - Individual - - - - This document defines a YANG data model for the provisioning and - management of Traffic Engineering (TE) tunnels, Label Switched Paths - (LSPs), and interfaces. The model covers data that is independent of - any technology or dataplane encapsulation and is divided into two - YANG modules that cover device-specific, and device independent data. - - This model covers data for configuration, operational state, remote - procedural calls, and event notifications. - - - - - - - - - - - - A YANG Data Model for requesting path computation - - Huawei Technologies - - - Nokia - - - Telefonica - - - Google - - - China Unicom - - - - There are scenarios, typically in a hierarchical Software-Defined - Networking (SDN) context, where the topology information provided by - a Traffic Engineering (TE) network provider may be insufficient for - its client to perform multi-domain path computation. In these cases - the client would need to request the TE network provider to compute - some intra-domain paths to be used by the client to choose the - optimal multi-domain paths. - - This document provides a mechanism to request path computation by - augmenting the Remote Procedure Calls (RPCs) defined in RFC YYYY. - - [RFC EDITOR NOTE: Please replace RFC YYYY with the RFC number of - draft-ietf-teas-yang-te once it has been published. - - Moreover, this document describes some use cases where the path - computation request, via YANG-based protocols (e.g., NETCONF or - RESTCONF), can be needed. - - - - - - - - - - - - YANG Data Model for Layer 3 TE Topologies - - Alef Edge - - - Individual - - - Juniper Networks - - - Cisco Systems Inc - - - Ciena - - - Telefonica - - - - This document defines a YANG data model for layer 3 traffic - engineering topologies. - - - - - - - - OSPF Traffic Engineering (TE) Metric Extensions @@ -6946,7 +7140,150 @@ Names" registry :
Changes from RFC 8776 -To be added in a future revision of this draft. +This version adds new common data types, identities, and groupings to the YANG modules. It also updates some of the existing data types, identities, and groupings in the YANG modules and fixes few bugs in . + +The following new identities have been added to the 'ietf-te-types' module: + + + lsp-provisioning-error-reason; + association-type-diversity; + tunnel-admin-state-auto; + lsp-restoration-restore-none; + restoration-scheme-rerouting; + path-metric-optimization-type; + link-path-metric-type; + link-metric-type and its derived identities; + path-computation-error-reason and its derived identities; + protocol-origin-type and its derived identities; + svec-objective-function-type and its derived identities; + svec-metric-type and its derived identities. + + +The following new data types have been added to the 'ietf-te-types' module: + + + path-type; + te-gen-node-id. + + +The following new groupings have been added to the 'ietf-te-types' module: + + + encoding-and-switching-type; + te-generic-node-id. + + +The following new identities have been added to the 'ietf-te-packet-types' module: + + + bandwidth-profile-type; + link-metric-delay-variation; + link-metric-loss; + path-metric-delay-variation; + path-metric-loss. + + +The following new groupings have been added to the 'ietf-te-packet-types' module: + + + te-packet-path-bandwidth; + te-packet-link-bandwidth. + + +The following identities, already defined in , have been updated in the 'ietf-te-types' module: + + + objective-function-type (editorial); + action-exercise (bug fix); + path-metric-type: +new base identities have been added; + path-metric-te (bug fix); + path-metric-igp (bug fix); + path-metric-hop (bug fix); + path-metric-delay-average (bug fix); + path-metric-delay-minimum (bug fix); + path-metric-residual-bandwidth (bug fix); + path-metric-optimize-includes (bug fix); + path-metric-optimize-excludes (bug fix); + te-optimization-criterion (editorial). + + +The following data type, already defined in , has been updated in the 'ietf-te-types' module: + + + te-node-id; +The data type has been changed to be a union. + + +The following groupings, already defined in , have been updated in the 'ietf-te-types' module: + + + explicit-route-hop +The following new leaves have been added to the 'explicit-route-hop' grouping: + node-id-uri; + link-tp-id-uri; + +The following leaves, already defined in , have been updated in the 'explicit-route-hop': + node-id; + link-tp-id. +The mandatory true statements for the node-id and link-tp-id have been replaced by must statements that requires at least the presence of: + node-id or node-id-uri; + link-tp-id or link-tp-id-uri. + + + explicit-route-hop +The following new leaves have been added to the 'explicit-route-hop' grouping: + node-id-uri; + link-tp-id-uri; + +The following leaves, already defined in , have been updated in the 'explicit-route-hop': + node-id; + link-tp-id. +The mandatory true statements for the node-id and link-tp-id have been replaced by must statements that requires at least the presence of: + node-id or node-id-uri; + link-tp-id or link-tp-id-uri. + + + optimization-metric-entry: +The following leaves, already defined in , have been updated in the 'optimization-metric-entry': + metric-type; +The base identity has been updated without impacting the set of derived identities that are allowed. + + tunnel-constraints; +The following new leaf have been added to the 'tunnel-constraints' grouping: + network-id; + + path-constraints-route-objects: +The following container, already defined in , has been updated in the 'path-constraints-route-objects': + explicit-route-objects-always; +The container has been renamed as 'explicit-route-objects'. This change is not affecting any IETF standard YANG models since this grouping has not yet been used by any YANG model defined in existing IETF RFCs. + + generic-path-metric-bounds: +The following leaves, already defined in , have been updated in the 'optimization-metric-entry': + metric-type; +The base identity has been updated to: + increase the set of derived identities that are allowed and; + remove from this set the 'path-metric-optimize-includes' and the 'path-metric-optimize-excludes' identities (bug fixing) + + + generic-path-optimization +The following new leaf have been added to the 'generic-path-optimization' grouping: + tiebreaker; + +The following container, already defined in , has been deprecated: + tiebreakers. + + + +The following identities, already defined in , have been obsoletes in the 'ietf-te-types' module for bug fixing: + + + of-minimize-agg-bandwidth-consumption; + of-minimize-load-most-loaded-link; + of-minimize-cost-path-set; + lsp-protection-reroute-extra; + lsp-protection-reroute. +
TE Types YANG Diffs @@ -6992,61 +7329,134 @@ sed 's/^ > / > /' model-diff-spaces.txt < the license terms contained in, the Simplified BSD License set --- > the license terms contained in, the Revised BSD License set -65,66c75,113 +65,66c75,164 < This version of this YANG module is part of RFC 8776; see the < RFC itself for full legal notices."; --- > This version of this YANG module is part of RFC XXXX > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself > for full legal notices."; -> revision 2024-01-29 { +> revision 2024-02-16 { > description -> "Added: -> - base identity lsp-provisioning-error-reason; -> - identity association-type-diversity; -> - identity tunnel-admin-state-auto; -> - identity lsp-restoration-restore-none; -> - identity restoration-scheme-rerouting; -> - base identity path-computation-error-reason and -> its derived identities; -> - base identity protocol-origin-type and -> its derived identities; -> - base identity svec-objective-function-type and its derived -> identities; -> - base identity svec-metric-type and its derived identities; -> - grouping encoding-and-switching-type. -> -> Updated: -> - description of the base identity objective-function-type; -> - description and reference of identity action-exercise; -> - typedef te-node-id to support also 16 octects TE identifiers. -> -> Obsoleted: -> - identity of-minimize-agg-bandwidth-consumption; -> - identity of-minimize-load-most-loaded-link; -> - identity of-minimize-cost-path-set; -> - identity lsp-protection-reroute-extra; -> - identity lsp-protection-reroute. +> "This revision adds the following new identities: +> - lsp-provisioning-error-reason; +> - association-type-diversity; +> - tunnel-admin-state-auto; +> - lsp-restoration-restore-none; +> - restoration-scheme-rerouting; +> - path-metric-optimization-type; +> - link-path-metric-type; +> - link-metric-type and its derived identities; +> - path-computation-error-reason and its derived identities; +> - protocol-origin-type and its derived identities; +> - svec-objective-function-type and its derived identities; +> - svec-metric-type and its derived identities. +> +> This revision adds the following new data types: +> - path-type; +> - te-gen-node-id. +> +> This revision adds the following new groupings: +> - encoding-and-switching-type; +> - te-generic-node-id. +> +> This revision updates the following identities: +> - objective-function-type; +> - action-exercise; +> - path-metric-type; +> - path-metric-te; +> - path-metric-igp; +> - path-metric-hop; +> - path-metric-delay-average; +> - path-metric-delay-minimum; +> - path-metric-residual-bandwidth; +> - path-metric-optimize-includes; +> - path-metric-optimize-excludes; +> - te-optimization-criterion. > -> Container explicit-route-objects-always renamed as -> explicit-route-objects."; +> This revision updates the following data types: +> - te-node-id. +> +> This revision updates the following groupings: +> - explicit-route-hop: +> - adds the following leaves: +> - node-id-uri; +> - link-tp-id-uri; +> - updates the following leaves: +> - node-id; +> - link-tp-id; +> - record-route-state: +> - adds the following leaves: +> - node-id-uri; +> - link-tp-id-uri; +> - updates the following leaves: +> - node-id; +> - link-tp-id; +> - optimization-metric-entry: +> - updates the following leaves: +> - metric-type; +> - tunnel-constraints; +> - adds the following leaves: +> - network-id; +> - path-constraints-route-objects: +> - updates the following containers: +> - explicit-route-objects-always; +> - generic-path-metric-bounds: +> - updates the following leaves: +> - metric-type; +> - generic-path-optimization +> - adds the following leaves: +> - tiebreaker; +> - deprecate the following containers: +> - tiebreakers. +> +> This revision obsoletes the following identities: +> - of-minimize-agg-bandwidth-consumption; +> - of-minimize-load-most-loaded-link; +> - of-minimize-cost-path-set; +> - lsp-protection-reroute-extra; +> - lsp-protection-reroute. +> +> This revision provides also few editorial changes."; > reference > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; > } > // RFC Editor: replace XXXX with actual RFC number, update date > // information and remove this note -351a399,401 +70c168 +< "Latest revision of TE types."; +--- +> "Initial Version of TE types."; +86a185 +> +92a192 +> +93a194 +> +111a213 +> +155a258 +> +158a262 +> +263a368 +> +264a370 +> +269a376 +> +351a459,461 > // CHANGE NOTE: The typedef te-node-id below has been > // updated in this module revision > // RFC Editor: remove the note above and this note -353c403,406 +353c463,466 < type yang:dotted-quad; --- > type union { > type yang:dotted-quad; > type inet:ipv6-address-no-zone; > } -357,358c410,414 +357,358c470,474 < The identifier is represented as 4 octets in dotted-quad < notation. --- @@ -7055,7 +7465,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > dotted-quad notation or 16 octets in full, mixed, shortened, > or shortened-mixed IPv6 address notation. > -362,363c418,421 +362,363c478,481 < Router ID TLV described in Section 4.3 of RFC 5305, or the < TE Router ID TLV described in Section 3.2.1 of RFC 6119. --- @@ -7063,13 +7473,17 @@ sed 's/^ > / > /' model-diff-spaces.txt > Router ID TLV described in Section 3.2.1 of RFC 6119, or the > IPv6 TE Router ID TLV described in Section 4.1 of RFC 6119. > -368a427 +368a487 +> +370a490 > -370a430 +371a492 > -371a432 +519a641 > -545a607,647 +537a660 +> +545a669,709 > // CHANGE NOTE: The typedef path-type below has been > // added in this module revision > // RFC Editor: remove the note above and this note @@ -7111,7 +7525,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Generic type that identifies a node in a TE topology."; > } > -606a709,716 +606a771,778 > // CHANGE NOTE: The base identity lsp-provisioning-error-reason > // has been added in this module revision > // RFC Editor: remove the note above and this note @@ -7120,7 +7534,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Base identity for LSP provisioning errors."; > } > -982a1093,1110 +982a1155,1172 > // CHANGE NOTE: The identity association-type-diversity below has > // been added in this module revision > // RFC Editor: remove the note above and this note @@ -7130,7 +7544,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Association Type diversity used to associate LSPs whose > paths are to be diverse from each other."; > reference -> "RFC8800: Path Computation Element Communication Protocol +> "RFC 8800: Path Computation Element Communication Protocol > (PCEP) Extension for Label Switched Path (LSP) Diversity > Constraint Signaling"; > } @@ -7139,45 +7553,92 @@ sed 's/^ > / > /' model-diff-spaces.txt > // objective-function-type has been updated > // in this module revision > // RFC Editor: remove the note above and this note -985c1113 +985c1175 < "Base objective function type."; --- -> "Base identity for path objective function type."; -1015a1144,1146 +> "Base identity for path objective function types."; +1015a1206,1208 > // CHANGE NOTE: The identity of-minimize-agg-bandwidth-consumption > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1017a1149 +1017a1211 > status obsolete; -1020c1152 +1020c1214,1218 < consumption."; --- -> consumption."; -1023c1155 +> consumption. +> +> This identity has been obsoleted: the +> 'svec-of-minimize-agg-bandwidth-consumption' identity SHOULD +> be used instead."; +1023c1221 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; -1025a1158,1160 +1025a1224,1226 > // CHANGE NOTE: The identity of-minimize-load-most-loaded-link > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1027a1163 +1027a1229 > status obsolete; -1030c1166 +1030c1232,1236 < is carrying the highest load."; --- -> is carrying the highest load."; -1033c1169 +> is carrying the highest load. +> +> This identity has been obsoleted: the +> 'svec-of-minimize-load-most-loaded-link' identity SHOULD +> be used instead."; +1033c1239 < Computation Element Communication Protocol (PCEP)"; --- > Computation Element Communication Protocol (PCEP)"; -1035a1172,1174 +1035a1242,1244 > // CHANGE NOTE: The identity of-minimize-cost-path-set > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1037a1177 +1037a1247 > status obsolete; -1216a1357,1368 +1039c1249,1253 +< "Objective function for minimizing the cost on a path set."; +--- +> "Objective function for minimizing the cost on a path set. +> +> This identity has been obsoleted: the +> 'svec-of-minimize-cost-path-set' identity SHOULD +> be used instead."; +1049a1264,1266 +> // CHANGE NOTE: The reference of the identity path-locally-computed +> // below has been updated in this module revision +> // RFC Editor: remove the note above and this note +1056,1057c1273,1274 +< "RFC 3272: Overview and Principles of Internet Traffic +< Engineering, Section 5.4"; +--- +> "RFC 9522: Overview and Principles of Internet Traffic +> Engineering, Section 4.4"; +1059a1277,1280 +> // CHANGE NOTE: The reference of the identity +> // path-externally-queried below has been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +1071c1292 +< "RFC 3272: Overview and Principles of Internet Traffic +--- +> "RFC 9522: Overview and Principles of Internet Traffic +1072a1294 +> +1076a1299,1302 +> // CHANGE NOTE: The reference of the identity +> // path-explicitly-defined below has been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +1085c1311,1312 +< RFC 3272: Overview and Principles of Internet Traffic +--- +> +> RFC 9522: Overview and Principles of Internet Traffic +1216a1444,1455 > // CHANGE NOTE: The identity tunnel-admin-state-auto below > // has been added in this module revision > // RFC Editor: remove the note above and this note @@ -7190,7 +7651,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > when it is not used by the client layer."; > } > -1321a1474,1482 +1321a1561,1569 > // CHANGE NOTE: The identity lsp-restoration-restore-none > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -7200,7 +7661,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > "No LSP affected by a failure is restored."; > } > -1339a1501,1515 +1339a1588,1602 > // CHANGE NOTE: The identity restoration-scheme-rerouting > // below has been added in this module revision > // RFC Editor: remove the note above and this note @@ -7216,13 +7677,13 @@ sed 's/^ > / > /' model-diff-spaces.txt > for Generalized Multi-Protocol Label Switching (GMPLS)"; > } > -1383a1560,1562 +1383a1647,1649 > // CHANGE NOTE: The identity lsp-protection-reroute-extra > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1385a1565 +1385a1652 > status obsolete; -1387c1567,1571 +1387c1654,1658 < "'(Full) Rerouting' LSP protection type."; --- > "'(Full) Rerouting' LSP protection type. @@ -7230,13 +7691,13 @@ sed 's/^ > / > /' model-diff-spaces.txt > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; -1392a1577,1579 +1392a1664,1666 > // CHANGE NOTE: The identity lsp-protection-reroute > // below has been obsoleted in this module revision > // RFC Editor: remove the note above and this note -1394a1582 +1394a1669 > status obsolete; -1396c1584,1588 +1396c1671,1675 < "'Rerouting without Extra-Traffic' LSP protection type."; --- > "'Rerouting without Extra-Traffic' LSP protection type. @@ -7244,46 +7705,327 @@ sed 's/^ > / > /' model-diff-spaces.txt > This identity has been obsoleted: the > 'restoration-scheme-rerouting' identity SHOULD be used > instead."; -1628a1821,1824 +1628a1908,1911 > // CHANGE NOTE: The description and reference of the > // identity action-exercise have been updated in this module > // revision > // RFC Editor: remove the note above and this note -1632,1633c1828,1830 +1632,1633c1915,1917 < "An action that starts testing whether or not APS communication < is operating correctly. It is of lower priority than any --- > "An action that starts testing whether or not Automatic > Protection Switching (APS) communication is operating > correctly. It is of lower priority than any -1636,1637c1833,1834 +1636,1637c1920,1921 < "RFC 4427: Recovery (Protection and Restoration) Terminology < for Generalized Multi-Protocol Label Switching (GMPLS)"; --- > "ITU-T G.808.1 v4.0 (05/2014): Generic protection switching - > Linear trail and subnetwork protection"; -1916a2114,2116 -> // CHANGE NOTE: The description of the identity path-metric-type -> // has been updated in this module revision +1917c2201,2204 +< identity path-metric-type { +--- +> // CHANGE NOTE: The path-metric-optimization-type base identity +> // has been added in this module revision > // RFC Editor: remove the note above and this note -1919c2119,2122 +> identity path-metric-optimization-type { +1919c2206,2207 < "Base identity for the path metric type."; --- -> "Base identity for the path metric type. -> -> Derived identities SHOULD describe the unit and maximum value -> of the path metric types they define."; -1939a2143,2145 -> // CHANGE NOTE: The reference for the identity path-metric-hop +> "Base identity used to define the path metric optimization +> types."; +1922,1923c2210,2213 +< identity path-metric-te { +< base path-metric-type; +--- +> // CHANGE NOTE: The link-path-metric-type base identity > // has been added in this module revision > // RFC Editor: remove the note above and this note -1943a2150,2152 -> reference -> "RFC5440: Path Computation Element (PCE) Communication -> Protocol (PCEP)"; -1945a2155 +> identity link-path-metric-type { +1925,1928c2215,2221 +< "TE path metric."; +< reference +< "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a +< second MPLS Traffic Engineering (TE) Metric"; +--- +> "Base identity used to define the link and the path metric +> types. +> +> The unit of the path metric value is interpreted in the +> context of the path metric type and the derived identities +> SHOULD describe the unit of the path metric types they +> define."; +1931,1938c2224,2232 +< identity path-metric-igp { +< base path-metric-type; +< description +< "IGP path metric."; +< reference +< "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a +< second MPLS Traffic Engineering (TE) Metric"; +< } +--- +> // CHANGE NOTE: The link-metric-type base identity +> // and its derived identities +> // have been added in this module revision +> // RFC Editor: remove the note above and this note +> identity link-metric-type { +> base link-path-metric-type; +> description +> "Base identity for the link metric types."; +> } +1940,1944c2234,2240 +< identity path-metric-hop { +< base path-metric-type; +< description +< "Hop path metric."; +< } +--- +> identity link-metric-te { +> base link-metric-type; +> description +> "Traffic Engineering (TE) Link Metric."; +> reference +> "RFC 3630: Traffic Engineering (TE) Extensions to OSPF +> Version 2, section 2.5.5 +1946,1952c2242,2244 +< identity path-metric-delay-average { +< base path-metric-type; +< description +< "Average unidirectional link delay."; +< reference +< "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; +< } +--- +> RFC 5305: IS-IS Extensions for Traffic Engineering, +> section 3.7"; +> } +1954,1960c2246,2253 +< identity path-metric-delay-minimum { +< base path-metric-type; +< description +< "Minimum unidirectional link delay."; +< reference +< "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; +< } +--- +> identity link-metric-igp { +> base link-metric-type; +> description +> "Interior Gateway Protocol (IGP) Link Metric."; +> reference +> "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric +> as a second MPLS Traffic Engineering (TE) Metric"; +> } +1962,1972c2255,2266 +< identity path-metric-residual-bandwidth { +< base path-metric-type; +< description +< "Unidirectional Residual Bandwidth, which is defined to be +< Maximum Bandwidth (RFC 3630) minus the bandwidth currently +< allocated to LSPs."; +< reference +< "RFC 3630: Traffic Engineering (TE) Extensions to OSPF +< Version 2 +< RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; +< } +--- +> identity link-metric-delay-average { +> base link-metric-type; +> description +> "Unidirectional Link Delay, measured in units of +> microseconds."; +> reference +> "RFC 7471: OSPF Traffic Engineering (TE) Metric +> Extensions, section 4.1 +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric +> Extensions, section 4.1"; +> } +1974,1979c2268,2279 +< identity path-metric-optimize-includes { +< base path-metric-type; +< description +< "A metric that optimizes the number of included resources +< specified in a set."; +< } +--- +> identity link-metric-delay-minimum { +> base link-metric-type; +> description +> "Minimum unidirectional Link Delay, measured in units of +> microseconds."; +> reference +> "RFC 7471: OSPF Traffic Engineering (TE) Metric +> Extensions, section 4.2 +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric +> Extensions, section 4.2"; +> } +1981,1986c2281,2425 +< identity path-metric-optimize-excludes { +< base path-metric-type; +< description +< "A metric that optimizes to a maximum the number of excluded +< resources specified in a set."; +< } +--- +> identity link-metric-delay-maximum { +> base link-metric-type; +> description +> "Maximum unidirectional Link Delay, measured in units of +> microseconds."; +> reference +> "RFC 7471: OSPF Traffic Engineering (TE) Metric +> Extensions, section 4.2 +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric +> Extensions, section 4.2"; +> } +> +> identity link-metric-residual-bandwidth { +> base link-metric-type; +> description +> "Unidirectional Residual Bandwidth, measured in units of +> bytes per second. +> +> It is defined to be Maximum Bandwidth minus the bandwidth +> currently allocated to LSPs."; +> reference +> "RFC 7471: OSPF Traffic Engineering (TE) Metric +> Extensions, section 4.5 +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric +> Extensions, section 4.5"; +> } +> +> // CHANGE NOTE: The base and the description of the +> // path-metric-type identity +> // has been updated in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-type { +> base link-path-metric-type; +> base path-metric-optimization-type; +> description +> "Base identity for the path metric types."; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-te identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-te { +> base path-metric-type; +> description +> "Traffic Engineering (TE) Path Metric."; +> reference +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP), section 7.8"; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-igp identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-igp { +> base path-metric-type; +> description +> "Interior Gateway Protocol (IGP) Path Metric."; +> reference +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP), section 7.8"; +> } > -2110a2321,2724 +> // CHANGE NOTE: The description and the reference of the +> // path-metric-hop identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-hop { +> base path-metric-type; +> description +> "Hop Count Path Metric."; +> reference +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP), section 7.8"; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-delay-average identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-delay-average { +> base path-metric-type; +> description +> "The Path Delay Metric, measured in units of +> microseconds."; +> reference +> "RFC8233: Extensions to the Path Computation Element +> Communication Protocol (PCEP) to Compute Service-Aware +> Label Switched Paths (LSPs), section 3.1.1"; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-delay-minimum identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-delay-minimum { +> base path-metric-type; +> description +> "The Path Min Delay Metric, measured in units of +> microseconds."; +> reference +> "I-D.ietf-pce-sid-algo: Carrying SR-Algorithm information +> in PCE-based Networks, section 3.5.1"; +> } +> +> // CHANGE NOTE: The description and the reference of the +> // path-metric-residual-bandwidth identity have been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-residual-bandwidth { +> base path-metric-type; +> description +> "The Path Residual Bandwidth, defined as the minimum Link +> Residual Bandwidth all the links along the path. +> +> The Path Residual Bandwidth can be seen as the path +> metric associated with the Maximum residual Bandwidth Path +> (MBP) objective function."; +> reference +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; +> } +> +> // CHANGE NOTE: The base of the path-metric-optimize-includes +> // identity has been updated in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-optimize-includes { +> base path-metric-optimization-type; +> description +> "A metric that optimizes the number of included resources +> specified in a set."; +> } +> +> // CHANGE NOTE: The base of the path-metric-optimize-excludes +> // identity has been updated in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-optimize-excludes { +> base path-metric-optimization-type; +> description +> "A metric that optimizes to a maximum the number of excluded +> resources specified in a set."; +> } +2049a2489,2492 +> // CHANGE NOTE: The reference of the identity +> // te-optimization-criterion below has been updated +> // in this module revision +> // RFC Editor: remove the note above and this note +2054c2497 +< "RFC 3272: Overview and Principles of Internet Traffic +--- +> "RFC 9522: Overview and Principles of Internet Traffic +2110a2554,2994 > // CHANGE NOTE: The base identity path-computation-error-reason > // and its derived identities below have been > // added in this module revision @@ -7299,8 +8041,8 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Path computation has failed because of an unspecified > reason."; > reference -> "Section 7.5 of RFC5440: Path Computation Element (PCE) -> Communication Protocol (PCEP)"; +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP), section 7.5"; > } > > identity path-computation-error-no-topology { @@ -7320,7 +8062,13 @@ sed 's/^ > / > /' model-diff-spaces.txt > a Backward-Recursive Path Computation (BRPC) downstream > PCE or a child PCE."; > reference -> "RFC5441, RFC8685"; +> "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) +> Procedure to Compute Shortest Constrained Inter-Domain +> Traffic Engineering Label Switched Paths +> +> RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture"; > } > > identity path-computation-error-pce-unavailable { @@ -7331,10 +8079,11 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 31 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5440: Path Computation Element (PCE) Communication -> Protocol (PCEP); +> "RFC 5440: Path Computation Element (PCE) Communication +> Protocol (PCEP) > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-inclusion-hop { @@ -7353,9 +8102,12 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 19 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8685; +> "RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-resource { @@ -7367,9 +8119,12 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 20 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8685; +> "RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-child-pce-unresponsive { @@ -7381,9 +8136,12 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 21 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8685; +> "RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-domain-unknown { @@ -7395,9 +8153,12 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 22 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8685; +> "RFC 8685: Path Computation Element Communication Protocol +> (PCEP) Extensions for the Hierarchical Path Computation +> Element (H-PCE) Architecture > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-p2mp { @@ -7409,9 +8170,12 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 24 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC8306; +> "RFC 8306: Extensions to the Path Computation Element +> Communication Protocol (PCEP) for Point-to-Multipoint +> Traffic Engineering Label Switched Paths > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-migration { @@ -7423,9 +8187,12 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 26 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5557; +> "RFC 5557: Path Computation Element Communication Protocol +> (PCEP) Requirements and Protocol Extensions in Support of +> Global Concurrent Optimization > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-gco-solution { @@ -7437,9 +8204,12 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 25 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5557; +> "RFC 5557: Path Computation Element Communication Protocol +> (PCEP) Requirements and Protocol Extensions in Support of +> Global Concurrent Optimization > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-pks-expansion { @@ -7451,9 +8221,12 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 27 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5520; +> "RFC 5520: Preserving Topology Confidentiality in +> Inter-Domain Path Computation Using a Path-Key-Based +> Mechanism > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-brpc-chain-unavailable { @@ -7465,9 +8238,12 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 28 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5441; +> "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) +> Procedure to Compute Shortest Constrained Inter-Domain +> Traffic Engineering Label Switched Paths > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-source-unknown { @@ -7479,10 +8255,11 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 29 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5440: Path Computation Element (PCE) Communication +> "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-destination-unknown { @@ -7494,10 +8271,11 @@ sed 's/^ > / > /' model-diff-spaces.txt > It corresponds to bit 30 of the Flags field of the > NO-PATH-VECTOR TLV."; > reference -> "RFC5440: Path Computation Element (PCE) Communication +> "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > identity path-computation-error-no-server { @@ -7506,10 +8284,11 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Path computation has failed because path computation > server is unavailable."; > reference -> "RFC5440: Path Computation Element (PCE) Communication +> "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP); > -> https://www.iana.org/assignments/pcep/pcep.xhtml"; +> https://www.iana.org/assignments/pcep +> /pcep.xhtml#no-path-vector-tlv"; > } > > // CHANGE NOTE: The base identity protocol-origin-type and @@ -7534,7 +8313,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Protocol origin is Path Computation Engine Protocol > (PCEP)."; > reference -> "RFC5440: Path Computation Element (PCE) Communication +> "RFC 5440: Path Computation Element (PCE) Communication > Protocol (PCEP)"; > } > @@ -7542,7 +8321,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > base protocol-origin-type; > description > "Protocol origin is Border Gateway Protocol (BGP)."; -> reference "RFC9012"; +> reference "RFC 9012"; > } > > // CHANGE NOTE: The base identity svec-objective-function-type @@ -7553,8 +8332,8 @@ sed 's/^ > / > /' model-diff-spaces.txt > description > "Base identity for SVEC objective function type."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-agg-bandwidth-consumption { @@ -7563,8 +8342,8 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Objective function for minimizing aggregate bandwidth > consumption (MBC)."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-load-most-loaded-link { @@ -7573,8 +8352,8 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Objective function for minimizing the load on the link that > is carrying the highest load (MLL)."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-cost-path-set { @@ -7583,8 +8362,8 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Objective function for minimizing the cost on a path set > (MCC)."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-of-minimize-common-transit-domain { @@ -7593,9 +8372,9 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Objective function for minimizing the number of common > transit domains (MCTD)."; > reference -> "RFC8685: Path Computation Element Communication Protocol +> "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation -> Element (H-PCE) Architecture."; +> Element (H-PCE) Architecture"; > } > > identity svec-of-minimize-shared-link { @@ -7604,7 +8383,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Objective function for minimizing the number of shared > links (MSL)."; > reference -> "RFC8685: Path Computation Element Communication Protocol +> "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -7615,7 +8394,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Objective function for minimizing the number of shared > Shared Risk Link Groups (SRLG) (MSS)."; > reference -> "RFC8685: Path Computation Element Communication Protocol +> "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -7626,7 +8405,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > "Objective function for minimizing the number of shared > nodes (MSN)."; > reference -> "RFC8685: Path Computation Element Communication Protocol +> "RFC 8685: Path Computation Element Communication Protocol > (PCEP) Extensions for the Hierarchical Path Computation > Element (H-PCE) Architecture."; > } @@ -7639,35 +8418,35 @@ sed 's/^ > / > /' model-diff-spaces.txt > description > "Base identity for SVEC metric type."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > -> identity svec-metric-cumul-te { +> identity svec-metric-cumulative-te { > base svec-metric-type; > description > "Cumulative TE cost."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > -> identity svec-metric-cumul-igp { +> identity svec-metric-cumulative-igp { > base svec-metric-type; > description > "Cumulative IGP cost."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > -> identity svec-metric-cumul-hop { +> identity svec-metric-cumulative-hop { > base svec-metric-type; > description > "Cumulative Hop path metric."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-aggregate-bandwidth-consumption { @@ -7675,8 +8454,8 @@ sed 's/^ > / > /' model-diff-spaces.txt > description > "Aggregate bandwidth consumption."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > > identity svec-metric-load-of-the-most-loaded-link { @@ -7684,15 +8463,29 @@ sed 's/^ > / > /' model-diff-spaces.txt > description > "Load of the most loaded link."; > reference -> "RFC5541: Encoding of Objective Functions in the Path -> Computation Element Communication Protocol (PCEP)."; +> "RFC 5541: Encoding of Objective Functions in the Path +> Computation Element Communication Protocol (PCEP)"; > } > -2506a3121,3123 +2221,2225c3105,3111 +< "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions +< RFC 7823: Performance-Based Path Selection for Explicitly +< Routed Label Switched Paths (LSPs) Using TE Metric +< Extensions +< RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; +--- +> "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensionsù +> +> RFC 7823: Performance-Based Path Selection for Explicitly +> Routed Label Switched Paths (LSPs) Using TE Metric +> Extensions +> +> RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; +2506a3393,3395 > // CHANGE NOTE: The explicit-route-hop grouping below has been > // updated in this module revision > // RFC Editor: remove the note above and this note -2514a3132,3140 +2514a3404,3412 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; @@ -7702,9 +8495,9 @@ sed 's/^ > / > /' model-diff-spaces.txt > description > "The identifier of a node in the topology."; > } -2517d3142 +2517d3414 < mandatory true; -2566a3192,3202 +2566a3464,3474 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description @@ -7716,30 +8509,34 @@ sed 's/^ > / > /' model-diff-spaces.txt > description > "Link Termination Point (LTP) identifier."; > } -2569d3204 +2569d3476 < mandatory true; -2574a3210,3214 +2574a3482,3486 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } -2577d3216 +2577d3488 < mandatory true; -2646a3286,3289 +2631a3543,3545 +> // CHANGE NOTE: The explicit-route-hop grouping below has been +> // updated in this module revision +> // RFC Editor: remove the note above and this note +2646a3561,3564 > must "node-id-uri or node-id" { > description > "At least one node identifier MUST be present."; > } -2648a3292,3296 +2648a3567,3571 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } -2651d3298 +2651d3573 < mandatory true; -2696a3344,3354 +2696a3619,3629 > must "(link-tp-id-uri or link-tp-id) and " + > "(node-id-uri or node-id)" { > description @@ -7751,44 +8548,103 @@ sed 's/^ > / > /' model-diff-spaces.txt > description > "Link Termination Point (LTP) identifier."; > } -2699d3356 +2699d3631 < mandatory true; -2704a3362,3366 +2704a3637,3641 > leaf node-id-uri { > type nw:node-id; > description > "The identifier of a node in the topology."; > } -2968a3631,3635 +2881a3819,3821 +> // CHANGE NOTE: The grouping optimization-metric-entry below has +> // been updated in this module revision +> // RFC Editor: remove the note above and this note +2887c3827 +< base path-metric-type; +--- +> base path-metric-optimization-type; +2964a3905,3907 +> // CHANGE NOTE: The grouping tunnel-constraints below has +> // been updated in this module revision +> // RFC Editor: remove the note above and this note +2968a3912,3916 > leaf network-id { > type nw:network-id; > description > "The network topology identifier."; > } -2977c3644,3647 +2972a3921,3923 +> // CHANGE NOTE: The grouping path-constraints-route-objects below +> // has been updated in this module revision +> // RFC Editor: remove the note above and this note +2977c3928 < container explicit-route-objects-always { --- -> // CHANGE NOTE: The explicit-route-objects container below has -> // been updated in this module revision -> // RFC Editor: remove the note above and this note > container explicit-route-objects { -2979c3649 +2979c3930 < "Container for the 'exclude route' object list."; --- > "Container for the explicit route object lists."; -3124,3126c3794,3800 +3101a4053,4055 +> // CHANGE NOTE: The grouping generic-path-metric-bounds below +> // has been updated in this module revision +> // RFC Editor: remove the note above and this note +3107c4061 +< "TE path metric bounds container."; +--- +> "Top-level container for the list of path metric bounds."; +3111c4065,4073 +< "List of TE path metric bounds."; +--- +> "List of path metric bounds, which can apply to link and +> path metrics. +> +> TE paths which have at least one path metric which +> exceeds the specified bounds MUST NOT be selected. +> +> TE paths that traverse TE links which have at least one +> link metric which exceeds the specified bounds MUST NOT +> be selected."; +3114c4076 +< base path-metric-type; +--- +> base link-path-metric-type; +3124,3126c4086,4092 < "Upper bound on the end-to-end TE path metric. A zero < indicates an unbounded upper limit for the specific < 'metric-type'."; --- -> "Upper bound on the end-to-end TE path metric. +> "Upper bound on the specified 'metric-type'. > > A zero indicates an unbounded upper limit for the -> specific 'metric-type'. +> specificied 'metric-type'. > > The unit of is interpreted in the context of the -> path-metric-type."; -3379c4053,4112 +> 'metric-type' identity."; +3131a4098,4100 +> // CHANGE NOTE: The grouping generic-path-metric-bounds below +> // has been updated in this module revision +> // RFC Editor: remove the note above and this note +3154c4123,4127 +< "Container for the list of tiebreakers."; +--- +> "Container for the list of tiebreakers. +> +> This container has been obsoleted by the tiebreaker +> leaf."; +> status deprecated; +3189a4163,4171 +> leaf tiebreaker { +> type identityref { +> base path-tiebreaker-type; +> } +> default "te-types:path-tiebreaker-random"; +> description +> "The tiebreaker criteria to apply on an equally favored set +> of paths, in order to pick the best."; +> } +3379c4361,4420 < } \ No newline at end of file --- @@ -7807,7 +8663,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > description > "LSP encoding type."; > reference -> "RFC3945"; +> "RFC 3945"; > } > leaf switching-type { > type identityref { @@ -7816,7 +8672,7 @@ sed 's/^ > / > /' model-diff-spaces.txt > description > "LSP switching type."; > reference -> "RFC3945"; +> "RFC 3945"; > } > } > @@ -7911,31 +8767,33 @@ sed 's/^ > / > /' model-diff-spaces.txt < the license terms contained in, the Simplified BSD License set --- > the license terms contained in, the Revised BSD License set -51,52c61,80 +51,52c61,82 < This version of this YANG module is part of RFC 8776; see the < RFC itself for full legal notices."; --- > This version of this YANG module is part of RFC XXXX > (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself > for full legal notices."; -> revision 2024-01-25 { +> revision 2024-02-16 { > description -> "Added common TE packet identities: +> "This revision adds the following new identities: > - bandwidth-profile-type; -> - path-metric-loss; -> - path-metric-delay-variation. +> - link-metric-delay-variation; +> - link-metric-loss; +> - path-metric-delay-variation; +> - path-metric-loss. > -> Added common TE packet groupings: +> This revision adds the following new groupings: > - te-packet-path-bandwidth; > - te-packet-link-bandwidth. > -> Updated module description."; +> This revision provides also few editorial changes."; > reference > "RFC XXXX: Common YANG Data Types for Traffic Engineering"; > } > // RFC Editor: replace XXXX with actual RFC number, update date > // information and remove this note -61c89,187 +61c91,196 < /** --- > /* @@ -7984,65 +8842,72 @@ sed 's/^ > / > /' model-diff-spaces.txt > Marker with Efficient Handling of in-Profile Traffic"; > } > -> // CHANGE NOTE: The identity path-metric-loss below has -> // been added in this module revision -> // RFC Editor: remove the note above and this note -> identity path-metric-loss { -> base te-types:path-metric-type; -> description -> "The path loss (as a packet percentage) metric type -> encodes a function of the unidirectional loss metrics of all -> links traversed by a P2P path. -> -> The basic unit is 0.000003%, -> where (2^24 - 2) or 50.331642% is the maximum value of the -> path loss percentage that can be expressed. -> -> Values that are larger than the maximum value SHOULD be -> encoded as the maximum value."; -> reference -> "RFC8233: Extensions to the Path Computation Element -> Communication Protocol (PCEP) to Compute Service-Aware Label -> Switched Paths (LSPs); +> // CHANGE NOTE: The identity link-metric-delay-variation +> // below has been added in this module revision +> // RFC Editor: remove the note above and this note +> identity link-metric-delay-variation { +> base te-types:link-metric-type; +> description +> "The Unidirectional Delay Variation Metric, +> measured in units of microseconds."; +> reference +> "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, +> section 4.3 > -> RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; +> RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, +> section 4.3"; +> } > -> RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; -> } +> // CHANGE NOTE: The identity link-metric-loss below has +> // been added in this module revision +> // RFC Editor: remove the note above and this note +> identity link-metric-loss { +> base te-types:link-metric-type; +> description +> "The Unidirectional Link Loss Metric, +> measured in units of 0.000003%."; +> reference +> "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, +> section 4.4 > -> // CHANGE NOTE: The identity path-metric-delay-variation below has -> // been added in this module revision -> // RFC Editor: remove the note above and this note -> identity path-metric-delay-variation { -> base te-types:path-metric-type; -> description -> "The path delay variation encodes the sum of the unidirectional -> delay variation metrics of all links traversed by a P2P path. -> -> The path delay variation metric unit is in microseconds, where -> (2^24 - 1) or 16,777,215 microseconds (16.777215 sec) is the -> maximum value of the path delay variation that can be -> expressed. -> -> Values that are larger than the maximum value SHOULD be -> encoded as the maximum value."; -> reference -> "RFC8233: Extensions to the Path Computation Element -> Communication Protocol (PCEP) to Compute Service-Aware Label -> Switched Paths (LSPs); +> RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, +> section 4.4"; +> } > -> RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; +> // CHANGE NOTE: The identity path-metric-delay-variation +> // below has been added in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-delay-variation { +> base te-types:path-metric-type; +> description +> "The Path Delay Variation Metric, +> measured in units of microseconds."; +> reference +> "RFC8233: Extensions to the Path Computation Element +> Communication Protocol (PCEP) to Compute Service-Aware Label +> Switched Paths (LSPs), section 3.1.2"; +> } > -> RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; -> } +> // CHANGE NOTE: The identity path-metric-loss below has +> // been added in this module revision +> // RFC Editor: remove the note above and this note +> identity path-metric-loss { +> base te-types:path-metric-type; +> description +> "The Path Loss Metric, measured in units of 0.000003%."; +> reference +> "RFC8233: Extensions to the Path Computation Element +> Communication Protocol (PCEP) to Compute Service-Aware Label +> Switched Paths (LSPs), section 3.1.3"; +> } > > /* -180a307,310 +180a316,319 > /* > * Groupings > */ > -472a603,672 +472a612,681 > } > } > @@ -8178,835 +9043,934 @@ about the process to follow to provide tiny updates to a YANG module already pub diff --git a/ietf-te-packet-types.yang b/ietf-te-packet-types.yang index e1d1f59..8e9445b 100644 --- a/ietf-te-packet-types.yang +++ b/ietf-te-packet-types.yang @@ -61,18 +61,20 @@ module ietf-te-packet-types { This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; - revision 2024-01-25 { + revision 2024-02-16 { description - "Added common TE packet identities: + "This revision adds the following new identities: - bandwidth-profile-type; - - path-metric-loss; - - path-metric-delay-variation. + - link-metric-delay-variation; + - link-metric-loss; + - path-metric-delay-variation; + - path-metric-loss. - Added common TE packet groupings: + This revision adds the following new groupings: - te-packet-path-bandwidth; - te-packet-link-bandwidth. - Updated module description."; + This revision provides also few editorial changes."; reference "RFC XXXX: Common YANG Data Types for Traffic Engineering"; } @@ -132,57 +134,64 @@ module ietf-te-packet-types { Marker with Efficient Handling of in-Profile Traffic"; } - // CHANGE NOTE: The identity path-metric-loss below has - // been added in this module revision - // RFC Editor: remove the note above and this note - identity path-metric-loss { - base te-types:path-metric-type; - description - "The path loss (as a packet percentage) metric type - encodes a function of the unidirectional loss metrics of all - links traversed by a P2P path. - - The basic unit is 0.000003%, - where (2^24 - 2) or 50.331642% is the maximum value of the - path loss percentage that can be expressed. - - Values that are larger than the maximum value SHOULD be - encoded as the maximum value."; - reference - "RFC8233: Extensions to the Path Computation Element - Communication Protocol (PCEP) to Compute Service-Aware Label - Switched Paths (LSPs); + // CHANGE NOTE: The identity link-metric-delay-variation + // below has been added in this module revision + // RFC Editor: remove the note above and this note + identity link-metric-delay-variation { + base te-types:link-metric-type; + description + "The Unidirectional Delay Variation Metric, + measured in units of microseconds."; + reference + "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + section 4.3 - RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; + RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + section 4.3"; + } - RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - } + // CHANGE NOTE: The identity link-metric-loss below has + // been added in this module revision + // RFC Editor: remove the note above and this note + identity link-metric-loss { + base te-types:link-metric-type; + description + "The Unidirectional Link Loss Metric, + measured in units of 0.000003%."; + reference + "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions, + section 4.4 - // CHANGE NOTE: The identity path-metric-delay-variation below has - // been added in this module revision - // RFC Editor: remove the note above and this note - identity path-metric-delay-variation { - base te-types:path-metric-type; - description - "The path delay variation encodes the sum of the unidirectional - delay variation metrics of all links traversed by a P2P path. - - The path delay variation metric unit is in microseconds, where - (2^24 - 1) or 16,777,215 microseconds (16.777215 sec) is the - maximum value of the path delay variation that can be - expressed. - - Values that are larger than the maximum value SHOULD be - encoded as the maximum value."; - reference - "RFC8233: Extensions to the Path Computation Element - Communication Protocol (PCEP) to Compute Service-Aware Label - Switched Paths (LSPs); + RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions, + section 4.4"; + } - RFC7471: OSPF Traffic Engineering (TE) Metric Extensions; + // CHANGE NOTE: The identity path-metric-delay-variation + // below has been added in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-delay-variation { + base te-types:path-metric-type; + description + "The Path Delay Variation Metric, + measured in units of microseconds."; + reference + "RFC8233: Extensions to the Path Computation Element + Communication Protocol (PCEP) to Compute Service-Aware Label + Switched Paths (LSPs), section 3.1.2"; + } - RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions."; - } + // CHANGE NOTE: The identity path-metric-loss below has + // been added in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-loss { + base te-types:path-metric-type; + description + "The Path Loss Metric, measured in units of 0.000003%."; + reference + "RFC8233: Extensions to the Path Computation Element + Communication Protocol (PCEP) to Compute Service-Aware Label + Switched Paths (LSPs), section 3.1.3"; + } /* * Typedefs diff --git a/ietf-te-types.yang b/ietf-te-types.yang index cdd8555..6418267 100644 --- a/ietf-te-types.yang +++ b/ietf-te-types.yang @@ -75,37 +75,88 @@ module ietf-te-types { This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; - revision 2024-01-29 { - description - "Added: - - base identity lsp-provisioning-error-reason; - - identity association-type-diversity; - - identity tunnel-admin-state-auto; - - identity lsp-restoration-restore-none; - - identity restoration-scheme-rerouting; - - base identity path-computation-error-reason and - its derived identities; - - base identity protocol-origin-type and - its derived identities; - - base identity svec-objective-function-type and its derived - identities; - - base identity svec-metric-type and its derived identities; - - grouping encoding-and-switching-type. - - Updated: - - description of the base identity objective-function-type; - - description and reference of identity action-exercise; - - typedef te-node-id to support also 16 octects TE identifiers. - - Obsoleted: - - identity of-minimize-agg-bandwidth-consumption; - - identity of-minimize-load-most-loaded-link; - - identity of-minimize-cost-path-set; - - identity lsp-protection-reroute-extra; - - identity lsp-protection-reroute. - - Container explicit-route-objects-always renamed as - explicit-route-objects."; + revision 2024-02-16 { + description + "This revision adds the following new identities: + - lsp-provisioning-error-reason; + - association-type-diversity; + - tunnel-admin-state-auto; + - lsp-restoration-restore-none; + - restoration-scheme-rerouting; + - path-metric-optimization-type; + - link-path-metric-type; + - link-metric-type and its derived identities; + - path-computation-error-reason and its derived identities; + - protocol-origin-type and its derived identities; + - svec-objective-function-type and its derived identities; + - svec-metric-type and its derived identities. + + This revision adds the following new data types: + - path-type; + - te-gen-node-id. + + This revision adds the following new groupings: + - encoding-and-switching-type; + - te-generic-node-id. + + This revision updates the following identities: + - objective-function-type; + - action-exercise; + - path-metric-type; + - path-metric-te; + - path-metric-igp; + - path-metric-hop; + - path-metric-delay-average; + - path-metric-delay-minimum; + - path-metric-residual-bandwidth; + - path-metric-optimize-includes; + - path-metric-optimize-excludes; + - te-optimization-criterion. + + This revision updates the following data types: + - te-node-id. + + This revision updates the following groupings: + - explicit-route-hop: + - adds the following leaves: + - node-id-uri; + - link-tp-id-uri; + - updates the following leaves: + - node-id; + - link-tp-id; + - record-route-state: + - adds the following leaves: + - node-id-uri; + - link-tp-id-uri; + - updates the following leaves: + - node-id; + - link-tp-id; + - optimization-metric-entry: + - updates the following leaves: + - metric-type; + - tunnel-constraints; + - adds the following leaves: + - network-id; + - path-constraints-route-objects: + - updates the following containers: + - explicit-route-objects-always; + - generic-path-metric-bounds: + - updates the following leaves: + - metric-type; + - generic-path-optimization + - adds the following leaves: + - tiebreaker; + - deprecate the following containers: + - tiebreakers. + + This revision obsoletes the following identities: + - of-minimize-agg-bandwidth-consumption; + - of-minimize-load-most-loaded-link; + - of-minimize-cost-path-set; + - lsp-protection-reroute-extra; + - lsp-protection-reroute. + + This revision provides also few editorial changes."; reference "RFC XXXX: Common YANG Data Types for Traffic Engineering"; } @@ -114,7 +165,7 @@ module ietf-te-types { revision 2020-06-10 { description - "Latest revision of TE types."; + "Initial Version of TE types."; reference "RFC 8776: Common YANG Data Types for Traffic Engineering"; } @@ -131,13 +182,16 @@ module ietf-te-types { description "Administrative group / resource class / color representation in 'hex-string' type. + The most significant byte in the hex-string is the farthest to the left in the byte sequence. Leading zero bytes in the configured value may be omitted for brevity."; reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2 + RFC 5305: IS-IS Extensions for Traffic Engineering + RFC 7308: Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)"; } @@ -156,6 +210,7 @@ module ietf-te-types { description "Extended administrative group / resource class / color representation in 'hex-string' type. + The most significant byte in the hex-string is the farthest to the left in the byte sequence. Leading zero bytes in the configured value may be omitted for brevity."; @@ -200,9 +255,11 @@ module ietf-te-types { bit not set), abnormal (anomalous bit set), or unknown."; reference "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions + RFC 7823: Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric Extensions + RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; } @@ -308,12 +365,15 @@ module ietf-te-types { description "An identifier to uniquely identify an operator, which can be either a provider or a client. + The definition of this type is taken from RFCs 6370 and 5003. + This attribute type is used solely to provide a globally unique context for TE topologies."; reference "RFC 5003: Attachment Individual Identifier (AII) Types for Aggregation + RFC 6370: MPLS Transport Profile (MPLS-TP) Identifiers"; } @@ -578,6 +638,7 @@ module ietf-te-types { } description "An identifier for a topology. + It is optional to have one or more prefixes at the beginning, separated by colons. The prefixes can be 'network-types' as defined in the 'ietf-network' module in RFC 8345, to help the @@ -596,6 +657,7 @@ module ietf-te-types { } description "An identifier for a TE link endpoint on a node. + This attribute is mapped to a local or remote link identifier as defined in RFCs 3630 and 5305."; reference @@ -1099,7 +1161,7 @@ module ietf-te-types { "Association Type diversity used to associate LSPs whose paths are to be diverse from each other."; reference - "RFC8800: Path Computation Element Communication Protocol + "RFC 8800: Path Computation Element Communication Protocol (PCEP) Extension for Label Switched Path (LSP) Diversity Constraint Signaling"; } @@ -1110,7 +1172,7 @@ module ietf-te-types { // RFC Editor: remove the note above and this note identity objective-function-type { description - "Base identity for path objective function type."; + "Base identity for path objective function types."; } identity of-minimize-cost-path { @@ -1149,7 +1211,11 @@ module ietf-te-types { status obsolete; description "Objective function for minimizing aggregate bandwidth - consumption."; + consumption. + + This identity has been obsoleted: the + 'svec-of-minimize-agg-bandwidth-consumption' identity SHOULD + be used instead."; reference "RFC 5541: Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"; @@ -1163,7 +1229,11 @@ module ietf-te-types { status obsolete; description "Objective function for minimizing the load on the link that - is carrying the highest load."; + is carrying the highest load. + + This identity has been obsoleted: the + 'svec-of-minimize-load-most-loaded-link' identity SHOULD + be used instead."; reference "RFC 5541: Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"; @@ -1176,7 +1246,11 @@ module ietf-te-types { base objective-function-type; status obsolete; description - "Objective function for minimizing the cost on a path set."; + "Objective function for minimizing the cost on a path set. + + This identity has been obsoleted: the + 'svec-of-minimize-cost-path-set' identity SHOULD + be used instead."; reference "RFC 5541: Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"; @@ -1187,16 +1261,23 @@ module ietf-te-types { "Base identity for supported path computation mechanisms."; } + // CHANGE NOTE: The reference of the identity path-locally-computed + // below has been updated in this module revision + // RFC Editor: remove the note above and this note identity path-locally-computed { base path-computation-method; description "Indicates a constrained-path LSP in which the path is computed by the local LER."; reference - "RFC 3272: Overview and Principles of Internet Traffic - Engineering, Section 5.4"; + "RFC 9522: Overview and Principles of Internet Traffic + Engineering, Section 4.4"; } + // CHANGE NOTE: The reference of the identity + // path-externally-queried below has been updated + // in this module revision + // RFC Editor: remove the note above and this note identity path-externally-queried { base path-computation-method; description @@ -1208,12 +1289,17 @@ module ietf-te-types { returned by the external source may require further local computation on the device."; reference - "RFC 3272: Overview and Principles of Internet Traffic + "RFC 9522: Overview and Principles of Internet Traffic Engineering + RFC 4657: Path Computation Element (PCE) Communication Protocol Generic Requirements"; } + // CHANGE NOTE: The reference of the identity + // path-explicitly-defined below has been updated + // in this module revision + // RFC Editor: remove the note above and this note identity path-explicitly-defined { base path-computation-method; description @@ -1222,7 +1308,8 @@ module ietf-te-types { hops."; reference "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels - RFC 3272: Overview and Principles of Internet Traffic + + RFC 9522: Overview and Principles of Internet Traffic Engineering"; } @@ -2111,89 +2198,231 @@ module ietf-te-types { Protocol-Traffic Engineering (RSVP-TE)"; } - // CHANGE NOTE: The description of the identity path-metric-type - // has been updated in this module revision + // CHANGE NOTE: The path-metric-optimization-type base identity + // has been added in this module revision // RFC Editor: remove the note above and this note - identity path-metric-type { - description - "Base identity for the path metric type. - - Derived identities SHOULD describe the unit and maximum value - of the path metric types they define."; - } - - identity path-metric-te { - base path-metric-type; - description - "TE path metric."; - reference - "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a - second MPLS Traffic Engineering (TE) Metric"; - } - - identity path-metric-igp { - base path-metric-type; + identity path-metric-optimization-type { description - "IGP path metric."; - reference - "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a - second MPLS Traffic Engineering (TE) Metric"; + "Base identity used to define the path metric optimization + types."; } - // CHANGE NOTE: The reference for the identity path-metric-hop + // CHANGE NOTE: The link-path-metric-type base identity // has been added in this module revision // RFC Editor: remove the note above and this note - identity path-metric-hop { - base path-metric-type; + identity link-path-metric-type { description - "Hop path metric."; - reference - "RFC5440: Path Computation Element (PCE) Communication - Protocol (PCEP)"; + "Base identity used to define the link and the path metric + types. + + The unit of the path metric value is interpreted in the + context of the path metric type and the derived identities + SHOULD describe the unit of the path metric types they + define."; } + // CHANGE NOTE: The link-metric-type base identity + // and its derived identities + // have been added in this module revision + // RFC Editor: remove the note above and this note + identity link-metric-type { + base link-path-metric-type; + description + "Base identity for the link metric types."; + } - identity path-metric-delay-average { - base path-metric-type; - description - "Average unidirectional link delay."; - reference - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; - } + identity link-metric-te { + base link-metric-type; + description + "Traffic Engineering (TE) Link Metric."; + reference + "RFC 3630: Traffic Engineering (TE) Extensions to OSPF + Version 2, section 2.5.5 - identity path-metric-delay-minimum { - base path-metric-type; - description - "Minimum unidirectional link delay."; - reference - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; - } + RFC 5305: IS-IS Extensions for Traffic Engineering, + section 3.7"; + } - identity path-metric-residual-bandwidth { - base path-metric-type; - description - "Unidirectional Residual Bandwidth, which is defined to be - Maximum Bandwidth (RFC 3630) minus the bandwidth currently - allocated to LSPs."; - reference - "RFC 3630: Traffic Engineering (TE) Extensions to OSPF - Version 2 - RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions"; - } + identity link-metric-igp { + base link-metric-type; + description + "Interior Gateway Protocol (IGP) Link Metric."; + reference + "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric + as a second MPLS Traffic Engineering (TE) Metric"; + } - identity path-metric-optimize-includes { - base path-metric-type; - description - "A metric that optimizes the number of included resources - specified in a set."; - } + identity link-metric-delay-average { + base link-metric-type; + description + "Unidirectional Link Delay, measured in units of + microseconds."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.1 + + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.1"; + } - identity path-metric-optimize-excludes { - base path-metric-type; - description - "A metric that optimizes to a maximum the number of excluded - resources specified in a set."; - } + identity link-metric-delay-minimum { + base link-metric-type; + description + "Minimum unidirectional Link Delay, measured in units of + microseconds."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.2 + + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.2"; + } + + identity link-metric-delay-maximum { + base link-metric-type; + description + "Maximum unidirectional Link Delay, measured in units of + microseconds."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.2 + + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.2"; + } + + identity link-metric-residual-bandwidth { + base link-metric-type; + description + "Unidirectional Residual Bandwidth, measured in units of + bytes per second. + + It is defined to be Maximum Bandwidth minus the bandwidth + currently allocated to LSPs."; + reference + "RFC 7471: OSPF Traffic Engineering (TE) Metric + Extensions, section 4.5 + + RFC 8570: IS-IS Traffic Engineering (TE) Metric + Extensions, section 4.5"; + } + + // CHANGE NOTE: The base and the description of the + // path-metric-type identity + // has been updated in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-type { + base link-path-metric-type; + base path-metric-optimization-type; + description + "Base identity for the path metric types."; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-te identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-te { + base path-metric-type; + description + "Traffic Engineering (TE) Path Metric."; + reference + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.8"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-igp identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-igp { + base path-metric-type; + description + "Interior Gateway Protocol (IGP) Path Metric."; + reference + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.8"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-hop identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-hop { + base path-metric-type; + description + "Hop Count Path Metric."; + reference + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.8"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-delay-average identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-delay-average { + base path-metric-type; + description + "The Path Delay Metric, measured in units of + microseconds."; + reference + "RFC8233: Extensions to the Path Computation Element + Communication Protocol (PCEP) to Compute Service-Aware + Label Switched Paths (LSPs), section 3.1.1"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-delay-minimum identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-delay-minimum { + base path-metric-type; + description + "The Path Min Delay Metric, measured in units of + microseconds."; + reference + "I-D.ietf-pce-sid-algo: Carrying SR-Algorithm information + in PCE-based Networks, section 3.5.1"; + } + + // CHANGE NOTE: The description and the reference of the + // path-metric-residual-bandwidth identity have been updated + // in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-residual-bandwidth { + base path-metric-type; + description + "The Path Residual Bandwidth, defined as the minimum Link + Residual Bandwidth all the links along the path. + + The Path Residual Bandwidth can be seen as the path + metric associated with the Maximum residual Bandwidth Path + (MBP) objective function."; + reference + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; + } + + // CHANGE NOTE: The base of the path-metric-optimize-includes + // identity has been updated in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-optimize-includes { + base path-metric-optimization-type; + description + "A metric that optimizes the number of included resources + specified in a set."; + } + + // CHANGE NOTE: The base of the path-metric-optimize-excludes + // identity has been updated in this module revision + // RFC Editor: remove the note above and this note + identity path-metric-optimize-excludes { + base path-metric-optimization-type; + description + "A metric that optimizes to a maximum the number of excluded + resources specified in a set."; + } identity path-tiebreaker-type { description @@ -2257,11 +2486,15 @@ module ietf-te-types { RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels"; } + // CHANGE NOTE: The reference of the identity + // te-optimization-criterion below has been updated + // in this module revision + // RFC Editor: remove the note above and this note identity te-optimization-criterion { description "Base identity for the TE optimization criteria."; reference - "RFC 3272: Overview and Principles of Internet Traffic + "RFC 9522: Overview and Principles of Internet Traffic Engineering"; } @@ -2333,8 +2566,8 @@ module ietf-te-types { "Path computation has failed because of an unspecified reason."; reference - "Section 7.5 of RFC5440: Path Computation Element (PCE) - Communication Protocol (PCEP)"; + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP), section 7.5"; } identity path-computation-error-no-topology { @@ -2354,7 +2587,13 @@ module ietf-te-types { a Backward-Recursive Path Computation (BRPC) downstream PCE or a child PCE."; reference - "RFC5441, RFC8685"; + "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + Procedure to Compute Shortest Constrained Inter-Domain + Traffic Engineering Label Switched Paths + + RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture"; } identity path-computation-error-pce-unavailable { @@ -2365,10 +2604,11 @@ module ietf-te-types { It corresponds to bit 31 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5440: Path Computation Element (PCE) Communication - Protocol (PCEP); + "RFC 5440: Path Computation Element (PCE) Communication + Protocol (PCEP) - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-inclusion-hop { @@ -2387,9 +2627,12 @@ module ietf-te-types { It corresponds to bit 19 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-resource { @@ -2401,9 +2644,12 @@ module ietf-te-types { It corresponds to bit 20 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-child-pce-unresponsive { @@ -2415,9 +2661,12 @@ module ietf-te-types { It corresponds to bit 21 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-destination-domain-unknown { @@ -2429,9 +2678,12 @@ module ietf-te-types { It corresponds to bit 22 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8685; + "RFC 8685: Path Computation Element Communication Protocol + (PCEP) Extensions for the Hierarchical Path Computation + Element (H-PCE) Architecture - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-p2mp { @@ -2443,9 +2695,12 @@ module ietf-te-types { It corresponds to bit 24 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC8306; + "RFC 8306: Extensions to the Path Computation Element + Communication Protocol (PCEP) for Point-to-Multipoint + Traffic Engineering Label Switched Paths - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-gco-migration { @@ -2457,9 +2712,12 @@ module ietf-te-types { It corresponds to bit 26 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5557; + "RFC 5557: Path Computation Element Communication Protocol + (PCEP) Requirements and Protocol Extensions in Support of + Global Concurrent Optimization - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-gco-solution { @@ -2471,9 +2729,12 @@ module ietf-te-types { It corresponds to bit 25 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5557; + "RFC 5557: Path Computation Element Communication Protocol + (PCEP) Requirements and Protocol Extensions in Support of + Global Concurrent Optimization - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-pks-expansion { @@ -2485,9 +2746,12 @@ module ietf-te-types { It corresponds to bit 27 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5520; + "RFC 5520: Preserving Topology Confidentiality in + Inter-Domain Path Computation Using a Path-Key-Based + Mechanism - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-brpc-chain-unavailable { @@ -2499,9 +2763,12 @@ module ietf-te-types { It corresponds to bit 28 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5441; + "RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) + Procedure to Compute Shortest Constrained Inter-Domain + Traffic Engineering Label Switched Paths - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-source-unknown { @@ -2513,10 +2780,11 @@ module ietf-te-types { It corresponds to bit 29 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP); - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-destination-unknown { @@ -2528,10 +2796,11 @@ module ietf-te-types { It corresponds to bit 30 of the Flags field of the NO-PATH-VECTOR TLV."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP); - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } identity path-computation-error-no-server { @@ -2540,10 +2809,11 @@ module ietf-te-types { "Path computation has failed because path computation server is unavailable."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP); - https://www.iana.org/assignments/pcep/pcep.xhtml"; + https://www.iana.org/assignments/pcep + /pcep.xhtml#no-path-vector-tlv"; } // CHANGE NOTE: The base identity protocol-origin-type and @@ -2568,7 +2838,7 @@ module ietf-te-types { "Protocol origin is Path Computation Engine Protocol (PCEP)."; reference - "RFC5440: Path Computation Element (PCE) Communication + "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP)"; } @@ -2576,7 +2846,7 @@ module ietf-te-types { base protocol-origin-type; description "Protocol origin is Border Gateway Protocol (BGP)."; - reference "RFC9012"; + reference "RFC 9012"; } // CHANGE NOTE: The base identity svec-objective-function-type @@ -2587,8 +2857,8 @@ module ietf-te-types { description "Base identity for SVEC objective function type."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-agg-bandwidth-consumption { @@ -2597,8 +2867,8 @@ module ietf-te-types { "Objective function for minimizing aggregate bandwidth consumption (MBC)."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-load-most-loaded-link { @@ -2607,8 +2877,8 @@ module ietf-te-types { "Objective function for minimizing the load on the link that is carrying the highest load (MLL)."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-cost-path-set { @@ -2617,8 +2887,8 @@ module ietf-te-types { "Objective function for minimizing the cost on a path set (MCC)."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-of-minimize-common-transit-domain { @@ -2627,9 +2897,9 @@ module ietf-te-types { "Objective function for minimizing the number of common transit domains (MCTD)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation - Element (H-PCE) Architecture."; + Element (H-PCE) Architecture"; } identity svec-of-minimize-shared-link { @@ -2638,7 +2908,7 @@ module ietf-te-types { "Objective function for minimizing the number of shared links (MSL)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture."; } @@ -2649,7 +2919,7 @@ module ietf-te-types { "Objective function for minimizing the number of shared Shared Risk Link Groups (SRLG) (MSS)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture."; } @@ -2660,7 +2930,7 @@ module ietf-te-types { "Objective function for minimizing the number of shared nodes (MSN)."; reference - "RFC8685: Path Computation Element Communication Protocol + "RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture."; } @@ -2673,35 +2943,35 @@ module ietf-te-types { description "Base identity for SVEC metric type."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } - identity svec-metric-cumul-te { + identity svec-metric-cumulative-te { base svec-metric-type; description "Cumulative TE cost."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } - identity svec-metric-cumul-igp { + identity svec-metric-cumulative-igp { base svec-metric-type; description "Cumulative IGP cost."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } - identity svec-metric-cumul-hop { + identity svec-metric-cumulative-hop { base svec-metric-type; description "Cumulative Hop path metric."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-metric-aggregate-bandwidth-consumption { @@ -2709,8 +2979,8 @@ module ietf-te-types { description "Aggregate bandwidth consumption."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } identity svec-metric-load-of-the-most-loaded-link { @@ -2718,8 +2988,8 @@ module ietf-te-types { description "Load of the most loaded link."; reference - "RFC5541: Encoding of Objective Functions in the Path - Computation Element Communication Protocol (PCEP)."; + "RFC 5541: Encoding of Objective Functions in the Path + Computation Element Communication Protocol (PCEP)"; } /** @@ -2832,11 +3102,13 @@ module ietf-te-types { grouping are applicable to generic TE PM as well as packet TE PM."; reference - "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions - RFC 7823: Performance-Based Path Selection for Explicitly - Routed Label Switched Paths (LSPs) Using TE Metric - Extensions - RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; + "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensionsù + + RFC 7823: Performance-Based Path Selection for Explicitly + Routed Label Switched Paths (LSPs) Using TE Metric + Extensions + + RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions"; leaf one-way-delay { type uint32 { range "0..16777215"; @@ -3268,6 +3540,9 @@ module ietf-te-types { } } + // CHANGE NOTE: The explicit-route-hop grouping below has been + // updated in this module revision + // RFC Editor: remove the note above and this note grouping record-route-state { description "The Record Route grouping."; @@ -3541,12 +3816,15 @@ module ietf-te-types { } } + // CHANGE NOTE: The grouping optimization-metric-entry below has + // been updated in this module revision + // RFC Editor: remove the note above and this note grouping optimization-metric-entry { description "Optimization metrics configuration grouping."; leaf metric-type { type identityref { - base path-metric-type; + base path-metric-optimization-type; } description "Identifies the 'metric-type' that the path computation @@ -3624,6 +3902,9 @@ module ietf-te-types { } } + // CHANGE NOTE: The grouping tunnel-constraints below has + // been updated in this module revision + // RFC Editor: remove the note above and this note grouping tunnel-constraints { description "Tunnel constraints grouping that can be set on @@ -3637,13 +3918,13 @@ module ietf-te-types { uses common-constraints; } + // CHANGE NOTE: The grouping path-constraints-route-objects below + // has been updated in this module revision + // RFC Editor: remove the note above and this note grouping path-constraints-route-objects { description "List of route entries to be included or excluded when performing the path computation."; - // CHANGE NOTE: The explicit-route-objects container below has - // been updated in this module revision - // RFC Editor: remove the note above and this note container explicit-route-objects { description "Container for the explicit route object lists."; @@ -3769,19 +4050,30 @@ module ietf-te-types { } } + // CHANGE NOTE: The grouping generic-path-metric-bounds below + // has been updated in this module revision + // RFC Editor: remove the note above and this note grouping generic-path-metric-bounds { description "TE path metric bounds grouping."; container path-metric-bounds { description - "TE path metric bounds container."; + "Top-level container for the list of path metric bounds."; list path-metric-bound { key "metric-type"; description - "List of TE path metric bounds."; + "List of path metric bounds, which can apply to link and + path metrics. + + TE paths which have at least one path metric which + exceeds the specified bounds MUST NOT be selected. + + TE paths that traverse TE links which have at least one + link metric which exceeds the specified bounds MUST NOT + be selected."; leaf metric-type { type identityref { - base path-metric-type; + base link-path-metric-type; } description "Identifies an entry in the list of 'metric-type' items @@ -3791,18 +4083,21 @@ module ietf-te-types { type uint64; default "0"; description - "Upper bound on the end-to-end TE path metric. + "Upper bound on the specified 'metric-type'. A zero indicates an unbounded upper limit for the - specific 'metric-type'. + specificied 'metric-type'. The unit of is interpreted in the context of the - path-metric-type."; + 'metric-type' identity."; } } } } + // CHANGE NOTE: The grouping generic-path-metric-bounds below + // has been updated in this module revision + // RFC Editor: remove the note above and this note grouping generic-path-optimization { description "TE generic path optimization grouping."; @@ -3825,7 +4120,11 @@ module ietf-te-types { /* Tiebreakers */ container tiebreakers { description - "Container for the list of tiebreakers."; + "Container for the list of tiebreakers. + + This container has been obsoleted by the tiebreaker + leaf."; + status deprecated; list tiebreaker { key "tiebreaker-type"; description @@ -3861,6 +4160,15 @@ module ietf-te-types { } } } + leaf tiebreaker { + type identityref { + base path-tiebreaker-type; + } + default "te-types:path-tiebreaker-random"; + description + "The tiebreaker criteria to apply on an equally favored set + of paths, in order to pick the best."; + } } grouping generic-path-affinities { @@ -4065,7 +4373,7 @@ module ietf-te-types { description "LSP encoding type."; reference - "RFC3945"; + "RFC 3945"; } leaf switching-type { type identityref { @@ -4074,7 +4382,7 @@ module ietf-te-types { description "LSP switching type."; reference - "RFC3945"; + "RFC 3945"; } }