A Framework for Loop-Free Convergence
RFC 5715, “A Framework for Loop-Free Convergence”, is an Informational document published in January 2010 by M. Shand, S. Bryant. The canonical text is published by the RFC Editor.
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.
This framework provides a summary of the causes and consequences of micro-loops and enables the reader to form a judgement on whether micro-looping is an issue that needs to be addressed in specific networks. It also provides a survey of the currently proposed mechanisms that may be used to prevent or to suppress the formation of micro-loops when an IP or MPLS network undergoes topology change due to failure, repair, or management action. When sufficiently fast convergence is not available and the topology is susceptible to micro-loops, use of one or more of these mechanisms may be desirable. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5715 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5714 IP Fast Reroute Framework
- RFC 5716 Requirements for Federated File Systems
- RFC 5713 Security Threats and Security Requirements for the Access Node Control Protocol
- RFC 5712 MPLS Traffic Engineering Soft Preemption
- RFC 5718 An In-Band Data Communication Network For the MPLS Transport Profile
- RFC 5711 Node Behavior upon Originating and Receiving Resource Reservation Protocol Path Error Messages
- RFC 5719 Updated IANA Considerations for Diameter Command Code Allocations
- RFC 5710 PathErr Message Triggered MPLS and GMPLS LSP Reroutes