idnits 2.17.1 draft-ietf-bmwg-acc-bench-term-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 20 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 4. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 4 instances of too long lines in the document, the longest one being 56 characters in excess of 72. ** There are 452 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 2004) is 7316 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 843 looks like a reference -- Missing reference section? '2' on line 846 looks like a reference -- Missing reference section? '3' on line 849 looks like a reference -- Missing reference section? '4' on line 852 looks like a reference -- Missing reference section? '5' on line 855 looks like a reference Summary: 7 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group 2 INTERNET-DRAFT 3 Expires in: April 2004 4 Scott Poretsky 5 Quarry Technologies 7 Shankar Rao 8 Qwest Communications 10 Ray Piatt 11 Cable and Wireless 13 October 2003 15 Terminology for Accelerated Stress Benchmarking 17 19 Status of this Memo 21 This document is an Internet-Draft and is in full conformance with 22 all provisions of Section 10 of RFC2026. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six 30 months and may be updated, replaced, or obsoleted by other 31 documents at any time. It is inappropriate to use Internet-Drafts 32 as reference material or to cite them other than as "work in 33 progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 ABSTRACT 42 This terminology document provides the terms to be used for 43 benchmarking a router or switch under Accelerated Stress conditions. 44 Terminology is provided for performing this benchmark using 45 the Contol Plane, Data Plane, Management Plane, and Security 46 Plane of the Device Under Test. Terms are defined for 47 Configuration, Startup Conditions, Instability Conditions, Failure 48 Conditions, and Benchmarks. 50 Table of Contents 51 1. Introduction ............................................... 3 52 2. Existing definitions ....................................... 3 53 3. Term definitions............................................ 3 54 3.1 Benchmark Planes.......................................... 3 55 3.1.1 Control Plane........................................... 4 56 3.1.2 Data Plane.............................................. 5 57 3.1.3 Management Plane........................................ 5 58 3.1.4 Security Plane.......................................... 6 59 3.2 Configuration Sets........................................ 6 60 3.2.1 Control Plane Configuration Set......................... 7 61 3.2.2 Data Plane Configuration Set............................ 7 62 3.2.2.1 Traffic Profile....................................... 8 63 3.2.3 Management Plane Configuration Set...................... 8 64 3.2.4 Security Plane Configuration Set........................ 9 65 3.3 Startup Conditions........................................10 66 3.3.1 Control Plane Startup Conditions........................10 67 3.3.2 Security Plane Startup Conditions.......................11 68 3.4 Instability Conditions....................................11 69 3.4.1 Control Plane Instability Conditions....................12 70 3.4.2 Data Plane Instability Conditions.......................12 71 3.4.3 Management Plane Instability Conditions.................13 72 3.4.4 Security Plane Instability Conditions...................13 73 3.5 Failure Conditions........................................14 74 3.5.1 Unexpected Packet Loss..................................14 75 3.5.2 Unexpected Session Loss.................................14 76 3.5.3 Misrouted Packets.......................................15 77 3.5.4 Access Denial...........................................15 78 3.5.5 Errored Management Value................................16 79 3.5.6 Security Plane Failure..................................16 80 3.6 Benchmarks................................................17 81 3.6.1 Success Threshold.......................................17 82 3.6.2 Accelerated-Life Test Duration..........................17 83 4. Security Considerations.....................................18 84 5. References..................................................18 85 6. Author's Address............................................18 86 7. Full Copyright Statement....................................19 87 Appendix 1 - White Box Benchmarks..............................20 89 1. Introduction 91 Routers in an operational network are simultaneously configured with 92 multiple protocols and security policies while forwarding traffic and 93 being managed. To accurately benchmark a router for deployment it is 94 necessary to test that router in operational conditions by 95 simultaneously configuring and scaling network protocols and security 96 policies, forwarding traffic, and managing the device. It is helpful 97 to accelerate these network operational conditions so that the 98 router under test can be benchmarked with faster test duration. 99 Testing a router in accelerated network conditions is known as 100 Accelerated Stress Testing. 102 This document defines the Benchmark Planes used for the Accelerated 103 Life Benchmarking. These are the Control Plane, Data Plane, 104 Management Plane, and Security Plane. For each plane, the 105 Configuration Set, Startup Conditions, and Instability Conditions. 106 Terms are also defined for observing Failure Conditions and reporting 107 Benchmarks. White Box benchmarks are provided in Appendix 1 for 108 additional DUT behavior measurements. 110 2. Existing definitions 112 RFC 1242 "Benchmarking Terminology for Network Interconnect 113 Devices" and RFC 2285 "Benchmarking Terminology for LAN Switching 114 Devices" should be consulted before attempting to make use of this 115 document. 117 For the sake of clarity and continuity this RFC adopts the template 118 for definitions set out in Section 2 of RFC 1242. Definitions are 119 indexed and grouped together in sections for ease of reference. 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 123 this document are to be interpreted as described in RFC 2119. 125 3. Term definitions 127 3.1 Benchmark Planes 129 Definition: 130 The features, conditions, and behavior for the Accelerated Stress 131 Benchmarking. 133 Discussion: 134 There are four Benchmark Planes: Control Plane, Data Plane, 135 Management Plane, and Security Plane as shown in Figure 1. The 136 Benchmark Planes define the Configuration, Startup Conditions, 137 Instability Conditions, and Failure Conditions used for the test. 139 ___________ ___________ 140 | Control | | Management| 141 | Plane |___ ___| Plane | 142 | | | | | | 143 ----------- | | ----------- 144 \/ \/ ___________ 145 ___________ | Security | 146 | |<-----------| Plane | 147 | DUT | | | 148 |--->| |<---| ----------- 149 | ----------- | 150 | | 151 | ___________ | 152 | | Data | | 153 |--->| Plane |<---| 154 | | 155 ----------- 157 Figure 1. Router Accelerated Stress Benchmarking Planes 159 Measurement units: N/A 161 Issues: None 163 See Also: 164 Control Plane 165 Data Plane 166 Management Plane 167 Security Plane 169 3.1.1 Control Plane 170 Definition: 171 The Description of the control protocols enabled for 172 the Accelerated Stress Benchmarking. 174 Discussion: 175 The Control Plane defines the Configuration, Startup 176 Conditions, Instability Conditions, and Failure 177 Conditions of the control protocols used for the test. 178 Control Plane protocols may include routing protocols, 179 multicast protocols, and MPLS protocols. These can be 180 enabled or disabled for a benchmark test. 182 Measurement units: N/A 184 Issues: None 186 See Also: 187 Benchmark Planes 188 Control Plane Configuration Set 189 Control Plane Startup Conditions 190 Control Plane Instability Conditions 191 Control Plane Failure Conditions 192 3.1.2 Data Plane 194 Definition: 195 The data traffic profile used for the Accelerated Stress 196 Benchmarking. 198 Discussion: 199 The Data Plane defines the Configuration, Startup 200 Conditions, Instability Conditions, and Failure 201 Conditions of the data traffic used for the test. 202 The Data Plane includes the traffic and interface 203 profile. 205 Measurement Units: 206 N/A 208 See Also: 209 Benchmark Planes 210 Data Plane Configuration Set 211 Data Plane Startup Conditions 212 Data Plane Instability Conditions 213 Data Plane Failure Conditions 215 3.1.3 Management Plane 217 Definition: 218 The Management features and tools used for the 219 Accelerated Stress Benchmarking. 221 Discussion: 222 A key component of the Accelerated Stress Benchmarking is the 223 Management Plane to assess manageability of the router 224 under stress. The Management Plane defines the Configuration, 225 Startup Conditions, Instability Conditions, and Failure 226 Conditions of the management protocols and features used for 227 the test. The Management Plane includes SNMP, Logging/Debug, 228 and Statistics Collection. 230 Measurement units: 231 N/A 233 Issues: 234 None 236 See Also: 237 Benchmark Planes 238 Management Plane Configuration Set 239 Management Plane Startup Conditions 240 Management Plane Instability Conditions 241 Management Plane Failure Conditions 242 3.1.4 Security Plane 244 Definition: 245 The Security features used during the Accelerated Stress 246 Benchmarking. 248 Discussion: 249 The Control Plane defines the Configuration, Startup 250 Conditions, Instability Conditions, and Failure 251 Conditions of the security features and protocols used for 252 the test. The Security Plane includes the ACLs, Firewall, 253 Secure Protocols, and User Login. 255 Measurement units: 256 N/A 258 Issues: 259 None 261 See Also: 262 Benchmark Planes 263 Security Plane Configuration Set 264 Security Plane Startup Conditions 265 Security Plane Instability Conditions 266 Security Plane Failure Conditions 268 3.2 Configuration Sets 270 Definition: 271 The features and scaling limits used during the Accelerated Stress 272 Benchmarking. 274 Discussion: 275 There are four Configuration Sets: Control Plane Configuration Set, 276 Data Plane Configuration Set, Management Plane Configuration Set, 277 and Security Plane Configuration Set. 279 Measurement units: N/A 281 Issues: None 283 See Also: 284 Control Plane Configuration Set 285 Data Plane Configuration Set 286 Management Plane Configuration Set 287 Security Plane Configuration Set 288 3.2.1 Control Plane Configuration Set 289 Definition: 290 The routing protocols and scaling values used for the Accelerated 291 Life Benchmarking. 293 Discussion: 294 Control Plane Configuration Set is shown in Figure 2 and specifies 295 the Routing Protocols, Multicast, and MPLS configuration. Specific 296 protocols can be enabled or disabled for a benchmark test. 298 Measurement units: None 300 Issues: None 302 ____________ ____________ ____________ 303 | Routing | | Multicast | | MPLS | 304 | Protocols |___ | Protocols | __| Protocols | 305 | | | | | | | | 306 ------------ | ------------ | ------------ 307 | | | 308 | | | 309 | \/ | 310 | ___________ | 311 | | | | 312 |------->| DUT |<------| 313 | | 314 ----------- 315 Figure 2. Control Plane Configuration Module 317 See Also: 318 Data Plane Configuration Set 319 Management Configuration Set 320 Security Configuration Set 322 3.2.2 Data Plane Configuration Set 324 Definition: 325 The data traffic profile enabled for the Accelerated Stress 326 Benchmarking. 328 Discussion: 329 Data Plane Configuration Set includes the Traffic Profile and 330 interfaces used for the Accelerated Stress Benchmarking. 332 Measurement Units: 333 N/A 335 Issues: 336 None 338 See Also: 339 Traffic Profile 340 3.2.2.1 Traffic Profile 341 Definition 342 The characteristics of the Offered Load to the DUT used for 343 the Accelerated Stress Benchmarking. 345 Discussion 346 The Traffic Profile specifies the number of packet size(s), packet 347 rate per interface, number of flows, and encapsulation used for the offered load to the DUT. 349 Measurement Units: 350 Traffic Profile is reported as follows: 352 Parameter Units 353 --------- ------ 354 Packet Size(s) bytes 355 Packet Rate(interface) array of packets per second 356 Number of Flows number 357 Encapsulation(flow) array of encapsulation type 359 Issues: 360 None 362 See Also: 363 Data Plane Configuration Set 365 3.2.3 Management Plane Configuration Set 367 Definition: 368 The router management features enabled for the 369 Accelerated Stress Test. 371 Discussion: 372 A key component of the Accelerated Stress Test is the Management Configuration Set to assess manageability of the router under 373 stress. The Management Configuration Set defines the management configuration of the DUT. Features that are part of the 374 Management Configuration Set include SNMP, Logging/Debug, and 375 Statistics Collection, and services such as FTP, as shown in 376 Figure 3. 378 Measurement units: 379 N/A 381 Issues: 382 None 384 See Also: 385 Control Plane Configuration Set 386 Data Plane Configuration Set 387 Security Plane Configuration Set 389 ____________ ____________ 390 | | | Logging/ | 391 | SNMP | __| Debug | 392 | | | | | 393 ------------ | ------------ 394 | | 395 | | 396 \/ | 397 ___________ | 398 | | | 399 | DUT |<---| 400 | | 401 ----------- 402 | 403 | 404 \/ 405 ___________ 406 | Packet | 407 | Statistics| 408 | Collector | 409 | | 410 ----------- 412 Figure 3. Management Plane Configuration Set 414 3.2.4 Security Plane Configuration Set 416 Definition: 417 Security features and scaling enabled for the Accelerated Stress 418 Test. 420 Discussion: 421 The Security Plane Configuration Set includes the configuration 422 and scaling of ACLs, Firewall, IPsec, and User Access, as shown 423 in Figure 4. 425 ____________ ____________ ____________ 426 | | | Secure | | User | 427 |ACL/Firewall| | Protocol | __| Access | 428 | | | | | | | 429 ------------ ------------ | ------------ 430 | | | 431 | | | 432 | \/ | 433 | ___________ | 434 | | | | 435 |-------> | DUT |<--------| 436 | | 437 ----------- 438 Figure 4. Security Configuration Module 439 Measurement units: 440 N/A 442 Issues: 443 None 445 See Also: 446 ACL Configuration Set 447 Secure Protocol Configuration Set 448 Password Login Configuration Set 450 3.3 Startup Conditions 452 Definition: 453 Test conditions that occur at the start of the Accelerated 454 Life Benchmark to establish conditions for the remainder of 455 the test. 457 Discussion: 458 Startup Conditions may cause stress on the DUT and produce 459 failure. Startup Conditions are defined for the Control 460 Plane and Security Plane. 462 Measurement units: 463 N/A 465 Issues: 466 None 468 See Also: 469 Control Plane Startup Conditions 470 Data Plane Startup Conditions 471 Management Plane Startup Conditions 472 Security Plane Startup Conditions 474 3.3.1 Control Plane Startup Conditions 476 Definition: 477 Control Plane conditions that occur at the start 478 of the Accelerated Stress Benchmarking to establish conditions 479 for the remainder of the test. 481 Discussion: 482 Startup Conditions may cause stress on the DUT and produce 483 failure. Startup Conditions for the Control Plane include 484 session establishment rate, number of sessions established 485 and number of routes learned. 487 Measurement units: 488 N/A 489 Issues: 490 None 492 See Also: 493 Startup Conditions 494 Security Plane Startup Conditions 495 Control Plane Configuration Set 497 3.3.2 Security Plane Startup Conditions 499 Definition: 500 Security Plane conditions that occur at the start 501 of the Accelerated Stress Benchmarking to establish conditions 502 for the remainder of the test. 504 Discussion: 505 Startup Conditions may cause stress on the DUT and produce 506 failure. Startup Conditions for the Security Plane include 507 session establishment rate, number of sessions established 508 and number of policies learned, and number of user access 509 sessions opened. 511 Measurement units: 512 N/A 514 Issues: 515 None 517 See Also: 518 Startup Conditions 519 Data Plane Startup Conditions 520 Management Plane Startup Conditions 521 Security Plane Startup Conditions 523 3.4 Instability Conditions 525 Definition: 526 Test conditions that occur during the Accelerated Stress 527 Benchmark to produce instability and stress the DUT. 529 Discussion: 530 Instability Conditions are experienced by the DUT after the 531 Startup Conditions have completed. Instability Conditions 532 occur for the Control Plane, Data Plane, Management Plane, 533 and Security Plane. 535 Measurement units: 536 N/A 538 Issues: 539 None 540 See Also: 541 Control Plane Instability Conditions 542 Data Plane Instability Conditions 543 Management Plane Instability Conditions 544 Security Plane Instability Conditions 546 3.4.1 Control Plane Instability Conditions 548 Definition: 549 Control Plane conditions that occur during the Accelerated Stress 550 Benchmark to produce instability and stress the DUT. 552 Discussion: 553 Control Plane Instability Conditions are experienced by the DUT 554 after the Startup Conditions have completed. Control Plane 555 Instability Conditions experienced by the DUT include session 556 loss, route withdrawal, and route cost changes. 558 Measurement units: 559 N/A 561 Issues: 562 None 564 See Also: 565 Instability Conditions 566 Data Plane Instability Conditions 567 Management Plane Instability Conditions 568 Security Plane Instability Conditions 570 3.4.2 Data Plane Instability Conditions 571 Definition: 572 Data Plane conditions that occur during the Accelerated Stress 573 Benchmark to produce instability and stress the DUT. 575 Discussion: 576 Data Plane Instability Conditions are experienced by the DUT 577 after the Startup Conditions have completed. Data Plane 578 Instability Conditions experienced by the DUT include interface 579 shutdown, link loss, and overloaded links. 581 Measurement units: 582 N/A 584 Issues: 585 None 587 See Also: 588 Instability Conditions 589 Control Plane Instability Conditions 590 Management Plane Instability Conditions 591 Security Plane Instability Conditions 592 3.4.3 Management Plane Instability Conditions 594 Definition: 595 Management Plane conditions that occur during the Accelerated 596 Life Benchmark to produce instability and stress the DUT. 598 Discussion: 599 Management Plane Instability Conditions are experienced by the DUT 600 after the Startup Conditions have completed. Management Plane 601 Instability Conditions experienced by the DUT include repeated 602 FTP of large files. 604 Measurement units: 605 N/A 607 Issues: 608 None 610 See Also: 611 Instability Conditions 612 Control Plane Instability Conditions 613 Data Plane Instability Conditions 614 Security Plane Instability Conditions 616 3.4.4 Security Plane Instability Conditions 618 Definition: 619 Security Plane conditions that occur during the Accelerated 620 Life Benchmark to produce instability and stress the DUT. 622 Discussion: 623 Security Plane Instability Conditions are experienced by the DUT 624 after the Startup Conditions have completed. Security Plane 625 Instability Conditions experienced by the DUT include session 626 loss and policy changes. 628 Measurement units: 629 N/A 631 Issues: 632 None 634 See Also: 635 Instability Conditions 636 Control Plane Instability Conditions 637 Data Plane Instability Conditions 638 Management Plane Instability Conditions 639 3.5 Failure Conditions 641 3.5.1 Unexpected Session Loss 643 Definition: 644 Session Loss due to Control Plane or Data Plane failure during the 645 Accelerated Stress Benchmarking. 647 Discussion: 648 Session loss will be observed due to Convergence Events produced 649 by the Instability Conditions. This is not considered a failure 650 during the Accelerated Stress Benchmarking. It is expected behavior. 651 Unexpected packet loss occurs due to Data Plane or Control Plane 652 failure. 654 Measurement units: 655 sessions 657 Issues: 658 None 660 See Also: 661 Unexpected Packet Loss 662 Misrouted Packets 663 Access Denial 664 Errored Management Values 665 Security Plane Failure 667 3.5.2 Unexpected Packet Loss 668 Definition: 669 Packet Loss due to Control Plane or Data Plane failure during the 670 Accelerated Stress Benchmarking. 672 Discussion: 673 Packet loss will be observed due to Convergence Events produced 674 by the Instability Conditions. This is not considered a failure 675 during the Accelerated Stress Benchmarking. It is expected behavior. 676 Unexpected packet loss occurs due to Data Plane or Control Plane 677 failure. 679 Measurement units: 680 packets 682 Issues: 683 None 685 See Also: 686 Unexpected Session Loss 687 Misrouted Packets 688 Access Denial 689 Errored Management Values 690 Security Plane Failure 691 3.5.3 Misrouted Packets 693 Definition: 694 Packets routed to the incorrect next-hop or LSP due to Control 695 Plane failure during the Accelerated Stress Benchmarking. 697 Discussion: 698 Packets will be rerouted to new next-hops and LSPs due to Convergence 699 Events produced by the Instability Conditions. This is not considered 700 a failure during the Accelerated Stress Benchmarking. It is expected 701 behavior. Unexpected Misrouted packets occur due to Control Plane 702 failure. 704 Measurement units: 705 packets 707 Issues: 708 None 710 See Also: 711 Unexpected Packet Loss 712 Unexpected Session Loss 713 Access Denial 714 Errored Management Values 715 Security Plane Failure 717 3.5.4 Access Denial 719 Definition: 720 Inability to management the DUT due to the inability 721 to gain remote access to the DUT. 723 Discussion: 724 Handling of Instability Conditions may cause a Control Plane failure 725 of the DUT externally observable as the inability to remotely manage 726 the DUT. Whether using SNMP, Telnet, SSH, or FTP, failure to manage 727 the device constitues a failure. 729 Measurement units: 730 Failed session 732 Issues: 733 None 735 See Also: 736 Unexpected Packet Loss 737 Unexpected Session Loss 738 Misrouted Packets 739 Errored Management Value 740 Security Plane Failure 741 3.5.5 Errored Management Value 743 Definition: 744 Incorrect SNMP object value or statistic during the Accelerated 745 Life Benchmark. 747 Discussion: 748 Management of a router relies upon accurate reporting of object 749 values and statistics. The Accelerated Stress Benchmarkinging validates 750 that the DUT is able to report correct values when experiencing 751 Instability Conditions. 753 Measurement units: 754 Name of incorrect object or statistic 756 Issues: 757 None 759 See Also: 760 Unexpected Packet Loss 761 Unexpected Session Loss 762 Misrouted Packets 763 Access Denial 764 Security Plane Failure 765 Success Threshold 767 3.5.6 Security Plane Failure 768 Definition: 769 Violation of Security Policy for packets directed to the DUT 770 or routed through the DUT. 772 Discussion: 773 Security Policy is configured to permit and deny access to packets 774 destined for the DUT and packets to be routed through the DUT. 775 A violation of this security policy is when either a packet to 776 be denied is permitted or a packet to be permitted is denied. 778 Measurement units: 779 packets 781 Issues: 782 None 784 See Also: 785 Unexpected Packet Loss 786 Unexpected Session Loss 787 Misrouted Packets 788 Access Denial 789 Errored Management Value 790 3.6 Benchmarks 792 3.6.1 Success Threshold 794 Definition: 795 The intended number of hours for the DUT to operate without failure 796 during the Accelerated Stress Benchmarking. 798 Discussion: 799 Success Threshold is a user determined value of time. It is 800 necessary to define the Success Threshold because it is possible 801 for the DUT to experience zero failures for given Configuration 802 Sets, Startup Conditions, and Instability Conditions 804 Measurement units: 805 Hours 807 Issues: 808 None 810 See Also: 811 Accelerated-Life Test Duration 813 3.6.2 Accelerated-Life Test Duration 815 Definition: 816 The run-time for the Accelerated Stress Test without the DUT 817 exhibiting an error in the control plane, data plane, management 818 plane, or security plane. 820 Discussion: 821 For a successful test, the Test Duration will equal the 822 Success Threshold. In the event of any failure, the Test Duration 823 is less than the Success Threshold. Reporting of the Test 824 Duration MUST inlcude the Failure Condition from those defined 825 in this document. 827 Measurement units: 828 Hours 830 Issues: 831 None 833 See Also: 834 Success Threshold 835 4. Security Considerations 836 Documents of this type do not directly effect the security of 837 the Internet or of corporate networks as long as benchmarking 838 is not performed on devices or systems connected to operating 839 networks. 841 5. References 843 [1] Bradner, S., Editor, "Benchmarking Terminology for Network 844 Interconnection Devices", RFC 1242, July 1991. 846 [2] Mandeville, R., "Benchmarking Terminology for LAN Switching 847 Devices", RFC 2285, June 1998. 849 [3] Bradner, S. and McQuaid, J., "Benchmarking Methodology for 850 Network Interconnect Devices", RFC 2544, March 1999. 852 [4] "Core Router Evaluation for Higher Availability", Scott 853 Poretsky, NANOG 25, June 8, 2002, Toronto, CA. 855 [5] "Router Stress Testing to Validate Readiness for Network 856 Deployment", Scott Poretsky, IEEE CQR 2003. 858 6. Author's Address 860 Scott Poretsky 861 Quarry Technologies 862 8 New England Executive Park 863 Burlington, MA 01803 864 USA 865 Phone: + 1 781 395 5090 866 EMail: sporetsky@quarrytech.com 868 Shankar Rao 869 950 17th Street 870 Suite 1900 871 Qwest Communications 872 Denver, CO 80210 873 USA 874 Phone: + 1 303 437 6643 875 Email: srao@qwest.net 877 Ray Piatt 878 Cable and Wireless 879 11700 Plaza America Drive 880 Reston, VA 20190 881 USA 882 Phone: + 1 703 292 2113 883 Email: rpiatt@cw.net 884 7. Full Copyright Statement 886 Copyright (C) The Internet Society (1998). All Rights 887 Reserved. 889 This document and translations of it may be copied and 890 furnished to others, and derivative works that comment on or 891 otherwise explain it or assist in its implementation may be 892 prepared, copied, published and distributed, in whole or in 893 part, without restriction of any kind, provided that the above 894 copyright notice and this paragraph are included on all such 895 copies and derivative works. However, this document itself may 896 not be modified in any way, such as by removing the copyright 897 notice or references to the Internet Society or other Internet 898 organizations, except as needed for the purpose of developing 899 Internet standards in which case the procedures for copyrights 900 defined in the Internet Standards process must be followed, or 901 as required to translate it into languages other than English. 903 The limited permissions granted above are perpetual and will 904 not be revoked by the Internet Society or its successors or 905 assigns. This document and the information contained herein is 906 provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE 907 INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, 908 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY 909 THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY 910 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 911 FOR A PARTICULAR PURPOSE. 913 Appendix 1. White Box Benchmarking Terminology 914 Appendix 1.1 Minimum Available Memory 916 Definition: 917 Minimum DUT Available Memory during the duration of the 918 Accelerated Stress Test. 920 Discussion: 921 It is necessary to monitor DUT memory to measure this 922 benchmark. 924 Measurement units: 925 bytes 927 Issues: 928 None 930 See Also: 931 Maximum CPU Utilization 933 Appendix 1.2 Maximum CPU Utilization 935 Definition: 936 Maximum DUT CPU utilization during the duration of the 937 Accelerated Stress Test. 939 Discussion: 940 It is necessary to monitor DUT CPU Utilization to measure 941 this benchmark. 943 Measurement units: 944 % 946 Issues: 947 None 949 See Also: 950 Minimum Available Memory