[6lo] Paper on minimal fragment forwarding (was Question on draft-ietf-6lo-fragment-recovery and VRB)

Martine Lenders <m.lenders@fu-berlin.de> Fri, 30 August 2019 13:08 UTC

Return-Path: <m.lenders@fu-berlin.de>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 514CF120120 for <6lo@ietfa.amsl.com>; Fri, 30 Aug 2019 06:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.177
X-Spam-Status: No, score=-3.177 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id hstLkVOF58fb for <6lo@ietfa.amsl.com>; Fri, 30 Aug 2019 06:07:59 -0700 (PDT)
Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de []) (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 53AC2120115 for <6lo@ietf.org>; Fri, 30 Aug 2019 06:07:59 -0700 (PDT)
Received: from inpost2.zedat.fu-berlin.de ([]) by outpost.zedat.fu-berlin.de (Exim 4.85) for 6lo@ietf.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (envelope-from <m.lenders@fu-berlin.de>) id <1i3gdB-002kfH-KE>; Fri, 30 Aug 2019 15:07:57 +0200
Received: from mail-oi1-f179.google.com ([]) by inpost2.zedat.fu-berlin.de (Exim 4.85) for 6lo@ietf.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (envelope-from <m.lenders@fu-berlin.de>) id <1i3gdB-002qTq-7L>; Fri, 30 Aug 2019 15:07:57 +0200
Received: by mail-oi1-f179.google.com with SMTP id n1so5300023oic.3 for <6lo@ietf.org>; Fri, 30 Aug 2019 06:07:57 -0700 (PDT)
X-Gm-Message-State: APjAAAWOWjLqSCSeCgNcFB1nO831o4/jUr8baV1wp7yVCNBp886yWFaN 7qRdA7UphJ1Y3VzMTnEEWFps+kj6DZ8F4bt97VE=
X-Google-Smtp-Source: APXvYqx/CE/I6f9br1Zt50uGpVwyFbG0bAbr55PsPNFvY17ZLbZ8f9gk7pHi+pKtaDF1n2QmU5TJGip+EaNPODteCHU=
X-Received: by 2002:a54:4108:: with SMTP id l8mr9660231oic.97.1567170476096; Fri, 30 Aug 2019 06:07:56 -0700 (PDT)
MIME-Version: 1.0
References: <CALHmdRxLUXy9g94iYn+7Ujmr+0bmBR0Oo3psbHcZOauT08rOHg@mail.gmail.com> <MN2PR11MB35658D8325E730B3FD593019D8BD0@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB35658D8325E730B3FD593019D8BD0@MN2PR11MB3565.namprd11.prod.outlook.com>
From: Martine Lenders <m.lenders@fu-berlin.de>
Date: Fri, 30 Aug 2019 15:07:19 +0200
X-Gmail-Original-Message-ID: <CALHmdRxsfbqtdr=pPrm6ngkqAS_fWD2xLZMoU2C+gtrV+3NUqg@mail.gmail.com>
Message-ID: <CALHmdRxsfbqtdr=pPrm6ngkqAS_fWD2xLZMoU2C+gtrV+3NUqg@mail.gmail.com>
Cc: "6lo@ietf.org" <6lo@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000087c3170591554f02"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/tZ3hLNJQLi1QVMWek8pNPSkTC6w>
Subject: [6lo] Paper on minimal fragment forwarding (was Question on draft-ietf-6lo-fragment-recovery and VRB)
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2019 13:08:02 -0000


Am Fr., 30. Aug. 2019 um 13:44 Uhr schrieb Pascal Thubert (pthubert) <

> Great to hear about your implementation. The group is interested to learn
> about your progress (keep us tuned) and happy to help you through. P

That reminded me that I actually wanted to tell the group about a paper of
ours ages ago. It evaluates our implementation of

- M. S. Lenders, T. C. Schmidt, M. Wählisch. "A Lesson in Scaling 6LoWPAN -
Minimal Fragment Forwarding in Lossy Networks." in Proc. of IEEE LCN, 2019.

All the better now, as it allows me to show you the pre-print of its final
form, as it got accepted for IEEE LCN'19 [1]. The implementation itself is
PR'd against RIOT on GitHub [2]. Not many surprises, but maybe an
interesting read for some.

Kind regards,

[1] https://arxiv.org/abs/1905.08089
[2] https://github.com/RIOT-OS/RIOT/pull/11068