[6lo-fragmentation-dt] performance report for fragment forwarding

Rahul Arvind Jadhav <rahul.jadhav@huawei.com> Tue, 18 September 2018 09:00 UTC

Return-Path: <rahul.jadhav@huawei.com>
X-Original-To: 6lo-fragmentation-dt@ietfa.amsl.com
Delivered-To: 6lo-fragmentation-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 842E912F18C for <6lo-fragmentation-dt@ietfa.amsl.com>; Tue, 18 Sep 2018 02:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 mXsvPhTQ13BB for <6lo-fragmentation-dt@ietfa.amsl.com>; Tue, 18 Sep 2018 02:00:10 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4DDB127133 for <6lo-fragmentation-dt@ietf.org>; Tue, 18 Sep 2018 02:00:10 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 0C12379AFCBFC for <6lo-fragmentation-dt@ietf.org>; Tue, 18 Sep 2018 10:00:07 +0100 (IST)
Received: from BLREML408-HUB.china.huawei.com (10.20.4.47) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.399.0; Tue, 18 Sep 2018 10:00:07 +0100
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.224]) by BLREML408-HUB.china.huawei.com ([10.20.4.47]) with mapi id 14.03.0399.000; Tue, 18 Sep 2018 14:29:58 +0530
From: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
To: "6lo-fragmentation-dt@ietf.org" <6lo-fragmentation-dt@ietf.org>
CC: Yasuyuki Tanaka <yasuyuki.tanaka@inria.fr>, Rabi Narayan Sahoo <rabinarayans@huawei.com>
Thread-Topic: performance report for fragment forwarding
Thread-Index: AdRPIZfBL8K0t6K4TKOG0Pl/K7kTNQ==
Date: Tue, 18 Sep 2018 08:59:57 +0000
Message-ID: <982B626E107E334DBE601D979F31785C5DCB9A8E@BLREML503-MBX.china.huawei.com>
Accept-Language: en-IN, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.157.44]
Content-Type: multipart/alternative; boundary="_000_982B626E107E334DBE601D979F31785C5DCB9A8EBLREML503MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo-fragmentation-dt/RB-_nNimMtDsJOw1vli-1hJJu6w>
X-Mailman-Approved-At: Wed, 19 Sep 2018 14:09:09 -0700
Subject: [6lo-fragmentation-dt] performance report for fragment forwarding
X-BeenThere: 6lo-fragmentation-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: 6lo Fragmentation Design Team <6lo-fragmentation-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo-fragmentation-dt>, <mailto:6lo-fragmentation-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo-fragmentation-dt/>
List-Post: <mailto:6lo-fragmentation-dt@ietf.org>
List-Help: <mailto:6lo-fragmentation-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo-fragmentation-dt>, <mailto:6lo-fragmentation-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Sep 2018 09:00:19 -0000

Hello All,

We experimented with Fragment forwarding and tried to understand the performance implications vis-à-vis per-hop reassembly.

Following is the detailed report:
https://github.com/nyrahul/ietf-data/blob/master/6lo-fragfwd-perf-report.md

To summarize, we found that fragment forwarding has some practical issues when it comes to forwarding efficiency or PDR and latency "on single channel 802.15.4". While similar concerns were been raised previously during IETF meetings, we tried to validate it with data.

Please let us know if you have any comments.

Regards,
Rahul

This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!