RFC 4098: Terminology for Benchmarking BGP Device Convergence in the Control Plane
In plain English — editorial summary, not part of the RFC
This document establishes terminology to standardize the description of benchmarking methodology for measuring eBGP convergence in the control plane of a single BGP device. Future documents will address iBGP convergence, the initiation of forwarding based on converged control plane information and multiple interacting BGP devices.This terminology is applicable to both IPv4 and IPv6. Illustrative examples of each version are included where relevant. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4098
- Published
- June 2005
- Authors
- H. Berkowitz; E. Davies; S. Hares; P. Krishnaswamy; M. Lepp
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 36
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4264BGP WedgiesCurrent
November 2005
- RFC 4384BGP Communities for Data CollectionCurrent
February 2006
- RFC 4451BGP MULTI_EXIT_DISC (MED) ConsiderationsCurrent
March 2006
- RFC 8212Default External BGP (EBGP) Route Propagation Behavior without PoliciesCurrent
July 2017
- RFC 8327Mitigating the Negative Impact of Maintenance through BGP Session CullingCurrent
March 2018
- RFC 4272BGP Security Vulnerabilities AnalysisCurrent
January 2006
- RFC 4273Definitions of Managed Objects for BGP-4Current
January 2006
- RFC 4274BGP-4 Protocol AnalysisCurrent
January 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?