1 / 12

IETF CAPWAP Protocol Objectives

IETF CAPWAP Protocol Objectives. China Mobile,Huawei Technology, Intel Corporation,ZTE,RITT Nov. 8,2004. draft-zhou-capwap-objectives-00.txt. Co-authors: Wenhui Zhou (China Mobile) Zhonghui Yao (Huawei Technologies) Lily Yang (Intel Corp.)

snorma
Download Presentation

IETF CAPWAP Protocol Objectives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF CAPWAP Protocol Objectives China Mobile,Huawei Technology, Intel Corporation,ZTE,RITT Nov. 8,2004

  2. draft-zhou-capwap-objectives-00.txt • Co-authors: • Wenhui Zhou (China Mobile) • Zhonghui Yao (Huawei Technologies) • Lily Yang (Intel Corp.) • Meimei Dang (Research Institute of Telecommunication Technologies) • Dong Wang (ZTE) • http://www.capwap.org/objs/draft-zhou-capwap-objectives-00.txt

  3. Outline • Architectural requirements • User (client) access requirements • Service requirements • Centralized control requirements • Management requirements • Security requirements • QoS requirements

  4. Architectural requirements • Both local MAC and split MAC based products, (i.e., ACs or WTPs) must be able to co-exist and inter-operate in one WLAN access network. • But first we need to define exactly what is a Local (or Split) MAC AC (or WTP). • ACs and WTPs should be able to connect by a variety of interconnect technologies (e.g., Ethernet, bus backplanes, ATM (cell) fabrics, etc.). • CAPWAP-supported WTPs should be able to co-exist with non-CAPWAP WTPs in one WLAN access network.

  5. User (client) access requirements • There shouldn't be any impact on the client (both hardware and software platform) due to the use of CAPWAP protocol. Clients should not be required to be aware of the existence of CAPWAP protocol.

  6. Service requirements • Voice over WLAN. So CAPWAP should support IEEE 802.11e and provide fast-handoff capability to avoid voice interruption. • Restrict direct inter-WTP layer 2 communication. • WLAN network resource sharing: It is required that two or more WLAN service providers can share a hotspot WLAN network. This means that a physical WLAN network can be virtualized into several logical WLAN networks.

  7. Centralized control requirements • AC may perform access control functions based on radio resource and/or network resource. • AC should support handover and load balancing between different WTPS.

  8. Management requirements • It is possible that WTPs can be managed directly or through AC where AC acts as a management agent.

  9. Security requirements • It is required to support WPA and/or IEEE 802.11i for wireless air interface security. • It is required to provide mechanism supporting secure information exchange between AC and WTP

  10. QoS requirements • QoS policy should be supported between WTPs and AC via CAPWAP protocol.

  11. Thank You 谢谢！

  12. Questions？ • Comments？ • Suggestions？

More Related