Hybrid-MAC Model for CAPWAP

Document Type Expired Internet-Draft (individual)
Last updated 2013-08-21 (latest revision 2013-02-17)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The CAPWAP protocol supports two modes of operation: Split and Local MAC (medium access control), which has been described in [RFC5415].There are many functions in IEEE 802l.11 MAC layer that have not yet been clearly defined whether they belong to either the AP (Access Point) or the AC (Access Controller)in the Split and Local modes. Because different vendors have their own definition of these two models, depending upon the vendor many MAC layer functions continue to be mapped differently to either the AP or AC. If there is no clear definition of split MAC and local MAC, then operators will not only need to perform vendor specific configurations in their network but will continue to experience difficulty in interoperating APs and ACs from different vendors.


Chunju Shao (shaochunju@chinamobile.com)
Hui Deng (denghui@chinamobile.com)
Farooq Bari (farooq.bari@att.com)
Rong Zhang (zhangr@gsta.com)
Satoru Matsushima (satoru.matsushima@g.softbank.co.jp)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)