MTS/RAN5 IMS/IPv6 Workshop October 11th 2005 IPv6 Test Specifications Anthony Wiles, ETSI PTCC Leader of MTS STF276

MTS IPv6 Testing Activities STF 276 MTS project – part of the MTS-IPT program Led by PTCC on behalf of TC MTS Funded by eEurope But no technical influence Significant voluntary expert contribution by ETSI members (at least 140 days in 2005) Phase 1: Jan – Dec 2005 IPv6 core RFCs Phase 2: Jan – Dec 2006 IP SEC IPv6 Mobility IPv4-IPv6 Transitioning Aligned with the IPv6 Logo Program For more info visit: www.ipt.etsi.org

STF 276 Outputs IPv6 Testing Framework Core IPv6 IPv6 Requirements Catalogue Conformance TSS&TP Conformance TTCN-3 Test Suite TTCN-3 Library Updated Requirements Catalogue and Conformance test specs in phase 2 for IPSEC IPv6 Mobility IPv4-IPv6 Transitioning Also writing interoperability test specs For all the above protocols

RFCs for ‘Core IPv6’ RFC2460: IPv6 Basic Specification RFC2461: Neighbor Discovery & Redirect RFC2462 Stateless Address Autoconfiguration RFC2463: ICMPv6 RFC1981: Path MTU Discovery RFC2675: IPv6 Jumbograms RFC2373: IPv6 Addressing Architecture

IPv6 Testing Framework Process similar to ISO 9646 but adapted for IPv6 e.g., Instead of PICS we have the Requirements Catalogue Handles IOP testing as well as conformance testing Relationship between Requirements, TPs, TCs etc. Defines a semi-formal language for TPs Not mandatory to use Naming conventions On the Requirement, TP and TC level On the TTCN-3 level Requirements on the TTCN-3 libray Structure Adding new modules Documentation rules

The Requirements Catalogue Sources are mainly IETF RFCs but include Industry Practice, IPv6 Forum, 3GPP etc. Source is clearly identified Phase 1 has 6 RFCs, 200 pages of specification containing approximately 1,000 requirements Requirements types: MUST, SHOULD, MAY, NOTs Provides links between requirement source and resulting test purpose and test case/description Group of requirements may be spread across several documents Three requirements subjects: Node, Host, and Router

The Requirements Catalogue (cont’d) A scalable database containing all requirement elements HTML view of selected database elements HTML links between RFC, requirement, test purpose, and test case/description Mapping between RFC and IPv6 Logo requirements Mapping between RFC and 3GPP requirement

The Requirements Catalogue Online

Conformance TSS&TP For Core IPv6 404 Test Purposes identified from the requirements catalogue Of which 131 were shown to be not testable Written in TPLan (defined in the Framework) Keywords and syntax provide clear and consistent structure Keywords chosen for communications applications (sends, receives etc.) Text between keywords not part of syntax so free expression possible A TP’s basic structure (corresponding keyword): Header (TP id) Pre-conditions (with) Stimulus (when) Expected response (then)

TPLan Example for Conformance TP id : TP_COR_0047_01 Summary : ‘hop limit of one' RQ Ref : RQ_COR_0047 Config : CF_02_C TC Ref : TC_COR_0047_01 ensure that { --Stimulus when { IUT receives ‘Ipv6 packet' from ‘HS' containing ‘IPv6 Header' indicating ‘Hop limit' set to ‘1‘ } --Expected response then { IUT sends ‘ICMPv6 Time Exceeded' to ‘HS‘ containing ‘ICMP code' set to ‘ZERO‘ } }

Conformance Test Cases 404 potential Test Purposes identified from the requirements catalogue Of which 131 were shown to be not testable 273 TTCN-3 Test Cases written Approx. 100 have been fully validated (as of 14/10) All 273 Test Cases expected to be validated by the end of 2005 No test cases written for the (explicit) 3GPP requirements

