[OPSAWG] About GRE tunnel type in draft-ietf-opsawg-capwap-alt-tunnel-06

Duzongpeng <duzongpeng@huawei.com> Wed, 03 February 2016 08:25 UTC

Return-Path: <duzongpeng@huawei.com>
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 9EBB81B3393 for <opsawg@ietfa.amsl.com>; Wed, 3 Feb 2016 00:25:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 0OTEZPR-XGN3 for <opsawg@ietfa.amsl.com>; Wed, 3 Feb 2016 00:25:28 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48DFD1B3386 for <opsawg@ietf.org>; Wed, 3 Feb 2016 00:25:27 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CHW83091; Wed, 03 Feb 2016 08:25:23 +0000 (GMT)
Received: from LHREML707-CAH.china.huawei.com (10.201.5.199) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 3 Feb 2016 08:25:22 +0000
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 3 Feb 2016 08:25:22 +0000
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0235.001; Wed, 3 Feb 2016 16:25:10 +0800
From: Duzongpeng <duzongpeng@huawei.com>
To: "sgundave@cisco.com" <sgundave@cisco.com>, "rpazhyan@cisco.com" <rpazhyan@cisco.com>
Thread-Topic: About GRE tunnel type in draft-ietf-opsawg-capwap-alt-tunnel-06
Thread-Index: AdFeXF761QwMjZ2gSMSXMGpp0vtzXA==
Date: Wed, 03 Feb 2016 08:25:09 +0000
Message-ID: <BAFEC9523F57BC48A51C20226A5589575FDE7624@nkgeml514-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.149.226]
Content-Type: multipart/alternative; boundary="_000_BAFEC9523F57BC48A51C20226A5589575FDE7624nkgeml514mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.56B1B974.00ED, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 46ab1008d53e373c50caf25ed4b3ccf0
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/C84u9OxD5SDCTm3j-fC3yFqWiFI>
Cc: "zhen.cao@gmail.com" <zhen.cao@gmail.com>, "276076389@qq.com" <276076389@qq.com>, "caozhen@chinamobile.com" <caozhen@chinamobile.com>, "denghui@chinamobile.com" <denghui@chinamobile.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: [OPSAWG] About GRE tunnel type in draft-ietf-opsawg-capwap-alt-tunnel-06
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, 03 Feb 2016 08:25:33 -0000

Hi, Sri

         I have some commons about the GRE tunnel type in this alt-tunnel draft.

         In the current draft, several kinds of tunnel types are listed:


        Tunnel-Type           Type Value   Reference

        CAPWAP                0            [RFC5415<https://tools.ietf.org/html/rfc5415>],[RFC5416<https://tools.ietf.org/html/rfc5416>]

        L2TP                  1            [RFC2661<https://tools.ietf.org/html/rfc2661>]

        L2TPv3                2            [RFC3931<https://tools.ietf.org/html/rfc3931>]

        IP-IP                 3            [RFC2003<https://tools.ietf.org/html/rfc2003>]

        PMIPv6                4            [RFC5213<https://tools.ietf.org/html/rfc5213>]

        GRE-IPv4              5            [RFC2784<https://tools.ietf.org/html/rfc2784>]

        GRE-IPv6              6            [RFC2784<https://tools.ietf.org/html/rfc2784>]

         And it is said that

This
      specification provides details for this elements for CAPWAP and
      PMIPv6.

         What I suggest is that this specification should also refer to GRE-IPv4/v6.

         I think not too many modifications are needed. Just add a new session:

3.6<https://tools.ietf.org/html/draft-ietf-opsawg-capwap-alt-tunnel-06#section-3.5>.  GRE based Alternate Tunnel


   GRE can also be used
   for alternate tunnel encapsulation between the WTP and the AR.

   o  Access Router  Information: IP address or Fully
      Qualified Domain Name (FQDN) for the alternate tunnel endpoint.

   o  GRE Key: optional, defined in rfc2890.

   The message element structure for GRE encapsulation is shown in
   Figure 11:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |     Tunnel-Type=5 or  6        |   Info Element Length         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    .             Access Router Information Element                .
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    .             GRE Key Element                            .
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


            Figure 11: Alternate Tunnel Encapsulation - GRE

         Fortunately, we do not need to explain what the GRE key element is because there is already this explanation in the current draft "3.6.6.  GRE Key Element".

         I used to join in the work of this draft. I think we have taken this GRE type into consideration, but I do not know why it is missing now.

         What I means is that GRE type should not be considered in other drafts as L2TP or IP-IP, because GRE is a widely used and important tunnel type in WiFi network.

         So I suggest to add GRE tunnel type into this draft just as the CAPWAP and PMIP tunnel type.



Best wishes
Zongpeng Du