Re: [Lsr] Working Group Adoption Poll for "Updates to Anycast Property advertisement for OSPFv2" - draft-chen-lsr-anycast-flag-06

Hi Les,

> Knowledge of whether a given prefix is Anycast has proven useful in
existing deployments

Would you be so kind and enlighten us with a few practical examples in
which you exhibit practical usefulness of this flag at the IGP level?

More basic question - is this set by CLI or is there a special protocol
algorithm which set such flag ? If it is the latter, can you explain it ?

So if suddenly one src of such anycast goes down rest of the area still
thinks it is anycast ?

>From the BGP side of things indeed for basic IPv4/IPv6 concept of ghost
loopbacks were used as next hops which indeed were advertised as anycast
addresses. Is that one example in which you would hope that BGP prefers a
path if the next hop is an anycast address as told by IGP ? And you push
that "automation" to operators to prefer such paths by manual configuration
?

And to second Bruno's question - what is IGP's definition of an anycast
address ?

Many thx,
Robert

On Thu, Mar 21, 2024 at 7:47 PM Les Ginsberg (ginsberg) <ginsberg=
40cisco.com@dmarc.ietf.org> wrote:

> I support adoption of this draft.
> Knowledge of whether a given prefix is Anycast has proven useful in
> existing deployments - closing this gap for OSPFv2 is a good thing to do.
>
> One editorial comment. The introduction (and abstract) states:
>
> " Both SR-MPLS prefix-SID and IPv4 prefix may be configured as anycast
>    and as such the same value can be advertised by multiple routers."
>
> But there is no further discussion of prefix-SID in the draft.
> I think mention of the prefix-SID should be removed.
>
>     Les
>
>
> > -----Original Message-----
> > From: Lsr <lsr-bounces@ietf.org> On Behalf Of Acee Lindem
> > Sent: Tuesday, March 19, 2024 11:43 AM
> > To: lsr <lsr@ietf.org>
> > Cc: draft-chen-lsr-anycast-flag@ietf.org
> > Subject: [Lsr] Working Group Adoption Poll for "Updates to Anycast
> Property
> > advertisement for OSPFv2" - draft-chen-lsr-anycast-flag-06
> >
> >
> > This starts the Working Group adoption call for
> draft-chen-lsr-anycast-flag.
> > This is a simple OSPFv2 maintenance draft adding an Anycast flag for IPv4
> > prefixes to align with IS-IS and OSPFv3.
> >
> > Please send your support or objection to this list before April 6th,
> 2024.
> >
> > Thanks,
> > Acee
> >
> >
> > _______________________________________________
> > Lsr mailing list
> > Lsr@ietf.org
> > https://www.ietf.org/mailman/listinfo/lsr
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>