<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.chen-lsr-anycast-flag" target="https://datatracker.ietf.org/doc/html/draft-chen-lsr-anycast-flag-02">
   <front>
      <title>Updates to Anycast Property advertisement for OSPF</title>
      <author initials="R." surname="Chen" fullname="Ran Chen">
         <organization>ZTE Corporation</organization>
      </author>
      <author initials="D." surname="Zhao" fullname="Detao Zhao">
         <organization>ZTE Corporation</organization>
      </author>
      <author initials="P." surname="Psenak" fullname="Peter Psenak">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="K." surname="Talaulikar" fullname="Ketan Talaulikar">
         <organization>Arrcus, Inc</organization>
      </author>
      <date month="June" day="29" year="2023" />
      <abstract>
	 <t>   Both SR-MPLS prefixes-SID and IPv4 prefix may be configured as
   anycast and as such the same value can be advertised by multiple
   routers.  It is useful for other routers to know that the
   advertisement is for an anycast identifier.

   Each prefix is advertised along with an 8-bit field of
   capabilities,by using the flag flield in the OSPFv2 Extended Prefix
   TLV [RFC7684], but the definition of anycast flag to identify the
   prefix as anycast has not yet been defined.

   This document updates [RFC7684], by defining a new flag in the OSPFv2
   Extended Prefix TLV [RFC7684] to advertise the anycast property.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-chen-lsr-anycast-flag-02" />
   
</reference>
