ETSI TS 102 515 V1.1.2 (2008-01)

ETSI TS 102 515 V1.1.2 (2008-01)
Technical Specification


Methods for Testing and Specification (MTS);
Internet Protocol Testing (IPT): IPv6 Core Protocol;
Conformance Test Suite Structure and
Test Purposes (TSS&TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 102 515 V1.1.2 (2008-01)



Reference
RTS/MTS-IPT-005[2]-IPv6-CorTP
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

---------------------- Page: 2 ----------------------
3 ETSI TS 102 515 V1.1.2 (2008-01)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope.5
2 References.5
2.1 Normative references.5
2.2 Informative references.6
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations.6
4 Test Suite Structure (TSS).7
5 Test Purposes (TP).12
History .105

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 515 V1.1.2 (2008-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://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

---------------------- Page: 4 ----------------------
5 ETSI TS 102 515 V1.1.2 (2008-01)
1 Scope
The purpose of the present document is to provide Test Suite Structure and Test Purposes (TSS&TP) for conformance
tests of the core IPv6 protocol based on the requirements defined in the IPv6 requirements catalogue (TS 102 514 [2])
and written according to the guidelines of TS 102 351 [1], ISO/IEC 9646-2 [4] and ETS 300 406 [5].
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] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[4] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite specification".
[5] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[6] IETF RFC 1981: "Path MTU Discovery for IP version 6".
[7] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification".
[8] IETF RFC 2461: "Neighbor Discovery for IP Version 6 (IPv6)".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 515 V1.1.2 (2008-01)
[9] IETF RFC 2463: "Internet Control Message Protocol (ICMPv6) for the Internet Protocol
Version 6 (IPv6) Specification".
[10] IETF RFC 2675: "IPv6 Jumbograms".
[11] IETF RFC 3513: "Internet Protocol Version 6 (IPv6) Addressing Architecture".
2.2 Informative references
[12] IETF RFC 2374: "An IPv6 Aggregatable Global Unicast Address Format".
[13] IETF RFC 2462: "IPv6 Stateless Address Autoconfiguration".
[14] IETF RFC 2711: "IPv6 Router Alert Option".
[15] IETF RFC 2894: "Router Renumbering for IPv6".
[16] IETF RFC 3484: "Default Address Selection for Internet Protocol version 6 (IPv6)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
abstract test case: Refer to ISO/IEC 9646-1 [3].
Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [3].
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].
Lower Tester (LT): Refer to ISO/IEC 9646-1 [3].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATS Abstract Test Suite
IETF Internet Engineering Task Force
IPv6 Internet Protocol version 6
IUT Implementation Under Test
RC Requirements Catalogue
RQ Requirement
TP Test Purpose
TSS Test Suite Structure
UDP User Datagram Protocol
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 515 V1.1.2 (2008-01)
4 Test Suite Structure (TSS)
Test Purposes have been written for IPv6 nodes, hosts and routers according to the requirements (RQ) of the
requirements catalogue (RC) in TS 102 514 [2]. Test purposes have been written for behaviours requested with
"MUST" or "SHOULD", optional behaviour described with "MAY" or similar wording indicating an option has not
been turned into test purposes.
The test purposes have been divided into three groups:
Group 1: Node tests (all sub-groups)
Group 2: Host tests (only sub-groups that carry test purposes)
Group 3: Router tests (only sub-groups that carry test purposes)
The sub-grouping of these three groups follows the structure of the RC. Some of the sub-groups of the RC contained no
testable requirement. Headings for those sub-groups are in this test purpose document in the node group to give a full
view on the relation between RQ and TSS&TP.
Group 1  "Node tests (NT)"
Group 1.1  "Generate IPv6 packets (GIP)"
Group 1.1.1  "Generate Extension Header (GEH)"
Group 1.1.1.1  "Generate Destination Options Header (GDOH)"
Group 1.1.1.2  "Generate Routing Header (GRH)"
Group 1.1.1.3  "Generate Hop by Hop Header(GHHH)"
Group 1.1.2  "Generate IPv6 Header(GIH)"
Group 1.1.3  "Discover PMTU(DPMTU)"
Group 1.1.3.1  "Multicast PMTU Discovery (MPMTUD)"
Group 1.2  "Process IPv6 packets (PIP)"
Group 1.2.1  "Process Extension Headers (PEH)"
Group 1.2.1.1  "Process Fragment Packets (PFP)"
Group 1.2.1.2  "Process Routing Header (PRH)"
Group 1.2.1.3  "Process Hop-By-Hop Header (PHBHH)"
Group 1.2.1.4  "Process Extension Header Options (PEHO)"
Group 1.2.2  "Process IPv6 Header (PIP6)"
Group 1.2.2.1  "Process Hop Limit (PHL)"
Group 1.2.2.2  "Process Traffic Class (PTC)"
Group 1.2.2.3  "Process Flow Label (PHL)"
Group 1.2.2.4  "Process Checksum (PSC)"
Group 1.3  "Initialize (INI)"
Group 1.3.1  "Determine Default MTU (DDMTU)"
Group 1.3.2  "Configure Address (CA)"
Group 1.3.2.1  "Manual Address Configuration (MAC)"
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 515 V1.1.2 (2008-01)
Group 1.3.2.2  "Stateless Autoconfiguration (SLAC)"
Group 1.3.2.2.1 "Form Link-local Address (LLA)"
Group 1.3.2.2.2 "Process Invalid SA Syntax (PISAS)"
Group 1.3.2.3  "Stateful Autoconfiguration (SFAC)"
Group 1.3.2.4  "Simultaneous Stateless and Stateful Autoconfiguration (SSSAC)"
Group 1.3.2.5  "Detect Duplicate Address (DAD)"
Group 1.3.2.5.1 "Duplicate Address Detection Timers and Counters (DADTMR)"
Group 1.3.2.6  "Assign Global Address (GA)"
Group 1.3.2.6.1 "Use of M-Bit (UMB)"
Group 1.3.2.6.2 "Use of O-Bit (UOB)"
Group 1.3.2.6.3 "Process the Prefix Information Option (PPIO)"
Group 1.4  "Address use (AU)"
Group 1.5  "ICMPv6 Functions (ICF)"
Group 1.5.1  "Protect ICMP Messages from Attacks (PIMA)"
Group 1.5.2  "Process ICMPv6 Messages (PIM)"
Group 1.5.2.1  "Process ICMPv6 Information Messages (PIIM)"
Group 1.5.2.1.1 "Process Echo Reply Message (PERPM)"
Group 1.5.2.1.2 "Process Echo Request Message (PERQM)"
Group 1.5.2.2  "Process ICMPv6 Error Messages (PEM)"
Group 1.5.2.2.1 "Process Parameter Problem Message (PPPM)"
Group 1.5.2.2.2 "Process Time Exceeded Message (PTEM)"
Group 1.5.2.2.3 "Process Packet Too Big Message (PPTBM)"
Group 1.5.2.2.4 "Process Destination Unreachable Message (PDUM)"
Group 1.5.3  "Generate ICMPv6 Messages (GIM)"
Group 1.5.3.1  "Generate ICMPv6 Information Messages (GIIM)"
Group 1.5.3.1.1 "Generate Echo Request Message (GERQM)"
Group 1.5.3.2  "Generate ICMPv6 Error Messages (GIEM)"
Group 1.5.3.2.1 "Generate Parameter Problem Message (GPPM)"
Group 1.5.3.2.2 "Generate Time Exceeded Message (GTEM)"
Group 1.5.3.2.3 "Generate Message Too Big Message (GMTBM)"
Group 1.5.3.2.4 "Generate Destination Unreachable Message (GTEM)"
Group 1.5.3.2.4.1 "Destination Unreachable Code Field Value (DUCFV)"
Group 1.5.3.2.5 "Limit ICMP Bandwidth and Forwarding Costs (LIBFC)"
Group 1.5.3.3  "Determine ICMPv6 Message Source Address (DIMSA)"
Group 1.6  "Neighbour Discovery (ND)"
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 515 V1.1.2 (2008-01)
Group 1.6.1  "ND Protocol Constants and Default Values (NDPCDV)"
Group 1.6.2  "Address Resolution (AR)"
Group 1.6.2.1  "Address Resolution Behavior (ARB)"
Group 1.6.2.2  "Address Resolution Data Queue Handling (ARDQH)"
Group 1.6.3  "Neighbor Unreachability Detection (NUD)"
Group 1.6.3.1  "Neighbour Reachability Process (NRP)"
Group 1.6.3.1.1 "Start Neighbor Reachability Determination (SNRD)"
Group 1.6.3.1.2 "Determine Neighbor Reachability (DNR)"
Group 1.6.3.1.3 "Invalid Reachability Indications (IRI)"
Group 1.6.3.2  "Neighbor Reachability Probing (NRP)"
Group 1.6.4  "Next Hop Determination (NHD)"
Group 1.6.5  "Using Options in Neighbor Discovery Messages (UONDM)"
Group 1.6.6  "Process Neighbor Discovery Messages (PND)"
Group 1.6.6.1  "Process Neighbor Solicitation (PND)"
Group 1.6.6.1.1 "Discover Neighbor by NS (DNNS)"
Group 1.6.6.1.2 "Process Proxy NS (PPNS)"
Group 1.6.6.1.3 "Process Anycast NS (PANS)"
Group 1.6.6.1.4 "Process NS for Address Resolution (PNSAR)"
Group 1.6.6.1.5 "Process Field Anomalies in NS (NSFA)"
Group 1.6.6.1.6 "Process Option Anomalies in NS (NSOA)"
Group 1.6.6.2  "Process Neighbor Advertisement (PNA)"
Group 1.6.6.2.1 "Process Solicited Neighbor Advertisement (PSNA)"
Group 1.6.6.2.2 "Process Unsolicited Neighbor Advertisement (PUNA)"
Group 1.6.6.2.3  "Discover Neighbor by NA (DNNA)"
Group 1.6.6.2.4 "Process Field Anomalies in NA (PFANA)"
Group 1.6.6.2.5 "Process Option Anomalies in NA (POANA)"
Group 1.6.6.3  "Process Router Solicitation (PRA)"
Group 1.6.6.3.1 "Discover Neighbor by RS (DNRS)"
Group 1.6.6.3.2 "Router Processing of RS (RPRS)"
Group 1.6.6.3.3 "Host Processing of RS (HPRS)"
Group 1.6.6.3.4 "Process Field Anomalies in RS (PFARS)"
Group 1.6.6.3.5 "Process Option Anomalies in RS (POARS)"
Group 1.6.6.4  "Process Router Advertisement (PRA)"
Group 1.6.6.4.1 "Discover Neighbor by RA (DNRA)"
Group 1.6.6.4.2 "Router Processing of RA (RPRA)"
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 515 V1.1.2 (2008-01)
Group 1.6.6.4.3 "Host Processing of RA (HPRA)"
Group 1.6.6.4.4 "Process Field Anomalies in RA (PFARA)"
Group 1.6.6.4.5 "Process Option Anomalies in RA (PAORA)"
Group 1.6.6.5  "Process Redirect Message (PRM)"
Group 1.6.6.5.1 "Discover Neighbor by Redirect Message (DNRM)"
Group 1.6.6.5.2 "Router Processing of Redirect Message (RPRM)"
Group 1.6.6.5.3 "Host Processing of Redirect Message (HPRM)"
Group 1.6.6.5.4 "Process Field Anomalies in Redirect Message (PFARM)"
Group 1.6.6.5.5 "Process Option Anomalies in Redirect Message (POARM)"
Group 1.6.7  "Generate Neighbor Discovery Messages (GNDM)"
Group 1.6.7.1  "Generate Neighbor Solicitation (GNS)"
Group 1.6.7.1.1 "Generate Neighbor Solicitation Header (GNSH)"
Group 1.6.7.1.2 "Generate Neighbor Solicitation Option (GNSO)"
Group 1.6.7.1.3 "Generate NS for Address Resolution (GNSAR)"
Group 1.6.7.2  "Generate Neighbor Advertisement (GNA)"
Group 1.6.7.2.1 "Generate Unsolicited Neighbor Advertisement (GUNA)"
Group 1.6.7.2.1.1 "Form Unsolicited NA Header (FUNAH)"
Group 1.6.7.2.1.2 "Generate Unsolicited Proxy NA (GUPNA)"
Group 1.6.7.2.1.3 "Generate Unsolicited Anycast NA (GUANA)"
Group 1.6.7.2.2 "Form Neighbor Advertisement Header (FNAH)"
Group 1.6.7.3  "Generate Router Solicitation (GRA)"
Group 1.6.7.4  "Generate Router Advertisement (GRA)"
Group 1.6.7.5  "Generate Redirect Message (GRM)"
Group 1.7  "Address Architecture (AA)"
Group 1.8  "Jumbograms (JG)"
Group 1.8.1  "TCP Jumbograms (TCPJG)"
Group 1.8.2  "UDP Jumbograms (UDPJG)"
Group 1.8.3  "Process Jumbograms (PJG)"
Group 1.8.4  "Generate Jumbograms (GJG)
Group 2  "Host (HS)"
Group 2.3  "Initialize (INI)"
Group 2.3.2.2.1 "Form Link-local Address (LLA)"
Group 2.3.2.6  "Assign Global Address (GA)"
Group 2.3.2.6.1 "Use of M-bit (UMB)"
Group 2.3.2.6.2 "Use of O-Flag (UOB)"
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 515 V1.1.2 (2008-01)
Group 2.3.2.6.3 "Process the Prefix Information Option (PFX)"
Group 2.6  "Neighbour Discovery (ND)"
Group 2.6.1  "ND Protocol Constants and Default Values (NDPCDV)"
Group 2.6.6.1.4 "Process NS for Address Resolution (PNSAR)"
Group 2.6.6.3.3 "Host Processing of RS (HPRS)"
Group 2.6.6.4.3 "Host Processing of RA (HPRA)"
Group 2.6.6.4.5 "Process Option Anomalies in RA (POARA)"
Group 2.6.6.5.3 "Host Processing of Redirect Message (HPRM)"
Group 2.6.6.5.4 "Process Field Anomalies in Redirect Message (PFARM)"
Group 2.6.6.5.5 "Process Option Anomalies in Redirect Message (POARM)"
Group 2.6.7.3  "Generate Router Solicitation (GRS)"
Group 2.6.7.3.1 "Generate Router Solicitation Header (GRSH)"
Group 2.6.7.3.2 "Generate RS Source Link-layer Address Option (GRSSLAO)"
Group 2.6.7.3.3 "Router Solicitation Behavior (RSB)"
Group 3  "Router (RT)"
Group 3.2  "Process IPv6 packets (PIP)"
Group 3.2.1.2  "Process Routing Header (PRH)"
Group 3.3  "Initialize (INI)"
Group 3.3.2  "Configure Address {CA)"
Group 3.3.2.2  "Stateless Autoconfiguration (SAC)"
Group 3.3.2.2.1 "Form Link-local Address (LLA)"
Group 3.5  "ICMPv6 Functions (ICF)"
Group 3.5.2  "Process ICMPv6 Messages (PIM)"
Group 3.5.3.2.2  "Generate Time Exceeded Message (GTEM)"
Group 3.5.3.2.3  "Generate Message Too Big Message (GMTBM)"
Group 3.5.3.2.4  "Generate Destination Unreachable Message (GTEM)"
Group 3.5.3.2.4.1 "Destination Unreachable Code Field Value (DUCFV)"
Group 3.6  "Neighbour Discovery (ND)"
Group 3.6.1  "ND Protocol Constants and Default Values (NDPCDV)"
Group 3.6.2.1  "Address Resolution Behavior (ARB)"
Group 3.6.3.1.1  "Start Neighbor Reachability Determination (SNRD)"
Group 3.6.6.1.4  "Process NS for Address Resolution (PNSAR)"
Group 3.6.6.3  "Process Router Solicitation (PRS)"
Group 3.6.6.3.1 "Discover Neighbor by RS (DNRS)"
Group 3.6.6.3.2 "Router Processing of RS (RPRS)"
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 515 V1.1.2 (2008-01)
Group 3.6.6.3.4  "Process Field Anomalies in RS (PFARS)"
Group 3.6.6.3.5  "Process Option Anomalies in RS (POARS)"
Group 3.6.6.5.2  "Router Processing of Redirect Message (RPRM)"
Group 3.6.7.2  "Generate Neighbor Advertisement (GNA)"
Group 3.6.7.2.1.2 "Generate Unsolicited Proxy NA (GUPNA)"
Group 3.6.7.4  "Generate Router Advertisement (GRA)"
Group 3.6.7.4.1 "Form Router Advertisement Header (FRAH)"
Group 3.6.7.4.2 "Form Router Advertisement Options (FRAO)"
Group 3.6.7.4.2.1 "RA MTU Option (RAMTUO)"
Group 3.6.7.4.2.2 "RA Source Link-layer Address Option (RASLAO)"
Group 3.6.7.4.2.3 "RA Prefix Information Option (RAPIO)"
Group 3.6.7.4.3 "Router Advertisement Behavior (RAB)"
Group 3.6.7.4.3.1 "Startup Router Advertisement Behavior (SRAB)"
Group 3.6.7.4.3.1.1 "AdvCurHopLimit (ACHL)"
Group 3.6.7.4.3.1.2 "AdvDefaultLifetime (ADL)"
Group 3.6.7.4.3.1.3 "AdvManagedFlag (AMF)"
Group 3.6.7.4.3.1.4 "AdvOtherConfigFlag (AOCF)"
Group 3.6.7.4.3.1.5 "AdvReachableTime (ART)"
Group 3.6.7.4.3.1.6 "AdvRetransTimer (ADRT)"
Group 3.6.7.4.3.1.7 "MaxRtrAdvInterval (MAXRAI)"
Group 3.6.7.4.3.1.8 "MinRtrAdvInterval (MINRAI)"
Group 3.6.7.4.3.2 "Router Advertisement Behavior on Reconfiguration (RABR)"
Group 3.6.7.5  "Generate Redirect Message (GRM)"
Group 3.6.7.5.1 "Generate Redirect Options (GRO)"
Group 3.6.7.5.2 "Determine Redirect Target Address Field (DRTA)"
5 Test Purposes (TP)
The test purposes have been written in the formal notation TPlan as described in annex A of TS 102 351 [1]
TSS   : COR
Title  : 'IPv6 Core TSS and TP'
Version : 1.0.1
Date  : 12.09.2007
Author : 'STF276'
-- *****************************


