OSPF Restart Signaling
RFC 4812

Received changes through RFC Editor sync (changed abstract to 'OSPF is a link-state intra-domain routing protocol used in IP networks. Routers find new and detect unreachable neighbors via the Hello subprotocol. Hello OSPF packets are also used to ensure two-way connectivity within time. When a router restarts its OSPF software, it may not know its neighbors. If such a router sends a Hello packet on an interface, its neighbors are going to reset the adjacency, which may not be desirable in certain conditions.

This memo describes a vendor-specific mechanism that allows OSPF routers to inform their neighbors about the restart process. Note that this mechanism requires support from neighboring routers. The mechanism described in this document was proposed before Graceful OSPF Restart, as described in RFC 3623, came into existence. It is implemented/supported by at least one major vendor and is currently deployed in the field. The purpose of this document is to capture the details of this mechanism for public use. This mechanism is not an IETF standard. This memo provides information for the Internet community.')

[Ballot discuss]
My understanding is that draft-nguyen-ospf-restart has been obsoleted by RFC 3623, and thus should be withdrawn. I also understand that 3623 has been implemented by multiple vendors. Given that these are all on a common ballot, and the amount of time that has elaspsed since they were submitted, I would like to know the relationship between them, and whether the OSPF working group has reviewed them, before the others are progressed.