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-boun...@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-f...@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
