RFC 8333: Micro-loop Prevention by Introducing a Local Convergence Delay
In plain English — editorial summary, not part of the RFC
This document describes a mechanism for link-state routing protocols that prevents local transient forwarding loops in case of link failure. This mechanism proposes a two-step convergence by introducing a delay between the convergence of the node adjacent to the topology change and the network-wide convergence. Because this mechanism delays the IGP convergence, it may only be used for planned maintenance or when Fast Reroute (FRR) protects the traffic during the time between the link failure and the IGP convergence. The mechanism is limited to the link-down event in order to keep the mechanism simple. Simulations using real network topologies have been performed and show that local loops are a significant portion (>50%) of the total forwarding loops.
Document record
- Document ID
- RFC8333
- Published
- March 2018
- Authors
- S. Litkowski; B. Decraene; C. Filsfils; P. Francois
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8330OSPF Traffic Engineering (OSPF-TE) Link Availability Extension for Links with Variable Discrete BandwidthCurrent
February 2018
- RFC 8338Signaling Root-Initiated Point-to-Multipoint Pseudowire Using LDPCurrent
March 2018
- RFC 8339Definition of P2MP PW TLV for Label Switched Path (LSP) Ping MechanismsCurrent
March 2018
- RFC 8345A YANG Data Model for Network TopologiesCurrent
March 2018
- RFC 8320LDP Extensions to Support Maximally Redundant TreesCurrent
February 2018
- RFC 8346A YANG Data Model for Layer 3 TopologiesCurrent
March 2018
- RFC 8347A YANG Data Model for the Virtual Router Redundancy Protocol (VRRP)Current
March 2018
- RFC 8317Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)Current
January 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?