CAPWAP Control and Data Channel Separation for Multi-provider Scenario
draft-you-opsawg-capwap-separation-for-mp-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jianjie You , Haibin Song , Rong Zhang | ||
| Last updated | 2015-11-26 (Latest revision 2015-05-25) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The CAPWAP control channel and data channel split architecture has some benefits, such as relieving the capacity pressure of the AC. However, the current documents are not specific to the multi-provider scenario. This document discusses the third-party WLAN service provider scenario (i.e. Virtual Network Operator, VNO), and proposes to extend CAPWAP for supporting this use case.
Authors
Jianjie You
Haibin Song
Rong Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)