[OPSAWG] Seeking discussion on "Alternate Tunnel Encapsulation for Data Frames in CAPWAP"
"Rajesh Pazhyannur (rpazhyan)" <rpazhyan@cisco.com> Sun, 27 October 2013 00:08 UTC
Return-Path: <rpazhyan@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A00D11E81CA for <opsawg@ietfa.amsl.com>; Sat, 26 Oct 2013 17:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yesLXYW1+jxt for <opsawg@ietfa.amsl.com>; Sat, 26 Oct 2013 17:07:54 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id AE2F821F9E39 for <opsawg@ietf.org>; Sat, 26 Oct 2013 17:07:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4130; q=dns/txt; s=iport; t=1382832474; x=1384042074; h=from:to:subject:date:message-id:mime-version; bh=+I332YxD6TQCB8wHPayNr7ZKRaO6bgnUhgYjDqvXNzo=; b=RYF/p25DUNf0EEZt6IZQFdVCVQ2/4/r5lyjrtvPQq2sh3ovl8ltKhk9w 2VYmiuo+WUX4q+XlqoZIThPFPsDeDSs4dmdtgb9MBQ1xnavu+RFfweHen Eq3Du6D4hympD3aPcuMUjN1EMA2jip3JVJieX6+mZMWhetjHac8qFlbkw I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkwHAK9YbFKtJV2b/2dsb2JhbABZgkNEOFSsI4lmiEeBHxZtB4InAQQtXgEMHlYmAQQbE4dsDZYUoRiPJINXgQ0DmTmQWIFogT6CKg
X-IronPort-AV: E=Sophos; i="4.93,578,1378857600"; d="scan'208,217"; a="277111227"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP; 27 Oct 2013 00:07:40 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9R07eGX005526 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <opsawg@ietf.org>; Sun, 27 Oct 2013 00:07:40 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.202]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Sat, 26 Oct 2013 19:07:39 -0500
From: "Rajesh Pazhyannur (rpazhyan)" <rpazhyan@cisco.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: Seeking discussion on "Alternate Tunnel Encapsulation for Data Frames in CAPWAP"
Thread-Index: Ac7SqIs8II5D0brnRoyCTVQ6wZ7WWA==
Date: Sun, 27 Oct 2013 00:07:38 +0000
Message-ID: <4ED2E36A22261145861BAB2C24088B4320ED015B@xmb-aln-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.146.163]
Content-Type: multipart/alternative; boundary="_000_4ED2E36A22261145861BAB2C24088B4320ED015Bxmbalnx09ciscoc_"
MIME-Version: 1.0
Subject: [OPSAWG] Seeking discussion on "Alternate Tunnel Encapsulation for Data Frames in CAPWAP"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Sun, 27 Oct 2013 00:08:07 -0000
Hello We have resubmitted a new version of the draft titled "Alternate Tunnel Encapsulation for Data Frames in CAPWAP", http://datatracker.ietf.org/doc/draft-zhang-opsawg-capwap-cds/. The previous version was titled: "Separation of CAPWAP Control and Data Plane: Scenarios, Requirements and Solutions". Based on discussion in the last IETF, we reworked the draft. The draft provides a reason for the need for WTP to have additional tunnel (beyond CAPWAP) encapsulations for user traffic. It enables a WTP to advertise the capability to support such alternate tunnel encapsulation and the AC to configure such tunnel encapsulation on the WTP. 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 ecapsulation types such as IP-IP, IP-GRE, CAPWAP. We would like to get it adopted as a working group item and would like feedback on whether we are on track. Regards Rajesh
- [OPSAWG] Seeking discussion on "Alternate Tunnel … Rajesh Pazhyannur (rpazhyan)
- Re: [OPSAWG] Seeking discussion on "Alternate Tun… Romascanu, Dan (Dan)
- Re: [OPSAWG] Seeking discussion on "Alternate Tun… Rajesh Pazhyannur (rpazhyan)
- Re: [OPSAWG] Seeking discussion on "Alternate Tun… John Kaippallimalil
- Re: [OPSAWG] Seeking discussion on "Alternate Tun… Rajesh Pazhyannur (rpazhyan)