Skip to content

Preparation for v10 of RFC8776-bis #270

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
italobusi merged 13 commits into from
Feb 22, 2024
Merged

Preparation for v10 of RFC8776-bis #270

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
2a6271d
Updated revision description
italobusi Jan 29, 2024
cbe708f
Replaced references to RFC3272 with references to RFC9522
italobusi Feb 6, 2024
da82059
Updated te-types based on https://github.com/tsaad-dev/te/issues/103#…
italobusi Feb 9, 2024
8b70503
Updated te-types and te-packet types
italobusi Feb 9, 2024
3e42d2c
Fix compilation errors
italobusi Feb 9, 2024
b9e439b
Updated TE Types YANG
italobusi Feb 16, 2024
877da84
Updated tiebreaker definition: fix #263
italobusi Feb 16, 2024
f5c7a37
Updated optimization metrics: fix #264
italobusi Feb 16, 2024
be43134
Updated definition for path-metric-residual-bandwidth
italobusi Feb 16, 2024
9c0adb6
Updated revision description
italobusi Feb 16, 2024
05e9650
Minor editorial updates
italobusi Feb 16, 2024
0061afc
Added changes from RFC8776: fix #220
italobusi Feb 16, 2024
ec20375
Fix submission nits
italobusi Feb 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
121 changes: 65 additions & 56 deletions drafts/te-types-update/diffs/te-pkt-types/model-diff-spaces.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
< /**
---
> /*
Expand Down Expand Up @@ -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
> }
> }
>
Expand Down
121 changes: 65 additions & 56 deletions drafts/te-types-update/diffs/te-pkt-types/model-diff.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
< /**
---
> /*
Expand Down Expand Up @@ -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
> }
> }
>
Expand Down
Loading