Skip to main content

OSPF Graceful Link Shutdown
RFC 8379

Revision differences

Document history

Date By Action
2018-12-19
(System)
Received changes through RFC Editor sync (changed abstract to 'When a link is being prepared to be taken out of service, the traffic needs to …
Received changes through RFC Editor sync (changed abstract to 'When a link is being prepared to be taken out of service, the traffic needs to be diverted from both ends of the link. Increasing the metric to the highest value on one side of the link is not sufficient to divert the traffic flowing in the other direction.

It is useful for the routers in an OSPFv2 or OSPFv3 routing domain to be able to advertise a link as being in a graceful-shutdown state to indicate impending maintenance activity on the link. This information can be used by the network devices to reroute the traffic effectively.

This document describes the protocol extensions to disseminate graceful-link-shutdown information in OSPFv2 and OSPFv3.')
2018-11-27
Alvaro Retana Downref to RFC 6987 approved by Last Call for rfc8379-16
2018-05-11
(System)
Received changes through RFC Editor sync (created alias RFC 8379, changed title to 'OSPF Graceful Link Shutdown', changed abstract to 'When a link is …
Received changes through RFC Editor sync (created alias RFC 8379, changed title to 'OSPF Graceful Link Shutdown', changed abstract to 'When a link is being prepared to be taken out of service, the traffic needs to be diverted from both ends of the link. Increasing the metric to the highest value on one side of the link is not sufficient to divert the traffic flowing in the other direction.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-05-11, changed IESG state to RFC Published)
2018-05-11
(System) RFC published