Date: Tue, 1 Apr 2008 17:12:49 +0900
From: Hiroshi MIYATA <miyata@tahi.org>
Subject: [dhcptest:00271] Re: [Client Test] Timeout value is short at #28
To: dhcptest@tahi.org
Message-Id: <71FDEDFC-CC62-4A39-9233-4B2E8C628C52@tahi.org>
In-Reply-To: <20080331191659.aa10cb0a.mitch@linux.vnet.ibm.com>
References: <20080331191659.aa10cb0a.mitch@linux.vnet.ibm.com>
X-Mail-Count: 00271

Correct! ;-)

....miyata

On 2008/03/31, at 19:16, Mitsuru Chinen wrote:

> Hi there,
>
> I found an issue in the following client test:
>  #28 Part C : Maximum Elapsed Time in elapsed-time field
>
> Timeout value is 610 for receiving retransmitted Renew messages.
> I suppose 610 comes MRT(600) + some buffer(10).
> However, the maximum value of RT is defined with the following
> calcuration. (ref. RFC3315, Section 14)
>
>  RT = MRT + RAND_MAX * MRT
>
> As the RAND_MAX is 0.1. the maximum value of RT is 660.
> Therefore, I think the timeout value should be 670.
> The patch below is an proposal patch.
>
> Thank you,
> ----
> Mitsuru Chinen <mitch@linux.vnet.ibm.com>
>
> diff -uprN DHCPv6_Self_Test_P2_1_0_8.orig/rfc3315/ 
> C_RFC3315_22_9_ElapTimeOpt_maxtime.seq DHCPv6_Self_Test_P2_1_0_8/ 
> rfc3315/C_RFC3315_22_9_ElapTimeOpt_maxtime.seq
> --- DHCPv6_Self_Test_P2_1_0_8.orig/rfc3315/ 
> C_RFC3315_22_9_ElapTimeOpt_maxtime.seq	2007-02-01 16:50:26.000000000  
> +0900
> +++ DHCPv6_Self_Test_P2_1_0_8/rfc3315/ 
> C_RFC3315_22_9_ElapTimeOpt_maxtime.seq	2008-03-31 11:33:16.000000000  
> +0900
> @@ -64,7 +64,7 @@ my $IF0 = "Link0";
> my ($plifetime, $vlifetime) = (3000, 3500);
> #my ($time1, $time2) = (0.5*$plifetime, 0.8*$plifetime);
> my ($time1, $time2) = (50, 2500);
> -my $timeout = 610;
> +my $timeout = 670;
> my $maxrencounter = 9;
> vCapture($IF0);
> #--------------------------------------------------------------#
>