ETSI TS 102 516 V3.1.1 (2008-02)

Technical Specification
Methods for Testing and Specification (MTS);
Internet Protocol Testing (IPT): IPv6 Core Protocol;
Conformance Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma

�
2 ETSI TS 102 516 V3.1.1 (2008-02)

Reference
RTS/MTS-IPT-006[3]-IPv6-CorATS
Keywords
IP, IPv6, testing, TTCN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 102 516 V3.1.1 (2008-02)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.8
4 Abstract Test Method (ATM).8
4.1 IPv6 Test Configuration.8
4.2 Test configurations for Core IPv6 .10
4.2.1 CF_CORE_01.10
4.2.2 CF_CORE_02.10
4.2.3 CF_CORE_03.11
5 Untestable and not implemented Test Purposes (TP).11
5.1 Untestable TP.11
5.2 Not implemented TP .12
6 ATS implementation details.12
6.1 Mapping IPv6 addresses to MAC addresses .13
6.1.1 The Role of the Send Map in the Send Process .13
6.1.2 The Role of the Receive Map in the Receive Process.14
6.1.3 Example of Send Map and Receive Map.16
6.2 Test Cleanup.18
6.3 Value conventions in IPv6 ATS .19
6.3.1 Value conventions for IPv6 ATS.19
6.3.2 Value conventions for test adapter.20
7 PCTR conformance.20
8 PIXIT conformance.20
9 ATS Conformance.20
Annex A (normative): Abstract Test Suite (ATS) .21
A.1 The ATS in TTCN-3 core (text) format .21
Annex B (normative): Partial PIXIT proforma .22
B.1 Identification summary.22
B.2 ATS summary.22
B.3 Test laboratory.22
B.4 Client identification.23
B.5 SUT.23
B.6 Protocol layer information.23
B.6.1 Protocol identification.23
B.6.2 Generic Setup.24
B.6.3 Default Values.24
B.6.4 Unknown IDs.24
B.6.5 Mac Layer.25
B.6.6 Addresses.25
B.6.6.1 Prefixes.25
ETSI
4 ETSI TS 102 516 V3.1.1 (2008-02)
B.6.6.2 IUT Addresses.25
B.6.6.3 Tester Addresses.26
B.6.6.3.1 Host 1 (HS_01) .26
B.6.6.3.2 Host 2 (HS_02) .26
B.6.6.3.3 Host 3 (HS_03) .26
B.6.6.3.4 Router 1 (RT_01).27
B.6.6.3.5 Router 3 (RT_03).27
B.6.7 Timer.27
Annex C (normative): PCTR proforma .28
C.1 Identification summary.28
C.1.1 Protocol conformance test report.28
C.1.2 IUT identification.28
C.1.3 Testing environment.29
C.1.4 Limits and reservation.29
C.1.5 Comments.29
C.2 IUT Conformance status .30
C.3 Static conformance summary.30
C.4 Dynamic conformance summary.30
C.5 Static conformance review report.30
C.6 Test campaign report.31
C.7 Void.37
C.8 Observations.37
History .38

