Subject: RE: Draft 19 - Issue 40

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

Siva: 

Thank-you, we'll consider it consensus
with no changes to the text.

Sue

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

Hello,

    I am ok with this approach. My only observation is that by not doing
these actions where they are not required, it may be easier to spot errors
in an FSM implementation. This, however, can be viewed as a purely
implementation issue. Any resolution you have for this issue is fine by me.

Sivanand
([email-masked])

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

Siva opend with the observation:

 There are a few sections where the FSM draft states that the Connection
 Retry timer needs to be reset, wheras the conenct retry timer had been
 cleared prior to entering that state. We can remove these instructions
 to clear the connect retry timer.

 List of places where the connect retry timer need not be cleared

    a) Handling of Event 19 in the Connect State
    b) Handling of Events 12 in the Active State
    c) All cases where it is refered to in the OpenSent,
	OpenConfirm and Established states

Sue replied:

 Comment:
 1) Does it hurt to have the connect retry timer cleared
   at these points, since it has already been cleared.

 I felt it eased the implementations to allow the action
 routines to be shared across as many states as possible.
 You can see this a bit more actively.