2000
DOI: 10.17487/rfc2761
|View full text |Cite
|
Sign up to set email alerts
|

Terminology for ATM Benchmarking

Abstract: 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. The terms defined in this memo will be used in addition to terms defined in RFCs 1242, 2285, and 2544. This memo is a product of the Benchmarking Methodology Working Group (BMWG) of the Internet Engineering Task Force (IETF). This memo contains two major sections: Background and Definitions. Within the definitions section… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2002
2002
2009
2009

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(4 citation statements)
references
References 0 publications
0
4
0
Order By: Relevance
“…The Benchmarking Methodologies Working Group (BMWG) of the IETF has defined a coherent and reproducible benchmarking terminology and methodology in a series of requests for comments (RFCs). In particular, RFCs 2761 [2], 3116 [3], and 3133 [4] are relevant to IP QOS benchmarking. RFC 2761 and RFC 3133 define the terms and performance metrics associated with benchmarking tests for IP over ATM and IP over FR.…”
Section: Benchmarking Methodologiesmentioning
confidence: 99%
“…The Benchmarking Methodologies Working Group (BMWG) of the IETF has defined a coherent and reproducible benchmarking terminology and methodology in a series of requests for comments (RFCs). In particular, RFCs 2761 [2], 3116 [3], and 3133 [4] are relevant to IP QOS benchmarking. RFC 2761 and RFC 3133 define the terms and performance metrics associated with benchmarking tests for IP over ATM and IP over FR.…”
Section: Benchmarking Methodologiesmentioning
confidence: 99%
“…The next phase of the PSAX in-house automation addresses these issues by unifying the MOT and SUT test automation pilots under a common interface [3][4][5][6]. When the SUT is configured, database entries will be created and used by the MOT.…”
Section: Test Realization Specificsmentioning
confidence: 99%
“…The encryption and decryption key setup latencies are particularly important in applications where only several blocks of data are encrypted between two consecutive key changes. IPSec (Kent and Atkinson, 1998a;Kent and Atkinson, 1998b;Kent and Atkinson, 1998c) and ATM (Dunn and Martin, 2000), with small sizes of packets, and consecutive packets encrypted using different keys, are two widespread protocols in which the key setup latencies may play a very important role (Gaj and Chodowiec, 1999).…”
Section: Introductionmentioning
confidence: 99%