ETSI
5 ETSI TS 102 516 V3.1.1 (2008-02)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Methods for Testing and
Specification (MTS).
ETSI
6 ETSI TS 102 516 V3.1.1 (2008-02)
1 Scope
The present document specifies the Abstract Test Suite (ATS) for the core functions of the Internet Protocol, Version 6,
as defined in the specifications [11] through to [21]. The ATS is based on the requirements defined in the IPv6
requirements catalogue (TS 102 514 [2]) and theIPv6 test purposes (TS 102 515 [3]) and written according to the
guidelines of TS 102 514 [2], ISO/IEC 9646-2 [5] and ETS 300 406 [9].
The objective of the present document is to provide a basis for conformance tests for IPv6 equipment giving a high
probability of inter-operability between different manufacturer's IPv6 equipments.
Annex A provides the Tree and Tabular Combined Notation (TTCN-3) part of the ATS.
Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the ATS.
Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of the ATS.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TS 102 351: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT);
IPv6 Testing: Methodology and Framework".
[2] ETSI TS 102 514: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT):
IPv6 Core Protocol; Requirements Catalogue".
[3] ETSI TS 102 515: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT):
IPv6 Core Protocol; Conformance Test Suite Structure and Test Purposes (TSS&TP)".
[4] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
ETSI
7 ETSI TS 102 516 V3.1.1 (2008-02)
[5] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite specification".
[6] ISO/IEC 9646-4: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 4: Test realization".
[7] ISO/IEC 9646-5: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 5: Requirements on test laboratories and clients for the
conformance assessment process".
[8] ISO/IEC 9646-6: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 6: Protocol profile test specification".
[9] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[10] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[11] IETF RFC 1981: "Path MTU Discovery for IP version 6".
[12] IETF RFC 2374: "An IPv6 Aggregatable Global Unicast Address Format".
[13] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification".
[14] IETF RFC 2461: "Neighbor Discovery for IP Version 6 (IPv6)".
[15] IETF RFC 2462: "IPv6 Stateless Address Autoconfiguration".
[16] IETF RFC 2463: "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6
(IPv6) Specification".
[17] IETF RFC 2675: "IPv6 Jumbograms".
[18] IETF RFC 2711: "IPv6 Router Alert Option".
[19] IETF RFC 2894: "Router Renumbering for IPv6".
[20] IETF RFC 3484: "Default Address Selection for Internet Protocol version 6 (IPv6)".
[21] IETF RFC 3513: "Internet Protocol Version 6 (IPv6) Addressing Architecture".
[22] ETSI TS 102 594: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT):
IPv6 Security; Conformance Abstract Test Suite (ATS) and partial Protocol Implementation eXtra
Information for Testing (PIXIT) proforma".
[23] ETSI TS 102 596: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT):
IPv6 Mobility; Conformance Abstract Test Suite (ATS) and partial Protocol Implementation eXtra
Information for Testing (PIXIT) proforma".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions given in ISO/IEC 9646-1 [4] apply.
abstract test case
Abstract Test Method (ATM)
Abstract Test Suite (ATS)
Implementation Under Test (IUT)
ETSI
8 ETSI TS 102 516 V3.1.1 (2008-02)
Lower Tester (LT)
Test Purpose (TP)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
ETS Executable Test Suite
IETF Internet Engineering Task Force
IPv6 Internet Protocol version 6
IUT Implementation Under Test
MAC Medium Access Control
MOT Means Of Testing
MTC Main Test Component
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PTC Parallel Test Component
SUT System Under Test
TC Test Case
TP Test Purpose
TRI TTCN-3 Runtime Interface
TSI Test System Interface
TSS Test Suite Structure
UT Upper Tester
4 Abstract Test Method (ATM)
4.1 IPv6 Test Configuration
Figure 1 shows the IPv6 Test Configuration. More information for the IPv6 Test Configuration is provided below.
ETSI
9 ETSI TS 102 516 V3.1.1 (2008-02)
Test System
SUT
Action
Trigger
MTC
Upper Tester
Application
Sync ports
PTC01 PTC02 PTCn
PTCn+1
IPv6
IPv6 IPv6
TTCN-3
TTCN-3 TTCN-3 TTCN-3
Blackbox
cf   ip cf   ip cf    ut
ip (IUT)
Event
TSI cf TSI ut
Indication
TSI eth
Test Adapter
MAC
Figure 1: IPv6 Test Configuration
• MTC, PTC01, PTC02 to PTCn run MAC-independent TTCN-3 code.
• Each PTC has 1 cf port and 1 ip port.
• Any IPv6 message (unicast, multicast, all-nodes etc.) is sent via the ip port.
• Configuration messages are sent via the cf port in order to configure the test adapter.
• 1 and the same TSI cf port is mapped to all cf ports.
• 1 and the same TSI eth port is mapped to all ip ports.
• TTCN-3 uses ut port to control the Upper Tester Application.
• The Upper Tester Application allows to configure the IUT, trigger IUT actions and observe IUT events.
• MTC, PTC01, PTC02 to PTCn and its Test Adapter with MAC form the Lower Tester.
• MTC, PTCn + 1 and its Test Adapter with Upper Tester Application form the Upper Tester.
• Upper Tester implementation is not relevant for the prototype.
Test Adapter requirements:
• Test Adapter shall receive the AtsIpv6_TestConfiguration_TypesAndValues.CfMessage from every
participating PTC.
• Test Adapter shall set a MAC filter in order to capture IPv6 messages only.
• When receiving an IPv6 message from TRI, the Test Adapter shall:
- assemble a MAC message containing the IPv6 message and the appropriate Mac Addresses; and
- send the MAC message to the appropriate network device (MAC interface).
ETSI
10 ETSI TS 102 516 V3.1.1 (2008-02)
• When receiving a MAC message a network device, the Test Adapter shall:
- extract the IPv6 message; and
- enqueue the IPv6 message to the appropriate PTC.
4.2 Test configurations for Core IPv6
This clause describes the ATM used to test the IPv6 core functions as defined in the RFC specifications [11] through to
[21]. The three following configurations have been developed to test the two different types of IUT, hosts and routers.
Either a simple one-to-one connection between tester and IUT is established which serves as Point of Control and
Observation (PCO) or the IUT is connected to two Parallel Test Components (PTCs) that act as router or host
respectively.
4.2.1 CF_CORE_01
Figure 2 shows the configuration CF 01. This is the basic configuration for router or host tests. PTC01 simulates HS01
and RT01. This configuration is partly reused in configuration CF_CORE_03 (see figure 4).
Test System PTC01
HS01
RT01
NUT
Net A
Figure 2: CF_CORE_01
4.2.2 CF_CORE_02
Figure 3 shows CF_CORE_02. The IUT is a router. PTC01 simulates HS01. PTC02 simulate PTC02.
CF02_HS01 shall be used in the case where only 1 interface of the IUT is tested.
CF02_HS01
PTC01
HS01
Net A
Test
System
RUT
Net B
PTC02
HS02
Figure 3: CF_CORE_02
ETSI
11 ETSI TS 102 516 V3.1.1 (2008-02)
4.2.3 CF_CORE_03
Figure 4 shows CF_CORE_03. The IUT is a host. PTC01 simulates RT01 and HS02. PTC02 simulates RT02 and
HS03.
Test System
PTC01
PTC02
HS02
HS03
Net B
Net C
RT01
RT03
Net A
HUT
Figure 4: CF_CORE_03
5 Untestable and not implemented Test Purposes (TP)
The ATS is comprised of 271 TC. Those were derived from a total of 396 TP.
5.1 Untestable TP
This clause gives a list of 80 TP, which are not implemented in the ATS due to the chosen ATM or other restrictions:
TP_COR_1092_01, TP_COR_1089_01, TP_COR_1034_01, TP_COR_1008_01, TP_COR_1814_01,
TP_COR_1086_01, TP_COR_1122_01, TP_COR_9012_01, TP_COR_1272_01, TP_COR_9016_01,
TP_COR_9017_01, TP_COR_9018_01, TP_COR_9019_01, TP_COR_8009_01, TP_COR_1225_01,
TP_COR_1276_01, TP_COR_1282_01, TP_COR_1282_02, TP_COR_1256_01, TP_COR_1263_01,
TP_COR_1250_01, TP_COR_1292_01, TP_COR_1471_01, TP_COR_1472_01, TP_COR_1416_01,
TP_COR_1416_02, TP_COR_1416_03, TP_COR_1416_04, TP_COR_1458_01, TP_COR_1448_01,
TP_COR_1444_01, TP_COR_1442_01, TP_COR_8579_01, TP_COR_8492_01, TP_COR_8493_01,
TP_COR_8232_01, TP_COR_8583_01, TP_COR_8387_01, TP_COR_8402_01, TP_COR_8586_01,
TP_COR_8210_01, TP_COR_8246_01, TP_COR_8160_01, TP_COR_8169_01, TP_COR_8168_01,
TP_COR_8805_01, TP_COR_8338_02, TP_COR_8338_03, TP_COR_8338_05, TP_COR_8338_06,
TP_COR_8108_01, TP_COR_1294_01, TP_COR_1245_01, TP_COR_1248_01, TP_COR_1299_01,
TP_COR_9027_01, TP_COR_1304_01, TP_COR_1306_01, TP_COR_1315_01, TP_COR_8578_01,
TP_COR_8560_01, TP_COR_8530_01, TP_COR_8125_01, TP_COR_8126_01, TP_COR_8128_01,
TP_COR_8243_01, TP_COR_8133_01, TP_COR_8379_01, TP_COR_8384_01, TP_COR_8382_01,
TP_COR_1435_01, TP_COR_8577_01, TP_COR_8435_01, TP_COR_8512_01, TP_COR_8516_01,
TP_COR_8235_01, TP_COR_8574_01, TP_COR_8326_01, TP_COR_8297_01, TP_COR_8188_01
ETSI
12 ETSI TS 102 516 V3.1.1 (2008-02)
5.2 Not implemented TP
44 TP have not been implemented, as the dynamic behaviour that validates their test purposes is already implemented in
one or more TC. Table 1 gives the relation between the non-implemented TP and the TC that cover(s) its purpose.
Table 1: List of not implemented TP
TP not implemented TC that covers the dynamic behaviour
TP_COR_8814_01 TC_COR_8813_01
TP_COR_1455_01 TC_COR_1085_01
TP_COR_8013_01 TC_COR_1225_01
TP_COR_1244_01 TC_COR_1235_01
TP_COR_1239_01 TC_COR_1210_02
TP_COR_8148_01 TC_COR_1280_01
TP_COR_1257_01 TC_COR_1280_01
TP_COR_1419_01 TC_COR_1417_01
TP_COR_1459_01 TC_COR_1468_01
TP_COR_1453_01 TC_COR_1085_01
TP_COR_1453_02 TC_COR_1011_01
TP_COR_1453_03 TC_COR_1020_01
TP_COR_1447_01 TC_COR_1058_01
TP_COR_1447_02 TC_COR_1058_02
TP_COR_8415_01 TC_COR_8146_01
TP_COR_8483_01 TC_COR_8482_01
TP_COR_8491_01 TC_COR_8146_01
TP_COR_8494_01 TC_COR_8464_01
TP_COR_8499_01 TC_COR_8147_01
TP_COR_8504_01 TC_COR_8434_01
TP_COR_8511_01 TC_COR_8434_01, TC_COR_8504_01
TP_COR_8366_01 TC_COR_8507_01
TP_COR_8565_01 TC_COR_8396_01
TP_COR_8162_01 TC_COR_8159_01, TC_COR_8179_01,
TC_COR_8180_01
TP_COR_8444_01 TC_COR_8179_01
TP_COR_8452_01 TC_COR_8159_01
TP_COR_8171_01 TC_COR_8461_01
TP_COR_8172_01 TC_COR_8470_01
TP_COR_8410_01 TC_COR_8567_01
TP_COR_8587_01 TC_COR_8592_01
TP_COR_8118_01 TC_COR_8513_01
TP_COR_8113_01 TC_COR_8146_01
TP_COR_8149_01 TC_COR_8146_01
TP_COR_1228_01 Several TC test the behaviour implicitly
TP_COR_1303_01 TC_COR_1298_01
TP_COR_8343_01 TC_COR_8349_01
TP_COR_1042_01 TC_COR_1443_01
TP_COR_8107_01 Several TC test the behaviour implicitly
TP_COR_1419_03 TC_COR_1417_02
TP_COR_8330_01 TC_COR_8586_01
TP_COR_8299_01 TC_COR_9034_01
TP_COR_8315_01 TC_COR_9034_02
TP_COR_8315_02 TC_COR_9034_01
TP_COR_8550_01 TC_COR_8183_01
6 ATS implementation details
The following clauses describe the mapping and cleanup procedures used in the ATS and some ATS value conventions.
Further descriptions of the ATS conventions are found in TS 102 351 [1]. The ATS implementation details for the IPv6
mobility and security test suites are found in TS 102 596 [23] and TS 102 594 [22].
ETSI
Send Map
13 ETSI TS 102 516 V3.1.1 (2008-02)
6.1 Mapping IPv6 addresses to MAC addresses
The IPv6 ATS sends and receives IPv6 messages. The test adapter sends and receives MAC messages. The
configuration messages in the IPv6 ATS map the IPv6 parameters to the MAC parameters.
The code statement:
v_cfMsg.paramsHs02 := f_createParamsHs02(PX_MAC_UCA_RT01_A, true);
• creates all relevant IPv6 address properties (IPv6 Link-local address, IPv6 Global address, IPv6 SolNode
Multicast address etc) for the given MAC address;
• indicates with the test adapter flag true/false if the information is relevant for the test adapter or not:
true: this information is relevant on TTCN and test adapter level,
false: this information is only relevant on TTCN level.
The configuration message allows the test adapter to build Send Maps and Receive Maps. One possible format of Send
Maps and Receive Maps is discussed in the following clauses.
6.1.1 The Role of the Send Map in the Send Process
The Send Map provides the information to determine for a given IPv6 source/destination address:
• its related MAC source/destination address;
• the net device on which the related IPv6 message shall be sent out.
The Send Map is shown in table 2.
Table 2: Send Map
Key Value
IP@ PTC NetDeviceId MAC@
Reference
The Send Process is shown in figure 5.
PTC01
Net Device 1
Net Device 2
PTC02
TTCN-3
Test Adapter
Figure 5: Send Process
The use of the Send Map is shown in figure 6.
ETSI
14 ETSI TS 102 516 V3.1.1 (2008-02)
process Send_Map 1(1)
Yes
dstIp@ == allNodesMca@
No
Yes
dstIp@ == allRoutersMca@
No
==> use well-known dstMac@
sendMap(srcIP@, PTC) ==> netDevice + srcMac@
sendMap(srcIp@, PTC) ==> netDevice + srcMac@
sendMap(dstIp@, PTC) ==> netDevice + dstMac@
Source and destination address
is needed
Figure 6: Send Map process
6.1.2 The Role of the Receive Map in the Receive Process
The Receive Map provides the information to determine for a given MAC source/destination address:
• the PTC to which the related IPv6 message shall be sent.
The Receive Map is shown in table 3.
Table 3: Receive Map
Key Value
MAC@ PTC Role
The receive process consists of the following steps:
• Filter all received MAC packets according to v_cfMsg.macFilterList are passed to the Receive Map.
• Queue the IPv6 message to the appropriate PTC.
ETSI
Receive Map
MAC Filter
15 ETSI TS 102 516 V3.1.1 (2008-02)
PTC01
Net Device 1
Net Device 2
PTC02
Figure 7: Receive Process
The Mac Filter is shown in figure 8.
process MAC_Filter 1(1)
MAC message received
No
Is it for me? MAC dst == MAC filter list
discard
Yes
Yes
Did I sent it myself? MAC src == MAC filter list
No
discard
Receive Map
Figure 8: MAC Filter process
The use of the Receive Map is shown in figure 9.
ETSI
16 ETSI TS 102 516 V3.1.1 (2008-02)
process Receive_Map 1(1)
Yes
dstIp@ == allNodesMca@
No
copy to all PTCs
dstIp@ == allRoutersMca@ Yes
or
srcIp@ == c_16ZeroBytes and dstIp@ == solNodeMca
No
Copy to all PTCs
with role "Router
rcvMap(dstMac@) ==> PTC
2nd statement is added
to receive DAD NS.
- IUT == HS: DAD NS is ignored in default
- IUT == MN (returning home): TTCN replies,
otherwise MN would not know
that it's at home
Figure 9: Receive Map process
6.1.3 Example of Send Map and Receive Map
Figure 10 shows a part of a test case testing redirection. The comment boxes show extracts from
AtsIpv6_TestConfiguration.f_createCfMsg_rt01 and AtsIpv6_TestConfiguration.f_createCfMsg_rt03. The test adapter
flag true/false indicates if the information is relevant for the test adapter or not.
Example extracts of the Send Map and the Received Map which the test adapter needs to build for Redirect testing are
shown below in figure 10, tables 4 and 5.
ETSI
17 ETSI TS 102 516 V3.1.1 (2008-02)
MSC Redirect
CF_CORE_03 is used f_createParamsRt01(PX_MAC_UCA_RT01_A, false);
f_createParamsHs02(PX_MAC_UCA_RT01_A, false);
f_createParamsIutA(PX_MAC_UCA_IUT_1, true);
f_createParamsRt03(PX_MAC_UCA_RT03_A, true);
f_createParamsHs03(PX_MAC_UCA_RT03_A, true);
Test adapter shall not manag any HS02 and RT01
MAC address information for this PTC
f_createParamsRt01(PX_MAC_UCA_RT01_A, true);
f_createParamsHs02(PX_MAC_UCA_RT01_A, true);
f_createParamsIutA(PX_MAC_UCA_IUT_1, true);
f_createParamsRt03(PX_MAC_UCA_RT03_A, false);
f_createParamsHs03(PX_MAC_UCA_RT03_A, false);
Test adapter shall not manag any HS03 and RT03
MAC address information for this PTC
HUT
RT01 RT03
HUT default route = RT01
ERq
( MAC src = PX_MAC_UCA_RT03_A
MAC dst = PX_MAC_UCA_IUT
IP src = PX_GLA_HS03
IP dst = PX_GLA_IUT
)
ERp
(MAC src = PX_MAC_UCA_IUT
MAC dst = PX_MAC_UCA_RT01_A
IP src = PX_GLA_IUT
IP dst = PX_GLA_HS03
)
ICMPv6 Redirect(PX_MAC_UCA_RT03_A)
( MAC src = PX_MAC_UCA_RT01_A
MAC dst = PX_MAC_UCA_IUT
IP src = PX_LLA_RT01_A
IP dst = PX_LLA_IUT)
ERq
( MAC src = PX_MAC_UCA_RT03_A
MAC dst = PX_MAC_UCA_IUT
IP src = PX_GLA_HS03
IP dst = PX_GLA_IUT
)
ERp
(MAC src = PX_MAC_UCA_IUT
MAC dst = PX_MAC_UCA_RT03_A
IP src = PX_GLA_IUT
IP dst = PX_GLA_HS03 )
Figure 10: MSC Redirect
Extract of Send Map built from AtsIpv6_TestConfiguration.f_createCfMsg_rt01 and
AtsIpv6_TestConfiguration.f_createCfMsg_rt03.
ETSI
18 ETSI TS 102 516 V3.1.1 (2008-02)
Table 4: Extract of Send Map
Key Value
IP@ PTC NetDeviceId MAC@
Reference
m_cfRt01
PX_LLA_RT01_A PTC1 eth1 PX_MAC_UNI_RT01_A
PX_GLA_RT01_A PTC1 eth1 PX_MAC_UNI_RT01_A
PX_GLA_HS02 PTC1 eth1 PX_MAC_UNI_RT01_A
m_cfRt03
PX_LLA_RT03_A PTC2 eth1 PX_MAC_UNI_RT03_A
PX_GLA_RT03_A PTC2 eth1 PX_MAC_UNI_RT03_A
PX_LLA_HS03 PTC2 eth1 PX_MAC_UNI_RT03_A

