draft-ietf-bmwg-sdn-controller-benchmark-term-03.txt   draft-ietf-bmwg-sdn-controller-benchmark-term-04.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: June 8, 2017 Mark Tassinari Expires: December 29, 2017 Mark Tassinari
Hewlett-Packard Hewlett-Packard
Vishwas Manral Vishwas Manral
Nano Sec Nano Sec
Sarah Banks Sarah Banks
VSS Monitoring VSS Monitoring
January 8, 2017 June 29, 2017
Terminology for Benchmarking SDN Controller Performance Terminology for Benchmarking SDN Controller Performance
draft-ietf-bmwg-sdn-controller-benchmark-term-03 draft-ietf-bmwg-sdn-controller-benchmark-term-04
Abstract Abstract
This document defines terminology for benchmarking an SDN This document defines terminology for benchmarking an SDN
controller's control plane performance. It extends the terminology controller's control plane performance. It extends the terminology
already defined in RFC 7426 for the purpose of benchmarking SDN already defined in RFC 7426 for the purpose of benchmarking SDN
controllers. The terms provided in this document help to benchmark controllers. The terms provided in this document help to benchmark
SDN controller's performance independent of the controller's SDN controller's performance independent of the controller's
supported protocols and/or network services. A mechanism for supported protocols and/or network services. A mechanism for
benchmarking the performance of SDN controllers is defined in the benchmarking the performance of SDN controllers is defined in the
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 June 8, 2017. This Internet-Draft will expire on December 29, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 4, line 19 skipping to change at page 4, line 19
function and is placed in a centralized location called the SDN function and is placed in a centralized location called the SDN
controller. The SDN controller abstracts the underlying network and controller. The SDN controller abstracts the underlying network and
offers a global view of the overall network to applications and offers a global view of the overall network to applications and
business logic. Thus, an SDN controller provides the flexibility to business logic. Thus, an SDN controller provides the flexibility to
program, control, and manage network behaviour dynamically through program, control, and manage network behaviour dynamically through
standard interfaces. Since the network controls are logically standard interfaces. Since the network controls are logically
centralized, the need to benchmark the SDN controller performance centralized, the need to benchmark the SDN controller performance
becomes significant. This document defines terms to benchmark becomes significant. This document defines terms to benchmark
various controller designs for performance, scalability, reliability various controller designs for performance, scalability, reliability
and security, independent of northbound and southbound protocols. and security, independent of northbound and southbound protocols.
The methodologies are defined in [I-D.sdn-controller-benchmark-meth].
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. Term Definitions 2. Term Definitions
2.1. SDN Terms 2.1. SDN Terms
The terms defined in this section are extensions to the terms The terms defined in this section are extensions to the terms
defined in RFC 7426 "Software-Defined Networking (SDN): Layers and defined in [RFC7426] "Software-Defined Networking (SDN): Layers and
Architecture Terminology". This RFC should be referred before Architecture Terminology". This RFC should be referred before
attempting to make use of this document. attempting to make use of this document.
2.1.1. Flow 2.1.1. Flow
Definition: Definition:
The definition of Flow is same as microflows defined in RFC 4689 The definition of Flow is same as microflows defined in [RFC4689]
Section 3.1.5. Section 3.1.5.
Discussion: Discussion:
A flow can be set of packets having same source address, destination A flow can be set of packets having same source address, destination
address, source port and destination port, or any of these address, source port and destination port, or any of these
combinations. combinations.
Measurement Units: Measurement Units:
N/A N/A
See Also: See Also:
None None
2.1.2. Northbound Interface 2.1.2. Northbound Interface
Definition: Definition:
The definition of northbound interface is same Service Interface The definition of northbound interface is same Service Interface
defined in RFC 7426. defined in [RFC7426].
Discussion: Discussion:
The northbound interface allows SDN applications and orchestration The northbound interface allows SDN applications and orchestration
systems to program and retrieve the network information through the systems to program and retrieve the network information through the
SDN controller. SDN controller.
Measurement Units: Measurement Units:
N/A N/A
See Also: See Also:
skipping to change at page 6, line 33 skipping to change at page 6, line 33
Measurement Units: Measurement Units:
N/A N/A
See Also: See Also:
None None
2.1.6. Path 2.1.6. Path
Definition: Definition:
Refer to Section 5 in RFC 2330. Refer to Section 5 in [RFC2330].
Discussion: Discussion:
None None
Measurement Units: Measurement Units:
N/A N/A
See Also: See Also:
None None
skipping to change at page 21, line 24 skipping to change at page 21, line 24
January 2015. January 2015.
[RFC4689] S. Poretsky, J. Perser, S. Erramilli, S. Khurana [RFC4689] S. Poretsky, J. Perser, S. Erramilli, S. Khurana
"Terminology for Benchmarking Network-layer Traffic "Terminology for Benchmarking Network-layer Traffic
Control Mechanisms", RFC 4689, October 2006. Control Mechanisms", RFC 4689, October 2006.
[RFC2330] V. Paxson, G. Almes, J. Mahdavi, M. Mathis, [RFC2330] V. Paxson, G. Almes, J. Mahdavi, M. Mathis,
"Framework for IP Performance Metrics", RFC 2330, "Framework for IP Performance Metrics", RFC 2330,
May 1998. May 1998.
[OpenFlow Switch Specification] ONF,"OpenFlow Switch Specification"
Version 1.4.0 (Wire Protocol 0x05), October 14, 2013.
[I-D.sdn-controller-benchmark-meth] Bhuvaneswaran.V, Anton Basil, [I-D.sdn-controller-benchmark-meth] Bhuvaneswaran.V, Anton Basil,
Mark.T, Vishwas Manral, Sarah Banks "Benchmarking Mark.T, Vishwas Manral, Sarah Banks "Benchmarking
Methodology for SDN Controller Performance", Methodology for SDN Controller Performance",
draft-ietf-bmwg-sdn-controller-benchmark-meth-03 draft-ietf-bmwg-sdn-controller-benchmark-meth-04
(Work in progress), January 8, 2017 (Work in progress), June 8, 2017
5.2. Informative References 5.2. Informative References
[OpenContrail] Ankur Singla, Bruno Rijsman, "OpenContrail [OpenFlow Switch Specification] ONF,"OpenFlow Switch Specification"
Architecture Documentation", Version 1.4.0 (Wire Protocol 0x05), October 14, 2013.
http://opencontrail.org/opencontrail-architecture-documentation
[OpenDaylight] OpenDaylight Controller:Architectural Framework,
https://wiki.opendaylight.org/view/OpenDaylight_Controller
6. IANA Considerations 6. IANA Considerations
This document does not have any IANA requests. This document does not have any IANA requests.
7. Security Considerations 7. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
8. Acknowledgements 8. Acknowledgements
skipping to change at page 22, line 45 skipping to change at page 22, line 45
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@hpe.com Email: mark.tassinari@hpe.com
Vishwas Manral Vishwas Manral
Nano Sec, Nano Sec,CA
CA
Email: vishwas.manral@gmail.com Email: vishwas.manral@gmail.com
Sarah Banks Sarah Banks
VSS Monitoring VSS Monitoring
Email: sbanks@encrypted.net Email: sbanks@encrypted.net
 End of changes. 16 change blocks. 
23 lines changed or deleted 16 lines changed or added

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