<HTML dir=ltr><HEAD>
=
<META http-equiv=Content-Type content="text/html; charset=unicode">
=
<META content="MSHTML 6.00.6001.18183" name=GENERATOR></HEAD>
=
<BODY>
=
<DIV><FONT face="Courier New" color=#000000 =
size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" size=2>I'm running into a problem with =
one of the tests in&nbsp;the IPv6 Core Protocols test suite in the =
following configuration:</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" =
size=2>TN:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; FreeBSD 6.3-RELEASE</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2>Test =
Tool:&nbsp;&nbsp;&nbsp;&nbsp; v6eval-3.1.0</FONT></DIV>
=
<DIV><FONT face="Courier New" =
size=2>Package:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv6 Core =
Protocols Self_Test_4-0-3</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" size=2>Running the router tests (i.e. =
"make ipv6ready_p2_router").</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" size=2>I'm seeing a failure with test =
"V6LC_2_2_14_C - Reachable Time Configuration", which I think may be due =
to an error in the way the test script measures the reachable time. I =
suspect the test script is not accounting for the time in which the ND =
entry is in "STALE" state.</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" size=2>If I'm reading the RFC =
correctly, the ND entry should go through the following states on the =
NUT:</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" size=2>1) Enters REACHABLE state when =
NA received (and first echo reply sent)</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2>2) Enters STALE state =
ReachableTime milliseconds after NA received.</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2>3) Enters DELAY state when =
first echo reply sent after entering STALE state.</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2>4) Enters PROBE state 5 seconds =
after entering DELAY state (sends first NS)</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" size=2>The test calculates the =
reachable time as the interval between the first echo reply sent at 1) =
and the first NS sent at 4), minus 5 seconds. However, this calculation =
does not account for the time that the entry was in STALE state (i.e. =
the interval between the entry entering STALE state and the reception of =
the next echo request).</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" size=2>This error results in the =
reachable time calculation being too large, by up to the interval =
between echo requests sent by the TN. When the random reachable time is =
close to 15, this miscalculation results in the test =
failing.</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" size=2>I'm also seeing a problem where =
the TN sends echo requests at intervals of up to 1.5 seconds, which =
makes this problem worse.</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
=
<DIV><FONT face="Courier New" size=2>Best regards,</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2>Peter Hunt</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2>Software Engineer</FONT></DIV>
=
<DIV><FONT face="Courier New" size=2>Nokia =
S&amp;S</FONT></DIV></BODY></HTML>