0000009: TC_COR_1059_01 Routing Header address swapping error

ETSI's Bug Tracker - IPv6 Testing Conformance (TTCN3 + TPs)

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0000009

IPv6 Testing Conformance (TTCN3 + TPs)

Test Case (TTCN3)

public

31-08-2006 15:45

04-03-2016 11:17

Reporter

user9

Assigned To

Alexandre Berge

Priority

normal

Severity

minor

Reproducibility

always

Status

resolved

Resolution

fixed

Platform

OS Version

Cor - Mob - Sec - Trans

Summary

0000009: TC_COR_1059_01 Routing Header address swapping error

Description

In the test-case TC_COR_1059_01, the Echo Request with Routing Header sent by the 1st test-component, v_refHs01, is expected to be forwarded by the IUT, and is thus, received by the 2nd test-component, v_refHs02.

In your test-case, the address in the Routing Header of the received (forwarded) Echo Request is same as the address passed in the Routing Header of the original (sent) Echo Request, viz. v_paramsHs02.gla i.e., the Global Unicast Address of Host 2, which is our final destination. But as per RFC-2460, when the IPv6 Packet carrying Routing Header of Type 0 reaches an Address[i] in the Routing Header, the IPv6 Destination Address and the Address[i] are swapped.

Hence, the received (forwarded) Echo Request should contain the previous IPv6 Destination Address, viz. PX_GLA_IUT_A, in its Routing Header. (Please note that we will have to use the Module-Parameter PX_GLA_IUT_A instead of accessing the address of IUT_A through the CfMessage, as in the CfMessage passed to the 2nd test-component v_refHs02, the IUT’s Global Unicast Address is that of IUT_B, viz. PX_GLA_IUT_B.)

RFC Text: if Address [i] or the IPv6 Destination Address is multicast {

                                   discard the packet

                             }

                            else {

                                   swap the IPv6 Destination Address and Address[i]

Steps To Reproduce

Additional Information