Robert, In the new version of the draft, we have: “The aggregated site cost associated with a prefix (i.e., ANYCAST prefix) can be a value configured on the router to which the prefix is attached. The aggregated site cost can be computed based on an algorithm configured on router for specific prefixes. The detailed algorithm of computing the aggregated site cost is out of the scope of document. As the cost change can impact the path computation, there is a Minimum Interval for Metrics Change Advertisement which is configured on the routers to avoid route oscillations. Default is 30s. The aggregated site cost change rate is comparable with the rate of adding or removing application instances at locations to adapt to the workload distribution changes. The rate of change could be in weeks or days. On rare occasions, there might need rate changes in hours..”
Your comments and suggestions are greatly appreciated. Linda From: Robert Raszuk <[email protected]> Sent: Monday, January 17, 2022 5:29 AM To: Aijun Wang <[email protected]> Cc: Acee Lindem (acee) <[email protected]>; Linda Dunbar <[email protected]>; John E Drake <[email protected]>; Les Ginsberg (ginsberg) <[email protected]>; Gyan Mishra <[email protected]>; lsr <[email protected]> Subject: Re: [Lsr] Seeking feedback to the revised draft-dunbar-lsr-5g-edge-compute Aijun, Such metric will be same(because of the ANYCAST address be advertised simultaneously via R1/R2/R3 at the same time for one application server, for example, S1/aa08::4450). That is not really correct. On each router R1 or R2 or R3 when you for example redistribute or originate in any other way host route for example S1/aa08::4450 you can apply a different metric to it. That is why I keep asking what is the mechanism in which routers will be informed what host routes to advertise and what metric to use for each IP address of the server or application on the server. The most precise answer received so far was "it is out of scope". And that is important irrespective if we are talking about using passive interfaces, stub interfaces or simply static routes. Thx, R.
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
