Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000010

IPv6 Testing Conformance (TTCN3 + TPs)

Test Case (TTCN3)

public

31-08-2006 16:07

12-09-2007 18:48

Reporter

user9

Assigned To

Alexandre Berge

Priority

normal

Severity

minor

Reproducibility

always

Status

resolved

Resolution

fixed

Platform

OS Version

Summary

0000010: TC_COR_1056_01 Routing Header

Description

In test-case TC_COR_1056_01, we are sending an Echo Request to IUT with a Routing Header of Type 0. The IPv6 Destination Address of the message is a Multicast Address, and hence, we expect no Echo Request from the IUT (this we are verifying by f_expectNoMessage).

But, the SegmentsLeft field in the Routing Header has been made zero in the test-case.

My doubt is that when the IUT finds the SegmentsLeft field in the Routing Header as zero, it will not follow the checks specified in the RFC in case a Routing Header is present. The IUT will process the received Echo Request, as if, without any Routing Header, and thus, send an Echo Request in response to it.

This can be deduced from the following algorithm given in RFC-2460:

RFC Text:

if Segments Left = 0 {

      proceed to process the next header in the packet, whose type is

      identified by the Next Header field in the Routing header

   }

   else if Hdr Ext Len is odd {

         send an ICMP Parameter Problem, Code 0, message to the Source

         Address, pointing to the Hdr Ext Len field, and discard the

         packet

   }

   else {

      compute n, the number of addresses in the Routing header, by

      dividing Hdr Ext Len by 2

      if Segments Left is greater than n {

         send an ICMP Parameter Problem, Code 0, message to the Source

         Address, pointing to the Segments Left field, and discard the

         packet

      }

      else {

         decrement Segments Left by 1;

         compute i, the index of the next address to be visited in

         the address vector, by subtracting Segments Left from n

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

            discard the packet

         }

         else {

                   :

                   :

My interpretation from the above RFC text is, that, the check whether IPv6 Destination Address is a multicast is performed on the packet only if the “SegmentsLeft” field in the Routing Header is greater than zero.

Tags

No tags attached.

Cor - Mob - Sec - Trans

Attached Files

Relationships

Notes
(0000198) Alexandre Berge (administrator) 07-11-2006 11:53	Fixed during Beijing Plugtests 2006

Issue History
Date Modified	Username	Field	Change
31-08-2006 16:07	user9	New Issue
31-08-2006 18:09	user10	Status	new => feedback
22-09-2006 14:45	user1	Source (company - Author)	=> Huawey
07-11-2006 11:53	Alexandre Berge	Status	feedback => resolved
07-11-2006 11:53	Alexandre Berge	Fixed in Version	=> Next Release
07-11-2006 11:53	Alexandre Berge	Resolution	open => fixed
07-11-2006 11:53	Alexandre Berge	Assigned To	=> Alexandre Berge
07-11-2006 11:53	Alexandre Berge	Note Added: 0000198
12-09-2007 18:48	user10	Project	@3@ => IPv6 Testing Conformance (TTCN3 + TPs)

MantisBT 1.2.14 [^]