Since we didn't have enough time at today's LSR session, I want to continue the discussion of draft-dunbar-lsr-5g-edge-compute on the mailing list:
* Shraddha pointed out that advertising the "site aggregated cost" of a Prefix (ANYCAST) might cause oscillation of traffic flow as other egress routers with the same prefix attached can advertise different metric to cause the change of the path computation. OSPF-TE has the same problem, does it? Link Bandwidth or condition changes advertisement can cause IGP path change? >From each node's perspective, there has be a timer to adjust the IGP path >change with newly received "site-cost" metrics. In addition, "Site-Cost" associated with the prefix is only considered in computing the IGP path when the Flag in the FlexAlgo TLV is set to indicate the need to include the "site-cost" metrics. * draft-dunbar-lsr-5g-edge-compute is using E-intra-Area-Prefix-LSA[RFC7684] and Prefix Reachability TLV to advertise the "Site-Cost" associated with the prefix. At today's session, I heard that the "Stub Link" can be used as well. Want to hear WG opinion on which one is more suitable? One more point, the "Site-Cost" associated with a prefix is not only intended as Tiebreaker. When the Flag in the FlexAlgo TLV is set to indicate the need to include the "site-cost" metrics, the path computation will include the value in the SPF computation. Thank you very much. Linda
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
