Benchmarking Methodology Working Group                      B. Balarajah
Internet-Draft
Intended status: Informational                           C. Rossenhoevel
Expires: March 13, May 3, 2021                                            EANTC AG
                                                              B. Monkman
                                                              NetSecOPEN
                                                       September 9,
                                                        October 30, 2020

    Benchmarking Methodology for Network Security Device Performance
                  draft-ietf-bmwg-ngfw-performance-04
                  draft-ietf-bmwg-ngfw-performance-05

Abstract

   This document provides benchmarking terminology and methodology for
   next-generation network security devices including next-generation
   firewalls (NGFW), next-generation intrusion detection and prevention solutions (IDS/
   IPS)
   systems (NGIDS/NGIPS) and unified threat management (UTM)
   implementations.  This document aims to strongly improve the
   applicability, reproducibility, and transparency of benchmarks and to
   align the test methodology with today's increasingly complex layer 7
   application use cases.  The main areas covered in this document are
   test terminology, traffic profiles test configuration parameters, and benchmarking
   methodology for NGFWs NGFW and NGIDS/NGIPS to start with.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 13, May 3, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3   4
   2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Test Setup  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Testbed Configuration . . . . . . . . . . . . . . . . . .   4
     4.2.  DUT/SUT Configuration . . . . . . . . . . . . . . . . . .   5   6
       4.2.1.  Security Effectiveness Configuration  . . . . . . . .  11
     4.3.  Test Equipment Configuration  . . . . . . . . . . . . . .  10  12
       4.3.1.  Client Configuration  . . . . . . . . . . . . . . . .  10  12
       4.3.2.  Backend Server Configuration  . . . . . . . . . . . .  12  14
       4.3.3.  Traffic Flow Definition . . . . . . . . . . . . . . .  13  15
       4.3.4.  Traffic Load Profile  . . . . . . . . . . . . . . . .  14  16
   5.  Test Bed Considerations . . . . . . . . . . . . . . . . . . .  15  17
   6.  Reporting . . . . . . . . . . . . . . . . . . . . . . . . . .  15  18
     6.1.  Key Performance Indicators  . . . . . . . . . . . . . . .  17  20
   7.  Benchmarking Tests  . . . . . . . . . . . . . . . . . . . . .  18  21
     7.1.  Throughput Performance With NetSecOPEN Application Traffic Mix . . .  18  21
       7.1.1.  Objective . . . . . . . . . . . . . . . . . . . . . .  18  21
       7.1.2.  Test Setup  . . . . . . . . . . . . . . . . . . . . .  18  21
       7.1.3.  Test Parameters . . . . . . . . . . . . . . . . . . .  18  21
       7.1.4.  Test Procedures and Expected Results  . . . . . . . .  20  23
     7.2.  TCP/HTTP Connections Per Second . . . . . . . . . . . . .  21  24
       7.2.1.  Objective . . . . . . . . . . . . . . . . . . . . . .  21  24
       7.2.2.  Test Setup  . . . . . . . . . . . . . . . . . . . . .  21  24
       7.2.3.  Test Parameters . . . . . . . . . . . . . . . . . . .  22  24
       7.2.4.  Test Procedures and Expected Results  . . . . . . . .  23  26
     7.3.  HTTP Throughput . . . . . . . . . . . . . . . . . . . . .  24  27
       7.3.1.  Objective . . . . . . . . . . . . . . . . . . . . . .  24  27
       7.3.2.  Test Setup  . . . . . . . . . . . . . . . . . . . . .  24  27
       7.3.3.  Test Parameters . . . . . . . . . . . . . . . . . . .  25  27
       7.3.4.  Test Procedures and Expected Results  . . . . . . . .  27  29
     7.4.  TCP/HTTP Transaction Latency  . . . . . . . . . . . . . .  28  30
       7.4.1.  Objective . . . . . . . . . . . . . . . . . . . . . .  28  30
       7.4.2.  Test Setup  . . . . . . . . . . . . . . . . . . . . .  28  30
       7.4.3.  Test Parameters . . . . . . . . . . . . . . . . . . .  28  30
       7.4.4.  Test Procedures and Expected Results  . . . . . . . .  30  32

     7.5.  Concurrent TCP/HTTP Connection Capacity . . . . . . . . .  31  33
       7.5.1.  Objective . . . . . . . . . . . . . . . . . . . . . .  31  33
       7.5.2.  Test Setup  . . . . . . . . . . . . . . . . . . . . .  32  34
       7.5.3.  Test Parameters . . . . . . . . . . . . . . . . . . .  32  34
       7.5.4.  Test Procedures and Expected Results  . . . . . . . .  33  35
     7.6.  TCP/HTTPS Connections per Second  . . . . . . . . . . . .  34  36
       7.6.1.  Objective . . . . . . . . . . . . . . . . . . . . . .  34  36
       7.6.2.  Test Setup  . . . . . . . . . . . . . . . . . . . . .  35  37
       7.6.3.  Test Parameters . . . . . . . . . . . . . . . . . . .  35  37
       7.6.4.  Test Procedures and Expected Results  . . . . . . . .  36  38
     7.7.  HTTPS Throughput  . . . . . . . . . . . . . . . . . . . .  38  40
       7.7.1.  Objective . . . . . . . . . . . . . . . . . . . . . .  38  40
       7.7.2.  Test Setup  . . . . . . . . . . . . . . . . . . . . .  38  40
       7.7.3.  Test Parameters . . . . . . . . . . . . . . . . . . .  38  40
       7.7.4.  Test Procedures and Expected Results  . . . . . . . .  40  42
     7.8.  HTTPS Transaction Latency . . . . . . . . . . . . . . . .  41  43
       7.8.1.  Objective . . . . . . . . . . . . . . . . . . . . . .  41  43
       7.8.2.  Test Setup  . . . . . . . . . . . . . . . . . . . . .  41  43
       7.8.3.  Test Parameters . . . . . . . . . . . . . . . . . . .  41  43
       7.8.4.  Test Procedures and Expected Results  . . . . . . . .  43  45
     7.9.  Concurrent TCP/HTTPS Connection Capacity  . . . . . . . .  44  46
       7.9.1.  Objective . . . . . . . . . . . . . . . . . . . . . .  44  46
       7.9.2.  Test Setup  . . . . . . . . . . . . . . . . . . . . .  44  46
       7.9.3.  Test Parameters . . . . . . . . . . . . . . . . . . .  45  47
       7.9.4.  Test Procedures and Expected Results  . . . . . . . .  46  48
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  47  49
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  48  50
   10. Acknowledgements Contributors  . . . . . . . . . . . . . . . . . . . . . .  48
   11. Contributors . .  50
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  48  50
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  48  50
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  48  50
     12.2.  Informative References . . . . . . . . . . . . . . . . .  49  51
   Appendix A.  NetSecOPEN Basic Traffic Mix  Test Methodology - Security Effectiveness Evaluation  51
     A.1.  Test Objective  . . . . . . . . . . . .  49
   Authors' Addresses . . . . . . . . .  51
     A.2.  Testbed setup . . . . . . . . . . . . . .  58

1.  Introduction

   15 years have passed since IETF recommended test methodology and
   terminology for firewalls initially ([RFC2647], [RFC3511]).  The
   requirements for network security element performance and
   effectiveness have increased tremendously since then.  Security
   function implementations have evolved to more advanced areas and have
   diversified into intrusion detection and prevention, threat
   management, analysis of encrypted traffic, etc.  In an industry of
   growing importance, well-defined and reproducible key performance
   indicators (KPIs) are increasingly needed as they enable fair and
   reasonable comparison of network security functions.  All these
   reasons have led to the creation of a new next-generation firewall
   benchmarking document.

2.  Requirements

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", . . . . . . . .  52
     A.3.  Test Parameters . . . . . . . . . . . . . . . . . . . . .  52
       A.3.1.  DUT/SUT Configuration Parameters  . . . . . . . . . .  52
       A.3.2.  Test Equipment Configuration Parameters . . . . . . .  52
     A.4.  Test Results Validation Criteria  . . . . . . . . . . . .  52
     A.5.  Measurement . . . . . . . . . . . . . . . . . . . . . . .  53
     A.6.  Test Procedures and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119], [RFC8174] when, expected Results  . . . . . . . . . .  54
       A.6.1.  Step 1: Background traffic  . . . . . . . . . . . . .  54
       A.6.2.  Step 2: CVE emulation . . . . . . . . . . . . . . . .  54
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  54

1.  Introduction

   15 years have passed since IETF recommended test methodology and only when, they appear in all
   capitals, as shown here.

3.  Scope

   This document provides testing
   terminology and testing methodology for next-generation firewalls initially ([RFC2647], [RFC3511]).  The
   requirements for network security devices.  It covers security
   effectiveness configurations, followed by element performance benchmark
   testing.  This document and
   effectiveness have increased tremendously since then.  Security
   function implementations have evolved to more advanced areas and have
   diversified into intrusion detection and prevention, threat
   management, analysis of encrypted traffic, etc.  In an industry of
   growing importance, well-defined, and reproducible key performance
   indicators (KPIs) are increasingly needed as they enable fair and
   reasonable comparison of network security functions.  All these
   reasons have led to the creation of a new next-generation security
   device benchmarking document.