--***Cross references***

xref RQ_000 { RFC 2460, RF C2461, RFC 2463, RFC 2463, RFC 3513, RFC 1981, RFC 2675 }

--***Definitions***

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 102 515 V1.1.2 (2008-01)
def word generates
def word ignores
def word discards
def word accepts
def word set

def unit seconds

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Group 1 'Node tests (NT)'
Group 1.1 'Generate IPv6 packets (GIP)'
Group 1.1.1 'Generate Extension Header (GEH)'

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1092_01
summary : 'Send 59 in last IPv6 header'
RQ Ref : RQ_COR_1092
TC Ref : TC_COR_1092_01

with { IUT 'Node' and 'IUT ready to generate IPv6 packets'
 }

ensure that
{

when { IUT generates 'IPv6 packet'
   containing 'one or more extension headers'
   }

then { IUT sends 'IPv6 packet'
   containing 'a Next Header field in the last extension header' indicating 59
  }
}

Group 1.1.1.1 'Generate Destination Options Header(GDOH)'

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1089_01
summary : 'Tests destination options header, includes COR_1090 and COR_1091'
RQ Ref : RQ_COR_1089
TC Ref : TC_COR_1089_01

with { IUT 'Node' and 'IUT ready to generate IPv6 packets'
 }

ensure that
{

when { IUT generates 'IPv6 packet'
   containing 'a destination options header'
   }

then { IUT sends 'IPv6 packet'
   containing 'a Next Header field in header preceeding the destination options header'
indicating 60
   and containing 'a correctly coded destination options header'
  }
}

