Browse Prior Art Database

Basic BGP Convergence Benchmarking Methodology for Data-Plane Convergence (RFC7747) Disclosure Number: IPCOM000245865D
Original Publication Date: 2016-Apr-01
Included in the Prior Art Database: 2016-Apr-14
Document File: 70 page(s) / 66K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Papneja: AUTHOR [+5]


This document defines the methodology for benchmarking data-plane Forwarding Information Base (FIB) convergence performance of BGP in routers and switches using topologies of three or four nodes. The methodology proposed in this document applies to both IPv4 and IPv6, and if a particular test is unique to one version, it is marked accordingly. For IPv6 benchmarking, the Device Under Test (DUT) will require the support of Multiprotocol BGP (MP-BGP) [RFC4760] [RFC2545]. Similarly, both Internal BGP (iBGP) and External BGP (eBGP) are covered in the tests as applicable.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Internet Engineering Task Force (IETF)                        R. Papneja Request for Comments: 7747                           Huawei Technologies Category: Informational                                        B. Parise ISSN: 2070-1721                                          Skyport Systems                                                                 S. Hares                                                      Huawei Technologies                                                                   D. Lee                                                                     IXIA                                                            I. Varlashkin                                                                   Google                                                               April 2016

              Basic BGP Convergence Benchmarking Methodology                        for Data-Plane Convergence


   BGP is widely deployed and used by several service providers as the    default inter-AS (Autonomous System) routing protocol.  It is of    utmost importance to ensure that when a BGP peer or a downstream link    of a BGP peer fails, the alternate paths are rapidly used and routes    via these alternate paths are installed.  This document provides the    basic BGP benchmarking methodology using existing BGP convergence    terminology as defined in RFC 4098.

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

 Papneja, et al.               Informational                     [Page 1]
 RFC 7747               BGP Convergence Methodology            April 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust an...