RFC 4883: Benchmarking Terminology for Resource Reservation Capable Routers
In plain English — editorial summary, not part of the RFC
The primary purpose of this document is to define terminology specific to the benchmarking of resource reservation signaling of Integrated Services (IntServ) IP routers. These terms can be used in additional documents that define benchmarking methodologies for routers that support resource reservation or reporting formats for the benchmarking measurements. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4883
- Published
- July 2007
- Authors
- G. Feher; K. Nemeth; A. Korn; I. Cselenyi
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4923Quality of Service (QoS) Signaling in a Nested Virtual Private NetworkCurrent
August 2007
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 2212Specification of Guaranteed Quality of ServiceCurrent
September 1997
- RFC 2211Specification of the Controlled-Load Network Element ServiceCurrent
September 1997
- RFC 4878Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like InterfacesCurrent
June 2007
- RFC 4890Recommendations for Filtering ICMPv6 Messages in FirewallsCurrent
May 2007
- RFC 4891Using IPsec to Secure IPv6-in-IPv4 TunnelsCurrent
May 2007
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?