>>>>> On Thu, 23 Oct 2003 18:11:55 -0700,
>>>>> Vijay Devarapalli <[EMAIL PROTECTED]> said:
> here is another issue. it involves both 2461 and 2462.
> RFC 2461 says
> Before a host sends an initial solicitation, it SHOULD delay the
> transmission for a random amount of time between 0 and
> MAX_RTR_SOLICITATION_DELAY.
> RFC 2462 says
> If the Neighbor Solicitation is the first message to be sent from an
> interface after interface (re)initialization, the node should delay
> sending the message by a random delay between 0 and
> MAX_RTR_SOLICITATION_DELAY as specified in [DISCOVERY].
> lets assume a Mobile Node moves and attaches to a new
> link. it does router discovery and configures a Care-of
> address. the mobile node cannot send a Binding Update
> until it completes DAD for the Care-of address. these
> two random delays (before router discovery and before
> DAD) contribute a lot to the movement detection delay.
> I think this needs to be fixed.
> MAX_RTR_SOLICITATION_DELAY is 1 second. taking the worst
> case scenario, it could be 1 second before a sending
> router solicitation, one second before sending neighbor
> solicitation for DAD and then 1 second before DAD
> completes. the Binding Update cannot be sent until then.
Thanks for the pointer. I'll add this to my local issue list.
(Note to everyone: this does not mean I'm going to propose a change on
RFC2462 to address this.)
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
