Terminology for Benchmarking Network-layer Traffic Control Mechanisms
RFC 4689
|
| Document |
Type |
|
RFC - Informational
(October 2006; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 4689 (Informational)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
David Kessens
|
|
Send notices to |
|
(None)
|
Network Working Group S. Poretsky
Request for Comments: 4689 Reef Point Systems
Category: Informational J. Perser
Veriwave
S. Erramilli
Telcordia
S. Khurana
Motorola
October 2006
Terminology for Benchmarking Network-layer Traffic Control Mechanisms
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
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.
Poretsky, et al. Informational [Page 1]
RFC 4689 Terminology for Traffic Control Mechanisms October 2006
Table of Contents
1. Introduction ....................................................2
2. Existing Definitions ............................................3
3. Term Definitions ................................................4
3.1. Configuration Terms ........................................4
3.1.1. Classification ......................................4
3.1.2. Codepoint Set .......................................4
3.1.3. Forwarding Congestion ...............................5
3.1.4. Congestion Management ...............................6
3.1.5. Flow ................................................7
3.2. Measurement Terms ..........................................7
3.2.1. Forwarding Capacity .................................7
3.2.2. Conforming Packet ...................................8
3.2.3. Nonconforming Packet ................................9
3.2.4. Forwarding Delay ....................................9
3.2.5. Jitter .............................................11
3.2.6. Undifferentiated Response ..........................11
3.3. Sequence Tracking .........................................12
3.3.1. Test Sequence Number ...............................12
3.3.2. Stream .............................................12
3.3.3. In-Sequence Packet .................................13
3.3.4. Out-of-Order Packet ................................14
3.3.5. Duplicate Packet ...................................14
3.4. Vectors ...................................................15
3.4.1. Intended Vector ....................................15
3.4.2. Offered Vector .....................................16
3.4.3. Expected Vectors ...................................16
3.4.4. Output Vectors .....................................23
4. Security Considerations ........................................30
5. Acknowledgements ...............................................30
6. References .....................................................31
6.1. Normative References ......................................31
6.2. Informative References ....................................31
1. Introduction
New terminology is needed because most existing measurements assume
the absence of congestion and only a single per-hop behavior. This
document introduces several new terms that will allow measurements to
be taken during periods of congestion.
Another key difference from existing terminology is the definition of
measurements as observed on egress and ingress of a device/system
under test. Again, the existence of congestion requires the addition
of egress measurements, as well as of those taken on ingress; without
observing traffic leaving a device/system, it is not possible to say
whether traffic-control mechanisms effectively dealt with congestion.
Poretsky, et al. Informational [Page 2]
RFC 4689 Terminology for Traffic Control Mechanisms October 2006
Show full document text