draft-ietf-bmwg-acc-bench-meth-07.txt   draft-ietf-bmwg-acc-bench-meth-08.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: September 2007 Expires in: January 2008
Intended Status: Informational Intended Status: Informational
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
Shankar Rao Shankar Rao
Qwest Communications Qwest Communications
Methodology Guidelines for Methodology Guidelines for
Accelerated Stress Benchmarking Accelerated Stress Benchmarking
<draft-ietf-bmwg-acc-bench-meth-07.txt> <draft-ietf-bmwg-acc-bench-meth-08.txt>
Intellectual Property Rights (IPR) statement: Intellectual Property Rights (IPR) statement:
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Status of this Memo Status of this Memo
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 47 skipping to change at page 1, line 47
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
ABSTRACT ABSTRACT
Routers in an operational network are configured with multiple Routers in an operational network are configured with multiple
protocols and security policies while simultaneously forwarding protocols and security policies while simultaneously forwarding
traffic and being managed. To accurately benchmark a router for traffic and being managed. To accurately benchmark a router for
deployment it is necessary to test the router under accelerated deployment it is necessary to test the router in a lab environment
operational conditions, which is known as Stress Testing. This under accelerated conditions, which is known as Stress Testing.
document provides the Methodology Guidelines for performing This document provides the Methodology Guidelines for performing
Accelerated Stress Benchmarking of networking devices. Accelerated Stress Benchmarking of networking devices.
Descriptions of Test Topology, Benchmarks and Reporting Format The methodology is to be used with the companion terminology
are provided in addition to procedures for conducting various document [4]. These guidelines can be used as the basis for
test cases. The methodology is to be used with the companion additional methodology documents that benchmark stress conditions
terminology document [4]. These guidelines can be used as the for specific network technologies.
for Accelerated Stress Benchmarking
basis for additional methodology documents that benchmark for Accelerated Stress Benchmarking
stress conditions for specific network technologies.
Table of Contents Table of Contents
1. Introduction ............................................... 2 1. Introduction ............................................... 2
2. Existing definitions ....................................... 3 2. Existing definitions ....................................... 3
3. Test Setup.................................................. 3 3. Test Setup.................................................. 3
3.1 Test Topologies............................................ 3 3.1 Test Topologies............................................ 3
3.2 Test Considerations........................................ 3 3.2 Test Considerations........................................ 3
3.3 Reporting Format........................................... 4 3.3 Reporting Format........................................... 4
3.3.1 Configuration Sets....................................... 5 3.3.1 Configuration Sets....................................... 5
3.3.2 Startup Conditions....................................... 6 3.3.2 Startup Conditions....................................... 6
skipping to change at page 11, line 33 skipping to change at page 11, line 33
[1] Bradner, S., Editor, "Benchmarking Terminology for Network [1] Bradner, S., Editor, "Benchmarking Terminology for Network
Interconnection Devices", RFC 1242, October 1991. Interconnection Devices", RFC 1242, October 1991.
[2] Mandeville, R., "Benchmarking Terminology for LAN Switching [2] Mandeville, R., "Benchmarking Terminology for LAN Switching
Devices", RFC 2285, October 1998. Devices", RFC 2285, October 1998.
[3] Bradner, S. and McQuaid, J., "Benchmarking Methodology for [3] Bradner, S. and McQuaid, J., "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, March 1999. Network Interconnect Devices", RFC 2544, March 1999.
[4] Poretsky, S. and Rao, S., "Terminology for Accelerated [4] Poretsky, S. and Rao, S., "Terminology for Accelerated
Stress Benchmarking", draft-ietf-bmwg-acc-bench-term-11, Stress Benchmarking", draft-ietf-bmwg-acc-bench-term-12,
work in progress, March 2007. work in progress, July 2007.
[5] Bradner, S., "Key words for use in RFCs to Indicate [5] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
8. Informative References 8. Informative References
[RFC3871] RFC 3871 "Operational Security Requirements for Large [RFC3871] RFC 3871 "Operational Security Requirements for Large
Internet Service Provider (ISP) IP Network Infrastructure. Internet Service Provider (ISP) IP Network Infrastructure.
G. Jones, Ed.. IETF, September 2004. G. Jones, Ed.. IETF, September 2004.
[NANOG25] "Core Router Evaluation for Higher Availability", [NANOG25] "Core Router Evaluation for Higher Availability",
Scott Poretsky, NANOG 25, October 8, 2002, Toronto, CA. Scott Poretsky, NANOG 25, October 8, 2002, Toronto, CA.
[IEEECQR] "Router Stress Testing to Validate Readiness for [IEEECQR] "Router Stress Testing to Validate Readiness for
Network Deployment", Scott Poretsky, IEEE CQR 2003. Network Deployment", Scott Poretsky, IEEE CQR 2003.
[CONVMETH] Poretsky, S., "Benchmarking Methodology for IGP Data [CONVMETH] Poretsky, S., "Benchmarking Methodology for IGP Data
Plane Route Convergence", Plane Route Convergence",
draft-ietf-bmwg-igp-dataplane-conv-meth-11, work in draft-ietf-bmwg-igp-dataplane-conv-meth-13, work in
progress, March 2007. progress, July 2007.
for Accelerated Stress Benchmarking for Accelerated Stress Benchmarking
9. Author's Address 9. Author's Address
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
8 New England Executive Park 8 New England Executive Park
Burlington, MA 01803 Burlington, MA 01803
USA USA
 End of changes. 7 change blocks. 
16 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/