OSPF Link Overload
draft-ietf-ospf-link-overload-02

The information below is for an old version of the document
Document Type Expired Internet-Draft (ospf WG)
Authors Shraddha Hegde  , Pushpasis Sarkar  , Hannes Gredler  , Mohan Nanduri  , Luay Jalil 
Last updated 2017-01-08 (latest revision 2016-07-07)
Replaces draft-hegde-ospf-link-overload
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Reviews
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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
https://www.ietf.org/archive/id/draft-ietf-ospf-link-overload-02.txt

Abstract

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 metric on one side of the link is not sufficient to divert the traffic flowing in the other direction. It is useful for routers in an OSPFv2 or OSPFv3 routing domain to be able to advertise a link being in an overload state to indicate impending maintenance activity on the link. This information can be used by the network devices to re-route the traffic effectively. This document describes the protocol extensions to disseminate link overload information in OSPFv2 and OSPFv3.

Authors

Shraddha Hegde (shraddha@juniper.net)
Pushpasis Sarkar (pushpasis.ietf@gmail.com)
Hannes Gredler (hannes@gredler.at)
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.)