Subject: Issue 26 - Do you want me to add

From: "Susan Hares" <[email-masked]>
Date: Mon, 20 Jan 2003 18:13:19 -0500

Siva:

At the bottom is the re-cap of issue 26.  
Below is line is the text for adding option 3.
Please confirm if you wish to add option #3.
If you do, we have consensus on this topic.

Sue

===========

Addition Option #3
===============
To add #3, I would add an Event 7b with the following state machine

    Event7b: Automatic start with passive TCP flag and 
		bgp_stop_flap flag set

           Definition: Local system automatically starts the BGP 
		  Peer connection with passive TCP flag and
		  BGP Peer oscillation enabled.  The passive TCP 
		  flag indicates that this peer will listen prior to establishing
		  a BGP connection.  The bgp_stop_flag flag indicates
		  that this peer will damp persistent oscillations of peer
		  connections (connect-disconnect-connect). 

		  The exact method of  damping persistent peer
                          oscillations is left up to the  implementation and
                          is outside of the scope of this document. 
   	
           Status:    Optional depending on local system
   
The state machine would be
    
    # Event     Idle    Connect  Active   Open    Open      Estab. 
                                          sent    Confirm   
====================================================================
    7b Auto    See peer  Connect Active    Open    Open      Estab. 
      start &  damp     /Ignore /Ignore    Sent/   Confirm/ /Ignore 
      bgp flap draft/                     Ignore   Ignore    
      stop on   F-2   
      & passive
      [note 1]

	F-2 

	If no bgp flap damping is engaged, the local sytem will: 
	  1) Restart ConnectRetry timer (with initial value)
	  2) Listen for a valid remote TCP connection  
----------------

This began with Siva asking:

  Won't a variant of this with bgp_stop_flap option set be requried ?
  We can also achieve the same by using the bgp_stop-Flap option as a
  flag that is provided as an input to the state machine.

Siva later clarified this to include:

   We already have
   Event 3 - Automatic Start
   Event 5 - Automatic start with bgp_stop_flap option set
   To make things consistent, shouldn't we either
 
   a) Add 3 new events : 1) Manual start with bgp_stop flap option set
                         2) Manual start with passive TCP establishment
                            and bgp_stop_flap option set
                         3) Automatic start with passive TCP establishment
                            and bgp_stop_flap option set

   or
  
   b) Remove Event 6, and rely on a flag to tell us wether peer flap damping
      is to be performed for the session or not.

Sue said she prefered option A.  And stated that #1 & #2 are infeasible,
but that we need to add #3.