| CAPWAP IESG Review Comment T39 | <– Date –> <– Thread –> |
|
From: Pat Calhoun (pacalhou) (pcalhoun |
|
| Date: Wed, 18 Jun 2008 10:07:48 -0700 (PDT) | |
All, Here is the IESG Review Comment: T39. Section 13 is insufficient. The recommendation concerning non-configurability of WTPs makes, sense, but what about the ACS? How are ACs configured? It is OK to say that they are configured by proprietary CLI and/or MIB interfaces that will be defined in other CAPWAP document and/or by NETCONF in the future, but something needs to be said. You are correct, the CAPWAP protocol does not provide management of the AC. This is assumed to be done out of band. I am therefore proposing the following text: <text> 13. Management Considerations [...] The CAPWAP protocol does not deal with the management of the ACs. The AC is assumed to be configured through some separate management interface, which could be via a proprietary CLI, SNMP, NETCONF or some other management protocol. </text> PatC
-
CAPWAP IESG Review Comment T39 Pat Calhoun (pacalhou), June 18 2008
-
Re: CAPWAP IESG Review Comment T39 Romascanu, Dan (Dan), June 18 2008
- Re: CAPWAP IESG Review Comment T39 Pat Calhoun (pacalhou), June 18 2008
-
Re: CAPWAP IESG Review Comment T39 Romascanu, Dan (Dan), June 18 2008
Results generated by Tiger Technologies using MHonArc.