BGP RR Benchmarking Methodology
draft-lasserre-bgp-rr-benchmark-method-01

Document Type Expired Internet-Draft (individual)
Last updated 2017-03-27 (latest revision 2016-09-20)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-lasserre-bgp-rr-benchmark-method-01.txt

Abstract

BGP is commonly used with network operators in order to distribute routing information for both infrastructure routes as well as service routing information. BGP is used due to its ability to handle high amounts of prefixes and paths information coupled with administrative attributes, such as communities, in a reliable and scalable manner. A route-reflector is a key network component of BGP as it propose an alternative to internal border gateway protocol (iBGP) fully-meshed peering requirement. By acting as a concentration point it learns, process, and reflect prefixes from and to all its iBGP Peers also referred as route-reflector clients, and is a key element of such networks performances. As today networks grow in terms of size and offered services, this translates into more prefixes to be handled by BGP Route-Reflectors, and there is a demand by service providers to be able to benchmark this key function in a realistic and consistent manner. This document covers how to provide an accurate BGP route-reflector benchmark.

Authors

Gregory Lasserre (gregory.lasserre@nokia.com)
James Cumming (james.cumming@nokia.com)
Carsten Rossenhoevel (cross@eantc.de)
Guillaume Gaulon (guillaume.gaulon@orange.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)