idnits 2.17.1 draft-ietf-bmwg-sdn-controller-benchmark-term-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 21, 2016) is 2958 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC7426' is defined on line 851, but no explicit reference was found in the text == Unused Reference: 'RFC4689' is defined on line 856, but no explicit reference was found in the text == Unused Reference: 'RFC2330' is defined on line 860, but no explicit reference was found in the text == Unused Reference: 'I-D.sdn-controller-benchmark-meth' is defined on line 867, but no explicit reference was found in the text == Unused Reference: 'OpenContrail' is defined on line 875, but no explicit reference was found in the text == Unused Reference: 'OpenDaylight' is defined on line 879, but no explicit reference was found in the text == Outdated reference: A later version (-09) exists of draft-ietf-bmwg-sdn-controller-benchmark-meth-01 Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet-Draft Bhuvaneswaran Vengainathan 2 Network Working Group Anton Basil 3 Intended Status: Informational Veryx Technologies 4 Expires: September 19, 2016 Mark Tassinari 5 Hewlett-Packard 6 Vishwas Manral 7 Nano Sec 8 Sarah Banks 9 VSS Monitoring 10 March 21, 2016 12 Terminology for Benchmarking SDN Controller Performance 13 draft-ietf-bmwg-sdn-controller-benchmark-term-01 15 Abstract 17 This document defines terminology for benchmarking an SDN 18 controller's control plane performance. It extends the terminology 19 already defined in RFC 7426 for the purpose of benchmarking SDN 20 controllers. The terms provided in this document help to benchmark 21 SDN controller's performance independent of the controller's 22 supported protocols and/or network services. A mechanism for 23 benchmarking the performance of SDN controllers is defined in the 24 companion methodology document. These two documents provide a 25 standard mechanism to measure and evaluate the performance of 26 various controller implementations. 28 Status of this Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current. 38 Internet-Drafts are draft documents valid for a maximum of six 39 months and may be updated, replaced, or obsoleted by other documents 40 at any time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress. 43 This Internet-Draft will expire on September 19, 2016. 45 Copyright Notice 47 Copyright (c) 2016 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with 55 respect to this document. Code Components extracted from this 56 document must include Simplified BSD License text as described in 57 Section 4.e of the Trust Legal Provisions and are provided without 58 warranty as described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction...................................................3 63 2. Term Definitions...............................................4 64 2.1. SDN Terms.................................................4 65 2.1.1. Flow.................................................4 66 2.1.2. Northbound Interface.................................4 67 2.1.3. Controller Forwarding Table..........................4 68 2.1.4. Proactive Flow Provisioning Mode.....................5 69 2.1.5. Reactive Flow Provisioning Mode......................5 70 2.1.6. Path.................................................6 71 2.1.7. Standalone Mode......................................6 72 2.1.8. Cluster/Redundancy Mode..............................6 73 2.1.9. Asynchronous Message.................................7 74 2.1.10. Test Traffic Generator..............................7 75 2.2. Test Configuration/Setup Terms............................8 76 2.2.1. Number of Network Devices............................8 77 2.2.2. Test Iterations......................................8 78 2.2.3. Test Duration........................................8 79 2.2.4. Number of Cluster nodes..............................9 80 2.3. Benchmarking Terms........................................9 81 2.3.1. Performance..........................................9 82 2.3.1.1. Network Topology Discovery Time.................9 83 2.3.1.2. Asynchronous Message Processing Time...........10 84 2.3.1.3. Asynchronous Message Processing Rate...........10 85 2.3.1.4. Reactive Path Provisioning Time................11 86 2.3.1.5. Proactive Path Provisioning Time...............11 87 2.3.1.6. Reactive Path Provisioning Rate................12 88 2.3.1.7. Proactive Path Provisioning Rate...............12 89 2.3.1.8. Network Topology Change Detection Time.........12 90 2.3.2. Scalability.........................................13 91 2.3.2.1. Control Sessions Capacity......................13 92 2.3.2.2. Network Discovery Size.........................13 93 2.3.2.3. Forwarding Table Capacity......................14 94 2.3.3. Security............................................14 95 2.3.3.1. Exception Handling.............................14 96 2.3.3.2. Denial of Service Handling.....................15 97 2.3.4. Reliability.........................................15 98 2.3.4.1. Controller Failover Time.......................15 99 2.3.4.2. Network Re-Provisioning Time...................16 100 3. Test Setup....................................................16 101 3.1. Test setup - Controller working in Standalone Mode.......17 102 3.2. Test setup - Controller working in Cluster Mode..........18 103 4. Test Coverage.................................................19 104 5. References....................................................20 105 5.1. Normative References.....................................20 106 5.2. Informative References...................................20 107 6. IANA Considerations...........................................20 108 7. Security Considerations.......................................20 109 8. Acknowledgements..............................................21 110 9. Authors' Addresses............................................21 112 1. Introduction 114 Software Defined Networking (SDN) is a networking architecture in 115 which network control is decoupled from the underlying forwarding 116 function and is placed in a centralized location called the SDN 117 controller. The SDN controller abstracts the underlying network and 118 offers a global view of the overall network to applications and 119 business logic. Thus, an SDN controller provides the flexibility to 120 program, control, and manage network behaviour dynamically through 121 standard interfaces. Since the network controls are logically 122 centralized, the need to benchmark the SDN controller performance 123 becomes significant. This document defines terms to benchmark 124 various controller designs for performance, scalability, reliability 125 and security, independent of northbound and southbound protocols. 127 Conventions used in this document 129 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 130 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 131 document are to be interpreted as described in RFC 2119. 133 2. Term Definitions 135 2.1. SDN Terms 137 The terms defined in this section are extensions to the terms 138 defined in RFC 7426 ''Software-Defined Networking (SDN): Layers and 139 Architecture Terminology''. This RFC should be referred before 140 attempting to make use of this document. 142 2.1.1. Flow 144 Definition: 145 The definition of Flow is same as microflows defined in RFC 4689 146 Section 3.1.5. 148 Discussion: 149 A flow can be set of packets having same source address, destination 150 address, source port and destination port, or any of these 151 combinations. 153 Measurement Units: 154 N/A 156 See Also: 157 None 159 2.1.2. Northbound Interface 161 Definition: 162 The definition of northbound interface is same Service Interface 163 defined in RFC 7426. 165 Discussion: 166 The northbound interface allows SDN applications and orchestration 167 systems to program and retrieve the network information through the 168 SDN controller. 170 Measurement Units: 171 N/A 173 See Also: 174 None 176 2.1.3. Controller Forwarding Table 178 Definition: 180 A controller forwarding table contains flow entries learned in one 181 of two ways: first, entries could be learned from traffic received 182 through the data plane, or, second, these entries could be 183 statically provisioned on the controller, and distributed to devices 184 via the southbound interface. 186 Discussion: 187 The controller forwarding table has an aging mechanism which will be 188 applied only for dynamically learnt entries. 190 Measurement Units: 191 N/A 193 See Also: 194 None 196 2.1.4. Proactive Flow Provisioning Mode 198 Definition: 199 Controller programming flows in Network Devices based on the flow 200 entries provisioned through controller's northbound interface. 202 Discussion: 203 Orchestration systems and SDN applications can define the network 204 forwarding behaviour by programming the controller using proactive 205 flow provisioning. The controller can then program the Network 206 Devices with the pre-provisioned entries. 208 Measurement Units: 209 N/A 211 See Also: 212 None 214 2.1.5. Reactive Flow Provisioning Mode 216 Definition: 217 Controller programming flows in Network Devices based on the traffic 218 received from Network Devices through controller's southbound 219 interface 221 Discussion: 222 The SDN controller dynamically decides the forwarding behaviour 223 based on the incoming traffic from the Network Devices. The 224 controller then programs the Network Devices using Reactive Flow 225 Provisioning. 227 Measurement Units: 228 N/A 230 See Also: 231 None 233 2.1.6. Path 235 Definition: 236 Refer to Section 5 in RFC 2330. 238 Discussion: 239 None 241 Measurement Units: 242 N/A 244 See Also: 245 None 247 2.1.7. Standalone Mode 249 Definition: 250 Single controller handling all control plane functionalities without 251 redundancy, or the ability to provide high availability and/or 252 automatic failover. 254 Discussion: 255 In standalone mode, one controller manages one or more network 256 domains. 258 Measurement Units: 259 N/A 261 See Also: 262 None 264 2.1.8. Cluster/Redundancy Mode 266 Definition: 267 A group of 2 or more controllers handling all control plane 268 functionalities. 270 Discussion: 272 In cluster mode, multiple controllers are teamed together for the 273 purpose of load sharing and/or high availability. The controllers in 274 the group may work in active/standby (master/slave) or active/active 275 (equal) mode depending on the intended purpose. 277 Measurement Units: 278 N/A 280 See Also: 281 None 283 2.1.9. Asynchronous Message 285 Definition: 286 Any message from the Network Device that is generated for network 287 events. 289 Discussion: 290 Control messages like flow setup request and response message is 291 classified as asynchronous message. The controller has to return a 292 response message. Note that the Network Device will not be in 293 blocking mode and continues to send/receive other control messages 295 Measurement Units: 296 N/A 298 See Also: 299 None 301 2.1.10. Test Traffic Generator 303 Definition: 304 Test Traffic Generator is an entity that generates/receives network 305 traffic. 307 Discussion: 308 Test Traffic Generator can be an entity that interfaces with Network 309 Devices to send/receive real-time network traffic. 311 Measurement Units: 312 N/A 314 See Also: 315 None 317 2.2. Test Configuration/Setup Terms 319 2.2.1. Number of Network Devices 321 Definition: 322 The number of Network Devices present in the defined test topology. 324 Discussion: 325 The Network Devices defined in the test topology can be deployed 326 using real hardware or emulated in hardware platforms. 328 Measurement Units: 329 N/A 331 See Also: 332 None 334 2.2.2. Test Iterations 336 Definition: 337 The number of times the test needs to be repeated. 339 Discussion: 340 The test needs to be repeated for multiple iterations to obtain a 341 reliable metric. It is recommended that this test SHOULD be 342 performed for at least 10 iterations to increase the confidence in 343 measured result. 345 Measurement Units: 346 N/A 348 See Also: 349 None 351 2.2.3. Test Duration 353 Definition: 354 Defines the duration of test trails for each iteration. 356 Discussion: 357 Test duration forms the basis for stop criteria for benchmarking 358 tests. Test not completed within this time interval is considered as 359 incomplete. 361 Measurement Units: 362 seconds 364 See Also: 365 None 367 2.2.4. Number of Cluster nodes 369 Definition: 370 Defines the number of controllers present in the controller cluster. 372 Discussion: 373 This parameter is relevant when testing the controller performance 374 in clustering/teaming mode. The number of nodes in the cluster MUST 375 be greater than 1. 377 Measurement Units: 378 N/A 380 See Also: 381 None 383 2.3. Benchmarking Terms 385 This section defines metrics for benchmarking the SDN controller. 386 The procedure to perform the defined metrics is defined in the 387 accompanying methodology document. 389 2.3.1. Performance 391 2.3.1.1. Network Topology Discovery Time 393 Definition: 394 To measure the time taken to discover the network topology - nodes 395 and links by a controller. 397 Discussion: 398 Network topology discovery is key for the SDN controller to 399 provision and manage the network. So it is important to measure how 400 quickly the controller discovers the topology to learn the current 401 network state. This benchmark is obtained by presenting a network 402 topology (Tree, Mesh or Linear) with the given number of nodes to 403 the controller and wait for the discovery process to complete .It is 404 expected that the controller supports network discovery mechanism 405 and uses protocol messages for its discovery process. 407 Measurement Units: 408 milliseconds 410 See Also: 411 None 413 2.3.1.2. Asynchronous Message Processing Time 415 Definition: 416 To measure the time taken by the controller to process an 417 asynchronous message. 419 Discussion: 420 For SDN to support dynamic network provisioning, it is important to 421 measure how quickly the controller responds to an event triggered 422 from the network. The event could be any notification messages 423 generated by an Network Device upon arrival of a new flow, link down 424 etc. This benchmark is obtained by sending asynchronous messages 425 from every connected Network Devices one at a time for the defined 426 test duration. This test assumes that the controller will respond to 427 the received asynchronous message. 429 Measurement Units: 430 milliseconds 432 See Also: 433 None 435 2.3.1.3. Asynchronous Message Processing Rate 437 Definition: 438 To measure the maximum number of asynchronous messages that a 439 controller can process within the test duration. 441 Discussion: 442 As SDN assures flexible network and agile provisioning, it is 443 important to measure how many network events that the controller can 444 handle at a time. This benchmark is obtained by sending asynchronous 445 messages from every connected Network Devices at full connection 446 capacity for the given test duration. This test assumes that the 447 controller will respond to all the received asynchronous messages. 449 Measurement Units: 450 Messages processed per second. 452 See Also: 453 None 455 2.3.1.4. Reactive Path Provisioning Time 457 Definition: 458 The time taken by the controller to setup a path reactively between 459 source and destination node, expressed in milliseconds. 461 Discussion: 462 As SDN supports agile provisioning, it is important to measure how 463 fast that the controller provisions an end-to-end flow in the 464 dataplane. The benchmark is obtained by sending traffic from a 465 source endpoint to the destination endpoint, finding the time 466 difference between the first and the last flow provisioning message 467 exchanged between the controller and the Network Devices for the 468 traffic path. 470 Measurement Units: 471 milliseconds. 473 See Also: 474 None 476 2.3.1.5. Proactive Path Provisioning Time 478 Definition: 479 The time taken by the controller to setup a path proactively between 480 source and destination node, expressed in milliseconds. 482 Discussion: 483 For SDN to support pre-provisioning of traffic path from 484 application, it is important to measure how fast that the controller 485 provisions an end-to-end flow in the dataplane. The benchmark is 486 obtained by provisioning a flow on controller's northbound interface 487 for the traffic to reach from a source to a destination endpoint, 488 finding the time difference between the first and the last flow 489 provisioning message exchanged between the controller and the 490 Network Devices for the traffic path. 492 Measurement Units: 493 milliseconds. 495 See Also: 496 None 498 2.3.1.6. Reactive Path Provisioning Rate 500 Definition: 501 Measure the maximum number of independent paths a controller can 502 concurrently establish between source and destination nodes 503 reactively within the test duration, expressed in paths per second. 505 Discussion: 506 For SDN to support agile traffic forwarding, it is important to 507 measure how many end-to-end flows that the controller could setup in 508 the dataplane. This benchmark is obtained by sending traffic each 509 with unique source and destination pairs from the source Network 510 Device and determine the number of frames received at the 511 destination Network Device. 513 Measurement Units: 514 Paths provisioned per second. 516 See Also: 517 None 519 2.3.1.7. Proactive Path Provisioning Rate 521 Definition: 522 Measure the maximum number of independent paths a controller can 523 concurrently establish between source and destination nodes 524 proactively within the test duration, expressed in paths per second. 526 Discussion: 527 For SDN to support pre-provisioning of traffic path for a larger 528 network from the application, it is important to measure how many 529 end-to-end flows that the controller could setup in the dataplane. 530 This benchmark is obtained by sending traffic each with unique 531 source and destination pairs from the source Network Device. Program 532 the flows on controller's northbound interface for traffic to reach 533 from each of the unique source and destination pairs and determine 534 the number of frames received at the destination Network Device. 536 Measurement Units: 537 Paths provisioned per second. 539 See Also: 540 None 542 2.3.1.8. Network Topology Change Detection Time 544 Definition: 546 The amount of time required for the controller to detect any changes 547 in the network topology. 549 Discussion: 550 In order to for the controller to support fast network failure 551 recovery, it is critical to measure how fast the controller is able 552 to detect any network-state change events. This benchmark is 553 obtained by triggering a topology change event and measuring the 554 time controller takes to detect and initiate a topology re-discovery 555 process. 557 Measurement Units: 558 milliseconds 560 See Also: 561 None 563 2.3.2. Scalability 565 2.3.2.1. Control Sessions Capacity 567 Definition: 568 To measure the maximum number of control sessions the controller 569 can maintain. 571 Discussion: 572 Measuring the controller's control sessions capacity is important to 573 determine the controller's system and bandwidth resource 574 requirements. This benchmark is obtained by establishing control 575 session with the controller from each of the Network Device until it 576 fails. The number of sessions that were successfully established 577 will provide the Control Sessions Capacity. 579 Measurement Units: 580 N/A 582 See Also: 583 None 585 2.3.2.2. Network Discovery Size 587 Definition: 588 To measure the network size (number of nodes, links and hosts) that 589 a controller can discover. 591 Discussion: 593 For optimal network planning, it is key to measure the maximum 594 network size that the controller can discover. This benchmark is 595 obtained by presenting an initial set of Network Devices for 596 discovery to the controller. Based on the initial discovery, the 597 number of Network Devices is increased or decreased to determine the 598 maximum nodes that the controller can discover. 600 Measurement Units: 601 N/A 603 See Also: 604 None 606 2.3.2.3. Forwarding Table Capacity 608 Definition: 609 The maximum number of flow entries that a controller can manage in 610 its Forwarding table. 612 Discussion: 613 It is significant to measure the capacity of controller's Forwarding 614 Table to determine the number of flows that controller could forward 615 without flooding/dropping. This benchmark is obtained by 616 continuously presenting the controller with new flow entries through 617 reactive or proactive flow provisioning mode until the forwarding 618 table becomes full. The maximum number of nodes that the controller 619 can hold in its Forwarding Table will provide Forwarding Table 620 Capacity. 622 Measurement Units: 623 Maximum number of flow entries managed. 625 See Also: 626 None 628 2.3.3. Security 630 2.3.3.1. Exception Handling 632 Definition: 633 To determine the effect of handling error packets and notifications 634 on performance tests. 636 Discussion: 637 This benchmark test is to be performed after obtaining the baseline 638 performance of the performance tests defined in Section 2.3.1. This 639 benchmark determines the deviation from the baseline performance due 640 to the handling of error or failure messages from the connected 641 Network Devices. 643 Measurement Units: 644 N/A 646 See Also: 647 None 649 2.3.3.2. Denial of Service Handling 651 Definition: 652 To determine the effect of handling denial of service (DoS) attacks 653 on performance and scalability tests. 655 Discussion: 656 This benchmark test is to be performed after obtaining the baseline 657 performance of the performance and scalability tests defined in 658 section 2.3.1 and section 2.3.1.. This benchmark determines the 659 deviation from the baseline performance due to the handling of 660 denial of service attacks on controller. 662 Measurement Units: 663 Deviation of baseline metrics while handling Denial of Service 664 Attacks. 666 See Also: 667 None 669 2.3.4. Reliability 671 2.3.4.1. Controller Failover Time 673 Definition: 674 The time taken to switch from an active controller to the backup 675 controller, when the controllers work in redundancy mode and the 676 active controller fails. 678 Discussion: 679 This benchmark determine the impact of provisioning new flows when 680 controllers are teamed and the active controller fails. 682 Measurement Units: 683 milliseconds. 685 See Also: 686 None 688 2.3.4.2. Network Re-Provisioning Time 690 Definition: 691 The time taken to re-route the traffic by the Controller, when there 692 is a failure in existing traffic paths. 694 Discussion: 695 This benchmark determines the controller's re-provisioning ability 696 upon network failures. This benchmark test assumes the following: 697 i. Network topology supports redundant path between 698 source and destination endpoints. 699 ii. Controller does not pre-provision the redundant path. 701 Measurement Units: 702 milliseconds. 704 See Also: 705 None 707 3. Test Setup 709 This section provides common reference topologies that are later 710 referred to in individual tests defined in the companion methodology 711 document. 713 3.1. Test setup - Controller working in Standalone Mode 715 +-----------------------------------------------------------+ 716 | Application Plane Test Emulator | 717 | | 718 | +-----------------+ +-------------+ | 719 | | Application | | Service | | 720 | +-----------------+ +-------------+ | 721 | | 722 +-----------------------------+(I2)-------------------------+ 723 | 724 | 725 | (Northbound interface) 726 +-------------------------------+ 727 | +----------------+ | 728 | | SDN Controller | | 729 | +----------------+ | 730 | | 731 | Device Under Test (DUT) | 732 +-------------------------------+ 733 | (Southbound interface) 734 | 735 | 736 +-----------------------------+(I1)-------------------------+ 737 | | 738 | +-----------+ +-----------+ | 739 | | Network |l1 ln-1| Network | | 740 | | Device 1 |---- .... ----| Device n | | 741 | +-----------+ +-----------+ | 742 | |l0 |ln | 743 | | | | 744 | | | | 745 | +---------------+ +---------------+ | 746 | | Test Traffic | | Test Traffic | | 747 | | Generator | | Generator | | 748 | | (TP1) | | (TP2) | | 749 | +---------------+ +---------------+ | 750 | | 751 | Forwarding Plane Test Emulator | 752 +-----------------------------------------------------------+ 754 Figure 1 756 3.2. Test setup - Controller working in Cluster Mode 758 +-----------------------------------------------------------+ 759 | Application Plane Test Emulator | 760 | | 761 | +-----------------+ +-------------+ | 762 | | Application | | Service | | 763 | +-----------------+ +-------------+ | 764 | | 765 +-----------------------------+(I2)-------------------------+ 766 | 767 | 768 | (Northbound interface) 769 +---------------------------------------------------------+ 770 | | 771 | ------------------ ------------------ | 772 | | SDN Controller 1 | <--E/W--> | SDN Controller n | | 773 | ------------------ ------------------ | 774 | | 775 | Device Under Test (DUT) | 776 +---------------------------------------------------------+ 777 | (Southbound interface) 778 | 779 | 780 +-----------------------------+(I1)-------------------------+ 781 | | 782 | +-----------+ +-----------+ | 783 | | Network |l1 ln-1| Network | | 784 | | Device 1 |---- .... ----| Device n | | 785 | +-----------+ +-----------+ | 786 | |l0 |ln | 787 | | | | 788 | | | | 789 | +---------------+ +---------------+ | 790 | | Test Traffic | | Test Traffic | | 791 | | Generator | | Generator | | 792 | | (TP1) | | (TP2) | | 793 | +---------------+ +---------------+ | 794 | | 795 | Forwarding Plane Test Emulator | 796 +-----------------------------------------------------------+ 798 Figure 2 800 4. Test Coverage 802 + -----------------------------------------------------------------+ 803 | | Speed | Scalability | Reliability | 804 + -----------+-------------------+---------------+-----------------+ 805 | | 1. Network Topolo-|1. Network | | 806 | | -gy Discovery | Discovery | | 807 | | | Size | | 808 | | 2. Reactive Path | | | 809 | | Provisioning | | | 810 | | Time | | | 811 | | | | | 812 | | 3. Proactive Path | | | 813 | | Provisioning | | | 814 | Setup | Time | | | 815 | | | | | 816 | | 4. Reactive Path | | | 817 | | Provisioning | | | 818 | | Rate | | | 819 | | | | | 820 | | 5. Proactive Path | | | 821 | | Provisioning | | | 822 | | Rate | | | 823 | | | | | 824 +------------+-------------------+---------------+-----------------+ 825 | | 1. Asynchronous |1. Control |1. Network | 826 | | Message Proces-| Sessions | Topology | 827 | | -sing Rate | Capacity | Change | 828 | | | | Detection Time| 829 | | 2. Asynchronous |2. Forwarding | | 830 | | Message Proces-| Table |2. Exception | 831 | | -sing Time | Capacity | Handling | 832 | Operational| | | | 833 | | | |3. Denial of | 834 | | | | Service | 835 | | | | Handling | 836 | | | | | 837 | | | |4. Network Re- | 838 | | | | Provisioning | 839 | | | | Time | 840 | | | | | 841 +------------+-------------------+---------------+-----------------+ 842 | | | | | 843 | Tear Down | | |1. Controller | 844 | | | | Failover Time | 845 +------------+-------------------+---------------+-----------------+ 847 5. References 849 5.1. Normative References 851 [RFC7426] E. Haleplidis, K. Pentikousis, S. Denazis, J. Hadi Salim, 852 D. Meyer, O. Koufopavlou "Software-Defined Networking 853 (SDN): Layers and Architecture Terminology", RFC 7426, 854 January 2015. 856 [RFC4689] S. Poretsky, J. Perser, S. Erramilli, S. Khurana 857 "Terminology for Benchmarking Network-layer Traffic 858 Control Mechanisms", RFC 4689, October 2006. 860 [RFC2330] V. Paxson, G. Almes, J. Mahdavi, M. Mathis, 861 "Framework for IP Performance Metrics", RFC 2330, 862 May 1998. 864 [OpenFlow Switch Specification] ONF,"OpenFlow Switch Specification" 865 Version 1.4.0 (Wire Protocol 0x05), October 14, 2013. 867 [I-D.sdn-controller-benchmark-meth] Bhuvaneswaran.V, Anton Basil, 868 Mark.T, Vishwas Manral, Sarah Banks "Benchmarking 869 Methodology for SDN Controller Performance", 870 draft-ietf-bmwg-sdn-controller-benchmark-meth-01 871 (Work in progress), March 21, 2016 873 5.2. Informative References 875 [OpenContrail] Ankur Singla, Bruno Rijsman, "OpenContrail 876 Architecture Documentation", 877 http://opencontrail.org/opencontrail-architecture-documentation 879 [OpenDaylight] OpenDaylight Controller:Architectural Framework, 880 https://wiki.opendaylight.org/view/OpenDaylight_Controller 882 6. IANA Considerations 884 This document does not have any IANA requests. 886 7. Security Considerations 888 Security issues are not discussed in this memo. 890 8. Acknowledgements 892 The authors would like to acknowledge Al Morton (AT&T) for the 893 significant contributions to the earlier versions of this document. 894 The authors would like to thank the following individuals for 895 providing their valuable comments to the earlier versions of this 896 document: Sandeep Gangadharan (HP), M. Georgescu (NAIST), Andrew 897 McGregor (Google), Scott Bradner (Harvard University), Jay Karthik 898 (Cisco), Ramakrishnan (Dell), Khasanov Boris (Huawei). 900 9. Authors' Addresses 902 Bhuvaneswaran Vengainathan 903 Veryx Technologies Inc. 904 1 International Plaza, Suite 550 905 Philadelphia 906 PA 19113 908 Email: bhuvaneswaran.vengainathan@veryxtech.com 910 Anton Basil 911 Veryx Technologies Inc. 912 1 International Plaza, Suite 550 913 Philadelphia 914 PA 19113 916 Email: anton.basil@veryxtech.com 918 Mark Tassinari 919 Hewlett-Packard, 920 8000 Foothills Blvd, 921 Roseville, CA 95747 923 Email: mark.tassinari@hpe.com 925 Vishwas Manral 926 Nano Sec, 927 CA 929 Email: vishwas.manral@gmail.com 931 Sarah Banks 932 VSS Monitoring 934 Email: sbanks@encrypted.net