Extract of Receive Map built from AtsIpv6_TestConfiguration.f_createCfMsg_rt01 and
AtsIpv6_TestConfiguration.f_createCfMsg_rt03.
Table 5: Extract of Receive Map
Key Value
MAC@ PTC Role
m_cfRt01
PX_MAC_UNI_RT01_A PTC1 Router
m_cfRt03
PX_MAC_UNI_RT03_A PTC2 Router
6.2 Test Cleanup
The Core Test Cleanup procedure empties the IUT's Neighbor Cache. The Core Test Cleanup procedure is repeated for
each Neighbor Cache entry as shown in figure 11.
ETSI
19 ETSI TS 102 516 V3.1.1 (2008-02)
MSC Core_TestCleanup
This process is repeated for every IPv6 address used in the test case
RT/HS IUT
NA
(OverrideFlag set
TargetLLAOption with new MAC address )
alt 1 in the case of TN = RT
RA
(prefixLifetime = 0
routerLifetime = 0 )
ERq
ERp
loop 1
no reply to NS
NS
Figure 11: Core Test Cleanup
6.3 Value conventions in IPv6 ATS
6.3.1 Value conventions for IPv6 ATS
The generic approach for sending templates that need specific calculation (checksum, payload length, authenticator etc)
is:
1) Initialize templates with zero values.
2) Set values appropriate to test case (i.e. error values).
3) Send function checks:
- if zero value, then external function is called in order to calculate the correct value of the field;
- if non-zero value, then no external function is called. This allows to send templates with incorrect values.
ETSI
20 ETSI TS 102 516 V3.1.1 (2008-02)
6.3.2 Value conventions for test adapter
In all call cases except for IPSec the test adapter shall send the templates as they are defined in TTCN.
In the case of IPSec, the TTCN defines the templates in plaintext in order to allow the test operator to see plaintext
logging. TTCN provides all necessary security parameters for encryption/decryption to the test adapter. If the test
adapter detects any missing information, then it shall not add the missing information by itself, but it shall throw an
error exception.
7 PCTR conformance
A test laboratory, when requested by a client to produce a PCTR, is required, as specified in ISO/IEC 9646-5 [7], to
produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [7].
Furthermore, a test laboratory, offering testing for the ATS specification contained in annex C, when requested by a
client to produce a PCTR, is required to produce a PCTR conformant with the PCTR proforma contained in annex A.
A PCTR which conforms to this PCTR proforma specification shall preserve the content and ordering of the clauses
contained in annex A. Clause A.6 of the PCTR may contain additional columns. If included, these shall be placed to the
right of the existing columns. Text in italics may be retained by the test laboratory.
8 PIXIT conformance
A test realizer, producing an executable test suite for the Abstract Test Suite (ATS) specification contained in annex C,
is required, as specified in ISO/IEC 9646-4 [6], to produce an augmented partial PIXIT proforma conformant with this
partial PIXIT proforma specification.
An augmented partial PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a
minimum, have contents which are technically equivalent to annex B. The augmented partial PIXIT proforma may
contain additional questions that need to be answered in order to prepare the Means Of Testing (MOT) for a particular
Implementation Under Test (IUT).
A test laboratory, offering testing for the ATS specification contained in annex C, is required, as specified in
ISO/IEC 9646-5 [7], to further augment the augmented partial PIXIT proforma to produce a PIXIT proforma
conformant with this partial PIXIT proforma specification.
A PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, have contents
which are technically equivalent to annex B. The PIXIT proforma may contain additional questions that need to be
answered in order to prepare the test laboratory for a particular IUT.
9 ATS Conformance
The test realizer, producing a Means Of Testing (MOT) and Executable Test Suite (ETS) for the present document,
shall comply with the requirements of ISO/IEC 9646-4 [6]. In particular, these concern the realization of an Executable
Test Suite (ETS) based on each ATS. The test realizer shall provide a statement of conformance of the MOT to the
present document.
An ETS which conforms to the present document shall contain test groups and test cases which are technically
equivalent to those contained in the ATS in annex C. All sequences of test events comprising an abstract test case shall
be capable of being realized in the executable test case. Any further checking which the test system might be capable of
performing is outside the scope of the present document and shall not contribute to the verdict assignment for each test
case.
Test laboratories running conformance test services using this ATS shall comply with ISO/IEC 9646-5 [7].
A test laboratory which claims to conform to this ATS specification shall use an MOT which conforms to this ATS.
ETSI
21 ETSI TS 102 516 V3.1.1 (2008-02)
Annex A (normative):
Abstract Test Suite (ATS)
A.1 The ATS in TTCN-3 core (text) format
This ATS has been produced using the Testing and Test Control Notation (TTCN-3) according to ES 201 873-1 [10].
The TTCN-3 core (text) representation corresponding to this ATS is contained in several ASCII files contained in
archive ts_102516v030101p0.zip which accompanies the present document.
ETSI
22 ETSI TS 102 516 V3.1.1 (2008-02)
Annex B (normative):
Partial PIXIT proforma
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PIXIT.
The PIXIT Proforma is based on ISO/IEC 9646-6 [8]. Any needed additional information can be found in there.
B.1 Identification summary
Table B.1
PIXIT Number:
Test Laboratory Name:
Date of Issue:
Issued to:
B.2 ATS summary
Table B.2
Protocol Specification:
Protocol to be tested:
ATS Specification:
Abstract Test Method:
B.3 Test laboratory
Table B.3
Test Laboratory Identification:

