Subject: [Capwap] CAPWAP Primary objective

From: "David T. Perkins" <[email-masked]>
Date: Mon, 6 Nov 2006 14:14:15 -0800 (PST)

HI,

In all of the detailed discussions about specific technical
points, it appears that the primary objective of the CAPWAP
protocol is being missed. I want to restate what I believe 
it to be, and ask the WG chairs to judge concensus.

The primary objective of the CAPWAP protocol is:

 To provide for interoperation of WTPs and ACs so that
 basic operation and management can occur when a system
 is created from devices from different manufacturers
 and/or different versions of the CAPWAP protocol.

 In the initial version, the scope of interoperation is
 limited to a single AC and multiple WTPs.

 The operations that must be supported via the CAPWAP
 protocol MUST be complete so that no other management
 protocol need be implemented for life-cycle operation
 of the system. For example, if a WTP supports "in the
 field" image modification (upgrade or downgrade),
 this must be supported in CAPWAP and the device
 and not solely through another management interface,
 such as ssh to the WTP and then scp a new image
 to the WTP. Likewise, the addition or replacement
 of X.509 certs must be supported via CAPWAP if the 
 WTP supports X.509 cert management.

Regards,
/david t. perkins

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap