[dtn] [IBR-DTN] Time sync and fragmentation

Leonel Gaspar Soares <leonelgasparsoares@gmail.com> Mon, 20 March 2017 22:56 UTC

Return-Path: <leonelgasparsoares@gmail.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F5B7129406 for <dtn@ietfa.amsl.com>; Mon, 20 Mar 2017 15:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 wLSW6dnSakof for <dtn@ietfa.amsl.com>; Mon, 20 Mar 2017 15:56:21 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8FE512940E for <dtn@ietf.org>; Mon, 20 Mar 2017 15:56:20 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id x75so78346229vke.2 for <dtn@ietf.org>; Mon, 20 Mar 2017 15:56:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=VucVxjIUCmnBpNmo7DpDRoYXBNTDJLnTZTVmcxoGgfk=; b=RKc3vBBcAI08mZWy0RAO3zFh2jhwmdR0mkqN8BJu7EEtMQFe/TgbxU+Ad1PS24sG9y g3pOyoNb5Vml2ZGAV7qa2GS0vQVQ11rJXjHXPMUtNOnaA0P4mRYZaPI+DWScdYlh1Nen OEMupPXe4KFJ+aX+o9rugjGtSGT4pHJYXIxhgaEXBkL7zONKUYWOhumsQSMVQMzXSoMS V+ldFpgmcHGs+iWis9b0ygtvh6zbCmsyt6ZhhvQZSJ4bUOcWfru8ZrmWefNBBuau/sYP 17hVgtueUITr0yzsUs5CZLhQJO/uPI7+OquvNgiC+uztxYovEpI7b3iYEqswmXK3tv3r Yh3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=VucVxjIUCmnBpNmo7DpDRoYXBNTDJLnTZTVmcxoGgfk=; b=EZGnEnkGl8lGOd7H63rKwCwLrB0hmtaP+2yLeKbtrTI6kUr/sukBlWd8yxNZ8Mf5g7 I01YcMtEdfJqlSiI8gfaWNZANcbQCmyFOSR+6U4ho79OTQP736g4lGW+Z+dvAW6LhaeX AqlhQwF+ug2v5kEVia2c1XTAdylvJtbRb7RP53Y8ye3S011TYdOUB+H0ueHXh+AF1Tsn PQY3QcoU+uVBWESFcbRDIOgIuCg8EbiLOnOsO2GB/biowlOOQcgMu8ztZFHFkEXVpVQt Mr+wSOHJyu4e5wlm2ybdCmjFKcDtEUxxGzHtkf4plgcFA/kbd4izvl6+OzwjTdJE11xc UtOA==
X-Gm-Message-State: AFeK/H1oAu3X4KrSSDqD8y/BLTAIqEYy03HIsQXpzrHKDzhEQOA6goAFfMCXpHtNLUJibhDZDM0g2KBdUiWmkw==
X-Received: by 10.31.92.20 with SMTP id q20mr5430185vkb.132.1490050579857; Mon, 20 Mar 2017 15:56:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.32.165 with HTTP; Mon, 20 Mar 2017 15:56:19 -0700 (PDT)
From: Leonel Gaspar Soares <leonelgasparsoares@gmail.com>
Date: Mon, 20 Mar 2017 22:56:19 +0000
Message-ID: <CABvAxfsvwvXtDS3W=kj18ZbWGnrtNqNeyhYnOMDcGJss358J9g@mail.gmail.com>
To: dtn@ietf.org
Content-Type: multipart/alternative; boundary="001a114e1d94828bbe054b316f48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/bk66j8nPMt9eUffTGn2RCi5-miI>
Subject: [dtn] [IBR-DTN] Time sync and fragmentation
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Mar 2017 22:56:23 -0000

Hello, I'm currently studding IBR-DTN in OpenWrt, and would like to know
how does fragmentation work in this platform. How can fragment of bundle
size be configured?
Also, experimenting with different nodes (master in time announcement and
slaves) I have the impression that slave nodes produce bundles with
timestamp 1 Jan 2000, and these are always accepted, by other slaves or
master. After synchronization, slaves transmit bundles with master date,
but if the master goes away, new slaves will transmit bundles with
timestamp 1 Jan 2000, accepted by other slaves,witch in turn transmit
bundles with timestamp, say 20 March 2017 22h30, and these are accepted by
the new slaves! Do slaves accept all bundle timestamps? Bundles emited by
slaves accepted by all?
Thanks