idnits 2.17.1 draft-ietf-bmwg-ngfw-performance-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (November 19, 2019) is 1613 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) -- Obsolete informational reference (is this intentional?): RFC 3511 (Obsoleted by RFC 9411) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Benchmarking Methodology Working Group B. Balarajah 3 Internet-Draft 4 Intended status: Informational C. Rossenhoevel 5 Expires: May 22, 2020 EANTC AG 6 B. Monkman 7 NetSecOPEN 8 November 19, 2019 10 Benchmarking Methodology for Network Security Device Performance 11 draft-ietf-bmwg-ngfw-performance-02 13 Abstract 15 This document provides benchmarking terminology and methodology for 16 next-generation network security devices including next-generation 17 firewalls (NGFW), intrusion detection and prevention solutions (IDS/ 18 IPS) and unified threat management (UTM) implementations. This 19 document aims to strongly improve the applicability, reproducibility, 20 and transparency of benchmarks and to align the test methodology with 21 today's increasingly complex layer 7 application use cases. The main 22 areas covered in this document are test terminology, traffic profiles 23 and benchmarking methodology for NGFWs to start with. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at https://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on May 22, 2020. 42 Copyright Notice 44 Copyright (c) 2019 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (https://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4 61 3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 4. Test Setup . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 4.1. Testbed Configuration . . . . . . . . . . . . . . . . . . 4 64 4.2. DUT/SUT Configuration . . . . . . . . . . . . . . . . . . 5 65 4.3. Test Equipment Configuration . . . . . . . . . . . . . . 9 66 4.3.1. Client Configuration . . . . . . . . . . . . . . . . 9 67 4.3.2. Backend Server Configuration . . . . . . . . . . . . 11 68 4.3.3. Traffic Flow Definition . . . . . . . . . . . . . . . 11 69 4.3.4. Traffic Load Profile . . . . . . . . . . . . . . . . 12 70 5. Test Bed Considerations . . . . . . . . . . . . . . . . . . . 13 71 6. Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 14 72 6.1. Key Performance Indicators . . . . . . . . . . . . . . . 15 73 7. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . 16 74 7.1. Throughput Performance With NetSecOPEN Traffic Mix . . . 16 75 7.1.1. Objective . . . . . . . . . . . . . . . . . . . . . . 16 76 7.1.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 17 77 7.1.3. Test Parameters . . . . . . . . . . . . . . . . . . . 17 78 7.1.4. Test Procedures and expected Results . . . . . . . . 19 79 7.2. TCP/HTTP Connections Per Second . . . . . . . . . . . . . 20 80 7.2.1. Objective . . . . . . . . . . . . . . . . . . . . . . 20 81 7.2.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 20 82 7.2.3. Test Parameters . . . . . . . . . . . . . . . . . . . 20 83 7.2.4. Test Procedures and Expected Results . . . . . . . . 22 84 7.3. HTTP Throughput . . . . . . . . . . . . . . . . . . . . . 23 85 7.3.1. Objective . . . . . . . . . . . . . . . . . . . . . . 23 86 7.3.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 23 87 7.3.3. Test Parameters . . . . . . . . . . . . . . . . . . . 23 88 7.3.4. Test Procedures and Expected Results . . . . . . . . 25 89 7.4. TCP/HTTP Transaction Latency . . . . . . . . . . . . . . 26 90 7.4.1. Objective . . . . . . . . . . . . . . . . . . . . . . 26 91 7.4.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 26 92 7.4.3. Test Parameters . . . . . . . . . . . . . . . . . . . 26 93 7.4.4. Test Procedures and Expected Results . . . . . . . . 28 94 7.5. Concurrent TCP/HTTP Connection Capacity . . . . . . . . . 29 95 7.5.1. Objective . . . . . . . . . . . . . . . . . . . . . . 29 96 7.5.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 30 97 7.5.3. Test Parameters . . . . . . . . . . . . . . . . . . . 30 98 7.5.4. Test Procedures and expected Results . . . . . . . . 31 99 7.6. TCP/HTTPS Connections per second . . . . . . . . . . . . 32 100 7.6.1. Objective . . . . . . . . . . . . . . . . . . . . . . 32 101 7.6.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 33 102 7.6.3. Test Parameters . . . . . . . . . . . . . . . . . . . 33 103 7.6.4. Test Procedures and expected Results . . . . . . . . 35 104 7.7. HTTPS Throughput . . . . . . . . . . . . . . . . . . . . 36 105 7.7.1. Objective . . . . . . . . . . . . . . . . . . . . . . 36 106 7.7.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 36 107 7.7.3. Test Parameters . . . . . . . . . . . . . . . . . . . 36 108 7.7.4. Test Procedures and Expected Results . . . . . . . . 39 109 7.8. HTTPS Transaction Latency . . . . . . . . . . . . . . . . 40 110 7.8.1. Objective . . . . . . . . . . . . . . . . . . . . . . 40 111 7.8.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 40 112 7.8.3. Test Parameters . . . . . . . . . . . . . . . . . . . 40 113 7.8.4. Test Procedures and Expected Results . . . . . . . . 42 114 7.9. Concurrent TCP/HTTPS Connection Capacity . . . . . . . . 43 115 7.9.1. Objective . . . . . . . . . . . . . . . . . . . . . . 43 116 7.9.2. Test Setup . . . . . . . . . . . . . . . . . . . . . 43 117 7.9.3. Test Parameters . . . . . . . . . . . . . . . . . . . 43 118 7.9.4. Test Procedures and expected Results . . . . . . . . 45 119 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 46 120 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 121 10. Security Considerations . . . . . . . . . . . . . . . . . . . 46 122 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47 123 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 47 124 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 47 125 13.1. Normative References . . . . . . . . . . . . . . . . . . 47 126 13.2. Informative References . . . . . . . . . . . . . . . . . 47 127 Appendix A. NetSecOPEN Basic Traffic Mix . . . . . . . . . . . . 48 128 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 56 130 1. Introduction 132 15 years have passed since IETF recommended test methodology and 133 terminology for firewalls initially ([RFC2647], [RFC3511]). The 134 requirements for network security element performance and 135 effectiveness have increased tremendously since then. Security 136 function implementations have evolved to more advanced areas and have 137 diversified into intrusion detection and prevention, threat 138 management, analysis of encrypted traffic, etc. In an industry of 139 growing importance, well-defined and reproducible key performance 140 indicators (KPIs) are increasingly needed: They enable fair and 141 reasonable comparison of network security functions. All these 142 reasons have led to the creation of a new next-generation firewall 143 benchmarking document. 145 2. Requirements 147 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 148 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 149 "OPTIONAL" in this document are to be interpreted as described in BCP 150 14 [RFC2119], [RFC8174] when, and only when, they appear in all 151 capitals, as shown here. 153 3. Scope 155 This document provides testing terminology and testing methodology 156 for next-generation firewalls and related security functions. It 157 covers two main areas: security effectiveness configurations, 158 followed by performance benchmark testing. This document focuses on 159 advanced, realistic, and reproducible testing methods. Additionally, 160 it describes test bed environments, test tool requirements and test 161 result formats. 163 4. Test Setup 165 Test setup defined in this document is applicable to all benchmarking 166 test scenarios described in Section 7. 168 4.1. Testbed Configuration 170 Testbed configuration MUST ensure that any performance implications 171 that are discovered during the benchmark testing aren't due to the 172 inherent physical network limitations such as number of physical 173 links and forwarding performance capabilities (throughput and 174 latency) of the network devise in the testbed. For this reason, this 175 document recommends avoiding external devices such as switches and 176 routers in the testbed wherever possible. 178 However, in the typical deployment, the security devices ( Device 179 Under Test/System Under Test) are connected to routers and switches 180 which will reduce the number of entries in MAC or ARP tables of the 181 Device Under Test/System Under Test (DUT/SUT). If MAC or ARP tables 182 have many entries, this may impact the actual DUT/SUT performance due 183 to MAC and ARP/ND table lookup processes. Therefore, it is 184 RECOMMENDED to connect aggregation switches or routers between test 185 equipment and DUT/SUT as shown in Figure 1. The aggregation switches 186 or routers can be also used to aggregate the test equipment or DUT/ 187 SUT ports, if the numbers of used ports are mismatched between test 188 equipment and DUT/SUT. 190 If the test equipment is capable of emulating layer 3 routing 191 functionality and there is no need for test equipment port 192 aggregation, it is RECOMMENDED to configure the test setup as shown 193 in Figure 2. 195 +-------------------+ +-----------+ +--------------------+ 196 |Aggregation Switch/| | | | Aggregation Switch/| 197 | Router +------+ DUT/SUT +------+ Router | 198 | | | | | | 199 +----------+--------+ +-----------+ +--------+-----------+ 200 | | 201 | | 202 +-----------+-----------+ +-----------+-----------+ 203 | | | | 204 | +-------------------+ | | +-------------------+ | 205 | | Emulated Router(s)| | | | Emulated Router(s)| | 206 | | (Optional) | | | | (Optional) | | 207 | +-------------------+ | | +-------------------+ | 208 | +-------------------+ | | +-------------------+ | 209 | | Clients | | | | Servers | | 210 | +-------------------+ | | +-------------------+ | 211 | | | | 212 | Test Equipment | | Test Equipment | 213 +-----------------------+ +-----------------------+ 215 Figure 1: Testbed Setup - Option 1 217 +-----------------------+ +-----------------------+ 218 | +-------------------+ | +-----------+ | +-------------------+ | 219 | | Emulated Router(s)| | | | | | Emulated Router(s)| | 220 | | (Optional) | +----- DUT/SUT +-----+ (Optional) | | 221 | +-------------------+ | | | | +-------------------+ | 222 | +-------------------+ | +-----------+ | +-------------------+ | 223 | | Clients | | | | Servers | | 224 | +-------------------+ | | +-------------------+ | 225 | | | | 226 | Test Equipment | | Test Equipment | 227 +-----------------------+ +-----------------------+ 229 Figure 2: Testbed Setup - Option 2 231 4.2. DUT/SUT Configuration 233 A unique DUT/SUT configuration MUST be used for all benchmarking 234 tests described in Section 7. Since each DUT/SUT will have their own 235 unique configuration, users SHOULD configure their device with the 236 same parameters and security features that would be used in the 237 actual deployment of the device or a typical deployment in order to 238 achieve maximum security coverage. 240 This document attempts to define the recommended security features 241 which SHOULD be consistently enabled for all the benchmarking tests 242 described in Section 7. Table 1 below describes the RECOMMENDED sets 243 of feature list which SHOULD be configured on the DUT/SUT. 245 Based on customer use case, users MAY enable or disable SSL 246 inspection feature for "Throughput Performance with NetSecOPEN 247 Traffic Mix" test scenario described in Section 7.1 249 To improve repeatability, a summary of the DUT configuration 250 including description of all enabled DUT/SUT features MUST be 251 published with the benchmarking results. 253 +------------------------+ 254 | NGFW | 255 +-------------- +-------------+----------+ 256 | | | | 257 |DUT Features | RECOMMENDED | OPTIONAL | 258 | | | | 259 +----------------------------------------+ 260 |SSL Inspection | x | | 261 +----------------------------------------+ 262 |IDS/IPS | x | | 263 +----------------------------------------+ 264 |Web Filtering | | x | 265 +----------------------------------------+ 266 |Antivirus | x | | 267 +----------------------------------------+ 268 |Anti Spyware | x | | 269 +----------------------------------------+ 270 |Anti Botnet | x | | 271 +----------------------------------------+ 272 |DLP | | x | 273 +----------------------------------------+ 274 |DDoS | | x | 275 +----------------------------------------+ 276 |Certificate | | x | 277 |Validation | | | 278 +----------------------------------------+ 279 |Logging and | x | | 280 |Reporting | | | 281 +-------------- +------------------------+ 282 |Application | x | | 283 |Identification | | | 284 +---------------+-------------+----------+ 286 Table 1: DUT/SUT Feature List 288 In summary, DUT/SUT SHOULD be configured as follows: 290 o All security inspection enabled 292 o Disposition of all flows of traffic are logged - Logging to an 293 external device is permissible 295 o Detection of Common Vulnerabilities and Exposures (CVE) matching 296 the following characteristics when searching the National 297 Vulnerability Database (NVD) 299 * Common Vulnerability Scoring System (CVSS) Version: 2 301 * CVSS V2 Metrics: AV:N/Au:N/I:C/A:C 303 * AV=Attack Vector, Au=Authentication, I=Integrity and 304 A=Availability 306 * CVSS V2 Severity: High (7-10) 308 * If doing a group test the published start date and published 309 end date SHOULD be the same 311 o Geographical location filtering and Application Identification and 312 Control configured to be triggered based on a site or application 313 from the defined traffic mix 315 In addition, it is also RECOMMENDED to configure a realistic number 316 of access policy rules on the DUT/SUT. This document determines the 317 number of access policy rules for three different classes of DUT/SUT. 318 The classification of the DUT/SUT MAY be based on its maximum 319 supported firewall throughput performance number defined in the 320 vendor data sheet. This document classifies the DUT/SUT in four 321 different categories; namely Extra Small, Small, Medium, and Large. 323 The RECOMMENDED throughput values for the following classes are: 325 Extra Small (XS) - supported throughput less than 1Gbit/s 327 Small (S) - supported throughput less than 5Gbit/s 329 Medium (M) - supported throughput greater than 5Gbit/s and less than 330 10Gbit/s 332 Large (L) - supported throughput greater than 10Gbit/s 333 The Access Conrol Rules (ACL) defined in Table 2 MUST be configured 334 from top to bottom in the correct order as shown in the table. 335 (Note: There will be differences between how security vendors 336 implement ACL decision making.) The configured ACL MUST NOT block 337 the test traffic used for the benchmarking test scenarios. 339 +---------------------------------------------------+---------------+ 340 | | DUD/SUT | 341 | | Classification| 342 | | #rules | 343 +-----------+-----------+------------------+------------+---+---+---+ 344 | | Match | | | | | | | 345 | Rules Type| Criteria | Description | Action | XS| S | M | L | 346 +-------------------------------------------------------------------+ 347 |Application|Application| Any application | block | 5 | 10| 20| 50| 348 |layer | | traffic NOT | | | | | | 349 | | | included in the | | | | | | 350 | | | test traffic | | | | | | 351 +-----------------------+ ------------------------------------------+ 352 |Transport |Src IP and | Any src IP subnet| block | 25| 50|100|250| 353 |layer |TCP/UDP | used in the test | | | | | | 354 | |Dst ports | AND any dst ports| | | | | | 355 | | | NOT used in the | | | | | | 356 | | | test traffic | | | | | | 357 +-------------------------------------------------------------------+ 358 |IP layer |Src/Dst IP | Any src/dst IP | block | 25| 50|100|250| 359 | | | subnet NOT used | | | | | | 360 | | | in the test | | | | | | 361 +-------------------------------------------------------------------+ 362 |Application|Application| Applications | allow | 10| 10| 10| 10| 363 |layer | | included in the | | | | | | 364 | | | test traffic | | | | | | 365 +-------------------------------------------------------------------+ 366 |Transport |Src IP and | Half of the src | allow | 1| 1| 1| 1| 367 |layer |TCP/UDP | IP used in the | | | | | | 368 | |Dst ports | test AND any dst | | | | | | 369 | | | ports used in the| | | | | | 370 | | | test traffic. One| | | | | | 371 | | | rule per subnet | | | | | | 372 +-------------------------------------------------------------------+ 373 |IP layer |Src IP | The rest of the | allow | 1| 1| 1| 1| 374 | | | src IP subnet | | | | | | 375 | | | range used in the| | | | | | 376 | | | test. One rule | | | | | | 377 | | | per subnet | | | | | | 378 +-----------+-----------+------------------+--------+---+---+---+---+ 380 Table 2: DUT/SUT Access List 382 4.3. Test Equipment Configuration 384 In general, test equipment allows configuring parameters in different 385 protocol layers. These parameters thereby influence the traffic 386 flows which will be offered and impact performance measurements. 388 This document specifies common test equipment configuration 389 parameters applicable for all test scenarios defined in Section 7. 390 Any test scenario specific parameters are described under the test 391 setup section of each test scenario individually. 393 4.3.1. Client Configuration 395 This section specifies which parameters SHOULD be considered while 396 configuring clients using test equipment. Also, this section 397 specifies the recommended values for certain parameters. 399 4.3.1.1. TCP Stack Attributes 401 The TCP stack SHOULD use a TCP Reno [RFC5681] variant, which include 402 congestion avoidance, back off and windowing, fast retransmission, 403 and fast recovery on every TCP connection between client and server 404 endpoints. The default IPv4 and IPv6 MSS segments size MUST be set 405 to 1460 bytes and 1440 bytes respectively and a TX and RX receive 406 windows of 64 KByte. Client initial congestion window MUST NOT 407 exceed 10 times the MSS. Delayed ACKs are permitted and the maximum 408 client delayed Ack MUST NOT exceed 10 times the MSS before a forced 409 ACK. Up to 3 retries SHOULD be allowed before a timeout event is 410 declared. All traffic MUST set the TCP PSH flag to high. The source 411 port range SHOULD be in the range of 1024 - 65535. Internal timeout 412 SHOULD be dynamically scalable per RFC 793. Client SHOULD initiate 413 and close TCP connections. TCP connections MUST be closed via FIN. 415 4.3.1.2. Client IP Address Space 417 The sum of the client IP space SHOULD contain the following 418 attributes. The traffic blocks SHOULD consist of multiple unique, 419 discontinuous static address blocks. A default gateway is permitted. 420 The IPv4 ToS byte or IPv6 traffic class should be set to '00' or 421 '000000' respectively. 423 The following equation can be used to determine the required total 424 number of client IP addresses. 426 Desired total number of client IP = Target throughput [Mbit/s] / 427 Throughput per IP address [Mbit/s] 428 Based on deployment and use case scenario, the value for "Throughput 429 per IP address" can be varied. 431 (Option 1) DUT/SUT deployment scenario 1 : 6-7 Mbit/s per IP (e.g. 432 1,400-1,700 IPs per 10Gbit/s throughput) 434 (Option 2) DUT/SUT deployment scenario 2 : 0.1-0.2 Mbit/s per IP 435 (e.g. 50,000-100,000 IPs per 10Gbit/s throughput) 437 Based on deployment and use case scenario, client IP addresses SHOULD 438 be distributed between IPv4 and IPv6 type. The Following options can 439 be considered for a selection of traffic mix ratio. 441 (Option 1) 100 % IPv4, no IPv6 443 (Option 2) 80 % IPv4, 20% IPv6 445 (Option 3) 50 % IPv4, 50% IPv6 447 (Option 4) 20 % IPv4, 80% IPv6 449 (Option 5) no IPv4, 100% IPv6 451 4.3.1.3. Emulated Web Browser Attributes 453 The emulated web browser contains attributes that will materially 454 affect how traffic is loaded. The objective is to emulate modern, 455 typical browser attributes to improve realism of the result set. 457 For HTTP traffic emulation, the emulated browser MUST negotiate HTTP 458 1.1. HTTP persistency MAY be enabled depending on test scenario. 459 The browser MAY open multiple TCP connections per Server endpoint IP 460 at any time depending on how many sequential transactions are needed 461 to be processed. Within the TCP connection multiple transactions MAY 462 be processed if the emulated browser has available connections. The 463 browser SHOULD advertise a User-Agent header. Headers MUST be sent 464 uncompressed. The browser SHOULD enforce content length validation. 466 For encrypted traffic, the following attributes SHALL define the 467 negotiated encryption parameters. The test clients MUST use TLSv1.2 468 or higher. TLS record size MAY be optimized for the HTTPS response 469 object size up to a record size of 16 KByte. The client endpoint 470 MUST send TLS Extension Server Name Indication (SNI) information when 471 opening a security tunnel. Each client connection MUST perform a 472 full handshake with server certificate and MUST NOT use session reuse 473 or resumption. Cipher suite and key size should be defined in the 474 parameter session of each test scenario. 476 4.3.2. Backend Server Configuration 478 This document specifies which parameters should be considered while 479 configuring emulated backend servers using test equipment. 481 4.3.2.1. TCP Stack Attributes 483 The TCP stack on the server side SHOULD be configured similar to the 484 client side configuration described in Section 4.3.1.1. In addition, 485 server initial congestion window MUST NOT exceed 10 times the MSS. 486 Delayed ACKs are permitted and the maximum server delayed ACK MUST 487 NOT exceed 10 times the MSS before a forced ACK. 489 4.3.2.2. Server Endpoint IP Addressing 491 The server IP blocks SHOULD consist of unique, discontinuous static 492 address blocks with one IP per Server Fully Qualified Domain Name 493 (FQDN) endpoint per test port. The IPv4 ToS byte and IPv6 traffic 494 class bytes should be set to '00' and '000000' respectively. 496 4.3.2.3. HTTP / HTTPS Server Pool Endpoint Attributes 498 The server pool for HTTP SHOULD listen on TCP port 80 and emulate 499 HTTP version 1.1 with persistence. The Server MUST advertise server 500 type in the Server response header [RFC2616]. For HTTPS server, TLS 501 1.2 or higher MUST be used with a maximum record size of 16 KByte and 502 MUST NOT use ticket resumption or Session ID reuse . The server MUST 503 listen on port TCP 443. The server SHALL serve a certificate to the 504 client. It is REQUIRED that the HTTPS server also check Host SNI 505 information with the FQDN. Cipher suite and key size should be 506 defined in the parameter section of each test scenario. 508 4.3.3. Traffic Flow Definition 510 This section describes the traffic pattern between client and server 511 endpoints. At the beginning of the test, the server endpoint 512 initializes and will be ready to accept connection states including 513 initialization of the TCP stack as well as bound HTTP and HTTPS 514 servers. When a client endpoint is needed, it will initialize and be 515 given attributes such as a MAC and IP address. The behavior of the 516 client is to sweep though the given server IP space, sequentially 517 generating a recognizable service by the DUT. Thus, a balanced, mesh 518 between client endpoints and server endpoints will be generated in a 519 client port server port combination. Each client endpoint performs 520 the same actions as other endpoints, with the difference being the 521 source IP of the client endpoint and the target server IP pool. The 522 client SHALL use Fully Qualified Domain Names (FQDN) in Host Headers 523 and for TLS Server Name Indication (SNI). 525 4.3.3.1. Description of Intra-Client Behavior 527 Client endpoints are independent of other clients that are 528 concurrently executing. When a client endpoint initiates traffic, 529 this section describes how the client steps though different 530 services. Once the test is initialized, the client endpoints SHOULD 531 randomly hold (perform no operation) for a few milliseconds to allow 532 for better randomization of start of client traffic. Each client 533 will either open a new TCP connection or connect to a TCP persistence 534 stack still open to that specific server. At any point that the 535 service profile may require encryption, a TLS encryption tunnel will 536 form presenting the URL request to the server. The server will then 537 perform an SNI name check with the proposed FQDN compared to the 538 domain embedded in the certificate. Only when correct, will the 539 server process the HTTPS response object. The initial response 540 object to the server MUST NOT have a fixed size; its size is based on 541 benchmarking tests described in Section 7. Multiple additional sub- 542 URLs (response objects on the service page) MAY be requested 543 simultaneously. This MAY be to the same server IP as the initial 544 URL. Each sub-object will also use a conical FQDN and URL path, as 545 observed in the traffic mix used. 547 4.3.4. Traffic Load Profile 549 The loading of traffic is described in this section. The loading of 550 a traffic load profile has five distinct phases: Init, ramp up, 551 sustain, ramp down, and collection. 553 1. During the Init phase, test bed devices including the client and 554 server endpoints should negotiate layer 2-3 connectivity such as 555 MAC learning and ARP. Only after successful MAC learning or ARP/ 556 ND resolution SHALL the test iteration move to the next phase. 557 No measurements are made in this phase. The minimum RECOMMEND 558 time for Init phase is 5 seconds. During this phase, the 559 emulated clients SHOULD NOT initiate any sessions with the DUT/ 560 SUT, in contrast, the emulated servers should be ready to accept 561 requests from DUT/SUT or from emulated clients. 563 2. In the ramp up phase, the test equipment SHOULD start to generate 564 the test traffic. It SHOULD use a set approximate number of 565 unique client IP addresses actively to generate traffic. The 566 traffic SHOULD ramp from zero to desired target objective. The 567 target objective will be defined for each benchmarking test. The 568 duration for the ramp up phase MUST be configured long enough, so 569 that the test equipment does not overwhelm DUT/SUT's supported 570 performance metrics namely; connections per second, concurrent 571 TCP connections, and application transactions per second. The 572 RECOMMENDED time duration for the ramp up phase is 180-300 573 seconds. No measurements are made in this phase. 575 3. In the sustain phase, the test equipment SHOULD continue 576 generating traffic to constant target value for a constant number 577 of active client IPs. The mininum RECOMMENDED time duration for 578 sustain phase is 300 seconds. This is the phase where 579 measurements occur. 581 4. In the ramp down/close phase, no new connections are established, 582 and no measurements are made. The time duration for ramp up and 583 ramp down phase SHOULD be same. The RECOMMENDED duration of this 584 phase is between 180 to 300 seconds. 586 5. The last phase is administrative and will occur when the test 587 equipment merges and collates the report data. 589 5. Test Bed Considerations 591 This section recommends steps to control the test environment and 592 test equipment, specifically focusing on virtualized environments and 593 virtualized test equipment. 595 1. Ensure that any ancillary switching or routing functions between 596 the system under test and the test equipment do not limit the 597 performance of the traffic generator. This is specifically 598 important for virtualized components (vSwitches, vRouters). 600 2. Verify that the performance of the test equipment matches and 601 reasonably exceeds the expected maximum performance of the system 602 under test. 604 3. Assert that the test bed characteristics are stable during the 605 entire test session. Several factors might influence stability 606 specifically for virtualized test beds, for example additional 607 workloads in a virtualized system, load balancing and movement of 608 virtual machines during the test, or simple issues such as 609 additional heat created by high workloads leading to an emergency 610 CPU performance reduction. 612 Test bed reference pre-tests help to ensure that the maximum desired 613 traffic generator aspects such as throughput, transaction per second, 614 connection per second, concurrent connection and latency. 616 Once the desired maximum performance goals for the system under test 617 have been identified, a safety margin of 10% SHOULD be added for 618 throughput and subtracted for maximum latency and maximum packet 619 loss. 621 Test bed preparation may be performed either by configuring the DUT 622 in the most trivial setup (fast forwarding) or without presence of 623 DUT. 625 6. Reporting 627 This section describes how the final report should be formatted and 628 presented. The final test report MAY have two major sections; 629 Introduction and result sections. The following attributes SHOULD be 630 present in the introduction section of the test report. 632 1. The name of the NetSecOPEN traffic mix (see Appendix A) MUST be 633 prominent. 635 2. The time and date of the execution of the test MUST be prominent. 637 3. Summary of testbed software and Hardware details 639 A. DUT Hardware/Virtual Configuration 641 + This section SHOULD clearly identify the make and model of 642 the DUT 644 + The port interfaces, including speed and link information 645 MUST be documented. 647 + If the DUT is a virtual VNF, interface acceleration such 648 as DPDK and SR-IOV MUST be documented as well as cores 649 used, RAM used, and the pinning / resource sharing 650 configuration. The Hypervisor and version MUST be 651 documented. 653 + Any additional hardware relevant to the DUT such as 654 controllers MUST be documented 656 B. DUT Software 658 + The operating system name MUST be documented 660 + The version MUST be documented 662 + The specific configuration MUST be documented 664 C. DUT Enabled Features 666 + Configured DUT/SUT features (see Table 1) MUST be 667 documented 669 + Attributes of those featured MUST be documented 671 + Any additional relevant information about features MUST be 672 documented 674 D. Test equipment hardware and software 676 + Test equipment vendor name 678 + Hardware details including model number, interface type 680 + Test equipment firmware and test application software 681 version 683 4. Results Summary / Executive Summary 685 1. Results SHOULD resemble a pyramid in how it is reported, with 686 the introduction section documenting the summary of results 687 in a prominent, easy to read block. 689 2. In the result section of the test report, the following 690 attributes should be present for each test scenario. 692 a. KPIs MUST be documented separately for each test 693 scenario. The format of the KPI metrics should be 694 presented as described in Section 6.1. 696 b. The next level of details SHOULD be graphs showing each 697 of these metrics over the duration (sustain phase) of the 698 test. This allows the user to see the measured 699 performance stability changes over time. 701 6.1. Key Performance Indicators 703 This section lists KPIs for overall benchmarking tests scenarios. 704 All KPIs MUST be measured during the sustain phase of the traffic 705 load profile described in Section 4.3.4. All KPIs MUST be measured 706 from the result output of test equipment. 708 o Concurrent TCP Connections 709 This key performance indicator measures the average concurrent 710 open TCP connections in the sustaining period. 712 o TCP Connections Per Second 713 This key performance indicator measures the average established 714 TCP connections per second in the sustaining period. For "TCP/ 715 HTTP(S) Connection Per Second" benchmarking test scenario, the KPI 716 is measured average established and terminated TCP connections per 717 second simultaneously. 719 o Application Transactions Per Second 720 This key performance indicator measures the average successfully 721 completed application transactions per second in the sustaining 722 period. 724 o TLS Handshake Rate 725 This key performance indicator measures the average TLS 1.2 or 726 higher session formation rate within the sustaining period. 728 o Throughput 729 This key performance indicator measures the average Layer 2 730 throughput within the sustaining period as well as average packets 731 per seconds within the same period. The value of throughput 732 SHOULD be presented in Gbit/s rounded to two places of precision 733 with a more specific Kbit/s in parenthesis. Optionally, goodput 734 MAY also be logged as an average goodput rate measured over the 735 same period. Goodput result SHALL also be presented in the same 736 format as throughput. 738 o URL Response time / Time to Last Byte (TTLB) 739 This key performance indicator measures the minimum, average and 740 maximum per URL response time in the sustaining period. The 741 latency is measured at Client and in this case would be the time 742 duration between sending a GET request from Client and the 743 receival of the complete response from the server. 745 o Time to First Byte (TTFB) 746 This key performance indicator will measure minimum, average and 747 maximum the time to first byte. TTFB is the elapsed time between 748 sending the SYN packet from the client and receiving the first 749 byte of application date from the DUT/SUT. TTFB SHOULD be 750 expressed in millisecond. 752 7. Benchmarking Tests 754 7.1. Throughput Performance With NetSecOPEN Traffic Mix 756 7.1.1. Objective 758 Using NetSecOPEN traffic mix, determine the maximum sustainable 759 throughput performance supported by the DUT/SUT. (see Appendix A for 760 details about traffic mix) 761 This test scenario is RECOMMENDED to perform twice; one with SSL 762 inspection feature enabled and the second scenario with SSL 763 inspection feature disabled on the DUT/SUT. 765 7.1.2. Test Setup 767 Test bed setup MUST be configured as defined in Section 4. Any test 768 scenario specific test bed configuration changes MUST be documented. 770 7.1.3. Test Parameters 772 In this section, test scenario specific parameters SHOULD be defined. 774 7.1.3.1. DUT/SUT Configuration Parameters 776 DUT/SUT parameters MUST conform to the requirements defined in 777 Section 4.2. Any configuration changes for this specific test 778 scenario MUST be documented. 780 7.1.3.2. Test Equipment Configuration Parameters 782 Test equipment configuration parameters MUST conform to the 783 requirements defined in Section 4.3. Following parameters MUST be 784 noted for this test scenario: 786 Client IP address range defined in Section 4.3.1.2 788 Server IP address range defined in Section 4.3.2.2 790 Traffic distribution ratio between IPv4 and IPv6 defined in 791 Section 4.3.1.2 793 Target throughput: It can be defined based on requirements. 794 Otherwise it represents aggregated line rate of interface(s) used 795 in the DUT/SUT 797 Initial throughput: 10% of the "Target throughput" 799 One of the following ciphers and keys are RECOMMENDED to use for 800 this test scenarios. 802 1. ECHDE-ECDSA-AES128-GCM-SHA256 with Prime256v1 (Signature Hash 803 Algorithm: ecdsa_secp256r1_sha256 and Supported group: 804 sepc256r1) 806 2. ECDHE-RSA-AES128-GCM-SHA256 with RSA 2048 (Signature Hash 807 Algorithm: rsa_pkcs1_sha256 and Supported group: sepc256) 809 3. ECDHE-ECDSA-AES256-GCM-SHA384 with Secp521 (Signature Hash 810 Algorithm: ecdsa_secp384r1_sha384 and Supported group: 811 sepc521r1) 813 4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash 814 Algorithm: rsa_pkcs1_sha384 and Supported group: secp256) 816 7.1.3.3. Traffic Profile 818 Traffic profile: Test scenario MUST be run with a single application 819 traffic mix profile (see Appendix A for details about traffic mix). 820 The name of the NetSecOPEN traffic mix MUST be documented. 822 7.1.3.4. Test Results Validation Criteria 824 The following test Criteria is defined as test results validation 825 criteria. Test results validation criteria MUST be monitored during 826 the whole sustain phase of the traffic load profile. 828 a. Number of failed application transactions (receiving any HTTP 829 response code other than 200 OK) MUST be less than 0.001% (1 out 830 of 100,000 transactions) of total attempt transactions 832 b. Number of Terminated TCP connections due to unexpected TCP RST 833 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 834 connections) of total initiated TCP connections 836 c. Maximum deviation (max. dev) of URL Response Time or TTLB (Time 837 To Last Byte) MUST be less than X (The value for "X" will be 838 finalized and updated after completion of PoC test) 839 The following equation MUST be used to calculate the deviation of 840 URL Response Time or TTLB 841 max. dev = max((avg_latency - min_latency),(max_latency - 842 avg_latency)) / (Initial latency) 843 Where, the initial latency is calculated using the following 844 equation. For this calculation, the latency values (min', avg' 845 and max') MUST be measured during test procedure step 1 as 846 defined in Section 7.1.4.1. 847 The variable latency represents URL Response Time or TTLB. 848 Initial latency:= min((avg' latency - min' latency) | (max' 849 latency - avg' latency)) 851 d. Maximum value of Time to First Byte (TTFB) MUST be less than X 853 7.1.3.5. Measurement 855 Following KPI metrics MUST be reported for this test scenario. 857 Mandatory KPIs: average Throughput, TTFB (minimum, average and 858 maximum), TTLB (minimum, average and maximum) and average Application 859 Transactions Per Second 861 Note: TTLB MUST be reported along with min, max and avg object size 862 used in the traffic profile. 864 Optional KPIs: average TCP Connections Per Second and average TLS 865 Handshake Rate 867 7.1.4. Test Procedures and expected Results 869 The test procedures are designed to measure the throughput 870 performance of the DUT/SUT at the sustaining period of traffic load 871 profile. The test procedure consists of three major steps. 873 7.1.4.1. Step 1: Test Initialization and Qualification 875 Verify the link status of the all connected physical interfaces. All 876 interfaces are expected to be in "UP" status. 878 Configure traffic load profile of the test equipment to generate test 879 traffic at the "Initial throughput" rate as described in the 880 parameters Section 7.1.3.2. The test equipment SHOULD follow the 881 traffic load profile definition as described in Section 4.3.4. The 882 DUT/SUT SHOULD reach the "Initial throughput" during the sustain 883 phase. Measure all KPI as defined in Section 7.1.3.5. The measured 884 KPIs during the sustain phase MUST meet validation criteria "a" and 885 "b" defined in Section 7.1.3.4. 887 If the KPI metrics do not meet the validation criteria, the test 888 procedure MUST NOT be continued to step 2. 890 7.1.4.2. Step 2: Test Run with Target Objective 892 Configure test equipment to generate traffic at the "Target 893 throughput" rate defined in the parameter table. The test equipment 894 SHOULD follow the traffic load profile definition as described in 895 Section 4.3.4. The test equipment SHOULD start to measure and record 896 all specified KPIs. The frequency of KPI metric measurements SHOULD 897 be 2 seconds. Continue the test until all traffic profile phases are 898 completed. 900 The DUT/SUT is expected to reach the desired target throughput during 901 the sustain phase. In addition, the measured KPIs MUST meet all 902 validation criteria. Follow step 3, if the KPI metrics do not meet 903 the validation criteria. 905 7.1.4.3. Step 3: Test Iteration 907 Determine the maximum and average achievable throughput within the 908 validation criteria. Final test iteration MUST be performed for the 909 test duration defined in Section 4.3.4. 911 7.2. TCP/HTTP Connections Per Second 913 7.2.1. Objective 915 Using HTTP traffic, determine the maximum sustainable TCP connection 916 establishment rate supported by the DUT/SUT under different 917 throughput load conditions. 919 To measure connections per second, test iterations MUST use different 920 fixed HTTP response object sizes defined in Section 7.2.3.2. 922 7.2.2. Test Setup 924 Test bed setup SHOULD be configured as defined in Section 4. Any 925 specific test bed configuration changes such as number of interfaces 926 and interface type, etc. MUST be documented. 928 7.2.3. Test Parameters 930 In this section, test scenario specific parameters SHOULD be defined. 932 7.2.3.1. DUT/SUT Configuration Parameters 934 DUT/SUT parameters MUST conform to the requirements defined in 935 Section 4.2. Any configuration changes for this specific test 936 scenario MUST be documented. 938 7.2.3.2. Test Equipment Configuration Parameters 940 Test equipment configuration parameters MUST conform to the 941 requirements defined in Section 4.3. Following parameters MUST be 942 documented for this test scenario: 944 Client IP address range defined in Section 4.3.1.2 946 Server IP address range defined in Section 4.3.2.2 947 Traffic distribution ratio between IPv4 and IPv6 defined in 948 Section 4.3.1.2 950 Target connections per second: Initial value from product data sheet 951 (if known) 953 Initial connections per second: 10% of "Target connections per 954 second" 956 The client SHOULD negotiate HTTP 1.1 and close the connection with 957 FIN immediately after completion of one transaction. In each test 958 iteration, client MUST send GET command requesting a fixed HTTP 959 response object size. 961 The RECOMMENDED response object sizes are 1, 2, 4, 16, 64 KByte 963 7.2.3.3. Test Results Validation Criteria 965 The following test Criteria is defined as test results validation 966 criteria. Test results validation criteria MUST be monitored during 967 the whole sustain phase of the traffic load profile. 969 a. Number of failed Application transactions (receiving any HTTP 970 response code other than 200 OK) MUST be less than 0.001% (1 out 971 of 100,000 transactions) of total attempt transactions 973 b. Number of Terminated TCP connections due to unexpected TCP RST 974 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 975 connections) of total initiated TCP connections 977 c. During the sustain phase, traffic should be forwarded at a 978 constant rate 980 d. Concurrent TCP connections SHOULD be constant during steady 981 state. Any deviation of concurrent TCP connections MUST be less 982 than 10%. This confirms the DUT opens and closes TCP connections 983 almost at the same rate 985 7.2.3.4. Measurement 987 Following KPI metric MUST be reported for each test iteration. 989 average TCP Connections Per Second 991 7.2.4. Test Procedures and Expected Results 993 The test procedure is designed to measure the TCP connections per 994 second rate of the DUT/SUT at the sustaining period of the traffic 995 load profile. The test procedure consists of three major steps. 996 This test procedure MAY be repeated multiple times with different IP 997 types; IPv4 only, IPv6 only and IPv4 and IPv6 mixed traffic 998 distribution. 1000 7.2.4.1. Step 1: Test Initialization and Qualification 1002 Verify the link status of all connected physical interfaces. All 1003 interfaces are expected to be in "UP" status. 1005 Configure the traffic load profile of the test equipment to establish 1006 "initial connections per second" as defined in the parameters 1007 Section 7.2.3.2. The traffic load profile SHOULD be defined as 1008 described in Section 4.3.4. 1010 The DUT/SUT SHOULD reach the "Initial connections per second" before 1011 the sustain phase. The measured KPIs during the sustain phase MUST 1012 meet validation criteria a, b, c, and d defined in Section 7.2.3.3. 1014 If the KPI metrics do not meet the validation criteria, the test 1015 procedure MUST NOT be continued to "Step 2". 1017 7.2.4.2. Step 2: Test Run with Target Objective 1019 Configure test equipment to establish "Target connections per second" 1020 defined in the parameters table. The test equipment SHOULD follow 1021 the traffic load profile definition as described in Section 4.3.4. 1023 During the ramp up and sustain phase of each test iteration, other 1024 KPIs such as throughput, concurrent TCP connections and application 1025 transactions per second MUST NOT reach to the maximum value the DUT/ 1026 SUT can support. The test results for specific test iterations 1027 SHOULD NOT be reported, if the above mentioned KPI (especially 1028 throughput) reaches the maximum value. (Example: If the test 1029 iteration with 64 KByte of HTTP response object size reached the 1030 maximum throughput limitation of the DUT, the test iteration MAY be 1031 interrupted and the result for 64 KByte SHOULD NOT be reported). 1033 The test equipment SHOULD start to measure and record all specified 1034 KPIs. The frequency of measurement SHOULD be 2 seconds. Continue 1035 the test until all traffic profile phases are completed. 1037 The DUT/SUT is expected to reach the desired target connections per 1038 second rate at the sustain phase. In addition, the measured KPIs 1039 MUST meet all validation criteria. 1041 Follow step 3, if the KPI metrics do not meet the validation 1042 criteria. 1044 7.2.4.3. Step 3: Test Iteration 1046 Determine the maximum and average achievable connections per second 1047 within the validation criteria. 1049 7.3. HTTP Throughput 1051 7.3.1. Objective 1053 Determine the throughput for HTTP transactions varying the HTTP 1054 response object size. 1056 7.3.2. Test Setup 1058 Test bed setup SHOULD be configured as defined in Section 4. Any 1059 specific test bed configuration changes such as number of interfaces 1060 and interface type, etc. must be documented. 1062 7.3.3. Test Parameters 1064 In this section, test scenario specific parameters SHOULD be defined. 1066 7.3.3.1. DUT/SUT Configuration Parameters 1068 DUT/SUT parameters MUST conform to the requirements defined in 1069 Section 4.2. Any configuration changes for this specific test 1070 scenario MUST be documented. 1072 7.3.3.2. Test Equipment Configuration Parameters 1074 Test equipment configuration parameters MUST conform to the 1075 requirements defined in Section 4.3. Following parameters MUST be 1076 documented for this test scenario: 1078 Client IP address range defined in Section 4.3.1.2 1080 Server IP address range defined in Section 4.3.2.2 1082 Traffic distribution ratio between IPv4 and IPv6 defined in 1083 Section 4.3.1.2 1084 Target Throughput: Initial value from product data sheet (if known) 1086 Initial Throughput: 10% of "Target Throughput" 1088 Number of HTTP response object requests (transactions) per 1089 connection: 10 1091 RECOMMENDED HTTP response object size: 1 KByte, 16 KByte, 64 KByte, 1092 256 KByte and mixed objects defined in the table 1094 +---------------------+---------------------+ 1095 | Object size (KByte) | Number of requests/ | 1096 | | Weight | 1097 +---------------------+---------------------+ 1098 | 0.2 | 1 | 1099 +---------------------+---------------------+ 1100 | 6 | 1 | 1101 +---------------------+---------------------+ 1102 | 8 | 1 | 1103 +---------------------+---------------------+ 1104 | 9 | 1 | 1105 +---------------------+---------------------+ 1106 | 10 | 1 | 1107 +---------------------+---------------------+ 1108 | 25 | 1 | 1109 +---------------------+---------------------+ 1110 | 26 | 1 | 1111 +---------------------+---------------------+ 1112 | 35 | 1 | 1113 +---------------------+---------------------+ 1114 | 59 | 1 | 1115 +---------------------+---------------------+ 1116 | 347 | 1 | 1117 +---------------------+---------------------+ 1119 Table 3: Mixed Objects 1121 7.3.3.3. Test Results Validation Criteria 1123 The following test Criteria is defined as test results validation 1124 criteria. Test results validation criteria MUST be monitored during 1125 the whole sustain phase of the traffic load profile 1127 a. Number of failed Application transactions (receiving any HTTP 1128 response code other than 200 OK) MUST be less than 0.001% (1 out 1129 of 100,000 transactions) of attempt transactions. 1131 b. Traffic should be forwarded constantly. 1133 c. Concurrent connetions MUST be constant. The deviation of 1134 concurrent TCP connection MUST NOT increase more than 10% 1136 7.3.3.4. Measurement 1138 The KPI metrics MUST be reported for this test scenario: 1140 average Throughput and average HTTP Transactions per Second 1142 7.3.4. Test Procedures and Expected Results 1144 The test procedure is designed to measure HTTP throughput of the DUT/ 1145 SUT. The test procedure consists of three major steps. This test 1146 procedure MAY be repeated multiple times with different IPv4 and IPv6 1147 traffic distribution and HTTP response object sizes. 1149 7.3.4.1. Step 1: Test Initialization and Qualification 1151 Verify the link status of the all connected physical interfaces. All 1152 interfaces are expected to be in "UP" status. 1154 Configure traffic load profile of the test equipment to establish 1155 "Initial Throughput" as defined in the parameters Section 7.3.3.2. 1157 The traffic load profile SHOULD be defined as described in 1158 Section 4.3.4. The DUT/SUT SHOULD reach the "Initial Throughput" 1159 during the sustain phase. Measure all KPI as defined in 1160 Section 7.3.3.4. 1162 The measured KPIs during the sustain phase MUST meet the validation 1163 criteria "a" defined in Section 7.3.3.3. 1165 If the KPI metrics do not meet the validation criteria, the test 1166 procedure MUST NOT be continued to "Step 2". 1168 7.3.4.2. Step 2: Test Run with Target Objective 1170 The test equipment SHOULD start to measure and record all specified 1171 KPIs. The frequency of measurement SHOULD be 2 seconds. Continue 1172 the test until all traffic profile phases are completed. 1174 The DUT/SUT is expected to reach the desired "Target Throughput" at 1175 the sustain phase. In addition, the measured KPIs must meet all 1176 validation criteria. 1178 Perform the test separately for each HTTP response object size. 1180 Follow step 3, if the KPI metrics do not meet the validation 1181 criteria. 1183 7.3.4.3. Step 3: Test Iteration 1185 Determine the maximum and average achievable throughput within the 1186 validation criteria. Final test iteration MUST be performed for the 1187 test duration defined in Section 4.3.4. 1189 7.4. TCP/HTTP Transaction Latency 1191 7.4.1. Objective 1193 Using HTTP traffic, determine the average HTTP transaction latency 1194 when DUT is running with sustainable HTTP transactions per second 1195 supported by the DUT/SUT under different HTTP response object sizes. 1197 Test iterations MUST be performed with different HTTP response object 1198 sizes in two different scenarios.one with a single transaction and 1199 the other with multiple transactions within a single TCP connection. 1200 For consistency both the single and multiple transaction test MUST be 1201 configured with HTTP 1.1. 1203 Scenario 1: The client MUST negotiate HTTP 1.1 and close the 1204 connection with FIN immediately after completion of a single 1205 transaction (GET and RESPONSE). 1207 Scenario 2: The client MUST negotiate HTTP 1.1 and close the 1208 connection FIN immediately after completion of 10 transactions (GET 1209 and RESPONSE) within a single TCP connection. 1211 7.4.2. Test Setup 1213 Test bed setup SHOULD be configured as defined in Section 4. Any 1214 specific test bed configuration changes such as number of interfaces 1215 and interface type, etc. MUST be documented. 1217 7.4.3. Test Parameters 1219 In this section, test scenario specific parameters SHOULD be defined. 1221 7.4.3.1. DUT/SUT Configuration Parameters 1223 DUT/SUT parameters MUST conform to the requirements defined in 1224 Section 4.2. Any configuration changes for this specific test 1225 scenario MUST be documented. 1227 7.4.3.2. Test Equipment Configuration Parameters 1229 Test equipment configuration parameters MUST conform to the 1230 requirements defined in Section 4.3 . Following parameters MUST be 1231 documented for this test scenario: 1233 Client IP address range defined in Section 4.3.1.2 1235 Server IP address range defined in Section 4.3.2.2 1237 Traffic distribution ratio between IPv4 and IPv6 defined in 1238 Section 4.3.1.2 1240 Target objective for scenario 1: 50% of the maximum connection per 1241 second measured in test scenario TCP/HTTP Connections Per Second 1242 (Section 7.2) 1244 Target objective for scenario 2: 50% of the maximum throughput 1245 measured in test scenario HTTP Throughput (Section 7.3) 1247 Initial objective for scenario 1: 10% of Target objective for 1248 scenario 1" 1250 Initial objective for scenario 2: 10% of "Target objective for 1251 scenario 2" 1253 HTTP transaction per TCP connection: test scenario 1 with single 1254 transaction and the second scenario with 10 transactions 1256 HTTP 1.1 with GET command requesting a single object. The 1257 RECOMMENDED object sizes are 1, 16 or 64 KByte. For each test 1258 iteration, client MUST request a single HTTP response object size. 1260 7.4.3.3. Test Results Validation Criteria 1262 The following test Criteria is defined as test results validation 1263 criteria. Test results validation criteria MUST be monitored during 1264 the whole sustain phase of the traffic load profile. Ramp up and 1265 ramp down phase SHOULD NOT be considered. 1267 Generic criteria: 1269 a. Number of failed Application transactions (receiving any HTTP 1270 response code other than 200 OK) MUST be less than 0.001% (1 out 1271 of 100,000 transactions) of attempt transactions. 1273 b. Number of Terminated TCP connections due to unexpected TCP RST 1274 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 1275 connections) of total initiated TCP connections 1277 c. During the sustain phase, traffic should be forwarded at a 1278 constant rate. 1280 d. Concurrent TCP connections should be constant during steady 1281 state. This confirms the DUT opens and closes TCP connections at 1282 the same rate. 1284 e. After ramp up the DUT MUST achieve the "Target objective" defined 1285 in the parameter Section 7.4.3.2 and remain in that state for the 1286 entire test duration (sustain phase). 1288 7.4.3.4. Measurement 1290 Following KPI metrics MUST be reported for each test scenario and 1291 HTTP response object sizes separately: 1293 TTFB (minimum, average and maximum) and TTLB (minimum, average and 1294 maximum) 1296 All KPI's are measured once the target throughput achieves the steady 1297 state. 1299 7.4.4. Test Procedures and Expected Results 1301 The test procedure is designed to measure the average application 1302 transaction latencies or TTLB when the DUT is operating close to 50% 1303 of its maximum achievable throughput or connections per second. This 1304 test procedure CAN be repeated multiple times with different IP types 1305 (IPv4 only, IPv6 only and IPv4 and IPv6 mixed traffic distribution), 1306 HTTP response object sizes and single and multiple transactions per 1307 connection scenarios. 1309 7.4.4.1. Step 1: Test Initialization and Qualification 1311 Verify the link status of the all connected physical interfaces. All 1312 interfaces are expected to be in "UP" status. 1314 Configure traffic load profile of the test equipment to establish 1315 "Initial objective" as defined in the parameters Section 7.4.3.2. 1316 The traffic load profile can be defined as described in 1317 Section 4.3.4. 1319 The DUT/SUT SHOULD reach the "Initial objective" before the sustain 1320 phase. The measured KPIs during the sustain phase MUST meet the 1321 validation criteria a, b, c, d, e and f defined in Section 7.4.3.3. 1323 If the KPI metrics do not meet the validation criteria, the test 1324 procedure MUST NOT be continued to "Step 2". 1326 7.4.4.2. Step 2: Test Run with Target Objective 1328 Configure test equipment to establish "Target objective" defined in 1329 the parameters table. The test equipment SHOULD follow the traffic 1330 load profile definition as described in Section 4.3.4. 1332 During the ramp up and sustain phase, other KPIs such as throughput, 1333 concurrent TCP connections and application transactions per second 1334 MUST NOT reach to the maximum value that the DUT/SUT can support. 1335 The test results for specific test iterations SHOULD NOT be reported, 1336 if the above mentioned KPI (especially throughput) reaches to the 1337 maximum value. (Example: If the test iteration with 64 KByte of HTTP 1338 response object size reached the maximum throughput limitation of the 1339 DUT, the test iteration MAY be interrupted and the result for 64 1340 KByte SHOULD NOT be reported). 1342 The test equipment SHOULD start to measure and record all specified 1343 KPIs. The frequency of measurement SHOULD be 2 seconds. Continue 1344 the test until all traffic profile phases are completed. DUT/SUT is 1345 expected to reach the desired "Target objective" at the sustain 1346 phase. In addition, the measured KPIs MUST meet all validation 1347 criteria. 1349 Follow step 3, if the KPI metrics do not meet the validation 1350 criteria. 1352 7.4.4.3. Step 3: Test Iteration 1354 Determine the maximum achievable connections per second within the 1355 validation criteria and measure the latency values. 1357 7.5. Concurrent TCP/HTTP Connection Capacity 1359 7.5.1. Objective 1361 Determine the maximum number of concurrent TCP connections that the 1362 DUT/ SUT sustains when using HTTP traffic. 1364 7.5.2. Test Setup 1366 Test bed setup SHOULD be configured as defined in Section 4. Any 1367 specific test bed configuration changes such as number of interfaces 1368 and interface type, etc. must be documented. 1370 7.5.3. Test Parameters 1372 In this section, test scenario specific parameters SHOULD be defined. 1374 7.5.3.1. DUT/SUT Configuration Parameters 1376 DUT/SUT parameters MUST conform to the requirements defined in 1377 Section 4.2. Any configuration changes for this specific test 1378 scenario MUST be documented. 1380 7.5.3.2. Test Equipment Configuration Parameters 1382 Test equipment configuration parameters MUST conform to the 1383 requirements defined in Section 4.3. Following parameters MUST be 1384 noted for this test scenario: 1386 Client IP address range defined in Section 4.3.1.2 1388 Server IP address range defined in Section 4.3.2.2 1390 Traffic distribution ratio between IPv4 and IPv6 defined in 1391 Section 4.3.1.2 1393 Target concurrent connection: Initial value from product data 1394 sheet (if known) 1396 Initial concurrent connection: 10% of "Target concurrent 1397 connection" 1399 Maximum connections per second during ramp up phase: 50% of 1400 maximum connections per second measured in test scenario TCP/HTTP 1401 Connections per second (Section 7.2) 1403 Ramp up time (in traffic load profile for "Target concurrent 1404 connection"): "Target concurrent connection" / "Maximum 1405 connections per second during ramp up phase" 1407 Ramp up time (in traffic load profile for "Initial concurrent 1408 connection"): "Initial concurrent connection" / "Maximum 1409 connections per second during ramp up phase" 1411 The client MUST negotiate HTTP 1.1 with persistence and each client 1412 MAY open multiple concurrent TCP connections per server endpoint IP. 1414 Each client sends 10 GET commands requesting 1 KByte HTTP response 1415 object in the same TCP connection (10 transactions/TCP connection) 1416 and the delay (think time) between the transaction MUST be X seconds. 1418 X = ("Ramp up time" + "steady state time") /10 1420 The established connections SHOULD remain open until the ramp down 1421 phase of the test. During the ramp down phase, all connections 1422 SHOULD be successfully closed with FIN. 1424 7.5.3.3. Test Results Validation Criteria 1426 The following test Criteria is defined as test results validation 1427 criteria. Test results validation criteria MUST be monitored during 1428 the whole sustain phase of the traffic load profile. 1430 a. Number of failed Application transactions (receiving any HTTP 1431 response code other than 200 OK) MUST be less than 0.001% (1 out 1432 of 100,000 transaction) of total attempted transactions 1434 b. Number of Terminated TCP connections due to unexpected TCP RST 1435 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 1436 connections) of total initiated TCP connections 1438 c. During the sustain phase, traffic should be forwarded constantly 1440 7.5.3.4. Measurement 1442 Following KPI metric MUST be reported for this test scenario: 1444 average Concurrent TCP Connections 1446 7.5.4. Test Procedures and expected Results 1448 The test procedure is designed to measure the concurrent TCP 1449 connection capacity of the DUT/SUT at the sustaining period of 1450 traffic load profile. The test procedure consists of three major 1451 steps. This test procedure MAY be repeated multiple times with 1452 different IPv4 and IPv6 traffic distribution. 1454 7.5.4.1. Step 1: Test Initialization and Qualification 1456 Verify the link status of the all connected physical interfaces. All 1457 interfaces are expected to be in "UP" status. 1459 Configure test equipment to establish "Initial concurrent TCP 1460 connections" defined in Section 7.5.3.2. Except ramp up time, the 1461 traffic load profile SHOULD be defined as described in Section 4.3.4. 1463 During the sustain phase, the DUT/SUT SHOULD reach the "Initial 1464 concurrent TCP connections". The measured KPIs during the sustain 1465 phase MUST meet the validation criteria "a" and "b" defined in 1466 Section 7.5.3.3. 1468 If the KPI metrics do not meet the validation criteria, the test 1469 procedure MUST NOT be continued to "Step 2". 1471 7.5.4.2. Step 2: Test Run with Target Objective 1473 Configure test equipment to establish "Target concurrent TCP 1474 connections". The test equipment SHOULD follow the traffic load 1475 profile definition (except ramp up time) as described in 1476 Section 4.3.4. 1478 During the ramp up and sustain phase, the other KPIs such as 1479 throughput, TCP connections per second and application transactions 1480 per second MUST NOT reach to the maximum value that the DUT/SUT can 1481 support. 1483 The test equipment SHOULD start to measure and record KPIs defined in 1484 Section 7.5.3.4. The frequency of measurement SHOULD be 2 seconds. 1485 Continue the test until all traffic profile phases are completed. 1487 The DUT/SUT is expected to reach the desired target concurrent 1488 connection at the sustain phase. In addition, the measured KPIs must 1489 meet all validation criteria. 1491 Follow step 3, if the KPI metrics do not meet the validation 1492 criteria. 1494 7.5.4.3. Step 3: Test Iteration 1496 Determine the maximum and average achievable concurrent TCP 1497 connections capacity within the validation criteria. 1499 7.6. TCP/HTTPS Connections per second 1501 7.6.1. Objective 1503 Using HTTPS traffic, determine the maximum sustainable SSL/TLS 1504 session establishment rate supported by the DUT/SUT under different 1505 throughput load conditions. 1507 Test iterations MUST include common cipher suites and key strengths 1508 as well as forward looking stronger keys. Specific test iterations 1509 MUST include ciphers and keys defined in Section 7.6.3.2. 1511 For each cipher suite and key strengths, test iterations MUST use a 1512 single HTTPS response object size defined in the test equipment 1513 configuration parameters Section 7.6.3.2 to measure connections per 1514 second performance under a variety of DUT Security inspection load 1515 conditions. 1517 7.6.2. Test Setup 1519 Test bed setup SHOULD be configured as defined in Section 4. Any 1520 specific test bed configuration changes such as number of interfaces 1521 and interface type, etc. MUST be documented. 1523 7.6.3. Test Parameters 1525 In this section, test scenario specific parameters SHOULD be defined. 1527 7.6.3.1. DUT/SUT Configuration Parameters 1529 DUT/SUT parameters MUST conform to the requirements defined in 1530 Section 4.2. Any configuration changes for this specific test 1531 scenario MUST be documented. 1533 7.6.3.2. Test Equipment Configuration Parameters 1535 Test equipment configuration parameters MUST conform to the 1536 requirements defined in Section 4.3. Following parameters MUST be 1537 documented for this test scenario: 1539 Client IP address range defined in Section 4.3.1.2 1541 Server IP address range defined in Section 4.3.2.2 1543 Traffic distribution ratio between IPv4 and IPv6 defined in 1544 Section 4.3.1.2 1546 Target connections per second: Initial value from product data sheet 1547 (if known) 1549 Initial connections per second: 10% of "Target connections per 1550 second" 1552 RECOMMENDED ciphers and keys: 1554 1. ECHDE-ECDSA-AES128-GCM-SHA256 with Prime256v1 (Signature Hash 1555 Algorithm: ecdsa_secp256r1_sha256 and Supported group: sepc256r1) 1557 2. ECDHE-RSA-AES128-GCM-SHA256 with RSA 2048 (Signature Hash 1558 Algorithm: rsa_pkcs1_sha256 and Supported group: sepc256) 1560 3. ECDHE-ECDSA-AES256-GCM-SHA384 with Secp521 (Signature Hash 1561 Algorithm: ecdsa_secp384r1_sha384 and Supported group: sepc521r1) 1563 4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash 1564 Algorithm: rsa_pkcs1_sha384 and Supported group: secp256) 1566 The client MUST negotiate HTTPS 1.1 and close the connection with FIN 1567 immediately after completion of one transaction. In each test 1568 iteration, client MUST send GET command requesting a fixed HTTPS 1569 response object size. The RECOMMENDED object sizes are 1, 2, 4, 16, 1570 64 KByte. 1572 7.6.3.3. Test Results Validation Criteria 1574 The following test Criteria is defined as test results validation 1575 criteria: 1577 a. Number of failed Application transactions (receiving any HTTP 1578 response code other than 200 OK) MUST be less than 0.001% (1 out 1579 of 100,000 transactions) of attempt transactions 1581 b. Number of Terminated TCP connections due to unexpected TCP RST 1582 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 1583 connections) of total initiated TCP connections 1585 c. During the sustain phase, traffic should be forwarded at a 1586 constant rate 1588 d. Concurrent TCP connections SHOULD be constant during steady 1589 state. This confirms that the DUT open and close the TCP 1590 connections at the same rate 1592 7.6.3.4. Measurement 1594 Following KPI metrics MUST be reported for this test scenario: 1596 average TCP Connections Per Second, average TLS Handshake Rate (TLS 1597 Handshake Rate can be measured in the test scenario using 1KB object 1598 size) 1600 7.6.4. Test Procedures and expected Results 1602 The test procedure is designed to measure the TCP connections per 1603 second rate of the DUT/SUT at the sustaining period of traffic load 1604 profile. The test procedure consists of three major steps. This 1605 test procedure MAY be repeated multiple times with different IPv4 and 1606 IPv6 traffic distribution. 1608 7.6.4.1. Step 1: Test Initialization and Qualification 1610 Verify the link status of all connected physical interfaces. All 1611 interfaces are expected to be in "UP" status. 1613 Configure traffic load profile of the test equipment to establish 1614 "Initial connections per second" as defined in Section 7.6.3.2. The 1615 traffic load profile CAN be defined as described in Section 4.3.4. 1617 The DUT/SUT SHOULD reach the "Initial connections per second" before 1618 the sustain phase. The measured KPIs during the sustain phase MUST 1619 meet the validation criteria a, b, c, and d defined in 1620 Section 7.6.3.3. 1622 If the KPI metrics do not meet the validation criteria, the test 1623 procedure MUST NOT be continued to "Step 2". 1625 7.6.4.2. Step 2: Test Run with Target Objective 1627 Configure test equipment to establish "Target connections per second" 1628 defined in the parameters table. The test equipment SHOULD follow 1629 the traffic load profile definition as described in Section 4.3.4. 1631 During the ramp up and sustain phase, other KPIs such as throughput, 1632 concurrent TCP connections and application transactions per second 1633 MUST NOT reach the maximum value that the DUT/SUT can support. The 1634 test results for specific test iteration SHOULD NOT be reported, if 1635 the above mentioned KPI (especially throughput) reaches the maximum 1636 value. (Example: If the test iteration with 64 KByte of HTTPS 1637 response object size reached the maximum throughput limitation of the 1638 DUT, the test iteration can be interrupted and the result for 64 1639 KByte SHOULD NOT be reported). 1641 The test equipment SHOULD start to measure and record all specified 1642 KPIs. The frequency of measurement SHOULD be 2 seconds. Continue 1643 the test until all traffic profile phases are completed. 1645 The DUT/SUT is expected to reach the desired target connections per 1646 second rate at the sustain phase. In addition, the measured KPIs 1647 must meet all validation criteria. 1649 Follow the step 3, if the KPI metrics do not meet the validation 1650 criteria. 1652 7.6.4.3. Step 3: Test Iteration 1654 Determine the maximum and average achievable connections per second 1655 within the validation criteria. 1657 7.7. HTTPS Throughput 1659 7.7.1. Objective 1661 Determine the throughput for HTTPS transactions varying the HTTPS 1662 response object size. 1664 Test iterations MUST include common cipher suites and key strengths 1665 as well as forward looking stronger keys. Specific test iterations 1666 MUST include the ciphers and keys defined in the parameter 1667 Section 7.7.3.2. 1669 7.7.2. Test Setup 1671 Test bed setup SHOULD be configured as defined in Section 4. Any 1672 specific test bed configuration changes such as number of interfaces 1673 and interface type, etc. must be documented. 1675 7.7.3. Test Parameters 1677 In this section, test scenario specific parameters SHOULD be defined. 1679 7.7.3.1. DUT/SUT Configuration Parameters 1681 DUT/SUT parameters MUST conform to the requirements defined in 1682 Section 4.2. Any configuration changes for this specific test 1683 scenario MUST be documented. 1685 7.7.3.2. Test Equipment Configuration Parameters 1687 Test equipment configuration parameters MUST conform to the 1688 requirements defined in Section 4.3. Following parameters MUST be 1689 documented for this test scenario: 1691 Client IP address range defined in Section 4.3.1.2 1693 Server IP address range defined in Section 4.3.2.2 1695 Traffic distribution ratio between IPv4 and IPv6 defined in 1696 Section 4.3.1.2 1697 Target Throughput: Initial value from product data sheet (if known) 1699 Initial Throughput: 10% of "Target Throughput" 1701 Number of HTTPS response object requests (transactions) per 1702 connection: 10 1704 RECOMMENDED ciphers and keys: 1706 1. ECHDE-ECDSA-AES128-GCM-SHA256 with Prime256v1 (Signature Hash 1707 Algorithm: ecdsa_secp256r1_sha256 and Supported group: sepc256r1) 1709 2. ECDHE-RSA-AES128-GCM-SHA256 with RSA 2048 (Signature Hash 1710 Algorithm: rsa_pkcs1_sha256 and Supported group: sepc256) 1712 3. ECDHE-ECDSA-AES256-GCM-SHA384 with Secp521 (Signature Hash 1713 Algorithm: ecdsa_secp384r1_sha384 and Supported group: sepc521r1) 1715 4. ECDHE-RSA-AES256-GCM-SHA384 with RSA 4096 (Signature Hash 1716 Algorithm: rsa_pkcs1_sha384 and Supported group: secp256) 1718 RECOMMENDED HTTPS response object size: 1 KByte, 2 KByte, 4 KByte, 16 1719 KByte, 64 KByte, 256 KByte and mixed object defined in the table 1720 below. 1722 +---------------------+---------------------+ 1723 | Object size (KByte) | Number of requests/ | 1724 | | Weight | 1725 +---------------------+---------------------+ 1726 | 0.2 | 1 | 1727 +---------------------+---------------------+ 1728 | 6 | 1 | 1729 +---------------------+---------------------+ 1730 | 8 | 1 | 1731 +---------------------+---------------------+ 1732 | 9 | 1 | 1733 +---------------------+---------------------+ 1734 | 10 | 1 | 1735 +---------------------+---------------------+ 1736 | 25 | 1 | 1737 +---------------------+---------------------+ 1738 | 26 | 1 | 1739 +---------------------+---------------------+ 1740 | 35 | 1 | 1741 +---------------------+---------------------+ 1742 | 59 | 1 | 1743 +---------------------+---------------------+ 1744 | 347 | 1 | 1745 +---------------------+---------------------+ 1747 Table 4: Mixed Objects 1749 7.7.3.3. Test Results Validation Criteria 1751 The following test Criteria is defined as test results validation 1752 criteria. Test results validation criteria MUST be monitored during 1753 the whole sustain phase of the traffic load profile. 1755 a. Number of failed Application transactions (receiving any HTTP 1756 response code other than 200 OK) MUST be less than 0.001% (1 out 1757 of 100,000 transactions) of attempt transactions. 1759 b. Traffic should be forwarded constantly. 1761 c. The deviation of concurrent TCP connections MUST be less than 10% 1763 7.7.3.4. Measurement 1765 The KPI metrics MUST be reported for this test scenario: 1767 average Throughput and average HTTPS Transactions Per Second 1769 7.7.4. Test Procedures and Expected Results 1771 The test procedure consists of three major steps. This test 1772 procedure MAY be repeated multiple times with different IPv4 and IPv6 1773 traffic distribution and HTTPS response object sizes. 1775 7.7.4.1. Step 1: Test Initialization and Qualification 1777 Verify the link status of the all connected physical interfaces. All 1778 interfaces are expected to be in "UP" status. 1780 Configure traffic load profile of the test equipment to establish 1781 "initial throughput" as defined in the parameters Section 7.7.3.2. 1783 The traffic load profile should be defined as described in 1784 Section 4.3.4. The DUT/SUT SHOULD reach the "Initial Throughput" 1785 during the sustain phase. Measure all KPI as defined in 1786 Section 7.7.3.4. 1788 The measured KPIs during the sustain phase MUST meet the validation 1789 criteria "a" defined in Section 7.7.3.3. 1791 If the KPI metrics do not meet the validation criteria, the test 1792 procedure MUST NOT be continued to "Step 2". 1794 7.7.4.2. Step 2: Test Run with Target Objective 1796 The test equipment SHOULD start to measure and record all specified 1797 KPIs. The frequency of measurement SHOULD be 2 seconds. Continue 1798 the test until all traffic profile phases are completed. 1800 The DUT/SUT is expected to reach the desired "Target Throughput" at 1801 the sustain phase. In addition, the measured KPIs MUST meet all 1802 validation criteria. 1804 Perform the test separately for each HTTPS response object size. 1806 Follow step 3, if the KPI metrics do not meet the validation 1807 criteria. 1809 7.7.4.3. Step 3: Test Iteration 1811 Determine the maximum and average achievable throughput within the 1812 validation criteria. Final test iteration MUST be performed for the 1813 test duration defined in Section 4.3.4. 1815 7.8. HTTPS Transaction Latency 1817 7.8.1. Objective 1819 Using HTTPS traffic, determine the average HTTPS transaction latency 1820 when DUT is running with sustainable HTTPS transactions per second 1821 supported by the DUT/SUT under different HTTPS response object size. 1823 Scenario 1: The client MUST negotiate HTTPS and close the connection 1824 with FIN immediately after completion of a single transaction (GET 1825 and RESPONSE). 1827 Scenario 2: The client MUST negotiate HTTPS and close the connection 1828 with FIN immediately after completion of 10 transactions (GET and 1829 RESPONSE) within a single TCP connection. 1831 7.8.2. Test Setup 1833 Test bed setup SHOULD be configured as defined in Section 4. Any 1834 specific test bed configuration changes such as number of interfaces 1835 and interface type, etc. MUST be documented. 1837 7.8.3. Test Parameters 1839 In this section, test scenario specific parameters SHOULD be defined. 1841 7.8.3.1. DUT/SUT Configuration Parameters 1843 DUT/SUT parameters MUST conform to the requirements defined in 1844 Section 4.2. Any configuration changes for this specific test 1845 scenario MUST be documented. 1847 7.8.3.2. Test Equipment Configuration Parameters 1849 Test equipment configuration parameters MUST conform to the 1850 requirements defined in Section 4.3. Following parameters MUST be 1851 documented for this test scenario: 1853 Client IP address range defined in Section 4.3.1.2 1855 Server IP address range defined in Section 4.3.2.2 1857 Traffic distribution ratio between IPv4 and IPv6 defined in 1858 Section 4.3.1.2 1860 RECOMMENDED cipher suites and key size: ECDHE-ECDSA-AES256-GCM-SHA384 1861 with Secp521 bits key size (Signature Hash Algorithm: 1862 ecdsa_secp384r1_sha384 and Supported group: sepc521r1) 1863 Target objective for scenario 1: 50% of the maximum connections per 1864 second measured in test scenario TCP/HTTPS Connections per second 1865 (Section 7.6) 1867 Target objective for scenario 2: 50% of the maximum throughput 1868 measured in test scenario HTTPS Throughput (Section 7.7) 1870 Initial objective for scenario 1: 10% of Target objective for 1871 scenario 1" 1873 Initial objective for scenario 2: 10% of "Target objective for 1874 scenario 2" 1876 HTTPS transaction per TCP connection: test scenario 1 with single 1877 transaction and the second scenario with 10 transactions 1879 HTTPS 1.1 with GET command requesting a single 1, 16 or 64 KByte 1880 object. For each test iteration, client MUST request a single HTTPS 1881 response object size. 1883 7.8.3.3. Test Results Validation Criteria 1885 The following test Criteria is defined as test results validation 1886 criteria. Test results validation criteria MUST be monitored during 1887 the whole sustain phase of the traffic load profile. Ramp up and 1888 ramp down phase SHOULD NOT be considered. 1890 Generic criteria: 1892 a. Number of failed Application transactions (receiving any HTTP 1893 response code other than 200 OK) MUST be less than 0.001% (1 out 1894 of 100,000 transactions) of attempt transactions. 1896 b. Number of Terminated TCP connections due to unexpected TCP RST 1897 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 1898 connections) of total initiated TCP connections 1900 c. During the sustain phase, traffic should be forwarded at a 1901 constant rate. 1903 d. Concurrent TCP connections should be constant during steady 1904 state. This confirms the DUT opens and closes TCP connections at 1905 the same rate. 1907 e. After ramp up the DUT MUST achieve the "Target objective" defined 1908 in the parameter Section 7.8.3.2 and remain in that state for the 1909 entire test duration (sustain phase). 1911 7.8.3.4. Measurement 1913 Following KPI metrics MUST be reported for each test scenario and 1914 HTTPS response object sizes separately: 1916 TTFB (minimum, average and maximum) and TTLB (minimum, average and 1917 maximum) 1919 All KPI's are measured once the target connections per second 1920 achieves the steady state. 1922 7.8.4. Test Procedures and Expected Results 1924 The test procedure is designed to measure average TTFB or TTLB when 1925 the DUT is operating close to 50% of its maximum achievable 1926 connections per second. This test procedure can be repeated multiple 1927 times with different IP types (IPv4 only, IPv6 only and IPv4 and IPv6 1928 mixed traffic distribution), HTTPS response object sizes and single 1929 and multiple transactions per connection scenarios. 1931 7.8.4.1. Step 1: Test Initialization and Qualification 1933 Verify the link status of the all connected physical interfaces. All 1934 interfaces are expected to be in "UP" status. 1936 Configure traffic load profile of the test equipment to establish 1937 "Initial objective" as defined in the parameters Section 7.8.3.2. 1938 The traffic load profile can be defined as described in 1939 Section 4.3.4. 1941 The DUT/SUT SHOULD reach the "Initial objective" before the sustain 1942 phase. The measured KPIs during the sustain phase MUST meet the 1943 validation criteria a, b, c, d, e and f defined in Section 7.8.3.3. 1945 If the KPI metrics do not meet the validation criteria, the test 1946 procedure MUST NOT be continued to "Step 2". 1948 7.8.4.2. Step 2: Test Run with Target Objective 1950 Configure test equipment to establish "Target objective" defined in 1951 the parameters table. The test equipment SHOULD follow the traffic 1952 load profile definition as described in Section 4.3.4. 1954 During the ramp up and sustain phase, other KPIs such as throughput, 1955 concurrent TCP connections and application transactions per second 1956 MUST NOT reach to the maximum value that the DUT/SUT can support. 1957 The test results for specific test iterations SHOULD NOT be reported, 1958 if the above mentioned KPI (especially throughput) reaches to the 1959 maximum value. (Example: If the test iteration with 64 KByte of HTTP 1960 response object size reached the maximum throughput limitation of the 1961 DUT, the test iteration MAY be interrupted and the result for 64 1962 KByte SHOULD NOT be reported). 1964 The test equipment SHOULD start to measure and record all specified 1965 KPIs. The frequency of measurement SHOULD be 2 seconds. Continue 1966 the test until all traffic profile phases are completed. DUT/SUT is 1967 expected to reach the desired "Target objective" at the sustain 1968 phase. In addition, the measured KPIs MUST meet all validation 1969 criteria. 1971 Follow step 3, if the KPI metrics do not meet the validation 1972 criteria. 1974 7.8.4.3. Step 3: Test Iteration 1976 Determine the maximum achievable connections per second within the 1977 validation criteria and measure the latency values. 1979 7.9. Concurrent TCP/HTTPS Connection Capacity 1981 7.9.1. Objective 1983 Determine the maximum number of concurrent TCP connections that the 1984 DUT/SUT sustains when using HTTPS traffic. 1986 7.9.2. Test Setup 1988 Test bed setup SHOULD be configured as defined in Section 4. Any 1989 specific test bed configuration changes such as number of interfaces 1990 and interface type, etc. MUST be documented. 1992 7.9.3. Test Parameters 1994 In this section, test scenario specific parameters SHOULD be defined. 1996 7.9.3.1. DUT/SUT Configuration Parameters 1998 DUT/SUT parameters MUST conform to the requirements defined in 1999 Section 4.2. Any configuration changes for this specific test 2000 scenario MUST be documented. 2002 7.9.3.2. Test Equipment Configuration Parameters 2004 Test equipment configuration parameters MUST conform to the 2005 requirements defined in Section 4.3. Following parameters MUST be 2006 documented for this test scenario: 2008 Client IP address range defined in Section 4.3.1.2 2010 Server IP address range defined in Section 4.3.2.2 2012 Traffic distribution ratio between IPv4 and IPv6 defined in 2013 Section 4.3.1.2 2015 RECOMMENDED cipher suites and key size: ECDHE-ECDSA-AES256-GCM- 2016 SHA384 with Secp521 bits key size (Signature Hash Algorithm: 2017 ecdsa_secp384r1_sha384 and Supported group: sepc521r1) 2019 Target concurrent connections: Initial value from product data 2020 sheet (if known) 2022 Initial concurrent connections: 10% of "Target concurrent 2023 connections" 2025 Connections per second during ramp up phase: 50% of maximum 2026 connections per second measured in test scenario TCP/HTTPS 2027 Connections per second (Section 7.6) 2029 Ramp up time (in traffic load profile for "Target concurrent 2030 connections"): "Target concurrent connections" / "Maximum 2031 connections per second during ramp up phase" 2033 Ramp up time (in traffic load profile for "Initial concurrent 2034 connections"): "Initial concurrent connections" / "Maximum 2035 connections per second during ramp up phase" 2037 The client MUST perform HTTPS transaction with persistence and each 2038 client can open multiple concurrent TCP connections per server 2039 endpoint IP. 2041 Each client sends 10 GET commands requesting 1 KByte HTTPS response 2042 objects in the same TCP connections (10 transactions/TCP connection) 2043 and the delay (think time) between each transactions MUST be X 2044 seconds. 2046 X = ("Ramp up time" + "steady state time") /10 2048 The established connections SHOULD remain open until the ramp down 2049 phase of the test. During the ramp down phase, all connections 2050 SHOULD be successfully closed with FIN. 2052 7.9.3.3. Test Results Validation Criteria 2054 The following test Criteria is defined as test results validation 2055 criteria. Test results validation criteria MUST be monitored during 2056 the whole sustain phase of the traffic load profile. 2058 a. Number of failed Application transactions (receiving any HTTP 2059 response code other than 200 OK) MUST be less than 0.001% (1 out 2060 of 100,000 transactions) of total attempted transactions 2062 b. Number of Terminated TCP connections due to unexpected TCP RST 2063 sent by DUT/SUT MUST be less than 0.001% (1 out of 100,000 2064 connections) of total initiated TCP connections 2066 c. During the sustain phase, traffic SHOULD be forwarded constantly 2068 7.9.3.4. Measurement 2070 Following KPI metric MUST be reported for this test scenario: 2072 average Concurrent TCP Connections 2074 7.9.4. Test Procedures and expected Results 2076 The test procedure is designed to measure the concurrent TCP 2077 connection capacity of the DUT/SUT at the sustaining period of 2078 traffic load profile. The test procedure consists of three major 2079 steps. This test procedure MAY be repeated multiple times with 2080 different IPv4 and IPv6 traffic distribution. 2082 7.9.4.1. Step 1: Test Initialization and Qualification 2084 Verify the link status of all connected physical interfaces. All 2085 interfaces are expected to be in "UP" status. 2087 Configure test equipment to establish "initial concurrent TCP 2088 connections" defined in Section 7.9.3.2. Except ramp up time, the 2089 traffic load profile SHOULD be defined as described in Section 4.3.4. 2091 During the sustain phase, the DUT/SUT SHOULD reach the "Initial 2092 concurrent TCP connections". The measured KPIs during the sustain 2093 phase MUST meet the validation criteria "a" and "b" defined in 2094 Section 7.9.3.3. 2096 If the KPI metrics do not meet the validation criteria, the test 2097 procedure MUST NOT be continued to "Step 2". 2099 7.9.4.2. Step 2: Test Run with Target Objective 2101 Configure test equipment to establish "Target concurrent TCP 2102 connections".The test equipment SHOULD follow the traffic load 2103 profile definition (except ramp up time) as described in 2104 Section 4.3.4. 2106 During the ramp up and sustain phase, the other KPIs such as 2107 throughput, TCP connections per second and application transactions 2108 per second MUST NOT reach to the maximum value that the DUT/SUT can 2109 support. 2111 The test equipment SHOULD start to measure and record KPIs defined in 2112 Section 7.9.3.4. The frequency of measurement SHOULD be 2 seconds. 2113 Continue the test until all traffic profile phases are completed. 2115 The DUT/SUT is expected to reach the desired target concurrent 2116 connections at the sustain phase. In addition, the measured KPIs 2117 MUST meet all validation criteria. 2119 Follow step 3, if the KPI metrics do not meet the validation 2120 criteria. 2122 7.9.4.3. Step 3: Test Iteration 2124 Determine the maximum and average achievable concurrent TCP 2125 connections within the validation criteria. 2127 8. Formal Syntax 2129 9. IANA Considerations 2131 This document makes no request of IANA. 2133 Note to RFC Editor: this section may be removed on publication as an 2134 RFC. 2136 10. Security Considerations 2138 The primary goal of this document is to provide benchmarking 2139 terminology and methodology for next-generation network security 2140 devices. However, readers should be aware that there is some overlap 2141 between performance and security issues. Specifically, the optimal 2142 configuration for network security device performance may not be the 2143 most secure, and vice-versa. The Cipher suites are recommended in 2144 this document are just for test purpose only. The Cipher suite 2145 recommendation for a real deployment is outside the scope of this 2146 document. 2148 11. Acknowledgements 2150 Acknowledgements will be added in the future release. 2152 12. Contributors 2154 The authors would like to thank the many people that contributed 2155 their time and knowledge to this effort. 2157 Specifically, to the co-chairs of the NetSecOPEN Test Methodology 2158 working group and the NetSecOPEN Security Effectiveness working group 2159 - Alex Samonte, Aria Eslambolchizadeh, Carsten Rossenhoevel and David 2160 DeSanto. 2162 Additionally, the following people provided input, comments and spent 2163 time reviewing the myriad of drafts. If we have missed anyone the 2164 fault is entirely our own. Thanks to - Amritam Putatunda, Chao Guo, 2165 Chris Chapman, Chris Pearson, Chuck McAuley, David White, Jurrie Van 2166 Den Breekel, Michelle Rhines, Rob Andrews, Samaresh Nair, and Tim 2167 Winters. 2169 13. References 2171 13.1. Normative References 2173 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2174 Requirement Levels", BCP 14, RFC 2119, 2175 DOI 10.17487/RFC2119, March 1997, 2176 . 2178 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2179 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2180 May 2017, . 2182 13.2. Informative References 2184 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 2185 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 2186 Transfer Protocol -- HTTP/1.1", RFC 2616, 2187 DOI 10.17487/RFC2616, June 1999, 2188 . 2190 [RFC2647] Newman, D., "Benchmarking Terminology for Firewall 2191 Performance", RFC 2647, DOI 10.17487/RFC2647, August 1999, 2192 . 2194 [RFC3511] Hickman, B., Newman, D., Tadjudin, S., and T. Martin, 2195 "Benchmarking Methodology for Firewall Performance", 2196 RFC 3511, DOI 10.17487/RFC3511, April 2003, 2197 . 2199 [RFC5681] Allman, M., Paxson, V., and E. Blanton, "TCP Congestion 2200 Control", RFC 5681, DOI 10.17487/RFC5681, September 2009, 2201 . 2203 Appendix A. NetSecOPEN Basic Traffic Mix 2205 A traffic mix for testing performance of next generation firewalls 2206 MUST scale to stress the DUT based on real-world conditions. In 2207 order to achieve this the following MUST be included: 2209 o Clients connecting to multiple different server FQDNs per 2210 application 2212 o Clients loading apps and pages with connections and objects in 2213 specific orders 2215 o Multiple unique certificates for HTTPS/TLS 2217 o A wide variety of different object sizes 2219 o Different URL paths 2221 o Mix of HTTP and HTTPS 2223 A traffic mix for testing performance of next generation firewalls 2224 MUST also facility application identification using different 2225 detection methods with and without decryption of the traffic. Such 2226 as: 2228 o HTTP HOST based application detection 2230 o HTTPS/TLS Server Name Indication (SNI) 2232 o Certificate Subject Common Name (CN) 2234 The mix MUST be of sufficient complexity and volume to render 2235 differences in individual apps as statistically insignificant. For 2236 example, changes in like to like apps - such as one type of video 2237 service vs. another both consist of larger objects whereas one news 2238 site vs. another both typically have more connections then other apps 2239 because of trackers and embedded advertising content. To achieve 2240 sufficient complexity, a mix MUST have: 2242 o Thousands of URLs each client walks thru 2244 o Hundreds of FQDNs each client connects to 2246 o Hundreds of unique certificates for HTTPS/TLS 2248 o Thousands of different object sizes per client in orders matching 2249 applications 2251 The following is a description of what a popular application in an 2252 enterprise traffic mix contains. 2254 Table 5 lists the FQDNs, number of transactions and bytes transferred 2255 as an example client interacts with Office 365 Outlook, Word, Excel, 2256 PowerPoint, SharePoint and Skype. 2258 +---------------------------------+------------+-------------+ 2259 | Office365 FQDN | Bytes | Transaction | 2260 +============================================================+ 2261 | r1.res.office365.com | 14,056,960 | 192 | 2262 +---------------------------------+------------+-------------+ 2263 | s1-word-edit-15.cdn.office.net | 6,731,019 | 22 | 2264 +---------------------------------+------------+-------------+ 2265 | company1-my.sharepoint.com | 6,269,492 | 42 | 2266 +---------------------------------+------------+-------------+ 2267 | swx.cdn.skype.com | 6,100,027 | 12 | 2268 +---------------------------------+------------+-------------+ 2269 | static.sharepointonline.com | 6,036,947 | 41 | 2270 +---------------------------------+------------+-------------+ 2271 | spoprod-a.akamaihd.net | 3,904,250 | 25 | 2272 +---------------------------------+------------+-------------+ 2273 | s1-excel-15.cdn.office.net | 2,767,941 | 16 | 2274 +---------------------------------+------------+-------------+ 2275 | outlook.office365.com | 2,047,301 | 86 | 2276 +---------------------------------+------------+-------------+ 2277 | shellprod.msocdn.com | 1,008,370 | 11 | 2278 +---------------------------------+------------+-------------+ 2279 | word-edit.officeapps.live.com | 932,080 | 25 | 2280 +---------------------------------+------------+-------------+ 2281 | res.delve.office.com | 760,146 | 2 | 2282 +---------------------------------+------------+-------------+ 2283 | s1-powerpoint-15.cdn.office.net | 557,604 | 3 | 2284 +---------------------------------+------------+-------------+ 2285 | appsforoffice.microsoft.com | 511,171 | 5 | 2286 +---------------------------------+------------+-------------+ 2287 | powerpoint.officeapps.live.com | 471,625 | 14 | 2288 +---------------------------------+------------+-------------+ 2289 | excel.officeapps.live.com | 342,040 | 14 | 2290 +---------------------------------+------------+-------------+ 2291 | s1-officeapps-15.cdn.office.net | 331,343 | 5 | 2292 +---------------------------------+------------+-------------+ 2293 | webdir0a.online.lync.com | 66,930 | 15 | 2294 +---------------------------------+------------+-------------+ 2295 | portal.office.com | 13,956 | 1 | 2296 +---------------------------------+------------+-------------+ 2297 | config.edge.skype.com | 6,911 | 2 | 2298 +---------------------------------+------------+-------------+ 2299 | clientlog.portal.office.com | 6,608 | 8 | 2300 +---------------------------------+------------+-------------+ 2301 | webdir.online.lync.com | 4,343 | 5 | 2302 +---------------------------------+------------+-------------+ 2303 | graph.microsoft.com | 2,289 | 2 | 2304 +---------------------------------+------------+-------------+ 2305 | nam.loki.delve.office.com | 1,812 | 5 | 2306 +---------------------------------+------------+-------------+ 2307 | login.microsoftonline.com | 464 | 2 | 2308 +---------------------------------+------------+-------------+ 2309 | login.windows.net | 232 | 1 | 2310 +---------------------------------+------------+-------------+ 2312 Table 5: Office365 2314 Clients MUST connect to multiple server FQDNs in the same order as 2315 real applications. Connections MUST be made when the client is 2316 interacting with the application and MUST NOT first setup up all 2317 connections. Connections SHOULD stay open per client for subsequent 2318 transactions to the same FQDN similar to how a web browser behaves. 2319 Clients MUST use different URL Paths and Object sizes in orders as 2320 they are observed in real Applications. Clients MAY also setup 2321 multiple connections per FQDN to process multiple transactions in a 2322 sequence at the same time. Table 6 has a partial example sequence of 2323 the Office 365 Word application transactions. 2325 +---------------------------------+----------------------+----------+ 2326 | FQDN | URL Path | Object | 2327 | | | size | 2328 +===================================================================+ 2329 | company1-my.sharepoint.com | /personal... | 23,132 | 2330 +---------------------------------+----------------------+----------+ 2331 | word-edit.officeapps.live.com | /we/WsaUpload.ashx | 2 | 2332 +---------------------------------+----------------------+----------+ 2333 | static.sharepointonline.com | /bld/.../blank.js | 454 | 2334 +---------------------------------+----------------------+----------+ 2335 | static.sharepointonline.com | /bld/.../ | 23,254 | 2336 | | initstrings.js | | 2337 +---------------------------------+----------------------+----------+ 2338 | static.sharepointonline.com | /bld/.../init.js | 292,740 | 2339 +---------------------------------+----------------------+----------+ 2340 | company1-my.sharepoint.com | /ScriptResource... | 102,774 | 2341 +---------------------------------+----------------------+----------+ 2342 | company1-my.sharepoint.com | /ScriptResource... | 40,329 | 2343 +---------------------------------+----------------------+----------+ 2344 | company1-my.sharepoint.com | /WebResource... | 23,063 | 2345 +---------------------------------+----------------------+----------+ 2346 | word-edit.officeapps.live.com | /we/wordeditorframe. | 60,657 | 2347 | | aspx... | | 2348 +---------------------------------+----------------------+----------+ 2349 | static.sharepointonline.com | /bld/_layouts/.../ | 454 | 2350 | | blank.js | | 2351 +---------------------------------+----------------------+----------+ 2352 | s1-word-edit-15.cdn.office.net | /we/s/.../ | 19,201 | 2353 | | EditSurface.css | | 2354 +---------------------------------+----------------------+----------+ 2355 | s1-word-edit-15.cdn.office.net | /we/s/.../ | 221,397 | 2356 | | WordEditor.css | | 2357 +---------------------------------+----------------------+----------+ 2358 | s1-officeapps-15.cdn.office.net | /we/s/.../ | 107,571 | 2359 | | Microsoft | | 2360 | | Ajax.js | | 2361 +---------------------------------+----------------------+----------+ 2362 | s1-word-edit-15.cdn.office.net | /we/s/.../ | 39,981 | 2363 | | wacbootwe.js | | 2364 +---------------------------------+----------------------+----------+ 2365 | s1-officeapps-15.cdn.office.net | /we/s/.../ | 51,749 | 2366 | | CommonIntl.js | | 2367 +---------------------------------+----------------------+----------+ 2368 | s1-word-edit-15.cdn.office.net | /we/s/.../ | 6,050 | 2369 | | Compat.js | | 2370 +---------------------------------+----------------------+----------+ 2371 | s1-word-edit-15.cdn.office.net | /we/s/.../ | 54,158 | 2372 | | Box4Intl.js | | 2373 +---------------------------------+----------------------+----------+ 2374 | s1-word-edit-15.cdn.office.net | /we/s/.../ | 24,946 | 2375 | | WoncaIntl.js | | 2376 +---------------------------------+----------------------+----------+ 2377 | s1-word-edit-15.cdn.office.net | /we/s/.../ | 53,515 | 2378 | | WordEditorIntl.js | | 2379 +---------------------------------+----------------------+----------+ 2380 | s1-word-edit-15.cdn.office.net | /we/s/.../ | 1,978,712| 2381 | | WordEditorExp.js | | 2382 +---------------------------------+----------------------+----------+ 2383 | s1-word-edit-15.cdn.office.net | /we/s/.../jSanity.js | 10,912 | 2384 +---------------------------------+----------------------+----------+ 2385 | word-edit.officeapps.live.com | /we/OneNote.ashx | 145,708 | 2386 +---------------------------------+----------------------+----------+ 2388 Table 6: Office365 Word Transactions 2390 For application identification the HTTPS/TLS traffic MUST include 2391 realistic Certificate Subject Common Name (CN) data as well as Server 2392 Name Indications (SNI). For example, a DUT MAY detect Facebook Chat 2393 traffic by inspecting the certificate and detecting *.facebook.com in 2394 the certificate subject CN and subsequently detect the word chat in 2395 the FQDN 5-edge-chat.facebook.com and identify traffic on the 2396 connection to be Facebook Chat. 2398 Table 7 includes further examples in SNI and CN pairs for several 2399 FQDNs of Office 365. 2401 +------------------------------+----------------------------------+ 2402 |Server Name Indication (SNI) | Certificate Subject | 2403 | | Common Name (CN) | 2404 +=================================================================+ 2405 | r1.res.office365.com | *.res.outlook.com | 2406 +------------------------------+----------------------------------+ 2407 | login.windows.net | graph.windows.net | 2408 +------------------------------+----------------------------------+ 2409 | webdir0a.online.lync.com | *.online.lync.com | 2410 +------------------------------+----------------------------------+ 2411 | login.microsoftonline.com | stamp2.login.microsoftonline.com | 2412 +------------------------------+----------------------------------+ 2413 | webdir.online.lync.com | *.online.lync.com | 2414 +------------------------------+----------------------------------+ 2415 | graph.microsoft.com | graph.microsoft.com | 2416 +------------------------------+----------------------------------+ 2417 | outlook.office365.com | outlook.com | 2418 +------------------------------+----------------------------------+ 2419 | appsforoffice.microsoft.com | appsforoffice.microsoft.com | 2420 +------------------------------+----------------------------------+ 2422 Table 7: Office365 SNI and CN Pairs Examples 2424 NetSecOPEN has provided a reference enterprise perimeter traffic mix 2425 with dozens of applications, hundreds of connections, and thousands 2426 of transactions. 2428 The enterprise perimeter traffic mix consists of 70% HTTPS and 30% 2429 HTTP by Bytes, 58% HTTPS and 42% HTTP by Transactions. By 2430 connections with a single connection per FQDN the mix consists of 43% 2431 HTTPS and 57% HTTP. With multiple connections per FQDN the HTTPS 2432 percentage is higher. 2434 Table 8 is a summary of the NetSecOPEN enterprise perimeter traffic 2435 mix sorted by bytes with unique FQDNs and transactions per 2436 applications. 2438 +------------------+-------+--------------+-------------+ 2439 | Application | FQDNs | Transactions | Bytes | 2440 +=======================================================+ 2441 | Office365 | 26 | 558 | 52,931,947 | 2442 +------------------+-------+--------------+-------------+ 2443 | Box | 4 | 90 | 23,276,089 | 2444 +------------------+-------+--------------+-------------+ 2445 | Salesforce | 6 | 365 | 23,137,548 | 2446 +------------------+-------+--------------+-------------+ 2447 | Gmail | 13 | 139 | 16,399,289 | 2448 +------------------+-------+--------------+-------------+ 2449 | Linkedin | 10 | 206 | 15,040,918 | 2450 +------------------+-------+--------------+-------------+ 2451 | DailyMotion | 8 | 77 | 14,751,514 | 2452 +------------------+-------+--------------+-------------+ 2453 | GoogleDocs | 2 | 71 | 14,205,476 | 2454 +------------------+-------+--------------+-------------+ 2455 | Wikia | 15 | 159 | 13,909,777 | 2456 +------------------+-------+--------------+-------------+ 2457 | Foxnews | 82 | 499 | 13,758,899 | 2458 +------------------+-------+--------------+-------------+ 2459 | Yahoo Finance | 33 | 254 | 13,134,011 | 2460 +------------------+-------+--------------+-------------+ 2461 | Youtube | 8 | 97 | 13,056,216 | 2462 +------------------+-------+--------------+-------------+ 2463 | Facebook | 4 | 207 | 12,726,231 | 2464 +------------------+-------+--------------+-------------+ 2465 | CNBC | 77 | 275 | 11,939,566 | 2466 +------------------+-------+--------------+-------------+ 2467 | Lightreading | 27 | 304 | 11,200,864 | 2468 +------------------+-------+--------------+-------------+ 2469 | BusinessInsider | 16 | 142 | 11,001,575 | 2470 +------------------+-------+--------------+-------------+ 2471 | Alexa | 5 | 153 | 10,475,151 | 2472 +------------------+-------+--------------+-------------+ 2473 | CNN | 41 | 206 | 10,423,740 | 2474 +------------------+-------+--------------+-------------+ 2475 | Twitter Video | 2 | 72 | 10,112,820 | 2476 +------------------+-------+--------------+-------------+ 2477 | Cisco Webex | 1 | 213 | 9,988,417 | 2478 +------------------+-------+--------------+-------------+ 2479 | Slack | 3 | 40 | 9,938,686 | 2480 +------------------+-------+--------------+-------------+ 2481 | Google Maps | 5 | 191 | 8,771,873 | 2482 +------------------+-------+--------------+-------------+ 2483 | SpectrumIEEE | 7 | 145 | 8,682,629 | 2484 +------------------+-------+--------------+-------------+ 2485 | Yelp | 9 | 146 | 8,607,645 | 2486 +------------------+-------+--------------+-------------+ 2487 | Vimeo | 12 | 74 | 8,555,960 | 2488 +------------------+-------+--------------+-------------+ 2489 | Wikihow | 11 | 140 | 8,042,314 | 2490 +------------------+-------+--------------+-------------+ 2491 | Netflix | 3 | 31 | 7,839,256 | 2492 +------------------+-------+--------------+-------------+ 2493 | Instagram | 3 | 114 | 7,230,883 | 2494 +------------------+-------+--------------+-------------+ 2495 | Morningstar | 30 | 150 | 7,220,121 | 2496 +------------------+-------+--------------+-------------+ 2497 | Docusign | 5 | 68 | 6,972,738 | 2498 +------------------+-------+--------------+-------------+ 2499 | Twitter | 1 | 100 | 6,939,150 | 2500 +------------------+-------+--------------+-------------+ 2501 | Tumblr | 11 | 70 | 6,877,200 | 2502 +------------------+-------+--------------+-------------+ 2503 | Whatsapp | 3 | 46 | 6,829,848 | 2504 +------------------+-------+--------------+-------------+ 2505 | Imdb | 16 | 251 | 6,505,227 | 2506 +------------------+-------+--------------+-------------+ 2507 | NOAAgov | 1 | 44 | 6,316,283 | 2508 +------------------+-------+--------------+-------------+ 2509 | IndustryWeek | 23 | 192 | 6,242,403 | 2510 +------------------+-------+--------------+-------------+ 2511 | Spotify | 18 | 119 | 6,231,013 | 2512 +------------------+-------+--------------+-------------+ 2513 | AutoNews | 16 | 165 | 6,115,354 | 2514 +------------------+-------+--------------+-------------+ 2515 | Evernote | 3 | 47 | 6,063,168 | 2516 +------------------+-------+--------------+-------------+ 2517 | NatGeo | 34 | 104 | 6,026,344 | 2518 +------------------+-------+--------------+-------------+ 2519 | BBC News | 18 | 156 | 5,898,572 | 2520 +------------------+-------+--------------+-------------+ 2521 | Investopedia | 38 | 241 | 5,792,038 | 2522 +------------------+-------+--------------+-------------+ 2523 | Pinterest | 8 | 102 | 5,658,994 | 2524 +------------------+-------+--------------+-------------+ 2525 | Succesfactors | 2 | 112 | 5,049,001 | 2526 +------------------+-------+--------------+-------------+ 2527 | AbaJournal | 6 | 93 | 4,985,626 | 2528 +------------------+-------+--------------+-------------+ 2529 | Pbworks | 4 | 78 | 4,670,980 | 2530 +------------------+-------+--------------+-------------+ 2531 | NetworkWorld | 42 | 153 | 4,651,354 | 2532 +------------------+-------+--------------+-------------+ 2533 | WebMD | 24 | 280 | 4,416,736 | 2534 +------------------+-------+--------------+-------------+ 2535 | OilGasJournal | 14 | 105 | 4,095,255 | 2536 +------------------+-------+--------------+-------------+ 2537 | Trello | 5 | 39 | 4,080,182 | 2538 +------------------+-------+--------------+-------------+ 2539 | BusinessWire | 5 | 109 | 4,055,331 | 2540 +------------------+-------+--------------+-------------+ 2541 | Dropbox | 5 | 17 | 4,023,469 | 2542 +------------------+-------+--------------+-------------+ 2543 | Nejm | 20 | 190 | 4,003,657 | 2544 +------------------+-------+--------------+-------------+ 2545 | OilGasDaily | 7 | 199 | 3,970,498 | 2546 +------------------+-------+--------------+-------------+ 2547 | Chase | 6 | 52 | 3,719,232 | 2548 +------------------+-------+--------------+-------------+ 2549 | MedicalNews | 6 | 117 | 3,634,187 | 2550 +------------------+-------+--------------+-------------+ 2551 | Marketwatch | 25 | 142 | 3,291,226 | 2552 +------------------+-------+--------------+-------------+ 2553 | Imgur | 5 | 48 | 3,189,919 | 2554 +------------------+-------+--------------+-------------+ 2555 | NPR | 9 | 83 | 3,184,303 | 2556 +------------------+-------+--------------+-------------+ 2557 | Onelogin | 2 | 31 | 3,132,707 | 2558 +------------------+-------+--------------+-------------+ 2559 | Concur | 2 | 50 | 3,066,326 | 2560 +------------------+-------+--------------+-------------+ 2561 | Service-now | 1 | 37 | 2,985,329 | 2562 +------------------+-------+--------------+-------------+ 2563 | Apple itunes | 14 | 80 | 2,843,744 | 2564 +------------------+-------+--------------+-------------+ 2565 | BerkeleyEdu | 3 | 69 | 2,622,009 | 2566 +------------------+-------+--------------+-------------+ 2567 | MSN | 39 | 203 | 2,532,972 | 2568 +------------------+-------+--------------+-------------+ 2569 | Indeed | 3 | 47 | 2,325,197 | 2570 +------------------+-------+--------------+-------------+ 2571 | MayoClinic | 6 | 56 | 2,269,085 | 2572 +------------------+-------+--------------+-------------+ 2573 | Ebay | 9 | 164 | 2,219,223 | 2574 +------------------+-------+--------------+-------------+ 2575 | UCLAedu | 3 | 42 | 1,991,311 | 2576 +------------------+-------+--------------+-------------+ 2577 | ConstructionDive | 5 | 125 | 1,828,428 | 2578 +------------------+-------+--------------+-------------+ 2579 | EducationNews | 4 | 78 | 1,605,427 | 2580 +------------------+-------+--------------+-------------+ 2581 | BofA | 12 | 68 | 1,584,851 | 2582 +------------------+-------+--------------+-------------+ 2583 | ScienceDirect | 7 | 26 | 1,463,951 | 2584 +------------------+-------+--------------+-------------+ 2585 | Reddit | 8 | 55 | 1,441,909 | 2586 +------------------+-------+--------------+-------------+ 2587 | FoodBusinessNews | 5 | 49 | 1,378,298 | 2588 +------------------+-------+--------------+-------------+ 2589 | Amex | 8 | 42 | 1,270,696 | 2590 +------------------+-------+--------------+-------------+ 2591 | Weather | 4 | 50 | 1,243,826 | 2592 +------------------+-------+--------------+-------------+ 2593 | Wikipedia | 3 | 27 | 958,935 | 2594 +------------------+-------+--------------+-------------+ 2595 | Bing | 1 | 52 | 697,514 | 2596 +------------------+-------+--------------+-------------+ 2597 | ADP | 1 | 30 | 508,654 | 2598 +------------------+-------+--------------+-------------+ 2599 | | | | | 2600 +------------------+-------+--------------+-------------+ 2601 | Grand Total | 983 | 10021 | 569,819,095 | 2602 +------------------+-------+--------------+-------------+ 2604 Table 8: Summary of NetSecOPEN Enterprise Perimeter Traffic Mix 2606 Authors' Addresses 2608 Balamuhunthan Balarajah 2610 Email: bm.balarajah@gmail.com 2612 Carsten Rossenhoevel 2613 EANTC AG 2614 Salzufer 14 2615 Berlin 10587 2616 Germany 2618 Email: cross@eantc.de 2620 Brian Monkman 2621 NetSecOPEN 2623 Email: bmonkman@netsecopen.org