[ieee-ietf-coord] Issue 22. CAPWAP extensions in OPSAWG
Benoit Claise <bclaise@cisco.com> Mon, 01 February 2016 14:49 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB461A92FB for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 1 Feb 2016 06:49:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Noa2n_mZfxNa for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 1 Feb 2016 06:49:36 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83C5F1A92F3 for <ieee-ietf-coord@ietf.org>; Mon, 1 Feb 2016 06:49:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10725; q=dns/txt; s=iport; t=1454338175; x=1455547775; h=to:cc:from:subject:message-id:date:mime-version; bh=64FNIUr1RII+Sy+F5la+jrpF5ZTeZFOzyyeZtovklwE=; b=K9aCD0uWZL4oSb6iSDfou53iugpinHExVoEp6t3NjCaWiOJLrYoFvdVg GuGpAIGvjplJsuMQEhqxPTiEkFmMi45IrvsZ60QLO0z2VvVCgZHKJDvdb 1OsPeqiWQj+45NOVpxSy9f+Z7idhEfjziuxJftiI6b01mrADoBNy03Mnf 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CsBAAycK9W/xbLJq1ehAxtiFivSoQFJoVpggQBAQEBAQGBAAuERCdIBQgBPBYLAgsDAgECAUsNCAEBiBcOrhGORQEBAQEBAQEDAQEBAQEBARmGD4g5EQGDHoE6BZZvhUeIBIFbSoZ6hVGFbohQYoNtOy4Bh0yBMAEBAQ
X-IronPort-AV: E=Sophos;i="5.22,380,1449532800"; d="scan'208,217";a="623954226"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2016 14:49:33 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u11EnX84005099; Mon, 1 Feb 2016 14:49:33 GMT
To: "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <56AF707C.7040705@cisco.com>
Date: Mon, 01 Feb 2016 15:49:32 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------030705000702060705010008"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/6CaLCuHYNC7QB8LBJdQGg7052Fw>
Cc: "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: [ieee-ietf-coord] Issue 22. CAPWAP extensions in OPSAWG
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2016 14:49:38 -0000
Dear all, Here is an update on this topic: 22. CAPWAP extensions in OPSAWG 22.1. Description: - Extensions to the CAPWAP protocol are being defined in the IETF OPSAWG. The OPSAWG will send the documents that relate to IEEE 802.11 technology to the IEEE 802.11 WG for expert review. - Status 1/27/14 (Benoit Claise) - there are two relevant drafts in Working Group Last Call. He sent out via email an updated description of this item, to be added to the next iteration of the shared work items list. Dan Romascanu will edit the shared work items list accordingly. - Status 9/23/14 (Dorothy Stanley): Liaison requests have been made from the opsawg to IEEE 802.11 for review and comment on each of these documents. The IEEE 802.11 responded with the liaisons below. There are no open liaison requests from opsawg to IEEE 802.11 at this time. - Status 1/20/15 (Dan): 2 out of 3 documents were approved by the IESG and are now in RFC Editor Queue - Status 6/15/15 (Dan): one WG document pending (in AD is watching state) http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/; one individual submission http://datatracker.ietf.org/doc/draft-you- opsawg-capwap-separation-for-mp/. - Status 6/18/15 (Benoit): RFC 7494, IEEE 802.11 Medium Access Control (MAC) Profile for Control and Provisioning of Wireless Access Points (CAPWAP), has been published. A second document on the OPSAWG CAPWAP tunnel is nearly ready for Working Group Last Call; he will let 802.11 know when that is done. - Status 9/29/15 (Benoit): draft-ietf-opsawg-capwap-alt-tunnel (Alternate Tunnel Encapsulation for Data Frames in CAPWAP) will merge with draft-you-opsawg-capwap-separation-for-mp (CAPWAP Control and Data Channel Separation for Multi-provider Scenario) 22.2. Relevant Documents - http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-extension/ - http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac - RFC 7494 - http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/ - approved - https://datatracker.ietf.org/liaison/1312/ - https://mentor.ieee.org/802.11/dcn/14/11-14-0913-01-0000-liaison- response-opsawg-capwap-extension.docx - https://mentor.ieee.org/802.11/dcn/14/11-14-0684-01-0000-capwap- hybridmac-liaison-response.docx - Tunnel encapsulation response: slide 5 in https://mentor.ieee.org/ 802.11/dcn/14/11-14-0500-00-0000-may-2014-liaison-to-ietf-report.pptx - http://datatracker.ietf.org/doc/draft-you-opsawg-capwap-separation- for-mp/ - http://www.rfc-editor.org/rfc/rfc7494.txt 22.3. Owners: Benoit Claise and Dorothy Stanley 22.4. Action Items - Benoit to fill in the DESCRIPTION DONE - Benoit to ensure that OPSAWG chairs send documents at Last Call to IEEE 802.11 - Dorothy Stanley to channel requests for reviews and responses between the OPSAWG and IEEE 802.11 Here is the update, received from the OPSAWG chairs: The last update you gave them was: Status 9/29/15 (Benoit): draft-ietf-opsawg-capwap-alt-tunnel (Alternate Tunnel Encapsulation for Data Frames in CAPWAP) will merge with draft-you-opsawg-capwap-separation-for-mp (CAPWAP Control and Data Channel Separation for Multi-provider Scenario) The document was returned to the WG, and they authors posted a new version with much of the Multi-provider stuff in (https://www.ietf.org/rfcdiff?url1=draft-ietf-opsawg-capwap-alt-tunnel-05&url2=draft-ietf-opsawg-capwap-alt-tunnel-06) <https://www.ietf.org/rfcdiff?url1=draft-ietf-opsawg-capwap-alt-tunnel-05&url2=draft-ietf-opsawg-capwap-alt-tunnel-06%29_> - October 19, 2015 Since that though, there has been no real discussion or progress.... Regards, Benoit
- [ieee-ietf-coord] Issue 22. CAPWAP extensions in … Benoit Claise