On 03/12/2014 19:59, Uma Chunduri wrote:
>the method of calculating the
>repair topology itself ought to be private to the orchestrator.
When we agree to standardize the IPFRR related parameters, IMO it’s
important to standardize the relevant algorithm too regardless of
where it’s used.
If it is used in a distributed manner this question is less relevant
as it’s mostly multi-vendor deployments.
Even when an orchestrator is computing using a particular algorithm
IMO, it’s important Vendor X and Vendor Y of the controller do the
same thing and
also this has to be **clearly** understood to validate (to see the
corner cases are working correct) and debug stuff, once deployed.
Proprietary stuff may come with their own cost/risk.
I would appreciate hearing the operator's perspective(s) on this.
Will we see two vendor's controllers operate over the same set of nodes
such that identical behaviour is required, or is this an area where we
are likely to see customization to execute the repair in a way that best
suits the specifics of the network and the applicable business model?
Stewart
_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg
