Index: [Article Count Order] [Thread]

Date: Wed, 5 Mar 2008 20:10:15 -0800
From: "Hunt Peter (Nokia-S&S/MtView)" <Peter.Hunt@nokia.com>
Subject: [users:00632] Re: Question about test V6LC_2_2_14_C in IPv6 Core suite 1-4-11
To: ext Yukiyo Akisada <akisada@tahi.org>
Cc: <users@tahi.org>
Message-Id: <00FF785D-1246-42FE-93D0-936DA78B90F4@mimectl>
In-Reply-To: <20080306125944.28ec7dcc.akisada@tahi.org>
References: <0D756262-E9D6-4D19-819E-6CF9232DC8C9@mimectl>, <20080306125944.28ec7dcc.akisada@tahi.org>
X-Mail-Count: 00632

Thanks very much for the quick reply.Best regards,Peter HuntFrom: ext Yukiyo AkisadaSent: Wed 3/5/2008 7:59 PMTo: Hunt Peter (Nokia-S&S/MtView)Cc: users@tahi.orgSubject: Re: [users:00630] Question about test V6LC_2_2_14_C in IPv6 Core s=uite 1-4-11Hi, Peter.Thanks for your input.It is completely tester's failure.The calucuration is done only by back calculation from the unicast NS.So, your situation must be happen.Usually, the problem is hidden by repeating the testbecause ReachableTime has the randomness.I will change the judgement.The tester must also care about actual time when NUT reply the Echo.Regards,On Wed, 5 Mar 2008 17:57:00 -0800"Hunt Peter (Nokia-S&S/MtView)" <Peter.Hunt@nokia.com> wrote:> > I'm running the Self Test suite in the following configuration:> > * Environment: FreeBSD 6.3> * Test Tool version: v6eval 3.0.12> * Self Test package version 1-4-11> > I have a question about the test V6LC_2_2_14_C in the v2 Core suite, whic=h tests the reachable time of a router.> > The test determines the reachable time of the router by resolving an ND e=ntry, sending echo requests each second until it receives an NS from the NU=T, and then subtracting 5 seconds (i.e. the DELAY_FIRST_PROBE_TIME) from th=e time it took to receive the NS. It then verifies the reachable time is be=tween 5 and 15 seconds (i.e. the valid range for the randomized reachable t=ime derived from a 10-second configured value).> > My concern is that the test might result in a false failure if the random=ized reachable time value is close to 15 seconds, and there is a delay betw=een when the reachable time for the entry is reached, and when the NUT rece=ives the next echo request from the TN.> > For example, if the randomized reachable time is 14.8 seconds:> > * At 0 seconds, the entry on the NUT is resolved> * At 14.8 seconds, the reachable time is reached and the entry>   enters STALE state> * At 15.3 seconds (say) the NUT receives the next echo request>   from the TN, sends an echo reply, and the entry enters DELAY state.> * At 20.3 seconds, the entry enters PROBE state and the NUT sends>   the next NS.> > In this case, the test would calculate a reachable time of 15.3 seconds a=nd fail. Yet the NUT derived the randomized value correctly.> > Does the test account for the time that the ND entry on the NUT is in STA=LE state? That is, does it account for the time between when the reachable =time expires and the next echo reply is sent?> > Thanks in advance,> > Peter Hunt> Software Engineer> Nokia S&S> ----Yukiyo Akisada <akisada@tahi.org>
	

632_2.html (attatchment)(tag is disabled)