Subject: [OPSAWG] FW: New Version Notification for draft-xue-opsawg-capwap-separation-capability-00.txt

From: Xueli <[email-masked]>
Date: Wed, 10 Jul 2013 05:55:00 +0000

Hi All

There is a new draft about CAPWAP extension for CAPWAP data channel and control channel separation. 
Your comments and review are appreciated.

Best wishes

Li Xue

>-----Original Message-----
>From: [email-masked] [mailto:[email-masked]]
>Sent: Wednesday, July 10, 2013 11:59 AM
>To: John Kaippallimalil; Duzongpeng; Dapeng Liu; Rong Zhang; Xueli
>Subject: New Version Notification for
>draft-xue-opsawg-capwap-separation-capability-00.txt
>
>
>A new version of I-D, draft-xue-opsawg-capwap-separation-capability-00.txt
>has been successfully submitted by Li Xue and posted to the
>IETF repository.
>
>Filename:	 draft-xue-opsawg-capwap-separation-capability
>Revision:	 00
>Title:		 Capability Announcement and AR Discovery in CAPWAP
>Control and Data Channel Separation
>Creation date:	 2013-07-10
>Group:		 Individual Submission
>Number of pages: 9
>URL:
>http://www.ietf.org/internet-drafts/draft-xue-opsawg-capwap-separation-cap
>ability-00.txt
>Status:
>http://datatracker.ietf.org/doc/draft-xue-opsawg-capwap-separation-capabilit
>y
>Htmlized:
>http://tools.ietf.org/html/draft-xue-opsawg-capwap-separation-capability-00
>
>
>Abstract:
>   In a centralized IEEE 802.11 Wireless Local Area Network (WLAN)
>   architecture, the Access Controller (AC) does not have the
>   intelligence to aggregate all the wireless frames. In addition,
>   increasing amounts of traffic handled by each access point would
>   require even more processing at an AC.  Thus it is normal in an
>   existing operator's network for the WTPs to forward the wireless
>   frames directly to AR to avoid overloading the AC.  In this scenario,
>   CAPWAP Control Channel and CAPWAP Data Channel are separated from
>   each other.  This document provides extensions to CAPWAP for the
>   split scenario where CAPWAP Control and Data Channel are separated.
>
>
>
>
>
>The IETF Secretariat