datatracker.ietf.org
Sign in
Version 5.6.4.p1, 2014-10-20
Report a bug

Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence
RFC 6413

Document type: RFC - Informational (November 2011; No errata)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 6413 (Informational)
Responsible AD: Ron Bonica
IESG Note: Al Morton (acmorton@att.com) is the shepherd.
Send notices to: bmwg-chairs@tools.ietf.org

Internet Engineering Task Force (IETF)                       S. Poretsky
Request for Comments: 6413                          Allot Communications
Category: Informational                                        B. Imhoff
ISSN: 2070-1721                                         Juniper Networks
                                                           K. Michielsen
                                                           Cisco Systems
                                                           November 2011

Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence

Abstract

   This document describes the methodology for benchmarking Link-State
   Interior Gateway Protocol (IGP) Route Convergence.  The methodology
   is to be used for benchmarking IGP convergence time through
   externally observable (black-box) data-plane measurements.  The
   methodology can be applied to any link-state IGP, such as IS-IS and
   OSPF.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6413.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Poretsky, et al.              Informational                     [Page 1]
RFC 6413          IGP Convergence Benchmark Methodology    November 2011

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Motivation . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.2.  Factors for IGP Route Convergence Time . . . . . . . . . .  4
     1.3.  Use of Data Plane for IGP Route Convergence
           Benchmarking . . . . . . . . . . . . . . . . . . . . . . .  5
     1.4.  Applicability and Scope  . . . . . . . . . . . . . . . . .  6
   2.  Existing Definitions . . . . . . . . . . . . . . . . . . . . .  6
   3.  Test Topologies  . . . . . . . . . . . . . . . . . . . . . . .  7
     3.1.  Test Topology for Local Changes  . . . . . . . . . . . . .  7
     3.2.  Test Topology for Remote Changes . . . . . . . . . . . . .  8
     3.3.  Test Topology for Local ECMP Changes . . . . . . . . . . . 10
     3.4.  Test Topology for Remote ECMP Changes  . . . . . . . . . . 11
     3.5.  Test topology for Parallel Link Changes  . . . . . . . . . 11
   4.  Convergence Time and Loss of Connectivity Period . . . . . . . 12
     4.1.  Convergence Events without Instant Traffic Loss  . . . . . 13
     4.2.  Loss of Connectivity (LoC) . . . . . . . . . . . . . . . . 16
   5.  Test Considerations  . . . . . . . . . . . . . . . . . . . . . 17
     5.1.  IGP Selection  . . . . . . . . . . . . . . . . . . . . . . 17
     5.2.  Routing Protocol Configuration . . . . . . . . . . . . . . 17
     5.3.  IGP Topology . . . . . . . . . . . . . . . . . . . . . . . 17
     5.4.  Timers . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     5.5.  Interface Types  . . . . . . . . . . . . . . . . . . . . . 18
     5.6.  Offered Load . . . . . . . . . . . . . . . . . . . . . . . 18

[include full document text]