%% You should probably cite rfc7494 instead of this I-D.
@techreport{ietf-opsawg-capwap-hybridmac-02,
    number =    {draft-ietf-opsawg-capwap-hybridmac-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac/02/},
    author =    {Chunju Shao and DENG Hui and Rajesh Pazhyannur and Farooq Bari and Rong Zhang and Satoru Matsushima},
    title =     {{IEEE 802.11 MAC Profile for CAPWAP}},
    pagetotal = 10,
    year =      2014,
    month =     feb,
    day =       14,
    abstract =  {CAPWAP defines two entities Wireless Transmission Point (WTP) and Access Controller (AC). CAPWAP also defines two MAC (Medium Access Control) modes for IEEE 802.11 WTPs: Split and Local MAC . For each MAC mode, CAPWAP describes how the MAC functionality is split between the WTP and AC. However, certain functions have not been clearly defined. For example for the Split MAC mode, the IEEE 802.11 encryption is specified as located in either the AC or the WTP with no clear way for the AC to inform the WTP where it should be. This lack of specification leads to interoperability especially when AC and WTP come from different vendors. To solve the problem, this specification defines a IEEE 802.11 MAC profile where each profile specifies an unambigous division of functionality between the WTP and AC. The IEEE 802.11 MAC profile is used as follows: The WTP informs the AC of the supported profiles during the discovery or join process and the AC configures the WTP with one of the supported profiles while configuring a WLAN.},
}