OSPF Link Overload

Document Type Replaced Internet-Draft (individual)
Authors Shraddha Hegde  , Hannes Gredler  , Mohan Nanduri  , Luay Jalil 
Last updated 2015-07-19
Replaced by RFC 8379
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ospf-link-overload
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Many OSPFv2 or OSPFv3 deployments run on overlay networks provisioned by means of pseudo-wires or L2-circuits. when the devices in the underlying network go for maintenance, it is useful to divert the traffic away from the node before the maintenance is actually scheduled. Since the nodes in the underlying network are not visible to OSPF, existing stub router mechanism described in [RFC3137] cannot be used. It is useful for routers in OSPFv2 or OSPFv3 routing domain to be able to advertise a link being in overload state to indicate impending maintenance activity in the underlying network devices. This document describes the protocol extensions to disseminate link overload information in OSPFv2 and OSPFv3 protocol.


Shraddha Hegde (shraddha@juniper.net)
Hannes Gredler (hannes@juniper.net)
Mohan Nanduri (mnanduri@microsoft.com)
Luay Jalil (luay.jalil@verizon.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)