%% You should probably cite rfc7494 instead of this I-D.
@techreport{ietf-opsawg-capwap-hybridmac-01,
    number =    {draft-ietf-opsawg-capwap-hybridmac-01},
    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/01/},
    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 = 11,
    year =      2013,
    month =     oct,
    day =       12,
    abstract =  {The CAPWAP protocol defines two modes of operation for IEEE 802.11 WTPs: Split and Local MAC (medium access control), as described in {[}RFC5415{]},{[}RFC5416{]}. Specifically, {[}RFC5416{]} describes in detail the division of labor between WTP and AC in the Split and Local MAC modes. Unfortunately, there are many functions that have not yet been clearly defined whether they belong to the WTP or the AC. For example IEEE 802.11 encryption is specified as located in either in the AC or the WTP with no clear way to negotiate where it should be located. This lack of specification leads to interoperability between AC and WTP when AC and WTP come from different vendors. To solve this problem, this specification defines the concept of IEEE 802.11 MAC profile where each profile refers to a table containing an unambigous division of labor between WTP and AC. The profile is used as follows: the WTP informs the AC of the supported profiles and the AC selects the profile when it configures the WTP.},
}