Hi John, Sorry for delay in the response; I was away from the emails. Please see in-line.
Thanks Regards … Zafar <snip> <snip> procedure (in draft-hegde-spring-traffic-accounting-for-sr-paths) that breaks SR Architecture, highly unscalable and complicated to implement. [JD] Do you have any evidence to justify any of your assertions, above? Please note that in draft-hegde-spring-traffic-accounting-for-sr-paths: • The transit node needs to be able to recognize the special label, read the SR Path Identification label and update the counter against such “states”. • The draft proposes to push (up to) 3 Labels for each segment in the SR Path. That means that label stack is increased up to 3x times! This is a serious a scaling issue. • The controller needs to keep track of transit node capability and push the additional per-path labels, accordingly. I.e., the controller also needs to maintain such information for the transit nodes. <snip>
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
