[rfc-dist] RFC 4883 on Benchmarking Terminology for Resource Reservation Capable Routers
rfc-editor at rfc-editor.org
Wed Jul 25 09:01:07 PDT 2007
A new Request for Comments is now available in online RFC libraries.
Title: Benchmarking Terminology for Resource Reservation
Author: G. Feher, K. Nemeth,
A. Korn, I. Cselenyi
Date: July 2007
Mailbox: Gabor.Feher at tmit.bme.hu,
Krisztian.Nemeth at tmit.bme.hu,
Andras.Korn at tmit.bme.hu,
Istvan.Cselenyi at teliasonera.com
I-D Tag: draft-ietf-bmwg-benchres-term-08.txt
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.
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
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
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.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist