draft-ietf-bmwg-conterm-02.txt   draft-ietf-bmwg-conterm-03.txt 
Benchmarking Working Group H.Berkowitz, Gett Communications Benchmarking Working Group H.Berkowitz, Gett Communications
Internet Draft S.Hares, Nexthop Internet Draft S.Hares, Nexthop
Document: draft-ietf-bmwg-conterm-02.txt A.Retana, Cisco Document: draft-ietf-bmwg-conterm-03.txt A.Retana, Cisco
Expires December 2002 P.Krishnaswamy, Consultant Expires January 2003 P.Krishnaswamy, Consultant
M.Lepp, Juniper Networks M.Lepp, Juniper Networks
E.Davies, Nortel Networks E.Davies, Nortel Networks
June 2002 July 2002
Terminology for Benchmarking BGP Device Convergence Terminology for Benchmarking BGP Device Convergence
in the Control Plane in the Control Plane
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1]. all provisions of Section 10 of RFC2026 [1].
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 other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
A revised version of this draft document will be submitted to the RFC A revised version of this draft document will be submitted to the RFC
editor as a Informational document for the Internet Community. editor as a Informational document for the Internet Community.
Discussion and suggestions for improvement are requested. Discussion and suggestions for improvement are requested.
This document will expire before December 2002. Distribution of this This document will expire before January 2003 . Distribution of this
draft is unlimited. draft is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
This draft establishes terminology to standardize the description of This draft establishes terminology to standardize the description of
benchmarking methodology for measuring eBGP convergence in the benchmarking methodology for measuring eBGP convergence in the
skipping to change at page 15, line 44 skipping to change at page 15, line 44
Definition: Definition:
(Paraphrased from 1771[1]) The MRAI timer determines the (Paraphrased from 1771[1]) The MRAI timer determines the
minimum time between advertisements of routes to a minimum time between advertisements of routes to a
particular destination (prefix) from a single BGP device. particular destination (prefix) from a single BGP device.
The timer is applied on a pre-prefix basis, although the The timer is applied on a pre-prefix basis, although the
timer is set on a per BGP device basis. timer is set on a per BGP device basis.
Discussion: Discussion:
Given that a BGP instance may manage in excess of 100,000 Given that a BGP instance may manage in excess of 100,000
routes, RFC 1771 allows for a degree of optimization in routes, RFC 1771 allows for a degree of optimization in
order to limit the number of timers needed. The NRAI does order to limit the number of timers needed. The MRAI does
not apply to routes received from BGP speakers in the same not apply to routes received from BGP speakers in the same
AS or to explicit withdrawals. AS or to explicit withdrawals.
RFC 1771 also recommends that random jitter is applied to RFC 1771 also recommends that random jitter is applied to
MRAI in an attempt to avoid synchronization effects MRAI in an attempt to avoid synchronization effects
between the BGP instances in a network. between the BGP instances in a network.
In this document we define RIB convergence by measuring In this document we define RIB convergence by measuring
the time an NRAI is advertised to the DUT to the time it the time an NLRI is advertised to the DUT to the time it
is advertised from the DUT. Clearly any delay inserted by is advertised from the DUT. Clearly any delay inserted by
the MRAI will have a significant effect on this the MRAI will have a significant effect on this
measurement. measurement.
Measurement Units: seconds. Measurement Units: seconds.
Issues: Issues:
See Also: NLRI, BGP route See Also: NLRI, BGP route
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/