Re: Comments on FSM

[Susan Hares <[e-mail]>]

Kunihiro:

Thanks for the input.

Sue

At 04:54 PM 1/16/2002 -0800, Kunihiro Ishiguro wrote:
>Thanks Alex.  I've check bgp4-17 FSM.  Below new items are added.
>
>Status  : IdleHold
>Timer   : IdleHold timer
>Variable: IdleHoldtimer
>           IdleHoldtimer ceiling mentioned as "local limit"
>           ConnectRetryCnt
>Event   : Manual start
>           Auto start
>Flag    : Keep Idle
>
>Instead of IdleHold timer we should explicitly mention about Start
>timer.  It is already implicitly used in RFC1771.  It is almost same
>as IdleHold timer but hopefully does not have impact on current
>implementation.
>
>We don't need Keep Idle flag.  Instead of that just stop Start timer.
>This mechanism can be used not only exponential backoff but also
>administratively shutdown or maximum prefix overflow.  So let's keep
>it simple.




>In IdleHold state there is a description for local limit of
>IdleHoldTimer.
>
> >         Upon entering the Idle Hold state, if the IdleHoldTimer exceeds
> >         the local limit the "Keep Idle" flag is set.
>
>This should be clearly defined.  For example StartTimer Ceiling.
>
>Difference between manual start and auto start is small.  I'm not sure
>separating Start event into Manual start event and Auto start event is
>good idea or not.  So my proposal is liek this.
>
>Status  : No new status
>Timer   : Start timer
>Variable: StartTimer
>           StartTimer Ceiling
>           Connect Retry Count
>
>(Possible addition
>Event   : Manual start
>           Auto start)
>
>IMHO, this topic needs more discussion and clarification.
>
> >Maybe the exponential backoff parts could be published as a separate draft
> >instead of including it in the base specification?
>
>I agrree with Greg.  A separate draft for exponential back off make
>sense.  I think even we have a separate draft for exponential back
>off, previous draft bgp4-16 FSM description still work fine with that.
>--
>Kunihiro Ishiguro