Skip to main content

A Framework for Loop-Free Convergence
RFC 5715

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'A micro-loop is a packet forwarding loop that may occur transiently among two or more routers …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-10-14
(System) Notify list changed from rtgwg-chairs@ietf.org, draft-ietf-rtgwg-lf-conv-frmwk@ietf.org to (None)
2010-10-27
(System) Posted related IPR disclosure: Cisco's Statement of IPR related to RFC 5715
2010-01-19
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2010-01-19
Cindy Morgan [Note]: 'RFC 5715' added by Cindy Morgan
2010-01-14
(System) RFC published