1. 61 st IETF – CAPWAP Working Group1 CAPWAP Objectives Saravanan Govindan Panasonic 8 November, 2004

2. 61 st IETF – CAPWAP Working Group2 Background Based on discussions in previous meeting and on mailing list Follows outline in charter goals; –Requirements that address Problem Statement –Advantages to a CAPWAP protocol –Customer requirements

3. 61 st IETF – CAPWAP Working Group3 Adaptive Interfaces Enables protocol support for both local MAC and split MAC designs Allows for mixed deployments of both types of WTPs in a single WLAN domain –e.g. Split-MAC WTPs in local office and local-MAC WTPs in remote offices Results in a protocol that achieves true interoperability Based on scenario of

4. 61 st IETF – CAPWAP Working Group4 Support for Logical Networks Prevalent business trend in sharing physical WLAN resources –ISPs seeking cost-efficiencies in building and managing networks Sharing infrastructure addresses these concerns –Multiple logical network are created within one physical WLAN –Each logical network is assigned to a different ISP or subscriber group Protocol that supports this objective directly addresses cost concerns

5. 61 st IETF – CAPWAP Working Group5 Multiple Authentication Mechanisms With spread of WLANs, there is a diversity of authentication needs –Corporate network uses certificates and keys –Coffee shop issues temporary passcodes with each cup Differences can be present even within a single large WLAN CAPWAP protocol needs to recognize and relay different authentication information Enabling support for different authentication mechanisms is therefore crucial

6. 61 st IETF – CAPWAP Working Group6 Automated Processes New WTPs are designed for low cost and installation ease –Redeploying a WTP from one location to another becomes simple and also frequent Each redeployment requires discovery and initialization processes –These processes can become intensive and error- prone in large networks Advantages of automating discovery & initialization –WLAN management is simplified –Operational costs are reduced

7. 61 st IETF – CAPWAP Working Group7 WLAN Status Monitoring Large scale of WLAN deployments means there are multiple points for complication –Numerous WTPs and users –Dynamic nature of wireless medium So network requires constant monitoring in order to react to any complications For effective management, status monitoring needs to be integral to CAPWAP protocol Regular status information also helps with higher level functions like charging and accounting

8. 61 st IETF – CAPWAP Working Group8 QoS VoIP is a major service over WLANs System-wide QoS is crucial for its support This includes QoS over both –Switching segment (AC-WTPs) –Wireless medium segment (WTP-users) Protocol has to coordinate performance over both these segments CAPWAP needs to enable QoS because it affects –User perception –Business performance

9. 61 st IETF – CAPWAP Working Group9 WLAN Status Monitoring Relation to Problems Management Complexity Configuration Consistency Management of Wireless Medium WLAN Security Logical Networks Support Automated Processes Adaptive Interface QoS Problems: Multiple Authentication Mechanisms WLAN Status Monitoring Objectives:

10. 61 st IETF – CAPWAP Working Group10 Next Steps Discuss objectives further

11. 61 st IETF – CAPWAP Working Group11 Questions? Comments?