[6lo] RIOT implementation for Selective Fragment Recovery
Martine Lenders <mail@martine-lenders.eu> Tue, 05 November 2019 19:48 UTC
Return-Path: <mail@martine-lenders.eu>
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 630BD1200F4 for <6lo@ietfa.amsl.com>; Tue, 5 Nov 2019 11:48:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 XbfAKqJMZccF for <6lo@ietfa.amsl.com>; Tue, 5 Nov 2019 11:48:57 -0800 (PST)
Received: from dubhe.uberspace.de (dubhe.uberspace.de [185.26.156.47]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ADCE1208AB for <6lo@ietf.org>; Tue, 5 Nov 2019 11:48:56 -0800 (PST)
Received: (qmail 26809 invoked from network); 5 Nov 2019 19:48:54 -0000
Received: from localhost (HELO mail-oi1-f178.google.com) (127.0.0.1) by dubhe.uberspace.de with SMTP; 5 Nov 2019 19:48:54 -0000
Received: by mail-oi1-f178.google.com with SMTP id k2so18664623oij.12 for <6lo@ietf.org>; Tue, 05 Nov 2019 11:48:53 -0800 (PST)
X-Gm-Message-State: APjAAAWhfHkWMsIjq2ZQnA7Fp9R0pthFg8g/s7Wcax/SCHvT4cElIxAK DEZGw+vwc4xnsblGFM6ztGdMmibjeGhc5HlPcRg=
X-Google-Smtp-Source: APXvYqzQUcL4BlGzQFqBGVbTY4jDZfRHBm57jeN4zpW8zahdLOQGz0KRDTIZQdURT9p7vBtjLJxc9zUPqmEef8PAuIk=
X-Received: by 2002:aca:306:: with SMTP id 6mr637778oid.162.1572983330435; Tue, 05 Nov 2019 11:48:50 -0800 (PST)
MIME-Version: 1.0
From: Martine Lenders <mail@martine-lenders.eu>
Date: Tue, 05 Nov 2019 20:48:14 +0100
X-Gmail-Original-Message-ID: <CALHmdRwnxq-P96dcTzZ5mQgHsJR7q4833JTwdc4z_CJh4+Qs-A@mail.gmail.com>
Message-ID: <CALHmdRwnxq-P96dcTzZ5mQgHsJR7q4833JTwdc4z_CJh4+Qs-A@mail.gmail.com>
To: 6lo@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a5f81f05969eb8c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/yiOS5PPUeLtOZRizDtdwDPV08zg>
X-Mailman-Approved-At: Tue, 05 Nov 2019 22:23:19 -0800
Subject: [6lo] RIOT implementation for Selective Fragment Recovery
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: Tue, 05 Nov 2019 19:48:59 -0000
Hello, I finally finished a first presentable draft of my Selective Fragment Recovery implementation for RIOT [1]. It still needs a lot of testing and thus there are most definitely still some major bugs in there, but feel free to have a look. Regarding my previous question [2]: I solved it now by making the node where the hop-limit is reached the reassembling end-point, which is I believe most in line with the protocol as it was designed. Best regards, Martine [1] https://github.com/RIOT-OS/RIOT/pull/12648 [2] https://mailarchive.ietf.org/arch/msg/6lo/vWZvBbdjR15vOYNkz-mw6VXBJH0
- [6lo] RIOT implementation for Selective Fragment … Martine Lenders
- Re: [6lo] RIOT implementation for Selective Fragm… Pascal Thubert (pthubert)