2.  Requirements

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119], [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

3.  Scope

   This document provides testing terminology and testing methodology
   for next-generation security devices.  It covers the validation of
   security effectiveness configurations of the security devices,
   followed by performance benchmark testing.  This document focuses on
   advanced, realistic, and reproducible testing methods.  Additionally,
   it describes test bed testbed environments, test tool requirements requirements, and test
   result formats.

4.  Test Setup

   Test setup defined in this document is applicable to all benchmarking
   test scenarios described in Section 7.

4.1.  Testbed Configuration

   Testbed configuration MUST ensure that any performance implications
   that are discovered during the benchmark testing aren't due to the
   inherent physical network limitations such as the number of physical
   links and forwarding performance capabilities (throughput and
   latency) of the network devise devices in the testbed.  For this reason,
   this document recommends avoiding external devices such as switches
   and routers in the testbed wherever possible.

   However, in the typical deployment, the security devices (Device
   Under Test/System Under Test) are connected to routers and switches
   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
   to MAC and ARP/ND (Neighbor Discovery) table lookup processes.
   Therefore, it is RECOMMENDED to connect aggregation switches or
   routers between test 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/
   SUT DUT/SUT ports, if the numbers of used ports are
   mismatched between test equipment and DUT/SUT.

   If the test equipment is capable of emulating layer 3 routing
   functionality and there is no need for a test equipment port
   aggregation, it is RECOMMENDED to configure the test setup as shown
   in Figure 2.

    +-------------------+      +-----------+      +--------------------+
    |Aggregation Switch/|      |           |      | Aggregation Switch/|
    | Router            +------+  DUT/SUT  +------+ Router             |
    |                   |      |           |      |                    |
    +----------+--------+      +-----------+      +--------+-----------+
               |                                           |
               |                                           |
   +-----------+-----------+                   +-----------+-----------+
   |                       |                   |                       |
   | +-------------------+ |                   | +-------------------+ |
   | | Emulated Router(s)| |                   | | Emulated Router(s)| |
   | |     (Optional)    | |                   | |     (Optional)    | |
   | +-------------------+ |                   | +-------------------+ |
   | +-------------------+ |                   | +-------------------+ |
   | |      Clients      | |                   | |      Servers      | |
   | +-------------------+ |                   | +-------------------+ |
   |                       |                   |                       |
   |    Test Equipment     |                   |    Test Equipment     |
   +-----------------------+                   +-----------------------+

                    Figure 1: Testbed Setup - Option 1

   +-----------------------+                   +-----------------------+
   | +-------------------+ |   +-----------+   | +-------------------+ |
   | | Emulated Router(s)| |   |           |   | | Emulated Router(s)| |
   | |    (Optional)     | +----- DUT/SUT  +-----+    (Optional)     | |
   | +-------------------+ |   |           |   | +-------------------+ |
   | +-------------------+ |   +-----------+   | +-------------------+ |
   | |     Clients       | |                   | |      Servers      | |
   | +-------------------+ |                   | +-------------------+ |
   |                       |                   |                       |
   |   Test Equipment      |                   |   Test Equipment      |
   +-----------------------+                   +-----------------------+

                    Figure 2: Testbed Setup - Option 2

4.2.  DUT/SUT Configuration

   A unique DUT/SUT configuration MUST be used for all benchmarking
   tests described in Section 7.  Since each DUT/SUT will have their own
   unique configuration, users SHOULD configure their device with the
   same parameters and security features that would be used in the
   actual deployment of the device or a typical deployment in order to
   achieve maximum security coverage.

   This document attempts to define the recommended security features
   which SHOULD be consistently enabled for all the benchmarking tests
   described in Section 7.  Table 1 and Table 2 below describes describe the sets
   of security feature list which for NGFW and NGIDS/NGIPS that SHOULD be
   configured on the DUT/SUT.

   Based on customer use case, users MAY enable or disable SSL
   inspection feature for "Throughput Performance with NetSecOPEN
   Traffic Mix" test scenario described in Section 7.1 DUT/SUT respectively.

   To improve repeatability, a summary of the DUT configuration
   including a description of all enabled DUT/SUT features MUST be
   published with the benchmarking results.

                                +------------------------+
                                |           NGFW         |
                +-------------- +-------------+----------+
                |               |             |          |
                |DUT Features   | RECOMMENDED | OPTIONAL |
                |               |             |          |
                +----------------------------------------+
                |SSL Inspection |     x       |          |
                +----------------------------------------+
                |IDS/IPS        |     x       |          |
                +----------------------------------------+
                |Anti Spyware   |     x       |          |
                +----------------------------------------+
                |Antivirus      |     x       |          |
                +----------------------------------------+
                |Anti Botnet    |     x       |          |
                +----------------------------------------+
                |Web Filtering  |             |    x     |
                +----------------------------------------+
                |DLP            |             |    x     |
                +----------------------------------------+
                |DDoS           |             |    x     |
                +----------------------------------------+
                |Certificate    |             |    x     |
                |Validation     |             |          |
                +----------------------------------------+
                |Logging and    |     x       |          |
                |Reporting      |             |          |
                +-------------- +------------------------+
                |Application    |     x       |          |
                |Identification |             |          |
                +---------------+-------------+----------+

                      Table 1: DUT/SUT Feature

   The following table provides a brief description of the security
   features.

   +------------------+------------------------------------------------+
   | DUT/SUT NGFW Security Features
                                +------------------------+
                                | Description       NGIDS/NGIPS      |
   +------------------+------------------------------------------------+
                +-----------------------------+----------+
                | SSL Inspection               | DUT/SUT intercept and decrypt inbound HTTPS             |          |
                |DUT Features   | traffic between servers and clients. Once the RECOMMENDED | OPTIONAL |
                | content inspection has been completed, DUT/SUT               |             |          | MUST encrypt the HTTPS traffic with ciphers
                +----------------------------------------+
                |SSL Inspection |     x       |          | and keys used
                +----------------------------------------+
                |Anti Spyware   |     x       |          |
                +----------------------------------------+
                |Antivirus      |     x       |          |
                +----------------------------------------+
                |Anti Botnet    |     x       |          |
                +----------------------------------------+
                |Logging and    |     x       |          |
                |Reporting      |             |          |
                +-------------+ +------------------------+
                |Application    |     x       |          |
                |Identification |             |          |
                +----------------------------------------+
                |Deep Packet    |     x       |          |
                |Inspection     |             |          |
                +----------------------------------------+
                |Anti Evasion   |     x       |          |
                +---------------+-------------+----------+

                  Table 2: NGIDS/NGIPS Security Features

   The following table provides a brief description of the security
   features.

   +------------------+------------------------------------------------+
   | DUT/SUT Features | Description                                    |
   +-------------------------------------------------------------------+
   | SSL Inspection   | DUT/SUT intercept and decrypt inbound HTTPS    |
   |                  | traffic between servers and clients. Once the  |
   |                  | content inspection has been completed, DUT/SUT |
   |                  | MUST encrypt the HTTPS traffic with ciphers    |
   |                  | and keys used by the clients and servers.      |
   +------------------+------------------------------------------------+
   +-------------------------------------------------------------------+
   | IDS/IPS          | DUT DUT/SUT MUST detect and block exploits targeting         |
   |                  | targeting known and unknown vulnerabilities across the    |
   |                  | across the monitored network.                  |
   +------------------+------------------------------------------------+
   +-------------------------------------------------------------------+
   | Anti Malware     | DUT DUT/SUT MUST detect and prevent the transmission of|            |
   |                  | transmission of malicious executable code and any associated  |
   |                  | any associated communications across the monitored network.       |
   |                  | monitored network. This includes data          |
   |                  | exfiltration as well as     |
   |                  | command and control   .|
   |                  | channels.                                      |
   +------------------+------------------------------------------------+
   +-------------------------------------------------------------------+
   | Anti Spyware     |Anti-Spyware is a subcategory of Anti Malware.  |
   |                  |Spyware transmits information without the user's|
   |                  |knowledge or permission. DUT/SUT MUST detect and|
   |                  |block initial infection or transmission of data.|
   +-------------------------------------------------------------------+
   | Anti Botnet      |DUT/SUT MUST detect traffic to or from botnets. |
   +-------------------------------------------------------------------+
   | Anti Evasion     |DUT/SUT MUST detect and mitigate attacks that   |
   |                  |have been obfuscated in some manner.            |
   +-------------------------------------------------------------------+
   | Web Filtering    | DUT DUT/SUT MUST detect and block malicious websites   | website|
   |                  | including defined classifications of website   |
   |                  | across the monitored network.                  |
   +------------------+------------------------------------------------+
   +-------------------------------------------------------------------+
   | DLP              | DUT DUT/SUT MUST detect and block the transmission of |
   |                  | of Personally Identifiable Information (PII) and   |
   |                  | and specific files across the monitored network.   |
   +------------------+------------------------------------------------+ network|
   +------------------+   ---------------------------------------------+
   | Certificate      | DUT DUT/SUT  MUST validate certifcates certificates used in encrypted|    |
   | Validation       | comunications encrypted communications across the monitored  |
   |                  | network.                                       |
   +------------------+------------------------------------------------+
   +-------------------------------------------------------------------+
   | Logging and      | DUT DUT/SUT MUST be able to log and report all traffic     |
   | Reporting        | traffic at the flow level across the monitored network.|
   +------------------+------------------------------------------------+ monitored.|
   +-------------------------------------------------------------------+
   | Application      | DUT DUT/SUT MUST detect known applications as defined      |
   | Identification   | defined within the traffic mix selected across the |
   |                  | the monitored network.                         |
   +------------------+------------------------------------------------+
   +------------------+-------------------------------------------------

                   Table 2: NGFW 3: Security Feature Description

   In summary, DUT/SUT SHOULD be configured as follows:

   o  All RECOMMENDED security inspection enabled

   o  Disposition of all flows of traffic are logged - Logging to an
      external device is permissible

   o  Detection of Common Vulnerabilities and Exposures (CVE) matching
      the following characteristics when searching the National
      Vulnerability Database (NVD)

      *  Common Vulnerability Scoring System (CVSS) Version: 2

      *  CVSS V2 Metrics: AV:N/Au:N/I:C/A:C

      *  AV=Attack Vector, Au=Authentication, I=Integrity and
         A=Availability

      *  CVSS V2 Severity: High (7-10)

      *  If doing a group test the published start date and published
         end date SHOULD be the same

   o  Geographical location filtering  Geographical location filtering and Application Identification and
      Control configured to be triggered based on a site or application
      from the defined traffic mix

   In addition, a realistic number of access control rules (ACL) MUST be
   configured on the DUT/SUT.  However, this is applicable only for the
   security devices where ACL's are configurable. configurable and also the ACL
   configuration on NGIDS/NGIPS devices is OPTIONAL.  This document
   determines the number of access policy rules for four different
   classes of DUT/SUT.  The classification of the DUT/SUT MAY be based
   on its maximum supported firewall throughput performance number
   defined in the vendor datasheet.  This document classifies the DUT/
   SUT in four different categories; namely Extra Small, Small, Medium,
   and Large.

   The RECOMMENDED throughput values for the following classes are:

   Extra Small (XS) - supported throughput less than 1Gbit/s

   Small (S) - supported throughput less than 5Gbit/s

   Medium (M) - supported throughput greater than 5Gbit/s and less than
   10Gbit/s

   Large (L) - supported throughput greater than 10Gbit/s

   The Access Control Rules (ACL) defined in Table 3 4 MUST be configured
   from top to bottom in the correct order as shown in the table.  The
   ACL entries MUST be configured in Forward Information Base (FIB)
   table of the DUT/SUT.  (Note: There will be differences between how
   security vendors implement ACL decision making.)  The configured ACL
   MUST NOT block the security and performance test traffic used for the
   benchmarking test scenarios.

                                                       +---------------+
                                                       | DUT/SUT       |
                                                       | Classification|
                                                       | # Rules       |
   +-----------+-----------+------------------+------------+---+---+---+
   |           | Match     |                  |        |   |   |   |   |
   | Rules Type| Criteria  |   Description    | Action | XS| S | M | L |
   +-------------------------------------------------------------------+
   |Application|Application| Any application  |  block | 5 | 10| 20| 50|
   |layer      |           | traffic NOT      |        |   |   |   |   |
   |           |           | included in the  |        |   |   |   |   |
   |           |           | test traffic     |        |   |   |   |   |
   +-----------------------+ ------------------------------------------+
   |Transport  |Src IP and | Any src IP subnet|  block | 25| 50|100|250|
   |layer      |TCP/UDP    | used in the test |        |   |   |   |   |
   |           |Dst ports  | AND any dst ports|        |   |   |   |   |
   |           |           | NOT used in the  |        |   |   |   |   |
   |           |           | test traffic     |        |   |   |   |   |
   +-------------------------------------------------------------------+
   |IP layer   |Src/Dst IP | Any src/dst IP   |  block | 25| 50|100|250|
   |           |           | subnet NOT used  |        |   |   |   |   |
   |           |           | in the test      |        |   |   |   |   |
   +-------------------------------------------------------------------+
   |Application|Application| Applications     |  allow | 10| 10| 10| 10|
   |layer      |           | included in the  |        |   |   |   |   |
   |           |           | test traffic     |        |   |   |   |   |
   +-------------------------------------------------------------------+
   |Transport  |Src IP and | Half of the src  |  allow |  1|  1|  1|  1|
   |layer      |TCP/UDP    | IP used in the   |        |   |   |   |   |
   |           |Dst ports  | test AND any dst |        |   |   |   |   |
   |           |           | ports used in the|        |   |   |   |   |
   |           |           | test traffic. One|        |   |   |   |   |
   |           |           | rule per subnet  |        |   |   |   |   |
   +-------------------------------------------------------------------+
   |IP layer   |Src IP     | The rest of the  |  allow |  1|  1|  1|  1|
   |           |           | src IP subnet    |        |   |   |   |   |
   |           |           | range used in the|        |   |   |   |   |
   |           |           | test. One rule   |        |   |   |   |   |
   |           |           | per subnet       |        |   |   |   |   |
   +-----------+-----------+------------------+--------+---+---+---+---+

                       Table 3: 4: DUT/SUT Access List

4.2.1.  Security Effectiveness Configuration

   The Security features (defined in table 1 and 2) of the DUT/SUT MUST
   be configured effectively in such a way to detect, prevent, and
   report the defined security Vulnerability sets.  This Section defines
   the selection of the security Vulnerability sets from Common
   Vulnerabilities and Exposures (CVE) list for the testing.  The
   vulnerability set MUST reflects a minimum of 500 CVEs from no older
   than 10 calendar years to the current year.  These CVEs SHOULD be
   selected with a focus on in-use software commonly found in business
   applications, with a Common Vulnerability Scoring System (CVSS)
   Severity of High (7-10).

   This Document is mainly focused on performance benchmarking.
   However, it is strongly RECOMMENDED to validate the security
   configuration of the DUT/SUT by evaluating the security effectiveness
   as a Prerequisite for performance benchmarking tests defined in the
   section 7.  The Methodology for evaluating Security effectiveness is
   defined in Appendix A.

4.3.  Test Equipment Configuration

   In general, test equipment allows configuring parameters in different
   protocol layers.  These parameters thereby influence the traffic
   flows which will be offered and impact performance measurements.

   This section specifies common test equipment configuration parameters
   applicable for all test scenarios defined in Section 7.  Any test
   scenario specific parameters are described under the test setup
   section of each test scenario individually.

4.3.1.  Client Configuration

   This section specifies which parameters SHOULD be considered while
   configuring clients using test equipment.  Also, this section
   specifies the RECOMMENDED values for certain parameters.

4.3.1.1.  TCP Stack Attributes

   The TCP stack SHOULD use a TCP Reno [RFC5681] variant, which include
   congestion avoidance, back off and windowing, fast retransmission,
   and fast recovery on every TCP connection between client and server
   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
   windows of 64 KByte.  Client initial congestion window MUST NOT
   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
   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
   port range SHOULD be in the range of 1024 - 65535.  Internal timeout
   SHOULD be dynamically scalable per RFC 793.  Client  The client SHOULD
   initiate and close TCP connections.  TCP connections MUST be closed
   via FIN.

4.3.1.2.  Client IP Address Space

   The sum of the client IP space SHOULD contain the following
   attributes.

   o  The IP blocks SHOULD consist of multiple unique, discontinuous
      static address blocks.

   o  A default gateway is permitted.

   o  The IPv4 Type of Service (ToS) byte or IPv6 traffic class should
      be set to '00' or '000000' respectively.

   The following equation can be used to determine the required total
   number of client IP addresses.

   Desired total number of client IP = Target throughput [Mbit/s] /
   Throughput per IP address [Mbit/s]

   Based on deployment and use case scenario, the value for "Throughput
   per IP address" can be varied.

   (Option 1)  DUT/SUT deployment scenario 1 : 6-7 Mbit/s per IP (e.g.
               1,400-1,700 IPs per 10Gbit/s throughput)

   (Option 2)  DUT/SUT deployment scenario 2 : 0.1-0.2 Mbit/s per IP
               (e.g.  50,000-100,000 IPs per 10Gbit/s throughput)

   Based on deployment and use case scenario, client IP addresses SHOULD
   be distributed between IPv4 and IPv6 type.  The Following options can
   be considered for a selection of traffic mix ratio.

   (Option 1)  100 % IPv4, no IPv6

   (Option 2)  80 % IPv4, 20% IPv6

   (Option 3)  50 % IPv4, 50% IPv6

   (Option 4)  20 % IPv4, 80% IPv6

   (Option 5)  no IPv4, 100% IPv6

4.3.1.3.  Emulated Web Browser Attributes

   The emulated web client contains attributes that will materially
   affect how traffic is loaded.  The objective is to emulate modern,
   typical browser attributes to improve realism of the result set.

   For HTTP traffic emulation, the emulated browser MUST negotiate HTTP
   1.1.  HTTP persistence MAY be enabled depending on the test scenario.
   The browser MAY open multiple TCP connections per Server endpoint IP
   at any time depending on how many sequential transactions are needed
   to be processed.  Within the TCP connection multiple transactions MAY
   be processed if the emulated browser has available connections.  The
   browser SHOULD advertise a User-Agent header.  Headers MUST be sent
   uncompressed.  The browser SHOULD enforce content length validation.

   For encrypted traffic, the following attributes SHALL define the
   negotiated encryption parameters.  The test clients MUST use TLSv1.2
   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
   SHOULD send TLS Extension Server Name Indication (SNI) information
   when opening a security tunnel.  Each client connection MUST perform
   a full handshake with server certificate and MUST NOT use session
   reuse or resumption.

   The following ciphers and keys are RECOMMENDED to use for HTTPS based
   benchmarking tests defined in Section 7.

   1.  ECHDE-ECDSA-AES128-GCM-SHA256 with Prime256v1 (Signature Hash
       Algorithm: ecdsa_secp256r1_sha256 and Supported group: sepc256r1)

   2.  ECDHE-RSA-AES128-GCM-SHA256 with RSA 2048 (Signature Hash
       Algorithm: rsa_pkcs1_sha256 and Supported group: sepc256)

   3.  ECDHE-ECDSA-AES256-GCM-SHA384 with Secp521 (Signature Hash
       Algorithm: ecdsa_secp384r1_sha384 and Supported group: sepc521r1)

   4.  ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash
       Algorithm: rsa_pkcs1_sha384 and Supported group: secp256)

   Note: The above ciphers and keys were those commonly used enterprise
   grade encryption cipher suites . suites.  It is recognised recognized that these will
   evolve over time.  Individual certification bodies SHOULD use ciphers
   and keys that reflect evolving use cases.  These choices MUST be
   documented in the resulting test reports with detailed information on
   the ciphers and keys used along with reasons for the choices.

