Hi,
let me CC to 6man ML,
Per RFC4861,
6.3.4. Processing Received Router Advertisements
...
- If the address is already present in the host's Default Router
List and the received Router Lifetime value is zero,
immediately
time-out the entry as specified in Section 6.3.5.
...
6.3.5. Timing out Prefixes and Default Routers
Whenever the invalidation timer expires for a Prefix List entry,
that
entry is discarded. No existing Destination Cache entries need be
updated, however. Should a reachability problem arise with an
existing Neighbor Cache entry, Neighbor Unreachability Detection
will
perform any needed recovery.
Whenever the Lifetime of an entry in the Default Router List
expires,
that entry is discarded. When removing a router from the Default
Router list, the node MUST update the Destination Cache in such a
way
that all entries using the router perform next-hop determination
again rather than continue sending traffic to the (deleted) router.
I'm not sure what does "immediately time-out the entry as specified
in Section 6.3.5." mean.
Does it mean both paragraphs in 6.3.5. or just the latter paragraph ?
If the latter paragraph only should be executed, the address given
by rogue RA remains, right ?
On 2009/11/09, at 19:55, Yuji Sekiya wrote:
At Mon, 9 Nov 2009 19:52:48 +0900,
Arifumi Matsumoto wrote:
IIRC, routerlifetime and address lifetime is not correlated.
So, that address can be used for the source address for
outgoing sessions, right ?
I think some of implementation bind prefix and its default
router, so default router is expired, the prefix is not
selected as source address.
-- Yuji Sekiya
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