End group 1.1.1.1
Group 1.1.1.2 'Generate Routing Header(GRH)'

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1034_01
summary : 'Tests routing header, includes COR_1035, COR_1036, COR_1037, COR_1038, COR_1043, COR_1047
and COR_1048'
RQ Ref : RQ_COR_1034
TC Ref : TC_COR_1034_01

with { IUT 'Node' and 'IUT ready to generate IPv6 packets'
 }

ensure that
{

ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 102 515 V1.1.2 (2008-01)
when { IUT generates 'IPv6 packet'
   containing 'a routing header'
   }

then { IUT sends 'IPv6 packet'
   containing 'a Next Header field in header preceeding the routing header' indicating 43
   and containing 'a correctly coded routing header'
  }
}

End group 1.1.1.2
Group 1.1.1.3 'Generate Hop by Hop Header(GHHH)'

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1008_01
summary : 'Tests hop by hop header, includes COR_1009, COR_1032 and COR_1033'
RQ Ref : RQ_COR_1008
TC Ref : TC_COR_1008_01

with { IUT 'Node' and 'IUT ready to generate IPv6 packets'
 }

ensure that
{

when { IUT generates 'IPv6 packet'
   containing 'a hop by hop header'
   }

then { IUT sends 'IPv6 packet'
   containing 'a Next Header field in the IPv6 header' indicating 0
   and containing 'a correctly coded hop by hop header'
  }
}

