ETSI TS 102 518 V1.1.1 (2008-02)

Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv4 to IPV6 Transitioning; Conformance Test Suite Structure and Test Purposes (TSS&TP)

DTS/MTS-IPT-020-IPv6-TrsTSS_TP

General Information

• Status: Published
• Publication Date: 04-Feb-2008
• Technical Committee: MTS IPT - IP Testing Group
• Current Stage: 12 - Completion
• Due Date: 07-Feb-2008
• Completion Date: 05-Feb-2008

Standards Content (Sample)

ETSI TS 102 518 V1.1.1 (2008-02)
Technical Specification


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


�

---------------------- Page: 1 ----------------------
2 ETSI TS 102 518 V1.1.1 (2008-02)



Reference
DTS/MTS-IPT-020-IPv6-TrsTSS_TP
Keywords
conformance, IP, IPv6, testing, TSS&TP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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 518 V1.1.1 (2008-02)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope.5
2 References.5
2.1 Normative references.5
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations.6
4 Test Suite Structure (TSS).6
Annex A (normative): Test Purposes (TP).8
A.1 IPv6 Transitioning - RFC 2529.8
A.1.1 Node Tests.8
A.1.1.1 Encapsulating IPv4 Header frame format validation .8
A.1.1.2 Stateless Auto-configuration and Link-local addresses on 6over4 .9
A.1.1.3 Source and Target Link layer address options .9
A.1.1.4 IPv6 Multicast address mapping to IPv4 multicast address to support Neighbor Discovery.11
A.1.2 Route Tests.12
A.1.2.1 Boundary routers handling multicast IPv4 packets from 6over4 domain .12
A.2 IPv6 Transitioning - RFC 2765.12
A.2.1 IPv4-to-IPv6 translation.12
A.2.2 IPv6-to-IPv4 translation.21
A.3 IPv6 Transitioning - RFC 3056.29
A.3.1 Node Tests.29
A.3.1.1 Test IPv6 Prefix Allocation .29
A.3.1.2 Encapsulation in IPv4 .29
A.3.1.2.1 Encapsulation of an IPv6Packet in an IPv4Packet .29
A.3.1.3 6to4 Site Communication .30
A.3.1.3.1 Unicast scenario .30
A.3.1.4 Security Consideration.31
A.3.1.4.1 Security consideration during Encapsulation of IPv6 packet in an IPv4 packet .31
A.3.1.4.2 Security consideration during Decapsulation of IPv6 packet from IPv4 packet .33
A.4 IPv6 Transitioning - RFC 4213.35
A.4.1 Nodes Tests.35
A.4.1.1 Resolver libraries.35
A.4.1.2 Configured tunneling - encapsulation.35
A.4.1.2.1 Encapsulation of an IPv6Packet in an IPv4Packet .35
A.4.1.3 Configured tunneling - decapsulation .38
A.4.1.3.1 Decapsulation of IPv6Packet from IPv4Packet.38
A.4.1.3.2 Handling errorneous packet while decapsulation.40
A.4.1.3.3 Link-local address on tunnel interface .41
A.4.1.4 Neighbor Discovery messages on tunnel interface .41
A.4.1.4.1 Processing Probes packets on tunnel interface.41
A.4.1.4.2 Processing Neighbor discovery packets on tunnel interface .42
A.4.1.4.3 Sending Neighbor Discovery packets on tunnel interface.43
History .44

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 518 V1.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

