Re: [GROW] Proposing a well-known BGP community for Anycast

2022-07-05 Thread Jeffrey Haas
Max, > On Jul 5, 2022, at 6:40 AM, Maximilian Wilhelm wrote: > 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 i

Re: [GROW] Working Group Adoption Call: draft-lucente-grow-bmp-tlv-ebit (Ends 02/May/2022)

2022-07-05 Thread Job Snijders
Dear all, The call for working group adoption ended some time ago, it seems numerous people are in favor of progressing this work in the GROW working group. Authors - please resubmit this draft as 'draft-ietf-grow-bmp-tlv-ebit' Kind regards, Job GROW co-chair On Fri, Apr 08, 2022 at 04:19:19PM

Re: [GROW] Proposing a well-known BGP community for Anycast

2022-07-05 Thread Robert Raszuk
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 an

Re: [GROW] Proposing a well-known BGP community for Anycast

2022-07-05 Thread Job Snijders
Dear Max, On Tue, Jul 05, 2022 at 12:40:48PM +0200, Maximilian Wilhelm wrote: > 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 T

[GROW] Proposing a well-known BGP community for Anycast

2022-07-05 Thread Maximilian Wilhelm
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 prin