ETSI TS 103 238-3 V1.1.1 (2015-01)

ETSI TS 103 238-3 V1.1.1 (2015-01)






TECHNICAL SPECIFICATION
Integrated broadband cable
telecommunication networks (CABLE);
Testing; Conformance test specifications
for NAT64 technology;
Part 3: Abstract Test Suite (ATS) and
Protocol Implementation eXtra Information for Testing (PIXIT)

�

---------------------- Page: 1 ----------------------
2 ETSI TS 103 238-3 V1.1.1 (2015-01)



Reference
DTS/CABLE-00011-3
Keywords
ATS, CPE, IP, IPv6
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
The present document can be downloaded from:
http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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 or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2015.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 238-3 V1.1.1 (2015-01)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Abstract test method . 8
4.1 Abstract protocol tester . 8
4.2 Test configurations . 9
4.2.1 CF01: LSN as IUT . 9
4.3 TTCN-3 Test architecture. 10
4.4 Ports and ASPs (Abstract Services Primitives) . 12
4.4.1 TTCN-3 ports. 12
4.4.2 Abstract Service Primitives . 12
5 Implemented Test Purposes . 13
6 ATS conventions . 13
6.1 Naming conventions . 13
6.1.1 General guidelines . 13
6.1.2 NAT64 specific TTCN-3 naming conventions . 15
6.1.3 Usage of Log statements . 15
6.1.4 Test Case (TC) identifier . 16
6.2 On line documentation . 16
Annex A (normative): Partial PIXIT proforma for NAT64 . 17
A.1 Identification summary. 17
A.2 ATS summary . 17
A.3 Test laboratory . 17
A.4 Client identification . 17
A.5 SUT . 18
A.6 Protocol layer information. 18
A.6.1 Protocol identification . 18
A.6.2 IUT information . 19
Annex B (normative): PCTR Proforma for NAT64 . 21
B.1 Identification summary. 21
B.1.1 Protocol conformance test report . 21
B.1.2 IUT identification . 21
B.1.3 Testing environment . 21
B.1.4 Limits and reservation . 22
B.1.5 Comments. 22
B.2 IUT Conformance status . 22
B.3 Static conformance summary . 22
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 238-3 V1.1.1 (2015-01)
B.4 Dynamic conformance summary . 23
B.5 Static conformance review report . 23
B.6 Test campaign report . 24
B.7 Observations . 25
Annex C (normative): TTCN-3 library modules . 26
C.1 Electronic annex, zip file with TTCN-3 code . 26
History . 27

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 238-3 V1.1.1 (2015-01)
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://ipr.etsi.org).
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 Integrated broadband cable
telecommunication networks (CABLE).
The present document is part 3 of a multi-part deliverable covering the conformance test specification for NAT64
technology:
Part 1: "Test requirements and Protocol Implementation Conformance Statement (PICS) proforma";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 3: "Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)".
The development of the present document follows the guidance provided in the ETSI EG 202 798 [i.1]. Therefore the
present document is also based on the guidance provided in ETSI EG 202 798 [i.1].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will",
"will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 238-3 V1.1.1 (2015-01)
1 Scope
The present document contains the Abstract Test Suite (ATS) for NAT64 technology as defined in RFC 6052 [1] and
RFC 6146 [2] which address specific cable industry requirements as defined in ETSI TS 101 569-1 [11] in compliance
with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [6].
The objective of the present document is to provide a basis for conformance tests for NAT64 technology equipment
giving a high probability of inter-operability between different manufacturer's equipment.
The ISO standards for the methodology of conformance testing (ISO/IEC 9646-1 [3] and ISO/IEC 9646-2 [4]) as well
as the ETSI rules for conformance testing (ETSI ETS 300 406 [7]) are used as a basis for the test methodology.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] IETF RFC 6052: "IPv6 addressing of IPv4/IPv6 translators".
[2] IETF RFC 6146: "Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients
to IPv4 Servers".
[3] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts".
[4] ISO/IEC 9646-2 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 2: Abstract Test Suite specification".
[5] ISO/IEC 9646-6 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 6: Protocol profile test specification".
[6] ISO/IEC 9646-7 (1995): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 7: Implementation Conformance
Statements".
[7] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[8] 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".
[9] ETSI TS 103 238-1: "Integrated broadband cable telecommunication networks (CABLE);
Integrated Broadband Cable and Television Networks Cable IPv6 Transition Test Plan for NAT64;
Part 1: Test requirements and Protocol Implementation Conformance Statement (PICS) proforma".
[10] ETSI TS 103 238-2: "Integrated broadband cable telecommunication networks (CABLE);
Integrated Broadband Cable and Television Networks Cable IPv6 Transition Test Plan for NAT64;
Part 2: Test Suite Structure and Test Purposes (TSS&TP)".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 238-3 V1.1.1 (2015-01)
[11] ETSI TS 101 569-1: "Integrated Broadband Cable Telecommunication Networks (CABLE); Cable
Network Transition to IPv6 Part 1: IPv6 Transition Requirements".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI EG 202 798: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and
interoperability testing".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI TR 101 569-1 [11],
ISO/IEC 9646-1 [3] and ISO/IEC 9646-7 [6] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply.
ALG Application Layer Gateway
ASP Abstract Services Primitives
ATM Abstract Test Method
ATS Abstract Test Suite
CPE Customer Premises Equipment
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
FTP File Transfer Protocol
GRT Global Routing Table
HTTP HyperText Transfer Protocol
ICMP Internet Control Message Protocol
IETF Internet Engineering Task Force
IP Internet Protocol
IPv4 IP version 4
IPv6 IP version 6
IUT Implementation Under Test
LAN Local Area Network
LSN Large Scale NAT
MSS (TCP) Maximum Segment Size
MTC Main Test Component
MTS Methods for Testing and Specification
MTU Maximum Transmission Unit
NAT Network Address Translation / Network Address Translator
NPU Network Processing Unit
PA Platform Adaptor
PIXIT Protocol Implementation eXtra Information for Testing
PPTP Point-to-Point Tunneling Protocol
PTC Parallel Test Component
RSTP Rapid Spanning Tree Protocol
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 238-3 V1.1.1 (2015-01)
RTSP Real-Time Streaming Protocol
SA System Adaptor
SIP Session Initiation Protocol
SUT System Under Test
TA Test Adaptor
TC Test Case
TCP Transmission Control Protocol
TP Test Purpose
TSS Test Suite Structure
TTCN Testing and Test Control Notation
VRF Virtual Routing and Forwarding
4 Abstract test method
This clause describes the ATM used to test the NAT64 technology.
4.1 Abstract protocol tester
An abstract protocol tester presented in figure 1 is a process providing the test behaviour for testing an IUT. Thus it will
emulate an entity which is capable of proving the IUT functionalities. This type of test architecture provides a situation
of communication which is equivalent to real operation between real devices. The test system will simulate valid and
invalid behaviours, and will analyse the reaction of the IUT. Then the test verdict, e.g. pass or fail, will depend on the
result of this analysis. Thus this type of test architecture enables to focus the test objective on the IUT behaviour only.
In order to access an IUT, the corresponding abstract protocol tester needs to use lower layers to establish a proper
connection to the system under test (SUT) over a physical link (Lower layers link).

