2018
DOI: 10.17487/rfc8333
|View full text |Cite
|
Sign up to set email alerts
|

Micro-loop Prevention by Introducing a Local Convergence Delay

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
3
1
1

Relationship

1
4

Authors

Journals

citations
Cited by 7 publications
(7 citation statements)
references
References 0 publications
0
7
0
Order By: Relevance
“…In general, fast IP failure recovery in the intra-domain unicast setting is a well-understood problem area, with several well-established standards [32], [130], [150], [154], [155], [169], [178], [190], [225], inter-operable implementations in off-the-shelf routers [181]- [183], [231], operational experience [180], [203], and extensive research literature [173], [184] available. Open problems remain, however: even after several iterations it is still not entirely clear how to reliably avoid intermittent micro-loops without slowing down re-convergence [190] and provide the required quality of service even during routing transients [152], [153].…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…In general, fast IP failure recovery in the intra-domain unicast setting is a well-understood problem area, with several well-established standards [32], [130], [150], [154], [155], [169], [178], [190], [225], inter-operable implementations in off-the-shelf routers [181]- [183], [231], operational experience [180], [203], and extensive research literature [173], [184] available. Open problems remain, however: even after several iterations it is still not entirely clear how to reliably avoid intermittent micro-loops without slowing down re-convergence [190] and provide the required quality of service even during routing transients [152], [153].…”
Section: Discussionmentioning
confidence: 99%
“…Correspondingly, various optimization methods are available in the literature to improve failure-case coverage in operational networks [184]- [189]. Third, LFA is prone to forming transient "microloops" during recovery, caused by certain routers still using the "normal" routes while others already switching to the recovery routes [32], [190], and possibly "LFA loops" as well that may show up after all routers have switched. For instance, using a link-protecting LFA to protect a node failure may generate an LFA loop that will persist until the IGP finishes full reconvergence in the background [32], [191], [192].…”
Section: B Shortest-path Fast Reroutementioning
confidence: 99%
“…In general, fast IP failure recovery in the intra-domain unicast setting is a well-understood problem area, with several well-established standards [32], [124], [141], [145], [146], [160], [170], [182], [217], inter-operable implementations in off-the-shelf routers [173]- [175], [223], operational experience [172], [195], and extensive research literature [165], [176] available. Open problems remain, however: even after several iterations it is still not entirely clear how to reliably avoid intermittent micro-loops without slowing down re-convergence [182] and provide the required quality of service even during routing transients [143], [144].…”
Section: Discussionmentioning
confidence: 99%
“…Second, LFA does not guarantee full failure coverage: depending on the topology and link costs LFA can protect about 80% of single link failures . Third, LFA is prone to forming transient "microloops" during recovery, caused by certain routers still using the "normal" routes while others already switching to the recovery routes [32], [182], and possibly "LFA loops" as well that may show up after all routers have switched. For instance, using a link-protecting LFA to protect a node failure may generate an LFA loop that will persist until the IGP finishes full reconvergence in the background [32], [183], [184].…”
Section: B Shortest-path Fast Reroutementioning
confidence: 99%
“…[RFC6976] has not been widely implemented, presumably due to the complexity of the technique. [RFC8333] has been implemented. However, it does not prevent all micro-loops that can occur for a given topology and failure scenario.…”
Section: Specifications Like Is-is ([Rfc1195]mentioning
confidence: 99%