Index: [Article Count Order] [Thread]

Date: Tue, 18 Sep 2007 16:26:36 -0500
From: "Leino, Tammy" <tammy_leino@mentor.com>
Subject: [dhcptest:00211] Re: DHCPv6 self-test RAND of .1 fails
To: <dhcptest@tahi.org>
Message-Id: <7ECEF9368E169544B43882BC98EB5D92032DAA08@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DAA06@SVR-ALH-EXC-02.mgc.mentorg.com>
X-Mail-Count: 00211

I apologize for the multiple emails, but I wanted to mention that the =tests do not fail when RAND is -.1, which leads me to believe there is =an anomaly in the TAHI test suite when RAND is .1.Best Regards,Tammy Leino>  -----Original Message-----> From: 	Leino, Tammy  > Sent:	Tuesday, September 18, 2007 5:19 PM> To:	'dhcptest@tahi.org'> Subject:	DHCPv6 self-test RAND of .1 fails> > Hello All,> > Whenever my node generates a RAND value of .1, the TAHI test suite =fails for all max retransmission time tests.  It seems the TAHI test =suite is interpretting the definition of RAND in RFC 3315 as -.1 to .1 =non-inclusive.> > Here is the situation for RFC 3315 test #37 when RAND is chosen as .1 =in retransmissions:> > First retransmission> RT = IRT + (RAND * IRT)> RT = 1 + (.1 * 1)> RT = 1.1> > Second retransmission> RT = (2 * RTprev) + (RAND * RTprev)> RT = (2 * 1.1) + (.1 * 1.1)> RT = 2.31> > Third retransmission> RT = (2 * RTprev) + (RAND * RTprev)> RT = (2 * 2.31) + (.1 * 2.31)> RT = 4.851> > The test fails here due to "Actual RT is bigger than the expected =maximum value".  I am not sure what the expected maximum value is.> > First, can someone comment on whether the TAHI test suite interprets =the RAND values defined in RFC 3315 as inclusive or non-inclusive?> > Second, if the values are supposed to be inclusive, can someone verify =that this is a problem with the TAHI test suite?> > Best Regards,> Tammy Leino> 
	

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