[6lo] draft-ietf-6lo-minimal-fragment-00: When to remove VRB entries?

Martine Lenders <m.lenders@fu-berlin.de> Wed, 06 February 2019 14:49 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40351126CB6 for <6lo@ietfa.amsl.com>; Wed, 6 Feb 2019 06:49:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 yn6xeJlGZ4jW for <6lo@ietfa.amsl.com>; Wed, 6 Feb 2019 06:49:45 -0800 (PST)
Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 CD71A126BED for <6lo@ietf.org>; Wed, 6 Feb 2019 06:49:44 -0800 (PST)
Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) 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 <1grOWF-001nZr-6Z>; Wed, 06 Feb 2019 15:49:43 +0100
Received: from mail-ot1-f54.google.com ([209.85.210.54]) by inpost2.zedat.fu-berlin.de (Exim 4.85) for 6lo@ietf.org with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (envelope-from <m.lenders@fu-berlin.de>) id <1grOWE-001X2a-Sj>; Wed, 06 Feb 2019 15:49:43 +0100
Received: by mail-ot1-f54.google.com with SMTP id u16so12218920otk.8 for <6lo@ietf.org>; Wed, 06 Feb 2019 06:49:42 -0800 (PST)
X-Gm-Message-State: AHQUAuZmdaSI7E+iZbZDBsWr3CSIQNwHxsP//2NL2zt2DPKOoeJgmry6 8ERByObab5FISKi7iVgFb+ALVQctlPTU/6Rf/7s=
X-Google-Smtp-Source: AHgI3IYnDr5Y2MX8bXCfeK1NF5slIwx6O31kveJziwSUlr3SAdcqRueGfap/7tANsOStKc4Z7EskVQbWL81WcFXtc+M=
X-Received: by 2002:a9d:754f:: with SMTP id b15mr5555447otl.231.1549464581737; Wed, 06 Feb 2019 06:49:41 -0800 (PST)
MIME-Version: 1.0
From: Martine Lenders <m.lenders@fu-berlin.de>
Date: Wed, 06 Feb 2019 15:49:05 +0100
X-Gmail-Original-Message-ID: <CALHmdRwqF972Y4DG8x9QW_fg+AkwnQtzUVSgyE77FBYYO0SLpQ@mail.gmail.com>
Message-ID: <CALHmdRwqF972Y4DG8x9QW_fg+AkwnQtzUVSgyE77FBYYO0SLpQ@mail.gmail.com>
To: 6lo@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fc92ab05813ad50e"
X-Originating-IP: 209.85.210.54
X-ZEDAT-Hint: A
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/Ez0tzZDqawVn6AFhYzAFWUOtJns>
Subject: [6lo] draft-ietf-6lo-minimal-fragment-00: When to remove VRB entries?
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: Wed, 06 Feb 2019 14:49:46 -0000

Hi,

I'm currently in the process of implementing first prototypes of both
minimal fragment forwarding [1] and fragment recovery [2] for RIOT [3].

However, I'm unsure how I can determine when it is safe to remove a VRB
entry at least for the minimal forwarding case (even for a successfully
transmitted datagram). As far as I have seen not even the original VRB
draft [4] mentions a strategy for that.

For the success case I could of course just count the bytes of the
fragments and remove the VRB entry once I reach the datagram size, however
this does not account for possibly received duplicates (unless I keep track
of at least the intervals of all received fragments which of course costs
more memory).

The failure case is easier, since I could just use the timeout used in the
original 6Lo fragmentation, but using this for the success case as an
alternative to my proposal above might lead to a congestion of the VRB.

Are there any other strategies I might have missed?

Kind regards,
Martine Lenders

[1] https://datatracker.ietf.org/doc/draft-ietf-6lo-minimal-fragment/
[2] https://datatracker.ietf.org/doc/draft-ietf-6lo-fragment-recovery/
[3] https://github.com/RIOT-OS/RIOT
[4]
https://datatracker.ietf.org/doc/draft-ietf-lwig-tcp-constrained-node-networks/