hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.2.5 Transport-Layer Header Translation | TP Id TP_SIIT_T46_TLH_01 Test Objective Verify that IUT recalculates and updates TCP headers when the address translation algorithm is not checksum neutral. Reference IETF RFC 7915 [1], clause 4.5 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/1_5_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv4 packet with the total length less than 1280 bytes containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), with the value greater than or equal to 2 Protocol, Header Checksum, Source Address, Destination Address, TCP header containing Source Port, Destination Port, Sequence Number, Acknowledge Number, Data Offset, Reserved, Control Bits, Window, Checksum, Urgent Point, Options, Data from the IPv4 node } then { the IUT sends an IPv6 packet containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, TCP header containing Source Port, Destination Port, Sequence Number, Acknowledge Number, Data Offset, Reserved, Control Bits, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 75 Window, Checksum, with the value taking into account IP addresses change Urgent Point, Options, Data to the IPv6 node } } TP Id TP_SIIT_T46_TLH_02 Test Objective Verify that IUT recalculates and updates UDP headers when the checksum value is not zero and the address translation algorithm is not checksum neutral. Reference IETF RFC 7915 [1], clause 4.5 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/1_5_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv4 packet with the total length less than 1280 bytes containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), with the value greater than or equal to 2 Protocol, Header Checksum, Source Address, Destination Address, UDP header containing Source Port, Destination Port, Length, Checksum, with the value greater than 0 Data from the IPv4 node } then { the IUT sends an IPv6 packet containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, UDP header containing Source Port, Destination Port, Sequence Number, Checksum, with the value taking into account IP addresses change Data to the IPv6 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 76 TP Id TP_SIIT_T46_TLH_03 Test Objective Verify that IUT recalculates and updates UDP headers when the checksum value is zero and the address translation algorithm is not checksum neutral. Reference IETF RFC 7915 [1], clause 4.5 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/1_5_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv4 packet with the total length less than 1280 bytes containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), with the value greater than or equal to 2 Protocol, Header Checksum, Source Address, Destination Address, UDP header containing Source Port, Destination Port, Length, Checksum, with the value equal to 0 Data from the IPv4 node } then { the IUT sends an IPv6 packet containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, UDP header containing Source Port, Destination Port, Sequence Number, Checksum, calculate the value taking into account IP addresses change Data to the IPv6 node or drops that IPv4 packet } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 77 |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.2.6 Knowing When to Translate | TP Id TP_SIIT_T46_KWT_01 Test Objective Verify that the IUT provides a normal forwarding function. Reference IETF RFC 7915 [1], clause 4.6 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/1_6_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes the IUT is configured with a specific route by which an IPv4 address is reachable within IPv4 pool } Expected Behaviour ensure that { when { IUT receives an IPv4 packet with the total length less than 1280 bytes containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), with the value greater than or equal to 2 Protocol, Header Checksum, Source Address, Destination Address, an IPv4 address is reachable by a specific route Data from the IPv4 node } then { the IUT forwards that IPv4 packet without translating to the IPv4 node } } |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3 Translating from IPv6 to IPv4 | |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.1 Translating IPv6 Headers to IPv4 Headers | TP Id TP_SIIT_T64_IPHDR_01 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header. Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Data from the IPv6 node ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 78 } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, with the value of 4 Internet Header Length (IHL), with the value of 5 Type of Service (TOS), copied from Traffic Class Total Length, with the value which is payload length value from the IPv6 header, plus the size of the IPv4 header Identification (Fragment ID), Flags, setting the More Fragments flag to 0, and the Don't Fragment (DF) flag is set to 0 Fragment Offset, set to all zeros Time to Live (TTL), with the value of decrementing the Hop Limit value Protocol, copied from Next Header Header Checksum, calculating the checksum once the IPv4 header has been created Source Address, mapped to an IPv4 address according the algorithm Destination Address, mapped to an IPv4 address according the algorithm Data to the IPv4 node } } TP Id TP_SIIT_T64_IPHDR_02 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header and the IUT is configured to set the IPv4 TOS Octet to a specific value (5). Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_1_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, with the value of 0 Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Data from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), with the value of 5 Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, Data to the IPv4 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 79 TP Id TP_SIIT_T64_IPHDR_03 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header and the translated IPv4 packet is greater than 1 260 bytes. Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_1_5 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1300 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length equal to 1300 bytes containing IPv6 basic header containing Version, Traffic Class, with the value of 0 Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Data from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, with Don't Fragment (DF) flag set to 1 Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, Data to the IPv4 node } } TP Id TP_SIIT_T64_IPHDR_04 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header and the Hop Limit value is 0. Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_1_7 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value equal to 1 Source Address, Destination Address, Data from the IPv6 node } then { ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 80 IUT sends the ICMpv4 "TTL Exceeded" to the IPv4 node or ICMPv6 "Hop Limit Exceeded" error to the IPv6 node } } TP Id TP_SIIT_T64_IPHDR_05 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header and ignores the IPv6 header HOPOPT (0). Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_1_8 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, with the value of 0 Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Hop-by-Hop Options Header containing Next Header, Hdr Ext Len, Options, Data from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, Data to the IPv4 node } } TP Id TP_SIIT_T64_IPHDR_06 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header and ignores the IPv6 header IPv6-Route (43). Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_1_8 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 81 IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, with the value of 43 Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Routing Header containing Next Header, Hdr Ext Len, Routing Type, Segment Left, Type-specific data, Data from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, Data to the IPv4 node } } TP Id TP_SIIT_T64_IPHDR_07 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header and ignores the IPv6 header IPv6-Opts (60). Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_1_8 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, with the value of 60 Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Routing Header containing Next Header, Hdr Ext Len, Routing Type, Segment Left, with the value of 0 Type-specific data, Data from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 82 Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, Data to the IPv4 node } } TP Id TP_SIIT_T64_IPHDR_08 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header and ignores any of an IPv6 Hop-by-Hop Options header, Destination Options header, or Routing header with the Segments Left field equal to zero. Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, with the value of 60 Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Routing Header containing Next Header, Hdr Ext Len, Routing Type, Segment Left, with the value of 0 Type-specific data, Data from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, Data to the IPv4 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 83 TP Id TP_SIIT_T64_IPHDR_09 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header and a Routing header with a non-zero Segments Left field (1). Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_3 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, with the value of 60 Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Routing Header containing Next Header, Hdr Ext Len, Routing Type, Segment Left, with the value of 1 Type-specific data, Data from the IPv6 node } then { IUT sends an IPv6 packet containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, with the value of 60 Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 43 Data, as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU to the IPv6 node } } TP Id TP_SIIT_T64_IPHDR_10 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is an IPv6 Fragment Header. Reference IETF RFC 7915 [1], clause 5.1.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_4 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 84 Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Fragment Header containing Next Header Reserved Fragment Offset Res M flag Identification Data from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, with the value of 4 Internet Header Length (IHL), with the value of 5 Type of Service (TOS), copied from Traffic Class Total Length, with the value set to payload length value from the IPv6 header, minus the length of the extension headers up to the Fragmentation Header, minus 8 for the Fragment Header, plus the size of the IPv4 header Identification (Fragment ID), copying the low-order 16 bits in the Identification field in the Fragment Header Flags, The IPv4 More Fragments (MF) flag is copied from the M flag in the IPv6 Fragment Header, and the Don't Fragment (DF) flag is set to 0 Fragment Offset, copied from the Fragment Offset field of the IPv6 Fragment Header Time to Live (TTL), with the value of decrementing the Hop Limit value Protocol, copied from Next Header Header Checksum, calculating the checksum once the IPv4 header has been created Source Address, mapped to an IPv4 address according the algorithm Destination Address, mapped to an IPv4 address according the algorithm Data to the IPv4 node } } TP Id TP_SIIT_T64_IPHDR_11 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is an IPv6 Fragment Header and Next Header field of the Fragment Header is an extension header (except ESP, but including the Authentication Header (AH)). Reference IETF RFC 7915 [1], clause 5.1.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_4_1, PICS_A2/2_1_4_5 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Fragment Header containing Next Header, with the value of 51 Reserved, Fragment Offset, Res, M flag, Identification, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 85 Data from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_IPHDR_12 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is an IPv6 Fragment Header and the size of IPv4 packet is larger than the MTU of the next-hop interface. Reference IETF RFC 7915 [1], clause 5.1.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_4_7 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes the MTU of the next-hop interface is 576 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with length less than or equal to 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, Fragment Header containing Next Header, Reserved, Fragment Offset, Res, M flag, Identification, Data from the IPv6 node } then { IUT translates IPv6 packet and fragments IPv4 packet and sends packets to the IPv4 node } } |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.2 Translating ICMPv6 Headers into ICMPv4 Headers | TP Id TP_SIIT_T64_ICMPH_01 Test Objective Verify that the IUT successfully translates Echo Request messages (128), adjusts the type value to 8 and recalculates the ICMP checksum both to take the type change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 86 Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 128 Code, Checksum, Identifier Sequence Number, Data from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, ICMP header containing Type, with the value of 8 Code, Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Identifier, Sequence number, Data to the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_02 Test Objective Verify that the IUT successfully translates Echo Request messages (129), adjusts the type value to 0 and recalculates the ICMP checksum both to take the type change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 129 Code, Checksum, Identifier Sequence Number, Data from the IPv6 node } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 87 then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, ICMP header containing Type, with the value of 0 Code, Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Identifier, Sequence number, Data to the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_03 Test Objective Verify that the IUT successfully drops the MLD Multicast Listener Query messages (130). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 130 Code, Checksum, Maximum Response Delay, Reserved, Multicast Address from the IPv6 node } then { IUT drops that packet } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 88 TP Id TP_SIIT_T64_ICMPH_04 Test Objective Verify that the IUT successfully drops the MLD Multicast Listener Report messages (131). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 131 Code, Checksum, Maximum Response Delay, Reserved, Multicast Address from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_04 Test Objective Verify that the IUT successfully drops the MLD Multicast Listener Done messages (132). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 132 Code, Checksum, Maximum Response Delay, Reserved, Multicast Address from the IPv6 node } then { IUT drops that packet } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 89 TP Id TP_SIIT_T64_ICMPH_05 Test Objective Verify that the IUT successfully drops the Router Solicitation messages (133). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_3 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 133 Code, Checksum, Reserved, options, from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_06 Test Objective Verify that the IUT successfully drops the Router Advertisement messages (134). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_3 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 134 Code, Checksum, Cur Hop Limit, M, O, Reserved, Router Lifetime, Reachable Time, Retrans Timer, Options, from the IPv6 node } then { ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 90 IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_07 Test Objective Verify that the IUT successfully drops the Neighbour Solicitation messages (135). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_3 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 135 Code, Checksum, Reserved, Target Address, Options, from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_08 Test Objective Verify that the IUT successfully drops the Neighbour Advertisement messages (136). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_3 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 136 Code, Checksum, R, S, O, Reserved, Target Address, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 91 Options, from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_09 Test Objective Verify that the IUT successfully drops the Neighbour Advertisement messages (137). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_3 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 137 Code, Checksum, Reserved, Target Address, Destination Address, Options, from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_10 Test Objective Verify that the IUT successfully drops the Unknown informational messages (254). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_1_4 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 254 Code, Checksum, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 92 Reserved, Target Address, Destination Address, Options, from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_11 Test Objective Verify that the IUT successfully adjusts the type values of Destination Unreachable messages (type 1) to 3, the code 0 (No route to destination) to 1 (Host unreachable) and the ICMP checksum both to take the type/code change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_1_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 1 Code, with the value of 0 Checksum, Reserved, Unused, Data, as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, ICMP header containing Type, with the value of 3 Code, with the value of 1 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Unused, Data, Internet Header plus 64 bits of Original Data Datagram to the IPv4 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 93 TP Id TP_SIIT_T64_ICMPH_12 Test Objective Verify that the IUT successfully adjusts the type values of Destination Unreachable messages (type 1) to 3, the code 1 (Communication with destination administratively prohibited) to 10 (Communication with destination host administratively prohibited) and the ICMP checksum both to take the type/code change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_1_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 1 Code, with the value of 1 Checksum, Reserved, Unused, Data, as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, ICMP header containing Type, with the value of 3 Code, with the value of 10 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Unused, Data, Internet Header plus 64 bits of Original Data Datagram to the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_13 Test Objective Verify that the IUT successfully adjusts the type values of Destination Unreachable messages (type 1) to 3, the code 2 (Beyond scope of source address) to 1 (Host unreachable) and the ICMP checksum both to take the type/code change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_1_3 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 94 Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 1 Code, with the value of 2 Checksum, Reserved, Unused, Data, as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, ICMP header containing Type, with the value of 3 Code, with the value of 1 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Unused, Data, Internet Header plus 64 bits of Original Data Datagram to the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_14 Test Objective Verify that the IUT successfully adjusts the type values of Destination Unreachable messages (type 1) to 3, the code 3 (Address unreachable) to 1 (Host unreachable) and the ICMP checksum both to take the type/code change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_1_4 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 1 Code, with the value of 3 ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 95 Checksum, Reserved, Unused, Data, as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, ICMP header containing Type, with the value of 3 Code, with the value of 1 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Unused, Data, Internet Header plus 64 bits of Original Data Datagram to the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_15 Test Objective Verify that the IUT successfully adjusts the type values of Destination Unreachable messages (type 1) to 3, the code 4 (Port unreachable) to 3 (Port unreachable) and the ICMP checksum both to take the type/code change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_1_4 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 1 Code, with the value of 3 Checksum, Reserved, Unused, Data, as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 96 Fragment Offset, Time to Live (TTL), Header Checksum, Destination Address, ICMP header containing Type, with the value of 3 Code, with the value of 3 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Unused, Data, Internet Header plus 64 bits of Original Data Datagram to the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_16 Test Objective Verify that the IUT successfully drops Destination Unreachable messages with unknown code values (10). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_1_4 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 1 Code, with the value of 10 Checksum, Reserved, Unused, Data, as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_17 Test Objective Verify that the IUT successfully translates Packet Too Big (Type 2) messages to an ICMPv4 Destination Unreachable (Type 3) with Code 4, and adjust the ICMPv4 checksum both to take the type change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_2_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 97 Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 2 Code, with the value of 0 Checksum, MTU, Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 11 Code, Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_18 Test Objective Verify that the IUT successfully translates Time Exceeded (Type 3) messages, set the Type to 11, and adjusts the ICMPv4 checksum both to take the type change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_3 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 3 Code, Checksum, Unused, Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 98 } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 11 Code, Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_19 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 0 and pointer 0, sets the Type to 12, the Code to 0, and the pointer to 0. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 0 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 99 ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 0 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_20 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 0 and pointer 1, sets the Type to 12, the Code to 0, and the pointer to 1. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 1 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 1 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 100 TP Id TP_SIIT_T64_ICMPH_21 Test Objective Verify that the IUT successfully drops Parameter Problem (Type 4) messages with Code 0 and pointer 2. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 2 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_22 Test Objective Verify that the IUT successfully drops Parameter Problem (Type 4) messages with Code 0 and pointer 3. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 3 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT drops that packet ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 101 } } TP Id TP_SIIT_T64_ICMPH_23 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 0 and pointer 4, sets the Type to 12, the Code to 0, and the pointer to 2. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 4 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 2 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 102 TP Id TP_SIIT_T64_ICMPH_24 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 0 and pointer 5, sets the Type to 12, the Code to 0, and the pointer to 2. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 5 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 2 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_25 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 0 and pointer 6, sets the Type to 12, the Code to 0, and the pointer to 9. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 103 IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 6 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 9 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_26 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 0 and pointer 7, sets the Type to 12, the Code to 0, and the pointer to 8. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 7 ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 104 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 8 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_27 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 0 and pointer 7, sets the Type to 12, the Code to 0, and the pointer to 8. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value of 7 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 105 Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 8 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_28 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 0 and pointer ranging from 8 to 23, sets the Type to 12, the Code to 0, and the pointer to 12. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value ranging from 8 to 23 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 12 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 106 TP Id TP_SIIT_T64_ICMPH_29 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 0 and pointer ranging from 24 to 39, sets the Type to 12, the Code to 0, and the pointer to 16. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value ranging from 24 to 39 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 16 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_30 Test Objective Verify that the IUT successfully translates Parameter Problem (Type 4) messages with Code 1, sets the Type to 3, and the Code to 2. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_4_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 107 IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 4 Code, with the value of 0 Checksum, Pointer, with the value ranging from 8 to 23 Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 12 Code, with the value of 0 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Pointer, with the value of 12 unused, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } TP Id TP_SIIT_T64_ICMPH_31 Test Objective Verify that the IUT successfully drops Unknown error messages (type 0). Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_5 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 0 Code, Checksum, Unused, Data, copying as much of invoking packet as possible without the ICMPv6 packet ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 108 exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT drops that packet } } TP Id TP_SIIT_T64_ICMPH_32 Test Objective Verify that the IUT successfully translates ICMPv6 packet contains an ICMPv6 Extension, adjust the ICMPv6 Extension length attribute accordingly. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_6 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 1 Code, with the value of 0 Checksum, Length, Unused, Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 3 Code, with the value of 1 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Unused, Length, adjusting the value due to changes caused by translation Next-Hop MTU, Internet Header + 64 bits of Original Data Datagram from the IPv4 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 109 TP Id TP_SIIT_T64_ICMPH_34 Test Objective Verify that the IUT successfully passes ICMPv6 packet with extensions not defined in IETF RFC 4884 [4] as opaque bit strings and any IPv6 address literals contained. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_2_2_7 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, ICMP header containing Type, with the value of 1 Code, with the value of 0 Checksum, Length, Unused, Pointer, the field that not defined Data, copying as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU Extension Header containing Version, Reserved, Checksum, Extension object containing Length, Class-Num, C-Type, Object payload, from the IPv6 node } then { IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 3 Code, with the value of 1 Checksum, adjusting the value both take the type change into account and to exclude the ICMPv6 pseudo-header Unused, Length, adjusting the value due to changes caused by translation Next-Hop MTU, Internet Header + 64 bits of Original Data Datagram Data, copied from the ICMP Extension without translation from the IPv4 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 110 |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.3 Translating ICMPv6 Error Messages into ICMPv4 | TP Id TP_SIIT_T64_ICMPE_01 Test Objective Verify the IUT translates the ICMP error messages containing the packet in error just like a normal IP packet (except that the TTL/Hop Limit value of the inner IPv4/IPv6 packet are not decremented), and update the Total Length field in the outer IPv4 header. Reference IETF RFC 7915 [1], clause 5.3 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_3_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { the IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, with value of taking into account the length change in Data Next Header, Hop Limit, Source Address, Destination Address, ICMP Header containing Type, with the value of 1 Code, with the value of 0 Checksum, Unused, Data containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, Data, from the IPv6 node } then { the IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), with the value greater than or equal to 2 Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 3 Code, with the value of 0 Checksum, Pointer, unused, Internet Header + 64 bits of Original Data Datagram containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), no changes ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 111 Protocol, Header Checksum, Source Address, mapped to an IPv4 address according the algorithm Destination Address, mapped to an IPv4 address according the algorithm Data Datagram to the IPv6 node } } TP Id TP_SIIT_T64_ICMPE_02 Test Objective Verify the IUT translates the inner IP header. Reference IETF RFC 7915 [1], clause 5.3 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_3_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { the IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, ICMP Header containing Type, with the value of 1 Code, with the value of 0 Checksum, Unused, Data containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, Data, without embedded IP headers from the IPv6 node } then { the IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), with the value greater than or equal to 2 Protocol, Header Checksum, Source Address, Destination Address, ICMP header containing Type, with the value of 3 Code, with the value of 0 Checksum, Pointer, unused, Internet Header + 64 bits of Original Data Datagram containing IPv4 basic header containing ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 112 Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), with the value greater than or equal to 2 Protocol, Header Checksum, Source Address, Destination Address, Data Datagram, to the IPv4 node } } TP Id TP_SIIT_T64_ICMPE_03 Test Objective Verify the IUT stops the process of translating the outer IP headers at the first embedded header and drops the packet if it contains more embedded headers. Reference IETF RFC 7915 [1], clause 5.3 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_3_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, ICMP Header containing Type, with the value of 1 Code, with the value of 0 Checksum, Unused, Data containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, Data, with embedded IP headers from the IPv6 node } then { the IUT drops that IPv6 packet } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 113 |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.4 Generation of ICMPv6 Error Messages | TP Id TP_SIIT_T64_GE_01 Test Objective Verify that the IUT sends back an ICMPv6 error message to the original sender of the packet if the IPv6 packet is discarded. Reference IETF RFC 7915 [1], clause 5.4 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_4_1, 2_4_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes the IUT is configured to the access of IPv6 node is denied } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, Data from the IPv6 node } then { IUT discards that IPv6 packet and sends an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, Destination Address, with the IPv6 address of that IPv6 packet ICMP header containing Type, with the value of 1 Code, with the value of 1 Checksum, unused, Data to the IPv6 node } } |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.5 Transport-Layer Header Translation | TP Id TP_SIIT_T64_TLH_01 Test Objective Verify that IUT recalculates and updates TCP headers when the address translation algorithm is not checksum neutral. Reference IETF RFC 7915 [1], clause 5.5 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_5_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 114 Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, TCP header containing Source Port, Destination Port, Sequence Number, Acknowledge Number, Data Offset, Reserved, Control Bits, Window, Checksum, Urgent Point, Options, Data from the IPv6 node } then { the IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), Protocol, Header Checksum, Source Address, Destination Address, TCP header containing Source Port, Destination Port, Sequence Number, Acknowledge Number, Data Offset, Reserved, Control Bits, Window, Checksum, with the value taking into account IP addresses change Urgent Point, Options, Data to the IPv4 node } } TP Id TP_SIIT_T64_TLH_02 Test Objective Verify that IUT recalculates and updates UDP headers when the checksum value is not zero and the address translation algorithm is not checksum neutral. Reference IETF RFC 7915 [1], clause 5.5 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_5_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 115 Source Address, Destination Address, UDP header containing Source Port, Destination Port, Sequence Number, Checksum, with the value greater than 0 Data from the IPv6 node } then { the IUT sends an IPv4 packet containing IPv4 basic header containing Version, Internet Header Length (IHL), Type of Service (TOS), Total Length, Identification (Fragment ID), Flags, Fragment Offset, Time to Live (TTL), with the value greater than or equal to 2 Protocol, Header Checksum, Source Address, Destination Address, UDP header containing Source Port, Destination Port, Length, Checksum, with the value taking into account IP addresses change Data to the IPv4 node } } |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.6 Knowing When to Translate | TP Id TP_SIIT_T64_KWT_01 Test Objective Verify that the IUT provides a normal forwarding function. Reference IETF RFC 7915 [1], clause 5.6 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_6_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 MTU in the network is 1280 bytes the IUT is configured with a specific route by which an IPv6 address is reachable within IPv6 pool } Expected Behaviour ensure that { when { IUT receives an IPv6 packet with the total length less than 1280 bytes containing IPv6 basic header containing IPv6 basic header containing Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, with the value greater than or equal to 2 Source Address, Destination Address, an IPv6 address is reachable by a specific route Data from the IPv6 node } then { the IUT forwards that IPv6 packet without translating to the IPv6 node } } ETSI ETSI TS 104 153-2 V1.1.1 (2026-02) 116 History Version Date Status V1.1.1 February 2026 Publication |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 1 Scope | The present document provides a universal, inclusive structured framework-repository directory that identifies cybersecurity activity clusters and associated commonly used specifications that entail information exchange and associated information repositories. Responsible parties, network location and availability are included. Uses involving cybersecurity legislative instruments such as those in the EU, as well as industry norms, are identified and information repositories - especially those used for AI LLM ingestion - are included. The ETSI Forge and OID leaf are used for the UCYBEX repository-directory. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 2 References | |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 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 referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. 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] ETSI: "Collaborative tools for standardized technologies". [2] JSON Schema: "Specification". [3] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 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] Recommendation ITU-T X.1500: "Overview of cybersecurity information exchange". [i.2] GCVE.EU: "GCVE: Global CVE Allocation System". [i.3] EU: "ELI - European Legislation Identifier". ETSI ETSI TS 104 170 V1.1.1 (2026-02) 7 |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 3 Definition of terms, symbols and abbreviations | |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 3.1 Terms | For the purposes of the present document, the following terms apply: automation: use of technology, often including AI and machine learning, to automate cybersecurity processes, reducing human intervention and improving the efficiency of security operations bill of materials: document that lists the software or hardware components, including their versions and dependencies, used in a product or system coding: knowledge enabling professionals to analyse vulnerabilities, develop security tools, and understand the tactics of malicious actors configuration: cyber state consisting of the settings, rules and parameters that define enhanced security for a system or network disinformation: identification of deliberate efforts to spread false information through ICT-based services hardened images: cyber state consisting of virtual machine images that are pre-configured to meet the robust security recommendations of the associated Critical Security Control Benchmark incident response: structured process for handling security incidents, including detection, containment, eradication, and recovery monitoring and auditing: structured process of continuously monitoring systems for security breaches and conducting regular security audits normative binding: asserted relationship for compliance with one or more obligations in a normative instrument, indicated with an instrument identifier such as a European Legislative Identifier ontology: set of concepts and categories in a subject area or domain that shows their properties and the relations between them playbook: standard set of procedures to identify, coordinate, remediate, recover, and track successful mitigations from incidents and vulnerabilities affecting an organisation’s systems, data, and networks processes: series of steps and procedures designed to protect an organization's assets, data, and systems from cyber threats risk management: structured process of identifying, assessing, and mitigating cybersecurity risks risk measurement: quantitative structured process for assessing risk level security awareness training: process of educating employees about cybersecurity threats and best practices semantic framework: structured approach to organizing and abstracting data and knowledge, allowing for a deeper understanding of relationships between concepts and entities state: cybersecurity state of a device or system threat: malicious action or event that can negatively impact an organization or individual through an information system trust: means to assess the integrity, security, and reliability of systems, processes, organizations and individuals vulnerability: specific weakness or flaw in a system, network, or application that attackers can exploit to compromise security vulnerability management: process of regularly scanning and patching systems for vulnerabilities weakness: standardized way to describe and classify common software and hardware errors that can be exploited by attackers ETSI ETSI TS 104 170 V1.1.1 (2026-02) 8 |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 3.2 Symbols | Void. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ELI European Legislative Identifier UCYBEX Universal Cybersecurity Information Exchange Framework 4 Universal Cybersecurity Information Exchange Framework (UCYBEX) |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.0 Cybersecurity information exchange models | The contemporary period of cybersecurity information exchange emerged in the 1990 timeframe and consisted of the exchange of combinations of incident, vulnerability, and threat information via repositories among a complex global community of product and service vendors, end users, and industry and government cyber security organizations [i.1]. The actual sharing of information together with a broad array of related protocols was depicted within ITU-T as a five-component activity. See Figure 4.0-1 below. Figure 4.0-1: Cybersecurity information exchange model [i.1] |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.1 UCYBEX Framework - Repository architecture | The present document facilitates the exchange of cybersecurity information using a framework that establishes a design architecture for openness, diversity, extensibility, and interoperability. This global decentralised, autonomous framework architecture enables widespread sharing of cybersecurity resources including obligation compliance relationships via multiple common distributed repositories that enable users to discover and access those resources in the form of other directory lists, specifications, tools, or any other kind of related enrichment information. It is modelled after the Global CVE framework architecture [i.2]. The structure for the framework - repository record format is set forth in clause 4.2. The JSON representation is in Annex A. ETSI Source Forge requirements [1] and JSON format requirements [2] apply to the implementation of the UCYBEX framework. An example of the ETSI implementation of the framework list is provided in Annex B. ETSI ETSI TS 104 170 V1.1.1 (2026-02) 9 |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2 UCYBEX Framework Resource Record Format and Values | |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.1 Overview | Figure 4.2-1: Mindmap of the UCYBEX Framework Resource Record, V1.0.1 |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.2 UCYBEXversion | This required value describes the present UCYBEX Framework Resource Record specification version being used and expressed as three numbers separated by commas and set initially to 1.0.1. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.3 UCYBEXresourcetype | This required value describes the UCYBEX resource type in the following non-case-sensitive enumeration: list Another UCYBEX or compatible Framework Resource list spec Any technical specification for cybersecurity repository Any information repository for cybersecurity purposes enrichment Any cybersecurity enrichment information including AI BOMs and knowledge graphs tool Any program intended to assist cybersecurity or related risk management playbook Any playbook for cybersecurity … A description of any other resource, preferably using clause 3.1 terminology |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.4 UCYBEXresourcename | This required value describes the name of the resource without any constraints - prefaced by any related identifier associated with the name. For example, "ETSI TS 104 170 V1.0.0 - Rec. ITU-T X.1500 Cyber Security (CYBER); Universal Cybersecurity Information Exchange Framework - Repository". |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.5 UCYBEXresourceaddress | This required value describes the resource address location without any constraints - preferably as a persistent, precise, accessible Uniform Resource Identifier (URI) or a link capable of providing the resource. For example, https://www.etsi.org/deliver/etsi_ts/104170 [TBD]. ETSI ETSI TS 104 170 V1.1.1 (2026-02) 10 |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.6 UCYBEXresourcecontact | This optional value describes the national incorporation jurisdiction using a recognized country identifier and contact information without any constraints for the entity maintaining and accessing the resource preferably including physical and location and useable email address. For example, "France, ETSI Secretariat, ETSI 650, Route des Lucioles 06560 Valbonne - Sophia Antipolis FRANCE, secretariat@etsi.org". |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.7 UCYBEXresourceaccess | This optional value without any constraints describes any resource access controls, for example, "paywall" or "members only". The default when leaving blank is publicly available without constraints. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.8 UCYBEXresourcetrust | This optional value without any constraints describes any resource trust mechanisms such as a digital certificate. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.9 UCYBEXnormbindings | This optional value without any constraints describes any asserted normative binding, i.e. an asserted relationship for compliance with one or more obligations in a normative instrument, indicated with an instrument identifier such as a European Legislative Identifier (ELI) [i.3]. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.10 UCYBEXnote | This optional value without any constraints describes any useful attributes of the resource. ETSI ETSI TS 104 170 V1.1.1 (2026-02) 11 Annex A (normative): UCYBEX Framework Resource Record JSON Format V1.0.1 { "$schema": "http://[tbd]", "title": "JSON Schema for UCYBEX Framework Resource Record version 1.0.1", "$id": "https://www.etsi.org/[tbd]", "properties": { "UCYBEXversion": { "description": "present UCYBEX Framework Resource Record specification version being used and expressed as three numbers separated by commas and set initially to 1.0.1", "type": "1.0.1" }, "UCYBEXresourcetype": { "description": "UCYBEX resource type ", "enum": [ "list", "spec", "repository", "enrichment", "tool", "playbook" ], "type": "string", }, "UCYBEXresourcename": { "description": "the name of the resource", "type": "string", "identifier": " ", "name": " " }, "UCYBEXresourceaddress": { "description": "resource address location", "type": "string" }, "UCYBEXresourcecontact": { "description": "national incorporation jurisdiction using a recognized country identifier and contact information for the entity maintaining and accessing the resource", "type": "string", "jurisdiction": " ", "entity name": " ", "street": " ", "city": " ", "phone": " ", "email": " " }, "UCYBEXresourceaccess": { "description": "describes any resource access controls", "type": "string" }, "UCYBEXresourcetrust": { "description": "any resource trust mechanisms", "type": "string" }, "UCYBEXresourcenormbindings": { "description": "any asserted normative binding, i.e. an asserted relationship for compliance with one or more obligations in a normative instrument", "type": "string" }, "UCYBEXnote": { "description": "any useful attributes of the resource", "type": "string" }, ETSI ETSI TS 104 170 V1.1.1 (2026-02) 12 }, "required": [ "UCYBEXversion", "UCYBEXresourcetype", "UCYBEXresourceaddress" ] } ETSI ETSI TS 104 170 V1.1.1 (2026-02) 13 Annex B (informative): ETSI UCYBEX Framework Resource Record Example UCYBEXversion 1.0.1 UCYBEXresourcetype spec UCYBEXresourcename ETSI TS 104 170 V1.0.1 , Cyber Security (CYBER); Universal Cybersecurity Information Exchange Framework - Repository UCYBEXresourceaddress https://www.etsi.org/deliver/etsi_ts/104170[TBD] UCYBEXresourcecontact France, ETSI Secretariat, ETSI 650, Route des Lucioles 06560 Valbonne - Sophia Antipolis FRANCE, secretariat@etsi.org UCYBEXresourceaccess UCYBEXresourcetrust Certificate, fdfad996ee0874b568dc40b300ec036d91456150b1acfaf69c25b2bb13f55483 UCYBEXnormbindings UCYBEXnote ETSI implementation specification for UCYBEX framework resource repository ===== UCYBEXversion 1.0.1 UCYBEXresourcetype repository UCYBEXresourcename UCYBEX Framework Resources Known to ETSI UCYBEXresourceaddress https://forge.etsi.org/rep/explore/projects [TBD] UCYBEXresourcecontact France, ETSI Secretariat, ETSI 650, Route des Lucioles 06560 Valbonne - Sophia Antipolis FRANCE, secretariat@etsi.org UCYBEXresourceaccess UCYBEXresourcetrust Certificate, fdfad996ee0874b568dc40b300ec036d91456150b1acfaf69c25b2bb13f55483 UCYBEXnormbindings UCYBEXnote ETSI implementation of UCYBEX resource framework repository ===== UCYBEXversion 1.0.1 ….. ETSI ETSI TS 104 170 V1.1.1 (2026-02) 14 Annex C (informative): Bibliography • ML Commons: Croissant. • Schema.org: Schemas. ETSI ETSI TS 104 170 V1.1.1 (2026-02) 15 History Version Date Status V1.1.1 February 2026 Publication |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 1 Scope | The present document describes considerations for situations in which providers choose to adopt web-based portal solutions to respond to requests from Authorized Organizations. The present document describes portals and explains how existing ETSI TC LI specifications can be used to improve portal design. The present document shows how portals can become a stepping stone towards adoption of interfaces defined by an ETSI TC LI Technical Specification. The present document highlights some caveats around portals and makes it clear that portals are not a substitute for meeting ETSI TC LI Technical Specifications. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 2 References | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 2.1 Normative references | Normative references are not applicable in the present document. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 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 may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI TS 103 976: "Interface for Lawful Disclosure of vehicle-related data". [i.2] ETSI TS 103 120: "Lawful Interception (LI); Interface for warrant information". [i.3] ETSI TS 103 307: "CYBER; Security Aspects for LI and RD Interfaces". [i.4] ETSI TS 103 280: "Lawful Interception (LI); Dictionary for common parameters". [i.5] ETSI TS 103 705: "Lawful Interception (LI); Data Structures for Lawful Disclosure". |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 3 Definition of terms, symbols and abbreviations | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 976 [i.1] and the following apply: Authorized Organization (AO): any organization legally authorized to make requests and receive results provider: organization responding to a request (the organization that includes the Request Processing System) Request Processing System (RPS): system within an organization which holds the data that is subject to the request where there is a lawful reason for it to respond to requests for information |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 3.2 Symbols | Void. ETSI ETSI TR 104 196 V1.1.1 (2026-02) 6 |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AO Authorized Organization API Application Programming Interface IMEI International Mobile Equipment Identity IMSI International Mobile Subscriber Identity RPS Request Processing System VIN Vehicle Identification Number |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4 Core concepts | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.1 Goal | The goal of the present document is to help people to adopt ETSI TC LI Technical Specifications i.e. full computer-to-computer API (Application Programming Interface). It is acknowledged that initially people might not be able to move to a full computer-to-computer system, and so portals can be a useful stepping stone. The present document aims to assist with the design of portal solutions, and in the longer term to facilitate the move towards adoption of ETSI TC LI Technical Specifications. The present document is neither encouraging nor discouraging the use of portals alongside an API system for the long term. Further details are given in clause 4.5. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.2 Definition of a portal | A portal is defined to be a website hosted by, or on behalf of the provider which allows an Authorized Organization to type in requests and then receive results either through the website or delivered over other channels (not specified here). |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.3 Caveat | Adoption of the present document does not imply that a system is compliant with any ETSI TC LI Technical Specification; it is not a substitute for compliance with other ETSI TC LI standards. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.4 Reference design | The approach in Figure 4.4-1 is recommended. The key point is to run one system with two front ends (one for meeting an ETSI Technical Specification, and one for a portal). The goal is to make the front end systems as thin as possible i.e. to put most of the functionality in the main Request Processing System. Figure 4.4-1: Approach to portal design ETSI ETSI TR 104 196 V1.1.1 (2026-02) 7 The design in Figure 4.4-1 is not a strict architecture or design and is not intended to constrain data flows or security boundaries. The functionality in the smaller boxes (labelled front end in Figure 4.4-1) is likely to be different between APIs and portals. This would typically include the following: • The portal needs a User Interface design; the API needs to terminate API connections. • The security is different (see clause 4.6). The functionality in the larger box (labelled Request Processing System in Figure 4.4-1) would typically be created once and could be accessed via both the portal and API solutions. It would typically include: • Single workflow engine: each request follows the same path regardless of whether it came from the portal or API. • Single way to submit query into the provider database. • Single way to create the results (meaning that the results are identical whether requested through a portal or through a API). • Single approach to supplying integrity information such as hashing (e.g. see also ETSI TS 103 307 [i.3]). • Single audit log. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.5 Use of portals alongside systems with full APIs | It is clear that the full API is the best long-term solution for high volume uses, but the present document does not advise in favour or against running portals alongside an API solution. Clause 4.5 notes some benefits and drawbacks of doing this, in order to help people make decisions about use of portals. Considerations around offering both an ETSI-compliant API and a portal (designed in line with the present document): • It is credible to state that this is a solution that can meet the needs of any AO globally. If the AO has a high volume of requests, they can use the ETSI-compliant API (designed to meet a wide range of requirements and agreed by a broad community). If an AO has a low volume of requests, or does not want to build a ETSI solution, then they can use the provider portal. With an API and a portal (producing identical results, from the same underlying system), it is realistic to state that no other solution needs to be offered or will be offered by the provider. Considerations around offering an API (without a portal): • If a provider offers an API, then it would incur some extra cost to build a portal as well. The present document is not implying it is a requirement to build portals in addition to APIs; in some scenarios the extra expense of a portal might not be justified. The security will be easier without portal access, because then the user management issues (i.e. which users are allowed to access the system) are taken care of by the AO. Further details are given in clause 4.6. The onboarding process is harder for smaller AOs, which can introduce a higher barrier to entry. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6 Security | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6.1 General | The present document does not contain a full analysis of portal security, instead.it identifies some risks and issues to consider. ETSI ETSI TR 104 196 V1.1.1 (2026-02) 8 |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6.2 Clear boundaries of responsibility | The Responsible Owner at an AO is the person who takes responsibility for a request that is issued (Was it lawful? Was it correct? Did it go to the right place? Can I justify it?). The Responsible Owner at a Provider is the person who takes responsibility for how the request is handled (Did I check it was correct and authorized? Was it lawful to release this data? Can I justify it?). In order to meet their responsibilities, it is important for a Responsible Owner to understand exactly where their responsibility starts and ends. This point will be called the Front Door. The AO Front Door is the point where a request is issued (under the authority of the AO Responsible Owner). The Provider Front Door is the point where a Provider issues the results (under the authority of the Provider Responsible Owner). The Responsible Owners may wish to get suppliers or vendors to build systems which help the Responsible Owner meet their responsibilities, i.e. to perform tasks behind the relevant Front Door. The appropriate legislation determines whether risks or obligations can be transferred to suppliers or vendors (it might be the case that risks and obligations ultimately still sit with the Responsible Owner). The Responsible Owners should make sure they know how their obligations are being met. This might include: • Knowing where their Front Door is and exactly when/why information leaves/enters. • Factors such as retention periods, user verification, data localization (where is data stored) should be clearly understood by the Responsible Owner. Care should taken about functionality that sits between the AO Front Door and the Provider Front Door (i.e. is not inside either Front Door). It is likely to be best to minimize any functionality that sits here. It might be unclear who is responsible for anything that is between the Front Doors. The following examples might be relevant: • Having stateful functionality between the Front Doors risks having a different understanding of the status of requests in AO and Provider. The Responsible Owner might have issued a request which they think has reached its destination but it has not, which might carry serious legal consequences. • Having processing between the Front Doors might cause an issue when material is used in court. It also creates a risk of differing understandings of the data at AO and Provider. It introduces the risk of mistakes taking place between one Front Door and the other. • Having storage between the Front Doors could create a data security issue. Who can see the data? Who can access it? Who is responsible for the data if compromised. Ultimately the Responsible Owner at AO or Provider (or both) will carry various consequences here. • Care should be taken about routeing or proxying between the Front Doors. Basic network-level routeing is often necessary. It is important that the choice of destination for a request was made inside the AO Front Door. Care should be taken about routeing or proxying that could result in requests going to a different place from the Front Door that the Responsible Owner chose. • There are risks about functionality which could be used by more than one AO or Provider. This carries risk of information going to the wrong place, or data being shared with people who are not entitled to see it. • Generating requests anywhere other than within the AO runs the risk of the request being unlawful as it might not have been approved and fully understood by the Responsible Owner. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6.3 Management of users | An important issue for portals is that the provider is responsible for management of the list of accredited users. In general, for a portal solution, the provider would be responsible for managing risks arising when users join or leave the Authorized Organization (AO), or where privileges are revoked. Verification of new AO users can be difficult with risks around e-mail spoofing. It is recommended to use a range of techniques (beyond looking at the email domain) in order to build confidence in AO users. The Responsible Owner at the Provider (see clause 4.6.2) is responsible for data released by the Provider and therefore this is the person who needs to understand what assurances were received, so they can decide if they are sufficient. Risks can be introduced if particular AO staff are on leave and so need to allocate certain functions to others. The risks are increased if two different AO organizations are involved. ETSI ETSI TR 104 196 V1.1.1 (2026-02) 9 |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6.4 Other security points | Standard cyber security risks (e.g. Distributed Denial of Service attack) should be considered. It should be noted that an attack through either front end (see figure 4.4-1) can affect the central Request Processing System i.e. care should be taken around the security of both front ends. If a separate results channel is created, it is important to consider the security of this channel too. 5 Parts of ETSI TC LI Technical Specifications that are applicable to portal design |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.1 List of parts of ETSI TC LI Technical Specifications | It is recommended that the following parts of an ETSI Technical Specification are used (where appropriate) as part of designing portals: 1) Fundamental model. The ETSI model has a clear boundary between what is AO-managed and what is provider-managed. There are strong reasons to have clear boundaries of responsibility: it is fundamental to many legal and policy requirements in various jurisdictions. 2) Definitions: explaining that terms from the relevant specifications (e.g. ETSI TS 103 120 [i.2], ETSI TS 103 280 [i.4] and ETSI TS 103 976 [i.1]) should be used where suitable. 3) Identifiers and house-keeping. This would include using provider and AO identifiers. 4) Request types: for certain situations (e.g. vehicles), there is a clear set of request types (see ETSI TS 103 976 [i.1]). It is recommended that these are used where they are suitable. 5) Results: where a standardized request type has been used (as described in the point about request types), it is recommended to use the corresponding response structures (e.g. see ETSI TS 103 976 [i.1]). 6) Workflow: it is recommended to follow the Workflow steps from an ETSI TS (mostly this is defined in ETSI TS 103 120 [i.2] e.g. see the Simple Workflow in ETSI TS 103 120 [i.2], clause H.2). This gives a structure for when results are delivered and when error responses are sent, etc. 7) Look at ways that ETSI TC LI data structures (ETSI TS 103 705 [i.5]) can be used to help portal design. User interface design can help support the above points. For example, it would be helpful for a user interface to guide an AO user through the ETSI-defined fields, enforcing the strongly-typed definitions from the very start of the process and using ETSI-defined terminology. It would be helpful for the user interface to guide users through the ETSI-defined workflow. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2 Use of ETSI TC LI specifications in a vehicles context | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.1 Explanation | Clause 5.2 contains illustrations of the points listed in clause 5.1, specifically for a vehicles context. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.2 Fundamental Model | This point relates to ensuring that the boundaries of responsibility are clearly demarcated. The following transitions should be clear to all parties: • The point when the AO submits a request (i.e. an obligation is created on the provider). The AO user should be asked to confirm the submission of a request (with clarity about where the request will be sent). It is helpful for everyone to be able to see and understand which stage of the workflow (described in clause 5.2.7) is in progress. ETSI ETSI TR 104 196 V1.1.1 (2026-02) 10 • The point when the response is delivered (the end of the obligation on the provider). |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.3 Definitions | For vehicles, it is recommended to use the standardized definitions for these concepts (and others where appropriate): • VIN. • Location. • Time and date. • IMSI and IMEI. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.4 Identifiers | It is helpful to have a clear system of identifiers for every party (AO or provider). It is useful to have a unique name for each organization to prevent confusion. For example, the AOs involve should work together to ensure that they do not re-use common acronyms. It is out of scope to describe personal details for any individuals on either side of the interface. It is helpful to have a unique reference number for each request that is made. There are different ways to create the reference number (either the AO creates it, or the provider does). For a portal it is recommended that there is an option for the AO to include a reference number as it submits the request. The provider is responsible for creating a unique request number (unique within that provider). The provider may use the AO reference number in their request numbering. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.5 Request types | It is recommended that a portal uses any of the request types from ETSI TS 103 976 [i.1], clause 7, that are appropriate. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.6 Results | Wherever one of the ETSI TS 103 976 [i.1] request types has been used, it is recommended to use the accompanying results format. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.7 Workflow | It is recommended to follow the steps in ETSI TS 103 120 [i.2], clause H.2.4. The benefit is that it is clear at all items who is supported to be responding next. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.8 Use of ETSI TC LI data structures | No additional comments on this topic are made in the present document. ETSI ETSI TR 104 196 V1.1.1 (2026-02) 11 Annex A: Change history Status of Technical Report ETSI TR 104 196 Considerations for using portals to support requests from Authorized Organizations TC LI approval date Version Remarks January 2026 1.1.1 First publication of the TR after approval at ETSI TC LI#71 in Sophia Antipolis (France) ETSI ETSI TR 104 196 V1.1.1 (2026-02) 12 History Version Date Status V1.1.1 February 2026 Publication |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 1 Scope | The present document specifies the general aspects and principles of the R1 interface. It is part of a TS-family covering the R1 interface specifications. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 2 References | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 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 referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. 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] O-RAN.WG2.TS.A1AP-R004: "O-RAN A1 interface: Application Protocol". [2] O-RAN.WG2.TS.Use-Case-Requirements-R004: "O-RAN Non-RT RIC & A1/R1 Interface: Use Cases and Requirements". [3] O-RAN.WG2.TS.Non-RT-RIC-ARCH-R004: "O-RAN Non-RT RIC: Architecture". [4] O-RAN.WG11.TS.SecProtSpec.O-R003: "O-RAN Security Protocols Specifications". [5] O-RAN.WG2.TS.R1TP-R004: "O-RAN Transport protocols for R1 Services". [6] O-RAN.WG6.TS.O2IMS-INTERFACE-R004: "O-RAN O2IMS-Interface Specification". [7] O-RAN.WG6.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R004: "O-RAN O2dms Interface Specification: Profile based on ETSI NFV Protocol and Data Models". [8] O-RAN.WG6.TS.O2-GA&P-R004: "O-RAN O2 Interface General Aspects and Principles". [9] O-RAN.WG11.TS.SRCS.0-R004: "O-RAN Security Requirements and Controls Specification". [10] O-RAN.WG1.OAM-Architecture: "O-RAN Operations and Maintenance Architecture". |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 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 may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Vocabulary for 3GPP Specifications (3GPP TR 21.905 version 9.4.0 Release 9)". ETSI ETSI TS 104 228 V11.0.0 (2026-02) 8 |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 3 Definition of terms, symbols and abbreviations | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 3.1 Terms | For the purposes of the present document, the following terms apply: AI/ML model: algorithm that applies AI/ML techniques to produce model output data based on model input data AI/ML model training: process to train an AI/ML model by learning the input/output relationship in a data driven manner and obtain a trained AI/ML model that can be used for inference data instance: set of data which resulted from a data job data job: entity that provides data related to a DME type DME type: data type managed and exposed by the DME services and identified by a DME type identifier O-RAN Non-real-time RAN Intelligent Controller (Non-RT RIC): logical function in the SMO framework that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in Near-RT RIC NOTE: The Non-RT RIC is comprised of the Non-RT RIC framework and Non-RT RIC applications (rApps). Non-RT RIC framework: functionality internal to the SMO framework that logically terminates the A1 interface and provides the R1 services to rApps through the R1 interface R1 interface: interface between rApps and Non-RT RIC framework via which R1 Services can be produced and consumed R1 services: collection of services including, but not limited to, service registration and discovery services, authentication and authorization services, AI/ML workflow services, RAN OAM-related services as well as A1and O2 related services Non-RT RIC application rApp: application designed to consume and/or produce R1 Services NOTE: rApps can leverage the functionality provided by the SMO/Non-RT RIC framework to deliver value added services related to intelligent RAN optimization and operation. rApp instance: individual occurrence of a Non-RT RIC application running in the Non-RT RIC runtime environment rApp instance identifier: unique identifier for each rApp instance, assigned by the SMO/Non-RT RIC framework during rApp registration |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 3.2 Symbols | Void. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence API Application Programming Interface CM Configuration Management DME Data Management and Exposure DMS Deployment Management Service EI Enrichment Information FM Fault Management FQDN Fully Qualified Domain Name ID Identifier IMS Infrastructure Management Service ETSI ETSI TS 104 228 V11.0.0 (2026-02) 9 ML Machine Learning OAM Operation And Maintenance PM Performance Management RAN Radio Access Network rAppId rApp Instance Identifier RBAC Role Based Access Control RIC RAN Intelligent Controller RT Real-Time SME Service Management and Exposure SMO Service Management and Orchestration SPS Security Protocols Specification SRS Security Requirements and controls Specification TBAC Target Based Access Control UCR Use Cases and Requirement URI Uniform Resource Identifier |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4 General Aspects of R1 Interface and R1 Services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4.1 Introduction | The following clauses cover the general aspects for R1 interface. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4.2 General principles | The general principles for the specification of the R1 interface are as follows: • The R1 interface is an open logical interface within the O-RAN architecture between the rApps and the Non- RT RIC framework. • The R1 interface supports the exchange of control signalling information and the collection and delivery of data between endpoints. • The R1 interface enables multi-vendor rApps to consume or produce the R1 services and is independent of specific implementations of the SMO and Non-RT RIC framework. • The R1 interface is defined in an extensible way that enables new services and data types to be added without needing to change the protocols or the procedures. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4.3 Specification objectives | The R1 interface specifications shall: • Facilitate inter-connection between rApps and Non-RT RIC framework supplied by different vendors. • Provide a level of abstraction between rApps and SMO/Non-RT RIC framework that can be the consumers and or producers of R1 services. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4.4 Capabilities | As described in [2] the R1 interface shall support: • Registration and Deregistration of R1 services. • Authentication of rApps. • Authorization of requests to access R1 services. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 10 • Facilitation of service discovery and service notifications for the registered R1 Services. • Registration and Deregistration of DME types. • Subscription and Unsubscription for registered DME types and collection and delivery of data for subscribed DME types. • Functionalities related to A1 and O2 interfaces, RAN OAM and AI/ML workflow. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5 R1 Services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1 Service management and exposure services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.1 General | As described in the Non-RT RIC Architecture specification [3], the Service management and exposure services provided by the SMO/Non-RT RIC framework enable: • rApp registration. • Registration of services. • Discovery of services. • Authentication and authorization. • Communication support. • Bootstrap (optional). Additionally, if the Bootstrap service is provided by the SMO/Non-RT RIC framework, an rApp can use it to discover the endpoints of the Service management and exposure services. The Service management and exposure services handle R1 services that are produced and/or consumed by rApps, as well as R1 services that are produced by functions in the SMO/Non-RT RIC framework and consumed by rApps. Additionally, the information related to the registered services is stored and the status of the service registrations is kept updated. The Service management and exposure services also handle the authorization of Service Consumers. When an R1 service is registered, it is available for discovery and invocation, by authorized Service Consumers. In the following, the term "Service Producer" refers to the role of an rApp to register and produce a service, and the term "Service Consumer" refers to the role of an rApp to discover and consume a service, using the Service management and exposure service. The term "Service management and exposure services Producer" refers to the logical R1 Service management and exposure functions in the SMO/Non-RT RIC framework acting as Service Producers of one or more of the Service management and exposure services. NOTE: An rApp can discover services produced by other functions than rApps via the R1 interface, while services registered by rApps cannot be discovered by other functions than rApps via the R1 interface. The R1 interface only specifies how rApp interacts using the Service management and exposure services in the roles of Service Producer and Service Consumer. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.2 Bootstrap service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.2.1 Overview | If the Bootstrap service is provided by the SMO/Non-RT RIC framework, an rApp can use it to discover the endpoints of the Service management and exposure services. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 11 |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.2.2 Bootstrap | The endpoint on which the Bootstrap service can be reached shall be version independent. It can be provisioned to the rApp or can be obtained e.g. from a fixed well-known address or FQDN. The following procedure is defined: • Discover bootstrap: This procedure enables determination of the endpoints of the other Service management and exposure services. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.3 Service registration service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.3.1 Overview | This service allows Service Producers to register information about the R1 services they produce. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.3.2 Registration of services | Register service is a procedure where a Service Producer declares its produced services to the Service management and exposure services Producer. Upon successful registration of a service, the information about the services is stored. Deregister service is a procedure where a Service Producer declares which services are no longer provided. The Service Producer can also update the registered information related to a service. When registering a service, the Service Producer provides the information about the service, and may provide information on, but not limited to, the following: • profile of the service; • information on how to access the service; • information on the API; • limitations/capabilities of the Service Producer. The following procedures are defined: • Register service: A Service Producer uses this procedure to register an R1 service that it produces with the capabilities that are being exposed. On receiving the request, the Service management and exposure services Producer determines whether the Service Producer is authorized to produce the service, and whether there are any conflicts. In the response, the Service management and exposure services Producer informs the Service Producer on the capabilities that they are allowed to expose. • Deregister service: A Service Producer can use this procedure to deregister an R1 service that it is registered to provide. • Update service registration: A Service Producer can use this procedure to update the registration of an R1 service that it provides. • Partially update service registration: A Service Producer can use this procedure to Partially update the registration of an R1 service that it provides. • Query registered services: A Service Producer can use this procedure to retrieve information about the registered services. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.4 Service discovery service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.4.1 Overview | This service allows Service Consumers to discover R1 services they intend to consume. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 12 |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.4.2 Discovery of services | For service discovery, a set of procedures enables a Service Consumer to retrieve information on available services based on selection criteria. NOTE: Available services either have been registered by service-producing rApps using the Service registration service (in case these are produced by rApps) or have been made known to the Service discovery service Producer by other means (in case they are produced by Service Producers inside the SMO/Non-RT RIC framework). Upon receiving the request to discover services, the Service management and exposure services Producer verifies the identity of the Service Consumer (see clause 5.1.6). The Service management and exposure services Producer retrieves the stored service information, applies the authorization policy, and performs filtering of service information based on the selection criteria provided in the request. The following procedures are defined: • Discover services: A Service Consumer uses this procedure to discover registered services. The Service Consumer can provide selection criteria to inquire about the registered services. The response contains a filtered list of available services based on which services the consumer is authorized to access. • Subscribe service availability: A Service Consumer can subscribe to notifications regarding changes in service(s) that are available and thereby receive a notification when a service has been registered, updated, or deregistered by a Service Producer. The subscription is created for the Service Consumer based on the services and capabilities that it is authorized to access, i.e. the Service Consumer only gets notified about changes in registration status of services that it is authorized to access. Upon subscription, the Service Consumer can pass selection criteria in order to control the set of services about which it wishes to be notified. • Update service availability subscription: A Service Consumer can update each of its own subscriptions for notifications regarding changes in the available services. • Unsubscribe service availability: A Service Consumer can unsubscribe from notifications regarding changes in the available services. • Notify service availability changes: The Service management and exposure services Producer can use this procedure to notify a subscribed Service Consumer about changes in the set of registered services that the Service Consumer is authorized to access. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.5 Void | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.6 Authentication and authorization | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.6.1 Overview | Authentication and authorization are realized as a combination of procedures and services that allow asserting the identity of Service Producers and Service Consumers and ensure that only authorized consumers can access the R1 services. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.6.2 Authentication | Authentication will be performed to authenticate the Service Consumers and Service Producers to allow them to provide or access R1 Services. Service Consumers and Service Producers can initiate secure communication for R1 services after the authentication information is validated. Authentication procedures shall comply to the requirements specified in SRS [9], clause 5.2.6. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.6.3 Authorization | Authorization procedures are used to grant Service Consumers access to registered R1 services and to allow Service Producers to produce R1 services. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 13 Authorization can be based on a mechanism to enforce authorization by policies, where exposed R1 services are further subject to authorization policies before granting access to registered services. Authorization policies refer to the attributes that are associated to the Service Consumer. For example, authorization policy can be RBAC or TBAC and the additional details are supplied in the policy attributes. Authorization procedures shall comply to the requirements specified in SRS [9], clause 5.2.6. The following procedures are defined: • Access token request: A Service Consumer can use the Access token request procedure to request access to the services as specified in SPS [4], clause 4.7.3.2. A token is granted for subsequent use of the requested R1 services that require authorization as specified in SPS [4], clause 4.7.3.3. • Revoke access: A Service Consumer with appropriate privileges (administrator) can use the Revoke access procedure to revoke the access to exposed R1 services. NOTE: The details of the Revoke access procedure are not defined in the present document. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.7 rApp registration service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.7.1 Overview | The rApp consumes this service to register with the Service management and exposure services Producer. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.7.2 rApp registration management | The rApp consumes this service to register with the Service management and exposure services Producer and may provide the following information such as rApp name, vendor, software version, certificates, role of the rApp (Service Producer and / or Service Consumer), and security credentials. On successful registration, the Service management and exposure services Producer responds with an rApp identifier (rAppId). NOTE: The procedure for provisioning the security credentials by an rApp with the Service management and exposure services Producer is not defined in the present document. The following procedure are defined: • Registration: An rApp can use this procedure to register with Service management and exposure services Producer. • Update registration: An rApp can use this procedure to update its registration with Service management and exposure services Producer. • Deregistration: An rApp can use this procedure to deregister with Service management and exposure services Producer. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2 Data management and exposure services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.1 General | As described in the Non-RT RIC Architecture specification [3], the Data management and exposure services enable: • Registration of DME types. • Discovery of DME types. • Request for data. • Subscription to data. • Collection of data from Data Producers and consumption of data by Data Consumers. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 14 • Access to optional data processing in the SMO/Non-RT RIC framework. The Data management and exposure services use DME types as descriptions of certain types of data that are available. A DME type is defined by a DME type identifier and the syntax of the DME type is given by an associated schema. A DME type is defined by one schema while a schema may be associated with one or multiple DME types. A Data Producer registers its production capabilities related to a DME type. The production capabilities information includes DME type information and producer constraints. When one or more production capabilities related to a DME type have been registered, it is available for discovery, and request for / subscription to data, by authorized Data Consumers. A Data Consumer uses the discovered information about the DME type for requesting or subscribing to data instances. Further, the data instances for a DME type may be stored, or the actual data production may be triggered by the SMO/Non-RT RIC framework on the need for data collection, including based on a request for data by a Data Consumer or a data offer from a Data Producer. Data Consumer refers to an rApp that can consume data for a DME type and Data Producer refers to an rApp that can produce data for a DME type. Based on DME type information, to trigger data collection or data consumption, data instances can be requested or subscribed to. While a data request causes the delivery of a data instance as a one-time response, a data subscription potentially causes multiple data delivery actions. Data consumption refers to a Data Consumer requesting for or subscribing to a data instance. Data collection refers to the SMO/Non-RT RIC framework requesting for or subscribing to a data instance. When initiating a data request or data subscription, the data instance to obtain is defined by the DME type information and by additional characteristics as listed below. NOTE 1: DME type information can be made available to Data Consumers using the Discover DME types procedure (see clause 5.2.3.2) or from configuration. DME type information can be made available by Data Producers to the Data management and exposure functions using the Register DME types procedure (see clause 5.2.2.2). This information that defines a data instance may contain, but is not limited to, the following parameters: • DME type identifier; • time interval for the data instance (start and end of the interval during which the data have been or will be collected); • granularity of collection (how often data are to be collected); • periodicity of delivery (how often data are to be delivered); • scope (i.e. filter on the data); • target (i.e. filter on the managed objects that the data is associated with). The collection of data from the Data Producers can for instance be started based on a trigger from a Data Consumer that requests/subscribes to specified data that needs to be generated and collected, at the discretion of functions in the SMO/Non-RT RIC framework or based on a data offer from a Data Producer. If an additional Data Consumer request for / subscribes to a data instance of a certain DME type and scope that is already being collected by the Data Management and Exposure functions, no additional data collection will be started with the Data Producer if the collected data meets the criteria of additional request. Once the data production is initiated, Data Consumer can query the status of production of data instances, or the Data Consumer can be notified if there are any changes in data production as part of subscribe data. Data management and exposure services include services that are produced by the Data management and exposure functions, as well as services to be produced by the Data Producers or Data Consumers and consumed by the Data management and exposure functions. NOTE 2: In the Non-RT RIC Architecture specification [3], it is described that the Data management and exposure services can enable an rApp to discover and consume DME types produced by functions other than rApps, and that DME types produced by rApps can be consumed by functions other than rApps. The R1 interface only specifies how rApps interact with the Data management and exposure service in the roles of Data Producer and Data Consumer. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 15 |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.2 Data registration service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.2.1 Overview | Data Producers consume this service to register DME types. The Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.2.2 Registration of DME types | Register DME type is a procedure where a Data Producer registers its production capabilities related to a DME type. Query DME type registration is a procedure where a Data Producer queries its production capabilities related to a DME type that it has previously registered. Update DME type registration is a procedure where a Data Producer updates its production capabilities related to a DME type that it has previously registered with the Data registration and discovery service Producer. Deregister DME type is a procedure where a Data Producer deregister its production capabilities related to a DME type. As part of the Register DME type procedure, the Data Producer provides the data type identifier and further information about its production capabilities related to the DME type, such as if it is stored e.g. in an object store or can be continuously produced and delivered and may provide information on, including but not limited to, the following: • DME type information which includes: - information on how to deliver the data, e.g. via push, pull or streaming; - periodicity of the data, in case it is generated periodically; - information on the data syntax (schema); - the supported data delivery methods (i.e. push and pull) by the Data Producer; - producer constraints of the Data Producer to filter the data (e.g. to provide only certain types of events if requested so by the Data Consumers); - information whether the Data Producer supports data request or data subscription or both. The following procedures are defined: • Register DME type: A Data Producer uses this procedure to register its production capabilities related to a DME type. On receiving the request, the Data registration service Producer determines whether the Data Producer is authorized to produce the DME type. In the response, the Data registration service Producer informs the Data Producer if it is allowed to produce the DME type. • Query DME type registration: A Data Producer uses this procedure to retrieve information about a its registration of production capabilities related to a DME type that it has previously registered. • Update DME type registration: A Data Producer uses this procedure to update its registration of production capabilities related to a DME type that it has previously registered. • Deregister DME type: A Data Producer can use this procedure to deregister its production capabilities related to a DME type that it has previously registered for which it is no longer able to produce data instances. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.3 Data discovery service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.3.1 Overview | Data Consumers consume this service to discover available DME types. The Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.3.2 Discovery of DME types | This set of procedures enables a Data Consumer to retrieve information on the registered DME types. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 16 Discovery of a DME type does not imply availability of data instances of that DME type. It is just an indication that Data Consumers can request or subscribe to data for that DME type. It can happen that the actual data production is only triggered by the request or subscription actions of the Data Consumers. The following procedures are defined: • Discover DME types: A Data Consumer can discover the DME types that are available. For each DME type, a DME type identifier and additional metadata are provided. • Query DME type information: A Data Consumer can retrieve information on a specific DME type identified by a DME type identifier. Such information enables the Data Consumer to formulate a request or subscription for data instances of that DME type. • Subscribe DME types changes: A Data Consumer can subscribe to notifications regarding changes in the set of available DME types and thereby receive notifications when DME types have been registered or deregistered. The subscription is created for the Data Consumer based on the DME types that it is authorized to access, i.e. the Data Consumer can only subscribe to get notified about changes in availability status of DME types that it is authorized to access. • Unsubscribe DME types changes: A Data Consumer can unsubscribe from notifications regarding changes in the set of available DME types. • Notify DME types changes: The Data registration and discovery service Producer uses this procedure to notify a subscribed Data Consumer about changes in the set of available DME types. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.