RFC 3918: Methodology for IP Multicast Benchmarking
In plain English — editorial summary, not part of the RFC
The purpose of this document is to describe methodology specific to the benchmarking of multicast IP forwarding devices. It builds upon the tenets set forth in RFC 2544, RFC 2432 and other IETF Benchmarking Methodology Working Group (BMWG) efforts. This document seeks to extend these efforts to the multicast paradigm. The BMWG produces two major classes of documents: Benchmarking Terminology documents and Benchmarking Methodology documents. The Terminology documents present the benchmarks and other related terms. The Methodology documents define the procedures required to collect the benchmarks cited in the corresponding Terminology documents. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3918
- Published
- October 2004
- Authors
- D. Stopp; B. Hickman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 31
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3917Requirements for IP Flow Information Export (IPFIX)Current
October 2004
- RFC 3919Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS)Current
October 2004
- RFC 3904Evaluation of IPv6 Transition Mechanisms for Unmanaged NetworksCurrent
September 2004
- RFC 3901DNS IPv6 Transport Operational GuidelinesObsoleted
September 2004
- RFC 3896Definitions of Managed Objects for the DS3/E3 Interface TypeCurrent
September 2004
- RFC 3895Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface TypesObsoleted
September 2004
- RFC 3955Evaluation of Candidate Protocols for IP Flow Information Export (IPFIX)Current
October 2004
- RFC 3956Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast AddressUpdated
November 2004
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?