draft-ietf-rtgwg-ordered-fib-03.txt   draft-ietf-rtgwg-ordered-fib-04.txt 
Network Working Group Pierre Francois Network Working Group Pierre Francois
Internet-Draft Olivier Bonaventure Internet-Draft Olivier Bonaventure
Intended status: Experimental Universite catholique de Louvain Intended status: Experimental Universite catholique de Louvain
Expires: September 6, 2010 Mike Shand Expires: April 25, 2011 Mike Shand
Stewart Bryant Stewart Bryant
Stefano Previdi Stefano Previdi
Clarence Filsfils Clarence Filsfils
Cisco Systems Cisco Systems
March 5, 2010 October 22, 2010
Loop-free convergence using oFIB Loop-free convergence using oFIB
draft-ietf-rtgwg-ordered-fib-03 draft-ietf-rtgwg-ordered-fib-04
Abstract Abstract
This draft describes a mechanism for use in conjunction with link This draft describes a mechanism for use in conjunction with link
state routing protocols which prevents the transient loops which state routing protocols which prevents the transient loops which
would otherwise occur during topology changes. It does this by would otherwise occur during topology changes. It does this by
correctly sequencing the FIB updates on the routers. correctly sequencing the FIB updates on the routers.
This mechanism can be used in the case of non-urgent link or node This mechanism can be used in the case of non-urgent link or node
shutdowns and restarts or link metric changes. It can also be used shutdowns and restarts or link metric changes. It can also be used
skipping to change at page 1, line 37 skipping to change at page 1, line 37
where a complete repair path is provided for all affected where a complete repair path is provided for all affected
destinations. destinations.
After a non-urgent topology change, each router computes a rank that After a non-urgent topology change, each router computes a rank that
defines the time at which it can safely update its FIB. A method for defines the time at which it can safely update its FIB. A method for
accelerating this loop-free convergence process by the use of accelerating this loop-free convergence process by the use of
completion messages is also described. completion messages is also described.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on April 25, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 6, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Conventions used in the document . . . . . . . . . . . . . . . 4 1. Conventions used in the document . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. The required FIB update order . . . . . . . . . . . . . . . . 5 3. The required FIB update order . . . . . . . . . . . . . . . . 5
3.1. Single Link Events . . . . . . . . . . . . . . . . . . . . 5 3.1. Single Link Events . . . . . . . . . . . . . . . . . . . . 5
3.1.1. Link Down / Metric Increase . . . . . . . . . . . . . 5 3.1.1. Link Down / Metric Increase . . . . . . . . . . . . . 5
3.1.2. Link Up / Metric Decrease . . . . . . . . . . . . . . 6 3.1.2. Link Up / Metric Decrease . . . . . . . . . . . . . . 6
3.2. Multi-link events . . . . . . . . . . . . . . . . . . . . 7 3.2. Multi-link events . . . . . . . . . . . . . . . . . . . . 7
 End of changes. 7 change blocks. 
15 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/