> 8.3. Host Specification
>
> A host receiving a valid redirect SHOULD update its Destination Cache
> accordingly so that subsequent traffic goes to the specified target.
> If no Destination Cache entry exists for the destination, an
> implementation SHOULD create such an entry.
But the above is a SHOULD and the validity checks in section 8.1
say MUST discard when this fails:
- The IP source address of the Redirect is the same as the current
first-hop router for the specified ICMP Destination Address.
If there is only one default route pointing at the link
from which the redirect was received
(or for implementations with a richer routing table,
the lookup of the destination address only finds one routing
table entry that points at that link), then the redirect can
be safely used to create a destination cache entry.
But when the lookup finds more than one possible next hops that might have
been used to send the original packet, it seems a bit dangerous to
accept the redirect.
Erik
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
