[OPSAWG] Last Call: <draft-ietf-opsawg-capwap-alt-tunnel-08.txt> (Alternate Tunnel Encapsulation for Data Frames in CAPWAP) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 16 September 2016 17:48 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A947E12B1AF; Fri, 16 Sep 2016 10:48:29 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.33.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <147404810964.25356.17640869796046521725.idtracker@ietfa.amsl.com>
Date: Fri, 16 Sep 2016 10:48:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/6JKncOpvQlNGoabeqF9hd6cFJk4>
Cc: opsawg-chairs@ietf.org, joelja@gmail.com, draft-ietf-opsawg-capwap-alt-tunnel@ietf.org, opsawg@ietf.org
Subject: [OPSAWG] Last Call: <draft-ietf-opsawg-capwap-alt-tunnel-08.txt> (Alternate Tunnel Encapsulation for Data Frames in CAPWAP) to Proposed Standard
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Sep 2016 17:48:30 -0000

The IESG has received a request from the Operations and Management Area
Working Group WG (opsawg) to consider the following document:
- 'Alternate Tunnel Encapsulation for Data Frames in CAPWAP'
  <draft-ietf-opsawg-capwap-alt-tunnel-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-09-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Control and Provisioning of Wireless Access Points (CAPWAP) defines a
   specification to encapsulate a station's data frames between the
   Wireless Transmission Point (WTP) and Access Controller (AC).
   Specifically, the station's IEEE 802.11 data frames can be either
   locally bridged or tunneled to the AC.  When tunneled, a CAPWAP data
   channel is used for tunneling.  In many deployments encapsulating
   data frames to an entity other than the AC (for example to an Access
   Router (AR)) is desirable.  Furthermore, it may also be desirable to
   use different tunnel encapsulation modes between the WTP and the
   Access Router.  This document defines extension to CAPWAP protocol
   for supporting this capability and refers to it as 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) 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 or join
   process and AC may select one of the supported alternate tunnel
   encapsulation types while configuring the WTP.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/ballot/


No IPR declarations have been submitted directly on this I-D.