4.3.2.  Backend Server Configuration

   This section specifies which parameters should be considered while
   configuring emulated backend servers using test equipment.

4.3.2.1.  TCP Stack Attributes

   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,
   server initial congestion window MUST NOT exceed 10 times the MSS.
   Delayed ACKs are permitted and the maximum server delayed ACK MUST
   NOT exceed 10 times the MSS before a forced ACK.

4.3.2.2.  Server Endpoint IP Addressing

   The sum of the server IP space SHOULD contain the following
   attributes.

   o  The server IP blocks SHOULD consist of unique, discontinuous
      static address blocks with one IP per Server Fully Qualified
      Domain Name (FQDN) endpoint per test port.

   o  A default gateway is permitted.  The IPv4 ToS byte and IPv6
      traffic class bytes should be set to '00' and '000000'
      respectively.

   o  The server IP addresses SHOULD be distributed between IPv4 and
      IPv6 with a ratio identical to the clients distribution ratio.

4.3.2.3.  HTTP / HTTPS Server Pool Endpoint Attributes

   The server pool for HTTP SHOULD listen on TCP port 80 and emulate
   HTTP version 1.1 with persistence.  The Server MUST advertise server
   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 KByte and
   MUST NOT use ticket resumption or Session ID reuse . reuse.  The server MUST
   listen on port TCP 443.  The server SHALL serve a certificate to the
   client.  The HTTPS server MUST check Host SNI information with the
   FQDN if the SNI is in use.  Cipher suite and key size on the server
   side MUST be configured smilar similar to the client side configuration
   described in Section 4.3.1.3.

4.3.3.  Traffic Flow Definition

   This section describes the traffic pattern between client and server
   endpoints.  At the beginning of the test, the server endpoint
   initializes and will be ready to accept connection states including
   initialization of the TCP stack as well as bound HTTP and HTTPS
   servers.  When a client endpoint is needed, it will initialize and be
   given attributes such as a MAC and IP address.  The behavior of the
   client is to sweep through the given server IP space, sequentially
   generating a recognizable service by the DUT.  Thus, a balanced, mesh
   between client endpoints and server endpoints will be generated in a
   client port server port combination.  Each client endpoint performs
   the same actions as other endpoints, with the difference being the
   source IP of the client endpoint and the target server IP pool.  The
   client MUST use the servers IP address or Fully Qualified Domain
   Names (FQDN) in Host Headers.For Headers.  For TLS the client MAY use Server Name
   Indication (SNI).

4.3.3.1.  Description of Intra-Client Behavior

   Client endpoints are independent of other clients that are
   concurrently executing.  When a client endpoint initiates traffic,
   this section describes how the client steps though through different
   services.  Once the test is initialized, the client endpoints SHOULD
   randomly hold (perform no operation) for a few milliseconds to allow
   for better randomization of the start of client traffic.  Each client
   will either open a new TCP connection or connect to a TCP persistence
   stack still open to that specific server.  At any point that the
   service profile may require encryption, a TLS encryption tunnel will
   form presenting the URL or IP address request to the server.  If
   using SNI, the server will then perform an SNI name check with the
   proposed FQDN compared to the domain embedded in the certificate.
   Only when correct, will the server process the HTTPS response object.
   The initial response object to the server MUST NOT have a fixed size;
   its size is based on benchmarking tests described in Section 7.
   Multiple additional sub-URLs (response objects on the service page)
   MAY be requested simultaneously.  This MAY be to the same server IP
   as the initial URL.  Each sub-object will also use a conical FQDN and
   URL path, as observed in the traffic mix used.

4.3.4.  Traffic Load Profile

   The loading of traffic is described in this section.  The loading of
   a traffic load profile has five distinct phases: Init, ramp up,
   sustain, ramp down, and collection.

   1.  During the Init phase, test bed testbed devices including the client and
       server endpoints should negotiate layer 2-3 connectivity such as
       MAC learning and ARP.  Only after successful MAC learning or ARP/
       ND resolution SHALL the test iteration move to the next phase.
       No measurements are made in this phase.  The minimum RECOMMEND
       time for Init phase is 5 seconds.  During this phase, the
       emulated clients SHOULD NOT initiate any sessions with the DUT/
       SUT, in contrast, the emulated servers should be ready to accept
       requests from DUT/SUT or from emulated clients.

   2.  In the ramp up phase, the test equipment SHOULD start to generate
       the test traffic.  It SHOULD use a set approximate number of
       unique client IP addresses actively to generate traffic.  The
       traffic SHOULD ramp from zero to desired target objective.  The
       target objective will be defined for each benchmarking test.  The
       duration for the ramp up phase MUST be configured long enough, so
       that the test equipment does not overwhelm DUT/SUT's supported
       performance metrics namely; connections per second, throughput,
       concurrent TCP connections, and application transactions per
       second.  No measurements are made in this phase.

   3.  In the sustain phase, the test equipment SHOULD continue
       generating traffic to constant target value for a constant number
       of active client IPs.  The mininum minimum RECOMMENDED time duration for
       sustain phase is 300 seconds.  This is the phase where
       measurements occur.

   4.  In the ramp down/close phase, no new connections are established,
       and no measurements are made.  The time duration for ramp up and
       ramp down phase SHOULD be the same.

   5.  The last phase is administrative and will occur when the test
       equipment merges and collates the report data.

5.  Test Bed Considerations

   This section recommends steps to control the test environment and
   test equipment, specifically focusing on virtualized environments and
   virtualized test equipment.

   1.  Ensure that any ancillary switching or routing functions between
       the system under test and the test equipment do not limit the
       performance of the traffic generator.  This is specifically
       important for virtualized components (vSwitches, vRouters).

   2.  Verify that the performance of the test equipment matches and
       reasonably exceeds the expected maximum performance of the system
       under test.

   3.  Assert that the test bed testbed characteristics are stable during the
       entire test session.  Several factors might influence stability
       specifically for virtualized test beds.  For example additional
       workloads in a virtualized system, load balancing balancing, and movement
       of virtual machines during the test, or simple issues such as
       additional heat created by high workloads leading to an emergency
       CPU performance reduction.

   Test bed

   Testbed reference pre-tests help to ensure that the maximum desired
   traffic generator aspects such as throughput, transaction per second,
   connection per second, concurrent connection connection, and latency.

   Once the desired maximum performance goals for the system under test
   have been identified, a safety margin of 10% SHOULD be added for
   throughput and subtracted for maximum latency and maximum packet
   loss.

   Test bed

   Testbed preparation may be performed either by configuring the DUT in
   the most trivial setup (fast forwarding) or without presence of the
   DUT.

6.  Reporting

   This section describes how the final report should be formatted and
   presented.  The final test report MAY have two major sections;
   Introduction and result sections.  The following attributes SHOULD be
   present in the introduction section of the test report.

   1.  The name of the NetSecOPEN traffic mix (see Appendix A) MUST be
       prominent.

   2.  The time and date of the execution of the test MUST be prominent.

   3.

   2.  Summary of testbed software and Hardware details

       A.  DUT  DUT/SUT Hardware/Virtual Configuration

           +  This section SHOULD clearly identify the make and model of
              the DUT DUT/SUT

           +  The port interfaces, including speed and link information
              MUST be documented.

           +  If the DUT DUT/SUT is a virtual Netwerk Virtual Network Function (VNF),
              host(server) hardware and software details, interface
              acceleration type such as DPDK and SR-IOV MUST be documented as
              well as cores used, RAM used, used CPU cores,
              used RAM, and the pinning / resource sharing configuration.  The Hypervisor (e.g.  Pinning details
              and NUMA Node) configuration MUST be documented.  The
              virtual components such as Hypervisor, virtual switch
              version MUST be also documented.

           +  Any additional hardware relevant to the DUT DUT/SUT such as
              controllers MUST be documented

       B.  DUT  DUT/SUT Software

           +  The operating system name MUST be documented

           +  The version MUST be documented

           +  The specific configuration MUST be documented

       C.  DUT  DUT/SUT Enabled Features
           +  Configured DUT/SUT features (see Table 1) 1 and Table 2) MUST
              be documented

           +  Attributes of those featured MUST be documented

           +  Any additional relevant information about features MUST be
              documented

       D.  Test equipment hardware and software

           +  Test equipment vendor name

           +  Hardware details including model number, interface type

           +  Test equipment firmware and test application software
              version

   4.

       E.  Key test parameters

           +  Used cipher suites and keys

           +  IPv4 and IPv6 traffic distribution

           +  Number of configured ACL

       F.  Details of application traffic mix used in the test scenario
           Throughput Performance With Application Traffic Mix
           (Section 7.1)

           +  Name of applications and layer 7 protocols

           +  Percentage of emulated traffic for each application and
              layer 7 protocols

           +  Percentage of encrypted traffic and used cipher suites and
              keys (The RECOMMENDED ciphers and keys are defined in
              Section 4.3.1.3)

           +  Used object sizes for each application and layer 7
              protocols

   3.  Results Summary / Executive Summary

       1.  Results SHOULD resemble a pyramid in how it is reported, with
           the introduction section documenting the summary of results
           in a prominent, easy to read block.

       2.  In the result section of the test report, the following
           attributes should be present for each test scenario.

           a.  KPIs MUST be documented separately for each test
               scenario.  The format of the KPI metrics should be
               presented as described in Section 6.1.

           b.  The next level of details SHOULD be graphs showing each
               of these metrics over the duration (sustain phase) of the
               test.  This allows the user to see the measured
               performance stability changes over time.

6.1.  Key Performance Indicators

   This section lists KPIs key performance indicators (KPIs) for overall
   benchmarking tests test scenarios.  All KPIs MUST be measured during the
   sustain phase of the traffic load profile described in Section 4.3.4.
   All KPIs MUST be measured from the result output of test equipment.

   o  Concurrent TCP Connections
      This key performance indicator KPI measures the average concurrent open TCP connections in
      the sustaining period.

   o  TCP Connections Per Second
      This key performance indicator KPI measures the average established TCP connections per
      second in the sustaining period.  For "TCP/
      HTTP(S) Connection Per Second" benchmarking test scenario, the  Also this KPI
      is measured measures average
      established and terminated TCP connections per second simultaneously.
      simultaneously for the test scenarios "TCP/HTTP(S) Connection Per
      Second" defined in Section 7.2 and Section 7.6.

   o  Application Transactions Per Second
      This key performance indicator KPI measures the average successfully completed application
      transactions per second in the sustaining period.

   o  TLS Handshake Rate
      This key performance indicator KPI measures the average TLS 1.2 or higher session formation
      rate within the sustaining period.

   o  Throughput
      This key performance indicator KPI measures the average Layer 2 throughput within the
      sustaining period as well as average packets per seconds within
      the same period.  The value of throughput SHOULD be presented in
      Gbit/s rounded to two places of precision with a more specific
      Kbit/s in parenthesis.  Optionally, goodput MAY also be logged as
      an average goodput rate measured over the same period.  Goodput
      result SHALL also be presented in the same format as throughput.

   o  URL Response time / Time to Last Byte (TTLB)
      This key performance indicator KPI measures the minimum, average and maximum per URL
      response time in the sustaining period.  The latency is measured
      at Client and in this case case, would be the time duration between
      sending a GET request from Client and the receival of the complete
      response from the server.

   o  Time to First Byte (TTFB)
      This key performance indicator KPI will measure minimum, average and maximum the time to
      first byte.  TTFB is the elapsed time between sending the SYN
      packet from the client and receiving the first byte of application
      date from the DUT/SUT.  TTFB SHOULD be expressed in millisecond.

7.  Benchmarking Tests

7.1.  Throughput Performance With NetSecOPEN Application Traffic Mix

7.1.1.  Objective

   Using NetSecOPEN a relevant application traffic mix, determine the maximum
   sustainable throughput performance supported by the DUT/SUT. (see Appendix A

   Based on customer use case, users can choose the application traffic
   mix for this test.  The details about the traffic mix)

   This test scenario is RECOMMENDED to perform twice; one with SSL
   inspection feature enabled and mix MUST be
   documented in the second scenario report.  At least the following traffic mix details
   MUST be documented and reported together with SSL
   inspection feature disabled on the DUT/SUT. test results:

      Name of applications and layer 7 protocols

      Percentage of emulated traffic for each application and layer 7
      protocols

      Percentage of encrypted traffic and used cipher suites and keys
      (The RECOMMENDED ciphers and keys are defined in Section 4.3.1.3)

      Used object sizes for each application and layer 7 protocols

7.1.2.  Test Setup

   Test bed

   Testbed setup MUST be configured as defined in Section 4.  Any test
   scenario specific test bed configuration changes MUST be documented.

7.1.3.  Test Parameters

   In this section, the test scenario specific parameters SHOULD be
   defined.

7.1.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT parameters MUST conform to the requirements defined in
   Section 4.2.  Any configuration changes for this specific test
   scenario MUST be documented.

7.1.3.2.  Test Equipment  In case the DUT is configured without
   SSL inspection feature, the test report MUST explain the implications
   of this to the relevant application traffic mix encrypted traffic.

