This draft is a result of a discussion we had among a few folks (Alia, Don,
Mike, Stewart, et al).
My goal with this document was to try and analyze formation of microloops,
plus identify the scenarios where they will not form, and categorize scenarios
where they normally will.
The next goal was to see if we can do something in the scenarios where
microloops normally form. I didn't try to get 100% coverage though (it's likely
to require tunnels).
Hopefully this should help the discussion on the list.
This is a forwarded message
From: [email protected] <[email protected]>
To: [email protected]
Date: Friday, October 8, 2004, 12:37:39 PM
Subject: I-D ACTION:draft-zinin-microloop-analysis-00.txt
===8<==============Original message text===============
A New Internet-Draft is available from the on-line Internet-Drafts directories.
Title : Analysis and Minimization of Microloops in Link-state
Author(s) : A. Zinin
Filename : draft-zinin-microloop-analysis-00.txt
Pages : 10
Date : 2004-10-8
Link-state routing protocols (e.g. OSPF or IS-IS) are known to
converge to a loop-free state within a finite period of time after a
failure. It is normal, however, to observe short-term loops during
the period of failure propagation, route recalculation, and
forwarding table update, due to the asynchronous nature of link-state
protocol operation. This document provides an analysis of formation
of such microloops and suggests simple mechanisms to minimize them.
A URL for this Internet-Draft is:
To remove yourself from the I-D Announcement list, send a message to
[email protected] with the word unsubscribe in the body of the
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
A list of Internet-Drafts directories can be found in
Internet-Drafts can also be obtained by e-mail.
Send a message to:
In the body type:
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
===8<===========End of original message text===========
<<< MESSAGE/EXTERNAL-BODY; name="1.msg": Unrecognized >>>
<<< MESSAGE/EXTERNAL-BODY; name="draft-zinin-microloop-analysis-00.txt": Unrecognized >>>
Description: Text document
Rtgwg mailing list