draft-ietf-bmwg-ngfw-performance-00.txt   draft-ietf-bmwg-ngfw-performance-01.txt 
Benchmarking Methodology Working Group B. Balarajah Benchmarking Methodology Working Group B. Balarajah
Internet-Draft Internet-Draft
Intended status: Informational C. Rossenhoevel Intended status: Informational C. Rossenhoevel
Expires: September 6, 2019 EANTC AG Expires: March 6, 2020 EANTC AG
B. Monkman B. Monkman
NetSecOPEN NetSecOPEN
March 5, 2019 September 3, 2019
Benchmarking Methodology for Network Security Device Performance Benchmarking Methodology for Network Security Device Performance
draft-ietf-bmwg-ngfw-performance-00 draft-ietf-bmwg-ngfw-performance-01
Abstract Abstract
This document provides benchmarking terminology and methodology for This document provides benchmarking terminology and methodology for
next-generation network security devices including next-generation next-generation network security devices including next-generation
firewalls (NGFW), intrusion detection and prevention solutions (IDS/ firewalls (NGFW), intrusion detection and prevention solutions (IDS/
IPS) and unified threat management (UTM) implementations. This IPS) and unified threat management (UTM) implementations. This
document aims to strongly improve the applicability, reproducibility, document aims to strongly improve the applicability, reproducibility,
and transparency of benchmarks and to align the test methodology with and transparency of benchmarks and to align the test methodology with
today's increasingly complex layer 7 application use cases. The main today's increasingly complex layer 7 application use cases. The main
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 6, 2019. This Internet-Draft will expire on March 6, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
4.1. Testbed Configuration . . . . . . . . . . . . . . . . . . 4 4.1. Testbed Configuration . . . . . . . . . . . . . . . . . . 4
4.2. DUT/SUT Configuration . . . . . . . . . . . . . . . . . . 5 4.2. DUT/SUT Configuration . . . . . . . . . . . . . . . . . . 5
4.3. Test Equipment Configuration . . . . . . . . . . . . . . 9 4.3. Test Equipment Configuration . . . . . . . . . . . . . . 9
4.3.1. Client Configuration . . . . . . . . . . . . . . . . 9 4.3.1. Client Configuration . . . . . . . . . . . . . . . . 9
4.3.2. Backend Server Configuration . . . . . . . . . . . . 11 4.3.2. Backend Server Configuration . . . . . . . . . . . . 11
4.3.3. Traffic Flow Definition . . . . . . . . . . . . . . . 11 4.3.3. Traffic Flow Definition . . . . . . . . . . . . . . . 11
4.3.4. Traffic Load Profile . . . . . . . . . . . . . . . . 12 4.3.4. Traffic Load Profile . . . . . . . . . . . . . . . . 12
5. Test Bed Considerations . . . . . . . . . . . . . . . . . . . 13 5. Test Bed Considerations . . . . . . . . . . . . . . . . . . . 13
6. Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 14 6. Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.1. Key Performance Indicators . . . . . . . . . . . . . . . 15 6.1. Key Performance Indicators . . . . . . . . . . . . . . . 15
7. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . 17 7. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . 16
7.1. Throughput Performance With NetSecOPEN Traffic Mix . . . 17 7.1. Throughput Performance With NetSecOPEN Traffic Mix . . . 17
7.1.1. Objective . . . . . . . . . . . . . . . . . . . . . . 17 7.1.1. Objective . . . . . . . . . . . . . . . . . . . . . . 17
7.1.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 17 7.1.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 17
7.1.3. Test Parameters . . . . . . . . . . . . . . . . . . . 17 7.1.3. Test Parameters . . . . . . . . . . . . . . . . . . . 17
7.1.4. Test Procedures and expected Results . . . . . . . . 19 7.1.4. Test Procedures and expected Results . . . . . . . . 19
7.2. TCP/HTTP Connections Per Second . . . . . . . . . . . . . 20 7.2. TCP/HTTP Connections Per Second . . . . . . . . . . . . . 20
7.2.1. Objective . . . . . . . . . . . . . . . . . . . . . . 20 7.2.1. Objective . . . . . . . . . . . . . . . . . . . . . . 20
7.2.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 20 7.2.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 20
7.2.3. Test Parameters . . . . . . . . . . . . . . . . . . . 20 7.2.3. Test Parameters . . . . . . . . . . . . . . . . . . . 20
7.2.4. Test Procedures and Expected Results . . . . . . . . 22 7.2.4. Test Procedures and Expected Results . . . . . . . . 22
skipping to change at page 2, line 51 skipping to change at page 2, line 51
7.3.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 23 7.3.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 23
7.3.3. Test Parameters . . . . . . . . . . . . . . . . . . . 23 7.3.3. Test Parameters . . . . . . . . . . . . . . . . . . . 23
7.3.4. Test Procedures and Expected Results . . . . . . . . 25 7.3.4. Test Procedures and Expected Results . . . . . . . . 25
7.4. TCP/HTTP Transaction Latency . . . . . . . . . . . . . . 26 7.4. TCP/HTTP Transaction Latency . . . . . . . . . . . . . . 26
7.4.1. Objective . . . . . . . . . . . . . . . . . . . . . . 26 7.4.1. Objective . . . . . . . . . . . . . . . . . . . . . . 26
7.4.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 26 7.4.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 26
7.4.3. Test Parameters . . . . . . . . . . . . . . . . . . . 26 7.4.3. Test Parameters . . . . . . . . . . . . . . . . . . . 26
7.4.4. Test Procedures and Expected Results . . . . . . . . 28 7.4.4. Test Procedures and Expected Results . . . . . . . . 28
7.5. Concurrent TCP/HTTP Connection Capacity . . . . . . . . . 29 7.5. Concurrent TCP/HTTP Connection Capacity . . . . . . . . . 29
7.5.1. Objective . . . . . . . . . . . . . . . . . . . . . . 29 7.5.1. Objective . . . . . . . . . . . . . . . . . . . . . . 29
7.5.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 29 7.5.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 30
7.5.3. Test Parameters . . . . . . . . . . . . . . . . . . . 30 7.5.3. Test Parameters . . . . . . . . . . . . . . . . . . . 30
7.5.4. Test Procedures and expected Results . . . . . . . . 31 7.5.4. Test Procedures and expected Results . . . . . . . . 31
7.6. TCP/HTTPS Connections per second . . . . . . . . . . . . 32 7.6. TCP/HTTPS Connections per second . . . . . . . . . . . . 33
7.6.1. Objective . . . . . . . . . . . . . . . . . . . . . . 32 7.6.1. Objective . . . . . . . . . . . . . . . . . . . . . . 33
7.6.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 33 7.6.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 33
7.6.3. Test Parameters . . . . . . . . . . . . . . . . . . . 33 7.6.3. Test Parameters . . . . . . . . . . . . . . . . . . . 33
7.6.4. Test Procedures and expected Results . . . . . . . . 35 7.6.4. Test Procedures and expected Results . . . . . . . . 35
7.7. HTTPS Throughput . . . . . . . . . . . . . . . . . . . . 36 7.7. HTTPS Throughput . . . . . . . . . . . . . . . . . . . . 36
7.7.1. Objective . . . . . . . . . . . . . . . . . . . . . . 36 7.7.1. Objective . . . . . . . . . . . . . . . . . . . . . . 36
7.7.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 36 7.7.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 36
7.7.3. Test Parameters . . . . . . . . . . . . . . . . . . . 36 7.7.3. Test Parameters . . . . . . . . . . . . . . . . . . . 36
7.7.4. Test Procedures and Expected Results . . . . . . . . 39 7.7.4. Test Procedures and Expected Results . . . . . . . . 39
7.8. HTTPS Transaction Latency . . . . . . . . . . . . . . . . 40 7.8. HTTPS Transaction Latency . . . . . . . . . . . . . . . . 40
7.8.1. Objective . . . . . . . . . . . . . . . . . . . . . . 40 7.8.1. Objective . . . . . . . . . . . . . . . . . . . . . . 40
7.8.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 40 7.8.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 40
7.8.3. Test Parameters . . . . . . . . . . . . . . . . . . . 40 7.8.3. Test Parameters . . . . . . . . . . . . . . . . . . . 40
7.8.4. Test Procedures and Expected Results . . . . . . . . 42 7.8.4. Test Procedures and Expected Results . . . . . . . . 42
7.9. Concurrent TCP/HTTPS Connection Capacity . . . . . . . . 43 7.9. Concurrent TCP/HTTPS Connection Capacity . . . . . . . . 43
7.9.1. Objective . . . . . . . . . . . . . . . . . . . . . . 43 7.9.1. Objective . . . . . . . . . . . . . . . . . . . . . . 43
7.9.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 43 7.9.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 43
7.9.3. Test Parameters . . . . . . . . . . . . . . . . . . . 43 7.9.3. Test Parameters . . . . . . . . . . . . . . . . . . . 43
7.9.4. Test Procedures and expected Results . . . . . . . . 45 7.9.4. Test Procedures and expected Results . . . . . . . . 45
8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 46 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 46
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47 10. Security Considerations . . . . . . . . . . . . . . . . . . . 46
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 47 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 47 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 47
12.1. Normative References . . . . . . . . . . . . . . . . . . 47 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 47
12.2. Informative References . . . . . . . . . . . . . . . . . 47 13.1. Normative References . . . . . . . . . . . . . . . . . . 47
13.2. Informative References . . . . . . . . . . . . . . . . . 47
Appendix A. NetSecOPEN Basic Traffic Mix . . . . . . . . . . . . 48 Appendix A. NetSecOPEN Basic Traffic Mix . . . . . . . . . . . . 48
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 56 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 56
1. Introduction 1. Introduction
15 years have passed since IETF recommended test methodology and 15 years have passed since IETF recommended test methodology and
terminology for firewalls initially ([RFC2647], [RFC3511]). The terminology for firewalls initially ([RFC2647], [RFC3511]). The
requirements for network security element performance and requirements for network security element performance and
effectiveness have increased tremendously since then. Security effectiveness have increased tremendously since then. Security
function implementations have evolved to more advanced areas and have function implementations have evolved to more advanced areas and have
skipping to change at page 4, line 17 skipping to change at page 4, line 17
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119], [RFC8174] when, and only when, they appear in all 14 [RFC2119], [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Scope 3. Scope
This document provides testing terminology and testing methodology This document provides testing terminology and testing methodology
for next-generation firewalls and related security functions. It for next-generation firewalls and related security functions. It
covers two main areas: Performance benchmarks and security covers two main areas: security effectiveness configurations,
effectiveness testing. This document focuses on advanced, realistic, followed by performance benchmark testing. This document focuses on
and reproducible testing methods. Additionally, it describes test advanced, realistic, and reproducible testing methods. Additionally,
bed environments, test tool requirements and test result formats. it describes test bed environments, test tool requirements and test
result formats.
4. Test Setup 4. Test Setup
Test setup defined in this document is applicable to all benchmarking Test setup defined in this document is applicable to all benchmarking
test scenarios described in Section 7. test scenarios described in Section 7.
4.1. Testbed Configuration 4.1. Testbed Configuration
Testbed configuration MUST ensure that any performance implications Testbed configuration MUST ensure that any performance implications
that are discovered during the benchmark testing aren't due to the that are discovered during the benchmark testing aren't due to the
inherent physical network limitations such as number of physical inherent physical network limitations such as number of physical
links and forwarding performance capabilities (throughput and links and forwarding performance capabilities (throughput and
latency) of the network devise in the testbed. For this reason, this latency) of the network devise in the testbed. For this reason, this
document recommends avoiding external devices such as switches and document recommends avoiding external devices such as switches and
routers in the testbed wherever possible. routers in the testbed wherever possible.
However, in the typical deployment, the security devices (DUT/SUT) However, in the typical deployment, the security devices ( Device
are connected to routers and switches which will reduce the number of Under Test/System Under Test) are connected to routers and switches
entries in MAC or ARP tables of the DUT/SUT. If MAC or ARP tables which will reduce the number of entries in MAC or ARP tables of the
Device Under Test/System Under Test (DUT/SUT). If MAC or ARP tables
have many entries, this may impact the actual DUT/SUT performance due have many entries, this may impact the actual DUT/SUT performance due
to MAC and ARP/ND table lookup processes. Therefore, it is to MAC and ARP/ND table lookup processes. Therefore, it is
RECOMMENDED to connect aggregation switches or routers between test RECOMMENDED to connect aggregation switches or routers between test
equipment and DUT/SUT as shown in Figure 1. The aggregation switches equipment and DUT/SUT as shown in Figure 1. The aggregation switches
or routers can be also used to aggregate the test equipment or DUT/ or routers can be also used to aggregate the test equipment or DUT/
SUT ports, if the numbers of used ports are mismatched between test SUT ports, if the numbers of used ports are mismatched between test
equipment and DUT/SUT. equipment and DUT/SUT.
If the test equipment is capable of emulating layer 3 routing If the test equipment is capable of emulating layer 3 routing
functionality and there is no need for test equipment port functionality and there is no need for test equipment port
skipping to change at page 5, line 46 skipping to change at page 5, line 48
| Test Equipment | | Test Equipment | | Test Equipment | | Test Equipment |
+-----------------------+ +-----------------------+ +-----------------------+ +-----------------------+
Figure 2: Testbed Setup - Option 2 Figure 2: Testbed Setup - Option 2
4.2. DUT/SUT Configuration 4.2. DUT/SUT Configuration
A unique DUT/SUT configuration MUST be used for all benchmarking A unique DUT/SUT configuration MUST be used for all benchmarking
tests described in Section 7. Since each DUT/SUT will have their own tests described in Section 7. Since each DUT/SUT will have their own
unique configuration, users SHOULD configure their device with the unique configuration, users SHOULD configure their device with the
same parameters that would be used in the actual deployment of the same parameters and security features that would be used in the
device or a typical deployment. Users MUST enable security features actual deployment of the device or a typical deployment in order to
on the DUT/SUT to achieve maximum security coverage for a specific achieve maximum security coverage.
deployment scenario.
This document attempts to define the recommended security features This document attempts to define the recommended security features
which SHOULD be consistently enabled for all the benchmarking tests which SHOULD be consistently enabled for all the benchmarking tests
described in Section 7. Table 1 below describes the RECOMMENDED sets described in Section 7. Table 1 below describes the RECOMMENDED sets
of feature list which SHOULD be configured on the DUT/SUT. of feature list which SHOULD be configured on the DUT/SUT.
Based on customer use case, users MAY enable or disable SSL Based on customer use case, users MAY enable or disable SSL
inspection feature for "Throughput Performance with NetSecOPEN inspection feature for "Throughput Performance with NetSecOPEN
Traffic Mix" test scenario described in Section 7.1 Traffic Mix" test scenario described in Section 7.1
To improve repeatability, a summary of the DUT configuration To improve repeatability, a summary of the DUT configuration
including description of all enabled DUT/SUT features MUST be including description of all enabled DUT/SUT features MUST be
published with the benchmarking results. published with the benchmarking results.
+---------------------+ +------------------------+
| NGFW | | NGFW |
+-------------- +-----------+---------+ +-------------- +-------------+----------+
| | | | | | | |
|DUT Features | Mandatory | Optional| |DUT Features | RECOMMENDED | OPTIONAL |
| | | | | | | |
+-------------------------------------+ +----------------------------------------+
|SSL Inspection | x | | |SSL Inspection | x | |
+-------------------------------------+ +----------------------------------------+
|IDS/IPS | x | | |IDS/IPS | x | |
+-------------------------------------+ +----------------------------------------+
|Web Filtering | | x | |Web Filtering | | x |
+-------------------------------------+ +----------------------------------------+
|Antivirus | x | | |Antivirus | x | |
+-------------------------------------+ +----------------------------------------+
|Anti Spyware | x | | |Anti Spyware | x | |
+-------------------------------------+ +----------------------------------------+
|Anti Botnet | x | | |Anti Botnet | x | |
+-------------------------------------+ +----------------------------------------+
|DLP | | x | |DLP | | x |
+-------------------------------------+ +----------------------------------------+
|DDoS | | x | |DDoS | | x |
+-------------------------------------+ +----------------------------------------+
|Certificate | | x | |Certificate | | x |
|Validation | | | |Validation | | |
+-------------------------------------+ +----------------------------------------+
|Logging and | x | | |Logging and | x | |
|Reporting | | | |Reporting | | |
+-------------- +---------------------+ +-------------- +------------------------+
|Application | x | | |Application | x | |
|Identification | | | |Identification | | |
+---------------+-----------+---------+ +---------------+-------------+----------+
Table 1: DUT/SUT Feature List Table 1: DUT/SUT Feature List
In summary, DUT/SUT SHOULD be configured as follows: In summary, DUT/SUT SHOULD be configured as follows:
o All security inspection enabled o All security inspection enabled
o Disposition of all traffic is logged - Logging to an external o Disposition of all traffic is logged - Logging to an external
device is permissible device is permissible
o Detection of CVEs matching the following characteristics when o Detection of Common Vulnerabilities and Exposures (CVE) matching
searching the National Vulnerability Database (NVD) the following characteristics when searching the National
Vulnerability Database (NVD)
* CVSS Version: 2 * Common Vulnerability Scoring System (CVSS) Version: 2
* CVSS V2 Metrics: AV:N/Au:N/I:C/A:C * CVSS V2 Metrics: AV:N/Au:N/I:C/A:C
* AV=Attack Vector, Au=Authentication, I=Integrity and * AV=Attack Vector, Au=Authentication, I=Integrity and
A=Availability A=Availability
* CVSS V2 Severity: High (7-10) * CVSS V2 Severity: High (7-10)
* If doing a group test the published start date and published * If doing a group test the published start date and published
end date SHOULD be the same end date SHOULD be the same
o Geographical location filtering and Application Identification and o Geographical location filtering and Application Identification and
Control configured to be triggered based on a site or application Control configured to be triggered based on a site or application
from the defined traffic mix from the defined traffic mix
In addition, it is also RECOMMENDED to configure a realistic number In addition, it is also RECOMMENDED to configure a realistic number
of access policy rules on the DUT/SUT. This document determines the of access policy rules on the DUT/SUT. This document determines the
number of access policy rules for three different classes of DUT/SUT. number of access policy rules for three different classes of DUT/SUT.
The classification of the DUT/SUT MAY be based on its maximum The classification of the DUT/SUT MAY be based on its maximum
supported firewall throughput performance number defined in the supported firewall throughput performance number defined in the
vendor data sheet. This document classifies the DUT/SUT in three vendor data sheet. This document classifies the DUT/SUT in four
different categories; namely small, medium, and maximum. different categories; namely Extra Small, Small, Medium, and Large.
The RECOMMENDED throughput values for the following classes are: The RECOMMENDED throughput values for the following classes are:
Extra Small (XS) - supported throughput less than 1Gbit/s Extra Small (XS) - supported throughput less than 1Gbit/s
Small (S) - supported throughput less than 5Gbit/s Small (S) - supported throughput less than 5Gbit/s
Medium (M) - supported throughput greater than 5Gbit/s and less than Medium (M) - supported throughput greater than 5Gbit/s and less than
10Gbit/s 10Gbit/s
skipping to change at page 9, line 29 skipping to change at page 9, line 29
configuring clients using test equipment. Also, this section configuring clients using test equipment. Also, this section
specifies the recommended values for certain parameters. specifies the recommended values for certain parameters.
4.3.1.1. TCP Stack Attributes 4.3.1.1. TCP Stack Attributes
The TCP stack SHOULD use a TCP Reno [RFC5681] variant, which include The TCP stack SHOULD use a TCP Reno [RFC5681] variant, which include
congestion avoidance, back off and windowing, fast retransmission, congestion avoidance, back off and windowing, fast retransmission,
and fast recovery on every TCP connection between client and server and fast recovery on every TCP connection between client and server
endpoints. The default IPv4 and IPv6 MSS segments size MUST be set endpoints. The default IPv4 and IPv6 MSS segments size MUST be set
to 1460 bytes and 1440 bytes respectively and a TX and RX receive to 1460 bytes and 1440 bytes respectively and a TX and RX receive
windows of 65536 bytes. Client initial congestion window MUST NOT windows of 64 KByte. Client initial congestion window MUST NOT
exceed 10 times the MSS. Delayed ACKs are permitted and the maximum exceed 10 times the MSS. Delayed ACKs are permitted and the maximum
client delayed Ack MUST NOT exceed 10 times the MSS before a forced client delayed Ack MUST NOT exceed 10 times the MSS before a forced
ACK. Up to 3 retries SHOULD be allowed before a timeout event is ACK. Up to 3 retries SHOULD be allowed before a timeout event is
declared. All traffic MUST set the TCP PSH flag to high. The source declared. All traffic MUST set the TCP PSH flag to high. The source
port range SHOULD be in the range of 1024 - 65535. Internal timeout port range SHOULD be in the range of 1024 - 65535. Internal timeout
SHOULD be dynamically scalable per RFC 793. Client SHOULD initiate SHOULD be dynamically scalable per RFC 793. Client SHOULD initiate
and close TCP connections. TCP connections MUST be closed via FIN. and close TCP connections. TCP connections MUST be closed via FIN.
4.3.1.2. Client IP Address Space 4.3.1.2. Client IP Address Space
The sum of the client IP space SHOULD contain the following The sum of the client IP space SHOULD contain the following
attributes. The traffic blocks SHOULD consist of multiple unique, attributes. The traffic blocks SHOULD consist of multiple unique,
discontinuous static address blocks. A default gateway is permitted. discontinuous static address blocks. A default gateway is permitted.
The IPv4 ToS byte or IPv6 traffic class should be set to '00' or The IPv4 ToS byte or IPv6 traffic class should be set to '00' or
'000000' respectively. '000000' respectively.
The following equation can be used to determine the required total The following equation can be used to determine the required total
number of client IP address. number of client IP addresses.
Desired total number of client IP = Target throughput [Mbit/s] / Desired total number of client IP = Target throughput [Mbit/s] /
Throughput per IP address [Mbit/s] Throughput per IP address [Mbit/s]
Based on deployment and use case scenario, the value for "Throughput Based on deployment and use case scenario, the value for "Throughput
per IP address" can be varied. per IP address" can be varied.
(Option 1) Enterprise customer use case: 6-7 Mbps per IP (e.g. (Option 1) DUT/SUT deployment scenario 1 : 6-7 Mbit/s per IP (e.g.
1,400-1,700 IPs per 10Gbit/s throughput) 1,400-1,700 IPs per 10Gbit/s throughput)
(Option 2) Mobile ISP use case: 0.1-0.2 Mbps per IP (e.g. (Option 2) DUT/SUT deployment scenario 2 : 0.1-0.2 Mbit/s per IP
50,000-100,000 IPs per 10Gbit/s throughput) (e.g. 50,000-100,000 IPs per 10Gbit/s throughput)
Based on deployment and use case scenario, client IP addresses SHOULD Based on deployment and use case scenario, client IP addresses SHOULD
be distributed between IPv4 and IPv6 type. The Following options can be distributed between IPv4 and IPv6 type. The Following options can
be considered for a selection of traffic mix ratio. be considered for a selection of traffic mix ratio.
(Option 1) 100 % IPv4, no IPv6 (Option 1) 100 % IPv4, no IPv6
(Option 2) 80 % IPv4, 20% IPv6 (Option 2) 80 % IPv4, 20% IPv6
(Option 3) 50 % IPv4, 50% IPv6 (Option 3) 50 % IPv4, 50% IPv6
skipping to change at page 10, line 48 skipping to change at page 10, line 48
be processed if the emulated browser has available connections. The be processed if the emulated browser has available connections. The
browser SHOULD advertise a User-Agent header. Headers MUST be sent browser SHOULD advertise a User-Agent header. Headers MUST be sent
uncompressed. The browser SHOULD enforce content length validation. uncompressed. The browser SHOULD enforce content length validation.
For encrypted traffic, the following attributes SHALL define the For encrypted traffic, the following attributes SHALL define the
negotiated encryption parameters. The test clients MUST use TLSv1.2 negotiated encryption parameters. The test clients MUST use TLSv1.2
or higher. TLS record size MAY be optimized for the HTTPS response or higher. TLS record size MAY be optimized for the HTTPS response
object size up to a record size of 16 KByte. The client endpoint object size up to a record size of 16 KByte. The client endpoint
MUST send TLS Extension Server Name Indication (SNI) information when MUST send TLS Extension Server Name Indication (SNI) information when
opening a security tunnel. Each client connection MUST perform a opening a security tunnel. Each client connection MUST perform a
full handshake with servercertificate and MUST NOT use session reuse full handshake with server certificate and MUST NOT use session reuse
or resumption. Cipher suite and key size should be defined in the or resumption. Cipher suite and key size should be defined in the
parameter session of each test scenario. parameter session of each test scenario.
4.3.2. Backend Server Configuration 4.3.2. Backend Server Configuration
This document specifies which parameters should be considerable while This document specifies which parameters should be considered while
configuring emulated backend servers using test equipment. configuring emulated backend servers using test equipment.
4.3.2.1. TCP Stack Attributes 4.3.2.1. TCP Stack Attributes
The TCP stack on the server side SHOULD be configured similar to the The TCP stack on the server side SHOULD be configured similar to the
client side configuration described in Section 4.3.1.1. In addition, client side configuration described in Section 4.3.1.1. In addition,
server initial congestion window MUST NOT exceed 10 times the MSS. server initial congestion window MUST NOT exceed 10 times the MSS.
Delayed ACKs are permitted and the maximum server delayed ACK MUST Delayed ACKs are permitted and the maximum server delayed ACK MUST
NOT exceed 10 times the MSS before a forced ACK. NOT exceed 10 times the MSS before a forced ACK.
skipping to change at page 11, line 30 skipping to change at page 11, line 30
The server IP blocks SHOULD consist of unique, discontinuous static The server IP blocks SHOULD consist of unique, discontinuous static
address blocks with one IP per Server Fully Qualified Domain Name address blocks with one IP per Server Fully Qualified Domain Name
(FQDN) endpoint per test port. The IPv4 ToS byte and IPv6 traffic (FQDN) endpoint per test port. The IPv4 ToS byte and IPv6 traffic
class bytes should be set to '00' and '000000' respectively. class bytes should be set to '00' and '000000' respectively.
4.3.2.3. HTTP / HTTPS Server Pool Endpoint Attributes 4.3.2.3. HTTP / HTTPS Server Pool Endpoint Attributes
The server pool for HTTP SHOULD listen on TCP port 80 and emulate The server pool for HTTP SHOULD listen on TCP port 80 and emulate
HTTP version 1.1 with persistence. The Server MUST advertise server HTTP version 1.1 with persistence. The Server MUST advertise server
type in the Server response header [RFC2616]. For HTTPS server, TLS type in the Server response header [RFC2616]. For HTTPS server, TLS
1.2 or higher MUST be used with a maximum record size of 16 KBytes 1.2 or higher MUST be used with a maximum record size of 16 KByte and
and MUST NOT use ticket resumption or Session ID reuse . The server MUST NOT use ticket resumption or Session ID reuse . The server MUST
MUST listen on port TCP 443. The server SHALL serve a certificate to listen on port TCP 443. The server SHALL serve a certificate to the
the client. It is REQUIRED that the HTTPS server also check Host SNI client. It is REQUIRED that the HTTPS server also check Host SNI
information with the FQDN. Cipher suite and key size should be information with the FQDN. Cipher suite and key size should be
defined in the parameter section of each test scenario. defined in the parameter section of each test scenario.
4.3.3. Traffic Flow Definition 4.3.3. Traffic Flow Definition
This section describes the traffic pattern between client and server This section describes the traffic pattern between client and server
endpoints. At the beginning of the test, the server endpoint endpoints. At the beginning of the test, the server endpoint
initializes and will be ready to accept connection states including initializes and will be ready to accept connection states including
initialization of the TCP stack as well as bound HTTP and HTTPS initialization of the TCP stack as well as bound HTTP and HTTPS
servers. When a client endpoint is needed, it will initialize and be servers. When a client endpoint is needed, it will initialize and be
skipping to change at page 13, line 44 skipping to change at page 13, line 44
under test. under test.
3. Assert that the test bed characteristics are stable during the 3. Assert that the test bed characteristics are stable during the
entire test session. Several factors might influence stability entire test session. Several factors might influence stability
specifically for virtualized test beds, for example additional specifically for virtualized test beds, for example additional
workloads in a virtualized system, load balancing and movement of workloads in a virtualized system, load balancing and movement of
virtual machines during the test, or simple issues such as virtual machines during the test, or simple issues such as
additional heat created by high workloads leading to an emergency additional heat created by high workloads leading to an emergency
CPU performance reduction. CPU performance reduction.
Test bed reference pre-tests help to ensure that the desired traffic Test bed reference pre-tests help to ensure that the maximum desired
generator aspects such as maximum throughput and the network traffic generator aspects such as throughput, transaction per second,
performance metrics such as maximum latency and maximum packet loss connection per second, concurrent connection and latency.
are met.
Once the desired maximum performance goals for the system under test Once the desired maximum performance goals for the system under test
have been identified, a safety margin of 10% SHOULD be added for have been identified, a safety margin of 10% SHOULD be added for
throughput and subtracted for maximum latency and maximum packet throughput and subtracted for maximum latency and maximum packet
loss. loss.
Test bed preparation may be performed either by configuring the DUT Test bed preparation may be performed either by configuring the DUT
in the most trivial setup (fast forwarding) or without presence of in the most trivial setup (fast forwarding) or without presence of
DUT. DUT.
skipping to change at page 15, line 4 skipping to change at page 14, line 49
B. DUT Software B. DUT Software
+ The operating system name MUST be documented + The operating system name MUST be documented
+ The version MUST be documented + The version MUST be documented
+ The specific configuration MUST be documented + The specific configuration MUST be documented
C. DUT Enabled Features C. DUT Enabled Features
+ Specific features, such as logging, NGFW, DPI MUST be
+ Configured DUT/SUT features (see Table 1) MUST be
documented documented
+ Attributes of those featured MUST be documented + Attributes of those featured MUST be documented
+ Any additional relevant information about features MUST be + Any additional relevant information about features MUST be
documented documented
D. Test equipment hardware and software D. Test equipment hardware and software
+ Test equipment vendor name + Test equipment vendor name
skipping to change at page 16, line 24 skipping to change at page 16, line 21
o TLS Handshake Rate o TLS Handshake Rate
This key performance indicator measures the average TLS 1.2 or This key performance indicator measures the average TLS 1.2 or
higher session formation rate within the sustaining period. higher session formation rate within the sustaining period.
o Throughput o Throughput
This key performance indicator measures the average Layer 2 This key performance indicator measures the average Layer 2
throughput within the sustaining period as well as average packets throughput within the sustaining period as well as average packets
per seconds within the same period. The value of throughput per seconds within the same period. The value of throughput
SHOULD be presented in Gbit/s rounded to two places of precision SHOULD be presented in Gbit/s rounded to two places of precision
with a more specific kbps in parenthesis. Optionally, goodput MAY with a more specific Kbit/s in parenthesis. Optionally, goodput
also be logged as an average goodput rate measured over the same MAY also be logged as an average goodput rate measured over the
period. Goodput result SHALL also be presented in the same format same period. Goodput result SHALL also be presented in the same
as throughput. format as throughput.
o URL Response time / Time to Last Byte (TTLB) o URL Response time / Time to Last Byte (TTLB)
This key performance indicator measures the minimum, average and This key performance indicator measures the minimum, average and
maximum per URL response time in the sustaining period. The maximum per URL response time in the sustaining period. The
latency is measured at Client and in this case would be the time latency is measured at Client and in this case would be the time
duration between sending a GET request from Client and the duration between sending a GET request from Client and the
receival of the complete response from the server. receival of the complete response from the server.
o Application Transaction Latency o Application Transaction Latency
This key performance indicator measures the minimum, average and This key performance indicator measures the minimum, average and
skipping to change at page 18, line 27 skipping to change at page 18, line 25
4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash 4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash
Algorithm: rsa_pkcs1_sha384 and Supported group: secp256) Algorithm: rsa_pkcs1_sha384 and Supported group: secp256)
7.1.3.3. Traffic Profile 7.1.3.3. Traffic Profile
Traffic profile: Test scenario MUST be run with a single application Traffic profile: Test scenario MUST be run with a single application
traffic mix profile (see Appendix A for details about traffic mix). traffic mix profile (see Appendix A for details about traffic mix).
The name of the NetSecOPEN traffic mix MUST be documented. The name of the NetSecOPEN traffic mix MUST be documented.
7.1.3.4. Test Results Acceptance Criteria 7.1.3.4. Test Results Validation Criteria
The following test Criteria is defined as test results acceptance The following test Criteria is defined as test results validation
criteria. Test results acceptance criteria MUST be monitored during criteria. Test results validation criteria MUST be monitored during
the whole sustain phase of the traffic load profile. the whole sustain phase of the traffic load profile.
a. Number of failed Application transactions MUST be less than a. Number of failed Application transactions (receiving any HTTP
0.001% (1 out of 100,000 transactions) of total attempt response code other than 200 OK) MUST be less than 0.001% (1 out
transactions of 100,000 transactions) of total attempt transactions
b. Number of Terminated TCP connections due to unexpected TCP RST b. Number of Terminated TCP connections due to unexpected TCP RST
sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
connections) of total initiated TCP connections connections) of total initiated TCP connections
c. Maximum deviation (max. dev) of application transaction time or c. Maximum deviation (max. dev) of application transaction time or
TTLB (Time To Last Byte) MUST be less than X (The value for "X" TTLB (Time To Last Byte) MUST be less than X (The value for "X"
will be finalized and updated after completion of PoC test) will be finalized and updated after completion of PoC test)
The following equation MUST be used to calculate the deviation of The following equation MUST be used to calculate the deviation of
application transaction latency or TTLB application transaction latency or TTLB
skipping to change at page 19, line 40 skipping to change at page 19, line 38
Verify the link status of the all connected physical interfaces. All Verify the link status of the all connected physical interfaces. All
interfaces are expected to be in "UP" status. interfaces are expected to be in "UP" status.
Configure traffic load profile of the test equipment to generate test Configure traffic load profile of the test equipment to generate test
traffic at the "Initial throughput" rate as described in the traffic at the "Initial throughput" rate as described in the
parameters Section 7.1.3.2. The test equipment SHOULD follow the parameters Section 7.1.3.2. The test equipment SHOULD follow the
traffic load profile definition as described in Section 4.3.4. The traffic load profile definition as described in Section 4.3.4. The
DUT/SUT SHOULD reach the "Initial throughput" during the sustain DUT/SUT SHOULD reach the "Initial throughput" during the sustain
phase. Measure all KPI as defined in Section 7.1.3.5. The measured phase. Measure all KPI as defined in Section 7.1.3.5. The measured
KPIs during the sustain phase MUST meet acceptance criteria "a" and KPIs during the sustain phase MUST meet validation criteria "a" and
"b" defined in Section 7.1.3.4. "b" defined in Section 7.1.3.4.
If the KPI metrics do not meet the acceptance criteria, the test If the KPI metrics do not meet the validation criteria, the test
procedure MUST NOT be continued to step 2. procedure MUST NOT be continued to step 2.
7.1.4.2. Step 2: Test Run with Target Objective 7.1.4.2. Step 2: Test Run with Target Objective
Configure test equipment to generate traffic at the "Target Configure test equipment to generate traffic at the "Target
throughput" rate defined in the parameter table. The test equipment throughput" rate defined in the parameter table. The test equipment
SHOULD follow the traffic load profile definition as described in SHOULD follow the traffic load profile definition as described in
Section 4.3.4. The test equipment SHOULD start to measure and record Section 4.3.4. The test equipment SHOULD start to measure and record
all specified KPIs. The frequency of KPI metric measurements MUST be all specified KPIs. The frequency of KPI metric measurements SHOULD
less than 5 seconds. Continue the test until all traffic profile be 2 seconds. Continue the test until all traffic profile phases are
phases are completed. completed.
The DUT/SUT is expected to reach the desired target throughput during The DUT/SUT is expected to reach the desired target throughput during
the sustain phase. In addition, the measured KPIs MUST meet all the sustain phase. In addition, the measured KPIs MUST meet all
acceptance criteria. Follow step 3, if the KPI metrics do not meet validation criteria. Follow step 3, if the KPI metrics do not meet
the acceptance criteria. the validation criteria.
7.1.4.3. Step 3: Test Iteration 7.1.4.3. Step 3: Test Iteration
Determine the maximum and average achievable throughput within the Determine the maximum and average achievable throughput within the
acceptance criteria. Final test iteration MUST be performed for the validation criteria. Final test iteration MUST be performed for the
test duration defined in Section 4.3.4. test duration defined in Section 4.3.4.
7.2. TCP/HTTP Connections Per Second 7.2. TCP/HTTP Connections Per Second
7.2.1. Objective 7.2.1. Objective
Using HTTP traffic, determine the maximum sustainable TCP connection Using HTTP traffic, determine the maximum sustainable TCP connection
establishment rate supported by the DUT/SUT under different establishment rate supported by the DUT/SUT under different
throughput load conditions. throughput load conditions.
skipping to change at page 21, line 4 skipping to change at page 20, line 50
Section 4.2. Any configuration changes for this specific test Section 4.2. Any configuration changes for this specific test
scenario MUST be documented. scenario MUST be documented.
7.2.3.2. Test Equipment Configuration Parameters 7.2.3.2. Test Equipment Configuration Parameters
Test equipment configuration parameters MUST conform to the Test equipment configuration parameters MUST conform to the
requirements defined in Section 4.3. Following parameters MUST be requirements defined in Section 4.3. Following parameters MUST be
documented for this test scenario: documented for this test scenario:
Client IP address range defined in Section 4.3.1.2 Client IP address range defined in Section 4.3.1.2
Server IP address range defined in Section 4.3.2.2
Server IP address range defined in Section 4.3.2.2
Traffic distribution ratio between IPv4 and IPv6 defined in Traffic distribution ratio between IPv4 and IPv6 defined in
Section 4.3.1.2 Section 4.3.1.2
Target connections per second: Initial value from product data sheet Target connections per second: Initial value from product data sheet
(if known) (if known)
Initial connections per second: 10% of "Target connections per Initial connections per second: 10% of "Target connections per
second" second"
The client SHOULD negotiate HTTP 1.1 and close the connection with The client SHOULD negotiate HTTP 1.1 and close the connection with
FIN immediately after completion of one transaction. In each test FIN immediately after completion of one transaction. In each test
iteration, client MUST send GET command requesting a fixed HTTP iteration, client MUST send GET command requesting a fixed HTTP
response object size. response object size.
The RECOMMENDED response object sizes are 1, 2, 4, 16, 64 KByte The RECOMMENDED response object sizes are 1, 2, 4, 16, 64 KByte
7.2.3.3. Test Results Acceptance Criteria 7.2.3.3. Test Results Validation Criteria
The following test Criteria is defined as test results acceptance The following test Criteria is defined as test results validation
criteria. Test results acceptance criteria MUST be monitored during criteria. Test results validation criteria MUST be monitored during
the whole sustain phase of the traffic load profile. the whole sustain phase of the traffic load profile.
a. Number of failed Application transactions MUST be less than a. Number of failed Application transactions (receiving any HTTP
0.001% (1 out of 100,000 transactions) of total attempt response code other than 200 OK) MUST be less than 0.001% (1 out
transactions of 100,000 transactions) of total attempt transactions
b. Number of Terminated TCP connections due to unexpected TCP RST b. Number of Terminated TCP connections due to unexpected TCP RST
sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
connections) of total initiated TCP connections connections) of total initiated TCP connections
c. During the sustain phase, traffic should be forwarded at a c. During the sustain phase, traffic should be forwarded at a
constant rate constant rate
d. Concurrent TCP connections SHOULD be constant during steady d. Concurrent TCP connections SHOULD be constant during steady
state. Any deviation of concurrent TCP connections MUST be less state. Any deviation of concurrent TCP connections MUST be less
skipping to change at page 22, line 26 skipping to change at page 22, line 26
Verify the link status of all connected physical interfaces. All Verify the link status of all connected physical interfaces. All
interfaces are expected to be in "UP" status. interfaces are expected to be in "UP" status.
Configure the traffic load profile of the test equipment to establish Configure the traffic load profile of the test equipment to establish
"initial connections per second" as defined in the parameters "initial connections per second" as defined in the parameters
Section 7.2.3.2. The traffic load profile SHOULD be defined as Section 7.2.3.2. The traffic load profile SHOULD be defined as
described in Section 4.3.4. described in Section 4.3.4.
The DUT/SUT SHOULD reach the "Initial connections per second" before The DUT/SUT SHOULD reach the "Initial connections per second" before
the sustain phase. The measured KPIs during the sustain phase MUST the sustain phase. The measured KPIs during the sustain phase MUST
meet acceptance criteria a, b, c, and d defined in Section 7.2.3.3. meet validation criteria a, b, c, and d defined in Section 7.2.3.3.
If the KPI metrics do not meet the acceptance criteria, the test If the KPI metrics do not meet the validation criteria, the test
procedure MUST NOT be continued to "Step 2". procedure MUST NOT be continued to "Step 2".
7.2.4.2. Step 2: Test Run with Target Objective 7.2.4.2. Step 2: Test Run with Target Objective
Configure test equipment to establish "Target connections per second" Configure test equipment to establish "Target connections per second"
defined in the parameters table. The test equipment SHOULD follow defined in the parameters table. The test equipment SHOULD follow
the traffic load profile definition as described in Section 4.3.4. the traffic load profile definition as described in Section 4.3.4.
During the ramp up and sustain phase of each test iteration, other During the ramp up and sustain phase of each test iteration, other
KPIs such as throughput, concurrent TCP connections and application KPIs such as throughput, concurrent TCP connections and application
transactions per second MUST NOT reach to the maximum value the DUT/ transactions per second MUST NOT reach to the maximum value the DUT/
SUT can support. The test results for specific test iterations SUT can support. The test results for specific test iterations
SHOULD NOT be reported, if the above mentioned KPI (especially SHOULD NOT be reported, if the above mentioned KPI (especially
throughput) reaches the maximum value. (Example: If the test throughput) reaches the maximum value. (Example: If the test
iteration with 64Kbyte of HTTP response object size reached the iteration with 64 KByte of HTTP response object size reached the
maximum throughput limitation of the DUT, the test iteration MAY be maximum throughput limitation of the DUT, the test iteration MAY be
interrupted and the result for 64kbyte SHOULD NOT be reported). interrupted and the result for 64 KByte SHOULD NOT be reported).
The test equipment SHOULD start to measure and record all specified The test equipment SHOULD start to measure and record all specified
KPIs. The frequency of measurement MUST be less than 5 seconds. KPIs. The frequency of measurement SHOULD be 2 seconds. Continue
Continue the test until all traffic profile phases are completed. the test until all traffic profile phases are completed.
The DUT/SUT is expected to reach the desired target connections per The DUT/SUT is expected to reach the desired target connections per
second rate at the sustain phase. In addition, the measured KPIs second rate at the sustain phase. In addition, the measured KPIs
MUST meet all acceptance criteria. MUST meet all validation criteria.
Follow step 3, if the KPI metrics do not meet the acceptance Follow step 3, if the KPI metrics do not meet the validation
criteria. criteria.
7.2.4.3. Step 3: Test Iteration 7.2.4.3. Step 3: Test Iteration
Determine the maximum and average achievable connections per second Determine the maximum and average achievable connections per second
within the acceptance criteria. within the validation criteria.
7.3. HTTP Throughput 7.3. HTTP Throughput
7.3.1. Objective 7.3.1. Objective
Determine the throughput for HTTP transactions varying the HTTP Determine the throughput for HTTP transactions varying the HTTP
response object size. response object size.
7.3.2. Test Setup 7.3.2. Test Setup
skipping to change at page 24, line 11 skipping to change at page 24, line 11
Traffic distribution ratio between IPv4 and IPv6 defined in Traffic distribution ratio between IPv4 and IPv6 defined in
Section 4.3.1.2 Section 4.3.1.2
Target Throughput: Initial value from product data sheet (if known) Target Throughput: Initial value from product data sheet (if known)
Initial Throughput: 10% of "Target Throughput" Initial Throughput: 10% of "Target Throughput"
Number of HTTP response object requests (transactions) per Number of HTTP response object requests (transactions) per
connection: 10 connection: 10
RECOMMENDED HTTP response object size: 1KB, 16KB, 64KB, 256KB and RECOMMENDED HTTP response object size: 1 KByte, 16 KByte, 64 KByte,
mixed objects defined in the table 256 KByte and mixed objects defined in the table
+---------------------+---------------------+ +---------------------+---------------------+
| Object size (KByte) | Number of requests/ | | Object size (KByte) | Number of requests/ |
| | Weight | | | Weight |
+---------------------+---------------------+ +---------------------+---------------------+
| 0.2 | 1 | | 0.2 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
| 6 | 1 | | 6 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
| 8 | 1 | | 8 | 1 |
skipping to change at page 24, line 41 skipping to change at page 24, line 41
+---------------------+---------------------+ +---------------------+---------------------+
| 35 | 1 | | 35 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
| 59 | 1 | | 59 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
| 347 | 1 | | 347 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
Table 3: Mixed Objects Table 3: Mixed Objects
7.3.3.3. Test Results Acceptance Criteria 7.3.3.3. Test Results Validation Criteria
The following test Criteria is defined as test results acceptance The following test Criteria is defined as test results validation
criteria. Test results acceptance criteria MUST be monitored during criteria. Test results validation criteria MUST be monitored during
the whole sustain phase of the traffic load profile the whole sustain phase of the traffic load profile
a. Number of failed Application transactions MUST be less than a. Number of failed Application transactions (receiving any HTTP
0.001% (1 out of 100,000 transactions) of attempt transactions. response code other than 200 OK) MUST be less than 0.001% (1 out
of 100,000 transactions) of attempt transactions.
b. Traffic should be forwarded constantly. b. Traffic should be forwarded constantly.
c. Concurrent connetions MUST be constant. The deviation of c. Concurrent connetions MUST be constant. The deviation of
concurrent TCP connection MUST NOT increase more than 10% concurrent TCP connection MUST NOT increase more than 10%
7.3.3.4. Measurement 7.3.3.4. Measurement
The KPI metrics MUST be reported for this test scenario: The KPI metrics MUST be reported for this test scenario:
skipping to change at page 25, line 35 skipping to change at page 25, line 35
interfaces are expected to be in "UP" status. interfaces are expected to be in "UP" status.
Configure traffic load profile of the test equipment to establish Configure traffic load profile of the test equipment to establish
"Initial Throughput" as defined in the parameters Section 7.3.3.2. "Initial Throughput" as defined in the parameters Section 7.3.3.2.
The traffic load profile SHOULD be defined as described in The traffic load profile SHOULD be defined as described in
Section 4.3.4. The DUT/SUT SHOULD reach the "Initial Throughput" Section 4.3.4. The DUT/SUT SHOULD reach the "Initial Throughput"
during the sustain phase. Measure all KPI as defined in during the sustain phase. Measure all KPI as defined in
Section 7.3.3.4. Section 7.3.3.4.
The measured KPIs during the sustain phase MUST meet the acceptance The measured KPIs during the sustain phase MUST meet the validation
criteria "a" defined in Section 7.3.3.3. criteria "a" defined in Section 7.3.3.3.
If the KPI metrics do not meet the acceptance criteria, the test If the KPI metrics do not meet the validation criteria, the test
procedure MUST NOT be continued to "Step 2". procedure MUST NOT be continued to "Step 2".
7.3.4.2. Step 2: Test Run with Target Objective 7.3.4.2. Step 2: Test Run with Target Objective
The test equipment SHOULD start to measure and record all specified The test equipment SHOULD start to measure and record all specified
KPIs. The frequency of measurement MUST be less than 5 seconds. KPIs. The frequency of measurement SHOULD be 2 seconds. Continue
Continue the test until all traffic profile phases are completed. the test until all traffic profile phases are completed.
The DUT/SUT is expected to reach the desired "Target Throughput" at The DUT/SUT is expected to reach the desired "Target Throughput" at
the sustain phase. In addition, the measured KPIs must meet all the sustain phase. In addition, the measured KPIs must meet all
acceptance criteria. validation criteria.
Perform the test separately for each HTTP response object size. Perform the test separately for each HTTP response object size.
Follow step 3, if the KPI metrics do not meet the acceptance Follow step 3, if the KPI metrics do not meet the validation
criteria. criteria.
7.3.4.3. Step 3: Test Iteration 7.3.4.3. Step 3: Test Iteration
Determine the maximum and average achievable throughput within the Determine the maximum and average achievable throughput within the
acceptance criteria. Final test iteration MUST be performed for the validation criteria. Final test iteration MUST be performed for the
test duration defined in Section 4.3.4. test duration defined in Section 4.3.4.
7.4. TCP/HTTP Transaction Latency 7.4. TCP/HTTP Transaction Latency
7.4.1. Objective 7.4.1. Objective
Using HTTP traffic, determine the average HTTP transaction latency Using HTTP traffic, determine the average HTTP transaction latency
when DUT is running with sustainable HTTP transactions per second when DUT is running with sustainable HTTP transactions per second
supported by the DUT/SUT under different HTTP response object sizes. supported by the DUT/SUT under different HTTP response object sizes.
skipping to change at page 27, line 35 skipping to change at page 27, line 35
Initial objective for scenario 1: 10% of Target objective for Initial objective for scenario 1: 10% of Target objective for
scenario 1" scenario 1"
Initial objective for scenario 2: 10% of "Target objective for Initial objective for scenario 2: 10% of "Target objective for
scenario 2" scenario 2"
HTTP transaction per TCP connection: test scenario 1 with single HTTP transaction per TCP connection: test scenario 1 with single
transaction and the second scenario with 10 transactions transaction and the second scenario with 10 transactions
HTTP 1.1 with GET command requesting a single object. The HTTP 1.1 with GET command requesting a single object. The
RECOMMENDED object sizes are 1, 16 or 64 Kbyte. For each test RECOMMENDED object sizes are 1, 16 or 64 KByte. For each test
iteration, client MUST request a single HTTP response object size. iteration, client MUST request a single HTTP response object size.
7.4.3.3. Test Results Acceptance Criteria 7.4.3.3. Test Results Validation Criteria
The following test Criteria is defined as test results acceptance The following test Criteria is defined as test results validation
criteria. Test results acceptance criteria MUST be monitored during criteria. Test results validation criteria MUST be monitored during
the whole sustain phase of the traffic load profile. Ramp up and the whole sustain phase of the traffic load profile. Ramp up and
ramp down phase SHOULD NOT be considered. ramp down phase SHOULD NOT be considered.
Generic criteria: Generic criteria:
a. Number of failed Application transactions MUST be less than a. Number of failed Application transactions (receiving any HTTP
0.001% (1 out of 100,000 transactions) of attempt transactions. response code other than 200 OK) MUST be less than 0.001% (1 out
of 100,000 transactions) of attempt transactions.
b. Number of Terminated TCP connections due to unexpected TCP RST b. Number of Terminated TCP connections due to unexpected TCP RST
sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
connections) of total initiated TCP connections connections) of total initiated TCP connections
c. During the sustain phase, traffic should be forwarded at a c. During the sustain phase, traffic should be forwarded at a
constant rate. constant rate.
d. Concurrent TCP connections should be constant during steady d. Concurrent TCP connections should be constant during steady
state. This confirms the DUT opens and closes TCP connections at state. This confirms the DUT opens and closes TCP connections at
skipping to change at page 28, line 49 skipping to change at page 29, line 7
Verify the link status of the all connected physical interfaces. All Verify the link status of the all connected physical interfaces. All
interfaces are expected to be in "UP" status. interfaces are expected to be in "UP" status.
Configure traffic load profile of the test equipment to establish Configure traffic load profile of the test equipment to establish
"Initial objective" as defined in the parameters Section 7.4.3.2. "Initial objective" as defined in the parameters Section 7.4.3.2.
The traffic load profile can be defined as described in The traffic load profile can be defined as described in
Section 4.3.4. Section 4.3.4.
The DUT/SUT SHOULD reach the "Initial objective" before the sustain The DUT/SUT SHOULD reach the "Initial objective" before the sustain
phase. The measured KPIs during the sustain phase MUST meet the phase. The measured KPIs during the sustain phase MUST meet the
acceptance criteria a, b, c, d, e and f defined in Section 7.4.3.3. validation criteria a, b, c, d, e and f defined in Section 7.4.3.3.
If the KPI metrics do not meet the acceptance criteria, the test If the KPI metrics do not meet the validation criteria, the test
procedure MUST NOT be continued to "Step 2". procedure MUST NOT be continued to "Step 2".
7.4.4.2. Step 2: Test Run with Target Objective 7.4.4.2. Step 2: Test Run with Target Objective
Configure test equipment to establish "Target objective" defined in Configure test equipment to establish "Target objective" defined in
the parameters table. The test equipment SHOULD follow the traffic the parameters table. The test equipment SHOULD follow the traffic
load profile definition as described in Section 4.3.4. load profile definition as described in Section 4.3.4.
During the ramp up and sustain phase, other KPIs such as throughput, During the ramp up and sustain phase, other KPIs such as throughput,
concurrent TCP connections and application transactions per second concurrent TCP connections and application transactions per second
MUST NOT reach to the maximum value that the DUT/SUT can support. MUST NOT reach to the maximum value that the DUT/SUT can support.
The test results for specific test iterations SHOULD NOT be reported, The test results for specific test iterations SHOULD NOT be reported,
if the above mentioned KPI (especially throughput) reaches to the if the above mentioned KPI (especially throughput) reaches to the
maximum value. (Example: If the test iteration with 64Kbyte of HTTP maximum value. (Example: If the test iteration with 64 KByte of HTTP
response object size reached the maximum throughput limitation of the response object size reached the maximum throughput limitation of the
DUT, the test iteration MAY be interrupted and the result for 64kbyte DUT, the test iteration MAY be interrupted and the result for 64
SHOULD NOT be reported). KByte SHOULD NOT be reported).
The test equipment SHOULD start to measure and record all specified The test equipment SHOULD start to measure and record all specified
KPIs. The frequency of measurement MUST be less than 5 seconds. KPIs. The frequency of measurement SHOULD be 2 seconds. Continue
Continue the test until all traffic profile phases are completed. the test until all traffic profile phases are completed. DUT/SUT is
DUT/SUT is expected to reach the desired "Target objective" at the expected to reach the desired "Target objective" at the sustain
sustain phase. In addition, the measured KPIs MUST meet all phase. In addition, the measured KPIs MUST meet all validation
acceptance criteria. criteria.
Follow step 3, if the KPI metrics do not meet the acceptance Follow step 3, if the KPI metrics do not meet the validation
criteria. criteria.
7.4.4.3. Step 3: Test Iteration 7.4.4.3. Step 3: Test Iteration
Determine the maximum achievable connections per second within the Determine the maximum achievable connections per second within the
acceptance criteria and measure the latency values. validation criteria and measure the latency values.
7.5. Concurrent TCP/HTTP Connection Capacity 7.5. Concurrent TCP/HTTP Connection Capacity
7.5.1. Objective 7.5.1. Objective
Determine the maximum number of concurrent TCP connections that the Determine the maximum number of concurrent TCP connections that the
DUT/ SUT sustains when using HTTP traffic. DUT/ SUT sustains when using HTTP traffic.
7.5.2. Test Setup 7.5.2. Test Setup
skipping to change at page 30, line 49 skipping to change at page 31, line 8
connection"): "Target concurrent connection" / "Maximum connection"): "Target concurrent connection" / "Maximum
connections per second during ramp up phase" connections per second during ramp up phase"
Ramp up time (in traffic load profile for "Initial concurrent Ramp up time (in traffic load profile for "Initial concurrent
connection"): "Initial concurrent connection" / "Maximum connection"): "Initial concurrent connection" / "Maximum
connections per second during ramp up phase" connections per second during ramp up phase"
The client MUST negotiate HTTP 1.1 with persistence and each client The client MUST negotiate HTTP 1.1 with persistence and each client
MAY open multiple concurrent TCP connections per server endpoint IP. MAY open multiple concurrent TCP connections per server endpoint IP.
Each client sends 10 GET commands requesting 1Kbyte HTTP response Each client sends 10 GET commands requesting 1 KByte HTTP response
object in the same TCP connection (10 transactions/TCP connection) object in the same TCP connection (10 transactions/TCP connection)
and the delay (think time) between the transaction MUST be X seconds. and the delay (think time) between the transaction MUST be X seconds.
X = ("Ramp up time" + "steady state time") /10 X = ("Ramp up time" + "steady state time") /10
The established connections SHOULD remain open until the ramp down The established connections SHOULD remain open until the ramp down
phase of the test. During the ramp down phase, all connections phase of the test. During the ramp down phase, all connections
SHOULD be successfully closed with FIN. SHOULD be successfully closed with FIN.
7.5.3.3. Test Results Acceptance Criteria 7.5.3.3. Test Results Validation Criteria
The following test Criteria is defined as test results acceptance The following test Criteria is defined as test results validation
criteria. Test results acceptance criteria MUST be monitored during criteria. Test results validation criteria MUST be monitored during
the whole sustain phase of the traffic load profile. the whole sustain phase of the traffic load profile.
a. Number of failed Application transactions MUST be less than a. Number of failed Application transactions (receiving any HTTP
0.001% (1 out of 100,000 transaction) of total attempted response code other than 200 OK) MUST be less than 0.001% (1 out
transactions of 100,000 transaction) of total attempted transactions
b. Number of Terminated TCP connections due to unexpected TCP RST b. Number of Terminated TCP connections due to unexpected TCP RST
sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
connections) of total initiated TCP connections connections) of total initiated TCP connections
c. During the sustain phase, traffic should be forwarded constantly c. During the sustain phase, traffic should be forwarded constantly
d. During the sustain phase, the maximum deviation (max. dev) of
application transaction latency or TTLB (Time To Last Byte) MUST
be less than 10%
7.5.3.4. Measurement 7.5.3.4. Measurement
Following KPI metrics MUST be reported for this test scenario: Following KPI metrics MUST be reported for this test scenario:
average Throughput, Concurrent TCP connections (minimum, average and average Throughput, Concurrent TCP connections (minimum, average and
maximum), TTLB/ application transaction latency (minimum, average and maximum), TTLB/ application transaction latency (minimum, average and
maximum) and average application transactions per second. maximum) and average application transactions per second.
7.5.4. Test Procedures and expected Results 7.5.4. Test Procedures and expected Results
skipping to change at page 32, line 11 skipping to change at page 32, line 16
Verify the link status of the all connected physical interfaces. All Verify the link status of the all connected physical interfaces. All
interfaces are expected to be in "UP" status. interfaces are expected to be in "UP" status.
Configure test equipment to establish "Initial concurrent TCP Configure test equipment to establish "Initial concurrent TCP
connections" defined in Section 7.5.3.2. Except ramp up time, the connections" defined in Section 7.5.3.2. Except ramp up time, the
traffic load profile SHOULD be defined as described in Section 4.3.4. traffic load profile SHOULD be defined as described in Section 4.3.4.
During the sustain phase, the DUT/SUT SHOULD reach the "Initial During the sustain phase, the DUT/SUT SHOULD reach the "Initial
concurrent TCP connections". The measured KPIs during the sustain concurrent TCP connections". The measured KPIs during the sustain
phase MUST meet the acceptance criteria "a" and "b" defined in phase MUST meet the validation criteria "a" and "b" defined in
Section 7.5.3.3. Section 7.5.3.3.
If the KPI metrics do not meet the acceptance criteria, the test If the KPI metrics do not meet the validation criteria, the test
procedure MUST NOT be continued to "Step 2". procedure MUST NOT be continued to "Step 2".
7.5.4.2. Step 2: Test Run with Target Objective 7.5.4.2. Step 2: Test Run with Target Objective
Configure test equipment to establish "Target concurrent TCP Configure test equipment to establish "Target concurrent TCP
connections". The test equipment SHOULD follow the traffic load connections". The test equipment SHOULD follow the traffic load
profile definition (except ramp up time) as described in profile definition (except ramp up time) as described in
Section 4.3.4. Section 4.3.4.
During the ramp up and sustain phase, the other KPIs such as During the ramp up and sustain phase, the other KPIs such as
throughput, TCP connections per second and application transactions throughput, TCP connections per second and application transactions
per second MUST NOT reach to the maximum value that the DUT/SUT can per second MUST NOT reach to the maximum value that the DUT/SUT can
support. support.
The test equipment SHOULD start to measure and record KPIs defined in The test equipment SHOULD start to measure and record KPIs defined in
Section 7.5.3.4. The frequency of measurement MUST be less than 5 Section 7.5.3.4. The frequency of measurement SHOULD be 2 seconds.
seconds. Continue the test until all traffic profile phases are Continue the test until all traffic profile phases are completed.
completed.
The DUT/SUT is expected to reach the desired target concurrent The DUT/SUT is expected to reach the desired target concurrent
connection at the sustain phase. In addition, the measured KPIs must connection at the sustain phase. In addition, the measured KPIs must
meet all acceptance criteria. meet all validation criteria.
Follow step 3, if the KPI metrics do not meet the acceptance Follow step 3, if the KPI metrics do not meet the validation
criteria. criteria.
7.5.4.3. Step 3: Test Iteration 7.5.4.3. Step 3: Test Iteration
Determine the maximum and average achievable concurrent TCP Determine the maximum and average achievable concurrent TCP
connections capacity within the acceptance criteria. connections capacity within the validation criteria.
7.6. TCP/HTTPS Connections per second 7.6. TCP/HTTPS Connections per second
7.6.1. Objective 7.6.1. Objective
Using HTTPS traffic, determine the maximum sustainable SSL/TLS Using HTTPS traffic, determine the maximum sustainable SSL/TLS
session establishment rate supported by the DUT/SUT under different session establishment rate supported by the DUT/SUT under different
throughput load conditions. throughput load conditions.
Test iterations MUST include common cipher suites and key strengths Test iterations MUST include common cipher suites and key strengths
skipping to change at page 34, line 21 skipping to change at page 34, line 28
3. ECDHE-ECDSA-AES256-GCM-SHA384 with Secp521 (Signature Hash 3. ECDHE-ECDSA-AES256-GCM-SHA384 with Secp521 (Signature Hash
Algorithm: ecdsa_secp384r1_sha384 and Supported group: sepc521r1) Algorithm: ecdsa_secp384r1_sha384 and Supported group: sepc521r1)
4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash 4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash
Algorithm: rsa_pkcs1_sha384 and Supported group: secp256) Algorithm: rsa_pkcs1_sha384 and Supported group: secp256)
The client MUST negotiate HTTPS 1.1 and close the connection with FIN The client MUST negotiate HTTPS 1.1 and close the connection with FIN
immediately after completion of one transaction. In each test immediately after completion of one transaction. In each test
iteration, client MUST send GET command requesting a fixed HTTPS iteration, client MUST send GET command requesting a fixed HTTPS
response object size. The RECOMMENDED object sizes are 1, 2, 4, 16, response object size. The RECOMMENDED object sizes are 1, 2, 4, 16,
64 Kbyte. 64 KByte.
7.6.3.3. Test Results Acceptance Criteria 7.6.3.3. Test Results Validation Criteria
The following test Criteria is defined as test results acceptance The following test Criteria is defined as test results validation
criteria: criteria:
a. Number of failed Application transactions MUST be less than a. Number of failed Application transactions (receiving any HTTP
0.001% (1 out of 100,000 transactions) of attempt transactions response code other than 200 OK) MUST be less than 0.001% (1 out
of 100,000 transactions) of attempt transactions
b. Number of Terminated TCP connections due to unexpected TCP RST b. Number of Terminated TCP connections due to unexpected TCP RST
sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
connections) of total initiated TCP connections connections) of total initiated TCP connections
c. During the sustain phase, traffic should be forwarded at a c. During the sustain phase, traffic should be forwarded at a
constant rate constant rate
d. Concurrent TCP connections SHOULD be constant during steady d. Concurrent TCP connections SHOULD be constant during steady
state. This confirms that the DUT open and close the TCP state. This confirms that the DUT open and close the TCP
skipping to change at page 35, line 24 skipping to change at page 35, line 31
Verify the link status of all connected physical interfaces. All Verify the link status of all connected physical interfaces. All
interfaces are expected to be in "UP" status. interfaces are expected to be in "UP" status.
Configure traffic load profile of the test equipment to establish Configure traffic load profile of the test equipment to establish
"Initial connections per second" as defined in Section 7.6.3.2. The "Initial connections per second" as defined in Section 7.6.3.2. The
traffic load profile CAN be defined as described in Section 4.3.4. traffic load profile CAN be defined as described in Section 4.3.4.
The DUT/SUT SHOULD reach the "Initial connections per second" before The DUT/SUT SHOULD reach the "Initial connections per second" before
the sustain phase. The measured KPIs during the sustain phase MUST the sustain phase. The measured KPIs during the sustain phase MUST
meet the acceptance criteria a, b, c, and d defined in meet the validation criteria a, b, c, and d defined in
Section 7.6.3.3. Section 7.6.3.3.
If the KPI metrics do not meet the acceptance criteria, the test If the KPI metrics do not meet the validation criteria, the test
procedure MUST NOT be continued to "Step 2". procedure MUST NOT be continued to "Step 2".
7.6.4.2. Step 2: Test Run with Target Objective 7.6.4.2. Step 2: Test Run with Target Objective
Configure test equipment to establish "Target connections per second" Configure test equipment to establish "Target connections per second"
defined in the parameters table. The test equipment SHOULD follow defined in the parameters table. The test equipment SHOULD follow
the traffic load profile definition as described in Section 4.3.4. the traffic load profile definition as described in Section 4.3.4.
During the ramp up and sustain phase, other KPIs such as throughput, During the ramp up and sustain phase, other KPIs such as throughput,
concurrent TCP connections and application transactions per second concurrent TCP connections and application transactions per second
MUST NOT reach the maximum value that the DUT/SUT can support. The MUST NOT reach the maximum value that the DUT/SUT can support. The
test results for specific test iteration SHOULD NOT be reported, if test results for specific test iteration SHOULD NOT be reported, if
the above mentioned KPI (especially throughput) reaches the maximum the above mentioned KPI (especially throughput) reaches the maximum
value. (Example: If the test iteration with 64Kbyte of HTTPS value. (Example: If the test iteration with 64 KByte of HTTPS
response object size reached the maximum throughput limitation of the response object size reached the maximum throughput limitation of the
DUT, the test iteration can be interrupted and the result for 64kbyte DUT, the test iteration can be interrupted and the result for 64
SHOULD NOT be reported). KByte SHOULD NOT be reported).
The test equipment SHOULD start to measure and record all specified The test equipment SHOULD start to measure and record all specified
KPIs. The frequency of measurement MUST be less than 5 seconds. KPIs. The frequency of measurement SHOULD be 2 seconds. Continue
Continue the test until all traffic profile phases are completed. the test until all traffic profile phases are completed.
The DUT/SUT is expected to reach the desired target connections per The DUT/SUT is expected to reach the desired target connections per
second rate at the sustain phase. In addition, the measured KPIs second rate at the sustain phase. In addition, the measured KPIs
must meet all acceptance criteria. must meet all validation criteria.
Follow the step 3, if the KPI metrics do not meet the acceptance Follow the step 3, if the KPI metrics do not meet the validation
criteria. criteria.
7.6.4.3. Step 3: Test Iteration 7.6.4.3. Step 3: Test Iteration
Determine the maximum and average achievable connections per second Determine the maximum and average achievable connections per second
within the acceptance criteria. within the validation criteria.
7.7. HTTPS Throughput 7.7. HTTPS Throughput
7.7.1. Objective 7.7.1. Objective
Determine the throughput for HTTPS transactions varying the HTTPS Determine the throughput for HTTPS transactions varying the HTTPS
response object size. response object size.
Test iterations MUST include common cipher suites and key strengths Test iterations MUST include common cipher suites and key strengths
as well as forward looking stronger keys. Specific test iterations as well as forward looking stronger keys. Specific test iterations
skipping to change at page 37, line 25 skipping to change at page 37, line 39
2. ECDHE-RSA-AES128-GCM-SHA256 with RSA 2048 (Signature Hash 2. ECDHE-RSA-AES128-GCM-SHA256 with RSA 2048 (Signature Hash
Algorithm: rsa_pkcs1_sha256 and Supported group: sepc256) Algorithm: rsa_pkcs1_sha256 and Supported group: sepc256)
3. ECDHE-ECDSA-AES256-GCM-SHA384 with Secp521 (Signature Hash 3. ECDHE-ECDSA-AES256-GCM-SHA384 with Secp521 (Signature Hash
Algorithm: ecdsa_secp384r1_sha384 and Supported group: sepc521r1) Algorithm: ecdsa_secp384r1_sha384 and Supported group: sepc521r1)
4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash 4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash
Algorithm: rsa_pkcs1_sha384 and Supported group: secp256) Algorithm: rsa_pkcs1_sha384 and Supported group: secp256)
RECOMMENDED HTTPS response object size: 1KB, 2KB, 4KB, 16KB, 64KB, RECOMMENDED HTTPS response object size: 1 KByte, 2 KByte, 4 KByte, 16
256KB and mixed object defined in the table below. KByte, 64 KByte, 256 KByte and mixed object defined in the table
below.
+---------------------+---------------------+ +---------------------+---------------------+
| Object size (KByte) | Number of requests/ | | Object size (KByte) | Number of requests/ |
| | Weight | | | Weight |
+---------------------+---------------------+ +---------------------+---------------------+
| 0.2 | 1 | | 0.2 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
| 6 | 1 | | 6 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
| 8 | 1 | | 8 | 1 |
skipping to change at page 38, line 32 skipping to change at page 38, line 32
+---------------------+---------------------+ +---------------------+---------------------+
| 35 | 1 | | 35 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
| 59 | 1 | | 59 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
| 347 | 1 | | 347 | 1 |
+---------------------+---------------------+ +---------------------+---------------------+
Table 4: Mixed Objects Table 4: Mixed Objects
7.7.3.3. Test Results Acceptance Criteria 7.7.3.3. Test Results Validation Criteria
The following test Criteria is defined as test results acceptance The following test Criteria is defined as test results validation
criteria. Test results acceptance criteria MUST be monitored during criteria. Test results validation criteria MUST be monitored during
the whole sustain phase of the traffic load profile. the whole sustain phase of the traffic load profile.
a. Number of failed Application transactions MUST be less than a. Number of failed Application transactions (receiving any HTTP
0.001% (1 out of 100,000 transactions) of attempt transactions. response code other than 200 OK) MUST be less than 0.001% (1 out
of 100,000 transactions) of attempt transactions.
b. Traffic should be forwarded constantly. b. Traffic should be forwarded constantly.
c. The deviation of concurrent TCP connections MUST be less than 10% c. The deviation of concurrent TCP connections MUST be less than 10%
7.7.3.4. Measurement 7.7.3.4. Measurement
The KPI metrics MUST be reported for this test scenario: The KPI metrics MUST be reported for this test scenario:
Average Throughput, Average transactions per second, concurrent Average Throughput, Average transactions per second, concurrent
skipping to change at page 39, line 24 skipping to change at page 39, line 24
interfaces are expected to be in "UP" status. interfaces are expected to be in "UP" status.
Configure traffic load profile of the test equipment to establish Configure traffic load profile of the test equipment to establish
"initial throughput" as defined in the parameters Section 7.7.3.2. "initial throughput" as defined in the parameters Section 7.7.3.2.
The traffic load profile should be defined as described in The traffic load profile should be defined as described in
Section 4.3.4. The DUT/SUT SHOULD reach the "Initial Throughput" Section 4.3.4. The DUT/SUT SHOULD reach the "Initial Throughput"
during the sustain phase. Measure all KPI as defined in during the sustain phase. Measure all KPI as defined in
Section 7.7.3.4. Section 7.7.3.4.
The measured KPIs during the sustain phase MUST meet the acceptance The measured KPIs during the sustain phase MUST meet the validation
criteria "a" defined in Section 7.7.3.3. criteria "a" defined in Section 7.7.3.3.
If the KPI metrics do not meet the acceptance criteria, the test If the KPI metrics do not meet the validation criteria, the test
procedure MUST NOT be continued to "Step 2". procedure MUST NOT be continued to "Step 2".
7.7.4.2. Step 2: Test Run with Target Objective 7.7.4.2. Step 2: Test Run with Target Objective
The test equipment SHOULD start to measure and record all specified The test equipment SHOULD start to measure and record all specified
KPIs. The frequency of measurement MUST be less than 5 seconds. KPIs. The frequency of measurement SHOULD be 2 seconds. Continue
Continue the test until all traffic profile phases are completed. the test until all traffic profile phases are completed.
The DUT/SUT is expected to reach the desired "Target Throughput" at The DUT/SUT is expected to reach the desired "Target Throughput" at
the sustain phase. In addition, the measured KPIs MUST meet all the sustain phase. In addition, the measured KPIs MUST meet all
acceptance criteria. validation criteria.
Perform the test separately for each HTTPS response object size. Perform the test separately for each HTTPS response object size.
Follow step 3, if the KPI metrics do not meet the acceptance Follow step 3, if the KPI metrics do not meet the validation
criteria. criteria.
7.7.4.3. Step 3: Test Iteration 7.7.4.3. Step 3: Test Iteration
Determine the maximum and average achievable throughput within the Determine the maximum and average achievable throughput within the
acceptance criteria. Final test iteration MUST be performed for the validation criteria. Final test iteration MUST be performed for the
test duration defined in Section 4.3.4. test duration defined in Section 4.3.4.
7.8. HTTPS Transaction Latency 7.8. HTTPS Transaction Latency
7.8.1. Objective 7.8.1. Objective
Using HTTPS traffic, determine the average HTTPS transaction latency Using HTTPS traffic, determine the average HTTPS transaction latency
when DUT is running with sustainable HTTPS transactions per second when DUT is running with sustainable HTTPS transactions per second
supported by the DUT/SUT under different HTTPS response object size. supported by the DUT/SUT under different HTTPS response object size.
skipping to change at page 41, line 20 skipping to change at page 41, line 20
Initial objective for scenario 1: 10% of Target objective for Initial objective for scenario 1: 10% of Target objective for
scenario 1" scenario 1"
Initial objective for scenario 2: 10% of "Target objective for Initial objective for scenario 2: 10% of "Target objective for
scenario 2" scenario 2"
HTTPS transaction per TCP connection: test scenario 1 with single HTTPS transaction per TCP connection: test scenario 1 with single
transaction and the second scenario with 10 transactions transaction and the second scenario with 10 transactions
HTTPS 1.1 with GET command requesting a single 1, 16 or 64 Kbyte HTTPS 1.1 with GET command requesting a single 1, 16 or 64 KByte
object. For each test iteration, client MUST request a single HTTPS object. For each test iteration, client MUST request a single HTTPS
response object size. response object size.
7.8.3.3. Test Results Acceptance Criteria 7.8.3.3. Test Results Validation Criteria
The following test Criteria is defined as test results acceptance The following test Criteria is defined as test results validation
criteria. Test results acceptance criteria MUST be monitored during criteria. Test results validation criteria MUST be monitored during
the whole sustain phase of the traffic load profile. Ramp up and the whole sustain phase of the traffic load profile. Ramp up and
ramp down phase SHOULD NOT be considered. ramp down phase SHOULD NOT be considered.
Generic criteria: Generic criteria:
a. Number of failed Application transactions MUST be less than a. Number of failed Application transactions (receiving any HTTP
0.001% (1 out of 100,000 transactions) of attempt transactions. response code other than 200 OK) MUST be less than 0.001% (1 out
of 100,000 transactions) of attempt transactions.
b. Number of Terminated TCP connections due to unexpected TCP RST b. Number of Terminated TCP connections due to unexpected TCP RST
sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
connections) of total initiated TCP connections connections) of total initiated TCP connections
c. During the sustain phase, traffic should be forwarded at a c. During the sustain phase, traffic should be forwarded at a
constant rate. constant rate.
d. Concurrent TCP connections should be constant during steady d. Concurrent TCP connections should be constant during steady
state. This confirms the DUT opens and closes TCP connections at state. This confirms the DUT opens and closes TCP connections at
skipping to change at page 42, line 38 skipping to change at page 42, line 38
Verify the link status of the all connected physical interfaces. All Verify the link status of the all connected physical interfaces. All
interfaces are expected to be in "UP" status. interfaces are expected to be in "UP" status.
Configure traffic load profile of the test equipment to establish Configure traffic load profile of the test equipment to establish
"Initial objective" as defined in the parameters Section 7.8.3.2. "Initial objective" as defined in the parameters Section 7.8.3.2.
The traffic load profile can be defined as described in The traffic load profile can be defined as described in
Section 4.3.4. Section 4.3.4.
The DUT/SUT SHOULD reach the "Initial objective" before the sustain The DUT/SUT SHOULD reach the "Initial objective" before the sustain
phase. The measured KPIs during the sustain phase MUST meet the phase. The measured KPIs during the sustain phase MUST meet the
acceptance criteria a, b, c, d, e and f defined in Section 7.8.3.3. validation criteria a, b, c, d, e and f defined in Section 7.8.3.3.
If the KPI metrics do not meet the acceptance criteria, the test If the KPI metrics do not meet the validation criteria, the test
procedure MUST NOT be continued to "Step 2". procedure MUST NOT be continued to "Step 2".
7.8.4.2. Step 2: Test Run with Target Objective 7.8.4.2. Step 2: Test Run with Target Objective
Configure test equipment to establish "Target objective" defined in Configure test equipment to establish "Target objective" defined in
the parameters table. The test equipment SHOULD follow the traffic the parameters table. The test equipment SHOULD follow the traffic
load profile definition as described in Section 4.3.4. load profile definition as described in Section 4.3.4.
During the ramp up and sustain phase, other KPIs such as throughput, During the ramp up and sustain phase, other KPIs such as throughput,
concurrent TCP connections and application transactions per second concurrent TCP connections and application transactions per second
MUST NOT reach to the maximum value that the DUT/SUT can support. MUST NOT reach to the maximum value that the DUT/SUT can support.
The test results for specific test iterations SHOULD NOT be reported, The test results for specific test iterations SHOULD NOT be reported,
if the above mentioned KPI (especially throughput) reaches to the if the above mentioned KPI (especially throughput) reaches to the
maximum value. (Example: If the test iteration with 64Kbyte of HTTP maximum value. (Example: If the test iteration with 64 KByte of HTTP
response object size reached the maximum throughput limitation of the response object size reached the maximum throughput limitation of the
DUT, the test iteration MAY be interrupted and the result for 64kbyte DUT, the test iteration MAY be interrupted and the result for 64
SHOULD NOT be reported). KByte SHOULD NOT be reported).
The test equipment SHOULD start to measure and record all specified The test equipment SHOULD start to measure and record all specified
KPIs. The frequency of measurement MUST be less than 5 seconds. KPIs. The frequency of measurement SHOULD be 2 seconds. Continue
Continue the test until all traffic profile phases are completed. the test until all traffic profile phases are completed. DUT/SUT is
DUT/SUT is expected to reach the desired "Target objective" at the expected to reach the desired "Target objective" at the sustain
sustain phase. In addition, the measured KPIs MUST meet all phase. In addition, the measured KPIs MUST meet all validation
acceptance criteria. criteria.
Follow step 3, if the KPI metrics do not meet the acceptance Follow step 3, if the KPI metrics do not meet the validation
criteria. criteria.
7.8.4.3. Step 3: Test Iteration 7.8.4.3. Step 3: Test Iteration
Determine the maximum achievable connections per second within the Determine the maximum achievable connections per second within the
acceptance criteria and measure the latency values. validation criteria and measure the latency values.
7.9. Concurrent TCP/HTTPS Connection Capacity 7.9. Concurrent TCP/HTTPS Connection Capacity
7.9.1. Objective 7.9.1. Objective
Determine the maximum number of concurrent TCP connections that the Determine the maximum number of concurrent TCP connections that the
DUT/SUT sustains when using HTTPS traffic. DUT/SUT sustains when using HTTPS traffic.
7.9.2. Test Setup 7.9.2. Test Setup
skipping to change at page 44, line 44 skipping to change at page 44, line 44
connections per second during ramp up phase" connections per second during ramp up phase"
Ramp up time (in traffic load profile for "Initial concurrent Ramp up time (in traffic load profile for "Initial concurrent
connections"): "Initial concurrent connections" / "Maximum connections"): "Initial concurrent connections" / "Maximum
connections per second during ramp up phase" connections per second during ramp up phase"
The client MUST perform HTTPS transaction with persistence and each The client MUST perform HTTPS transaction with persistence and each
client can open multiple concurrent TCP connections per server client can open multiple concurrent TCP connections per server
endpoint IP. endpoint IP.
Each client sends 10 GET commands requesting 1Kbyte HTTPS response Each client sends 10 GET commands requesting 1 KByte HTTPS response
objects in the same TCP connections (10 transactions/TCP connection) objects in the same TCP connections (10 transactions/TCP connection)
and the delay (think time) between each transactions MUST be X and the delay (think time) between each transactions MUST be X
seconds. seconds.
X = ("Ramp up time" + "steady state time") /10 X = ("Ramp up time" + "steady state time") /10
The established connections SHOULD remain open until the ramp down The established connections SHOULD remain open until the ramp down
phase of the test. During the ramp down phase, all connections phase of the test. During the ramp down phase, all connections
SHOULD be successfully closed with FIN. SHOULD be successfully closed with FIN.
7.9.3.3. Test Results Acceptance Criteria 7.9.3.3. Test Results Validation Criteria
The following test Criteria is defined as test results acceptance The following test Criteria is defined as test results validation
criteria. Test results acceptance criteria MUST be monitored during criteria. Test results validation criteria MUST be monitored during
the whole sustain phase of the traffic load profile. the whole sustain phase of the traffic load profile.
a. Number of failed Application transactions MUST be less than a. Number of failed Application transactions (receiving any HTTP
0.001% (1 out of 100,000 transactions) of total attempted response code other than 200 OK) MUST be less than 0.001% (1 out
transactions of 100,000 transactions) of total attempted transactions
b. Number of Terminated TCP connections due to unexpected TCP RST b. Number of Terminated TCP connections due to unexpected TCP RST
sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
connections) of total initiated TCP connections connections) of total initiated TCP connections
c. During the sustain phase, traffic SHOULD be forwarded constantly c. During the sustain phase, traffic SHOULD be forwarded constantly
d. During the sustain phase, the maximum deviation (max. dev) of
application transaction latency or TTLB (Time To Last Byte) MUST
be less than 10%
7.9.3.4. Measurement 7.9.3.4. Measurement
Following KPI metrics MUST be reported for this test scenario: Following KPI metrics MUST be reported for this test scenario:
Average Throughput, max. Min. Avg. Concurrent TCP connections, TTLB/ Average Throughput, max. Min. Avg. Concurrent TCP connections, TTLB/
application transaction latency and average application transactions application transaction latency and average application transactions
per second per second
7.9.4. Test Procedures and expected Results 7.9.4. Test Procedures and expected Results
skipping to change at page 46, line 7 skipping to change at page 46, line 4
Verify the link status of all connected physical interfaces. All Verify the link status of all connected physical interfaces. All
interfaces are expected to be in "UP" status. interfaces are expected to be in "UP" status.
Configure test equipment to establish "initial concurrent TCP Configure test equipment to establish "initial concurrent TCP
connections" defined in Section 7.9.3.2. Except ramp up time, the connections" defined in Section 7.9.3.2. Except ramp up time, the
traffic load profile SHOULD be defined as described in Section 4.3.4. traffic load profile SHOULD be defined as described in Section 4.3.4.
During the sustain phase, the DUT/SUT SHOULD reach the "Initial During the sustain phase, the DUT/SUT SHOULD reach the "Initial
concurrent TCP connections". The measured KPIs during the sustain concurrent TCP connections". The measured KPIs during the sustain
phase MUST meet the acceptance criteria "a" and "b" defined in phase MUST meet the validation criteria "a" and "b" defined in
Section 7.9.3.3. Section 7.9.3.3.
If the KPI metrics do not meet the acceptance criteria, the test If the KPI metrics do not meet the validation criteria, the test
procedure MUST NOT be continued to "Step 2". procedure MUST NOT be continued to "Step 2".
7.9.4.2. Step 2: Test Run with Target Objective 7.9.4.2. Step 2: Test Run with Target Objective
Configure test equipment to establish "Target concurrent TCP Configure test equipment to establish "Target concurrent TCP
connections".The test equipment SHOULD follow the traffic load connections".The test equipment SHOULD follow the traffic load
profile definition (except ramp up time) as described in profile definition (except ramp up time) as described in
Section 4.3.4. Section 4.3.4.
During the ramp up and sustain phase, the other KPIs such as During the ramp up and sustain phase, the other KPIs such as
throughput, TCP connections per second and application transactions throughput, TCP connections per second and application transactions
per second MUST NOT reach to the maximum value that the DUT/SUT can per second MUST NOT reach to the maximum value that the DUT/SUT can
support. support.
The test equipment SHOULD start to measure and record KPIs defined in The test equipment SHOULD start to measure and record KPIs defined in
Section 7.9.3.4. The frequency of measurement MUST be less than 5 Section 7.9.3.4. The frequency of measurement SHOULD be 2 seconds.
seconds. Continue the test until all traffic profile phases are Continue the test until all traffic profile phases are completed.
completed.
The DUT/SUT is expected to reach the desired target concurrent The DUT/SUT is expected to reach the desired target concurrent
connections at the sustain phase. In addition, the measured KPIs connections at the sustain phase. In addition, the measured KPIs
MUST meet all acceptance criteria. MUST meet all validation criteria.
Follow step 3, if the KPI metrics do not meet the acceptance Follow step 3, if the KPI metrics do not meet the validation
criteria. criteria.
7.9.4.3. Step 3: Test Iteration 7.9.4.3. Step 3: Test Iteration
Determine the maximum and average achievable concurrent TCP Determine the maximum and average achievable concurrent TCP
connections within the acceptance criteria. connections within the validation criteria.
8. Formal Syntax 8. Formal Syntax
9. IANA Considerations 9. IANA Considerations
This document makes no request of IANA. This document makes no request of IANA.
Note to RFC Editor: this section may be removed on publication as an Note to RFC Editor: this section may be removed on publication as an
RFC. RFC.
10. Acknowledgements 10. Security Considerations
The primary goal of this document is to provide benchmarking
terminology and methodology for next-generation network security
devices. However, readers should be aware that there is some overlap
between performance and security issues. Specifically, the optimal
configuration for network security device performance may not be the
most secure, and vice-versa. The Cipher suites are recommended in
this document are just for test purpose only. The Cipher suite
recommendation for a real deployment is outside the scope of this
document.
11. Acknowledgements
Acknowledgements will be added in the future release. Acknowledgements will be added in the future release.
11. Contributors 12. Contributors
The authors would like to thank the many people that contributed The authors would like to thank the many people that contributed
their time and knowledge to this effort. their time and knowledge to this effort.
Specifically, to the co-chairs of the NetSecOPEN Test Methodology Specifically, to the co-chairs of the NetSecOPEN Test Methodology
working group and the NetSecOPEN Security Effectiveness working group working group and the NetSecOPEN Security Effectiveness working group
- Alex Samonte, Aria Eslambolchizadeh, Carsten Rossenhoevel and David - Alex Samonte, Aria Eslambolchizadeh, Carsten Rossenhoevel and David
DeSanto. DeSanto.
Additionally, the following people provided input, comments and spent Additionally, the following people provided input, comments and spent
time reviewing the myriad of drafts. If we have missed anyone the time reviewing the myriad of drafts. If we have missed anyone the
fault is entirely our own. Thanks to - Amritam Putatunda, Chao Guo, fault is entirely our own. Thanks to - Amritam Putatunda, Chao Guo,
Chris Chapman, Chris Pearson, Chuck McAuley, David White, Jurrie Van Chris Chapman, Chris Pearson, Chuck McAuley, David White, Jurrie Van
Den Breekel, Michelle Rhines, Rob Andrews, Samaresh Nair, and Tim Den Breekel, Michelle Rhines, Rob Andrews, Samaresh Nair, and Tim
Winters. Winters.
12. References 13. References
12.1. Normative References 13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
12.2. Informative References 13.2. Informative References
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, Transfer Protocol -- HTTP/1.1", RFC 2616,
DOI 10.17487/RFC2616, June 1999, DOI 10.17487/RFC2616, June 1999,
<https://www.rfc-editor.org/info/rfc2616>. <https://www.rfc-editor.org/info/rfc2616>.
[RFC2647] Newman, D., "Benchmarking Terminology for Firewall [RFC2647] Newman, D., "Benchmarking Terminology for Firewall
Performance", RFC 2647, DOI 10.17487/RFC2647, August 1999, Performance", RFC 2647, DOI 10.17487/RFC2647, August 1999,
<https://www.rfc-editor.org/info/rfc2647>. <https://www.rfc-editor.org/info/rfc2647>.
 End of changes. 127 change blocks. 
233 lines changed or deleted 244 lines changed or added

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