Alternate Tunnel Encapsulation for Data Frames in CAPWAP
draft-zhang-opsawg-capwap-cds-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-10-21
Replaced by draft-ietf-opsawg-capwap-alt-tunnel
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           R. Zhang
Internet-Draft                                             China Telecom
Intended status: Standards Track                                  Z. Cao
Expires: April 25, 2014                                          H. Deng
                                                            China Mobile
                                                           R. Pazhyannur
                                                           S. Gundavelli
                                                                   Cisco
                                                        October 22, 2013

        Alternate Tunnel Encapsulation for Data Frames in CAPWAP
                    draft-zhang-opsawg-capwap-cds-01

Abstract

   CAPWAP ([RFC5416]) defines two tunneling modes for encapsulating data
   frames from stations associated with WLAN: 802.3 Tunnel and 802.11
   Tunnel modes.  This document provides for an alternate tunnel
   encapsulation.  The alternate tunnel encapsulation allows 1) the WTP
   to tunnel non-management data frames to an endpoint different from
   the AC and 2) allows the WTP to tunnel using one of many known
   encapsulation types such as IP-IP, IP-GRE, CAPWAP.  The WTP may
   advertise support for Alternate Tunnel encapsulation during the
   discovery process and AC may select one of the supported Alternate
   Tunnel encapsulate types during the WTP configuration.  Further, the
   AC may configure WTP to enable the alternate tunnel encapsulation.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 25, 2014.

Copyright Notice

Zhang, et al.            Expires April 25, 2014                 [Page 1]
Internet-Draft              Alternate Tunnel                October 2013

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions used in this document . . . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Alternate Tunnel Encapsulation  . . . . . . . . . . . . . . .   5
     2.1.  Supported Alternate Tunnel Encpsulation . . . . . . . . .   5
     2.2.   Alternate Tunnel Encapsulation . . . . . . . . . . . . .   5
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   CAPWAP ([RFC5415], [RFC5416]) defines a tunnel mode that specifies
   the frame tunneling type to be used for 802.11 data frames from all
   stations associated with the WLAN.  The following types are
   supported:

   o  Local Bridging: All user traffic is to be locally bridged.
   o  802.3 Tunnel: All user traffic is to be tunneled to the AC in
      802.3 format.
   o  802.11 Tunnel: All user traffic is to be tunneled to the AC in
      802.11 format.

   There are two shortcomings with currently specified tunneled modes:
   1) it does not allow the WTP to tunnel data frames to an endpoint
   different from the AC and 2) it does not allow the WTP to tunnel data
   frames using any encapsulation other than CAPWAP (as specified in
   Section 4.4.2 of [RFC5415]).  Next, we describe what is driving the
   above mentioned two requirements.

Zhang, et al.            Expires April 25, 2014                 [Page 2]
Show full document text