---------------------- Page: 4 ----------------------
5 ETSI TS 102 518 V1.1.1 (2008-02)
1 Scope
The purpose of the present document is to provide Test Suite Structure and Test Purposes (TSS&TP) for conformance
tests of the IPv4 to IPv6 transitioning protocol based on the requirements defined in the IPv6 requirements catalogue
(TS 102 599 [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 599: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT):
IPv4 to IPV6 Transitioning; 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 2529: "Transmission of IPv6 over IPv4 Domains without Explicit Tunnels".
[7] IETF RFC 2765: "Stateless IP/ICMP Translation Algorithm (SIIT)".
[8] IETF RFC 3056: "Connection of IPv6 Domains via IPv4 Clouds".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 518 V1.1.1 (2008-02)
[9] IETF RFC 4213: "Basic Transition Mechanisms for IPv6 Hosts and Routers".
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 [3] apply.
abstract test case
Abstract Test Method (ATM)
Abstract Test Suite (ATS)
Implementation Under Test (IUT)
Lower Tester (LT)
Test Purpose (TP)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATS Abstract Test Suite
IETF Internet Engineering Task Force
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
IUT Implementation Under Test
RC Requirements Catalogue
RQ Requirement
TP Test Purpose
TSS Test Suite Structure
4 Test Suite Structure (TSS)
Test Purposes have been written for 6to4-Nodes, 6to4-Routers, IP6/IP4_Nodes and IPtranslators according to the
requirements (RQ) of the requirements catalogue (RC) in TS 102 599 [2]. Test purposes have been written for
behaviours requested with "MUST", optional behaviour described with "SHOULD", "MAY" or similar wording
indicating an option has not been turned into test purposes.
The test purposes have been divided into four groups:
Group 1: IPv6 Transitioning - RFC 2529 [6]
Group 2: IPv6 Transitioning - RFC 2765 [7]
Group 3: IPv6 Transitioning - RFC 3056 [8]
Group 4: IPv6 Transitioning - RFC 4213 [9]
The sub-grouping of these two groups follows the structure of the RC.
Group 1 RFC 2529 [6]
Group 1.1 Node Tests
Group 1.1.1 Encapsulating IPv4 Header frame format validation
Group 1.1.2 Stateless Auto-configuration and Link-local addresses on 6over4
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 518 V1.1.1 (2008-02)
Group 1.1.3 Source and Target Link layer address options
Group 1.1.4 IPv6 Multicast address mapping to IPv4 multicast address to support Neighbor Discovery
Group 1.2 Router Tests
Group 1.2.1 Boundary routers handling multicast IPv4 packets from 6over4 domain

Group 2 RFC 2765 [7]
Group 2.1 IPv4-to-IPv6 translation
Group 2.2 IPv6-to-IPv4 translation

Group 3 RFC 3056 [8]
Group 3.1 Node Tests
Group 3.1.1 Test IPv6 Prefix Allocation
Group 3.2 Encapsulation in IPv4
Group 3.2.1 Encapsulation of an IPv6Packet in an IPv4Packet
Group 3.3 6to4 Site Communication
Group 3.3.1 Unicast scenario
Group 3.4 Security Consideration
Group 3.4.1 Security consideration during Encapsulation of IPv6 packet in an IPv4 packet
Group 3.4.2 Security consideration during Decapsulation of IPv6 packet from IPv4 packet

Group 4 RFC 4213 [9]
Group 4.1 Node Tests
Group 4.1.1 Resolver libraries
Group 4.1.2 Configured tunneling - encapsulation
Group 4.1.2.1 Encapsulation of an IPv6Packet in an IPv4Packet
Group 4.1.3 Configured tunneling - decapsulation
Group 4.1.3.1 Decapsulation of IPv6Packet from IPv4Packet
Group 4.1.3.2 Handling errorneous packet while decapsulation
Group 4.1.3.3 Link-local address on tunnel interface
Group 4.1.4 Neighbor Discovery messages on tunnel interface
Group 4.1.4.1 Processing Probes packets on tunnel interface
Group 4.1.4.2 Processing Neighbor discovery packets on tunnel interface
Group 4.1.4.3 Sending Neighbor Discovery packets on tunnel interface

ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 518 V1.1.1 (2008-02)
Annex A (normative):
Test Purposes (TP)
The test purposes have been written in the formal notation TPlan as described in annex A of TS 102 351 [1]. This
original textual output file is contained in an ASCII file (TRANS.tplan) (contained in archive
"ts_102518v010101p0.zip") which accompanies the present document. The raw text file has been converted to a table
format in this annex to allow better readability.
The two formats shall be considered equivalent. In the event that there appears to be syntactical or semantic differences
between the two then the textual TPlan representation takes precedence over the table format in this annex.
A.1 IPv6 Transitioning - RFC 2529
A.1.1 Node Tests
A.1.1.1 Encapsulating IPv4 Header frame format validation
Test Purpose
Identifier: TP_TRA_1003_01
Summary:
Test Dont fragment bit in an encapsulating IPv4 header
References: RQ_003_1003
IUT Role 6over4-Node Test Case: TC_TRA_1003_01
with { IUT ready to send IPv6Packet }
ensure that
   { when { IUT generates IPv6Packet }
    then { IUT encapsulates IPv6Packet in IPv4Packet
     and IUT sends IPv4Packet
         containing 'dont fragment bit'
           set to 0
      }
   }

Test Purpose
Identifier: TP_TRA_1004_01
Summary: Test protocol field in an encapsulating IPv4 header
References: RQ_003_1004
IUT Role 6over4-Node Test Case: TC_TRA_1004_01
with { IUT ready to send IPv6Packet }
ensure that
   { when { IUT generates IPv6Packet }
    then { IUT encapsulates IPv6Packet in IPv4Packet
     and IUT sends IPv4Packet
         containing protocol
           set to 41
      }
   }

ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 518 V1.1.1 (2008-02)
Test Purpose
Identifier: TP_TRA_1007_01
Summary: Test TTL field in an encapsulating IPv4 header
References: RQ_003_1007
IUT Role Test Case:
6over4-Node TC_TRA_1007_01
with { IUT configured 'TTL value of 8'
  and IUT ready to send IPv6Packet }
ensure that
   { when { IUT generates IPv6Packet }
    then { IUT encapsulates IPv6Packet in IPv4Packet
     and IUT sends IPv4Packet
         containing ttl
           set to 8
      }
   }

A.1.1.2 Stateless Auto-configuration and Link-local addresses on 6over4
Test Purpose
Identifier: TP_TRA_1009_01
Summary: Test IPv6 Link-local address format
References: RQ_003_1009, RQ_003_1010, RQ_003_1011, RQ_003_1012
IUT Role 6over4-Node Test Case: TC_TRA_1009_01
with { IUT ready to 'form IPv6 Link-local address' }
ensure that
   { when { IUT generates 'its Link-local address' }
    then { IUT 'forms Link-local address'
         containing 'universal or local bit set to zero'
       and containing 'last 32 bits as hexadecimal representation of IPv4 address appended to the prefix FE80::/64'
      }
   }

A.1.1.3 Source and Target Link layer address options
Test Purpose
Identifier: TP_TRA_1013_01
Summary:
Test Frame format of Target Link-layer address option in the Neighbor Advertisement
References:
RQ_003_1013,RQ_003_1014, RQ_003_1015, RQ_003_1016
IUT Role 6over4-Node Test Case: TC_TRA_1013_01
with { IUT ready to send 'Neighbor Advertisement' }
ensure that
   { when { IUT generates 'a Neighbor Advertisement'
         containing 'Target Link-layer Address option'
      }
    then { IUT sends 'Neighbor Advertisement' containing Link_layer_Address_option
         containing type
           set to 2 'bit 1 to 8'
         containing length
           set to 1 'bit 9 to 16'
         containing reserved
           set to 0 'bit 17 to 32'
         containing IPv4_address
           set to '32 bit address of the interface in network byte order'
      }
   }

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 518 V1.1.1 (2008-02)
Test Purpose
Identifier: TP_TRA_1013_02
Summary: Test Frame format of Source Link-layer address option in the Neighbor Solicitation
References: RQ_003_1013,RQ_003_1014, RQ_003_1015, RQ_003_1016
IUT Role Test Case:
6over4-Node TC_TRA_1013_02
with { IUT ready to send 'Neighbor Solicitation' }
ensure that
   { when { IUT generates 'a Neighbor Solicitation'
         containing 'Source Link-layer Address option'
      }
    then { IUT sends 'Neighbor Solicitation' containing Link_layer_Address_option
         containing type
           set to 1 'bit 1 to 8'
         containing length
           set to 1 'bit 9 to 16'
         containing reserved
           set to 0 'bit 17 to 32'
         containing IPv4_address
           set to '32 bit address of the interface in network byte order'
      }
   }

Test Purpose
Identifier: TP_TRA_1013_03
Summary: Test Frame format of Source Link-layer address option in the Router Advertisement
References: RQ_003_1013,RQ_003_1014, RQ_003_1015, RQ_003_1016
IUT Role 6over4-Router Test Case: TC_TRA_1013_03
with { IUT ready to send 'Router Advertisement' }
ensure that
   { when { IUT generates 'a Router Advertisement'
         containing 'Source Link-layer Address option'
      }
    then { IUT sends 'Router Advertisement' containing Link_layer_Address_option
         containing type
           set to 1 'bit 1 to 8'
         containing length
           set to 1 'bit 9 to 16'
         containing reserved
           set to 0 'bit 17 to 32'
         containing IPv4_address
           set to '32 bit address of the interface in network byte order'
      }
   }

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 518 V1.1.1 (2008-02)
Test Purpose
Identifier: TP_TRA_1013_04
Summary: Test Frame format of Source Link-layer address option in the Router Solicitation
References: RQ_003_1013,RQ_003_1014, RQ_003_1015, RQ_003_1016
IUT Role Test Case:
6over4-Node TC_TRA_1013_04
with { IUT ready to send 'Router Solicitation' }
ensure that
   { when { IUT generates 'a Router Solicitation'
         containing 'Source Link-layer Address option'
      }
    then { IUT sends 'Router Solicitation' containing Link_layer_Address_option
         containing type
           set to 1 'bit 1 to 8'
         containing length
           set to 1 'bit 9 to 16'
         containing reserved
           set to 0 'bit 17 to 32'
         containing IPv4_address
           set to '32 bit address of the interface in network byte order'
      }
   }

A.1.1.4 IPv6 Multicast address mapping to IPv4 multicast address to support
Neighbor Discovery
Test Purpose
Identifier: TP_TRA_1017_01
Summary: Test IPv6 all-node multicast address mapped to IPv4 multicast address
References: RQ_003_1017, RQ_003_1018, RQ_003_1020, RQ_003_1027
IUT Role 6over4-Node Test Case: TC_TRA_1017_01
with { IUT configured 'organization local scope address block i.e: 192'
  and IUT '6over4 interface is enabled'
  }
ensure that
   { when { IUT generates IPv6Packet 'with IPv6 destination address set to all-nodes multicast address FF02::1' }
    then { IUT sends IPv6Packet tunneled in IPv4Packet
         containing ipv4_dst_addr
           set to 'IPv4 multicast address 239.192.0.1'
      }
   }

Test Purpose
Identifier: TP_TRA_1017_02
Summary: Test IPv6 all-routers multicast address mapped to IPv4 multicast address
References:
RQ_003_1017, RQ_003_1018, RQ_003_1020, RQ_003_1027
IUT Role 6over4-Node Test Case: TC_TRA_1017_02
with { IUT configured 'organization local scope address block i.e: 192'
  and IUT '6over4 interface is enabled'
  }
ensure that
   { when { IUT generates IPv6Packet 'with IPv6 destination address set to all-routers multicast address FF02::2' }
    then { IUT sends IPv6Packet tunneled in IPv4Packet
         containing ipv4_dst_addr
           set to 'IPv4 multicast address 239.192.0.2'
      }
   }

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 518 V1.1.1 (2008-02)
Test Purpose
Identifier: TP_TRA_1017_03
Summary: Test IPv6 solicited-node multicast address mapped to IPv4 multicast address
References: RQ_003_1017, RQ_003_1018, RQ_003_1020, RQ_003_1027
IUT Role Test Case:
6over4-Node TC_TRA_1017_03
with { IUT configured 'organization local scope address block i.e: 192'
  and IUT '6over4 interface is enabled'
  }
ensure that
   { when { IUT generates IPv6Packet 'with IPv6 destination address set to solicited-node multicast address
FF02::1:FF28:9C5A' }
    then { IUT sends IPv6Packet tunneled in IPv4Packet
         containing ipv4_dst_addr
           set to 'IPv4 multicast address 239.192.156.90'
      }
   }

A.1.2 Route Tests
A.1.2.1 Boundary routers handling multicast IPv4 packets from 6over4
domain
Test Purpose
Identifier: TP_TRA_1024_02
Summary: Test multicast IPv4 packets with unknown organization-local scope destination address
References: RQ_003_1024
IUT Role 6to4-Router Test Case: TC_TRA_1024_02
with { IUT configured 'organization local scope address block i.e: 192' }
ensure that
   { when { IUT ready to receive IPv4Packet }
    then { IUT discards 'IPv4 multicast packets'
         containing 'destination address'
           set to 'unknown organization-local scope address block i.e: 50'
      }
   }

A.2 IPv6 Transitioning - RFC 2765
A.2.1 IPv4-to-IPv6 translation
Test Purpose
Identifier: TP_TRA_3003_01
Summary: Test 4to6 packet translation where DF bit is not set and fragmentation is necessary
References: RQ_003_3003, RQ_003_3006, RQ_003_3007, RQ_003_3011,
IUT Role IPtranslator Test Case: TC_TRA_3003_01
with { IUT ready to translate IPv4Packet }
ensure that
   { when { IUT receives IPv4Packet with 'data leading to overall size >1280 bytes'
         containing protocol
       and containing ip_identification
       and containing DF_bit set to 0
       and containing ttl
       and containing ipv4_src_addr
       and containing ipv4_dst_addr }
    then { IUT sends IPv6Packet
         containing flow_Label set to 'all zero bits'
ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 102 518 V1.1.1 (2008-02)
       and containing next_header set to 44
       and containing hop_limit set to 'value received in IPv4 ttl field'
       and containing ipv6_src_addr set to ipv4_src_addr with prefix_field '::ffff:0:0' and prefix_length 96
       and containing ipv6_dst_addr set to ipv4_dst_addr with prefix_field '::ffff:0:0' and prefix_length 96
       and containing Fragment_Header
           containing next_header set to protocol
           and containing offset set to 0
           and containing M_flag set to 1
           and containing ipv6_identification set to ip_identification 'padded with zeros'
    and IUT sends IPv6Packet
         containing flow_Label set to 'all zero bits'
       and containing next_header set to 44
       and containing hop_limit set to 'value received in IPv4 ttl field'
       and containing ipv6_src_addr set to ipv4_src_addr with prefix_field '::ffff:0:0' and prefix_length 96
       and containing ipv6_dst_addr set to ipv4_dst_addr with prefix_field '::ffff:0:0' and prefix_length 96
       and containing Fragment_Header
           containing next_header set to protocol
           and containing M_flag set to 0
           and containing ipv6_identification set to ip_identification 'padded with zeros'
      }
   }

Test Purpose
Identifier: TP_TRA_3004_01
Summary: Test 4to6 packet translation where DF bit is not set and fragmentation is not necessary
References: RQ_003_3004, RQ_003_3011, RQ_003_3014, RQ_003_3018,
IUT Role IPtranslator Test Case: TC_TRA_3004_01
with { IUT ready to translate IPv4Packet }
ensure that
   { when { IUT receives IPv4Packet with 'data leading to overall size <1280 bytes'
         containing protocol
       and containing ip_identification
       and containing DF_bit set to 0
       and containing ttl
       and containing ipv4_src_addr
       and containing ipv4_dst_addr
       and not containing options   }
    then { IUT sends IPv6Packet
         containing flow_Label set to 'all zero bits'
       and containing payload_len set to 'IPv4 total_len + 8 (fragment header) - 20 (IPv4 header)'
       and containing next_header set to 44
       and containing hop_limit set to 'value received in IPv4 ttl field'
       and containing ipv6_src_addr set to ipv4_src_addr w
...