The University of New Hampshire is investing a lot in projects of creating an environment where every product can be tested. Practically this is implementing of standards and observing how Internet Protocol will behave, especially new version 6 or MPLS Provider Edge IPv6. The main purpose of the test it to isolate the problems within a device.
The University of New Hampshire’s work and experts
The University of New Hampshire would like to acknowledge the efforts of the following individuals in the development of this test suite. This test suite belongs to the University of New Hampshire InterOperability Lab and is a collaborative effort of those listed below and the participants of Moonv6. Special thanks to France Telecom for the base test items.
Overview of New Hampshire’s work
The University of New Hampshire’s InterOperability Laboratory (IOL) is an institution designed to improve the interoperability of standards-based products by providing an environment where a product can be tested against other implementations of a standard. This suite of tests has been developed to help implementers evaluate the functioning of their Internet Protocol, version 6 MPLS Provider Edge IPv6 capable products. The tests do not determine if a product conforms to the IPv6 or MPLS specifications, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within a device. Successful completion of all tests contained in this suite does not guarantee that the tested device will interoperate with other IPv6 devices. However, combined with satisfactory operation in the IOL’s semi-production environment, these tests provide a reasonable level of confidence that the Device Under Test will function well in many multi-vendor IPv6 environments. Most will recommend 100 traffic.
Testing is very important in every field and this even more because software usually behaves differently with mock and real data.
RUT: Router Under Test RT: Route Target TR: Testing Router
RD: Route Distinguisher G: Traffic Generator
When several entities of the same type are present in a test configuration, a number is appended to the acronym to yield a label for each entity. For example, if there were three testing routers in the test configuration, they would be labeled G1, G2, and G3.