End group 1.1.1.3
End group 1.1.1
Group 1.1.2 'Generate IPv6 Header(GIH)'

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1000_01
summary : 'Tests IPv6 header, includes COR_1001'
RQ Ref : RQ_COR_1000
TC Ref : TC_COR_1000_01

with { IUT 'Node' and 'IUT ready to generate IPv6 packets'
 }

ensure that
{

when { IUT generates 'IPv6 packet'
   }

then { IUT sends 'IPv6 packet'
   containing 'a IPv6 header' indicating 'correct length and next header values'
  }
}

End group 1.1.2
Group 1.1.3 'Discover PMTU(DPMTU)'

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1806_01
summary : 'Tests reduction of PMTU on Packet Too Big message, includes COR1808 and COR_1818'
RQ Ref : RQ_COR_1806
TC Ref : TC_COR_1806_01

with { IUT 'Node' and 'IUT ready to generate IPv6 packets'
 }

ensure that
{

when { IUT generates 'IPv6 packet'
ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 102 515 V1.1.2 (2008-01)
   containing 'packet of size up to the known MTU of the first hop'

  and IUT receives 'Packet Too Big message'
   containing 'an MTU field set to a value smaller than the MTU used for sending'
   }

then { IUT sends 'IPv6 packet'
   containing 'packet of size up to the received MTU'
  }
}

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1821_01
summary : 'Tests reaction on Packet Too Big message with MTU less than minimum, includes COR1822'
RQ Ref : RQ_COR_1821
TC Ref : TC_COR_1821_01

