RFC 6413: Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence
In plain English — editorial summary, not part of the RFC
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. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6413
- Published
- November 2011
- Authors
- S. Poretsky; B. Imhoff; K. Michielsen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 42
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5443LDP IGP SynchronizationUpdated
March 2009
- RFC 5073IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node CapabilitiesCurrent
December 2007
- RFC 4561Definition of a Record Route Object (RRO) Node-Id Sub-ObjectCurrent
June 2006
- RFC 4124Protocol Extensions for Support of Diffserv-aware MPLS Traffic EngineeringCurrent
June 2005
- RFC 3785Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) MetricCurrent
May 2004
- RFC 3719Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS)Current
February 2004
- RFC 6412Terminology for Benchmarking Link-State IGP Data-Plane Route ConvergenceCurrent
November 2011
- RFC 6414Benchmarking Terminology for Protection PerformanceCurrent
November 2011
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?