Test Laboratory Manager:
Means of Testing:
SAP Address:
ETSI
23 ETSI TS 102 516 V3.1.1 (2008-02)
B.4 Client identification
Table B.4
Client Identification:
Client Test manager:
Test Facilities required:
B.5 SUT
Table B.5
Name:
Version:
SCS Number:
Machine configuration:
Operating System Identification:

IUT Identification:
PICS Reference for IUT:
Limitations of the SUT:
Environmental Conditions:
B.6 Protocol layer information
B.6.1 Protocol identification
Table B.6
Name:
Version:
PICS References:
ETSI
24 ETSI TS 102 516 V3.1.1 (2008-02)
B.6.2 Generic Setup
Table B.7: Generic Setup
Name Type Comments Value
PX_IUT_ROLE Router/Host Is the IUT a router or a host?
PX_TEST_CAMPAIGN CampaignType Selects only TCs that can be run in a campaign.
PX_CONFIGURATION_ID ConfigId The id of the current configuration/topology.
PX_UTS_AVAILABLE BOOLEAN Specifies if Upper Tester Server is available or
not.
B.6.3 Default Values
Table B.8: Default Values
Name Type Comments Value
PX_DAD_DUP_ADDR_DETECT_T Integer Number of DAD packet retransmissions
RANSMITS_IUT
PX_MAX_UNICAST_SOLICIT_IUT Integer Number of NUD Neighbor Solicitation
retransmissions
PX_MAX_MULTICAST_SOLICIT_I Integer Number of AR Neighbor Solicitation
UT retransmissions
B.6.4 Unknown IDs
Table B.9: Unknown IDs
Name Type Comments Value
PX_UNRECOGNIZED_EXT_HEADER_ID Integer Id of an IPv6 extension header that the IUT
does not recognize.
PX_NEXT_HEADER_STOPS_PACKET_P Integer Id of an IPv6 extension header that stops
ROCESSING packet processing.
PX_UNRECOGNIZED_ROUTING_TYPE Integer Id of a routing type that the IUT does not
recognize.
PX_UNKNOWN_ICMP_MESSAGE_TYPE Integer An ICMPv6 message type that is greater than
129 and unknown to the implementation.
PX_UNKNOWN_NBRADVOPT_ID Integer A Neighbor Advertisement option id that is
unknown to the implementation.
PX_UNKNOWN_NBRSOLOPT_ID Integer A Neighbor Solicitation option id that is
unknown to the implementation.
PX_UNKNOWN_RTRSOLOPT_ID Integer A Router Solicitation option id that is unknown
to the implementation.
PX_UNKNOWN_REDIRECTOPT_ID Integer A Redirect option id that is unknown to the
implementation.
PX_SKIP_OVER_HOP_BY_HOP_OPTIO Integer A hop by hop option id that is unknown to the
N implementation ('skip over' type).
PX_SKIP_OVER_DESTINATION_OPTIO Integer A destination option id that is unknown to the
N implementation ('skip over' type).
PX_DISCARD_PACKET_HOP_BY_HOP_ Integer A hop by hop option id that is unknown to the
OPTION implementation ('discard' type).
PX_DISCARD_PACKET_DESTINATION_ Integer A destination option id that is unknown to the
OPTION implementation ('discard' type).
PX_DISCARD_PACKET_HOP_BY_HOP_ Integer A destination option id that is unknown to the
OPTION_TYPE_10 implementation ('discard and always send
ICMP Parameter Problem message' type).
PX_DISCARD_PACKET_DESTINATION_ Integer A destination option id that is unknown to the
OPTION_TYPE_10 implementation ('discard and always send
ICMP Parameter Problem message' type).
ETSI
25 ETSI TS 102 516 V3.1.1 (2008-02)
Name Type Comments Value
PX_DISCARD_PACKET_HOP_BY_HOP_ Integer A destination option id that is unknown to the
OPTION_TYPE_11 implementation ('discard and, if not multicast,
send ICMP Parameter Problem message' type).
PX_DISCARD_PACKET_DESTINATION_ Integer A destination option id that is unknown to the
OPTION_TYPE_11 implementation ('discard and, if not multicast,
send ICMP Parameter Problem message' type).

B.6.5 Mac Layer
Table B.10: Mac Layer
Name Type Comments Value
PX_MAC_LAYER e_atm, Transport layer is ATM or Ethernet?
e_eth
PX_NET_DEVICE_ID_1 string Name of the primary TS interface
PX_NET_DEVICE_ID_2 string Name of the secondary TS interface
PX_MAC_OPTION_LEN Integer Length of Source Link-Layer and Target Link-
Layer options
B.6.6 Addresses
B.6.6.1 Prefixes
Table B.11: Prefixes
Name Type Comments Value
P
...