Specialist Task Force 320: Upgrading and maintenance of IPv6 test specifications

Who we are:

Team Leader: Steve Randall
Team Members: Alexandre Berge  
Peter Schmitting

What we do :

The purpose of this STF is to update and maintain the MTS IP Library components for IPv6 with respect to the Requirements Catalogue and the test specifications according to change requests received by TC MTS.

 The maintenance concerns the Requirements Catalogue (see task 1 and task 2 in clause 3.1.1), the conformance, and possibly the interoperability tests cases (see tasks 3 and 4 in clause 3.1.1). See annex A for description of the requested changes to date. More are anticipated before the STF starts work in 2007.

 In addition to the straightforward maintenance activities within this project, extensive user documentation for the conformance test specifications (task 3), not included during the IPv6 Phase 1 project, will be produced, as well as a minimum maintenance of the existing database structure developed to use a state of the art database as storage medium for the IPv6 Phase 1data (task 5).

Read our Terms of Reference

Why we do it:

These IPv6 Phase 1 test specifications are now being used by the stakeholders and have been submitted to the IPv6 Forum. Effective conformance and IOP testing of IPv6 is becoming ever more important as ETSI dependence on technologies such as IMS increases.

It is essential that this work is done in a timely manner in order to address requests for upgrades from the users of the test suites. It is also necessary to synchronise with global testing activities and especially in the context of IMS (3GPP and TISPAN NGN). The expertise needed is specialised and should build on that already provided in earlier STFs.

We are now faced with the maintenance of this work, which is necessary to maintain its usefulness.

Time plan for the work:

Start: January 2007
Duration: 11 months
Conclusion: December 2007

How to contact us:

If you would like more information, please contact the STF Leader: Laurent.vreck@etsi.org

Note: this information is based upon STF working assumptions.
The views expressed do not necessarily represent the position of ETSI in this context.