Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-11-26 Thread Robert Raszuk
Interesting observation indeed. I guess it depends on macro view if we are talking global or intradomain ("limited domains"). Cheers, R. On Sun, Nov 26, 2023 at 6:05 PM David Farmer wrote: > I don’t think you need multi path to utilize this anycast community, > neither do you need to override

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-11-26 Thread David Farmer
I don’t think you need multi path to utilize this anycast community, neither do you need to override hot potato routing. In fact in my mind, when this community is set you want to ensure hot potato routing, even if your normal policy was not to use hot potato routing. For example, in the research

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-11-26 Thread Robert Raszuk
Gert, I get that. And I am not asking to add specific prescription for automagic. However if I am reading this RFC as a vendor or as an operator I would find useful to have a section recommending a way in which I can use it a bit more directly then match in the policy. In fact to the best of my

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-11-26 Thread Gert Doering
Hi, On Sun, Nov 26, 2023 at 04:02:31PM +0100, Robert Raszuk wrote: > Effectively to make use of this community (provided all good marking and > good will of transits) you need to have some hooks in your local BGP > implementations to allow for multipath selection when at least one received > prefi

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-11-26 Thread Robert Raszuk
Hi, So I reread this discussion and have one more question .. . Abstract says: *To allow operators to take well informed decisions on which prefixesare carrying anycast traffic this document proposes a well-known BGPcommunity to denote this property.* Cool - but how is this decision going to

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-11-26 Thread Job Snijders
Dear Maximilian, On Sun, Nov 26, 2023 at 02:45:58PM +0100, Maximilian Wilhelm wrote: > Anno domini 2023 Maximilian Wilhelm scripsit: > > [...] > > Some time has past and I don't see any new comments, neither here nor > > to us authors. > > > > Hence I'd like to ask the chairs to start the WG Last

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-11-26 Thread Maximilian Wilhelm
Hi folks, Anno domini 2023 Maximilian Wilhelm scripsit: [...] > Some time has past and I don't see any new comments, neither here nor > to us authors. > > Hence I'd like to ask the chairs to start the WG Last Call. I believe this didn't happen so far, or did I miss it? :) So I'd like to ask to

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-06-21 Thread Kevin Wallace
Hi Max and folks, On Jun 21, 2023, at 12:53 PM, Maximilian Wilhelm wrote: > Some time has past and I don't see any new comments, neither here nor > to us authors. Job shared this on IRC and asked me to send feedback here. It seems that networks have little incentive to tag routes accurately, an

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-06-21 Thread Alarig Le Lay
Hello, I have some concerns about the RFC: 1. I’m not sure that it will be used to influence routing of anycast prefixes, but rather of prefixes that one wants to be treated as hot-potato 2. I don’t specially trust operators to take better routing decisions if the community is present; it

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-06-21 Thread Maximilian Wilhelm
Hi folks, Anno domini 2023 Maximilian Wilhelm scripsit: > Anno domini 2023 Job Snijders scripsit: > > The next step in this process is "Working Group Last Call", a period of > > time in which members of this working group can comment on the > > internet-draft's comments (before its send onwards t

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-05-29 Thread Maximilian Wilhelm
Hi, Anno domini 2023 Job Snijders scripsit: > On Sat, May 27, 2023 at 08:43:59PM +0200, Maximilian Wilhelm wrote: > > It looks like the expiration date of this draft is coming up. > > > > I've seen quite some support for this here so it was adopted as a WG > > document. Since then there wasn't m

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-05-29 Thread Job Snijders
On Sat, May 27, 2023 at 08:43:59PM +0200, Maximilian Wilhelm wrote: > Anno domini 2022 Job Snijders scripsit: > > > Thank you for your feedback! There was good support to adopt this > > internet-draft and continue work on it as a working group document. > > > > Authors, please name the internet-d

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2023-05-27 Thread Maximilian Wilhelm
Dear all, Anno domini 2022 Job Snijders scripsit: > Thank you for your feedback! There was good support to adopt this > internet-draft and continue work on it as a working group document. > > Authors, please name the internet-draft "draft-ietf-grow-anycast-community-00" > and submit it to https:

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-26 Thread Maximilian Wilhelm
Dear Job, On 11/26/22 23:25, Job Snijders wrote: Dear Maximilian, On Sat, Nov 26, 2022 at 11:17:06PM +0100, Maximilian Wilhelm wrote: thanks for the support! I re-uploaded the draft with the updated name. Chairs, I heard there is an option to ask for an early allocation for a community? I ha

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-26 Thread Job Snijders
Dear Maximilian, On Sat, Nov 26, 2022 at 11:17:06PM +0100, Maximilian Wilhelm wrote: > thanks for the support! > > I re-uploaded the draft with the updated name. > > Chairs, I heard there is an option to ask for an early allocation for > a community? I have to admit that I'm not deeply familar w

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-26 Thread Maximilian Wilhelm
Dear all, thanks for the support! I re-uploaded the draft with the updated name. Chairs, I heard there is an option to ask for an early allocation for a community? I have to admit that I'm not deeply familar with the process here, I have however a favorite value in mind which I would love to

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-26 Thread Job Snijders
Dear all, Thank you for your feedback! There was good support to adopt this internet-draft and continue work on it as a working group document. Authors, please name the internet-draft "draft-ietf-grow-anycast-community-00" and submit it to https://datatracker.ietf.org/submit/ Kind regards, Job

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-21 Thread Brian Dickson
On Sat, Nov 5, 2022 at 7:48 AM Job Snijders wrote: > Dear GROW, > > The authors of draft-wilhelm-grow-anycast-community asked whether this > working group could consider adoption of the internet-draft. > > This message is a request to the group for feedback on whether this > internet-draft should

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-07 Thread heasley
I support adoption. ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-05 Thread Randy Bush
read. like. support adoption. randy ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-05 Thread David Farmer
+1 to all the points below. On Sat, Nov 5, 2022 at 10:29 Robert Raszuk wrote: > Support. > > I was hesitant however below Gert's point made it obvious for me that this > should be > adopted and published: > > > > > *I find this a useful feature, being able to look at a prefix and seeif > the ori

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-05 Thread Robert Raszuk
Support. I was hesitant however below Gert's point made it obvious for me that this should be adopted and published: *I find this a useful feature, being able to look at a prefix and seeif the originating AS intended this to be anycast or not, and a standardcommunity makes this easier than hav

Re: [GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-05 Thread Gert Doering
Hi, On Sat, Nov 05, 2022 at 03:48:16PM +0100, Job Snijders wrote: > The authors of draft-wilhelm-grow-anycast-community asked whether this > working group could consider adoption of the internet-draft. Support adoption. I find this a useful feature, being able to look at a prefix and see if the

[GROW] Working Group Adoption Call: draft-wilhelm-grow-anycast-community (Ends 22/Nov/2022)

2022-11-05 Thread Job Snijders
Dear GROW, The authors of draft-wilhelm-grow-anycast-community asked whether this working group could consider adoption of the internet-draft. This message is a request to the group for feedback on whether this internet-draft should be adopted. Title: A well-known BGP community to denote prefixe