with { IUT 'Node' and 'IUT ready to generate IPv6 packets'
 }

ensure that
{

when { IUT generates 'IPv6 packet'
   containing 'packet of size up to the known MTU of the first hop'

 and IUT receives 'Packet Too Big message'
   containing 'an MTU field set to a value smaller than the IPv6 minimum link MTU'
   }

then { IUT sends 'IPv6 packet'
   containing 'a fragment header'
  }
}

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1823_01
summary : 'Tests reaction on Packet Too Big message with MTU higher than used MTU'
RQ Ref : RQ_COR_1823
TC Ref : TC_COR_1823_01

with { IUT 'Node' and 'IUT ready to generate IPv6 packets'
 }

ensure that
{

when { IUT generates 'IPv6 packet'
   containing 'packet of size up to the known MTU of the first hop'

 and IUT receives 'Packet Too Big message'
   containing 'an MTU field set to a value higher than the used MTU'
   }

then { IUT sends 'IPv6 packet'
   containing 'packet of size up to the known MTU of the first hop'
  }
}

Group 1.1.3.1 'Multicast PMTU Discovery (MPMTUD)'

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1814_01
summary : 'Tests reaction on several Packet Too Big messages when using multicast sending'
RQ Ref : RQ_COR_1814
TC Ref : TC_COR_1814_01

