Link State protocols SPF trigger and delay algorithm impact on IGP microloops
draft-litkowski-rtgwg-spf-uloop-pb-statement-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Stephane Litkowski | ||
Last updated | 2015-03-06 | ||
Replaced by | RFC 8541 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Reviews |
RTGDIR Early review
Has Issues
|
||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-rtgwg-spf-uloop-pb-statement | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
A micro-loop is a packet forwarding loop that may occur transiently among two or more routers in a hop-by-hop packet forwarding paradigm. In this document, we are trying to analyze the impact of using different Link State IGP implementations in a single network in regards of microloops. The analysis is focused on the SPF triggers and SPF delay algorithm.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)