RFC 4689: Terminology for Benchmarking Network-layer Traffic Control Mechanisms
In plain English — editorial summary, not part of the RFC
This document describes terminology for the benchmarking of devices that implement traffic control using packet classification based on defined criteria. The terminology is to be applied to measurements made on the data plane to evaluate IP traffic control mechanisms. Rules for packet classification can be based on any field in the IP header, such as the Differentiated Services Code Point (DSCP), or any field in the packet payload, such as port number. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4689
- Published
- October 2006
- Authors
- S. Poretsky; J. Perser; S. Erramilli; S. Khurana
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 34
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4682Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant DevicesUpdated
December 2006
- RFC 4697Observed DNS Resolution MisbehaviorUpdated
October 2006
- RFC 4706Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2)Current
November 2006
- RFC 4710Real-time Application Quality-of-Service Monitoring (RAQMON) FrameworkCurrent
October 2006
- RFC 4711Real-time Application Quality-of-Service Monitoring (RAQMON) MIBCurrent
October 2006
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 4656A One-way Active Measurement Protocol (OWAMP)Updated
September 2006
- RFC 4641DNSSEC Operational PracticesObsoleted
September 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?