IETF Logo Mail Archive

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

Xuxiaohu <xuxiaohu@huawei.com> Tue, 31 May 2016 07:51 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 CCB6F12D153 for <int-area@ietfa.amsl.com>; Tue, 31 May 2016 00:51:37 -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=ham 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 fxsk26WWloTh for <int-area@ietfa.amsl.com>; Tue, 31 May 2016 00:51:35 -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 9D4AC12D0CE for <int-area@ietf.org>; Tue, 31 May 2016 00:51:34 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml705-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CLC56177; Tue, 31 May 2016 07:51:32 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml705-cah.china.huawei.com (10.201.5.168) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 31 May 2016 08:51:32 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.169]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Tue, 31 May 2016 15:51:27 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-03
Thread-Index: AQHRsfdFpg5szZjRuk2CxGidq0DM15/AOacAgAFcxnD///TOAIAESJ5AgABjDQCAARz3UP//sRcAgAkTTgCAATtUAIAAKtGAgAE+fHA=
Date: Tue, 31 May 2016 07:51:27 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55A00C@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> <e523724c-cffd-784d-0147-aa64c2787727@bogus.com> <574C8288.7080804@isi.edu> <bd97158e-b6f1-5e55-af9a-07eca2660479@gmail.com>
In-Reply-To: <bd97158e-b6f1-5e55-af9a-07eca2660479@gmail.com>
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.574D4285.006B, 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/sS7_m5tmEMIYPcsYqTqiQ2q6PNg>
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: Tue, 31 May 2016 07:51:38 -0000


> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> Sent: Tuesday, May 31, 2016 4:46 AM
> To: Joe Touch
> Cc: joel jaeggli; Xuxiaohu; Fred Baker (fred); Wassim Haddad; int-area@ietf.org
> Subject: Re: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-03
> 
> And being pedantic...
> On 31/05/2016 06:12, Joe Touch wrote:
> >
> >
> > On 5/29/2016 4:23 PM, joel jaeggli wrote:
> >>>> I.e., you MUST support source fragmentation at the ingress at the
> >>>> outer
> >>>> IPv6 layer (because UDP doesn't have support for fragmentation and
> >>>> reassembly). If you make this requirement, you can handle IPv6 over
> >>>> the tunnel.
> >> Yeah I don't support it for this reason. getting IP fragments back
> >> together in the same place a reassembled is hard is in some cases
> >> especially when you hash. (see frag drop) given alternatives that
> >> better address such situations it seems hard to justify.
> >
> > If you intend to support recursive IP tunneling* and believe that IP
> > has a minimum MTU, then you have to accept reassembly.
> 
> If you intend to support recursive datagram tunneling and believe that any path
> has a minimum MTU, then you have to accept reassembly.

Let's take the Softwires network as an concrete example. What's the motivation for SPs to deploy recursive IP tunneling?

Xiaohu

> This is physics, and nothing to do with design details.
> 
> (Something I discovered in about 1983, when implementing OSI/CLNP at CERN
> over a homebrew network with 128 byte packets.)
> 
>    Brian
> 
> >
> > Joe
> >
> > * where "recursive IP tunneling" is IP in [zero or more other
> > protocols] in IP.
> >
> > _______________________________________________
> > Int-area mailing list
> > Int-area@ietf.org
> > https://www.ietf.org/mailman/listinfo/int-area
> >

v2.23.0 | Report a Bug | By Email