RFC 8379: OSPF Graceful Link Shutdown

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…

Read RFC 8379 on the RFC Editor

Outgoing relationships (15 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2328: OSPF Version 2
Normative reference — RFC 5340: OSPF for IPv6
Normative reference — RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2
Normative reference — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Normative reference — RFC 5329: Traffic Engineering Extensions to OSPF Version 3
Normative reference — RFC 7684: OSPFv2 Prefix/Link Attribute Advertisement
Normative reference — RFC 6845: OSPF Hybrid Broadcast and Point-to-Multipoint Interface Type
Normative reference — RFC 5817: Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks
Normative reference — RFC 6987: OSPF Stub Router Advertisement
Normative reference — RFC 8042: OSPF Two-Part Metric
Informative reference — RFC 4203: OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Informative reference — RFC 4552: Authentication/Confidentiality for OSPFv3
Informative reference — RFC 4915: Multi-Topology (MT) Routing in OSPF
Informative reference — RFC 4577: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)

Incoming relationships (1 related RFC)

Normatively referenced by — RFC 8510: OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID Advertisement