Re: CAPWAP IESG Comment T38
From: Pat Calhoun (pacalhou) (pcalhouncisco.com)
Date: Wed, 18 Jun 2008 18:34:29 -0700 (PDT)
OK, closing issue 79.

PatC 

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca [at] avaya.com] 
Sent: Wednesday, June 18, 2008 7:01 AM
To: Pat Calhoun (pacalhou); capwap [at] frascone.com
Subject: RE: [Capwap] CAPWAP IESG Comment T38

Ok with me. 

Dan
 

> -----Original Message-----
> From: Pat Calhoun (pacalhou) [mailto:pcalhoun [at] cisco.com]
> Sent: Wednesday, June 18, 2008 4:56 PM
> To: capwap [at] frascone.com
> Subject: [Capwap] CAPWAP IESG Comment T38
> 
> All,
> 
> Here is the IESG Review Comment:
> 
>    T38 - Section 9 should start with deployment considerations. It 
> looks like there
>    are some assumptions made here about at least an AC being present 
> and configured at
>    deployment, and other such. This should be made clear.
> 
> I have made changes to the introductory paragraph in section 9. The 
> text now reads:
> 
> <text>
>    This section defines CAPWAP operations responsible for debugging,
>    gathering statistics, logging, and firmware management. 
> The management
>    operations defined in this section are used by the AC to either
>    push/pull information to/from the WTP, or request that the WTP 
> reboot.
>    This section does not deal with the management of the AC per se, 
> and
>    assumes that the AC is operational and configured.
> </text>
> 
> PatC
> _________________________________________________________________
> To unsubscribe or modify your subscription options, please visit:
> http://lists.frascone.com/mailman/listinfo/capwap
> 
> Archives: http://lists.frascone.com/pipermail/capwap
> 

Results generated by Tiger Technologies using MHonArc.