@techreport{xue-opsawg-capwap-separation-capability-01,
    number =    {draft-xue-opsawg-capwap-separation-capability-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-xue-opsawg-capwap-separation-capability/01/},
    author =    {Li Xue and Zongpeng Du and Dapeng Liu and Rong Zhang and John Kaippallimalil},
    title =     {{Capability Announcement and AR Discovery in CAPWAP Control and Data Channel Separation}},
    pagetotal = 8,
    year =      2013,
    month =     oct,
    day =       21,
    abstract =  {In centralized IEEE 802.11 Wireless Local Area Network (WLAN) architecture, the Access Controller (AC) isn't intelligent enough actually to aggregate all the wireless frames, even the bandwidth requirement in the access point is increasing. Thus it is a general case in the existing operator's network that WTPs forward the wireless frames directly to Access Router (AR) to avoid overload on the AC. In this scenario, CAPWAP Control Channel and CAPWAP Data Channel are separated from each other. This document extends CAPWAP for applicability of CAPWAP Control and Data Channel separation.},
}