-
Notifications
You must be signed in to change notification settings - Fork 19
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.
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
Question on path-metric-optimize include and exclude #264
Labels
Comments
2024-02-09 TE Call
|
2024-02-16 TE call Define a new base identity for path optimization metrics, such that:
The metric types used for optimization should be path optimization metrics, while the metric types use for path metric bounds or properties should be path metric types. |
italobusi
added a commit
to italobusi/te
that referenced
this issue
Feb 16, 2024
italobusi
added a commit
that referenced
this issue
Feb 22, 2024
- Added description of the YANG model changes in [draft-ietf-teas-rfc8776-update-09](https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc8776-update-09) - Replaced references to RFC3272 with references to RFC9522: fix #261 - Updated tiebreaker definition: fix #263 - Updated optimization metrics: fix #264 - Clean-up link and path metrics for generic and packet TE types: fix #103 - Added description of the changes from RFC8776: fix #220
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
path-metric-optimize-includes
andpath-metric-optimize-excludes
identities have been defined with the basepath-metric-type
in RFC8776 in order to be used withingrouping optimization-metric-entry
With the current definition it is also possible to use them as
path-metric-bound
as well aspath-properties
. However, it is not fully clear how they can be used in these two casesNote: they could also be used as
tiebreaker-type
but this depends on the resolution of issue #263The text was updated successfully, but these errors were encountered: