Hi Max, Thank you for publishing this draft. I have few questions after reading it.
1. If I have /24 and I advertise it over N peerings N>1 to my ISP from my DMZ does it automatically become ANYCAST prefix ? 1a. Note that I may have just one real host route in this /24 which I consider a true anycast destination. 2. Are you proposing to make any changes to best path selection based on the presence of the specified community ? 3. As I am sure you realize hot-potato or not-so-hot-potato routing is the result of choosing a best paths with a given next hop. Consideration of correct metric to this next hop is what makes it hot or not. Now with the use of route reflection where RRs are not in the data path that metric is normally fake (possibly hot from perspective of RR but not necessarily hot from the perspective of the client) . That is why I wrote RFC9107 ( https://datatracker.ietf.org/doc/rfc9107/) to allow to use the correct metric. Are mandating use of such tools for prefixes marked with ANYCAST community ? 4. Or alternatively to #3 are you suggesting to always use ADD-PATHS ALL for all prefixes marked with ANYCAST community ? Bottom line you have written good justification why such marking makes sense. But currently draft is missing more description when to mark when advertising given prefix over eBGP sessions (redundant advertisement is a norm these days). There is also no description on expected BGP implementation behavior when such prefixes marked with ANYCAST community are received by BGP speaker. Many thx, R. On Tue, Jul 5, 2022 at 12:40 PM Maximilian Wilhelm <[email protected]> wrote: > Hey folks, > > after some discussion at RIPE84 we took the time to formalize a draft > to define a well-known BGP community to indicate a given prefix is > carrying Anycast traffic. The intent is to allow ISPs to do well > informed TE, especially in cases where they want to diverge from the > hot potato principle. > > You can find the draft at > > https://datatracker.ietf.org/doc/draft-wilhelm-grow-anycast-community/ > > Happy to share this at the upcoming meeting and hear your thoughts! > > Thanks and best, > Max > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow >
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