7.1.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST conform to the
   requirements defined in Section 4.3.  Following parameters MUST be
   noted for this test scenario:

      Client IP address range defined in Section 4.3.1.2

      Server IP address range defined in Section 4.3.2.2

      Traffic distribution ratio between IPv4 and IPv6 defined in
      Section 4.3.1.2

      Target throughput: It can be defined based on requirements.
      Otherwise
      Otherwise, it represents aggregated line rate of interface(s) used
      in the DUT/SUT

      Initial throughput: 10% of the "Target throughput"

      One of the ciphers and keys defined in Section 4.3.1.3 are
      RECOMMENDED to use for this test scenarios. scenario.

7.1.3.3.  Traffic Profile

   Traffic profile: Test scenario MUST be run with a single relevant
   application traffic mix profile (see Appendix A for details about traffic mix).
   The name of the NetSecOPEN traffic mix MUST be documented. profile.

7.1.3.4.  Test Results Validation Criteria

   The following test Criteria is defined as test results validation
   criteria.  Test results validation criteria MUST be monitored during
   the whole sustain phase of the traffic load profile.

   a.  Number of failed application transactions (receiving any HTTP
       response code other than 200 OK) MUST be less than 0.001% (1 out
       of 100,000 transactions) of total attempt transactions

   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
       connections) of total initiated TCP connections

   c.  Maximum deviation (max. dev) of URL Response Time or TTLB (Time
       To Last Byte) MUST be less than X (The value for "X" will be
       finalized and updated after completion of PoC test)
       The following equation MUST be used to calculate the deviation of
       URL Response Time or TTLB
       max. dev = max((avg_latency - min_latency),(max_latency -
       avg_latency)) / (Initial latency)
       Where, the initial latency is calculated using the following
       equation.  For this calculation, the latency values (min', avg'
       and max') MUST be measured during test procedure step 1 as
       defined in Section 7.1.4.1.
       The variable latency represents URL Response Time or TTLB.
       Initial latency:= min((avg' latency - min' latency) | (max'
       latency - avg' latency))

   d.  Maximum value of Time to First Byte (TTFB) MUST be less than X

7.1.3.5.  Measurement

   Following KPI metrics MUST be reported for this test scenario.

   Mandatory KPIs: average Throughput, TTFB (minimum, average average, and
   maximum), TTLB (minimum, average average, and maximum) and average
   Application Transactions Per Second

   Note: TTLB MUST be reported along with min, max max, and avg object size
   used in the traffic profile.

   Optional KPIs: average TCP Connections Per Second and average TLS
   Handshake Rate

7.1.4.  Test Procedures and Expected Results

   The test procedures are designed to measure the throughput
   performance of the DUT/SUT at the sustaining period of traffic load
   profile.  The test procedure consists of three major steps.

7.1.4.1.  Step 1: Test Initialization and Qualification

   Verify the link status of the all connected physical interfaces.  All
   interfaces are expected to be in "UP" status.

   Configure traffic load profile of the test equipment to generate test
   traffic at the "Initial throughput" rate as described in 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
   DUT/SUT SHOULD reach the "Initial throughput" during the sustain
   phase.  Measure all KPI as defined in Section 7.1.3.5.  The measured
   KPIs during the sustain phase MUST meet validation criteria "a" and
   "b" defined in Section 7.1.3.4.

   If the KPI metrics do not meet the validation criteria, the test
   procedure MUST NOT be continued to step 2.

7.1.4.2.  Step 2: Test Run with Target Objective

   Configure test equipment to generate traffic at the "Target
   throughput" rate defined in the parameter table.  The test equipment
   SHOULD follow the traffic load profile definition as described in
   Section 4.3.4.  The test equipment SHOULD start to measure and record
   all specified KPIs.  The frequency of KPI metric measurements SHOULD
   be 2 seconds.  Continue the test until all traffic profile phases are
   completed.

   The DUT/SUT is expected to reach the desired target throughput during
   the sustain phase.  In addition, the measured KPIs MUST meet all
   validation criteria.  Follow step 3, if the KPI metrics do not meet
   the validation criteria.

7.1.4.3.  Step 3: Test Iteration

   Determine the maximum and average achievable throughput within the
   validation criteria.  Final test iteration MUST be performed for the
   test duration defined in Section 4.3.4.

7.2.  TCP/HTTP Connections Per Second

7.2.1.  Objective

   Using HTTP traffic, determine the maximum sustainable TCP connection
   establishment rate supported by the DUT/SUT under different
   throughput load conditions.

   To measure connections per second, test iterations MUST use different
   fixed HTTP response object sizes defined in Section 7.2.3.2.

7.2.2.  Test Setup

   Test bed setup SHOULD be configured as defined in Section 4.  Any
   specific test bed configuration changes such as number of interfaces
   and interface type, etc.  MUST be documented.

7.2.3.  Test Parameters

   In this section, test scenario specific parameters SHOULD be defined.

7.2.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT parameters MUST conform to the requirements defined in
   Section 4.2.  Any configuration changes for this specific test
   scenario MUST be documented.

7.2.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST conform to the
   requirements defined in Section 4.3.  Following parameters MUST be
   documented for this test scenario:

   Client IP address range defined in Section 4.3.1.2

   Server IP address range defined in Section 4.3.2.2
   Traffic distribution ratio between IPv4 and IPv6 defined in
   Section 4.3.1.2

   Target connections per second: Initial value from product datasheet
   (if known)

   Initial connections per second: 10% of "Target connections per
   second" (an optional parameter for documentation)

   The client SHOULD negotiate HTTP 1.1 and close the connection with
   FIN immediately after completion of one transaction.  In each test
   iteration, client MUST send GET command requesting a fixed HTTP
   response object size.

   The RECOMMENDED response object sizes are 1, 2, 4, 16, 64 KByte

7.2.3.3.  Test Results Validation Criteria

   The following test Criteria is defined as test results validation
   criteria.  Test results validation criteria MUST be monitored during
   the whole sustain phase of the traffic load profile.

   a.  Number of failed Application transactions (receiving any HTTP
       response code other than 200 OK) MUST be less than 0.001% (1 out
       of 100,000 transactions) of total attempt transactions

   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
       connections) of total initiated TCP connections

   c.  During the sustain phase, traffic should be forwarded at a
       constant rate

   d.  Concurrent TCP connections MUST be constant during steady state
       and any deviation of concurrent TCP connections SHOULD be less
       than 10%. This confirms the DUT opens and closes TCP connections
       almost at the same rate

7.2.3.4.  Measurement

   Following KPI metric MUST be reported for each test iteration.

   average TCP Connections Per Second

7.2.4.  Test Procedures and Expected Results

   The test procedure is designed to measure the TCP connections per
   second rate of the DUT/SUT at the sustaining period of the traffic
   load profile.  The test procedure consists of three major steps.
   This test procedure MAY be repeated multiple times with different IP
   types; IPv4 only, IPv6 only and IPv4 and IPv6 mixed traffic
   distribution.

7.2.4.1.  Step 1: Test Initialization and Qualification

   Verify the link status of all connected physical interfaces.  All
   interfaces are expected to be in "UP" status.

   Configure the traffic load profile of the test equipment to establish
   "initial connections per second" as defined in the parameters
   Section 7.2.3.2.  The traffic load profile SHOULD be defined as
   described in Section 4.3.4.

   The DUT/SUT SHOULD reach the "Initial connections per second" before
   the sustain phase.  The measured KPIs during the sustain phase MUST
   meet validation criteria a, b, c, and d defined in Section 7.2.3.3.

   If the KPI metrics do not meet the validation criteria, the test
   procedure MUST NOT be continued to "Step 2".

7.2.4.2.  Step 2: Test Run with Target Objective

   Configure test equipment to establish "Target connections per second"
   defined in the parameters table.  The test equipment SHOULD follow
   the traffic load profile definition as described in Section 4.3.4.

   During the ramp up and sustain phase of each test iteration, other
   KPIs such as throughput, concurrent TCP connections and application
   transactions per second MUST NOT reach to the maximum value the DUT/
   SUT can support.  The test results for specific test iterations
   SHOULD NOT be reported, if the above mentioned KPI (especially
   throughput) reaches the maximum value.  (Example: If the test
   iteration with 64 KByte of HTTP response object size reached the
   maximum throughput limitation of the DUT, the test iteration MAY be
   interrupted and the result for 64 KByte SHOULD NOT be reported).

   The test equipment SHOULD start to measure and record all specified
   KPIs.  The frequency of measurement SHOULD be 2 seconds.  Continue
   the test until all traffic profile phases are completed.

   The DUT/SUT is expected to reach the desired target connections per
   second rate at the sustain phase.  In addition, the measured KPIs
   MUST meet all validation criteria.

   Follow step 3, if the KPI metrics do not meet the validation
   criteria.

7.2.4.3.  Step 3: Test Iteration

   Determine the maximum and average achievable connections per second
   within the validation criteria.

7.3.  HTTP Throughput

7.3.1.  Objective

   Determine the throughput for HTTP transactions varying the HTTP
   response object size.

7.3.2.  Test Setup

   Test bed setup SHOULD be configured as defined in Section 4.  Any
   specific test bed configuration changes such as number of interfaces
   and interface type, etc. must be documented.

7.3.3.  Test Parameters

   In this section, test scenario specific parameters SHOULD be defined.

7.3.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT parameters MUST conform to the requirements defined in
   Section 4.2.  Any configuration changes for this specific test
   scenario MUST be documented.

7.3.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST conform to the
   requirements defined in Section 4.3.  Following parameters MUST be
   documented for this test scenario:

   Client IP address range defined in Section 4.3.1.2

   Server IP address range defined in Section 4.3.2.2

   Traffic distribution ratio between IPv4 and IPv6 defined in
   Section 4.3.1.2
   Target Throughput: Initial value from product datasheet (if known)

   Initial Throughput: 10% of "Target Throughput" (an optional parameter
   for documentation)

   Number of HTTP response object requests (transactions) per
   connection: 10

   RECOMMENDED HTTP response object size: 1 KByte, 16 KByte, 64 KByte,
   256 KByte and mixed objects defined in the table

   +---------------------+---------------------+
   | Object size (KByte) | Number of requests/ |
   |                     | Weight              |
   +---------------------+---------------------+
   | 0.2                 | 1                   |
   +---------------------+---------------------+
   | 6                   | 1                   |
   +---------------------+---------------------+
   | 8                   | 1                   |
   +---------------------+---------------------+
   | 9                   | 1                   |
   +---------------------+---------------------+
   | 10                  | 1                   |
   +---------------------+---------------------+
   | 25                  | 1                   |
   +---------------------+---------------------+
   | 26                  | 1                   |
   +---------------------+---------------------+
   | 35                  | 1                   |
   +---------------------+---------------------+
   | 59                  | 1                   |
   +---------------------+---------------------+
   | 347                 | 1                   |
   +---------------------+---------------------+

                          Table 4: Mixed Objects

7.3.3.3.  Test Results Validation Criteria

   The following test Criteria is defined as test results validation
   criteria.  Test results validation criteria MUST be monitored during
   the whole sustain phase of the traffic load profile

   a.  Number of failed Application transactions (receiving any HTTP
       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.

   c.  Concurrent TCP connections MUST be constant during steady state
       and any deviation of concurrent TCP connections SHOULD be less
       than 10%. This confirms the DUT opens and closes TCP connections
       almost at the same rate

7.3.3.4.  Measurement

   The KPI metrics MUST be reported for this test scenario:

   average Throughput and average HTTP Transactions per Second

7.3.4.  Test Procedures and Expected Results

   The test procedure is designed to measure HTTP throughput of the DUT/
   SUT.  The test procedure consists of three major steps.  This test
   procedure MAY be repeated multiple times with different IPv4 and IPv6
   traffic distribution and HTTP response object sizes.

7.3.4.1.  Step 1: Test Initialization and Qualification

   Verify the link status of the all connected physical interfaces.  All
   interfaces are expected to be in "UP" status.

   Configure traffic load profile of the test equipment to establish
   "Initial Throughput" as defined in the parameters Section 7.3.3.2.

   The traffic load profile SHOULD be defined as described in
   Section 4.3.4.  The DUT/SUT SHOULD reach the "Initial Throughput"
   during the sustain phase.  Measure all KPI as defined in
   Section 7.3.3.4.

   The measured KPIs during the sustain phase MUST meet the validation
   criteria "a" defined in Section 7.3.3.3.

   If the KPI metrics do not meet the validation criteria, the test
   procedure MUST NOT be continued to "Step 2".

7.3.4.2.  Step 2: Test Run with Target Objective

   The test equipment SHOULD start to measure and record all specified
   KPIs.  The frequency of measurement SHOULD be 2 seconds.  Continue
   the test until all traffic profile phases are completed.

   The DUT/SUT is expected to reach the desired "Target Throughput" at
   the sustain phase.  In addition, the measured KPIs must meet all
   validation criteria.

   Perform the test separately for each HTTP response object size.

   Follow step 3, if the KPI metrics do not meet the validation
   criteria.

7.3.4.3.  Step 3: Test Iteration

   Determine the maximum and average achievable throughput within the
   validation criteria.  Final test iteration MUST be performed for the
   test duration defined in Section 4.3.4.

7.4.  TCP/HTTP Transaction Latency

7.4.1.  Objective

   Using HTTP traffic, determine the average HTTP transaction latency
   when DUT is running with sustainable HTTP transactions per second
   supported by the DUT/SUT under different HTTP response object sizes.

   Test iterations MUST be performed with different HTTP response object
   sizes in two different scenarios.one with a single transaction and
   the other with multiple transactions within a single TCP connection.
   For consistency both the single and multiple transaction test MUST be
   configured with HTTP 1.1.

   Scenario 1: The client MUST negotiate HTTP 1.1 and close the
   connection with FIN immediately after completion of a single
   transaction (GET and RESPONSE).

   Scenario 2: The client MUST negotiate HTTP 1.1 and close the
   connection FIN immediately after completion of 10 transactions (GET
   and RESPONSE) within a single TCP connection.

7.4.2.  Test Setup

   Test bed setup SHOULD be configured as defined in Section 4.  Any
   specific test bed configuration changes such as number of interfaces
   and interface type, etc.  MUST be documented.

7.4.3.  Test Parameters

   In this section, test scenario specific parameters SHOULD be defined.

7.4.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT parameters MUST conform to the requirements defined in
   Section 4.2.  Any configuration changes for this specific test
   scenario MUST be documented.

7.4.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST conform to the
   requirements defined in Section 4.3 . Following parameters MUST be
   documented for this test scenario:

   Client IP address range defined in Section 4.3.1.2

   Server IP address range defined in Section 4.3.2.2

   Traffic distribution ratio between IPv4 and IPv6 defined in
   Section 4.3.1.2

   Target objective for scenario 1: 50% of the maximum connection per
   second measured in test scenario TCP/HTTP Connections Per Second
   (Section 7.2)

   Target objective for scenario 2: 50% of the maximum throughput
   measured in test scenario HTTP Throughput (Section 7.3)

   Initial objective for scenario 1: 10% of Target objective for
   scenario 1" (an optional parameter for documentation)

   Initial objective for scenario 2: 10% of "Target objective for
   scenario 2" (an optional parameter for documentation)

   HTTP transaction per TCP connection: test scenario 1 with single
   transaction and the second scenario with 10 transactions

   HTTP 1.1 with GET command requesting a single object.  The
   RECOMMENDED object sizes are 1, 16 or 64 KByte.  For each test
   iteration, client MUST request a single HTTP response object size.

7.4.3.3.  Test Results Validation Criteria

   The following test Criteria is defined as test results validation
   criteria.  Test results validation criteria MUST be monitored during
   the whole sustain phase of the traffic load profile.  Ramp up and
   ramp down phase SHOULD NOT be considered.

   Generic criteria:

   a.  Number of failed Application transactions (receiving any HTTP
       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
       sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
       connections) of total initiated TCP connections

   c.  During the sustain phase, traffic should be forwarded at a
       constant rate.

   d.  Concurrent TCP connections MUST be constant during steady state
       and any deviation of concurrent TCP connections SHOULD be less
       than 10%. This confirms the DUT opens and closes TCP connections
       almost at the same rate

   e.  After ramp up the DUT MUST achieve the "Target objective" defined
       in the parameter Section 7.4.3.2 and remain in that state for the
       entire test duration (sustain phase).

7.4.3.4.  Measurement

   Following KPI metrics MUST be reported for each test scenario and
   HTTP response object sizes separately:

   TTFB (minimum, average and maximum) and TTLB (minimum, average and
   maximum)

   All KPI's are measured once the target throughput achieves the steady
   state.

7.4.4.  Test Procedures and Expected Results

   The test procedure is designed to measure the average application
   transaction latencies or TTLB when the DUT is operating close to 50%
   of its maximum achievable throughput or connections per second.  This
   test procedure CAN be repeated multiple times with different IP types
   (IPv4 only, IPv6 only and IPv4 and IPv6 mixed traffic distribution),
   HTTP response object sizes and single and multiple transactions per
   connection scenarios.

7.4.4.1.  Step 1: Test Initialization and Qualification

   Verify the link status of the all connected physical interfaces.  All
   interfaces are expected to be in "UP" status.

   Configure traffic load profile of the test equipment to establish
   "Initial objective" as defined in the parameters Section 7.4.3.2.
   The traffic load profile can be defined as described in
   Section 4.3.4.

   The DUT/SUT SHOULD reach the "Initial objective" before the sustain
   phase.  The measured KPIs during the sustain phase MUST meet the
   validation criteria a, b, c, d, e and f defined in Section 7.4.3.3.

   If the KPI metrics do not meet the validation criteria, the test
   procedure MUST NOT be continued to "Step 2".

7.4.4.2.  Step 2: Test Run with Target Objective

   Configure test equipment to establish "Target objective" defined in
   the parameters table.  The test equipment SHOULD follow the traffic
   load profile definition as described in Section 4.3.4.

   During the ramp up and sustain phase, other KPIs such as throughput,
   concurrent TCP connections and application transactions per second
   MUST NOT reach to the maximum value that the DUT/SUT can support.
   The test results for specific test iterations SHOULD NOT be reported,
   if the above mentioned KPI (especially throughput) reaches to the
   maximum value.  (Example: If the test iteration with 64 KByte of HTTP
   response object size reached the maximum throughput limitation of the
   DUT, the test iteration MAY be interrupted and the result for 64
   KByte SHOULD NOT be reported).

   The test equipment SHOULD start to measure and record all specified
   KPIs.  The frequency of measurement SHOULD be 2 seconds.  Continue
   the test until all traffic profile phases are completed.  DUT/SUT is
   expected to reach the desired "Target objective" at the sustain
   phase.  In addition, the measured KPIs MUST meet all validation
   criteria.

   Follow step 3, if the KPI metrics do not meet the validation
   criteria.

7.4.4.3.  Step 3: Test Iteration

   Determine the maximum achievable connections per second within the
   validation criteria and measure the latency values.

7.5.  Concurrent TCP/HTTP Connection Capacity

7.5.1.  Objective

   Determine the maximum number of concurrent TCP connections that the
   DUT/ SUT sustains when using HTTP traffic.

7.5.2.  Test Setup

   Test bed setup SHOULD be configured as defined in Section 4.  Any
   specific test bed configuration changes such as number of interfaces
   and interface type, etc. must be documented.

7.5.3.  Test Parameters

   In this section, test scenario specific parameters SHOULD be defined.

7.5.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT parameters MUST conform to the requirements defined in
   Section 4.2.  Any configuration changes for this specific test
   scenario MUST be documented.

7.5.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST conform to the
   requirements defined in Section 4.3.  Following parameters MUST be
   noted for this test scenario:

      Client IP address range defined in Section 4.3.1.2

      Server IP address range defined in Section 4.3.2.2

      Traffic distribution ratio between IPv4 and IPv6 defined in
      Section 4.3.1.2

      Target concurrent connection: Initial value from product datasheet
      (if known)

      Initial concurrent connection: 10% of "Target concurrent
      connection" (an optional parameter for documentation)

      Maximum connections per second during ramp up phase: 50% of
      maximum connections per second measured in test scenario TCP/HTTP
      Connections per second (Section 7.2)

      Ramp up time (in traffic load profile for "Target concurrent
      connection"): "Target concurrent connection" / "Maximum
      connections per second during ramp up phase"

      Ramp up time (in traffic load profile for "Initial concurrent
      connection"): "Initial concurrent connection" / "Maximum
      connections per second during ramp up phase"

   The client MUST negotiate HTTP 1.1 with persistence and each client
   MAY open multiple concurrent TCP connections per server endpoint IP.

   Each client sends 10 GET commands requesting 1 KByte HTTP response
   object in the same TCP connection (10 transactions/TCP connection)
   and the delay (think time) between the transaction MUST be X seconds.

   X = ("Ramp up time" + "steady state time") /10

   The established connections SHOULD remain open until the ramp down
   phase of the test.  During the ramp down phase, all connections
   SHOULD be successfully closed with FIN.

7.5.3.3.  Test Results Validation Criteria

   The following test Criteria is defined as test results validation
   criteria.  Test results validation criteria MUST be monitored during
   the whole sustain phase of the traffic load profile.

   a.  Number of failed Application transactions (receiving any HTTP
       response code other than 200 OK) MUST be less than 0.001% (1 out
       of 100,000 transaction) of total attempted transactions

   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
       connections) of total initiated TCP connections

   c.  During the sustain phase, traffic SHOULD be forwarded constantly

7.5.3.4.  Measurement

   Following KPI metric MUST be reported for this test scenario:

   average Concurrent TCP Connections

7.5.4.  Test Procedures and Expected Results

   The test procedure is designed to measure the concurrent TCP
   connection capacity of the DUT/SUT at the sustaining period of
   traffic load profile.  The test procedure consists of three major
   steps.  This test procedure MAY be repeated multiple times with
   different IPv4 and IPv6 traffic distribution.

7.5.4.1.  Step 1: Test Initialization and Qualification

   Verify the link status of the all connected physical interfaces.  All
   interfaces are expected to be in "UP" status.

   Configure test equipment to establish "Initial concurrent TCP
   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.

   During the sustain phase, the DUT/SUT SHOULD reach the "Initial
   concurrent TCP connections".  The measured KPIs during the sustain
   phase MUST meet the validation criteria "a" and "b" defined in
   Section 7.5.3.3.

   If the KPI metrics do not meet the validation criteria, the test
   procedure MUST NOT be continued to "Step 2".

7.5.4.2.  Step 2: Test Run with Target Objective

   Configure test equipment to establish "Target concurrent TCP
   connections".  The test equipment SHOULD follow the traffic load
   profile definition (except ramp up time) as described in
   Section 4.3.4.

   During the ramp up and sustain phase, the other KPIs such as
   throughput, TCP connections per second and application transactions
   per second MUST NOT reach to the maximum value that the DUT/SUT can
   support.

   The test equipment SHOULD start to measure and record KPIs defined in
   Section 7.5.3.4.  The frequency of measurement SHOULD be 2 seconds.
   Continue the test until all traffic profile phases are completed.

   The DUT/SUT is expected to reach the desired target concurrent
   connection at the sustain phase.  In addition, the measured KPIs must
   meet all validation criteria.

   Follow step 3, if the KPI metrics do not meet the validation
   criteria.

7.5.4.3.  Step 3: Test Iteration

   Determine the maximum and average achievable concurrent TCP
   connections capacity within the validation criteria.

7.6.  TCP/HTTPS Connections per Second

7.6.1.  Objective

   Using HTTPS traffic, determine the maximum sustainable SSL/TLS
   session establishment rate supported by the DUT/SUT under different
   throughput load conditions.

   Test iterations MUST include common cipher suites and key strengths
   as well as forward looking stronger keys.  Specific test iterations
   MUST include ciphers and keys defined in Section 7.6.3.2.

   For each cipher suite and key strengths, test iterations MUST use a
   single HTTPS response object size defined in the test equipment
   configuration parameters Section 7.6.3.2 to measure connections per
   second performance under a variety of DUT Security inspection load
   conditions.

7.6.2.  Test Setup

   Test bed setup SHOULD be configured as defined in Section 4.  Any
   specific test bed configuration changes such as number of interfaces
   and interface type, etc.  MUST be documented.

7.6.3.  Test Parameters

   In this section, test scenario specific parameters SHOULD be defined.

7.6.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT parameters MUST conform to the requirements defined in
   Section 4.2.  Any configuration changes for this specific test
   scenario MUST be documented.

7.6.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST conform to the
   requirements defined in Section 4.3.  Following parameters MUST be
   documented for this test scenario:

   Client IP address range defined in Section 4.3.1.2

   Server IP address range defined in Section 4.3.2.2

   Traffic distribution ratio between IPv4 and IPv6 defined in
   Section 4.3.1.2

   Target connections per second: Initial value from product datasheet
   (if known)

   Initial connections per second: 10% of "Target connections per
   second" (an optional parameter for documentation)

   RECOMMENDED ciphers and keys defined in Section 4.3.1.3
   The client MUST negotiate HTTPS 1.1 and close the connection with FIN
   immediately after completion of one transaction.  In each test
   iteration, client MUST send GET command requesting a fixed HTTPS
   response object size.  The RECOMMENDED object sizes are 1, 2, 4, 16,
   64 KByte.

7.6.3.3.  Test Results Validation Criteria

   The following test Criteria is defined as test results validation
   criteria:

   a.  Number of failed Application transactions (receiving any HTTP
       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
       sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
       connections) of total initiated TCP connections

   c.  During the sustain phase, traffic should be forwarded at a
       constant rate

   d.  Concurrent TCP connections MUST be constant during steady state
       and any deviation of concurrent TCP connections SHOULD be less
       than 10%. This confirms the DUT opens and closes TCP connections
       almost at the same rate

7.6.3.4.  Measurement

   Following KPI metrics MUST be reported for this test scenario:

   average TCP Connections Per Second, average TLS Handshake Rate (TLS
   Handshake Rate can be measured in the test scenario using 1KB object
   size)

7.6.4.  Test Procedures and Expected Results

   The test procedure is designed to measure the TCP connections per
   second rate of the DUT/SUT at the sustaining period of traffic load
   profile.  The test procedure consists of three major steps.  This
   test procedure MAY be repeated multiple times with different IPv4 and
   IPv6 traffic distribution.

7.6.4.1.  Step 1: Test Initialization and Qualification

   Verify the link status of all connected physical interfaces.  All
   interfaces are expected to be in "UP" status.

   Configure traffic load profile of the test equipment to establish
   "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.

   The DUT/SUT SHOULD reach the "Initial connections per second" before
   the sustain phase.  The measured KPIs during the sustain phase MUST
   meet the validation criteria a, b, c, and d defined in
   Section 7.6.3.3.

   If the KPI metrics do not meet the validation criteria, the test
   procedure MUST NOT be continued to "Step 2".

7.6.4.2.  Step 2: Test Run with Target Objective

   Configure test equipment to establish "Target connections per second"
   defined in the parameters table.  The test equipment SHOULD follow
   the traffic load profile definition as described in Section 4.3.4.

   During the ramp up and sustain phase, other KPIs such as throughput,
   concurrent TCP connections and application transactions per second
   MUST NOT reach the maximum value that the DUT/SUT can support.  The
   test results for specific test iteration SHOULD NOT be reported, if
   the above mentioned KPI (especially throughput) reaches the maximum
   value.  (Example: If the test iteration with 64 KByte of HTTPS
   response object size reached the maximum throughput limitation of the
   DUT, the test iteration can be interrupted and the result for 64
   KByte SHOULD NOT be reported).

   The test equipment SHOULD start to measure and record all specified
   KPIs.  The frequency of measurement SHOULD be 2 seconds.  Continue
   the test until all traffic profile phases are completed.

   The DUT/SUT is expected to reach the desired target connections per
   second rate at the sustain phase.  In addition, the measured KPIs
   must meet all validation criteria.

   Follow the step 3, if the KPI metrics do not meet the validation
   criteria.

7.6.4.3.  Step 3: Test Iteration

   Determine the maximum and average achievable connections per second
   within the validation criteria.

7.7.  HTTPS Throughput

7.7.1.  Objective

   Determine the throughput for HTTPS transactions varying the HTTPS
   response object size.

   Test iterations MUST include common cipher suites and key strengths
   as well as forward looking stronger keys.  Specific test iterations
   MUST include the ciphers and keys defined in the parameter
   Section 7.7.3.2.

7.7.2.  Test Setup

   Test bed setup SHOULD be configured as defined in Section 4.  Any
   specific test bed configuration changes such as number of interfaces
   and interface type, etc. must be documented.

7.7.3.  Test Parameters

   In this section, test scenario specific parameters SHOULD be defined.

7.7.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT parameters MUST conform to the requirements defined in
   Section 4.2.  Any configuration changes for this specific test
   scenario MUST be documented.

7.7.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST conform to the
   requirements defined in Section 4.3.  Following parameters MUST be
   documented for this test scenario:

   Client IP address range defined in Section 4.3.1.2

   Server IP address range defined in Section 4.3.2.2

   Traffic distribution ratio between IPv4 and IPv6 defined in
   Section 4.3.1.2

   Target Throughput: Initial value from product datasheet (if known)

   Initial Throughput: 10% of "Target Throughput" (an optional parameter
   for documentation)

   Number of HTTPS response object requests (transactions) per
   connection: 10
   RECOMMENDED ciphers and keys defined in Section 4.3.1.3

   RECOMMENDED HTTPS response object size: 1 KByte, 2 KByte, 4 KByte, 16
   KByte, 64 KByte, 256 KByte and mixed object defined in the table
   below.

   +---------------------+---------------------+
   | Object size (KByte) | Number of requests/ |
   |                     | Weight              |
   +---------------------+---------------------+
   | 0.2                 | 1                   |
   +---------------------+---------------------+
   | 6                   | 1                   |
   +---------------------+---------------------+
   | 8                   | 1                   |
   +---------------------+---------------------+
   | 9                   | 1                   |
   +---------------------+---------------------+
   | 10                  | 1                   |
   +---------------------+---------------------+
   | 25                  | 1                   |
   +---------------------+---------------------+
   | 26                  | 1                   |
   +---------------------+---------------------+
   | 35                  | 1                   |
   +---------------------+---------------------+
   | 59                  | 1                   |
   +---------------------+---------------------+
   | 347                 | 1                   |
   +---------------------+---------------------+

                          Table 5: Mixed Objects

7.7.3.3.  Test Results Validation Criteria

   The following test Criteria is defined as test results validation
   criteria.  Test results validation criteria MUST be monitored during
   the whole sustain phase of the traffic load profile.

   a.  Number of failed Application transactions (receiving any HTTP
       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.

   c.  Concurrent TCP connections MUST be constant during steady state
       and any deviation of concurrent TCP connections SHOULD be less
       than 10%. This confirms the DUT opens and closes TCP connections
       almost at the same rate

7.7.3.4.  Measurement

   The KPI metrics MUST be reported for this test scenario:

   average Throughput and average HTTPS Transactions Per Second

7.7.4.  Test Procedures and Expected Results

   The test procedure consists of three major steps.  This test
   procedure MAY be repeated multiple times with different IPv4 and IPv6
   traffic distribution and HTTPS response object sizes.

7.7.4.1.  Step 1: Test Initialization and Qualification

   Verify the link status of the all connected physical interfaces.  All
   interfaces are expected to be in "UP" status.

   Configure traffic load profile of the test equipment to establish
   "initial throughput" as defined in the parameters Section 7.7.3.2.

   The traffic load profile should be defined as described in
   Section 4.3.4.  The DUT/SUT SHOULD reach the "Initial Throughput"
   during the sustain phase.  Measure all KPI as defined in
   Section 7.7.3.4.

   The measured KPIs during the sustain phase MUST meet the validation
   criteria "a" defined in Section 7.7.3.3.

   If the KPI metrics do not meet the validation criteria, the test
   procedure MUST NOT be continued to "Step 2".

7.7.4.2.  Step 2: Test Run with Target Objective

   The test equipment SHOULD start to measure and record all specified
   KPIs.  The frequency of measurement SHOULD be 2 seconds.  Continue
   the test until all traffic profile phases are completed.

   The DUT/SUT is expected to reach the desired "Target Throughput" at
   the sustain phase.  In addition, the measured KPIs MUST meet all
   validation criteria.

   Perform the test separately for each HTTPS response object size.

   Follow step 3, if the KPI metrics do not meet the validation
   criteria.

7.7.4.3.  Step 3: Test Iteration

   Determine the maximum and average achievable throughput within the
   validation criteria.  Final test iteration MUST be performed for the
   test duration defined in Section 4.3.4.

7.8.  HTTPS Transaction Latency

7.8.1.  Objective

   Using HTTPS traffic, determine the average HTTPS transaction latency
   when DUT is running with sustainable HTTPS transactions per second
   supported by the DUT/SUT under different HTTPS response object size.

   Scenario 1: The client MUST negotiate HTTPS and close the connection
   with FIN immediately after completion of a single transaction (GET
   and RESPONSE).

   Scenario 2: The client MUST negotiate HTTPS and close the connection
   with FIN immediately after completion of 10 transactions (GET and
   RESPONSE) within a single TCP connection.

7.8.2.  Test Setup

   Test bed setup SHOULD be configured as defined in Section 4.  Any
   specific test bed configuration changes such as number of interfaces
   and interface type, etc.  MUST be documented.

7.8.3.  Test Parameters

   In this section, test scenario specific parameters SHOULD be defined.

7.8.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT parameters MUST conform to the requirements defined in
   Section 4.2.  Any configuration changes for this specific test
   scenario MUST be documented.

7.8.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST conform to the
   requirements defined in Section 4.3.  Following parameters MUST be
   documented for this test scenario:

   Client IP address range defined in Section 4.3.1.2

   Server IP address range defined in Section 4.3.2.2
   Traffic distribution ratio between IPv4 and IPv6 defined in
   Section 4.3.1.2

   RECOMMENDED cipher suites and key sizes defined in Section 4.3.1.3

   Target objective for scenario 1: 50% of the maximum connections per
   second measured in test scenario TCP/HTTPS Connections per second
   (Section 7.6)

   Target objective for scenario 2: 50% of the maximum throughput
   measured in test scenario HTTPS Throughput (Section 7.7)

   Initial objective for scenario 1: 10% of Target objective for
   scenario 1" (an optional parameter for documentation)

   Initial objective for scenario 2: 10% of "Target objective for
   scenario 2" (an optional parameter for documentation)

   HTTPS transaction per TCP connection: test scenario 1 with single
   transaction and the second scenario with 10 transactions

   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
   response object size.

7.8.3.3.  Test Results Validation Criteria

   The following test Criteria is defined as test results validation
   criteria.  Test results validation criteria MUST be monitored during
   the whole sustain phase of the traffic load profile.  Ramp up and
   ramp down phase SHOULD NOT be considered.

   Generic criteria:

   a.  Number of failed Application transactions (receiving any HTTP
       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
       sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000
       connections) of total initiated TCP connections

   c.  During the sustain phase, traffic should be forwarded at a
       constant rate.

   d.  Concurrent TCP connections MUST be constant during steady state
       and any deviation of concurrent TCP connections SHOULD be less
       than 10%. This confirms the DUT opens and closes TCP connections
       almost at the same rate

   e.  After ramp up the DUT MUST achieve the "Target objective" defined
       in the parameter Section 7.8.3.2 and remain in that state for the
       entire test duration (sustain phase).

7.8.3.4.  Measurement

   Following KPI metrics MUST be reported for each test scenario and
   HTTPS response object sizes separately:

   TTFB (minimum, average and maximum) and TTLB (minimum, average and
   maximum)

   All KPI's are measured once the target connections per second
   achieves the steady state.

7.8.4.  Test Procedures and Expected Results

   The test procedure is designed to measure average TTFB or TTLB when
   the DUT is operating close to 50% of its maximum achievable
   connections per second.  This test procedure can be repeated multiple
   times with different IP types (IPv4 only, IPv6 only and IPv4 and IPv6
   mixed traffic distribution), HTTPS response object sizes and single
   and multiple transactions per connection scenarios.

7.8.4.1.  Step 1: Test Initialization and Qualification

   Verify the link status of the all connected physical interfaces.  All
   interfaces are expected to be in "UP" status.

   Configure traffic load profile of the test equipment to establish
   "Initial objective" as defined in the parameters Section 7.8.3.2.
   The traffic load profile can be defined as described in
   Section 4.3.4.

   The DUT/SUT SHOULD reach the "Initial objective" before the sustain
   phase.  The measured KPIs during the sustain phase MUST meet the
   validation criteria a, b, c, d, e and f defined in Section 7.8.3.3.

   If the KPI metrics do not meet the validation criteria, the test
   procedure MUST NOT be continued to "Step 2".

7.8.4.2.  Step 2: Test Run with Target Objective

   Configure test equipment to establish "Target objective" defined in
   the parameters table.  The test equipment SHOULD follow the traffic
   load profile definition as described in Section 4.3.4.

   During the ramp up and sustain phase, other KPIs such as throughput,
   concurrent TCP connections and application transactions per second
   MUST NOT reach to the maximum value that the DUT/SUT can support.
   The test results for specific test iterations SHOULD NOT be reported,
   if the above mentioned KPI (especially throughput) reaches to the
   maximum value.  (Example: If the test iteration with 64 KByte of HTTP
   response object size reached the maximum throughput limitation of the
   DUT, the test iteration MAY be interrupted and the result for 64
   KByte SHOULD NOT be reported).

   The test equipment SHOULD start to measure and record all specified
   KPIs.  The frequency of measurement SHOULD be 2 seconds.  Continue
   the test until all traffic profile phases are completed.  DUT/SUT is
   expected to reach the desired "Target objective" at the sustain
   phase.  In addition, the measured KPIs MUST meet all validation
   criteria.

   Follow step 3, if the KPI metrics do not meet the validation
   criteria.

7.8.4.3.  Step 3: Test Iteration

   Determine the maximum achievable connections per second within the
   validation criteria and measure the latency values.

7.9.  Concurrent TCP/HTTPS Connection Capacity

7.9.1.  Objective

   Determine the maximum number of concurrent TCP connections that the
   DUT/SUT sustains when using HTTPS traffic.

7.9.2.  Test Setup

   Test bed setup SHOULD be configured as defined in Section 4.  Any
   specific test bed configuration changes such as number of interfaces
   and interface type, etc.  MUST be documented.

7.9.3.  Test Parameters

   In this section, test scenario specific parameters SHOULD be defined.

7.9.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT parameters MUST conform to the requirements defined in
   Section 4.2.  Any configuration changes for this specific test
   scenario MUST be documented.

7.9.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST conform to the
   requirements defined in Section 4.3.  Following parameters MUST be
   documented for this test scenario:

      Client IP address range defined in Section 4.3.1.2

      Server IP address range defined in Section 4.3.2.2

      Traffic distribution ratio between IPv4 and IPv6 defined in
      Section 4.3.1.2

      RECOMMENDED cipher suites and key sizes defined in Section 4.3.1.3

      Target concurrent connections: Initial value from product
      datasheet (if known)

      Initial concurrent connections: 10% of "Target concurrent
      connections" (an optional parameter for documentation)

      Connections per second during ramp up phase: 50% of maximum
      connections per second measured in test scenario TCP/HTTPS
      Connections per second (Section 7.6)

      Ramp up time (in traffic load profile for "Target concurrent
      connections"): "Target concurrent connections" / "Maximum
      connections per second during ramp up phase"

      Ramp up time (in traffic load profile for "Initial concurrent
      connections"): "Initial concurrent connections" / "Maximum
      connections per second during ramp up phase"

   The client MUST perform HTTPS transaction with persistence and each
   client can open multiple concurrent TCP connections per server
   endpoint IP.

   Each client sends 10 GET commands requesting 1 KByte HTTPS response
   objects in the same TCP connections (10 transactions/TCP connection)
   and the delay (think time) between each transactions MUST be X
   seconds.

   X = ("Ramp up time" + "steady state time") /10

   The established connections SHOULD remain open until the ramp down
   phase of the test.  During the ramp down phase, all connections
   SHOULD be successfully closed with FIN.

7.9.3.3.  Test Results Validation Criteria

   The following test Criteria is defined as test results validation
   criteria.  Test results validation criteria MUST be monitored during
   the whole sustain phase of the traffic load profile.

   a.  Number of failed Application transactions (receiving any HTTP
       response code other than 200 OK) MUST be less than 0.001% (1 out
       of 100,000 transactions) of total attempted transactions

   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
       connections) of total initiated TCP connections

   c.  During the sustain phase, traffic SHOULD be forwarded constantly

7.9.3.4.  Measurement

   Following KPI metric MUST be reported for this test scenario:

   average Concurrent TCP Connections

7.9.4.  Test Procedures and Expected Results

   The test procedure is designed to measure the concurrent TCP
   connection capacity of the DUT/SUT at the sustaining period of
   traffic load profile.  The test procedure consists of three major
   steps.  This test procedure MAY be repeated multiple times with
   different IPv4 and IPv6 traffic distribution.

7.9.4.1.  Step 1: Test Initialization and Qualification

   Verify the link status of all connected physical interfaces.  All
   interfaces are expected to be in "UP" status.

   Configure test equipment to establish "initial concurrent TCP
   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.

   During the sustain phase, the DUT/SUT SHOULD reach the "Initial
   concurrent TCP connections".  The measured KPIs during the sustain
   phase MUST meet the validation criteria "a" and "b" defined in
   Section 7.9.3.3.

   If the KPI metrics do not meet the validation criteria, the test
   procedure MUST NOT be continued to "Step 2".

7.9.4.2.  Step 2: Test Run with Target Objective

   Configure test equipment to establish "Target concurrent TCP
   connections".  The test equipment SHOULD follow the traffic load
   profile definition (except ramp up time) as described in
   Section 4.3.4.

   During the ramp up and sustain phase, the other KPIs such as
   throughput, TCP connections per second and application transactions
   per second MUST NOT reach to the maximum value that the DUT/SUT can
   support.

   The test equipment SHOULD start to measure and record KPIs defined in
   Section 7.9.3.4.  The frequency of measurement SHOULD be 2 seconds.
   Continue the test until all traffic profile phases are completed.

   The DUT/SUT is expected to reach the desired target concurrent
   connections at the sustain phase.  In addition, the measured KPIs
   MUST meet all validation criteria.

   Follow step 3, if the KPI metrics do not meet the validation
   criteria.

7.9.4.3.  Step 3: Test Iteration

   Determine the maximum and average achievable concurrent TCP
   connections within the validation criteria.

8.  IANA Considerations

   This document makes no request of IANA.

   Note to RFC Editor: this section may be removed on publication as an
   RFC.

9.  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 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.

10.  Acknowledgements

   Acknowledgements will be added in the future release.

11.  Contributors

   The authors would like to thank the many people that following individuals contributed
   their time and knowledge to this effort.

   Specifically, significantly to the co-chairs creation
   of the NetSecOPEN Test Methodology
   working group and the NetSecOPEN Security Effectiveness working group
   - this document:

   Alex Samonte, Amritam Putatunda, Aria Eslambolchizadeh, Carsten Rossenhoevel and David
   DeSanto.

   Additionally, the following people provided input, comments
   DeSanto, Jurrie Van Den Breekel, Ryan Liles, Samaresh Nair, Stephen
   Goudreault, and spent
   time reviewing Tim Otto

11.  Acknowledgements

   The authors wish to acknowledge the myriad members of drafts.  If we have missed anyone NetSecOPEN for their
   participation in the
   fault is entirely our own.  Thanks creation of this document.  Additionally the
   following members need to - Amritam Putatunda, be acknowledged:

   Anand Vijayan, Baski Mohan, Chao Guo, Chris Chapman, Brown, Chris Pearson, Chuck McAuley, David White, Jurrie Van
   Den Breekel, Michelle Rhines, Rob Andrews, Samaresh Nair, and Marshall,
   Jay Lindenauer, Michael Shannon, Mike Deichman, Ray Vinson, Ryan
   Riese, Tim Carlin, Tim
   Winters. Otto and Toulnay Orkun

12.  References

12.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

12.2.  Informative References

   [RFC2616]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
              Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
              Transfer Protocol -- HTTP/1.1", RFC 2616,
              DOI 10.17487/RFC2616, June 1999,
              <https://www.rfc-editor.org/info/rfc2616>.

   [RFC2647]  Newman, D., "Benchmarking Terminology for Firewall
              Performance", RFC 2647, DOI 10.17487/RFC2647, August 1999,
              <https://www.rfc-editor.org/info/rfc2647>.

   [RFC3511]  Hickman, B., Newman, D., Tadjudin, S., and T. Martin,
              "Benchmarking Methodology for Firewall Performance",
              RFC 3511, DOI 10.17487/RFC3511, April 2003,
              <https://www.rfc-editor.org/info/rfc3511>.

   [RFC5681]  Allman, M., Paxson, V., and E. Blanton, "TCP Congestion
              Control", RFC 5681, DOI 10.17487/RFC5681, September 2009,
              <https://www.rfc-editor.org/info/rfc5681>.

Appendix A.  NetSecOPEN Basic Traffic Mix

   A traffic mix for testing performance of next generation firewalls
   MUST scale to stress the DUT based on real-world conditions.  Test Methodology - Security Effectiveness Evaluation

A.1.  Test Objective

   This test methodology verifies the DUT/SUT is able to detect, prevent
   and report the vulnerabilities.

   In this test, background test traffic will be generated in order to achieve this
   utilize the following MUST DUT/SUT.  In parallel, the CVEs will be included:

   o  Clients connecting sent to multiple different server FQDNs per
      application

   o  Clients loading apps and pages with connections the DUT/
   SUT as encrypted and objects as well as clear text payload formats using a
   traffic generator.  The selection of the CVEs is described in
      specific orders

   o  Multiple unique certificates for HTTPS/TLS
   Section 4.2.1.

   o  A wide variety  Number of different object sizes

   o  Different URL paths blocked CVEs

   o  Mix  Number of HTTP and HTTPS

   A bypassed (nonblocked) CVEs

   o  Background traffic mix for testing performance of next generation firewalls
   MUST also facilitate application identification using different
   detection methods with and without decryption of (verify if the traffic.  Such
   as:

   o  HTTP HOST based application detection
   o  HTTPS/TLS Server Name Indication (SNI) background traffic
      is impacted while sending CVE toward DUT/SUT)

   o  Certificate Subject Common Name (CN)  Accuracy of DUT/SUT statistics in term of vulnerabilities
      reporting

A.2.  Testbed setup

   The mix same Testbed MUST be of sufficient complexity used for security effectiveness test and volume to render
   differences in individual apps as statistically insignificant.  For
   example, changes in like to like apps - such
   well as one type of video
   service vs. another both consist of larger objects whereas one news
   site vs. another both typically have more connections then other apps
   because of trackers and embedded advertising content.  To achieve
   sufficient complexity, a mix for benchmarking test cases defined in Section 7.

A.3.  Test Parameters

   In this section, the test scenario specific parameters SHOULD be
   defined.

A.3.1.  DUT/SUT Configuration Parameters

   DUT/SUT configuration Parameters MUST have:

   o  Thousands of URLs each client walks thru

   o  Hundreds of FQDNs each client connects conform to

   o  Hundreds of unique certificates the requirements
   defined in Section 4.2.  The same DUT configuration MUST be used for HTTPS/TLS

   o  Thousands of different object sizes per client
   Security effectiveness test and as well as for benchmarking test
   cases defined in orders matching
      applications Section 7.  The following is a description of what a popular application DUT/SUT MUST be configured in an
   enterprise traffic mix contains.

   Table 6 lists the FQDNs, number of transactions inline
   mode and bytes transferred
   as an example, client interactions with Office 365 Outlook, Word,
   Excel, PowerPoint, SharePoint all detected attack traffic MUST be dropped and Skype.

   +---------------------------------+------------+-------------+
   | Office365 FQDN                  | Bytes      | Transaction |
   +============================================================+
   | r1.res.office365.com            | 14,056,960 | 192         |
   +---------------------------------+------------+-------------+
   | s1-word-edit-15.cdn.office.net  | 6,731,019  | 22          |
   +---------------------------------+------------+-------------+
   | company1-my.sharepoint.com      | 6,269,492  | 42          |
   +---------------------------------+------------+-------------+
   | swx.cdn.skype.com               | 6,100,027  | 12          |
   +---------------------------------+------------+-------------+
   | static.sharepointonline.com     | 6,036,947  | 41          |
   +---------------------------------+------------+-------------+
   | spoprod-a.akamaihd.net          | 3,904,250  | 25          |
   +---------------------------------+------------+-------------+
   | s1-excel-15.cdn.office.net      | 2,767,941  | 16          |
   +---------------------------------+------------+-------------+
   | outlook.office365.com           | 2,047,301  | 86          |
   +---------------------------------+------------+-------------+
   | shellprod.msocdn.com            | 1,008,370  | 11          |
   +---------------------------------+------------+-------------+
   | word-edit.officeapps.live.com   | 932,080    | 25          |
   +---------------------------------+------------+-------------+
   | res.delve.office.com            | 760,146    | 2           |
   +---------------------------------+------------+-------------+
   | s1-powerpoint-15.cdn.office.net | 557,604    | 3           |
   +---------------------------------+------------+-------------+
   | appsforoffice.microsoft.com     | 511,171    | 5           |
   +---------------------------------+------------+-------------+
   | powerpoint.officeapps.live.com  | 471,625    | 14          |
   +---------------------------------+------------+-------------+
   | excel.officeapps.live.com       | 342,040    | 14          |
   +---------------------------------+------------+-------------+
   | s1-officeapps-15.cdn.office.net | 331,343    | 5           |
   +---------------------------------+------------+-------------+
   | webdir0a.online.lync.com        | 66,930     | 15          |
   +---------------------------------+------------+-------------+
   | portal.office.com               | 13,956     | 1           |
   +---------------------------------+------------+-------------+
   | config.edge.skype.com           | 6,911      | 2           |
   +---------------------------------+------------+-------------+
   | clientlog.portal.office.com     | 6,608      | 8           |
   +---------------------------------+------------+-------------+
   | webdir.online.lync.com          | 4,343      | 5           |
   +---------------------------------+------------+-------------+
   | graph.microsoft.com             | 2,289      | 2           |
   +---------------------------------+------------+-------------+
   | nam.loki.delve.office.com       | 1,812      | 5           |
   +---------------------------------+------------+-------------+
   | login.microsoftonline.com       | 464        | 2           |
   +---------------------------------+------------+-------------+
   | login.windows.net               | 232        | 1           |
   +---------------------------------+------------+-------------+

                            Table 6: Office365

   Clients the session
   Should be reset

A.3.2.  Test Equipment Configuration Parameters

   Test equipment configuration parameters MUST connect conform to multiple server FQDNs in the
   requirements defined in Section 4.3.  The same order Client and server IP
   ranges MUST be configured as
   real applications.  Connections used in the benchmarking test cases.  In
   addition, the following parameters MUST be made when documented for this test
   scenario:

   o  Background Traffic: 45% of maximum HTTP throughput and 45% of
      Maximum HTTPS throughput supported by the client is
   interacting DUT/SUT (measured with
      object size 64 KByte in the application test scenarios "HTTP(S) Throughput"
      defined in Section 7.3 and MUST NOT first setup up all
   connections.  Connections SHOULD stay open Section 7.7.

   o  RECOMMENDED CVE traffic transmission Rate: 10 CVEs per client for subsequent
   transactions second

   o  RECOMMEND to generate each CVE multiple times (sequentially) at 10
      CVEs per second

   o  Ciphers and Keys for the same FQDN similar to how a web browser behaves.
   Clients encrypted CVE traffic MUST use different URL Paths and Object sizes in orders the same
      cipher configured for HTTPS traffic related benchmarking test
      scenarios (Section 7.6 - Section 7.9)

A.4.  Test Results Validation Criteria

   The following test Criteria is defined as
   they are observed test results validation
   criteria.  Test results validation criteria MUST be monitored during
   the whole test duration.

   a.  Number of failed Application transaction in real Applications.  Clients MAY also setup
   multiple the background
       traffic MUST be less than 0.01% of attempted transactions

   b.  Number of Terminated TCP connections per FQDN of the background traffic
       (due to process multiple transactions unexpected TCP RST sent by DUT/SUT) MUST be less than
       0.01% of total initiated TCP connections in a
   sequence the background
       traffic

   c.  During the sustain phase, traffic should be forwarded at a
       constant rate

   d.  False positive MUST NOT occur in the same time.  Table 7 has background traffic

A.5.  Measurement

   Following KPI metrics MUST be reported for this test scenario:

   Mandatory KPIs:

   o  Blocked CVEs: It should be represented in the following ways:

      *  Number of blocked CVEs out of total CVEs

      *  Percentage of blocked CVEs

   o  Unblocked CVEs: It should be represented in the following ways:

      *  Number of unblocked CVEs out of total CVEs

      *  Percentage of unblocked CVEs

   o  Background traffic behavior: it should represent one of the
      followings ways:

      *  No impact (traffic transmission at a partial example sequence constant rate)

      *  Minor impact (e.g. small spikes- +/- 100 Mbit/s)

      *  Heavily impacted (e.g. large spikes and reduced the background
         throughput > 100 Mbit/s)

   o  DUT/SUT reporting accuracy: DUT/SUT MUST report all detected
      vulnerabilities.

   Optional KPIs:

   o  List of unblocked CVEs

A.6.  Test Procedures and expected Results

   The test procedure is designed to measure the Office 365 Word application transactions.

   +---------------------------------+----------------------+----------+
   | FQDN                            | URL Path             | Object   |
   |                                 |                      | size     |
   +===================================================================+
   | company1-my.sharepoint.com      | /personal...         | 23,132   |
   +---------------------------------+----------------------+----------+
   | word-edit.officeapps.live.com   | /we/WsaUpload.ashx   | 2        |
   +---------------------------------+----------------------+----------+
   | static.sharepointonline.com     | /bld/.../blank.js    | 454      |
   +---------------------------------+----------------------+----------+
   | static.sharepointonline.com     | /bld/.../            | 23,254   |
   |                                 | initstrings.js       |          |
   +---------------------------------+----------------------+----------+
   | static.sharepointonline.com     | /bld/.../init.js     | 292,740  |
   +---------------------------------+----------------------+----------+
   | company1-my.sharepoint.com      | /ScriptResource...   | 102,774  |
   +---------------------------------+----------------------+----------+
   | company1-my.sharepoint.com      | /ScriptResource...   | 40,329   |
   +---------------------------------+----------------------+----------+
   | company1-my.sharepoint.com      | /WebResource...      | 23,063   |
   +---------------------------------+----------------------+----------+
   | word-edit.officeapps.live.com   | /we/wordeditorframe. | 60,657   |
   |                                 | aspx...              |          |
   +---------------------------------+----------------------+----------+
   | static.sharepointonline.com     | /bld/_layouts/.../   | 454      |
   |                                 | blank.js             |          |
   +---------------------------------+----------------------+----------+
   | s1-word-edit-15.cdn.office.net  | /we/s/.../           | 19,201   |
   |                                 | EditSurface.css      |          |
   +---------------------------------+----------------------+----------+
   | s1-word-edit-15.cdn.office.net  | /we/s/.../           | 221,397  |
   |                                 | WordEditor.css       |          |
   +---------------------------------+----------------------+----------+
   | s1-officeapps-15.cdn.office.net | /we/s/.../           | 107,571  |
   |                                 | Microsoft            |          |
   |                                 | Ajax.js              |          |
   +---------------------------------+----------------------+----------+
   | s1-word-edit-15.cdn.office.net  | /we/s/.../           | 39,981   |
   |                                 | wacbootwe.js         |          |
   +---------------------------------+----------------------+----------+
   | s1-officeapps-15.cdn.office.net | /we/s/.../           | 51,749   |
   |                                 | CommonIntl.js        |          |
   +---------------------------------+----------------------+----------+
   | s1-word-edit-15.cdn.office.net  | /we/s/.../           | 6,050    |
   |                                 | Compat.js            |          |
   +---------------------------------+----------------------+----------+
   | s1-word-edit-15.cdn.office.net  | /we/s/.../           | 54,158   |
   |                                 | Box4Intl.js          |          |
   +---------------------------------+----------------------+----------+
   | s1-word-edit-15.cdn.office.net  | /we/s/.../           | 24,946   |
   |                                 | WoncaIntl.js         |          |
   +---------------------------------+----------------------+----------+
   | s1-word-edit-15.cdn.office.net  | /we/s/.../           | 53,515   |
   |                                 | WordEditorIntl.js    |          |
   +---------------------------------+----------------------+----------+
   | s1-word-edit-15.cdn.office.net  | /we/s/.../           | 1,978,712|
   |                                 | WordEditorExp.js     |          |
   +---------------------------------+----------------------+----------+
   | s1-word-edit-15.cdn.office.net  | /we/s/.../jSanity.js | 10,912   |
   +---------------------------------+----------------------+----------+
   | word-edit.officeapps.live.com   | /we/OneNote.ashx     | 145,708  |
   +---------------------------------+----------------------+----------+

                   Table 7: Office365 Word Transactions

   For application identification security effectiveness
   of the DUT/SUT at the sustaining period of the HTTPS/TLS traffic MUST include
   realistic Certificate Subject Common Name (CN) data as well as Server
   Name Indications (SNI).  For example, a DUT load profile.
   The test procedure consists of two major steps.  This test procedure
   MAY detect Facebook Chat be repeated multiple times with different IPv4 and IPv6 traffic by inspecting
   distribution.

A.6.1.  Step 1: Background traffic

   Generate the certificate and detecting *.facebook.com background traffic at the transmission rate defined in
   the certificate subject CN and subsequently detect parameter section.

   The DUT/SUT MUST reach the word chat target objective (throughput) in sustain
   phase.  The measured KPIs during the FQDN 5-edge-chat.facebook.com sustain phase MUST meet the test
   validation criteria a, b, c and identify traffic on d defined in Appendix A.4.

   If the
   connection to KPI metrics do not meet the acceptance criteria, the test
   procedure MUST NOT be Facebook Chat.

   Table 8 includes further examples in SNI and CN pairs for several
   FQDNs of Office 365.

   +------------------------------+----------------------------------+
   |Server Name Indication (SNI)  | Certificate Subject              |
   |                              | Common Name (CN)                 |
   +=================================================================+
   | r1.res.office365.com         | *.res.outlook.com                |
   +------------------------------+----------------------------------+
   | login.windows.net            | graph.windows.net                |
   +------------------------------+----------------------------------+
   | webdir0a.online.lync.com     | *.online.lync.com                |
   +------------------------------+----------------------------------+
   | login.microsoftonline.com    | stamp2.login.microsoftonline.com |
   +------------------------------+----------------------------------+
   | webdir.online.lync.com       | *.online.lync.com                |
   +------------------------------+----------------------------------+
   | graph.microsoft.com          | graph.microsoft.com              |
   +------------------------------+----------------------------------+
   | outlook.office365.com        | outlook.com                      |
   +------------------------------+----------------------------------+
   | appsforoffice.microsoft.com  | appsforoffice.microsoft.com      |
   +------------------------------+----------------------------------+

               Table 8: Office365 SNI and CN Pairs Examples

   NetSecOPEN has provided a reference enterprise perimeter continued to "Step 2".

A.6.2.  Step 2: CVE emulation

   While generating the background traffic mix
   with dozens of applications, hundreds of connections, (in sustain phase), send the
   CVE traffic as defined in the parameter section.

   The test equipment SHOULD start to measure and thousands
   of transactions. record all specified
   KPIs.  The enterprise perimeter traffic mix consists frequency of 70% HTTPS and 30%
   HTTP by Bytes, 58% HTTPS and 42% HTTP by Transactions.  By
   connections with a single connection per FQDN measurement MUST be less than 2 seconds.
   Continue the mix consists of 43%
   HTTPS test until all CVEs are sent.

   The measured KPIs MUST meet all test validation criteria a, b, c, and 57% HTTP.  With multiple connections per FQDN
   d defined in Appendix A.4.

   In addition, the HTTPS
   percentage is higher.

   Table 9 is a summary of DUT/SUT SHOULD report the NetSecOPEN enterprise perimeter traffic
   mix sorted by bytes with unique FQDNs and transactions per
   applications.

   +------------------+-------+--------------+-------------+
   | Application      | FQDNs | Transactions | Bytes       |
   +=======================================================+
   | Office365        | 26    | 558          | 52,931,947  |
   +------------------+-------+--------------+-------------+
   | Box              | 4     | 90           | 23,276,089  |
   +------------------+-------+--------------+-------------+
   | Salesforce       | 6     | 365          | 23,137,548  |
   +------------------+-------+--------------+-------------+
   | Gmail            | 13    | 139          | 16,399,289  |
   +------------------+-------+--------------+-------------+
   | Linkedin         | 10    | 206          | 15,040,918  |
   +------------------+-------+--------------+-------------+
   | DailyMotion      | 8     | 77           | 14,751,514  |
   +------------------+-------+--------------+-------------+
   | GoogleDocs       | 2     | 71           | 14,205,476  |
   +------------------+-------+--------------+-------------+
   | Wikia            | 15    | 159          | 13,909,777  |
   +------------------+-------+--------------+-------------+
   | Foxnews          | 82    | 499          | 13,758,899  |
   +------------------+-------+--------------+-------------+
   | Yahoo Finance    | 33    | 254          | 13,134,011  |
   +------------------+-------+--------------+-------------+
   | Youtube          | 8     | 97           | 13,056,216  |
   +------------------+-------+--------------+-------------+
   | Facebook         | 4     | 207          | 12,726,231  |
   +------------------+-------+--------------+-------------+
   | CNBC             | 77    | 275          | 11,939,566  |
   +------------------+-------+--------------+-------------+
   | Lightreading     | 27    | 304          | 11,200,864  |
   +------------------+-------+--------------+-------------+
   | BusinessInsider  | 16    | 142          | 11,001,575  |
   +------------------+-------+--------------+-------------+
   | Alexa            | 5     | 153          | 10,475,151  |
   +------------------+-------+--------------+-------------+
   | CNN              | 41    | 206          | 10,423,740  |
   +------------------+-------+--------------+-------------+
   | Twitter Video    | 2     | 72           | 10,112,820  |
   +------------------+-------+--------------+-------------+
   | Cisco Webex      | 1     | 213          | 9,988,417   |
   +------------------+-------+--------------+-------------+
   | Slack            | 3     | 40           | 9,938,686   |
   +------------------+-------+--------------+-------------+
   | Google Maps      | 5     | 191          | 8,771,873   |
   +------------------+-------+--------------+-------------+
   | SpectrumIEEE     | 7     | 145          | 8,682,629   |
   +------------------+-------+--------------+-------------+
   | Yelp             | 9     | 146          | 8,607,645   |
   +------------------+-------+--------------+-------------+
   | Vimeo            | 12    | 74           | 8,555,960   |
   +------------------+-------+--------------+-------------+
   | Wikihow          | 11    | 140          | 8,042,314   |
   +------------------+-------+--------------+-------------+
   | Netflix          | 3     | 31           | 7,839,256   |
   +------------------+-------+--------------+-------------+
   | Instagram        | 3     | 114          | 7,230,883   |
   +------------------+-------+--------------+-------------+
   | Morningstar      | 30    | 150          | 7,220,121   |
   +------------------+-------+--------------+-------------+
   | Docusign         | 5     | 68           | 6,972,738   |
   +------------------+-------+--------------+-------------+
   | Twitter          | 1     | 100          | 6,939,150   |
   +------------------+-------+--------------+-------------+
   | Tumblr           | 11    | 70           | 6,877,200   |
   +------------------+-------+--------------+-------------+
   | Whatsapp         | 3     | 46           | 6,829,848   |
   +------------------+-------+--------------+-------------+
   | Imdb             | 16    | 251          | 6,505,227   |
   +------------------+-------+--------------+-------------+
   | NOAAgov          | 1     | 44           | 6,316,283   |
   +------------------+-------+--------------+-------------+
   | IndustryWeek     | 23    | 192          | 6,242,403   |
   +------------------+-------+--------------+-------------+
   | Spotify          | 18    | 119          | 6,231,013   |
   +------------------+-------+--------------+-------------+
   | AutoNews         | 16    | 165          | 6,115,354   |
   +------------------+-------+--------------+-------------+
   | Evernote         | 3     | 47           | 6,063,168   |
   +------------------+-------+--------------+-------------+
   | NatGeo           | 34    | 104          | 6,026,344   |
   +------------------+-------+--------------+-------------+
   | BBC News         | 18    | 156          | 5,898,572   |
   +------------------+-------+--------------+-------------+
   | Investopedia     | 38    | 241          | 5,792,038   |
   +------------------+-------+--------------+-------------+
   | Pinterest        | 8     | 102          | 5,658,994   |
   +------------------+-------+--------------+-------------+
   | Succesfactors    | 2     | 112          | 5,049,001   |
   +------------------+-------+--------------+-------------+
   | AbaJournal       | 6     | 93           | 4,985,626   |
   +------------------+-------+--------------+-------------+
   | Pbworks          | 4     | 78           | 4,670,980   |
   +------------------+-------+--------------+-------------+
   | NetworkWorld     | 42    | 153          | 4,651,354   |
   +------------------+-------+--------------+-------------+
   | WebMD            | 24    | 280          | 4,416,736   |
   +------------------+-------+--------------+-------------+
   | OilGasJournal    | 14    | 105          | 4,095,255   |
   +------------------+-------+--------------+-------------+
   | Trello           | 5     | 39           | 4,080,182   |
   +------------------+-------+--------------+-------------+
   | BusinessWire     | 5     | 109          | 4,055,331   |
   +------------------+-------+--------------+-------------+
   | Dropbox          | 5     | 17           | 4,023,469   |
   +------------------+-------+--------------+-------------+
   | Nejm             | 20    | 190          | 4,003,657   |
   +------------------+-------+--------------+-------------+
   | OilGasDaily      | 7     | 199          | 3,970,498   |
   +------------------+-------+--------------+-------------+
   | Chase            | 6     | 52           | 3,719,232   |
   +------------------+-------+--------------+-------------+
   | MedicalNews      | 6     | 117          | 3,634,187   |
   +------------------+-------+--------------+-------------+
   | Marketwatch      | 25    | 142          | 3,291,226   |
   +------------------+-------+--------------+-------------+
   | Imgur            | 5     | 48           | 3,189,919   |
   +------------------+-------+--------------+-------------+
   | NPR              | 9     | 83           | 3,184,303   |
   +------------------+-------+--------------+-------------+
   | Onelogin         | 2     | 31           | 3,132,707   |
   +------------------+-------+--------------+-------------+
   | Concur           | 2     | 50           | 3,066,326   |
   +------------------+-------+--------------+-------------+
   | Service-now      | 1     | 37           | 2,985,329   |
   +------------------+-------+--------------+-------------+
   | Apple itunes     | 14    | 80           | 2,843,744   |
   +------------------+-------+--------------+-------------+
   | BerkeleyEdu      | 3     | 69           | 2,622,009   |
   +------------------+-------+--------------+-------------+
   | MSN              | 39    | 203          | 2,532,972   |
   +------------------+-------+--------------+-------------+
   | Indeed           | 3     | 47           | 2,325,197   |
   +------------------+-------+--------------+-------------+
   | MayoClinic       | 6     | 56           | 2,269,085   |
   +------------------+-------+--------------+-------------+
   | Ebay             | 9     | 164          | 2,219,223   |
   +------------------+-------+--------------+-------------+
   | UCLAedu          | 3     | 42           | 1,991,311   |
   +------------------+-------+--------------+-------------+
   | ConstructionDive | 5     | 125          | 1,828,428   |
   +------------------+-------+--------------+-------------+
   | EducationNews    | 4     | 78           | 1,605,427   |
   +------------------+-------+--------------+-------------+
   | BofA             | 12    | 68           | 1,584,851   |
   +------------------+-------+--------------+-------------+
   | ScienceDirect    | 7     | 26           | 1,463,951   |
   +------------------+-------+--------------+-------------+
   | Reddit           | 8     | 55           | 1,441,909   |
   +------------------+-------+--------------+-------------+
   | FoodBusinessNews | 5     | 49           | 1,378,298   |
   +------------------+-------+--------------+-------------+
   | Amex             | 8     | 42           | 1,270,696   |
   +------------------+-------+--------------+-------------+
   | Weather          | 4     | 50           | 1,243,826   |
   +------------------+-------+--------------+-------------+
   | Wikipedia        | 3     | 27           | 958,935     |
   +------------------+-------+--------------+-------------+
   | Bing             | 1     | 52           | 697,514     |
   +------------------+-------+--------------+-------------+
   | ADP              | 1     | 30           | 508,654     |
   +------------------+-------+--------------+-------------+
   |                  |       |              |             |
   +------------------+-------+--------------+-------------+
   | Grand Total      | 983   | 10021        | 569,819,095 |
   +------------------+-------+--------------+-------------+

      Table 9: Summary of NetSecOPEN Enterprise Perimeter Traffic Mix vulnerabilities correctly.

Authors' Addresses

   Balamuhunthan Balarajah
   Berlin
   Germany

   Email: bm.balarajah@gmail.com
   Carsten Rossenhoevel
   EANTC AG
   Salzufer 14
   Berlin  10587
   Germany

   Email: cross@eantc.de

   Brian Monkman
   NetSecOPEN
   417 Independence Court
   Mechanicsburg, PA  17050
   USA

   Email: bmonkman@netsecopen.org