with { IUT 'Node' and 'IUT ready to generate IPv6 packets'
 }

ensure that
{

when { IUT generates 'IPv6 packet'
   containing 'packet of size up to the known MTU of the first hop'
ETSI

---------------------- Page: 15 ----------------------
16 ETSI TS 102 515 V1.1.2 (2008-01)
   and containing 'destination address' indicating 'multicast address'

 and IUT receives 'multiple Packet Too Big messages'
   containing 'MTU fields set to values smaller than the used MTU'
   }

then { IUT sends 'IPv6 packet'
   containing 'packet of size up to the smallest received MTU'
  }
}

End group 1.1.3.1
End group 1.1.3
End group 1.1
Group 1.2 'Process IPv6 packets (PIP)'

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_8814_01
summary : 'Tests reaction on unsupported jumbogram'
RQ Ref : RQ_COR_8814
TC Ref : TC_COR_8814_01

with { IUT 'Node' and 'IUT ready to process IPv6 packets'
 }

ensure that
{

when { IUT receives 'IPv6 packet'
   containing 'next header' indicating 'Hop-by-Hop Options'
   and containing 'payload length' indicating 0
   }

then { IUT sends 'ICMP Parameter Problem message'
   containing 'code' indicating 0 'erroneous header field encountered'
   and containing 'pointer' indicating 'high-order octet of the IPv6 payload length'
   and IUT ignores 'received packet'
  }
}

Group 1.2.1 'Process Extension Headers (PEH)'

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

TP Id  : TP_COR_1010_01
summary : 'Tests reaction on unrecognized Next Header value'
RQ Ref : RQ_COR_1010
TC Ref : TC_COR_10
...