[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: onlinkassumption-00 comments



On Mon, 17 Nov 2003 08:18:45 +0200 (EET), "Pekka Savola"
<pekkas@netcore.fi> said:
> On Sun, 16 Nov 2003, Chirayu Patel wrote:
> > >    on-link until at least address resolution has failed, which is
> > >    no less than three seconds (MAX_MULTICAST_SOLICIT *
> > >    RETRANS_TIMER)
> > >
> > > ==> isn't this four seconds, i.e., (MAX_MULTICAT_SOLICIT + 1) *
> > > RETRANS_TIMER .. remember that the last retransmission attempt has
> > > to time out as well before giving up ?
> >
> > There is no delay before sending the first one, and for each NS
> > (MAX_MULTICAST_SOLICIT in number) there is a RETRANS_TIMER wait.
> > Hence, it will be (MAX_MULTICAST_SOLICIT * RETRANS_TIMER).
>
> I mean, there has to be some delay after sending the first address
                ^^^^^^^^^^^^^^^^^^^^

The only delay will be for processing i.e. table lookup etc, and not a
timer based delay. It will be negligible when compared to RETRANS_TIMER.

So, for all practical purposes the aggregate delay will be
(MAX_MULTICAST_SOLICIT * RETRANS_TIMER).

> resolution request (before the first retransmit).
>
> So the delay after initiating the retransmissions is 3 seconds, but
> there should be some delay before that as well, yes?