Re: [Idr] Hold Negotiation

On Fri, Mar 07, 2008 at 06:17:57PM -0800, Vishwas Manral wrote:
> I found an ambiguity in the Hold Time negotiation for the value of 0 received.
> 
> The idea of negotiation of the Hold time is that if we will use the
> smaller of the two values of Hold time to be the actual Hold Time. A
> value of 0, actually means the Maximum Hold time. So in case we get a
> value of 0 from the neighbor, should we use the value of Hold time as
> 0(a smaller numeric value - but a bigger  value as such) or should we
> use the value of (x > 0) as it is logically lesser than the value of 0
> Hold time.
> 
> I would think we want the latter. Do let me know what you think?

RFC 4271 says the following:
: If the negotiated hold time value is zero, then the HoldTimer and
: KeepaliveTimer are not started.

This is supported at various points throughout the FSM documentation
calling out the case of non-zero and zero.  For example:

:         - if the HoldTimer initial value is non-zero,
:             - starts the KeepaliveTimer with the initial value and
:             - resets the HoldTimer to the negotiated value,
:           else, if the HoldTimer initial value is zero,
:             - resets the KeepaliveTimer and
:             - resets the HoldTimer value to zero,
:         - and changes its state to OpenConfirm.

So, while non-zero values are a negotiated timer the zero case is
intended to shut off the timers.

-- Jeff
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr