Closed arthurMll closed 6 years ago
You can also take a look at this document:
https://tools.ietf.org/html/draft-ietf-teas-yang-path-computation-02
We have started the work from TAPI path computation and further improved it based on feedbacks/comments from TE experts in IETF
In particular, it highlights the importance of having alignment between path computation and connectivity setup path constraints
My 2 cents
Italo
@arthurMll I will update it today to align with the Connectivity model.
Thanks, Italo.
From: italobusi notifications@github.com Sent: Friday, August 31, 2018 1:49 AM To: OpenNetworkingFoundation/TAPI Cc: Subscribed Subject: [EXTERNAL] Re: [OpenNetworkingFoundation/TAPI] Missing path constrains into tapi-path-computation model (#333)
You can also take a look at this document:
https://tools.ietf.org/html/draft-ietf-teas-yang-path-computation-02
We have started the work from TAPI path computation and further improved it based on feedbacks/comments from TE experts in IETF
In particular, it highlights the importance of having alignment between path computation and connectivity setup path constraints
My 2 cents
Italo
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/OpenNetworkingFoundation/TAPI/issues/333#issuecomment-417598036, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABEOpwDpN3HX6qE9cGl7S--rGjp9_LPdks5uWPijgaJpZM4WUt4q.
According to my latest review of tapi-path-computation model, there are some parameters already included in tapi-connectivity model regarding the introduction of path constrains which are currently missing.
My general comment is that all path constrians which are available in tapi-connectivity model shall be availabe for the path computation service. Nevertheless its possible that some cases may differ, so I leave here what I consider are missing now within the "routing-constraint" container: