Closed arthurMll closed 5 months ago
Already discussed during TAPI call 25/06/2019, the overall idea is that the concept of nominal or primary route for a given connection is not modeled in TAPI yet.
Regarding (1), the assumption is correct, currently defined "tapi-connectivity:connection/switch-control/switch/selected-route” object is intended to represent only the current active route for a given connection. Thus, the discussion from now and on is regarding the required new definitions in TAPI required to support new use cases which required this distinction between the nominal route and the backup paths.
Solved from version 2.3.1 on.
Currently there is not distinction between which is the "Nominal" or "Primary" route and the rest of backup routes, for a given connection. There are more than one point to tackle here: