[rfc-dist] RFC 6976 on Framework for Loop-Free Convergence Using the Ordered Forwarding Information Base (oFIB) Approach

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Tue Jul 30 07:11:19 PDT 2013

A new Request for Comments is now available in online RFC libraries.

        RFC 6976

        Title:      Framework for Loop-Free Convergence Using 
                    the Ordered Forwarding Information Base (oFIB) 
        Author:     M. Shand, S. Bryant,
                    S. Previdi, C. Filsfils,
                    P. Francois, O. Bonaventure
        Status:     Informational
        Stream:     IETF
        Date:       July 2013
        Mailbox:    imc.shand at googlemail.com, 
                    stbryant at cisco.com, 
                    sprevidi at cisco.com,
                    cfilsfil at cisco.com, 
                    pierre.francois at imdea.org,  
                    Olivier.Bonaventure at uclouvain.be
        Pages:      28
        Characters: 61011
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-ordered-fib-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6976.txt

This document describes an illustrative framework of a mechanism for
use in conjunction with link-state routing protocols that prevents
the transient loops that would otherwise occur during topology
changes.  It does this by correctly sequencing the forwarding
information base (FIB) updates on the routers.

This mechanism can be used in the case of non-urgent (management
action) link or node shutdowns and restarts or link metric changes.
It can also be used in conjunction with a fast reroute mechanism that
converts a sudden link or node failure into a non-urgent topology
change.  This is possible where a complete repair path is provided
for all affected destinations.

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
accelerating this loop-free convergence process by the use of
completion messages is also described.

The technology described in this document has been subject to
extensive simulation using pathological convergence behavior and real
network topologies and costs.  However, the mechanisms described in
this document are purely illustrative of the general approach and do
not constitute a protocol specification.  This document represents a
snapshot of the work of the Routing Area Working Group at the time of
publication and is published as a document of record.  Further work
is needed before implementation or deployment.

This document is a product of the Routing Area Working Group Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

More information about the rfc-dist mailing list