Re: [Lwip] [E] [6lo] fragment forwarding implementation and performance report

"Chakrabarti, Samita" <samita.chakrabarti@verizon.com> Mon, 08 October 2018 20:54 UTC

Return-Path: <samita.chakrabarti@verizon.com>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EAF8131007 for <lwip@ietfa.amsl.com>; Mon, 8 Oct 2018 13:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.27
X-Spam-Level:
X-Spam-Status: No, score=0.27 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizon.com header.b=ka93hv7E; dkim=pass (2048-bit key) header.d=verizon-com.20150623.gappssmtp.com header.b=FjfMd0jq
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 l3n9XN0H8tc1 for <lwip@ietfa.amsl.com>; Mon, 8 Oct 2018 13:54:05 -0700 (PDT)
Received: from mx0b-0024a201.pphosted.com (mx0b-0024a201.pphosted.com [148.163.153.92]) (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 20107130E96 for <lwip@ietf.org>; Mon, 8 Oct 2018 13:54:05 -0700 (PDT)
Received: from pps.filterd (m0115886.ppops.net [127.0.0.1]) by mx0b-0024a201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w98Kne3I186525 for <lwip@ietf.org>; Mon, 8 Oct 2018 16:54:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon.com; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : cc : content-type; s=corp; bh=Qgv1hN1W2WhfF8dW+bBxZTqkHMLxAHyfdAcgWp46FwY=; b=ka93hv7Ej/o8NzzoiBz71CV/c8Evd+NzMX3FZZpujCBa34u7u/wZz8QwqsldXZ66lR1D dsac5NNbNj/6z9yG/AX08QEu2X4g+XPOF7k1zIikVOux9YtaI00D9hqRept9TG+EclxB XnfmDBitQgOcm7jG1OCxK2QtcFfUHrEwVAI=
Received: from mail-oi1-f198.google.com (mail-oi1-f198.google.com [209.85.167.198]) by mx0b-0024a201.pphosted.com with ESMTP id 2n0c7tsr16-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <lwip@ietf.org>; Mon, 08 Oct 2018 16:54:03 -0400
Received: by mail-oi1-f198.google.com with SMTP id s128-v6so15488691ois.18 for <lwip@ietf.org>; Mon, 08 Oct 2018 13:54:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Qgv1hN1W2WhfF8dW+bBxZTqkHMLxAHyfdAcgWp46FwY=; b=FjfMd0jqNr3w4TKdnGtLAfZFHceXixBgf5pZsPcKRIP006vpYScj4GeywRuWfMMe45 KbmohdhXSr+23CR5L9ukONMkhEhKM3kMVhZkMwpXOYjwkUvNkLZuJqJW1iyWunmdxsqf AZajPn4FMi3eCQqQu/0zHL3GumDqP3vi0/7gR0BsUTMeQ9I0tV//iGntJXlW5JcTKQIc TaYPb4roT5JLPI9lP90IIO67VyN/ABeSM6BpEzYdopyTJzLyQZobYnJX/9mGNvDmAqCJ OQDxHiOwcXx9uNCIopN1Tb3AuQ0S7YKnYiG6NPbFu3rrM4O/JnZNZ1fzAUIaCmWM7ruX VTZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Qgv1hN1W2WhfF8dW+bBxZTqkHMLxAHyfdAcgWp46FwY=; b=jpGGCEECVI4AbFgCH6iAWlnCjcJZBTUM2fUvKENhu6HXXdi1uKPYCozV+en4QoL44I ircyfUX67QfrSPkGBHKx0BGA380nNBEnwMCr2E3lNJHlMQ8Es6MbKH8lmtKtSb2wznfM W1a4EJ/fKEDtMAFYMphCNNnrOVo6y3jFhiCjFKmQMugGSZ8BuzmrVz9YCg8YFqH6cSfa IMJUd9v948W6FbyMCk01fA010viw13i+hS4qbjmnG+CUvd480l3DndDZPgrnQT8AEKdA WnoiQpGhmU1iqAiCtVXvNnUKzXDU6eaCVZD3tQVJZf/tdC9FG/FNCqpzPTX1tRe/s7/5 ykRw==
X-Gm-Message-State: ABuFfogRgy10WbkkesB3nRREa6kwAHjVKkZ8pSDJAPPZpgs+im7xxnPR Zu6jCEJhhZemZCxPGq+v3QLE1j/CcpxivuF/nuu68WqfQWCeLDUN9GU4laDPcRwI9DTmjFfeO+1 +GD9D04/frXdh3MgW8wmT
X-Received: by 2002:a9d:38b4:: with SMTP id p49mr13002553otc.227.1539032043276; Mon, 08 Oct 2018 13:54:03 -0700 (PDT)
X-Google-Smtp-Source: ACcGV62zNItDXvVR8YH3fctFJhIi1RHYt1t8bfDJKSofCpziRi2v0pdpEIItROyB+62WLcV3Tm3WvdzuSt5d7urJT64=
X-Received: by 2002:a9d:38b4:: with SMTP id p49mr13002547otc.227.1539032043094; Mon, 08 Oct 2018 13:54:03 -0700 (PDT)
MIME-Version: 1.0
References: <CAO0Djp0UM+iKdH+ibkyo7RSZ5a1TSDPCi6U5Sk6_-+pSvKduLg@mail.gmail.com>
In-Reply-To: <CAO0Djp0UM+iKdH+ibkyo7RSZ5a1TSDPCi6U5Sk6_-+pSvKduLg@mail.gmail.com>
From: "Chakrabarti, Samita" <samita.chakrabarti@verizon.com>
Date: Mon, 08 Oct 2018 16:53:51 -0400
Message-ID: <CAHYRG6OG8yT-fJ=WEm5B3LVZePhnFBsudGtN1Ldbrxog0dNamQ@mail.gmail.com>
To: rahul.ietf@gmail.com
Cc: 6lo@ietf.org, lwip@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003a19730577bdd254"
X-mailroute: internal
X-Proofpoint-Spam-Details: rule=out_spam_notspam policy=out_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=878 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810080195
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/TYwDHLib3Dj1WHo10FwuBhHMmfE>
Subject: Re: [Lwip] [E] [6lo] fragment forwarding implementation and performance report
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Lightweight IP stack. Official mailing list for IETF LWIG Working Group." <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lwip/>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 20:54:07 -0000

Hi Rahul,

Thanks very much for sharing the fragment forwarding implementation results.
The following drafts are implemented as per the link you provided:
Fragment Forwarding drafts

   1. Virtual reassembly buffers in 6LoWPAN
   <https://datatracker.ietf.org/doc/draft-ietf-lwig-6lowpan-virtual-reassembly/>
   2. LLN Minimal Fragment Forwarding
   <https://datatracker.ietf.org/doc/draft-watteyne-6lo-minimal-fragment/>


>From the results, I noticed an observation that send rate 80s, and 40s are
doing better than the 160s  send rate with 50s forwarding fragment spacing.
Send rate Xs means sending fragmented packets at X sec interval - right?
I thought, the performance would improve with higher X value,  but that is
not true - perhaps due to increased payload size.
A graph or tabular result with same payload size with increased send
interval rate might be useful to figure out the optimal pacing time for
that payload - just a thought.

In general, very interesting results!

Also, it shows that by controlling the pacing of forwarding the fragments
the performance can be improved to a great degree in a medium to small size
mesh. ( in this example, 50 nodes).

What happens when you increase the mesh size ( aka number of nodes)?

Cheers,
-Samita

On Mon, Oct 8, 2018 at 7:17 AM Rahul Jadhav <rahul.ietf@gmail.com> wrote:

> <sending to 6lo, lwig WGs because both have relevant drafts>
>
>
>
> Hello All,
>
>
> We tried experimenting with the virtual reassembly buffer and fragment
> forwarding drafts.
>
> One fundamental characteristic that has major implications on fragment
> forwarding performance is its behavior with realistic 802.15.4 RF
> (especially when a train of fragments are simultaneously received and
> transmitted). This is something which was not evaluated in any other
> experiment.
>
>
>
> You ll find the details of the implementation, test setup details and
> performance result here:
>
> https://github.com/nyrahul/ietf-data/blob/rst/6lo-fragfwd-perf-report.rst
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_nyrahul_ietf-2Ddata_blob_rst_6lo-2Dfragfwd-2Dperf-2Dreport.rst&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=PeFHI-ltr748QRhWwqigY8iNFPw9EcyFDwOeSrv6KQc&s=Rtytc7AFwMLDcwFQOSojZZZ3hiXl-j78GKTwYRi8Nw0&e=>
>
>
>
> Results are quite interesting: Simultaneous send/recv of fragments with
> fragment forwarding has major implications on PDR/Latency.
>
>
>
> Feedback most welcome.
>
>
>
> Thanks,
>
> Rahul
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_6lo&d=DwICAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=PeFHI-ltr748QRhWwqigY8iNFPw9EcyFDwOeSrv6KQc&s=ebzWBVEJyovVUcFHM2mByigGnDBv0aoTSm21fmwa5vU&e=
>