Internet DRAFT - draft-ietf-bmwg-atm-term-abr
draft-ietf-bmwg-atm-term-abr
A new Request for Comments is now available in online RFC libraries.
RFC 3134
Title: Terminology for ATM ABR Benchmarking
Author(s): J. Dunn, C. Martin
Status: Informational
Date: June 2001
Mailbox: Jeffrey.Dunn@worldnet.att.net,
Cynthia.E.Martin@worldnet.att.net
Pages: 16
Characters: 29542
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bmwg-atm-term-abr-03.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3134.txt
This memo discusses and defines terms associated with performance
benchmarking tests and the results of these tests in the context of
Asynchronous Transfer Mode (ATM) based switching devices supporting
ABR (Available Bit Rate). The terms defined in this memo will be used
in addition to terms defined in RFCs 1242, 2285, and 2544 and 2761.
This memo is a product of the Benchmarking Methodology Working Group
(BMWG) of the Internet Engineering Task Force (IETF).
This document is a product of the Benchmarking Methodology Working
Group of the IETF.
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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@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@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.