Microloop prevention by introducing a local convergence delay
draft-litkowski-rtgwg-uloop-delay-04
| Document | Type | Replaced Internet-Draft (rtgwg WG) | |
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaced by | RFC 8333 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-rtgwg-uloop-delay | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-litkowski-rtgwg-uloop-delay-04.txt
Abstract
This document describes a mechanism for link-state routing protocols to prevent local transient forwarding loops in case of link failure. This mechanism Proposes a two-steps convergence by introducing a delay between the convergence of the node adjacent to the topology change and the network wide convergence. As this mechanism delays the IGP convergence it may only be used for planned maintenance or when fast reroute protects the traffic between the link failure and the IGP convergence. Simulations using real network topologies have been performed and show that local loops are a significant portion (>50%) of the total forwarding loops.
Authors
Stephane Litkowski
(stephane.litkowski@orange.com)
Bruno Decraene
(bruno.decraene@orange.com)
Clarence Filsfils
(cfilsfil@cisco.com)
Pierre Francois
(pierre.francois@imdea.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)