| CAPWAP IESG Review Comment T37 | <– Date –> <– Thread –> |
|
From: Pat Calhoun (pacalhou) (pcalhoun |
|
| Date: Wed, 18 Jun 2008 09:24:50 -0700 (PDT) | |
All, Here is the IESG Review Comment: T37 - Section 8.1 - If the WTP opts to save the configuration locally - how is this option selected? Is this a local WTP configurations issue? If so please specify There are a couple of ways of dealing with this one: 1. The simplest way of dealing with this would be to make this an implementation decision. 2. Allow the AC to configure this behavior. However, this would require new message elements, additional text in the configuration request messages, etc. Given that in the end, it really doesn't matter which way the WTP decides to behave, I would prefer we go with option one and minimize the changes to the spec at this point. Therefore, my proposed text is: <text> 8.1. Configuration Consistency The CAPWAP protocol provides flexibility in how WTP configuration is managed. A WTP can behave in one of two ways, which is implementation specific: </text> PatC
-
CAPWAP IESG Review Comment T37 Pat Calhoun (pacalhou), June 18 2008
-
Re: CAPWAP IESG Review Comment T37 Romascanu, Dan (Dan), June 18 2008
- Re: CAPWAP IESG Review Comment T37 Pat Calhoun (pacalhou), June 18 2008
-
Re: CAPWAP IESG Review Comment T37 Romascanu, Dan (Dan), June 18 2008
Results generated by Tiger Technologies using MHonArc.