Hi, Yao.
This is the same answer with "Subject: [users:00530] Self_Test_1.4.9 ND #8".
The router must use the same value of AdvReachableTime as his own BaseReachableTime.
RFC 4861 says,
6.2.1. Router Configuration Variables
------------------------------------------------------------------------
2456 The above variables contain information that is placed in outgoing
2457 Router Advertisement messages. Hosts use the received information to
2458 initialize a set of analogous variables that control their external
2459 behavior (see Section 6.3.2). Some of these host variables (e.g.,
2460 CurHopLimit, RetransTimer, and ReachableTime) apply to all nodes
2461 including routers. In practice, these variables may not actually be
2462 present on routers, since their contents can be derived from the
2471 variables described above. However, external router behavior MUST be
2472 the same as host behavior with respect to these variables. In
2473 particular, this includes the occasional randomization of the
2474 ReachableTime value as described in Section 6.3.2.
Please see from line 2459.
Thanks,
On Fri, 01 Feb 2008 15:53:26 -0700
Yinghui Yao <Yinghui.Yao@alcatel-lucent.com> wrote:
> Hi,
>
> I think this is an invalid test. TAHI is mistaking ReachableTime with
> AdvReachableTime. The test asks the user to send RA with rltime 10000,
> this should only affect the value in RA packet. For the router itself,
> it would still use ReachableTime (calculated from BaseReachableTime) to
> time its ND entries out. Please give me some comments.
>
> Thanks,
> Yinghui Yao
> Alcatel-Lucent
>
>
------------------------------------------------------------------------
Yukiyo Akisada <akisada@tahi.org>