RFC 6414: Benchmarking Terminology for Protection Performance
In plain English — editorial summary, not part of the RFC
This document provides common terminology and metrics for benchmarking the performance of sub-IP layer protection mechanisms. The performance benchmarks are measured at the IP layer; protection may be provided at the sub-IP layer. The benchmarks and terminology can be applied in methodology documents for different sub-IP layer protection mechanisms such as Automatic Protection Switching (APS), Virtual Router Redundancy Protocol (VRRP), Stateful High Availability (HA), and Multiprotocol Label Switching Fast Reroute (MPLS-FRR). This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6414
- Published
- November 2011
- Authors
- S. Poretsky; R. Papneja; J. Karthik; S. Vapiwala
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 33
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6413Benchmarking Methodology for Link-State IGP Data-Plane Route ConvergenceCurrent
November 2011
- RFC 6412Terminology for Benchmarking Link-State IGP Data-Plane Route ConvergenceCurrent
November 2011
- RFC 6408Diameter Straightforward-Naming Authority Pointer (S-NAPTR) UsageCurrent
November 2011
- RFC 6397Multi-Threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) Routing Information Export Format with Geo-Location ExtensionsCurrent
October 2011
- RFC 6396Multi-Threaded Routing Toolkit (MRT) Routing Information Export FormatCurrent
October 2011
- RFC 6390Guidelines for Considering New Performance Metric DevelopmentCurrent
October 2011
- RFC 6441Time to Remove Filters for Previously Unallocated IPv4 /8sCurrent
November 2011
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 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?