IETF Logo Mail Archive

Re: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-03

Xuxiaohu <xuxiaohu@huawei.com> Thu, 26 May 2016 09:04 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B47412D0D9 for <int-area@ietfa.amsl.com>; Thu, 26 May 2016 02:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level:
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 g9XiC6wV5PcF for <int-area@ietfa.amsl.com>; Thu, 26 May 2016 02:04:29 -0700 (PDT)
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 2B9C112D0B9 for <int-area@ietf.org>; Thu, 26 May 2016 01:55:56 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CKU70796; Thu, 26 May 2016 08:55:53 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 26 May 2016 09:55:52 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.169]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Thu, 26 May 2016 16:55:47 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Joe Touch <touch@isi.edu>, Tom Herbert <tom@herbertland.com>
Thread-Topic: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-03
Thread-Index: AQHRsfdFpg5szZjRuk2CxGidq0DM15/AOacAgAFcxnD///TOAIAESJ5AgABjDQCAARz3UP//sRcAgAC6YtCAABY6AIABDenQ//+QjgAAEiqZkP//ha2A//95U1CAAXRNgP/+hdoA
Date: Thu, 26 May 2016 08:55:46 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555EDD@NKGEML515-MBS.china.huawei.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557C2@NKGEML515-MBS.china.huawei.com> <CALx6S36_VH550y4qf_k+YFOUPG85Wq-ihc_zVfSgBHvV8kfp5Q@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55584B@NKGEML515-MBS.china.huawei.com> <CALx6S34WwLD0z=-xgt1bNyEcMmYWJDHO=3J5G7g4YzRECEo9zA@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555887@NKGEML515-MBS.china.huawei.com> <2344c73f-ead6-95ca-6e3b-0c66016810fa@isi.edu>
In-Reply-To: <2344c73f-ead6-95ca-6e3b-0c66016810fa@isi.edu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.5746BA1A.0094, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.5.169, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 1e2f889b308b13b6add75c4aa06f40a6
Archived-At: <http://mailarchive.ietf.org/arch/msg/int-area/CL3xCKpDFlhFKNgxJV16m3j04D8>
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-03
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 09:04:31 -0000


> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Thursday, May 26, 2016 2:15 AM
> To: Xuxiaohu; Tom Herbert
> Cc: Fred Baker (fred); Wassim Haddad; int-area@ietf.org
> Subject: Re: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-03
> 
> 
> 
> On 5/24/2016 9:08 PM, Xuxiaohu wrote:
> >> The existing protocols that provide the same functionality are GUE and
> GRE/UDP.
> >> > GUE allows encapsulation of any IP protocol over UDP, GRE will
> >> > allow encapsulation of any Ethertype of UDP. Both of these provide
> >> > a means to encapsulate of IPv4 and IPv6 in UDP.
> >
> > Which is more generic? If both are generic, why we need two?
> 
> GRE and GUE represent steps in a direction, as does SEAL. That direction is to
> support increased checksums, fragmentation support, control channels, etc.

GRE or GRE/UDP?

> This document represents a step backwards, is useful only in more limited
> environments, etc.

Thanks for confirming that this encapsulation is useful in limited environment (i.e., Softwires networks). As said before, both fruit knives and Swiss Army knives are sold in the market. In other words, both generic and simple approaches have their own applicable scenarios.

Xiaohu

> Again, not a good reason for the WG to adopt it.
> 
> Joe

v2.23.0 | Report a Bug | By Email