RFC 5695: MPLS Forwarding Benchmarking Methodology for IP Flows
In plain English — editorial summary, not part of the RFC
This document describes a methodology specific to the benchmarking of Multiprotocol Label Switching (MPLS) forwarding devices, limited to the most common MPLS packet forwarding scenarios and delay measurements for each, considering IP flows. It builds upon the tenets set forth in RFC 2544, RFC 1242, and other IETF Benchmarking Methodology Working Group (BMWG) efforts. This document seeks to extend these efforts to the MPLS paradigm. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5695
- Published
- November 2009
- Authors
- A. Akhter; R. Asati; C. Pignataro
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5710PathErr Message Triggered MPLS and GMPLS LSP ReroutesCurrent
January 2010
- RFC 5712MPLS Traffic Engineering Soft PreemptionCurrent
January 2010
- RFC 5671Applicability of the Path Computation Element (PCE) to Point-to-Multipoint (P2MP) MPLS and GMPLS Traffic Engineering (TE)Current
October 2009
- RFC 5884Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)Updated
June 2010
- RFC 5921A Framework for MPLS in Transport NetworksUpdated
July 2010
- RFC 5439An Analysis of Scaling Issues in MPLS-TE Core NetworksCurrent
February 2009
- RFC 5420Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)Updated
February 2009
- RFC 5392OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic EngineeringCurrent
January 2009
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?