Pat to ask Michael for use cases showing what's the benefit of adding these 
messages.

I do not believe there is a case where a CAPWAP AP would reboot out of its own 
will, without the AC knowing, unless it is a fatal error. If there is a fatal 
error on the AP, it is unlikely that the AP would be able to send a message to 
the AC. Further, if the AC wants to reset, it could send a reset AP to all of 
its connected APs.

> If I understand properly, you are asking for a response to the Reboot 
> request, to allow the AC to immediately clear out its state?

This is only one application.
Aother scenario:

Because AP occurs some fatal error, it maybe restart the system of AP. Before 
this operation, I recommend AP need try to notify AC this information. Based 
on this, AC can immediately clear out its state.

Best regards
Michael




> 
> Pat Calhoun
> CTO, Wireless Networking Business Unit Cisco Systems
> 
> 
> 
> > -----Original Message-----
> > From: zhaoyujin 31390 [zhaoyujin@huawei.com]
> > Sent: Tuesday, February 07, 2006 9:20 AM
> > To: capwap@frascone.com
> > Subject: [Capwap] I recommend LWAPP add a new notification message 
> > "Gratuitous disconnect notification"
> > 
> > Hi:
> > 
> >   Many protocol defines "Gratuitous notification message". 
> > Based on this message, the peer device can avoid to wait timeout for 
> > detecting the protocol is down and release the system resource.
> > 
> >   At present, LWAPP defines "Reset AP", I think it is not enough.
> > 
> >   Can LWAPP add a same message. Before AP reboots, it try to send a 
> > "Gratuitous notification message" to AC. And same for AC.
> > 
> > Best regards
> > Micheal
> > 
> >