Getting back on your original post, after a bit of more thinking: Perhaps centralized or distributed computing of repair path approach pros/cons are interesting to discuss ;
>That would suggest that whilst we might benefit from standardizing >the advertisement of some IPFRR related parameters, and would >certainly benefit from standardization of the YANG models needed >to control the IPFRR subsystem, Sure. >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. -- Uma C.
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
