SDN Test Plans
The test plans on this page may be downloaded and used for internal purposes only. The test plans may not be commercialized in any way without express permission of the UNH-IOL.
The SDN testing service currently offers the following test plans. These documents are constantly being updated to improve readability and to reflect the current specifications. Please contact us if you would like more information or have questions about the SDN testing service.
When testing based on the following test plans is performed, all reports generated will be digitally signed using an Adobe digital certificate. Upon reception of the report, the recipient can verify its authenticity using our document validation instructions.
IOL
Certification
- Status
- Fully Documented (Active)
- Revision
- 1.0
- Testing Days Needed
- Last Modified
- 2014-10-21
- Abstract
- The OpenFlow specification is the first Software-Defined Networking (SDN) standard and a vital element of an open software-defined network architecture. The OpenFlow Conformance Certification for networking vendors demonstrates compliance with the OpenFlow™ specification for hardware such as switches and routers, as well as the network software.
- Status
- Fully Documented (Active)
- Revision
- NIST IPv6 Profile v1.0
- Testing Days Needed
- 5 days
- Last Modified
- 2010-01-25
- Abstract
- The UNH-IOL will offer OSPFv3 testing designed specifically for the USGv6 test program.
- Status
- Fully Documented (Active)
- Revision
- NIST IPv6 Profile v1.0
- Testing Days Needed
- 5 days
- Last Modified
- 2010-01-25
- Abstract
- The UNH-IOL will offer BGP4+ testing designed specifically for the USGv6 test program.
Conformance
- Status
- Under Development
- Revision
- 1.0
- Testing Days Needed
- Last Modified
- 2020-06-01
- Abstract
- This Test Plan describes a set of tests to exercise either the Sender or Receiver role of the DCTCP. These tests are designed to be run using a packet generator/protocol analyzer against an isolated DUT (Device, or implementation, Under Test).
- Status
- Fully Documented (Active)
- Revision
- 3.7
- Testing Days Needed
- 5 days
- Last Modified
- 2009-02-27
- Abstract
- The Border Gateway Protocol (BGP) is an inter-Autonomous System routing protocol. The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This includes information on the list of Autonomous Systems (ASs) that reachability information traverses. From this, a graph of AS connectivity is constructed from which routing loops may be pruned and some policy decisions at the AS level may be enforced.
- Status
- Fully Documented (Active)
- Revision
- 2.9
- Testing Days Needed
- 5 days
- Last Modified
- 2008-07-21
- Abstract
- OSPF is a link-state routing protocol. It is designed to be run internal to a single Autonomous System. Each OSPF router maintains an identical database describing the Autonomous System's topology. From this database, a routing table is calculated by constructing a shortest-path tree.
- Status
- Fully Documented (Active)
- Revision
- 1.9
- Testing Days Needed
- 5 days
- Last Modified
- 2004-12-18
- Abstract
- An OSPF NSSA is an optional type of OSPF area that has the capability of importing external routes into a designated OSPF area. The NSSA area has a new option bit (the N-bit) and a new type of LSA (Type-7). This is an optional test suite that can be tested as an extension to our OSPF Operations Test Suite.
- Status
- Under Development
- Revision
- 4.6
- Testing Days Needed
- 5 days
- Last Modified
- 2009-01-12
- Abstract
- IS-IS is a Link State Protocol. IS-IS systems form adjacencies with other systems in the same Area (Level-1), Domain (Level-2), or both to build Link State Databases where network and neighbor topology information is stored. Dijkstra Shortest Path First algorithm is then used to create a Forwarding Information Database containing routing information learned through IS-IS.
- Status
- Fully Documented (Active)
- Revision
- 4.4
- Testing Days Needed
- 5 days
- Last Modified
- 2005-09-01
- Abstract
- RIP is a routing protocol based on the Bellman-Ford (or distance vector) algorithm. This algorithm has been used for routing computations in computer networks since the early days of the ARPANET.
- Status
- Fully Documented (Active)
- Revision
- 2.0
- Testing Days Needed
- 5 days
- Last Modified
- 2004-01-30
- Abstract
- This suite of tests is intended to help implementers evaluate the functionality of their products that support RIPng, the next generation routing information protocol. This suite is designed to test interoperability of the device under test with other RIPng capable devices. These tests cover RFCs 2080 and 2460.
- Status
- Fully Documented (Active)
- Revision
- 2.4
- Testing Days Needed
- 5 days
- Last Modified
- 2006-06-06
- Abstract
- PIM-SM is a multicast routing protocol that uses an underlying topology-gathering unicast protocol to populate a routing table with routes; it is independent of which protocol is actually used. In Sparse Mode, the number of routers with attached group members is small with respect to the total number of routers; group members are widely dispersed. PIM-SM is often deployed in Multicast WAN scenarios.
- Status
- Fully Documented (Active)
- Revision
- 2.4
- Testing Days Needed
- 5 days
- Last Modified
- 2006-04-11
- Abstract
- VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IP address(es) associated with a virtual router is called the Master, and forwards packets sent to these IP addresses. The election process provides dynamic fail over in the forwarding responsibility should the Master become unavailable. This allows any of the virtual router IP addresses on the LAN to be used as the default first hop router by end-hosts.
Interoperability
- Status
- Draft (Active)
- Revision
- 0.3
- Testing Days Needed
- 5 days
- Last Modified
- 2014-05-08
- Abstract
- VRRPv3 specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRPv3 routers on a LAN. The VRRPv3 router controlling the IP address(es) associated with a virtual router is called the Master, and forwards packets transmitted to these IP addresses. The election process provides dynamic fail over in the forwarding responsibility should the Master become unavailable. This allows any of the virtual router IP addresses on the LAN to be used as the default first hop router by end-hosts. The advantage gained from using VRRPv3 is a higher availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host.
- Status
- Fully Documented (Active)
- Revision
- 1.0
- Testing Days Needed
- 5 days
- Last Modified
- 2009-09-23
- Abstract
- This test suite is a forward looking test suite for the USGv6 test program. This suite of tests is also intended to help implementers evaluate the functionality of their products that support IPv6. The following IETF documents are covered: RFC 3810 and 4606.
- Status
- Fully Documented (Active)
- Revision
- 1.0
- Testing Days Needed
- 5 Days
- Last Modified
- 2006-09-20
- Abstract
- This suite of tests has been developed to help implementers evaluate the functioning of their Border Gateway Protocol 4 (from now on referred to as BGP) products. This test suite has been designed to test interoperability of a device under test with other BGP based products. This test suite focuses on testing configurations of the network that could cause problems when deployed if the device under test does not operate properly with the devices that it is connected to. The tests do not determine if a product conforms to the BGP specification, but they are designed as interoperability tests. These tests provide one method to isolate problems within the BGP capable device that will affect the interoperability performance. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other BGP capable devices. However, these tests do provide a reasonable level of confidence that the RUT will function well in most BGP environments.
- Status
- Fully Documented (Active)
- Revision
- 1.6
- Testing Days Needed
- 5 days
- Last Modified
- 2008-09-09
- Abstract
- This suite of tests has been developed to help implementers evaluate the functionality of their products that support OSPF. This test suite focuses on testing the Interoperability of the DUT with other OSPF devices. The tests do not determine if a product conforms to the specifications that define OSPF, but they are designed as interoperability tests. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with all other OSPF devices in any scenario. However, these tests provide a reasonable level of confidence that the DUT will function well in most OSPF environments.
- Status
- Fully Documented (Active)
- Revision
- 2.2
- Testing Days Needed
- 5 days
- Last Modified
- 2006-12-01
- Abstract
- This suite of tests has been developed to help implementers evaluate the functionality of their products that support RIP. This test suite focuses on testing the Interoperability the DUT with other RIP devices. The tests do not determine if a product conforms to the specifications that define RIP, but they are designed as interoperability tests. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with all other RIP devices in any scenario. However, these tests provide a reasonable level of confidence that the DUT will function well in most RIP environments.
- Status
- Fully Documented (Active)
- Revision
- 2.1
- Testing Days Needed
- 5 days
- Last Modified
- 2007-03-12
- Abstract
- This suite of tests is intended to help implementers evaluate the functionality of their products that support RIPng, the next generation routing information protocol. This suite is designed to test interoperability of the device under test with other RIPng capable devices. These tests cover RFCs 2080 and 2460.
- Status
- Fully Documented (Active)
- Revision
- 1.5
- Testing Days Needed
- 5 days
- Last Modified
- 2008-08-27
- Abstract
- This suite of tests has been developed to help implementers evaluate the functionality of their products that support PIM-SM. This test suite focuses on testing the Interoperability between the Device Under Test with other PIM-SM devices. The tests do not determine if a product conforms to the specifications that define PIM-SM, but they are designed as interoperability tests. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with all other PIM-SM devices in any scenario. However, these tests provide a reasonable level of confidence that the DUT will function well in most PIM-SM environments.
- Status
- Fully Documented (Active)
- Revision
- 1.5
- Testing Days Needed
- 5 Days
- Last Modified
- 2008-08-27
- Abstract
- This suite of tests is intended to help implementers evaluate the functionality of their products that support PIM-SM. This suite is designed to test interoperability of the device under test with other PIM-SM capable devices. These tests cover RFCs 4606 and 3810.
Key
| Fully Documented |
| Draft |