Oblivious Pseudorandom Functions (OPRFs) using Prime-Order Groups
draft-sullivan-cfrg-voprf-03
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2019-07-21
|
03 | Alexey Melnikov | Set stream state to Replaced |
2019-07-03
|
03 | Kenny Paterson | Adopted by CFRG as a work item, July 3rd 2019. |
2019-07-03
|
03 | Kenny Paterson | IRTF state changed to Active RG Document from Candidate RG Document |
2019-05-23
|
03 | Nick Sullivan | IRTF state changed to Candidate RG Document |
2019-05-23
|
03 | Nick Sullivan | Notification list changed to none |
2019-05-23
|
03 | Nick Sullivan | Changed group to Crypto Forum (CFRG) |
2019-05-23
|
03 | Nick Sullivan | Changed stream to IRTF |
2019-03-11
|
03 | Alex Davidson | New version available: draft-sullivan-cfrg-voprf-03.txt |
2019-03-11
|
03 | (System) | New version approved |
2019-03-11
|
03 | (System) | Request for posting confirmation emailed to previous authors: Christopher Wood , Alex Davidson , Nick Sullivan |
2019-03-11
|
03 | Alex Davidson | Uploaded new revision |
2019-03-11
|
03 | (System) | Internet-Draft Bhuvaneswaran Vengainathan Network Working Group … Internet-Draft Bhuvaneswaran Vengainathan Network Working Group Anton Basil Intended Status: Informational Veryx Technologies Expires: April 18, 2016 Mark Tassinari Hewlett-Packard Vishwas Manral Ionos Corp Sarah Banks VSS Monitoring October 19, 2015 Terminology for Benchmarking SDN Controller Performance draft-ietf-bmwg-sdn-controller-benchmark-term-00 Abstract This document defines terminology for benchmarking an SDN Controller's performance. The terms provided in this document help to benchmark SDN controller's performance independent of the controller's supported protocols and/or network services. A mechanism for benchmarking the performance of SDN controllers is defined in the companion methodology document. These two documents provide a standard mechanism to measure and evaluate the performance of various controller implementations. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress. This Internet-Draft will expire on April 18, 2016. Bhuvan, et al Expires April 18, 2016 [Page 1] Internet-Draft SDN Controller Benchmarking Terminology October 2015 Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ................................................ 3 2. Term Definitions ............................................ 4 2.1. SDN Terms .............................................. 4 2.1.1. SDN Node .......................................... 4 2.1.2. SDN Application ................................... 4 2.1.3. Flow .............................................. 4 2.1.4. Northbound Interface .............................. 5 2.1.5. Southbound Interface .............................. 5 2.1.6. Controller Forwarding Table ....................... 5 2.1.7. Proactive Flow Provisioning Mode .................. 6 2.1.8. Reactive Flow Provisioning Mode ................... 6 2.1.9. Path .............................................. 7 2.1.10. Standalone Mode .................................. 7 2.1.11. Cluster/Redundancy Mode .......................... 7 2.1.12. Asynchronous Message ............................. 8 2.1.13. Test Traffic Generator ........................... 8 2.2. Test Configuration/Setup Terms ......................... 9 2.2.1. Number of SDN Nodes ............................... 9 2.2.2. Test Iterations ................................... 9 2.2.3. Test Duration ..................................... 9 2.2.4. Number of Cluster nodes ........................... 10 2.3. Benchmarking Terms ..................................... 10 2.3.1. Performance ....................................... 10 2.3.1.1. Network Topology Discovery Time .............. 10 2.3.1.2. Asynchronous Message Processing Time.......... 11 2.3.1.3. Asynchronous Message Processing Rate.......... 11 2.3.1.4. Reactive Path Provisioning Time .............. 12 2.3.1.5. Proactive Path Provisioning Time ............. 12 Bhuvan, et al Expires April 18, 2016 [Page 2] Internet-Draft SDN Controller Benchmarking Terminology October 2015 2.3.1.6. Reactive Path Provisioning Rate .............. 13 2.3.1.7. Proactive Path Provisioning Rate ............. 13 2.3.1.8. Network Topology Change Detection Time ....... 13 2.3.2. Scalability ....................................... 14 2.3.2.1. Control Sessions Capacity .................... 14 2.3.2.2. Network Discovery Size ....................... 14 2.3.2.3. Forwarding Table Capacity .................... 15 2.3.3. Security ......................................... 15 2.3.3.1. Exception Handling ........................... 15 2.3.3.2. Denial of Service Handling ................... 16 2.3.4. Reliability ....................................... 16 2.3.4.1. Controller Failover Time ..................... 16 2.3.4.2. Network Re-Provisioning Time ................. 17 3. Test Coverage .............................................. 17 4. References ................................................. 18 4.1. Normative References ................................... 18 4.2. Informative References ................................. 19 5. IANA Considerations ........................................ 19 6. Security Considerations ..................................... 19 7. Acknowledgements ........................................... 19 8. Authors' Addresses ......................................... 19 1. Introduction Software Defined Networking (SDN) is a networking architecture in which network control is decoupled from the underlying forwarding function and is placed in a centralized location called the SDN controller. The SDN controller abstracts the underlying network and offers a global view of the overall network to applications and business logic. Thus, an SDN controller provides the flexibility to program, control, and manage network behaviour dynamically through standard interfaces. Since the network controls are logically centralized, the need to benchmark the SDN controller performance becomes significant. This document defines terms to benchmark various controller designs for performance, scalability, reliability and security, independent of northbound and southbound protocols. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Bhuvan, et al Expires April 18, 2016 [Page 3] Internet-Draft SDN Controller Benchmarking Terminology October 2015 2. Term Definitions 2.1. SDN Terms 2.1.1. SDN Node Definition: An SDN node is a simulated/emulated entity that forwards data in a software defined environment. Discussion: An SDN node can be an emulated/simulated switch, router, gateway, or any network service appliance that supports standardized or proprietary programmable interface. Measurement Units: N/A See Also: None 2.1.2. SDN Application Definition: Any business logic that alter the network behaviour dynamically through controller&Request for posting confirmation emailed to previous authors: Christopher Wood , Alex Davidson , Nick Sullivan |
2019-03-11
|
03 | Alex Davidson | Uploaded new revision |
2018-11-03
|
02 | Alexey Melnikov | Added to session: IETF-103: cfrg Mon-1120 |
2018-10-22
|
02 | Christopher Wood | New version available: draft-sullivan-cfrg-voprf-02.txt |
2018-10-22
|
02 | (System) | New version approved |
2018-10-22
|
02 | (System) | Request for posting confirmation emailed to previous authors: Christopher Wood , Alex Davidson , Nick Sullivan |
2018-10-22
|
02 | Christopher Wood | Uploaded new revision |
2018-07-02
|
01 | Nick Sullivan | New version available: draft-sullivan-cfrg-voprf-01.txt |
2018-07-02
|
01 | (System) | New version approved |
2018-07-02
|
01 | (System) | Request for posting confirmation emailed to previous authors: Christopher Wood , Nick Sullivan |
2018-07-02
|
01 | Nick Sullivan | Uploaded new revision |
2018-03-05
|
00 | Christopher Wood | New version available: draft-sullivan-cfrg-voprf-00.txt |
2018-03-05
|
00 | (System) | New version approved |
2018-03-05
|
00 | Christopher Wood | Request for posting confirmation emailed to submitter and authors: Christopher Wood , Nick Sullivan |
2018-03-05
|
00 | Christopher Wood | Uploaded new revision |