[rfc-dist] RFC 8379 on OSPF Graceful Link Shutdown

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri May 11 17:21:07 PDT 2018

A new Request for Comments is now available in online RFC libraries.

        RFC 8379

        Title:      OSPF Graceful Link Shutdown 
        Author:     S. Hegde,
                    P. Sarkar,
                    H. Gredler,
                    M. Nanduri,
                    L. Jalil
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2018
        Mailbox:    shraddha at juniper.net, 
                    pushpasis.ietf at gmail.com, 
                    hannes at rtbrick.com,
                    mnanduri at ebay.com, 
                    luay.jalil at verizon.com
        Pages:      17
        Characters: 37671
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-link-overload-16.txt

        URL:        https://www.rfc-editor.org/info/rfc8379

        DOI:        10.17487/RFC8379

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

This document describes the protocol extensions to disseminate
graceful-link-shutdown information in OSPFv2 and OSPFv3.

This document is a product of the Open Shortest Path First IGP Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

More information about the rfc-dist mailing list