Test system SUT
PDUs
Abstract protocol tester IUT
Lower layers
Lower layers
Lower layers link

Figure 1: Generic abstract protocol tester
The "Protocol Data Units" (PDUs) are the messages exchanged between the IUT and the abstract protocol tester which
permits to trigger the IUT and to analyse its reactionThe result of the analysis allows to assign the test verdict.
Further control actions on the IUT may be necessary from inside the SUT, for instance to simulate a primitive from the
upper layer or the management/security entity. Further details on such control actions are provided by means of an
upper tester presented in clause 4.3.
The above "Abstract Test Method" (ATM) is well defined in ISO/IEC 9646-1 [3] and supports a wide range of
approaches for testing including the TTCN-3 abstract test language [8].The abstract protocol tester used for NAT64 test
suite is described in figure 2. The test system will send and receive IP packets, by using other upper layer protocols such
as DHCP, DNS and FTP, in order to analyse NAT64 functionality.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 238-3 V1.1.1 (2015-01)
Test System System Under Test
NAT64
Functionality
DNS/FTP/
SIP/RTSP/etc.*
IP packets
IPv4/IPv6
IPv4/IPv6
Ethernet Ethernet
Lower Layers Link

NOTE: * Those protocols are used to prove certain NAT64 functionalities.

Figure 2: Abstract Protocol Tester - NAT64
4.2 Test configurations
The test suite for NAT64 uses only a test configuration to cover the different test scenarios where Large Scale NAT
(LSN) is the IUT.
4.2.1 CF01: LSN as IUT
In this configuration, the LSN is the IUT and the test system simulates an IPv6 client in one side and a IPv4 server in
the other side.
Test system (TTCN-3)
IPv4 Host -
Simulated
LSN - IUT
IPv6 Host -
Simulated