Example TTCN-3 Test Case testcase TC_COR_0047_01() runs on Ipv6Node system EtherNetAdapter { f_cf02Up(); // Configure test system for HS->RT // No preamble required in this case f_TP_HopsSetToOne(); // Perform test // No postamble required in this case f_cf02Down(); // Return test system to initial state } function f_TP_HopsSetToOne() runs on Ipv6Node { var Ipv6Packet v_ipPkt; var FncRetCode v_ret := f_echoTimeExceeded( 1, v_ipPkt ); if ( v_ret == e_success and v_ipPkt.icmpCode == 0 ) { setverdict(pass);} else { setverdict(fail); } function f_echoTimeExceeded(in UInt8 p_hops, out Ipv6Packet p_ípPkt ) runs on Ipv6Node return FncRetCode { var Ipv6Packet v_ipPacket; var FncRetCode v_ret; ipPort.send( m_echoReqWithHops(p_hops) ); alt { [] ipPort.receive( mw_anyTimeExceeded ) -> value p_ipPkt { return e_success } [] ipPort.receive { return e_error } }

SSH (secured remote control) control network  IPv4 @ only Test networks  IPv6 @ only Validation Platform Internet (IPv4) SSH (secured remote control) ETSIHQ 172.27.x.x CUxxx Oleane .17 172.27.1.1 .252 .57 .253 UUnet ETSI_ONLINE FW Open Source Op. Syst. FreeBSD Fedora Core Linux RedHat Linux Remote controllable Secure (Private key + Pwd) Validation can be done locally and remotely 212.234.161.x Mask: 255.255.255.0 PLUGTESTS 212.234.161.1 217.167.116.1 ETSI_PUBLIC 212.234.160.x PF1000: 2001:660:5503:1000 /64 PF6: 2001:660:5503:6 /64 FErouter1 Fedora core 3 Ns6.etsi.org R 6Wind meeting ::6 2Mb inrias ::2 renaters ::1 PF3000 IPv6 RHhost2 Linux Redhat ES4 + TTCN-3 tools RHhost3 Linux Redhat ES4 + TTCN-3 tools FBrouter5 FreeBSD 5.3 FBrouter4 FreeBSD 5.3 A PF276a: 2001:660:5503:276a /64 PF276b: 2001:660:5503:276b /64 B

TTCN-3 Result Visualisation

TTCN-3 Graphical Logging

Test Report Generation

Conformance Tester Architecture Lower Tester Only Test System (LT) IPv6 SUT TTCN-3 Test Case Main Test Component IPv6 IUT TRI IPv6 Transport SUT Adapter IPv6 Transport

Conformance Tester Architecture Lower Tester and Upper Tester Test System IPv6 SUT TTCN-3 Test Case Upper Tester Server Main Test Component Upper Tester Client IPv6 Test Component IPv6 IUT TRI IPv6 Transport SCOP Transport SUT Adapter SCOP Transport IPv6 Transport

Example Test Configuration 1 PTC_UT

Example Test Configuration 2

Test Topology 03

The TTCN-3 Library (Currently Core IPv6) Each test uses this library Decreases test code size and improves its quality Reduces time to develop new tests Contains useful definitions for different purposes Test component synchronization Basic IPv6 packet exchanges Preamble, test purpose, and postamble code Test configurations Code for driving upper IPv6 interface for conformance testing and automated interoperability testing Extensively documented Extensible Easily add modules Easily add tests to test suites

What is TTCN-3? Updated version of TTCN-2 Very different syntax to TTCN-2 retains many of the basic ‘testing concepts’ of TTCN-2 More like a regular programming language Has extended applicability Especially to ‘IP-oriented’ protocols (not just OSI) Not just conformance Good tool support Good book: http://eu.wiley.com/WileyCDA/WileyTitle/productCd-0470012242.html

TTCN-3 Standards ES 201 873-1 (Z.140) ES 201 873-2 (Z.141) TTCN-3 Core Language ES 201 873-2 (Z.141) TTCN-3 Tabular Presentation Format (TFT) TR 101 873-3 (will eventually be ES 201 873-3) (Z.142) TTCN-3 Graphical Presentation Format (GFT) ES 201 873-4 (Z.143) TTCN-3 Operational Semantics ES 201 873-5 TTCN-3 Runtime Interface (TRI) ES 201 873-6 TTCN-3 Control Interfaces (TCI) ES 201 873-7 Using ASN.1 with TTCN-3 To come: XML, IDL, C/C++

Main Capabilities of TTCN-3 Dynamic concurrent testing configurations Various communication mechanisms (synch and asynch) Data and signature templates with powerful matching mechanisms (including regular expressions) Specification of encoding information User-defined attributes (e.g., display modes) Test suite parameterization Control of Test Case execution and selection mechanisms Control of complex test configurations Assignment and handling of test verdicts Fully harmonized with ASN.1 (XML and IDL coming) Different presentation formats Well-defined syntax, static - and operational semantics

The Core Language and TTCN-3 presentation Formats Text format Core format is text based (most popular) TTCN-3 can be edited or viewed in other formats Tabular format (for TTCN-2 people) Graphical format (good for visual overview) Other standardized formats in the future? Proprietary formats possible PresentationFormat3 PresentationFormatn Graphical Format Tabular Format TTCN-3 Core Language

The Core Language Use With Other Languages TTCN can be integrated with other 'type and value' systems Fully harmonized with ASN.1 (1997) Harmonization possible with other languages IDL, XML, C/C++ ASN.1 Types & Values IDL Types & Values Other types & Valuesn XML Types & Values TTCN-3 Core Language

Points for Consideration by RAN5 We think all requirements (generic and 3GPP) are in the catalogue but are there additional RFCs? Will need to write some additional TPs at least for the identified 3GPP requirements 3GPP usually write TPs and Test Descriptions then TTCN maybe the intermediate level is not needed for IPv6 testing (test are less complex than what RAN5 are used to doing) Basic TTCN-3 library components could be used by RAN5 lot of TTCN-3 code which RAN5 could reuse - pick what you need additional tests needed for 3GPP requirements additional configurations? New Pre- and Postambles (different bearers) Invocation of TTCN-2 Pre- and Postambles possible on a language level (but supported by tools?) Timely tool support Validate over wire? Could use ETSI IPv6 testbed

STF276@Work!