[rfc-dist] RFC 4689 on Terminology for Benchmarking Network-layer Traffic Control Mechanisms
rfc-editor@rfc-editor.org
rfc-editor at rfc-editor.org
Tue Oct 31 15:38:12 PST 2006
A new Request for Comments is now available in online RFC libraries.
RFC 4689
Title: Terminology for Benchmarking Network-layer Traffic
Control Mechanisms
Author: S. Poretsky, J. Perser,
S. Erramilli, S. Khurana
Status: Informational
Date: October 2006
Mailbox: sporetsky at reefpoint.com,
jerry at perser.org,
shobha at research.telcordia.com,
skhurana at motorola.com
Pages: 34
Characters: 62369
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bmwg-dsmterm-13.txt
URL: http://www.rfc-editor.org/rfc/rfc4689.txt
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.
This document is a product of the Benchmarking Methodology
Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
More information about the rfc-dist
mailing list