Subject: RE: Draft 19 - Issue 44

From: "Susan Hares" <[email-masked]>
Date: Thu, 30 Jan 2003 05:38:33 -0500

Siva:

Yes, we can change the "D" in state machine to a "y".

The issue is what if Connect state occurs and there is not
a TCP connection.  Should an OPEN with wrong version 
be accepted?  If the Open Delay flag is off, the connection
state should not be getting an Open.  The "D" action below
works for "open delay flag off".  

The "y" action you suggest can occur if the open delay
timer is on.  

If this is the issue, please confirm.

We could say: if open delay flag is on -> y action
		  if open delay flag is off -> D action 

Please let me know if this is the concern, and suggest
text.   

Thanks for looking through this state change 1 more Time (1MT).

Sue 

-----Original Message-----
From: Sivananda Ramnath - CTD, Chennai. [mailto:[email-masked]]
Sent: Monday, January 27, 2003 7:07 AM
To: Susan Hares
Cc: Sivananda Ramnath (E-mail)
Subject: Draft 19 - Issue 44

Hello,

    "Default event handling" was perhaps a poor choice of words.

    What I meant is this

    Event 23 (Notify Message Version error) only indicates a version
mismatch. By going through action sequence D, we will be performing peer
oscillation damping. Should we perform damping, since this is not really a
cause for persistent oscillation ?

    Also, since we have a distinct event to indicate a version error event,
can include text indicating that version negotiation processing should take
place upon receipt of this event ?

Siva
([email-masked])

This began with Siva saying:

 This is currently being handled in the default event processing section.
 However, we do not need to go through the peer oscillation damping
 process in this case. Can we change the wordings to reflect this, or
 move this out of peer oscillation damping processing ?

Sue replied:

1)  There is no default event handling process in the text, you
    will need to specify the text.

2) The state table below (hares-statemt-03.txt) states shows
   the changes 
-------------
Event 23
states:
current    Idle Connect Active Open-Sent Open-Cnf  Establish
     ----------------------------------------------------
next state Idle  Idle    Idle  Idle      Idle       Idle
           -----------------------------------------------
action     V      D       D     Y        Y           T
           ==============================================

V - Indicate FSM errors and ignore.
D - 1) resets the connect retry timer (sets to zero),
     2) drops the TCP connection,
     2) releases all BGP resources,
     3) increments the ConnectRetryCnt (connect retry count) by 1,
     4) [optionally] performs the bgp peer oscillation damping, and
       Goes to Idle state.
   
  Y  1) resets the connect retry timer (sets to zero),
     2) Drops the TCP connection,
     3) releases all BGP resources,
     4) [optionally]

This was discussed in the "Comments 21-30" thread: Comment #25.

----------------------------------------------------------------------------