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

[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)

[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 originating AS intended this to be anycast or not, and a
> standardcommunity makes this easier than having to look up per-AS
> documentation.*
>
> Essentially no harm, only (potential) benefit.
>
> Thx,
> R.
>
>
>
> On Sat, Nov 5, 2022 at 3:52 PM Gert Doering  wrote:
>
>> 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 originating AS intended this to be anycast or not, and a standard
>> community makes this easier than having to look up per-AS documentation.
>>
>> (Our routing policy is simple enough that I might not actually have our
>> routers *act* on it, but it's still useful when looking at BGP
>> announcements
>> when troubleshooting)
>>
>> Gert Doering
>> -- NetMaster
>> --
>> have you enabled IPv6 on something today...?
>>
>> SpaceNet AG  Vorstand: Sebastian v. Bomhard, Michael
>> Emmer
>> Joseph-Dollinger-Bogen 14
>> 
>>   Aufsichtsratsvors.: A. Grundner-Culemann
>> D-80807 Muenchen HRB: 136055 (AG Muenchen)
>> Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
>>
>> ___
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
> ___
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
-- 
===
David Farmer   Email:far...@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SEPhone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===
___
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)

[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 having to look up per-AS documentation.*

Essentially no harm, only (potential) benefit.

Thx,
R.



On Sat, Nov 5, 2022 at 3:52 PM Gert Doering  wrote:

> 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 originating AS intended this to be anycast or not, and a standard
> community makes this easier than having to look up per-AS documentation.
>
> (Our routing policy is simple enough that I might not actually have our
> routers *act* on it, but it's still useful when looking at BGP
> announcements
> when troubleshooting)
>
> Gert Doering
> -- NetMaster
> --
> have you enabled IPv6 on something today...?
>
> SpaceNet AG  Vorstand: Sebastian v. Bomhard, Michael
> Emmer
> Joseph-Dollinger-Bogen 14Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
>
> ___
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
___
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)

[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 originating AS intended this to be anycast or not, and a standard
community makes this easier than having to look up per-AS documentation.

(Our routing policy is simple enough that I might not actually have our
routers *act* on it, but it's still useful when looking at BGP announcements
when troubleshooting)

Gert Doering
-- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG  Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

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

[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 prefixes used for Anycast
Abstract: 
   In theory routing decisions on the Internet and by extension within
   ISP networks should always use hot-potato routing to reach any given
   destination.  In reality operators sometimes choose to not use the
   hot-potato paths to forward traffic due to a variety of reasons,
   mostly motivated by traffic engineering considerations.  For prefixes
   carrying anycast traffic in virtually all situations it is advisable
   to stick to the hot-potato principle.  As operators mostly don't know
   which prefixes are carrying unicast or anycast traffic, they can't
   differentiate between them in their routing policies.

   To allow operators to take well informed decisions on which prefixes
   are carrying anycast traffic this document proposes a well-known BGP
   community to denote this property.

The Internet-Draft can be found here: 
https://datatracker.ietf.org/doc/draft-wilhelm-grow-anycast-community/

Please share with the mailing list if you are think this work should be
adopted by GROW, willing to review and/or otherwise contribute to this
draft!

WG Adoption call ends November 22th, 2022.

Kind regards,

Job / Chris

___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow