Re: [OPSAWG] Review of "Alternate Tunnel Encapsulation for Data Frames in CAPWAP" - draft-ietf-opsawg-capwap-alt-tunnel

Andreas Schultz <aschultz@tpip.net> Wed, 17 February 2016 11:05 UTC

Return-Path: <aschultz@tpip.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 848401B38BE for <opsawg@ietfa.amsl.com>; Wed, 17 Feb 2016 03:05:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] 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 jfetoPBKm7Nk for <opsawg@ietfa.amsl.com>; Wed, 17 Feb 2016 03:05:34 -0800 (PST)
Received: from mail.tpip.net (mail.tpip.net [92.43.49.48]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACA3B1B38C1 for <opsawg@ietf.org>; Wed, 17 Feb 2016 03:05:33 -0800 (PST)
Received: from office.tpip.net (office.tpip.net [92.43.51.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tpip.net (Postfix) with ESMTPS id 7B3634F404; Wed, 17 Feb 2016 11:05:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by office.tpip.net (Postfix) with ESMTP id 216A3A3066; Wed, 17 Feb 2016 12:06:25 +0100 (CET)
Received: from office.tpip.net ([127.0.0.1]) by localhost (office.tpip.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id alfi8sljfC56; Wed, 17 Feb 2016 12:06:24 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by office.tpip.net (Postfix) with ESMTP id 992CDA306D; Wed, 17 Feb 2016 12:06:24 +0100 (CET)
X-Virus-Scanned: amavisd-new at tpip.net
Received: from office.tpip.net ([127.0.0.1]) by localhost (office.tpip.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id aFcmriLMH5-e; Wed, 17 Feb 2016 12:06:24 +0100 (CET)
Received: from [192.168.13.53] (unknown [192.168.13.53]) by office.tpip.net (Postfix) with ESMTPSA id 3AEBBA3066; Wed, 17 Feb 2016 12:06:24 +0100 (CET)
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Warren Kumari <warren@kumari.net>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <CAHw9_iK57UBZcwfoQNzHGjiCrgWaBH9tUBeHGkss5TjBwF6ZHA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA6BF1B1D5@AZ-FFEXMB04.global.avaya.com>
From: Andreas Schultz <aschultz@tpip.net>
Message-ID: <56C453F9.8080406@tpip.net>
Date: Wed, 17 Feb 2016 12:05:29 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA6BF1B1D5@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/OzvzbHg4lNVa9Uwv-A1lS3vjxcI>
Cc: Dorothy Stanley <DStanley@arubanetworks.com>
Subject: Re: [OPSAWG] Review of "Alternate Tunnel Encapsulation for Data Frames in CAPWAP" - draft-ietf-opsawg-capwap-alt-tunnel
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
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: <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: Wed, 17 Feb 2016 11:05:36 -0000

Hi,

On 02/17/2016 11:36 AM, Romascanu, Dan (Dan) wrote:
> Hi,
>
> I have reviewed the previous versions of this document. I do not find significant changes in the content since. I believe that it’s ready
> for publication.

The comments in https://www.ietf.org/mail-archive/web/opsawg/current/msg04161.html have not yet been addressed.
Having written those comment, I obviously feel that there should be some changes made before publication.

Regards
Andreas


> AFAIK the document was also reviewed by IEEE 802.11. I am copying the Dorothy Stanley who is the liaison manager, as I do not know if she is
> subscribed to the WG mail list.
>
> Regards,
>
> Dan
>
> *From:*OPSAWG [mailto:opsawg-bounces@ietf.org] *On Behalf Of *Warren Kumari
> *Sent:* Wednesday, February 17, 2016 12:31 AM
> *To:* opsawg@ietf.org
> *Subject:* [OPSAWG] Review of "Alternate Tunnel Encapsulation for Data Frames in CAPWAP" - draft-ietf-opsawg-capwap-alt-tunnel
>
> Dear OpsAWG,
>
> While we have lots of energy / interest, we'd appreciate some additional review of draft-ietf-opsawg-capwap-alt-tunnel
> (https://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dopsawg-2Dcapwap-2Dalt-2Dtunnel_&d=BQMFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=YSTTTzZjDjD_fxRDbZTWgW6tBrwOadoMW7MP4RRFFdQ&s=ZuwP2TZyReJXmH8tHtt8Bg0SDGvmX2_un8TtmJU5sQI&e=> ).
>
> This document has an interesting history - it completed WGLC in 2014-08-27 and was submitted to be published as an RFC on 2014-09-08.
>
> We then got draft-you-opsawg-capwap-separation-for-mp, which had some some significant similarities. We asked the ADs to hold alt-tunnel
> while we discussed what to do, and then finally asked the ADs / IESG to return it to the WG so that these two documents could be merged into
> one ( https://www.ietf.org/mail-archive/web/opsawg/current/msg04071.html
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mail-2Darchive_web_opsawg_current_msg04071.html&d=BQMFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=YSTTTzZjDjD_fxRDbZTWgW6tBrwOadoMW7MP4RRFFdQ&s=59ocMkJDZW_0tPUy9QccyjIc81Yjqe5RhjgrCX0aG8M&e=> ).
>
> This document has already passed one WGLC (module the minor merging), and we are waiting on the authors to address some comments (e.g:
> https://www.ietf.org/mail-archive/web/opsawg/current/msg04161.html
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mail-2Darchive_web_opsawg_current_msg04161.html&d=BQMFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=YSTTTzZjDjD_fxRDbZTWgW6tBrwOadoMW7MP4RRFFdQ&s=Y24UHv4v54xg7rgWKHivf8xbeORWBYd3sjg6SJg1t2w&e=> )
> and update the email addresses - once that happens we will do another WGLC -- but, while we are waiting, we'd appreciate any other review
> and feedback.
>
> W
>
>
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>