Figure 3: CF01, LSN equipment is the IUT
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 238-3 V1.1.1 (2015-01)
4.3 TTCN-3 Test architecture
In general, a conformance test system architecture based on TTCN-3 is as figure 4 shows.
SUT
NAT64 Test System
Codec Test control
Upper tester application
Upper tester
NAT64 Abstract Test Suite
NAT64 IUT
transport
Test adaptor
NAT64 lower
Upper tester NAT64 lower
transport Layers Layers
Lower layer transport link
Upper tester transport link

Figure 4: Global test architecture
The "System Under Test" (SUT) contains:
• The "Implementation Under Test" (IUT), i.e. the object of the test.
• The "Upper tester application" enables to trigger or capture some actions (i.e. higher layer service primitives)
on the IUT.
• The "NAT64 lower layers" enable to establish a proper connection to the system under test (SUT) over a
physical link (Lower layer transport link).
• The "Upper tester transport" is a functionality, which enables the test system to communicate with the upper
tester application. Then the upper tester can be controlled by a TTCN-3 test component as part of the test
process.
The "NAT64 test system" contains:
• The "TTCN-3 test components" are processes providing the test behaviour. The test behaviour may be
provided as one single process or may require several independent processes.
• The "Codec" is a functional part of the test system to encode and decode messages between the TTCN-3
internal data representation and the format required by the related base standard.
• The "Test Control" enables the management of the TTCN-3 test execution (parameter input, logs, test
selection, etc.).
• The "Test adaptor" (TA) realizes the interface between the TTCN-3 ports using TTCN-3 messages, and the
physical interfaces provided by the IUT.
Based on the above test architecture, figure 5 shows a detailed test architecture used for the NAT64. The NAT64 ATS
requires using several Parallel Test Components (PTC) dealing with specific communication protocols and a Main Test
Component (MTC) dealing with PTCs' synchronization. The different test components communicate with the NAT64
SUT over several ports (described in section 4.4) which are used to exchange protocol messages between the test
components and the NAT64 IUT.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 238-3 V1.1.1 (2015-01)
The Upper tester entity enables triggering some functionalities by simulating actions or primitives from above
applications.
NAT64 TTCN-3 ATS
SSyncync
NAT64 por port t
component
(sync)
Upper tester / Monitoring Hosts IPv4 server
external functions component components component
control
UT
port
Test Adaptor (TA)*
CODECS
IPv4 IPv6 PPTP RTSP FTP SIP
IPv6 Ftp Sip
IPvIPv44 Pptp Rtsp
port port port
por port t port port

External Upper Tester NAT64 lower layers stack
functions Transport

Platform Adaptor (PA) System Adaptor (SA)
UT IPv4 IPv6
* NOTE: Test Adaptor
port
port port
(TA) is out of scope

