[ieee-ietf-coord] Fwd: Re: IEEE 802 Coordination on CAPWAP

Benoit Claise <bclaise@cisco.com> Mon, 16 October 2017 13:19 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4E47132D67 for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 16 Oct 2017 06:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 t005HeaWYjY4 for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 16 Oct 2017 06:19:51 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27C61132320 for <ieee-ietf-coord@ietf.org>; Mon, 16 Oct 2017 06:19:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8856; q=dns/txt; s=iport; t=1508159991; x=1509369591; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=xqmvq63docATFYxWCcda0DTuaALwCJegMfhGfdLY9c4=; b=IRJloPUXUitNpvqwRhjb76+Cw9xqFK6rokdgssoklcM9nYWJurzUZAM+ zQisaw6F6uYEfVd8oJaUQdLdAvKcTrO/P58kREivxhlWkcW5XUyxU9DO8 ujib/QZE4PsWV47K7QpskLuibnjk63OdxH5w7gRJ+PDbPtCNl3Q4QVkt9 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CWAAB/seRZ/xbLJq1dGQEBAQEBAQEBAQEBBwEBAQEBhENuJ4N6ih90kDOQcIU/EIIECiOFGAKFFRgBAgEBAQEBAQFrHQuFHQEBBSNLFwQcAwEBASgDAgJGBwIIBg0GAgEBihkQqi2CJyaLCwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgy2DWIFqK4J/gT2DEFiCc4JhBYoPiSOOFodfh0OFSYIUG4Vbg1okhw6OD4dggTkfOIFZNCEIHRVJgmSCaIF5PjaKVQEBAQ
X-IronPort-AV: E=Sophos;i="5.43,387,1503360000"; d="scan'208,217";a="655478413"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Oct 2017 13:19:38 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v9GDJbpi030006 for <ieee-ietf-coord@ietf.org>; Mon, 16 Oct 2017 13:19:38 GMT
References: <1b07b0fc-6b7c-90c1-923f-69738e3d26ab@cisco.com>
To: "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
X-Forwarded-Message-Id: <1b07b0fc-6b7c-90c1-923f-69738e3d26ab@cisco.com>
Message-ID: <810eb756-8b3f-0d7f-9ab2-7d36973c50ce@cisco.com>
Date: Mon, 16 Oct 2017 15:19:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <1b07b0fc-6b7c-90c1-923f-69738e3d26ab@cisco.com>
Content-Type: multipart/alternative; boundary="------------0D22FE7F0A768A88E754C9E3"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/bbAjIsJJ9gX4YPNth6RHs-QsTLk>
Subject: [ieee-ietf-coord] Fwd: Re: IEEE 802 Coordination on CAPWAP
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.22
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, 16 Oct 2017 13:19:54 -0000

Russ,

Here is the latest status:



    -------- Forwarded Message --------
    Subject: 	Re: [OPSAWG] WG LC for draft-ietf-opsawg-capwap-alt-tunnel-10
    Date: 	Tue, 10 Oct 2017 02:59:15 +0000
    From: 	Tianran Zhou <zhoutianran@huawei.com>
    To: 	Tianran Zhou <zhoutianran@huawei.com>, opsawg@ietf.org
    <opsawg@ietf.org>
    CC: 	opsawg-chairs@ietf.org <opsawg-chairs@ietf.org>



    Hi WG,

    This call is concluded without objection on the revision.
    Let's move forward to IESG.

    Thanks,
    Tianran

    > -----Original Message-----
    > From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Tianran Zhou
    > Sent: Wednesday, September 20, 2017 2:05 PM
    > To: opsawg@ietf.org
    > Cc: opsawg-chairs@ietf.org
    > Subject: [OPSAWG] WG LC for draft-ietf-opsawg-capwap-alt-tunnel-10
    > 
    > Dear OPSAWG,
    > 
    > The following draft was sent to IESG, but received some critical comments.
    > 
    > Alternate Tunnel Encapsulation for Data Frames in CAPWAP
    > https://tools.ietf.org/html/draft-ietf-opsawg-capwap-alt-tunnel-10
    > 
    > Now the authors have addressed all the comments, and received confirmation
    > from the Security DIR reviewer.
    > https://datatracker.ietf.org/doc/review-ietf-opsawg-capwap-alt-tunnel-
    > 09-secdir-early-meadows-2017-08-10/
    > 
    > This is a notice to start a two-week OPSAWG WG last call review for the
    > document.
    > Please read the above draft and send any issues, comments, or corrections
    > to this mailing list.
    > Please indicate your support or concerns by Wednesday Oct 4, 2017.
    > 
    > Please note that the authors decided to change the document type to
    > Experimental, as stated below:
    > 1.3.  History of the document
    >    This document was started to accommodate Service Provider's need of a
    >    more flexible deployment mode with alternative tunnels [RFC7494].
    >    Experiments and tests have been done for this alt-tunnel network
    >    infrastructure.  However important, the deployment of relevant
    >    technology is yet to complete.  This experimental document is
    >    intended to serve as a historical reference for any future work as to
    >    the operational and deployment requirements.
    > 
    > Thanks,
    > Tianran, as co-chair
    > 


Regards, Benoit
> Benoit:
>
> In preparation for the coordination call that will take place on October 16th, I have a few questions regarding CAPWAP.
>
> Coordination Item 22: CAPWAP extensions in OPSAWG
>
> - draft-ietf-opsawg-capwap-extension has expired
> - draft-ietf-opsawg-capwap-alt-tunnel is marked dead in the datatracker
>
> Does this mean that this coordination item should be closed?
>
> Russ
>
> .
>