Protocol Action: 'OSPFv2 Anycast Property Advertisement' to Proposed Standard (draft-ietf-lsr-anycast-flag-13.txt)

The IESG <iesg-secretary@ietf.org> Mon, 26 January 2026 17:18 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'OSPFv2 Anycast Property Advertisement' to Proposed Standard (draft-ietf-lsr-anycast-flag-13.txt)
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <176944790244.915120.348369034372345047@dt-datatracker-77f8b84995-z4hzn>
Date: Mon, 26 Jan 2026 09:18:22 -0800
Message-ID-Hash: 7I7PHAPMZBIO5GW4MHZJHAEJUKNPTBEV
CC: The IESG <iesg@ietf.org>, acee.ietf@gmail.com, draft-ietf-lsr-anycast-flag@ietf.org, gunter@vandevelde.cc, lsr-chairs@ietf.org, lsr@ietf.org, rfc-editor@rfc-editor.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/kaD3I07ltuk38wNVaXOtUftAP48>

The IESG has approved the following document:
- 'OSPFv2 Anycast Property Advertisement'
  (draft-ietf-lsr-anycast-flag-13.txt) as Proposed Standard

This document is the product of the Link State Routing Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and Ketan
Talaulikar.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lsr-anycast-flag/




Technical Summary

   An IP 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.

   This document defines a new flag in the OSPFv2 Extended Prefix TLV
   Flags to advertise the anycast property.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

The document has strong consensus. 

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

No known implementations

Personnel

   The Document Shepherd for this document is Acee Lindem. The Responsible
   Area Director is Gunter Van de Velde.

IANA Note

  Version Changed - Review Needed
  Expert Reviews OK

Protocol Action: 'OSPFv2 Anycast Property Adverti… The IESG