Capwap Mailing List: Re: ChangeStatePendingTimer clarification

[Pat Calhoun (pacalhou) (pcalhoun]

Smitha,
 
Thanks for pointing out this error. The fix is actually quite simple, as
there was a typo in the text below. The text currently reads:
"The WTP also starts the ChangeStatePendingTimer timer (see Section
4.7)."

But instead should have read:
"The AC also starts the ChangeStatePendingTimer timer (see Section
4.7)."

There is already text in the Configure to Reset state transition that
covers the case where the ChangeStatePendingTimer timer expires.

Thanks,

PatC
________________________________

From: Pat Calhoun (pacalhou) 
Sent: Sunday, December 02, 2007 2:27 PM
To: Smitha Smitha (ssmitha); capwap
Subject: Re: [Capwap] ChangeStatePendingTimer clarification


Unfortunately this message got lost in the shuffle. I have created
tracker entry 25.
 
PatC

________________________________

From: Smitha Smitha (ssmitha) 
Sent: Monday, August 13, 2007 7:52 PM
To: capwap
Subject: [Capwap] ChangeStatePendingTimer clarification


The definition for ChangeStatePendingTimer is as given below:
 
  The maximum time, in seconds, the AC will wait for the Change State
   Event Request from the WTP after having transmitted a successful
   Configuration Status Response message.  The default value is 25
   seconds
 
So - according to this ChangeStatePendingTimer is started after sending
configuration status response.
 
Transition from Join to Configure:
 
  AC:  This state transition occurs immediately after the AC
         transmits the Join Response message to the WTP.  If the AC
         receives the Configuration Status message from the WTP, the AC
         MUST transmit a Configuration Status Response message (see
         Section 8.3) to the WTP, and MAY include specific message
         elements to override the WTP's configuration.  The WTP also
         starts the ChangeStatePendingTimer timer (see Section 4.7).

This does not clarify when ChangeStatePendingTimer is started and also
no timer is started after sending a Join Response message to the WTP. If
the WTP never sends a Configuration Status message, AC will hold the
DTLS session. So, I think we should start the neighbor dead interval
timer after sending join response. That will solve the issue.
 
Thanks
Smitha