Skip to content
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

Questions on the list of tiebreakers defined in RFC8776 #263

Closed
italobusi opened this issue Feb 9, 2024 · 2 comments · Fixed by #262
Closed

Questions on the list of tiebreakers defined in RFC8776 #263

italobusi opened this issue Feb 9, 2024 · 2 comments · Fixed by #262

Comments

@italobusi
Copy link
Collaborator

italobusi commented Feb 9, 2024

The model provides a list of tiebreaker criteria "to apply on an equally favored set of paths, in order to pick the best".

Few questions for clarification:

  1. The tiebreaker-type is an identityref with base path-metric-type and not with base path-tiebreaker-type

  2. Is the list ordered or not? If ordered, how? If not, how different tiebreakers can be applied?

Note that RFC8776 defines the path-tiebreaker-type base identity and its derived identities but no data node using them.

@italobusi italobusi changed the title Tiebreac Questions on the list of tiebreakers defined in RFC8776 Feb 9, 2024
@italobusi
Copy link
Collaborator Author

italobusi commented Feb 9, 2024

@italobusi italobusi self-assigned this Feb 9, 2024
@italobusi italobusi removed their assignment Feb 9, 2024
@italobusi italobusi added waiting Pending resolution of other open issue(s) agreed and removed agreed waiting Pending resolution of other open issue(s) labels Feb 16, 2024
@italobusi
Copy link
Collaborator Author

2024-02-16 TE call

     |     |     +--rw optimizations
     |     |     |  +--rw (algorithm)?
     |     |     |     +--:(metric) {path-optimization-metric}?
     |     |     |     |  +--rw optimization-metric* [metric-type]
     |     |     |     |  |  +--rw metric-type                       identityref
     |     |     |     |  |  +--rw weight?                           uint8
     |     |     |     +--:(objective-function) {path-optimization-objective-function}?
     |     |     |        +--rw objective-function
     |     |     |           +--rw objective-function-type?   identityref
     |     |     +--rw tiebreaker    path-tiebreaker-type // default random

@italobusi italobusi added agreed and removed waiting Pending resolution of other open issue(s) labels Feb 16, 2024
@italobusi italobusi self-assigned this Feb 16, 2024
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
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant