RFC 5715: A Framework for Loop-Free Convergence
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5715
- Published
- January 2010
- Authors
- M. Shand; S. Bryant
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5714IP Fast Reroute FrameworkCurrent
January 2010
- RFC 6571Loop-Free Alternate (LFA) Applicability in Service Provider (SP) NetworksCurrent
June 2012
- RFC 6981A Framework for IP and MPLS Fast Reroute Using Not-Via AddressesCurrent
August 2013
- RFC 5712MPLS Traffic Engineering Soft PreemptionCurrent
January 2010
- RFC 5718An In-Band Data Communication Network For the MPLS Transport ProfileCurrent
January 2010
- RFC 5711Node Behavior upon Originating and Receiving Resource Reservation Protocol (RSVP) Path Error MessagesCurrent
January 2010
- RFC 5710PathErr Message Triggered MPLS and GMPLS LSP ReroutesCurrent
January 2010
- RFC 5709OSPFv2 HMAC-SHA Cryptographic AuthenticationUpdated
October 2009
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?