Figure 5: NAT64 TTCN-3 test architecture
The following protocol test components are available. Each of these components can be mapped to either a "Main Test
Component" (MTC), when only one component shall be executed, or to a "Parallel Test Component" (PTC), if several
components shall be used:
• IPv4Server: This component simulates an IPv4 server entity and ist functionality.
• HOST: These components simulate one or more hosts (one component per host).
• MONITORING: This component is used to monitor traffic from the IUT.
The Sync component is mapped to the MTC and is used to trigger and synchronize the PTCs in order to orchestrate the
test environment executed by the PTCs. In addition, it starts and terminates the test cases.
The upper tester external functions control represents the functions which the protocol test components may use to
control the upper tester which is located in the SUT. These functions may use either external functions or dedicated
messages and a dedicated port to realize synchronization. These functions can be executed in the protocol test
components.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 238-3 V1.1.1 (2015-01)
4.4 Ports and ASPs (Abstract Services Primitives)
4.4.1 TTCN-3 ports
The NAT64 Test Suite implements the following ports:
• Ipv6Port, to send and receive IPv6 packets.
• Ipv4Port, to send and receive IPv4 packets.
• SipPort, to trigger the following SIP actions: authentication and data sending. It can monitor incoming traffic.
• RstpPort, to trigger the following RSTP actions: session setup and data sending. It can monitor incoming
traffic.
• FtpPort, to trigger the following FTP actions: login, logout, and data sending (both IPv4 and IPv6). It can
monitor incoming traffic.
• PptpPort, to trigger the following PPTP actions: session setup and data sending. It can monitor incoming
traffic.
• UtPort, included in order to be able to stimulate the IUT and receive extra information from IUT upper layers
(it is not used in the current implementation and is provided for future expansion).
4.4.2 Abstract Service Primitives
Abstract service primitives are commands or actions that need to be performed on the IUT in order to trigger certain
behaviour or to obtain information about the IUT state.
The list of ASP used in the NAT64 ATS is shown in table 1.
Table 1: NAT64 Abstract Service Primitives
TTCN-3 text Action/Command Description
Are routing tables configured GRT Action To check that routing tables are
upstream ingress & VRF upstream properly configured
egress?
Are routing tables configured VRF Action To check that routing tables are
upstream ingress & GRT upstream properly configured
egress?
Is Gateway Prefix withdrawn? Action To check that the gateway prefix is
withdrawn
Remove the routes for the next hop Command To remove the routes from IUT routing
tables
Remove the cache Command To remove the IUT cache
Simulate a hardware failure Command To simulate an IUT hardware failure
Remove the active NPU Command To remove the active NPU
Are all NPUs in the system used Action To check that all NPUs are properly
according to load-balancing rules? configured
Remove all NPUs Command To remove all NPUs
Shut down the NAT64 function Command To shut down the IUT
Is the IPv6 prefix withdrawn? Action To check that the IPv6 prefix is
withdrawn

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 238-3 V1.1.1 (2015-01)
5 Implemented Test Purposes
Table 2 shows the test purposes from [10] which have been implemented and included in the present document.
Table 2: Implemented Test Purposes
TP Identifier TC Identifier Group Subgroup PICS Untestable Implemented
TP/NAT64/LSN/BF/BV/01 TC_NAT64_LSN_BF_BV_01 Yes
Basic Function
TP/NAT64/LSN/BF/BV/02 TC_NAT64_LSN_BF_BV_02 Yes
TP/NAT64/LSN/NP/BV/01 TC_NAT64_LSN_NP_BV_01 NAT Pools Yes
TP/NAT64/LSN/AW/BV/01 TC_NAT64_LSN_AW_BV_01 Yes
Address Withdrawal Yes
TP/NAT64/LSN/AW/BV/02 TC_NAT64_LSN_AW_BV_02
TP/NAT64/LSN/AW/BV/03 TC_NAT64_LSN_AW_BV_03 Yes
TP/NAT64/LSN/FRAG/BV/ TC_NAT64_LSN_FRAG_BV_
Packet Fragmentation Yes
01 01

TP/NAT64/LSN/MSSC/BV/ TC_NAT64_LSN_MSSC_BV_
MSS Clamping Yes
01 01
TC_NAT64_LSN_SPR_BV_0 Static Port
TP/NAT64/LSN/SPR/BV/01 Yes
1 Reservation
TP/NAT64/LSN/NT/BV/01 TC_NAT64_LSN_NT_BV_01 NAT Timers Yes
TC_NAT64_LSN_ALG_BV_0
TP/NAT64/LSN/ALG/BV/01 Yes
1
TC_NAT64_LSN_ALG_BV_0
TP/NAT64/LSN/ALG/BV/02 PICS_SIP_TRANSLATION Yes
2 LSN

TC_NAT64_LSN_ALG_BV_0 Application Layer
TP/NAT64/LSN/ALG/BV/03 PICS_RTSP_TRANSLATION Yes
3
Gateway
TC_NAT64_LSN_ALG_BV_0
TP/NAT64/LSN/ALG/BV/04 PICS_PPTP_TRANSLATION Yes
4
TC_NAT64_LSN_ALG_BV_0
TP/NAT64/LSN/ALG/BV/05 PICS_ICMP_TRANSLATION Yes
5
TP/NAT64/LSN/RT/BV/01 TC_NAT64_LSN_RT_BV_01 PICS_RT_GRT_TO_VRF Yes
Routing Tables
TP/NAT64/LSN/RT/BV/02 TC_NAT64_LSN_RT_BV_02 PICS_RT_VRF_TO_GRT Yes
PICS_ANYCAST_
Anycast Addressing GATEWAYADDRESS_CONFIGUR Yes
TP/NAT64/LSN/AA/BV/01 TC_NAT64_LSN_AA_BV_01

ED
TP/NAT64/LSN/RED/BV/0 TC_NAT64_LSN_RED_BV_0
Redundancy PICS_REDUNDANCY Yes
1 1

TP/NAT64/LSN/LB/BV/01 TC_NAT64_LSN_LB_BV_01 Load Balancing PICS_LOAD_BALANCING Yes
TP/NAT64/LSN/FE/BV/01 TC_NAT64_LSN_FE_BV_01 Yes
Failure Events
TP/NAT64/LSN/FE/BV/0
...