etsi test specifications for ipv6 protocols ocg#23 16-17 june 2004, sophia antipolis
DESCRIPTION
ETSI Test Specifications for IPv6 Protocols OCG#23 16-17 June 2004, Sophia Antipolis. Steve Randall Dieter Hogrefe Anthony Wiles. EC/EFTA Funded IPv6 Testing. Introduction to MTS-IPT IPv6 Testing Project Overview Past Present Future Issues related to the IPv6 Testing Project - PowerPoint PPT PresentationTRANSCRIPT
Steve Randall
Dieter Hogrefe
Anthony Wiles
ETSI Test Specifications for IPv6 Protocols
OCG#2316-17 June 2004, Sophia Antipolis
ETSI OCG#23 June 2004 2
EC/EFTA Funded IPv6 Testing
Introduction to MTS-IPT IPv6 Testing Project Overview
Past Present Future
Issues related to the IPv6 Testing Project
Meeting the needs of other TBs Funding
ETSI OCG#23 June 2004 3
ETSI TC-MTS IP Testing Group (IPT)
Mandate to develop generic test specifications
IPT main focus
Methodologies and techniques for IP testing
Development of test specifications for IP and IP-related technologies
ETSI OCG#23 June 2004 4
IPv6 Testing Project
Project Overview
ETSI OCG#23 June 2004 5
Project Overview ETSI Testing IPv6 - Why?!
Response to ETSI members’ needs
To satisfy the European Commission’s mandate
To add value to the IPv6 Forum’s label program “IPv6 Ready”
ETSI OCG#23 June 2004 6
Project Overview ETSI Members’ Needs
Provide publicly available, no-cost, standardized IPv6 test specifications in a standard testing language based upon:
RFC requirements Industry practice requirements Other requirements (ETSI-specific, IPv6 logo-specific)
Provide a framework for efficient development within ETSI of future IPv6 test specifications such as 3G and NGN
Note: This project will not write 3G or NGN test suites
ETSI OCG#23 June 2004 7
Project Overview The European Commission’s Mandate
Complement IPv6-dependent initiatives for e-Government, e-Business, e-Health, e-Learning, and e-Procurement
Provide a key element in ensuring deployment, interoperability, security, and reliability of the IPv6 infrastructure;
Provide an even stronger European representation in the IPv6 Forum’s “IPv6 Ready” label program
ETSI OCG#23 June 2004 8
Project Overview Adding Value to “IPv6 Ready” Program
Publicly available, no-cost, standardized test specifications that the user can extend
Interoperability and conformance tests for both mandatory and optional requirements
Flexible basis on which specific testing implementations can be built
ETSI OCG#23 June 2004 9
Project OverviewEC/EFTA Funding
Project proposal submitted by MTS under eEurope program
50/50 funding ETSI – EC/EFTA
Member States and DG Information Society have expressed their strong support
ETSI OCG#23 June 2004 10
Project Overview Five Work Packages
WP 1: IPv6 TTCN-3 Test Development Framework WP 2: IPv6 Core test specifications
WP 3: IPv6 IPv6 Security (IPSEC) test specifications WP 4: IPv6 IPv6 Mobility test specifications WP 5: IPv6 IPv6 Transitioning test specifications
ETSI OCG#23 June 2004 11
Project OverviewIPv6 Project Timeline
September March September March September
2004 2005 2006
STF256 WP1: Framework
WP2: Core
WP3: Security
WP4: Mobility
WP5: Transitioning
ETSI OCG#23 June 2004 12
IPv6 Project IssuesMeeting the Needs of Others
Output of the project will be: a “library” of testing specifications a development framework within which library
modules can be used to build specific test suites a mechanism for selecting and characterizing tests
Inputs to the project will be: IETF RFCs Generic requirements of 3GPP and ETSI TBs
interested in IPv6 Current industry practice Interests and experience of the IPv6 Forum
ETSI OCG#23 June 2004 13
IPv6 Project IssuesFunding
EC/EFTA expects ETSI’s 50% to include technical effort as well as meeting time
For good project management, this effort must be given as STF Expert time
MTS fortunate to have significant voluntary expert time offered by its members for first two Work Packages
Future eEurope projects may need to ask for funds from FWP
ETSI OCG#23 June 2004 14
Points for Further Discussion
What is the basis for asking for future EC/EFTA funding? Do we take EC funds as a sub-contractor purely to
satisfy EC needs? or Do we seek co-funding from the EC for projects which
are of specific interest to ETSI?
If the latter, how will we fund the 50% contribution that ETSI will be expected to make? Purely voluntary effort? FWP/PTCC? Other?