|
GROUP REPORT
6TiSCH Interoperability Test Specifications
Disclaimer
The present document has been produced and approved by the IPv6 Integration (IP6) ETSI Industry Specification Group (ISG)
and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.
---------------------- Page: 1 ----------------------
2 ETSI GR IP6 017 V1.1.1 (2019-01)
Reference
DGR/IP6-0017
Keywords
6TiSCH, 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:
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
If you find errors in the present document, please send your comment to one of the following services:
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.
© ETSI 2019.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI GR IP6 017 V1.1.1 (2019-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 . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 User defined clause(s) from here onwards . 8
4.1 User defined subdivisions of clause(s) from here onwards . 8
4.1.1 Introduction. 8
4.1.2 The test description pro forma . 9
4.2 Tooling . 9
4.3 Test Description naming convention . 10
4.4 6TiSCH Tests Summary . 10
5 6TiSCH Test Configurations . 11
5.1 Node Under Test (NUT) . 11
5.2 System under Test (SUT) . 12
5.2.1 Single-hop scenario. 12
5.2.2 Multi-hop_1 scenario . 12
5.2.3 Multi-hop_2 scenario . 13
5.2.4 Star scenario. 13
5.3 Golden Device . 13
5.3.1 Introduction. 13
5.3.2 GD/root . 14
5.3.3 GD/root/SEC. 14
5.3.4 GD/sniffer . 14
5.3.5 Configuring Script . 14
6 Test Descriptions . 16
6.1 Synchronization . 16
6.2 Minimal tests . 18
6.3 RPL features . 21
6.4 L2SEC . 23
6.5 6top Protocol (6P) . 24
6.6 6LoRH . 28
6.7 SF0 . 31
6.8 SECJOIN . 32
6.9 BBR-ND . 36
Annex A: Default Parameters . 40
A.1 IEEE 802.15.4 Default Parameters . 40
A.1.1 Address length . 40
A.1.2 Frame version . 40
A.1.3 PAN ID compression and sequence number . 40
A.1.4 Payload termination IE . 40
A.1.5 IANA for 6P IE related . 40
A.1.6 6P Timeout . 41
A.1.7 RPL Operation Mode . 41
A.2 Default Security Keys . 41
ETSI
---------------------- Page: 3 ----------------------
4 ETSI GR IP6 017 V1.1.1 (2019-01)
A.3 IP in IP Encapsulation . 41
A.3.1 Context . 41
A.3.2 Echo Request sent from DR to 6N1 (containing source routing header). 41
A.3.3 Echo Reply sent from 6N2 to 6N1 (containing RPL option) . 42
Annex B: Bibliography . 44
Annex C: Authors & contributors . 45
History . 46
ETSI
---------------------- Page: 4 ----------------------
5 ETSI GR IP6 017 V1.1.1 (2019-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (https://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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) IPv6 Integration (IP6).
Modal verbs terminology
In the present document "should", "should not", "may", "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 GR IP6 017 V1.1.1 (2019-01)
1 Scope
The present document aims to provide guidelines for performing 6TiSCH Conformance and Interoperability Tests. To
this aim, it describes:
• The testbed architecture showing which IETF 6TiSCH systems and components are involved, and how they
are going to inter-work in the interoperation focus.
• The configurations used during test sessions, including the relevant parameter values of the different layers
(IEEE 802.15.4e TSCH and RPL).
• The interoperability test descriptions, describing the scenarios, which the participants will follow to perform
the tests.
• The guidelines for participants on how to use the golden device to test against their implementation.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
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
referenced 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] IEEE 802.15.4e™: "IEEE Standard for Local and metropolitan area networks--
Part 15.4: Low-Rate Wireless Personal Area Networks (LR-WPANs) Amendment 1: MAC
sublayer".
[i.2] IETF RFC 8180: "Minimal 6TiSCH Configuration", IETF 6TiSCH Working Group,
X. Vilajosana, K. Pister. June 2015.
[i.3] IETF RFC 6550: "RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks", T. Winter,
P. Thubert, A. Brandt, J. Hui, R. Kelsey, P. Levis, K. Pister, R. Struik, JP. Vasseur, and
R. Alexander, March 2012.
[i.4] IETF RFC 6552: "Objective Function Zero for the Routing Protocol for Low-Power and Lossy
Networks (RPL)", P. Thubert, March 2012.
[i.5] IETF RFC 6553: "The Routing Protocol for Low-Power and Lossy Networks (RPL) Option for
Carrying RPL Information in Data-Plane Datagrams", J. Hui, and JP. Vasseur, March 2012.
[i.6] IETF RFC 6554: "An IPv6 Routing Header for Source Routes with the Routing Protocol for
Low-Power and Lossy Networks (RPL)", J. Hui, JP. Vasseur, D. Culler, and V. Manral,
March 2012.
[i.7] IETF RFC 4919: "IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs):
Overview, Assumptions, Problem Statement, and Goals", N. Kushalnagar, G. Montenegro, and C.
Schumacher, August 2007.
ETSI
---------------------- Page: 6 ----------------------
7 ETSI GR IP6 017 V1.1.1 (2019-01)
[i.8] draft-ietf-6tisch-6top-protocol-09: "6TiSCH Operation Sublayer (6top)", IETF 6TiSCH Working
Group, Qin Wang, Xavier Vilajosana, November 2015.
[i.9] draft-ietf-6lo-routing-dispatch-02: "6LoWPAN Routing Header And Paging Dispatches", IETF 6lo
Working Group, P. Thubert, C. Bormann, L. Toutain, January 2016.
[i.10] IETF RFC 7554: "Using IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the Internet
of Things (IoT): Problem Statement", T. Watteyne, M. R. Palattella, L. A. Grieco, May 2015.
[i.11] ETSI EG 202 237: "Methods for Testing and Specification (MTS); Internet Protocol Testing
(IPT); Generic approach to interoperability testing".
[i.12] ETSI EG 202 568: "Methods for Testing and Specification (MTS); Internet Protocol Testing
(IPT); Testing: Methodology and Framework".
[i.13] IETF RFC 6282: "Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based
Networks".
[i.14] IETF RFC 6775: "Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal
Area Networks (6LoWPANs)".
[i.15] draft-ietf-6tisch-6top-sf0-00: "6TiSCH 6top Scheduling Function Zero / Experimental (SFX)".
[i.16] draft-ietf-6tisch-6top-protocol-04: "6TiSCH Operation Sublayer (6top) Protocol (6P)".
[i.17] IEEE 802.15.4-2015™: "IEEE Standard for Low-Rate Wireless Networks".
[i.18] draft-ietf-6tisch-6top-protocol-01: "6top Protocol (6P)".
[i.19] draft-ietf-6tisch-minimal-security-03: "Minimal Security Framework for 6TiSCH".
[i.20] draft-ietf-6lo-backbone-router-01: "IPv6 Backbone Router".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
DAG root (DR): 6TiSCH Node acting as root of the DAG in the 6TiSCH network topology
6TiSCH Node (6N): any node within a 6TiSCH network other than the DAG root
NOTE: It may act as parent and/or child node within the DAG. It communicates with its children and it parent
using the 6TiSCH minimal schedule, or any other TSCH schedule. In the test description, the term is used
to refer to a non-DAG root node.
System Under Test (SUT): any composition of a number of Nodes Under Test implemented by different vendors
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK ACKnowledgement packet
ARO Address Registration Option
BBR BackBone Router
ETSI
---------------------- Page: 7 ----------------------
8 ETSI GR IP6 017 V1.1.1 (2019-01)
BBR-ND BackBone Router – Neighbor Discovery
DAC Duplicate Address Confirmation
DAD Duplicate Address Detection
DAG Directed Acyclic Graph
DAO RPL Destination Advertisement Object
DAR Duplicate Address Request
DG DaG root
DIO RPL DAG Information Object
DODAG Destination Oriented DAG
DR Dag Root
EARO Extended ARO
EB Enhanced Beacon packet
F Frequency
GD Golden Device
GD/root Golden Device acting as DAG root
GD/root/SEC GD/root with enabled security options
GD/sniffer Golden Device acting as PS
GPIO General-Purpose Input/Output
IE Information Element
IOC InterOperation and Conformance
IOP InterOPeration
IP Internet Protocol
JP Join Protocol
JRC Join Registrar/Coordinator
KA Keep-Alive message
LA Logic Analyser
LBR Low-Power and Lossy Network Border Router
MIC Message Intergrity Check
MMCX Micro-Miniature CoaXial
NA Neighbor Advertissement
ND Neighbor Discovery
NS Neighbor Solicitation
NUT Node Under Test
OSC OSCilloscope
PAN Personal Area Network
PANID PAN IDentifier
PS Packet Sniffer
RPI RPL Packet Information
RPL Routing Protocol for Low power and Lossy Networks
SEC SECurity
SMA SubMiniature version A
SUT System Under Test
SYN SYNchronization
TD Test Description
TID Transaction IDentifier
u.FL micro Flex
UDP User Datagram Protocol
4 User defined clause(s) from here onwards
4.1 User defined subdivisions of clause(s) from here onwards
4.1.1 Introduction
According to well-established test methodology, such as ETSI EG 202 237 [i.11] and ETSI EG 202 568 [i.12], it is
possible to distinguish two different and complementary ways for testing devices which implement a given standard:
Conformance and Interoperability testing.
ETSI
---------------------- Page: 8 ----------------------
9 ETSI GR IP6 017 V1.1.1 (2019-01)
Conformance Testing aims at checking whether a product correctly implements a particular standardized protocol.
Thus, it establishes whether or not the protocol Implementation Under Test (IUT) meets the requirements specified for
the protocol itself. For example, it will test protocol message contents and format as well as the permitted sequences of
messages.
Interoperability Testing aims at checking whether a product works with other similar products. Thus, it proves that end-
to-end functionality between (at least) two devices (from different vendors) is, as required by the standard(s) on which
those devices are based.
Conformance testing in conjunction with interoperability testing provides both the proof of conformance and the
guarantee of interoperation. ETSI EG 202 237 [i.11] and ETSI EG 202 568 [i.12] describe several approaches on how
to combine these two methods. The most common approach consists in Interoperability Testing with Conformance
Checks, where reference points between the devices under test are monitored to verify the appropriate sequence and
contents of protocol messages, API calls, interface operations, etc. This will be the approach used by the 6TiSCH
Plugtests.
The test session will be mainly executed between two devices from different vendors. For some test descriptions, it may
be necessary to have more than two devices involved. The information about the test configuration, like the number of
devices or the roles required are indicated in clause 6.
4.1.2 The test description pro forma
The test descriptions are provided in pro forma tables, which include the different Steps of the Test Sequence. The Steps
may be of different types, depending on their purpose:
• A stimulus corresponds to an event that triggers a specific protocol action on a NUT, such as sending a
message.
• A configure corresponds to an action to modify the NUT or SUT configuration.
• An IOP check (IOP stands for "Interoperation") consists of observing that one NUT behaves as described in
the standard: i.e. resource creation, update, deletion, etc. For each IOP check in the Test Sequence, a result is
recorded.
• The overall IOP Verdict will be considered PASS if all the IOP checks in the sequence are PASS.
In the context of Interoperability Testing with Conformance Checks, an additional step type, CON checks (CON stands
for "Conformance") may be used to verify the appropriate sequence and contents of protocol messages, API calls,
interface operations, etc.
In this case, the IOP Verdict will be PASS if all the IOP checks are PASS, and CON Verdict will be PASS if all the
CON checks are PASS. The IOP/CON Verdict will be FAIL if at least one of the IOP/CON checks is FAIL.
Every IOP check and CON check of a test description should be performed using a trace created by a monitor tool, as
described in clause 4.2.
4.2 Tooling
Participant may use their own tools for logging and analysing messages for the "check" purpose. The monitor tools
include:
Packet Sniffer: An IEEE 802.15.4e compliant Packet Sniffer (PS) and the relevant tools to be able to analyse packets
exchanges over the air. Participant will be free to use their own PS, or a GD/sniffer made available by the 6TiSCH Plug
tests organizers.
Logic Analyser or Oscilloscope: A Logic Analyser (LA) to display the state of a GPIO (a pin on a board). Tools to
convert the captured data into timing diagrams are necessary.
Debug Pins (GPIOs): To the scope of the tests, at least two programmable Digital I/O pins are recommended. One of
the Debug pins should be used to track the slotted activity, and thus, be toggled at the beginning of each timeslot. The
other debug pin should be toggled every time an action as defined by the timeslot template happens, i.e. the debug pin
will toggle at tsTxOffset, tsRxAckDelay, etc.
ETSI
---------------------- Page: 9 ----------------------
10 ETSI GR IP6 017 V1.1.1 (2019-01)
Antenna Attenuators: The attenuators (which can be of different type: SMA, MMCX, u.FL) will be used to simulate
distance between nodes. By doing so, multi-hop topologies can be constructed without the need of physically separating
nodes. An attenuator can connect two motes using a pigtail (little wire) with the corresponding antenna connector
(e.g. SMA, MMCX, u.FL, etc.). Several attenuators (10 dB, 20 dB, 30 dB, etc.) will be used. It is also preferable that
they can be connected in a daisy chain.
4.3 Test Description naming convention
All the tests described in the present document, which will be performed during the Plugtests, can be classified in
different groups, based on the type of features they verify. There are four different groups of tests: Synchronization
(SYN), Packet Format (FORMAT), RPL features (RPL), and Security (SEC).
For each group, several tests are performed.
To identify each test, this TD uses a Test ID following the following naming convention:
TD_6TiSCH__.
4.4 6TiSCH Tests Summary
Table 1: 6TiSCH Tests
Test Test ID Test Summary Test Group
Number
1 TD_6TiSCH_SYN_01 Check that a 6N synchronizes and keeps synchronized SYN
by receiving EBs.
5 TD_6TiSCH_MINIMAL_01 Check the format of the IEEE 802.15.4e [i.1] EB packet MINIMAL
is correctly assembled.
6 TD_6TiSCH_MINIMAL_02 Check the timing template of TSCH time slot defined in MINIMAL
IETF RFC 8180 [i.2] is correctly implemented.
7 TD_6TiSCH_MINIMAL_03 Check channel hopping is correctly implemented MINIMAL
according to IETF RFC 8180 [i.2].
8 TD_6TiSCH_MINIMAL_04 Check the number of retransmissions is implemented MINIMAL
following IETF RFC 8180 [i.2].
9 TD_6TiSCH_MINIMAL_05 Check the minimal schedule is implemented according MINIMAL
to IETF RFC 8180 [i.2].
10 TD_6TiSCH_MINIMAL_06 Check the 6N sets its slot frame size correctly when MINIMAL
joining the network.
11 TD_6TiSCH_RPL_01 Check the value of EB join priority of a child 6N and a RPL
parent DR.
12 TD_6TiSCH_RPL_02 Check the rank of 6N is computed correctly according to RPL
IETF RFC 8180 [i.2].
13 TD_6TiSCH_RPL_03 Check a 6N child changes its time source neighbour RPL
(parent) correctly.
14 TD_6TiSCH_RPL_04 Check the format of RPL DIO message. RPL
15 TD_6TiSCH_RPL_05 Check the format of RPL DAO message. RPL
16 TD_6TiSCH_RPL_06 Check IP extension header in 6LoWPAN. RPL
19 TD_6TiSCH_6P_01 Check that a 6N can ADD a cell in the schedule 6P
according to draft-ietf-6tisch-6top-protocol-09 [i.8].
20 TD_6TiSCH_6P_02 Check that a 6N can COUNT the cells allocated in the 6P
schedule to a given neighbour, according to
draft-ietf-6tisch-6top-protocol-09 [i.8].
21 TD_6TiSCH_6P_03 Check that a 6N can obtain the LIST of cells in the 6P
schedule, according to draft-ietf-6tisch-6top-protocol-09.
22 TD_6TiSCH_6P_04 Check that a 6N can CLEAR the schedule of a node, 6P
according to draft-ietf-6tisch-6top-protocol-09.
23 TD_6TiSCH_6P_05 Check that a 6N can DELETE a cell in the schedule 6P
according to draft-ietf-6tisch-6top-protocol-09 [i.8].
24 TD_6TiSCH_6P_06 Check the correct implementation of the 6P timeout 6P
(after a 6P request is received), according to
draft-ietf-6tisch-6top-protocol-09 [i.8]
25 TD_6TiSCH_6LoRH_01 Check that the source routing header is correctly 6LoRH
encoded as a 6LoRH Critical RH3, according to
draft-ietf-6lo-routing-dispatch-02 [i.9].
ETSI
---------------------- Page: 10 ----------------------
11 ETSI GR IP6 017 V1.1.1 (2019-01)
Test Test ID Test Summary Test Group
Number
26 TD_6TiSCH_6LoRH_02 Check that, when the packet's sent towards the DR, the 6LoRH
RPL Information Option is correctly encoded as a
6LoRH RPI, according to
draft-ietf-6lo-routing-dispatch-02 [i.9].
27 TD_6TiSCH_6LoRH_03 Check that, when the packet's travel inside the RPL 6LoRH
domain, the IP in IP 6LoRH will not be presented in the
packet.
28 TD_6TiSCH_6LoRH_04 Check that, when the packet travel outside a RPL 6LoRH
domain, IP in IP 6LoRH is present in the packet.
29 TD_6TiSCH_SF0_01 Check SF0 initial overprovision of cells at bootstrap, SF0
according to draft-ietf-6tisch-6top-sf0-00 [i.15].
30 TD_6TiSCH_SF0_02 Check SF0 progressive allocation of cells as traffic SF0
demand increases, according to
draft-ietf-6tisch-6top-sf0-00 [i.15].
31 TD_6TiSCH_SF0_03 Check SF0 progressive de-allocation of slots as traffic SF0
demand decreases, according to
draft-ietf-6tisch-6top-sf0-00 [i.15].
32 TD_6TiSCH_SECJOIN_01 check that the join request is correctly received at the SECJOIN
JRC.
33 TD_6TiSCH_SECJOIN_02 check that the join response is correctly received at the
...