Subject: FSM review

From: "Xia W Zhao" <[email-masked]>
Date: 12 Sep 2002 19:13:05 -0400

Sue,

A standard description should serve better instead of using following
different ways:
"starts peer connection"
"starts the BGP peer session"
"start the peer Connection"
"start the BGP session"

Event4 & Event5: Definition:
  "The passive flag indicates that the peer will listen prior to
establishing a connection." sounds like normal peers do not listen prior
to establishing a/the connection. It should be changed to
  "The passive flag indicates that the peer will not initiate a
connection but listen prior to establishing a connection."

Event6 & Event8 & Idle state: 
  The following words 
  "persistent peer oscillation"
  "persistent BGP adjacency flapping"
  "persistent BGP peer flapping"
  "persistent BGP peer oscillation"
 
  should be consistent by using 
  "persistent BGP peer flapping". Because flapping can be caused by
oscillation and others, using flapping is more accurate.

Event8:
  "idle Hold timer", "Idle Hold timer", "Idle Hold Timer" should be
changed to

  "idle hold timer"

Event10: "hold time expires" should be changed to 
  "hold timer expires"

"8.2.3) Transport Message based" should be changed to 
"8.1.3 Transport Message Based Events"

Event14 Definition:
 "Transport request received with either ..." not clear to me. Is it
better to change it to
  "Event indicating transport received with either ..." if this is what
it meant.

Event17
  "Transport connection fails" should be changed to
  "Transport Connection Failed"

  "This BGP peer receives a transport connection failure notice" should
be changed to
  "The local system has received a transport connection failure notice"
  
  "the remtoe BGP peer's TCP machine" should be changed to 
  "the remote site' TCP machine", and

  "The local peer" should be changed to
  "The local system" for the purpose of consistent.

"8.2) Description of FSM" should be changed to
"8.2 Description of FSM".

Xia