Subject: issues 12 - consensus & two changes - 2nd message

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

Tom and idr: 

I believe issues 12 is in consensus. Please
ack the new text below.

Sue

==================

Change 1:  new text

Active state - event 19 
 
    If an Open is received with the Open Delay timer is 
    running [Event 19], the local system 
        - clears the connect retry timer (cleared to zero),
        - stops and clears the Open Delay timer  
        - completes the BGP initialization, 
        - stops and clears the Open Delay timer
        - sends an OPEN message, 
	- send a Keepalive message,
	- if the hold timer value is non-zero,
		- starts the keepalive timer to initial value,  
		- resets the hold timer to the negotiated value,
	  else if the hold timer is zero
		- resets the keepalive timer (set to zero),
		- resets the hold timer to zero.

        - changes its state to OpenConfirm.

    If the value of the autonomous system field is the same as the local 
    Autonomous System number, set the connection status to an internal
    connection; otherwise it is "external".

Change 2 - 
 Connect state
 event 17 (currently defined as going to Active)
 event 9 (stays in Connect state)

new Text:
    
     In response to the connect retry timer expires event [Event 
     9], the local system: 
        - drops the TCP connection, 
        - restarts the connect retry timer,
	- stops the Open Delay timer and resets the timer to zero,  
        - initiates a TCP connection to the other BGP peer, 
        - continues to listen for a connection that may be 
          initiated by the remote BGP peer, and
        - stays in Connect state.

     If the TCP connection fails [Event17], the local system:
         - restarts the connect retry timer, 
	 - stops the Open Delay timer and resets value to zero,
         - continues to listen for a connection that may be 
           initiated by the remote BGP peer, and
         - changes its state to Active. 
   
Sue Hares