draft-ietf-bmwg-sdn-controller-benchmark-meth-00.txt   draft-ietf-bmwg-sdn-controller-benchmark-meth-01.txt 
Internet-Draft Bhuvaneswaran Vengainathan Internet-Draft Bhuvaneswaran Vengainathan
Network Working Group Anton Basil Network Working Group Anton Basil
Intended Status: Informational Veryx Technologies Intended Status: Informational Veryx Technologies
Expires: April 18, 2016 Mark Tassinari Expires: September 19, 2016 Mark Tassinari
Hewlett-Packard Hewlett-Packard
Vishwas Manral Vishwas Manral
Ionos Corp Nano Sec
Sarah Banks Sarah Banks
VSS Monitoring VSS Monitoring
October 19, 2015 March 21, 2016
Benchmarking Methodology for SDN Controller Performance Benchmarking Methodology for SDN Controller Performance
draft-ietf-bmwg-sdn-controller-benchmark-meth-00 draft-ietf-bmwg-sdn-controller-benchmark-meth-01
Abstract Abstract
This document defines the methodologies for benchmarking performance This document defines the methodologies for benchmarking control
of SDN controllers. Terminology related to benchmarking SDN plane performance of SDN controllers. Terminology related to
controllers is described in the companion terminology document. SDN benchmarking SDN controllers is described in the companion
controllers have been implemented with many varying designs in order terminology document. SDN controllers have been implemented with
to achieve their intended network functionality. Hence, the authors many varying designs in order to achieve their intended network
have taken the approach of considering an SDN controller as a black functionality. Hence, the authors have taken the approach of
box, defining the methodology in a manner that is agnostic to considering an SDN controller as a black box, defining the
protocols and network services supported by controllers. The intent methodology in a manner that is agnostic to protocols and network
of this document is to provide a standard mechanism to measure the services supported by controllers. The intent of this document is to
performance of all controller implementations. provide a standard mechanism to measure the performance of all
controller implementations.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current. Drafts is at http://datatracker.ietf.org/drafts/current.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress. material or to cite them other than as "work in progress.
This Internet-Draft will expire on April 18, 2016. This Internet-Draft will expire on September 19, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction ................................................ 3 1. Introduction...................................................3
2. Scope ....................................................... 4 2. Scope..........................................................4
3. Test Setup .................................................. 4 3. Test Setup.....................................................4
3.1. Test setup - Controller working in Standalone Mode ..... 4 3.1. Test setup - Controller working in Standalone Mode........5
3.2. Test setup - Controller working in Cluster Mode ........ 5 3.2. Test setup - Controller working in Cluster Mode...........6
4. Test Considerations ......................................... 6 4. Test Considerations............................................7
4.1. Network Topology ....................................... 6 4.1. Network Topology..........................................7
4.2. Test Traffic ........................................... 7 4.2. Test Traffic..............................................7
4.3. Connection Setup ....................................... 7 4.3. Connection Setup..........................................7
4.4. Measurement Point Specification and Recommendation ..... 7 4.4. Measurement Point Specification and Recommendation........8
4.5. Connectivity Recommendation ............................ 8 4.5. Connectivity Recommendation...............................8
4.6. Test Repeatability ..................................... 8 4.6. Test Repeatability........................................8
5. Benchmarking Tests .......................................... 9 5. Benchmarking Tests.............................................9
5.1. Performance ............................................ 9 5.1. Performance...............................................9
5.1.1. Network Topology Discovery Time ................... 9 5.1.1. Network Topology Discovery Time......................9
5.1.2. Asynchronous Message Processing Time ............. 10 5.1.2. Asynchronous Message Processing Time................11
5.1.3. Asynchronous Message Processing Rate ............. 11 5.1.3. Asynchronous Message Processing Rate................12
5.1.4. Reactive Path Provisioning Time .................. 13 5.1.4. Reactive Path Provisioning Time.....................14
5.1.5. Proactive Path Provisioning Time ................. 14 5.1.5. Proactive Path Provisioning Time....................15
5.1.6. Reactive Path Provisioning Rate .................. 16 5.1.6. Reactive Path Provisioning Rate.....................16
5.1.7. Proactive Path Provisioning Rate ................. 17 5.1.7. Proactive Path Provisioning Rate....................18
5.1.8. Network Topology Change Detection Time ........... 18 5.1.8. Network Topology Change Detection Time..............19
5.2. 6.2 Scalability........................................ 20 5.2. 6.2 Scalability..........................................20
5.2.1. Control Session Capacity ......................... 20 5.2.1. Control Session Capacity............................20
5.2.2. Network Discovery Size ........................... 20 5.2.2. Network Discovery Size..............................21
5.2.3. 6.2.3 Forwarding Table Capacity .................. 21 5.2.3. 6.2.3 Forwarding Table Capacity.....................22
5.3. 6.3 Security .......................................... 23 5.3. 6.3 Security.............................................23
5.3.1. 6.3.1 Exception Handling ......................... 23 5.3.1. 6.3.1 Exception Handling............................23
5.3.2. Denial of Service Handling ....................... 24 5.3.2. Denial of Service Handling..........................25
5.4. Reliability ........................................... 26 5.4. Reliability..............................................26
5.4.1. Controller Failover Time ......................... 26 5.4.1. Controller Failover Time............................26
5.4.2. Network Re-Provisioning Time ..................... 27 5.4.2. Network Re-Provisioning Time........................27
6. References ................................................. 29 6. References....................................................29
6.1. Normative References .................................. 29 6.1. Normative References.....................................29
6.2. Informative References ................................ 29 6.2. Informative References...................................30
7. IANA Considerations ........................................ 30 7. IANA Considerations...........................................30
8. Security Considerations .................................... 30 8. Security Considerations.......................................30
9. Acknowledgments ............................................ 30 9. Acknowledgments...............................................30
Appendix A. Example Test Topologies ........................... 31 Appendix A. Example Test Topologies..............................31
A.1. Leaf-Spine Topology - Three Tier Network Architecture . 31 A.1. Leaf-Spine Topology - Three Tier Network Architecture....31
A.2. Leaf-Spine Topology - Two Tier Network Architecture ... 31 A.2. Leaf-Spine Topology - Two Tier Network Architecture......31
Appendix B. Benchmarking Methodology using OpenFlow Controllers 32 Appendix B. Benchmarking Methodology using OpenFlow Controllers..32
B.1. Protocol Overview ..................................... 32 B.1. Protocol Overview........................................32
B.2. Messages Overview ..................................... 32 B.2. Messages Overview........................................32
B.3. Connection Overview ................................... 32 B.3. Connection Overview......................................32
B.4. Performance Benchmarking Tests ........................ 33 B.4. Performance Benchmarking Tests...........................33
B.4.1. Network Topology Discovery Time .................. 33 B.4.1. Network Topology Discovery Time.....................33
B.4.2. Asynchronous Message Processing Time ............. 34 B.4.2. Asynchronous Message Processing Time................34
B.4.3. Asynchronous Message Processing Rate ............. 35 B.4.3. Asynchronous Message Processing Rate................35
B.4.4. Reactive Path Provisioning Time .................. 36 B.4.4. Reactive Path Provisioning Time.....................36
B.4.5. Proactive Path Provisioning Time ................. 37 B.4.5. Proactive Path Provisioning Time....................37
B.4.6. Reactive Path Provisioning Rate .................. 38 B.4.6. Reactive Path Provisioning Rate.....................38
B.4.7. Proactive Path Provisioning Rate ................. 39 B.4.7. Proactive Path Provisioning Rate....................39
B.4.8. Network Topology Change Detection Time ........... 40 B.4.8. Network Topology Change Detection Time..............40
B.5. Scalability ........................................... 41 B.5. Scalability..............................................41
B.5.1. Control Sessions Capacity ........................ 41 B.5.1. Control Sessions Capacity...........................41
B.5.2. Network Discovery Size ........................... 41 B.5.2. Network Discovery Size..............................41
B.5.3. Forwarding Table Capacity ........................ 42 B.5.3. Forwarding Table Capacity...........................42
B.6. Security .............................................. 44 B.6. Security.................................................44
B.6.1. Exception Handling ............................... 44 B.6.1. Exception Handling..................................44
B.6.2. Denial of Service Handling ....................... 45 B.6.2. Denial of Service Handling..........................45
B.7. Reliability ........................................... 47 B.7. Reliability..............................................47
B.7.1. Controller Failover Time ......................... 47 B.7.1. Controller Failover Time............................47
B.7.2. Network Re-Provisioning Time ..................... 48 B.7.2. Network Re-Provisioning Time........................48
Authors' Addresses ............................................ 51 Authors' Addresses...............................................51
1. Introduction 1. Introduction
This document provides generic methodologies for benchmarking SDN This document provides generic methodologies for benchmarking SDN
controller performance. An SDN controller may support many controller performance. An SDN controller may support many
northbound and southbound protocols, implement a wide range of northbound and southbound protocols, implement a wide range of
applications, and work solely, or as a group to achieve the desired applications, and work solely, or as a group to achieve the desired
functionality. This document considers an SDN controller as a black functionality. This document considers an SDN controller as a black
box, regardless of design and implementation. The tests defined in box, regardless of design and implementation. The tests defined in
the document can be used to benchmark SDN controller for the document can be used to benchmark SDN controller for
skipping to change at page 4, line 20 skipping to change at page 4, line 20
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. document are to be interpreted as described in RFC 2119.
2. Scope 2. Scope
This document defines methodology to measure the networking metrics This document defines methodology to measure the networking metrics
of SDN controllers. For the purpose of this memo, the SDN controller of SDN controllers. For the purpose of this memo, the SDN controller
is a function that manages and controls SDN nodes. Any SDN controller is a function that manages and controls Network Devices. Any SDN
without a control capability is out of scope for this memo. The controller without a control capability is out of scope for this
tests defined in this document enable benchmarking of SDN memo. The tests defined in this document enable benchmarking of SDN
Controllers in two ways; as a standalone controller and as a cluster Controllers in two ways; as a standalone controller and as a cluster
of homogeneous controllers. These tests are recommended for of homogeneous controllers. These tests are recommended for
execution in lab environments rather than in live network execution in lab environments rather than in live network
deployments. Performance benchmarking of a federation of controllers deployments. Performance benchmarking of a federation of controllers
is beyond the scope of this document. is beyond the scope of this document.
3. Test Setup 3. Test Setup
The tests defined in this document enable measurement of an SDN The tests defined in this document enable measurement of an SDN
controllers performance in standalone mode and cluster mode. This controllers performance in standalone mode and cluster mode. This
section defines common reference topologies that are later referred section defines common reference topologies that are later referred
to in individual tests. to in individual tests.
3.1. Test setup - Controller working in Standalone Mode 3.1. Test setup - Controller working in Standalone Mode
+-----------------------------------------------------------+ +-----------------------------------------------------------+
| Management Plane Test Emulator | | Application Plane Test Emulator |
| | | |
| -------------------- | | +-----------------+ +-------------+ |
| | SDN Applications | | | | Application | | Service | |
| -------------------- | | +-----------------+ +-------------+ |
| | | |
+-----------------------------+(I2)-------------------------+ +-----------------------------+(I2)-------------------------+
| |
| |
| (Northbound interface) | (Northbound interface)
+-------------------------------+ +-------------------------------+
| +----------------+ | | +----------------+ |
| | SDN Controller | | | | SDN Controller | |
| +----------------+ | | +----------------+ |
| | | |
| Device Under Test (DUT) | | Device Under Test (DUT) |
+-------------------------------+ +-------------------------------+
| (Southbound interface) | (Southbound interface)
| |
| |
+-----------------------------+(I1)-------------------------+ +-----------------------------+(I1)-------------------------+
| | | |
| +---------+ +---------+ | | +-----------+ +-----------+ |
| | SDN |l1 ln-1| SDN | | | | Network |l1 ln-1| Network | |
| | Node 1 |----- .... -----| Node n | | | | Device 1 |---- .... ----| Device n | |
| +---------+ +---------+ | | +-----------+ +-----------+ |
| |l0 |ln | | |l0 |ln |
| | | | | | | |
| | | | | | | |
| +---------------+ +---------------+ | | +---------------+ +---------------+ |
| | Test Traffic | | Test Traffic | | | | Test Traffic | | Test Traffic | |
| | Generator | | Generator | | | | Generator | | Generator | |
| | (TP1) | | (TP2) | | | | (TP1) | | (TP2) | |
| +---------------+ +---------------+ | | +---------------+ +---------------+ |
| | | |
| Forwarding Plane Test Emulator | | Forwarding Plane Test Emulator |
+-----------------------------------------------------------+ +-----------------------------------------------------------+
Figure 1 Figure 1
3.2. Test setup - Controller working in Cluster Mode 3.2. Test setup - Controller working in Cluster Mode
+-----------------------------------------------------------+ +-----------------------------------------------------------+
| Management Plane Test Emulator | | Application Plane Test Emulator |
| | | |
| -------------------- | | +-----------------+ +-------------+ |
| | SDN Applications | | | | Application | | Service | |
| -------------------- | | +-----------------+ +-------------+ |
| | | |
+-----------------------------+(I2)-------------------------+ +-----------------------------+(I2)-------------------------+
| |
| |
| (Northbound interface) | (Northbound interface)
+---------------------------------------------------------+ +---------------------------------------------------------+
| | | |
| ------------------ ------------------ | | ------------------ ------------------ |
| | SDN Controller 1 | <--E/W--> | SDN Controller n | | | | SDN Controller 1 | <--E/W--> | SDN Controller n | |
| ------------------ ------------------ | | ------------------ ------------------ |
| | | |
| Device Under Test (DUT) | | Device Under Test (DUT) |
+---------------------------------------------------------+ +---------------------------------------------------------+
| (Southbound interface) | (Southbound interface)
| |
| |
+-----------------------------+(I1)-------------------------+ +-----------------------------+(I1)-------------------------+
| | | |
| +---------+ +---------+ | | +-----------+ +-----------+ |
| | SDN |l1 ln-1| SDN | | | | Network |l1 ln-1| Network | |
| | Node 1 |----- .... -----| Node n | | | | Device 1 |---- .... ----| Device n | |
| +---------+ +---------+ | | +-----------+ +-----------+ |
| |l0 |ln | | |l0 |ln |
| | | | | | | |
| | | | | | | |
| +---------------+ +---------------+ | | +---------------+ +---------------+ |
| | Test Traffic | | Test Traffic | | | | Test Traffic | | Test Traffic | |
| | Generator | | Generator | | | | Generator | | Generator | |
| | (TP1) | | (TP2) | | | | (TP1) | | (TP2) | |
| +---------------+ +---------------+ | | +---------------+ +---------------+ |
| | | |
| Forwarding Plane Test Emulator | | Forwarding Plane Test Emulator |
+-----------------------------------------------------------+ +-----------------------------------------------------------+
Figure 2 Figure 2
4. Test Considerations 4. Test Considerations
4.1. Network Topology 4.1. Network Topology
The test cases SHOULD use Leaf-Spine topology with at least 1 SDN The test cases SHOULD use Leaf-Spine topology with at least 1
node in the topology for benchmarking. The test traffic generators Network Device in the topology for benchmarking. The test traffic
TP1 and TP2 SHOULD be connected to the first and the last SDN leaf generators TP1 and TP2 SHOULD be connected to the first and the last
node. If a test case uses test topology with 1 SDN node, the test leaf Network Device. If a test case uses test topology with 1
traffic generators TP1 and TP2 SHOULD be connected to the same node. Network Device, the test traffic generators TP1 and TP2 SHOULD be
However to achieve a complete performance characterization of the connected to the same node. However to achieve a complete
SDN controller, it is recommended that the controller be benchmarked performance characterization of the SDN controller, it is
for many network topologies and a varying number of SDN nodes. This recommended that the controller be benchmarked for many network
document includes a few sample test topologies, defined in Section topologies and a varying number of Network Devices. This document
10 - Appendix A for reference. Further, care should be taken to make includes a few sample test topologies, defined in Section 10 -
sure that a loop prevention mechanism is enabled either in the SDN Appendix A for reference. Further, care should be taken to make sure
that a loop prevention mechanism is enabled either in the SDN
controller, or in the network when the topology contains redundant controller, or in the network when the topology contains redundant
network paths. network paths.
4.2. Test Traffic 4.2. Test Traffic
Test traffic is used to notify the controller about the arrival of Test traffic is used to notify the controller about the arrival of
new flows. The test cases SHOULD use multiple frame sizes as new flows. The test cases SHOULD use multiple frame sizes as
recommended in RFC2544 for benchmarking. recommended in RFC2544 for benchmarking.
4.3. Connection Setup 4.3. Test Emulator Requirements
The Test Emulator SHOULD time stamp the transmitted and received
control messages to/from the controller on the established network
connections. The test cases use these values to compute the
controller processing time.
4.4. Connection Setup
There may be controller implementations that support unencrypted and There may be controller implementations that support unencrypted and
encrypted network connections with SDN nodes. Further, the encrypted network connections with Network Devices. Further, the
controller may have backward compatibility with SDN nodes running controller may have backward compatibility with Network Devices
older versions of southbound protocols. It is recommended that the running older versions of southbound protocols. It is recommended
controller performance be measured with one or more applicable that the controller performance be measured with one or more
connection setup methods defined below. applicable connection setup methods defined below.
1. Unencrypted connection with SDN nodes, running same protocol 1. Unencrypted connection with Network Devices, running same
version. protocol version.
2. Unencrypted connection with SDN nodes, running different 2. Unencrypted connection with Network Devices, running different
protocol versions. protocol versions.
Example: Example:
a. Controller running current protocol version and switch
a. Controller running current protocol version and switch
running older protocol version running older protocol version
b. Controller running older protocol version and switch b. Controller running older protocol version and switch
running current protocol version running current protocol version
3. Encrypted connection with SDN nodes, running same protocol 3. Encrypted connection with Network Devices, running same
version protocol version
4. Encrypted connection with SDN nodes, running different protocol 4. Encrypted connection with Network Devices, running different
versions. protocol versions.
Example: Example:
a. Controller running current protocol version and switch a. Controller running current protocol version and switch
running older protocol version running older protocol version
b. Controller running older protocol version and switch b. Controller running older protocol version and switch
running current protocol version running current protocol version
4.4. Measurement Point Specification and Recommendation 4.5. Measurement Point Specification and Recommendation
The measurement accuracy depends on several factors including the The measurement accuracy depends on several factors including the
point of observation where the indications are captured. For point of observation where the indications are captured. For
example, the notification can be observed at the controller or test example, the notification can be observed at the controller or test
emulator. The test operator SHOULD make the observations/ emulator. The test operator SHOULD make the observations/
measurements at the interfaces of test emulator unless it is measurements at the interfaces of test emulator unless it is
explicitly mentioned otherwise in the individual test. explicitly mentioned otherwise in the individual test.
4.5. Connectivity Recommendation 4.6. Connectivity Recommendation
The SDN controller in the test setup SHOULD be connected directly The SDN controller in the test setup SHOULD be connected directly
with the forwarding and the management plane test emulators to avoid with the forwarding and the management plane test emulators to avoid
any delays or failure introduced by the intermediate devices during any delays or failure introduced by the intermediate devices during
benchmarking tests. benchmarking tests.
4.6. Test Repeatability 4.7. Test Repeatability
To increase the confidence in measured result, it is recommended To increase the confidence in measured result, it is recommended
that each test SHOULD be repeated a minimum of 10 times. that each test SHOULD be repeated a minimum of 10 times.
Test Reporting Test Reporting
Each test has a reporting format that contains some global and Each test has a reporting format that contains some global and
identical reporting components, and some individual components that identical reporting components, and some individual components that
are specific to individual tests. The following test configuration are specific to individual tests. The following test configuration
parameters and controller settings parameters MUST be reflected in parameters and controller settings parameters MUST be reflected in
the test report. the test report.
Test Configuration Parameters: Test Configuration Parameters:
1. Controller name and version 1. Controller name and version
2. Northbound protocols and versions 2. Northbound protocols and versions
3. Southbound protocols and versions 3. Southbound protocols and versions
4. Controller redundancy mode (Standalone or Cluster Mode) 4. Controller redundancy mode (Standalone or Cluster Mode)
5. Connection setup (Unencrypted or Encrypted) 5. Connection setup (Unencrypted or Encrypted)
6. Network Topology (Mesh or Tree or Linear) 6. Network Topology (Mesh or Tree or Linear)
7. SDN Node Type (Physical or Virtual or Emulated) 7. Network Device Type (Physical or Virtual or Emulated)
8. Number of Nodes 8. Number of Nodes
9. Number of Links 9. Number of Links
10. Test Traffic Type 10. Test Traffic Type
11. Controller System Configuration (e.g., CPU, Memory, Operating 11. Controller System Configuration (e.g., CPU, Memory, Operating
System, Interface Speed etc.,) System, Interface Speed etc.,)
12. Reference Test Setup (e.g., Section 3.1 etc.,) 12. Reference Test Setup (e.g., Section 3.1 etc.,)
Controller Settings Parameters: Controller Settings Parameters:
1. Topology re-discovery timeout 1. Topology re-discovery timeout
2. Controller redundancy mode (e.g., active-standby etc.,) 2. Controller redundancy mode (e.g., active-standby etc.,)
To ensure the repeatability of test, the following capabilities of
test emulator SHOULD be reported
1. Maximum number of Network Devices that the forwarding plane
emulates
2. Control message processing time (e.g., Topology Discovery
Messages)
One way to determine the above two values are to simulate the
required control sessions and messages from the control plane.
5. Benchmarking Tests 5. Benchmarking Tests
5.1. Performance 5.1. Performance
5.1.1. Network Topology Discovery Time 5.1.1. Network Topology Discovery Time
Objective: Objective:
Measure the time taken by the SDN controller to discover the network Measure the time taken by the SDN controller to discover the network
skipping to change at page 9, line 24 skipping to change at page 10, line 4
topology (nodes and links), expressed in milliseconds. topology (nodes and links), expressed in milliseconds.
Reference Test Setup: Reference Test Setup:
The test SHOULD use one of the test setups described in section 3.1 The test SHOULD use one of the test setups described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. The controller MUST support network discovery. 1. The controller MUST support network discovery.
2. Tester should be able to retrieve the discovered topology 2. Tester should be able to retrieve the discovered topology
information either through the controller's management interface, information either through the controller's management interface,
or northbound interface to determine if the discovery was or northbound interface to determine if the discovery was
successful and complete. successful and complete.
3. Ensure that the controller's topology re-discovery timeout has 3. Ensure that the controller's topology re-discovery timeout has
been set to the maximum value to avoid initiation of re-discovery been set to the maximum value to avoid initiation of re-discovery
process in the middle of the test. process in the middle of the test.
Procedure: Procedure:
1. Ensure that the controller is operational, its network 1. Ensure that the controller is operational, its network
applications, northbound and southbound interfaces are up and applications, northbound and southbound interfaces are up and
running. running.
2. Establish the network connections between controller and SDN 2. Establish the network connections between controller and Network
nodes. Devices.
3. Record the time for the first discovery message (Tm1) received 3. Record the time for the first discovery message (Tm1) received
from the controller at forwarding plane test emulator interface from the controller at forwarding plane test emulator interface
I1. I1.
4. Query the controller every 3 seconds to obtain the discovered 4. Query the controller every 3 seconds to obtain the discovered
network topology information through the northbound interface or network topology information through the northbound interface or
the management interface and compare it with the deployed network the management interface and compare it with the deployed network
topology information. topology information.
5. Stop the test when the discovered topology information matches the 5. Stop the test when the discovered topology information matches the
deployed network topology, or when the discovered topology deployed network topology, or when the discovered topology
information for 3 consecutive queries return the same details. information for 3 consecutive queries return the same details.
6. Record the time last discovery message (Tmn) sent to controller 6. Record the time last discovery message (Tmn) sent to controller
from the forwarding plane test emulator interface (I1) when the from the forwarding plane test emulator interface (I1) when the
test completed successfully. (e.g., the topology matches). test completed successfully. (e.g., the topology matches).
Measurement: Measurement:
Topology Discovery Time Tr1 = Tmn-Tm1. Topology Discovery Time Tr1 = Tmn-Tm1.
Tr1 + Tr2 + Tr3 .. Trn Tr1 + Tr2 + Tr3 .. Trn
Average Topology Discovery Time = ----------------------- Average Topology Discovery Time = -----------------------
Total Test Iterations Total Test Iterations
Reporting Format: Reporting Format:
skipping to change at page 10, line 44 skipping to change at page 11, line 25
asynchronous message, expressed in milliseconds. asynchronous message, expressed in milliseconds.
Reference Test Setup: Reference Test Setup:
This test SHOULD use one of the test setup described in section 3.1 This test SHOULD use one of the test setup described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. The controller MUST have completed the network topology discovery 1. The controller MUST have completed the network topology discovery
for the connected SDN nodes. for the connected Network Devices.
Procedure: Procedure:
1. Generate asynchronous messages from every connected SDN node, 1. Generate asynchronous messages from every connected Network
to the SDN controller, one at a time in series from the Device, to the SDN controller, one at a time in series from the
forwarding plane test emulator for the test duration. forwarding plane test emulator for the test duration.
2. Record every request transmit (T1) timestamp and the
2. Record every request transmit (T1) timestamp and the
corresponding response (R1) received timestamp at the corresponding response (R1) received timestamp at the
forwarding plane test emulator interface (I1) for every forwarding plane test emulator interface (I1) for every
successful message exchange. successful message exchange.
Measurement: Measurement:
(R1-T1) + (R2-T2)..(Rn-Tn) (R1-T1) + (R2-T2)..(Rn-Tn)
Asynchronous Message Processing Time Tr1 = ----------------------- Asynchronous Message Processing Time Tr1 = -----------------------
Nrx Nrx
skipping to change at page 12, line 15 skipping to change at page 12, line 43
messages processed per second. messages processed per second.
Reference Test Setup: Reference Test Setup:
The test SHOULD use one of the test setups described in section 3.1 The test SHOULD use one of the test setups described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. The controller MUST have completed the network topology discovery 1. The controller MUST have completed the network topology discovery
for the connected SDN nodes. for the connected Network Devices.
Procedure: Procedure:
1. Generate asynchronous messages continuously at the maximum 1. Generate asynchronous messages continuously at the maximum
possible rate on the established connections from all the possible rate on the established connections from all the
connected SDN nodes in the forwarding plane test emulator for the connected Network Devices in the forwarding plane test emulator
Test Duration (Td). for the Test Duration (Td).
2. Record the total number of responses received from the controller 2. Record the total number of responses received from the controller
(Nrx) as well as the number of messages sent(Ntx) to the (Nrx) as well as the number of messages sent(Ntx) to the
controller within the test duration(Td) at the forwarding plane controller within the test duration(Td) at the forwarding plane
test emulator interface (I1). test emulator interface (I1).
Measurement: Measurement:
Nrx Nrx
Asynchronous Message Processing Rate Tr1 = ----- Asynchronous Message Processing Rate Tr1 = -----
Td Td
Tr1 + Tr2 + Tr3..Trn Tr1 + Tr2 + Tr3..Trn
Average Asynchronous Message Processing Rate= -------------------- Average Asynchronous Message Processing Rate= --------------------
Total Test Iterations Total Test Iterations
skipping to change at page 13, line 32 skipping to change at page 14, line 21
milliseconds. milliseconds.
Reference Test Setup: Reference Test Setup:
The test SHOULD use one of the test setups described in section 3.1 The test SHOULD use one of the test setups described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. The controller MUST contain the network topology information for 1. The controller MUST contain the network topology information for
the deployed network topology. the deployed network topology.
2. The controller should have the knowledge about the location of 2. The controller should have the knowledge about the location of
destination endpoint for which the path has to be provisioned. destination endpoint for which the path has to be provisioned.
This can be achieved through dynamic learning or static This can be achieved through dynamic learning or static
provisioning. provisioning.
3. Ensure that the default action for 'flow miss' in SDN node is 3. Ensure that the default action for 'flow miss' in Network Device
configured to 'send to controller'. is configured to 'send to controller'.
4. Ensure that each SDN node in a path requires the controller to 4. Ensure that each Network Device in a path requires the controller
make the forwarding decision while paving the entire path. to make the forwarding decision while paving the entire path.
Procedure: Procedure:
1. Send a single traffic stream from the test traffic generator TP1 1. Send a single traffic stream from the test traffic generator TP1
to test traffic generator TP2. to test traffic generator TP2.
2. Record the time of the first flow provisioning request message 2. Record the time of the first flow provisioning request message
sent to the controller (Tsf1) from the SDN node at the forwarding sent to the controller (Tsf1) from the Network Device at the
plane test emulator interface (I1). forwarding plane test emulator interface (I1).
3. Wait for the arrival of first traffic frame at the Traffic 3. Wait for the arrival of first traffic frame at the Traffic
Endpoint TP2 or the expiry of test duration (Td). Endpoint TP2 or the expiry of test duration (Td).
4. Record the time of the last flow provisioning response message 4. Record the time of the last flow provisioning response message
received from the controller (Tdf1) to the SDN node at the received from the controller (Tdf1) to the Network Device at the
forwarding plane test emulator interface (I1). forwarding plane test emulator interface (I1).
Measurement: Measurement:
Reactive Path Provisioning Time Tr1 = Tdf1-Tsf1. Reactive Path Provisioning Time Tr1 = Tdf1-Tsf1.
Tr1 + Tr2 + Tr3 .. Trn Tr1 + Tr2 + Tr3 .. Trn
Average Reactive Path Provisioning Time = ----------------------- Average Reactive Path Provisioning Time = -----------------------
Total Test Iterations Total Test Iterations
Reporting Format: Reporting Format:
The Reactive Path Provisioning Time results MUST be reported in the The Reactive Path Provisioning Time results MUST be reported in the
format of a table with a row for each iteration. The last row of the format of a table with a row for each iteration. The last row of the
table indicates the Average Reactive Path Provisioning Time table indicates the Average Reactive Path Provisioning Time
The report should capture the following information in addition to The report should capture the following information in addition to
the configuration parameters captured in section 5. the configuration parameters captured in section 5.
- Number of SDN nodes in the path - Number of Network Devices in the path
5.1.5. Proactive Path Provisioning Time 5.1.5. Proactive Path Provisioning Time
Objective: Objective:
To measure the time taken by the controller to setup a path To measure the time taken by the controller to setup a path
proactively between source and destination node, expressed in proactively between source and destination node, expressed in
milliseconds. milliseconds.
Reference Test Setup: Reference Test Setup:
The test SHOULD use one of the test setups described in section 3.1 The test SHOULD use one of the test setups described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. The controller MUST contain the network topology information for 1. The controller MUST contain the network topology information for
the deployed network topology. the deployed network topology.
2. The controller should have the knowledge about the location of 2. The controller should have the knowledge about the location of
destination endpoint for which the path has to be provisioned. destination endpoint for which the path has to be provisioned.
This can be achieved through dynamic learning or static This can be achieved through dynamic learning or static
provisioning. provisioning.
3. Ensure that the default action for flow miss in SDN node is 3. Ensure that the default action for flow miss in Network Device is
'drop'. 'drop'.
Procedure: Procedure:
1. Send a single traffic stream from test traffic generator TP1 to 1. Send a single traffic stream from test traffic generator TP1 to
TP2. TP2.
2. Install the flow entries to reach from test traffic generator TP1 2. Install the flow entries to reach from test traffic generator TP1
to the test traffic generator TP2 through controller's northbound to the test traffic generator TP2 through controller's northbound
or management interface. or management interface.
3. Wait for the arrival of first traffic frame at the test traffic 3. Wait for the arrival of first traffic frame at the test traffic
generator TP2 or the expiry of test duration (Td). generator TP2 or the expiry of test duration (Td).
4. Record the time when the proactive flow is provisioned in the 4. Record the time when the proactive flow is provisioned in the
Controller (Tsf1) at the management plane test emulator interface Controller (Tsf1) at the management plane test emulator interface
I2. I2.
5. Record the time of the last flow provisioning message received 5. Record the time of the last flow provisioning message received
from the controller (Tdf1) at the forwarding plane test emulator from the controller (Tdf1) at the forwarding plane test emulator
interface I1. interface I1.
Measurement: Measurement:
Proactive Flow Provisioning Time Tr1 = Tdf1-Tsf1. Proactive Flow Provisioning Time Tr1 = Tdf1-Tsf1.
Tr1 + Tr2 + Tr3 .. Trn Tr1 + Tr2 + Tr3 .. Trn
Average Proactive Path Provisioning Time = ----------------------- Average Proactive Path Provisioning Time = -----------------------
Total Test Iterations Total Test Iterations
Reporting Format: Reporting Format:
The Proactive Path Provisioning Time results MUST be reported in the The Proactive Path Provisioning Time results MUST be reported in the
format of a table with a row for each iteration. The last row of the format of a table with a row for each iteration. The last row of the
table indicates the Average Proactive Path Provisioning Time. table indicates the Average Proactive Path Provisioning Time.
The report should capture the following information in addition to The report should capture the following information in addition to
the configuration parameters captured in section 5. the configuration parameters captured in section 5.
- Number of SDN nodes in the path - Number of Network Devices in the path
5.1.6. Reactive Path Provisioning Rate 5.1.6. Reactive Path Provisioning Rate
Objective: Objective:
Measure the maximum number of independent paths a controller can Measure the maximum number of independent paths a controller can
concurrently establish between source and destination nodes concurrently establish between source and destination nodes
reactively within the test duration, expressed in paths per second. reactively within the test duration, expressed in paths per second.
Reference Test Setup: Reference Test Setup:
The test SHOULD use one of the test setups described in section 3.1 The test SHOULD use one of the test setups described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. The controller MUST contain the network topology information for 1. The controller MUST contain the network topology information for
the deployed network topology. the deployed network topology.
2. The controller should have the knowledge about the location of 2. The controller should have the knowledge about the location of
destination addresses for which the paths have to be provisioned. destination addresses for which the paths have to be provisioned.
This can be achieved through dynamic learning or static
provisioning. This can be achieved through dynamic learning or static
3. Ensure that the default action for 'flow miss' in SDN node is provisioning.
configured to 'send to controller'. 3. Ensure that the default action for 'flow miss' in Network Device
4. Ensure that each SDN node in a path requires the controller to is configured to 'send to controller'.
make the forwarding decision while provisioning the entire path. 4. Ensure that each Network Device in a path requires the controller
to make the forwarding decision while provisioning the entire
path.
Procedure: Procedure:
1. Send traffic with unique source and destination addresses from 1. Send traffic with unique source and destination addresses from
test traffic generator TP1. test traffic generator TP1.
2. Record total number of unique traffic frames (Ndf) received at the 2. Record total number of unique traffic frames (Ndf) received at the
test traffic generator TP2 within the test duration (Td). test traffic generator TP2 within the test duration (Td).
Measurement: Measurement:
Ndf Ndf
Reactive Path Provisioning Rate Tr1 = ------ Reactive Path Provisioning Rate Tr1 = ------
Td Td
Tr1 + Tr2 + Tr3 .. Trn Tr1 + Tr2 + Tr3 .. Trn
Average Reactive Path Provisioning Rate = ------------------------ Average Reactive Path Provisioning Rate = ------------------------
Total Test Iterations Total Test Iterations
Reporting Format: Reporting Format:
The Reactive Path Provisioning Rate results MUST be reported in the The Reactive Path Provisioning Rate results MUST be reported in the
format of a table with a row for each iteration. The last row of the format of a table with a row for each iteration. The last row of the
table indicates the Average Reactive Path Provisioning Rate. table indicates the Average Reactive Path Provisioning Rate.
The report should capture the following information in addition to The report should capture the following information in addition to
the configuration parameters captured in section 5. the configuration parameters captured in section 5.
- Number of SDN nodes in the path - Number of Network Devices in the path
- Offered rate - Offered rate
5.1.7. Proactive Path Provisioning Rate 5.1.7. Proactive Path Provisioning Rate
Objective: Objective:
Measure the maximum number of independent paths a controller can Measure the maximum number of independent paths a controller can
concurrently establish between source and destination nodes concurrently establish between source and destination nodes
proactively within the test duration, expressed in paths per second. proactively within the test duration, expressed in paths per second.
skipping to change at page 17, line 41 skipping to change at page 18, line 28
Prerequisite: Prerequisite:
1. The controller MUST contain the network topology information for 1. The controller MUST contain the network topology information for
the deployed network topology. the deployed network topology.
2. The controller should have the knowledge about the location of 2. The controller should have the knowledge about the location of
destination addresses for which the paths have to be provisioned. destination addresses for which the paths have to be provisioned.
This can be achieved through dynamic learning or static This can be achieved through dynamic learning or static
provisioning. provisioning.
3. Ensure that the default action for flow miss in SDN node is 3. Ensure that the default action for flow miss in Network Device is
'drop'. 'drop'.
Procedure: Procedure:
1. Send traffic continuously with unique source and destination 1. Send traffic continuously with unique source and destination
addresses from test traffic generator TP1. addresses from test traffic generator TP1.
2. Install corresponding flow entries to reach from simulated 2. Install corresponding flow entries to reach from simulated
sources at the test traffic generator TP1 to the simulated sources at the test traffic generator TP1 to the simulated
destinations at test traffic generator TP2 through controller's destinations at test traffic generator TP2 through controller's
skipping to change at page 18, line 32 skipping to change at page 19, line 15
Reporting Format: Reporting Format:
The Proactive Path Provisioning Rate results MUST be reported in the The Proactive Path Provisioning Rate results MUST be reported in the
format of a table with a row for each iteration. The last row of the format of a table with a row for each iteration. The last row of the
table indicates the Average Proactive Path Provisioning Rate. table indicates the Average Proactive Path Provisioning Rate.
The report should capture the following information in addition to The report should capture the following information in addition to
the configuration parameters captured in section 5. the configuration parameters captured in section 5.
- Number of SDN nodes in the path - Number of Network Devices in the path
- Offered rate - Offered rate
5.1.8. Network Topology Change Detection Time 5.1.8. Network Topology Change Detection Time
Objective: Objective:
Measure the time taken by the controller to detect any changes in Measure the time taken by the controller to detect any changes in
the network topology, expressed in milliseconds. the network topology, expressed in milliseconds.
skipping to change at page 19, line 15 skipping to change at page 19, line 41
Prerequisite: Prerequisite:
1. The controller MUST have discovered the network topology 1. The controller MUST have discovered the network topology
information for the deployed network topology. information for the deployed network topology.
2. The periodic network discovery operation should be configured to 2. The periodic network discovery operation should be configured to
twice the Test duration (Td) value. twice the Test duration (Td) value.
Procedure: Procedure:
1. Trigger a topology change event by bringing down an active SDN 1. Trigger a topology change event by bringing down an active
node in the topology. Network Device in the topology.
2. Record the time when the first topology change notification is 2. Record the time when the first topology change notification is
sent to the controller (Tcn) at the forwarding plane test emulator sent to the controller (Tcn) at the forwarding plane test emulator
interface (I1). interface (I1).
3. Stop the test when the controller sends the first topology re- 3. Stop the test when the controller sends the first topology re-
discovery message to the SDN node or the expiry of test interval discovery message to the Network Device or the expiry of test
(Td). interval (Td).
4. Record the time when the first topology re-discovery message is 4. Record the time when the first topology re-discovery message is
received from the controller (Tcd) at the forwarding plane test received from the controller (Tcd) at the forwarding plane test
emulator interface (I1) emulator interface (I1)
Measurement: Measurement:
Network Topology Change Detection Time Tr1 = Tcd-Tcn. Network Topology Change Detection Time Tr1 = Tcd-Tcn.
Tr1 + Tr2 + Tr3 .. Trn Tr1 + Tr2 + Tr3 .. Trn
skipping to change at page 20, line 21 skipping to change at page 20, line 43
Measure the maximum number of control sessions that the controller Measure the maximum number of control sessions that the controller
can maintain. can maintain.
Reference Test Setup: Reference Test Setup:
The test SHOULD use one of the test setups described in section 3.1 The test SHOULD use one of the test setups described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Procedure: Procedure:
1. Establish control connection with controller from every SDN node 1. Establish control connection with controller from every Network
emulated in the forwarding plane test emulator. Device emulated in the forwarding plane test emulator.
2. Stop the test when the controller starts dropping the control 2. Stop the test when the controller starts dropping the control
connection. connection.
3. Record the number of successful connections established with the 3. Record the number of successful connections established with the
controller (CCn) at the forwarding plane test emulator. controller (CCn) at the forwarding plane test emulator.
Measurement: Measurement:
Control Sessions Capacity = CCn. Control Sessions Capacity = CCn.
Reporting Format: Reporting Format:
The Control Session Capacity results MUST be reported in addition to The Control Session Capacity results MUST be reported in addition to
the configuration parameters captured in section 5. the configuration parameters captured in section 5.
skipping to change at page 21, line 9 skipping to change at page 21, line 30
Reference Test Setup: Reference Test Setup:
The test SHOULD use one of the test setups described in section 3.1 The test SHOULD use one of the test setups described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. The controller MUST support automatic network discovery. 1. The controller MUST support automatic network discovery.
2. Tester should be able to retrieve the discovered topology 2. Tester should be able to retrieve the discovered topology
information either through controller's management interface or information either through controller's management interface or
northbound interface. northbound interface.
Procedure: Procedure:
1. Establish the network connections between controller and network 1. Establish the network connections between controller and network
nodes. nodes.
2. Query the controller for the discovered network topology 2. Query the controller for the discovered network topology
information and compare it with the deployed network topology information and compare it with the deployed network topology
information. information.
3. 3a. Increase the number of nodes by 1 when the comparison is 3. 3a. Increase the number of nodes by 1 when the comparison is
successful and repeat the test. successful and repeat the test.
4. 3b. Decrease the number of nodes by 1 when the comparison fails 4. 3b. Decrease the number of nodes by 1 when the comparison fails
and repeat the test. and repeat the test.
5. Continue the test until the comparison of step 3b is successful. 5. Continue the test until the comparison of step 3b is successful.
6. Record the number of nodes for the last iteration (Ns) where the 6. Record the number of nodes for the last iteration (Ns) where the
topology comparison was successful. topology comparison was successful.
Measurement: Measurement:
Network Discovery Size = Ns. Network Discovery Size = Ns.
Reporting Format: Reporting Format:
The Network Discovery Size results MUST be reported in addition to The Network Discovery Size results MUST be reported in addition to
the configuration parameters captured in section 5. the configuration parameters captured in section 5.
skipping to change at page 22, line 11 skipping to change at page 22, line 32
The test SHOULD use one of the test setups described in section 3.1 The test SHOULD use one of the test setups described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. The controller Forwarding table should be empty. 1. The controller Forwarding table should be empty.
2. Flow Idle time MUST be set to higher or infinite value. 2. Flow Idle time MUST be set to higher or infinite value.
3. The controller MUST have completed network topology discovery. 3. The controller MUST have completed network topology discovery.
4. Tester should be able to retrieve the forwarding table information 4. Tester should be able to retrieve the forwarding table information
either through controller's management interface or northbound either through controller's management interface or northbound
interface. interface.
Procedure: Procedure:
Reactive Flow Provisioning Mode: Reactive Flow Provisioning Mode:
1. Send bi-directional traffic continuously with unique source and/or 1. Send bi-directional traffic continuously with unique source and/or
destination addresses from test traffic generators TP1 and TP2 at destination addresses from test traffic generators TP1 and TP2 at
the asynchronous message processing rate of controller. the asynchronous message processing rate of controller.
2. Query the controller at a regular interval (e.g., 5 seconds) for 2. Query the controller at a regular interval (e.g., 5 seconds) for
the number of learnt flow entries from its northbound interface. the number of learnt flow entries from its northbound interface.
3. Stop the test when the retrieved value is constant for three 3. Stop the test when the retrieved value is constant for three
consecutive iterations and record the value received from the last consecutive iterations and record the value received from the last
query (Nrp). query (Nrp).
Proactive Flow Provisioning Mode: Proactive Flow Provisioning Mode:
1. Install unique flows continuously through controller's northbound 1. Install unique flows continuously through controller's northbound
or management interface until a failure response is received from or management interface until a failure response is received from
the controller. the controller.
2. Record the total number of successful responses (Nrp). 2. Record the total number of successful responses (Nrp).
Note: Note:
Some controller designs for proactive flow provisioning mode may Some controller designs for proactive flow provisioning mode may
require the switch to send flow setup requests in order to generate require the switch to send flow setup requests in order to generate
flow setup responses. In such cases, it is recommended to generate flow setup responses. In such cases, it is recommended to generate
bi-directional traffic for the provisioned flows. bi-directional traffic for the provisioned flows.
Measurement: Measurement:
skipping to change at page 23, line 37 skipping to change at page 24, line 16
c. Network Topology Change Detection Time c. Network Topology Change Detection Time
Reference Test Setup: Reference Test Setup:
The test SHOULD use one of the test setups described in section 3.1 The test SHOULD use one of the test setups described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. This test MUST be performed after obtaining the baseline 1. This test MUST be performed after obtaining the baseline
measurement results for the above performance tests. measurement results for the above performance tests.
2. Ensure that the invalid messages are not dropped by the 2. Ensure that the invalid messages are not dropped by the
intermediate devices connecting the controller and SDN nodes. intermediate devices connecting the controller and Network
Devices.
Procedure: Procedure:
1. Perform the above listed performance tests and send 1% of messages 1. Perform the above listed performance tests and send 1% of messages
from the Asynchronous Message Processing Rate as invalid messages from the Asynchronous Message Processing Rate as invalid messages
from the connected SDN nodes emulated at the forwarding plane test from the connected Network Devices emulated at the forwarding
emulator. plane test emulator.
2. Perform the above listed performance tests and send 2% of messages 2. Perform the above listed performance tests and send 2% of messages
from the Asynchronous Message Processing Rate as invalid messages from the Asynchronous Message Processing Rate as invalid messages
from the connected SDN nodes emulated at the forwarding plane test from the connected Network Devices emulated at the forwarding
emulator. plane test emulator.
Note: Note:
Invalid messages can be frames with incorrect protocol fields or any Invalid messages can be frames with incorrect protocol fields or any
form of failure notifications sent towards controller. form of failure notifications sent towards controller.
Measurement: Measurement:
Measurement MUST be done as per the equation defined in the Measurement MUST be done as per the equation defined in the
corresponding performance test measurement section. corresponding performance test measurement section.
skipping to change at page 25, line 18 skipping to change at page 25, line 37
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
This test MUST be performed after obtaining the baseline measurement This test MUST be performed after obtaining the baseline measurement
results for the above tests. results for the above tests.
Procedure: Procedure:
1. Perform the listed tests and launch a DoS attack towards 1. Perform the listed tests and launch a DoS attack towards
controller while the test is running. controller while the test is running.
Note: Note:
DoS attacks can be launched on one of the following interfaces. DoS attacks can be launched on one of the following interfaces.
a. Northbound (e.g., Sending a huge number of requests on a. Northbound (e.g., Sending a huge number of requests on
northbound interface) northbound interface)
b. Management (e.g., Ping requests to controller's management b. Management (e.g., Ping requests to controller's management
interface) interface)
c. Southbound (e.g., TCP SYNC messages on southbound interface) c. Southbound (e.g., TCP SYNC messages on southbound interface)
Measurement: Measurement:
Measurement MUST be done as per the equation defined in the Measurement MUST be done as per the equation defined in the
corresponding test's measurement section. corresponding test's measurement section.
Reporting Format: Reporting Format:
The DoS Attacks Handling results MUST be reported in the format of The DoS Attacks Handling results MUST be reported in the format of
table with a column for each of the below parameters and row for table with a column for each of the below parameters and row for
skipping to change at page 26, line 24 skipping to change at page 26, line 42
Reference Test Setup: Reference Test Setup:
The test SHOULD use the test setup described in section 3.2 of this The test SHOULD use the test setup described in section 3.2 of this
document. document.
Prerequisite: Prerequisite:
1. Master controller election MUST be completed. 1. Master controller election MUST be completed.
2. Nodes are connected to the controller cluster as per the 2. Nodes are connected to the controller cluster as per the
Redundancy Mode (RM). Redundancy Mode (RM).
3. The controller cluster should have completed the network topology 3. The controller cluster should have completed the network topology
discovery. discovery.
4. The SDN Node MUST send all new flows to the controller when it 4. The Network Device MUST send all new flows to the controller when
receives from the test traffic generator. it receives from the test traffic generator.
5. Controller should have learnt the location of destination (D1) at 5. Controller should have learnt the location of destination (D1) at
test traffic generator TP2. test traffic generator TP2.
Procedure: Procedure:
1. Send uni-directional traffic continuously with incremental 1. Send uni-directional traffic continuously with incremental
sequence number and source addresses from test traffic generator sequence number and source addresses from test traffic generator
TP1 at the rate that the controller processes without any drops. TP1 at the rate that the controller processes without any drops.
2. Ensure that there are no packet drops observed at the test traffic 2. Ensure that there are no packet drops observed at the test traffic
generator TP2. generator TP2.
3. Bring down the active controller. 3. Bring down the active controller.
4. Stop the test when a first frame received on TP2 after failover 4. Stop the test when a first frame received on TP2 after failover
operation. operation.
5. Record the time at which the last valid frame received (T1) at 5. Record the time at which the last valid frame received (T1) at
test traffic generator TP2 before sequence error and the first test traffic generator TP2 before sequence error and the first
valid frame received (T2) after the sequence error at TP2 valid frame received (T2) after the sequence error at TP2
Measurement: Measurement:
Controller Failover Time = (T2 - T1) Controller Failover Time = (T2 - T1)
Packet Loss = Number of missing packet sequences. Packet Loss = Number of missing packet sequences.
Reporting Format: Reporting Format:
The Controller Failover Time results MUST be tabulated with the The Controller Failover Time results MUST be tabulated with the
following information. following information.
- Number of cluster nodes - Number of cluster nodes
- Redundancy mode - Redundancy mode
skipping to change at page 27, line 35 skipping to change at page 28, line 12
Compute the time taken to re-route the traffic by the controller Compute the time taken to re-route the traffic by the controller
when there is a failure in existing traffic paths. when there is a failure in existing traffic paths.
Reference Test Setup: Reference Test Setup:
This test SHOULD use one of the test setup described in section 3.1 This test SHOULD use one of the test setup described in section 3.1
or section 3.2 of this document. or section 3.2 of this document.
Prerequisite: Prerequisite:
1. Network with the given number of nodes and redundant paths MUST be 1. Network with the given number of nodes and redundant paths MUST be
deployed. deployed.
2. Ensure that the controller MUST have knowledge about the location 2. Ensure that the controller MUST have knowledge about the location
of test traffic generators TP1 and TP2. of test traffic generators TP1 and TP2.
3. Ensure that the controller does not pre-provision the alternate 3. Ensure that the controller does not pre-provision the alternate
path in the emulated SDN nodes at the forwarding plane test path in the emulated Network Devices at the forwarding plane test
emulator. emulator.
Procedure: Procedure:
1. Send bi-directional traffic continuously with unique sequence 1. Send bi-directional traffic continuously with unique sequence
number from TP1 and TP2. number from TP1 and TP2.
2. Bring down a link or switch in the traffic path. 2. Bring down a link or switch in the traffic path.
3. Stop the test after receiving first frame after network re- 3. Stop the test after receiving first frame after network re-
convergence. convergence.
4. Record the time of last received frame prior to the frame loss at 4. Record the time of last received frame prior to the frame loss at
TP2 (TP2-Tlfr) and the time of first frame received after the TP2 (TP2-Tlfr) and the time of first frame received after the
frame loss at TP2 (TP2-Tffr). frame loss at TP2 (TP2-Tffr).
5. Record the time of last received frame prior to the frame loss at 5. Record the time of last received frame prior to the frame loss at
TP1 (TP1-Tlfr) and the time of first frame received after the TP1 (TP1-Tlfr) and the time of first frame received after the
frame loss at TP1 (TP1-Tffr). frame loss at TP1 (TP1-Tffr).
Measurement: Measurement:
Forward Direction Path Re-Provisioning Time (FDRT) Forward Direction Path Re-Provisioning Time (FDRT)
= (TP2-Tffr - TP2-Tlfr) = (TP2-Tffr - TP2-Tlfr)
Reverse Direction Path Re-Provisioning Time (RDRT) Reverse Direction Path Re-Provisioning Time (RDRT)
= (TP1-Tffr - TP1-Tlfr) = (TP1-Tffr - TP1-Tlfr)
Network Re-Provisioning Time = (FDRT+RDRT)/2 Network Re-Provisioning Time = (FDRT+RDRT)/2
skipping to change at page 29, line 33 skipping to change at page 29, line 48
[RFC5440] JP. Vasseur, JL. Le Roux, "Path Computation Element (PCE) [RFC5440] JP. Vasseur, JL. Le Roux, "Path Computation Element (PCE)
Communication Protocol (PCEP)", RFC 5440, March 2009. Communication Protocol (PCEP)", RFC 5440, March 2009.
[OpenFlow Switch Specification] ONF,"OpenFlow Switch Specification" [OpenFlow Switch Specification] ONF,"OpenFlow Switch Specification"
Version 1.4.0 (Wire Protocol 0x05), October 14, 2013. Version 1.4.0 (Wire Protocol 0x05), October 14, 2013.
[I-D.sdn-controller-benchmark-term] Bhuvaneswaran.V, Anton Basil, [I-D.sdn-controller-benchmark-term] Bhuvaneswaran.V, Anton Basil,
Mark.T, Vishwas Manral, Sarah Banks, "Terminology for Mark.T, Vishwas Manral, Sarah Banks, "Terminology for
Benchmarking SDN Controller Performance", Benchmarking SDN Controller Performance",
draft-ietf-bmwg-sdn-controller-benchmark-term-00 draft-ietf-bmwg-sdn-controller-benchmark-term-01
(Work in progress), October 19, 2015 (Work in progress), March 21, 2016
6.2. Informative References 6.2. Informative References
[I-D.i2rs-architecture] A. Atlas, J. Halpern, S. Hares, D. Ward, [I-D.i2rs-architecture] A. Atlas, J. Halpern, S. Hares, D. Ward,
T. Nadeau, "An Architecture for the Interface to the T. Nadeau, "An Architecture for the Interface to the
Routing System", draft-ietf-i2rs-architecture-09 Routing System", draft-ietf-i2rs-architecture-09
(Work in progress), March 6, 2015 (Work in progress), March 6, 2015
[OpenContrail] Ankur Singla, Bruno Rijsman, "OpenContrail [OpenContrail] Ankur Singla, Bruno Rijsman, "OpenContrail
Architecture Documentation", Architecture Documentation",
skipping to change at page 30, line 19 skipping to change at page 30, line 33
8. Security Considerations 8. Security Considerations
Benchmarking tests described in this document are limited to the Benchmarking tests described in this document are limited to the
performance characterization of controller in lab environment with performance characterization of controller in lab environment with
isolated network. isolated network.
9. Acknowledgments 9. Acknowledgments
The authors would like to thank the following individuals for The authors would like to thank the following individuals for
providing their valuable comments to the earlier versions of this providing their valuable comments to the earlier versions of this
document: Al Morton (AT&T), Sandeep Gangadharan (HP), document: Al Morton (AT&T), Sandeep Gangadharan (HP), M. Georgescu
M. Georgescu (NAIST), Andrew McGregor (Google), Scott Bradner (NAIST), Andrew McGregor (Google), Scott Bradner (Harvard
(Harvard University), Jay Karthik (Cisco), Ramakrishnan (Dell), University), Jay Karthik (Cisco), Ramakrishnan (Dell), Khasanov
Khasanov Boris (Huawei), Brian Castelli (Spirent) Boris (Huawei), Brian Castelli (Spirent)
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
Appendix A. Example Test Topologies Appendix A. Example Test Topologies
A.1. Leaf-Spine Topology - Three Tier Network Architecture A.1. Leaf-Spine Topology - Three Tier Network Architecture
+----------+ +----------+
| SDN | | SDN |
| Node | (Core) | Node | (Core)
+----------+ +----------+
/ \ / \
/ \ / \
+------+ +------+ +------+ +------+
| SDN | | SDN | (Spine) | SDN | | SDN | (Spine)
| Node |.. | Node | | Node |.. | Node |
+------+ +------+ +------+ +------+
/ \ / \ / \ / \
/ \ / \ / \ / \
l1 / / \ ln-1 l1 / / \ ln-1
/ / \ \ / / \ \
+--------+ +-------+ +--------+ +-------+
| SDN | | SDN | | SDN | | SDN |
| Node |.. | Node | (Leaf) | Node |.. | Node | (Leaf)
+--------+ +-------+ +--------+ +-------+
A.2. Leaf-Spine Topology - Two Tier Network Architecture A.2. Leaf-Spine Topology - Two Tier Network Architecture
+------+ +------+ +------+ +------+
| SDN | | SDN | (Spine) | SDN | | SDN | (Spine)
| Node |.. | Node | | Node |.. | Node |
+------+ +------+ +------+ +------+
/ \ / \ / \ / \
/ \ / \ / \ / \
l1 / / \ ln-1 l1 / / \ ln-1
/ / \ \ / / \ \
+--------+ +-------+ +--------+ +-------+
| SDN | | SDN | | SDN | | SDN |
| Node |.. | Node | (Leaf) | Node |.. | Node | (Leaf)
+--------+ +-------+ +--------+ +-------+
Appendix B. Benchmarking Methodology using OpenFlow Controllers Appendix B. Benchmarking Methodology using OpenFlow Controllers
This section gives an overview of OpenFlow protocol and provides This section gives an overview of OpenFlow protocol and provides
test methodology to benchmark SDN controllers supporting OpenFlow test methodology to benchmark SDN controllers supporting OpenFlow
southbound protocol. southbound protocol.
B.1. Protocol Overview B.1. Protocol Overview
OpenFlow is an open standard protocol defined by Open Networking OpenFlow is an open standard protocol defined by Open Networking
Foundation (ONF), used for programming the forwarding plane of Foundation (ONF), used for programming the forwarding plane of
network switches or routers via a centralized controller. network switches or routers via a centralized controller.
B.2. Messages Overview B.2. Messages Overview
OpenFlow protocol supports three messages types namely controller- OpenFlow protocol supports three messages types namely controller-
to-switch, asynchronous and symmetric. to-switch, asynchronous and symmetric.
Controller-to-switch messages are initiated by the controller and Controller-to-switch messages are initiated by the controller and
used to directly manage or inspect the state of the switch. These used to directly manage or inspect the state of the switch. These
messages allow controllers to query/configure the switch (Features, messages allow controllers to query/configure the switch (Features,
Configuration messages), collect information from switch (Read-State Configuration messages), collect information from switch (Read-State
message), send packets on specified port of switch (Packet-out message), send packets on specified port of switch (Packet-out
message), and modify switch forwarding plane and state (Modify- message), and modify switch forwarding plane and state (Modify-
skipping to change at page 32, line 40 skipping to change at page 32, line 40
Asynchronous messages are generated by the switch without a Asynchronous messages are generated by the switch without a
controller soliciting them. These messages allow switches to update controller soliciting them. These messages allow switches to update
controllers to denote an arrival of new flow (Packet-in), switch controllers to denote an arrival of new flow (Packet-in), switch
state change (Flow-Removed, Port-status) and error (Error). state change (Flow-Removed, Port-status) and error (Error).
Symmetric messages are generated in either direction without Symmetric messages are generated in either direction without
solicitation. These messages allow switches and controllers to set solicitation. These messages allow switches and controllers to set
up connection (Hello), verify for liveness (Echo) and offer up connection (Hello), verify for liveness (Echo) and offer
additional functionalities (Experimenter). additional functionalities (Experimenter).
B.3. Connection Overview B.3. Connection Overview
OpenFlow channel is used to exchange OpenFlow message between an OpenFlow channel is used to exchange OpenFlow message between an
OpenFlow switch and an OpenFlow controller. The OpenFlow channel OpenFlow switch and an OpenFlow controller. The OpenFlow channel
connection can be setup using plain TCP or TLS. By default, a switch connection can be setup using plain TCP or TLS. By default, a switch
establishes single connection with SDN controller. A switch may establishes single connection with SDN controller. A switch may
establish multiple parallel connections to single controller establish multiple parallel connections to single controller
(auxiliary connection) or multiple controllers to handle controller (auxiliary connection) or multiple controllers to handle controller
failures and load balancing. failures and load balancing.
B.4. Performance Benchmarking Tests B.4. Performance Benchmarking Tests
B.4.1. Network Topology Discovery Time B.4.1. Network Topology Discovery Time
Procedure: Procedure:
SDN Nodes OpenFlow SDN Network Devices OpenFlow SDN
Controller Application Controller Application
| | | | | |
| |<Initialize controller | | |<Initialize controller |
| |app.,NB and SB interfaces> | | |app.,NB and SB interfaces> |
| | | | | |
|<Deploy network with | | |<Deploy network with | |
| given no. of OF switches> | | | given no. of OF switches> | |
| | | | | |
| OFPT_HELLO Exchange | | | OFPT_HELLO Exchange | |
|<-------------------------->| | |<-------------------------->| |
skipping to change at page 34, line 25 skipping to change at page 34, line 25
The Network Topology Discovery Time can be obtained by calculating The Network Topology Discovery Time can be obtained by calculating
the time difference between the first PACKET_OUT with LLDP message the time difference between the first PACKET_OUT with LLDP message
received from the controller (Tm1) and the last PACKET_IN with LLDP received from the controller (Tm1) and the last PACKET_IN with LLDP
message sent to the controller (Tmn) when the comparison is message sent to the controller (Tmn) when the comparison is
successful. successful.
B.4.2. Asynchronous Message Processing Time B.4.2. Asynchronous Message Processing Time
Procedure: Procedure:
SDN Nodes OpenFlow SDN Network Devices OpenFlow SDN
Controller Application Controller Application
| | | | | |
|PACKET_IN with single | | |PACKET_IN with single | |
|OFP match header | | |OFP match header | |
(T0)|--------------------------->| | (T0)|--------------------------->| |
| | | | | |
| PACKET_OUT with single OFP | | | PACKET_OUT with single OFP | |
| action header | | | action header | |
(R0)|<---------------------------| | (R0)|<---------------------------| |
| . | | | . | |
skipping to change at page 35, line 24 skipping to change at page 35, line 24
Discussion: Discussion:
The Asynchronous Message Processing Time will be obtained by sum of The Asynchronous Message Processing Time will be obtained by sum of
((R0-T0),(R1-T1)..(Rn - Tn))/ Nrx. ((R0-T0),(R1-T1)..(Rn - Tn))/ Nrx.
B.4.3. Asynchronous Message Processing Rate B.4.3. Asynchronous Message Processing Rate
Procedure: Procedure:
SDN Nodes OpenFlow SDN Network Devices OpenFlow SDN
Controller Application Controller Application
| | | | | |
|PACKET_IN with multiple OFP | | |PACKET_IN with multiple OFP | |
|match headers | | |match headers | |
|--------------------------->| | |--------------------------->| |
| | | | | |
| PACKET_OUT with multiple | | | PACKET_OUT with multiple | |
| OFP action headers| | | OFP action headers| |
|<---------------------------| | |<---------------------------| |
| | | | | |
skipping to change at page 36, line 25 skipping to change at page 36, line 25
Discussion: Discussion:
The Asynchronous Message Processing Rate will be obtained by The Asynchronous Message Processing Rate will be obtained by
calculating the number of OFP action headers received in all calculating the number of OFP action headers received in all
PACKET_OUT messages during the test duration. PACKET_OUT messages during the test duration.
B.4.4. Reactive Path Provisioning Time B.4.4. Reactive Path Provisioning Time
Procedure: Procedure:
Test Traffic Test Traffic SDN Nodes OpenFlow Test Traffic Test Traffic Network Devices OpenFlow
Generator TP1 Generator TP2 Controller Generator TP1 Generator TP2 Controller
| | | | | | | |
| |G-ARP (D1) | | | |G-ARP (D1) | |
| |--------------------->| | | |--------------------->| |
| | | | | | | |
| | |PACKET_IN(D1) | | | |PACKET_IN(D1) |
| | |------------------>| | | |------------------>|
| | | | | | | |
|Traffic (S1,D1) | | |Traffic (S1,D1) | |
(Tsf1)|----------------------------------->| | (Tsf1)|----------------------------------->| |
skipping to change at page 37, line 21 skipping to change at page 37, line 21
Discussion: Discussion:
The Reactive Path Provisioning Time can be obtained by finding the The Reactive Path Provisioning Time can be obtained by finding the
time difference between the transmit and receive time of the traffic time difference between the transmit and receive time of the traffic
(Tsf1-Tdf1). (Tsf1-Tdf1).
B.4.5. Proactive Path Provisioning Time B.4.5. Proactive Path Provisioning Time
Procedure: Procedure:
Test Traffic Test Traffic SDN Nodes OpenFlow SDN Test Traffic Test Traffic Network Devices OpenFlow SDN
Generator TP1 Generator TP2 Controller Application Generator TP1 Generator TP2 Controller Application
| | | | | | | | | |
| |G-ARP (D1) | | | | |G-ARP (D1) | | |
| |-------------->| | | | |-------------->| | |
| | | | | | | | | |
| | |PACKET_IN(D1) | | | | |PACKET_IN(D1) | |
| | |--------------->| | | | |--------------->| |
| | | | | | | | | |
|Traffic (S1,D1) | | | |Traffic (S1,D1) | | |
Tsf1)|---------------------------->| | | Tsf1)|---------------------------->| | |
skipping to change at page 38, line 15 skipping to change at page 38, line 15
Discussion: Discussion:
The Proactive Path Provisioning Time can be obtained by finding the The Proactive Path Provisioning Time can be obtained by finding the
time difference between the transmit and receive time of the traffic time difference between the transmit and receive time of the traffic
(Tsf1-Tdf1). (Tsf1-Tdf1).
B.4.6. Reactive Path Provisioning Rate B.4.6. Reactive Path Provisioning Rate
Procedure: Procedure:
Test Traffic Test Traffic SDN Nodes OpenFlow Test Traffic Test Traffic Network Devices OpenFlow
Generator TP1 Generator TP2 Controller Generator TP1 Generator TP2 Controller
| | | | | | | |
| | | | | | | |
| | | | | | | |
| |G-ARP (D1..Dn) | | | |G-ARP (D1..Dn) | |
| |--------------------| | | |--------------------| |
| | | | | | | |
| | |PACKET_IN(D1..Dn) | | | |PACKET_IN(D1..Dn) |
| | |--------------------->| | | |--------------------->|
| | | | | | | |
skipping to change at page 39, line 27 skipping to change at page 39, line 27
Discussion: Discussion:
The Reactive Path Provisioning Rate can be obtained by finding the The Reactive Path Provisioning Rate can be obtained by finding the
total number of frames received at TP2 after the test duration. total number of frames received at TP2 after the test duration.
B.4.7. Proactive Path Provisioning Rate B.4.7. Proactive Path Provisioning Rate
Procedure: Procedure:
Test Traffic Test Traffic SDN Nodes OpenFlow SDN Test Traffic Test Traffic Network Devices OpenFlow SDN
Generator TP1 Generator TP2 Controller Application Generator TP1 Generator TP2 Controller Application
| | | | | | | | | |
| |G-ARP (D1..Dn) | | | | |G-ARP (D1..Dn) | | |
| |-------------->| | | | |-------------->| | |
| | | | | | | | | |
| | |PACKET_IN(D1.Dn)| | | | |PACKET_IN(D1.Dn)| |
| | |--------------->| | | | |--------------->| |
| | | | | | | | | |
|Traffic (S1..Sn,D1..Dn) | | | |Traffic (S1..Sn,D1..Dn) | | |
Tsf1)|---------------------------->| | | Tsf1)|---------------------------->| | |
skipping to change at page 40, line 34 skipping to change at page 40, line 34
Discussion: Discussion:
The Proactive Path Provisioning Rate can be obtained by finding the The Proactive Path Provisioning Rate can be obtained by finding the
total number of frames received at TP2 after the test duration total number of frames received at TP2 after the test duration
B.4.8. Network Topology Change Detection Time B.4.8. Network Topology Change Detection Time
Procedure: Procedure:
SDN Nodes OpenFlow SDN Network Devices OpenFlow SDN
Controller Application Controller Application
| | | | | |
| | <Bring down a link in | | | <Bring down a link in |
| | switch S1>| | | switch S1>|
| | | | | |
T0 |PORT_STATUS with link down | | T0 |PORT_STATUS with link down | |
| from S1 | | | from S1 | |
|--------------------------->| | |--------------------------->| |
| | | | | |
|First PACKET_OUT with LLDP | | |First PACKET_OUT with LLDP | |
skipping to change at page 41, line 13 skipping to change at page 41, line 13
| | PACKET_OUT with LLDP T1>| | | PACKET_OUT with LLDP T1>|
Discussion: Discussion:
The Network Topology Change Detection Time can be obtained by The Network Topology Change Detection Time can be obtained by
finding the difference between the time the OpenFlow switch S1 sends finding the difference between the time the OpenFlow switch S1 sends
the PORT_STATUS message (T0) and the time that the OpenFlow the PORT_STATUS message (T0) and the time that the OpenFlow
controller sends the first topology re-discovery message (T1) to controller sends the first topology re-discovery message (T1) to
OpenFlow switches. OpenFlow switches.
B.5. Scalability B.5. Scalability
B.5.1. Control Sessions Capacity B.5.1. Control Sessions Capacity
Procedure: Procedure:
SDN Nodes OpenFlow Network Devices OpenFlow
Controller Controller
| | | |
| OFPT_HELLO Exchange for Switch 1 | | OFPT_HELLO Exchange for Switch 1 |
|<------------------------------------->| |<------------------------------------->|
| | | |
| OFPT_HELLO Exchange for Switch 2 | | OFPT_HELLO Exchange for Switch 2 |
|<------------------------------------->| |<------------------------------------->|
| . | | . |
| . | | . |
| . | | . |
skipping to change at page 41, line 42 skipping to change at page 41, line 42
| | | |
Discussion: Discussion:
The value of Switch n-1 will provide Control Sessions Capacity. The value of Switch n-1 will provide Control Sessions Capacity.
B.5.2. Network Discovery Size B.5.2. Network Discovery Size
Procedure: Procedure:
SDN Nodes OpenFlow SDN Network Devices OpenFlow SDN
Controller Application Controller Application
| | | | | |
| | <Deploy network with | | | <Deploy network with |
| |given no. of OF switches N>| | |given no. of OF switches N>|
| | | | | |
| OFPT_HELLO Exchange | | | OFPT_HELLO Exchange | |
|<-------------------------->| | |<-------------------------->| |
| | | | | |
| PACKET_OUT with LLDP | | | PACKET_OUT with LLDP | |
| to all switches | | | to all switches | |
skipping to change at page 43, line 6 skipping to change at page 43, line 6
Discussion: Discussion:
The value of N1 provides the Network Discovery Size value. The test The value of N1 provides the Network Discovery Size value. The test
duration can be set to the stipulated time within which the user duration can be set to the stipulated time within which the user
expects the controller to complete the discovery process. expects the controller to complete the discovery process.
B.5.3. Forwarding Table Capacity B.5.3. Forwarding Table Capacity
Procedure: Procedure:
Test Traffic SDN Nodes OpenFlow SDN Test Traffic Network Devices OpenFlow SDN
Generator TP1 Controller Application Generator TP1 Controller Application
| | | | | | | |
| | | | | | | |
|G-ARP (H1..Hn) | | | |G-ARP (H1..Hn) | | |
|----------------->| | | |----------------->| | |
| | | | | | | |
| |PACKET_IN(D1..Dn) | | | |PACKET_IN(D1..Dn) | |
| |------------------>| | | |------------------>| |
| | | | | | | |
| | |<Wait for 5 secs>| | | |<Wait for 5 secs>|
skipping to change at page 44, line 5 skipping to change at page 44, line 5
FWD: Forwarding Table FWD: Forwarding Table
Discussion: Discussion:
Query the controller forwarding table entries for multiple times Query the controller forwarding table entries for multiple times
until the three consecutive queries return the same value. The last until the three consecutive queries return the same value. The last
value retrieved from the controller will provide the Forwarding value retrieved from the controller will provide the Forwarding
Table Capacity value. The query interval is user configurable. The 5 Table Capacity value. The query interval is user configurable. The 5
seconds shown in this example is for representational purpose. seconds shown in this example is for representational purpose.
B.6. Security B.6. Security
B.6.1. Exception Handling B.6.1. Exception Handling
Procedure: Procedure:
Test Traffic Test Traffic SDN Nodes OpenFlow SDN Test Traffic Test Traffic Network Devices OpenFlow SDN
Generator TP1 Generator TP2 Controller Application Generator TP1 Generator TP2 Controller Application
| | | | | | | | | |
| |G-ARP (D1..Dn) | | | | |G-ARP (D1..Dn) | | |
| |------------------>| | | | |------------------>| | |
| | | | | | | | | |
| | |PACKET_IN(D1..Dn)| | | | |PACKET_IN(D1..Dn)| |
| | |---------------->| | | | |---------------->| |
| | | | | | | | | |
|Traffic (S1..Sn,D1..Dn) | | | |Traffic (S1..Sn,D1..Dn) | | |
|----------------------------->| | | |----------------------------->| | |
skipping to change at page 45, line 41 skipping to change at page 45, line 41
The procedure defined above provides test steps to determine the The procedure defined above provides test steps to determine the
effect of handling error packets on Path Programming Rate. Same effect of handling error packets on Path Programming Rate. Same
procedure can be adopted to determine the effects on other procedure can be adopted to determine the effects on other
performance tests listed in this benchmarking tests. performance tests listed in this benchmarking tests.
B.6.2. Denial of Service Handling B.6.2. Denial of Service Handling
Procedure: Procedure:
Test Traffic Test Traffic SDN Nodes OpenFlow SDN Test Traffic Test Traffic Network Devic OpenFlow SDN
Generator TP1 Generator TP2 Controller Application Generator TP1 Generator TP2 Controller Application
| | | | | | | | | |
| |G-ARP (D1..Dn) | | | | |G-ARP (D1..Dn) | | |
| |------------------>| | | | |------------------>| | |
| | | | | | | | | |
| | |PACKET_IN(D1..Dn)| | | | |PACKET_IN(D1..Dn)| |
| | |---------------->| | | | |---------------->| |
| | | | | | | | | |
|Traffic (S1..Sn,D1..Dn) | | | |Traffic (S1..Sn,D1..Dn) | | |
|----------------------------->| | | |----------------------------->| | |
skipping to change at page 47, line 5 skipping to change at page 47, line 5
TCP SYN attack should be launched from one of the emulated/simulated TCP SYN attack should be launched from one of the emulated/simulated
OpenFlow Switch. Rn1 provides the Path Programming Rate of OpenFlow Switch. Rn1 provides the Path Programming Rate of
controller uponhandling denial of service attack. controller uponhandling denial of service attack.
The procedure defined above provides test steps to determine the The procedure defined above provides test steps to determine the
effect of handling denial of service on Path Programming Rate. Same effect of handling denial of service on Path Programming Rate. Same
procedure can be adopted to determine the effects on other procedure can be adopted to determine the effects on other
performance tests listed in this benchmarking tests. performance tests listed in this benchmarking tests.
B.7. Reliability B.7. Reliability
B.7.1. Controller Failover Time B.7.1. Controller Failover Time
Procedure: Procedure:
Test Traffic Test Traffic SDN Nodes OpenFlow SDN Test Traffic Test Traffic Network Device OpenFlow SDN
Generator TP1 Generator TP2 Controller Application Generator TP1 Generator TP2 Controller Application
| | | | | | | | | |
| |G-ARP (D1) | | | | |G-ARP (D1) | | |
| |------------>| | | | |------------>| | |
| | | | | | | | | |
| | |PACKET_IN(D1) | | | | |PACKET_IN(D1) | |
| | |---------------->| | | | |---------------->| |
| | | | | | | | | |
|Traffic (S1..Sn,D1) | | | |Traffic (S1..Sn,D1) | | |
|-------------------------->| | | |-------------------------->| | |
skipping to change at page 48, line 36 skipping to change at page 48, line 36
traffic loss and the first frame received after the traffic loss traffic loss and the first frame received after the traffic loss
will provide the controller failover time. will provide the controller failover time.
If there is no frame loss during controller failover time, the If there is no frame loss during controller failover time, the
controller failover time can be deemed negligible. controller failover time can be deemed negligible.
B.7.2. Network Re-Provisioning Time B.7.2. Network Re-Provisioning Time
Procedure: Procedure:
Test Traffic Test Traffic SDN Nodes OpenFlow SDN Test Traffic Test Traffic Network Devices OpenFlow SDN
Generator TP1 Generator TP2 Controller Application Generator TP1 Generator TP2 Controller Application
| | | | | | | | | |
| |G-ARP (D1) | | | | |G-ARP (D1) | | |
| |-------------->| | | | |-------------->| | |
| | | | | | | | | |
| | |PACKET_IN(D1) | | | | |PACKET_IN(D1) | |
| | |---------------->| | | | |---------------->| |
| G-ARP (S1) | | | | G-ARP (S1) | | |
|---------------------------->| | | |---------------------------->| | |
| | | | | | | | | |
skipping to change at page 51, line 28 skipping to change at page 51, line 28
Philadelphia Philadelphia
PA 19113 PA 19113
Email: anton.basil@veryxtech.com Email: anton.basil@veryxtech.com
Mark Tassinari Mark Tassinari
Hewlett-Packard, Hewlett-Packard,
8000 Foothills Blvd, 8000 Foothills Blvd,
Roseville, CA 95747 Roseville, CA 95747
Email: mark.tassinari@hp.com Email: mark.tassinari@hpe.com
Vishwas Manral Vishwas Manral
Ionos Corp, Nano Sec,
4100 Moorpark Ave, CA
San Jose, CA
Email: vishwas@ionosnetworks.com Email: vishwas.manral@gmail.com
Sarah Banks Sarah Banks
VSS Monitoring VSS Monitoring
930 De Guigne Drive, 930 De Guigne Drive,
Sunnyvale, CA Sunnyvale, CA
Email: sbanks@encrypted.net Email: sbanks@encrypted.net
 End of changes. 133 change blocks. 
320 lines changed or deleted 343 lines changed or added

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