Re: [Softwires] [Int-area] Is it feasible to perform fragmentation on UDP encapsulated packets.

Xuxiaohu <xuxiaohu@huawei.com> Sat, 28 May 2016 02:59 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA9312B04A; Fri, 27 May 2016 19:59:15 -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 k4TC1rgpChF3; Fri, 27 May 2016 19:59:13 -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 D364212B044; Fri, 27 May 2016 19:59:11 -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 CKY31314; Sat, 28 May 2016 02:59:09 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Sat, 28 May 2016 03:59:08 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.169]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Sat, 28 May 2016 10:59:00 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Tom Herbert <tom@herbertland.com>
Thread-Topic: [Int-area] Is it feasible to perform fragmentation on UDP encapsulated packets.
Thread-Index: AQHRt/+2WtIZvGZrakmsedKxg0Mnz5/MXIgAgAE1HJA=
Date: Sat, 28 May 2016 02:59:00 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D559AC0@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> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <CALx6S37-oA22ZKjF5MxsTPaR9nRS-b1JuVidWmPYjNkqQtWNBg@mail.gmail.com>
In-Reply-To: <CALx6S37-oA22ZKjF5MxsTPaR9nRS-b1JuVidWmPYjNkqQtWNBg@mail.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.0A020206.5749097E.0022, 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: 39ca7292808ea04c84e6b5f49013feea
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/zVAympIj9177Y97sW4vo7FrVjBM>
Cc: Softwires WG <softwires@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [Int-area] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 May 2016 02:59:15 -0000

Hi Tom,

> -----Original Message-----
> From: Tom Herbert [mailto:tom@herbertland.com]
> Sent: Friday, May 27, 2016 11:06 PM
> To: Xuxiaohu
> Cc: int-area@ietf.org; Softwires WG; nvo3@ietf.org; lisp@ietf.org;
> tsvwg@ietf.org
> Subject: Re: [Int-area] Is it feasible to perform fragmentation on UDP
> encapsulated packets.
> 
> > The possible side-effect of performing fragmentation on UDP encapsulated
> packets is to worsen the reassembly burden on tunnel egress since fragments of
> UDP encapsulated packets are more likely to be forwarded across different
> paths towards the tunnel egress than those of IP or GRE encapsulated packets.
> >
> 
> Xiaohu,
> 
> I don't understand why UDP encapsulation would make things worse than other
> encapsulations. Fragmentation would be needed at tunnel ingress when packet

When performing fragmentation after UDP encapsulation (a.k.a., outer fragmentation), the first fragment (still a UDP packet) and the subsequent fragments (not a UDP packet anymore) of a given UDP encapsulated packet are more likely to be routed over different paths in contrast to IP or GRE encapsulated packets. As a result, the reordering issue on the tunnel egress which is required to do reassembly would become even worse.

> size exceeds MTU of the tunnel. RFC4459 describes the issues and general
> solutions that apply to the different techniques of IP tunneling.

Partially agree. The use of UDP as a tunneling protocol was not popular at the time when RFC4459 was published. Otherwise, the worse recording issue associated with the outer fragmentation of UDP encapsulated packets may need more attention in that RFC.

By the way, RFC4459 has illustrated the risk of performing [outer] fragmentation on tunneled packets clearly and said clearly that "...   So, if reassembly could be made to work sufficiently reliably, this would be one acceptable fallback solution but only for IPv6." However, I just occasionally noticed that in section 3.3.2.1 (Tunneling GRE over IPv4) of RFC7588, it said "By default, the GRE ingress node does not fragment delivery packets. However, the GRE ingress node includes a configuration option that allows delivery packet fragmentation." Does it mean there is a conflict between those two RFCs regarding whether outer fragmentation is needed for GRE over IPv4?

> > It seems that most X-over-UDP proposals choose to prohibit the tunnel ingress
> from performing fragmentation on UDP encapsulated packets. See the following
> quoted text regarding fragmentation from those X-over-UDP drafts:
> >
> Please look a draft-herbert-gue-fragmentation-02. This is a method where the
> fragmentation/reassembly is performed in the encapsulation layer instead of
> (outer or inner) IP layer.

It's an interesting idea. However, since it needs a dedicated fragmentation field in the GUE header, it seems that this approach is not suitable for the compressed GUE packet (a.k.a., in the same format of IP-in-UDP) where the fragmentation field and even the whole GUE header is gone.

Best regards,
Xiaohu

> Tom