Re: [dtn-interest] Bad Clock Vs. Clock rating (0)

Nik Ansell <nikansell00@gmail.com> Wed, 11 May 2016 04:07 UTC

Return-Path: <nikansell00@gmail.com>
X-Original-To: dtn-interest@ietfa.amsl.com
Delivered-To: dtn-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06E9312D13C for <dtn-interest@ietfa.amsl.com>; Tue, 10 May 2016 21:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO_END_DIGIT=0.25, 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 YTKhyJu9zToL for <dtn-interest@ietfa.amsl.com>; Tue, 10 May 2016 21:07:50 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 A8C5012D0AE for <dtn-interest@irtf.org>; Tue, 10 May 2016 21:07:50 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id d62so40167510iof.2 for <dtn-interest@irtf.org>; Tue, 10 May 2016 21:07:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to; bh=bg/c6ascauQfpWsHMZkR6QdO8+TIcYOqLMq92Rcyhgg=; b=IPNxZTbqkxwQU6c+tdVIFPOPkXPsFXXSNOkG6sJWj94Bh7hRRp0MfY9E3FSIogG/VN hhZcpOddDd/rR2JHFctzhbXGUwrQ52Sw6OOGOHwNKwZ+vqMMfi4DEfw2FhDDga2f6oJq VSKN3Lqavejq3Mkle3bSVSXZcxYDUCCdZQ5E+cbc+T/pxAHXmcTnhgd0iF395xv/fPv8 OfdqZWjbMQzLX8mZL6jj1sCzsShnRLuE9hcbPjMZXhQ7VScxS7QcKVfvXWqqjnBkpIFE 92sCpszkGOkADlo5O+pWigiL/nOoMc2CDIc6D39ODlupxLnLC2dn1eNwCVkMjDVp5NqQ 3n8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:date:message-id:subject :from:to; bh=bg/c6ascauQfpWsHMZkR6QdO8+TIcYOqLMq92Rcyhgg=; b=LA2Msp+C7lS477SYnuvu3QuyaxTSYhdi2FQSCQ+I7weF9w7yzd8gnvOVTXSqCKVguh MZxmUsmDDmhGpE399wF7fwoDetcOG/y/5uvQLT2i+92GWLA+iKfRLso6VMDGdfkpez0c GhUm01TBpxbOva9rTC0kI47iqvOx3Fp8AahAkld5HyIvbvrAIdH/qP8okbf7o8Qnc3Ca riVZOdlH5/AaYQTudm98Ln4QINBbX6chrTIx0en74R2H5iLEf2g2pgFmJ9/TO1e3OSAl 415CLbuJQUuCdjxlP1ex2ke3rN7BTjf9h9oqtH+zTVJt+3Fi2QJsfmP9J3fG1nhOzoOT Aa3g==
X-Gm-Message-State: AOPr4FXWrniKJuEGsA+CJj9cD7rZYiSo3KT1VsEJ1MqD7/PpJS1crKZd/VTOPsKUORtTwi9SMbNdObAG/wf78g==
MIME-Version: 1.0
X-Received: by 10.107.9.167 with SMTP id 39mr1601901ioj.98.1462939669850; Tue, 10 May 2016 21:07:49 -0700 (PDT)
Received: by 10.79.110.76 with HTTP; Tue, 10 May 2016 21:07:49 -0700 (PDT)
Date: Wed, 11 May 2016 08:07:49 +0400
Message-ID: <CAKLzrV9rkQqAzLqARmjqecTwYTKDN3RYO3dpq9ga-pgv9R4gtw@mail.gmail.com>
From: Nik Ansell <nikansell00@gmail.com>
To: dtn-interest@irtf.org
Content-Type: multipart/alternative; boundary=001a113eafa8598ad00532892f40
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtn-interest/H87NnOO_XP1VanUE9Oz5G0lfmmo>
Subject: Re: [dtn-interest] Bad Clock Vs. Clock rating (0)
X-BeenThere: dtn-interest@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nikansell00@gmail.com
List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." <dtn-interest.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn-interest/>
List-Post: <mailto:dtn-interest@irtf.org>
List-Help: <mailto:dtn-interest-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 04:07:53 -0000

A good way to get in touch with the IBR-DTN guys is to use the mailing list
below.

ibr-dtn@ibr.cs.tu-bs.de

The main admin page for the mailing list is here:
https://mail.ibr.cs.tu-bs.de/mailman/listinfo/ibr-dtn

Kind Regards,
Nik

On Tue, May 10, 2016 at 11:00 PM, <dtn-interest-request@irtf.org> wrote:

> Send dtn-interest mailing list submissions to
>         dtn-interest@irtf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.irtf.org/mailman/listinfo/dtn-interest
> or, via email, send a message with subject or body 'help' to
>         dtn-interest-request@irtf.org
>
> You can reach the person managing the list at
>         dtn-interest-owner@irtf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dtn-interest digest..."
>
> Today's Topics:
>
>    1. Re: Bad Clock Vs. Clock rating (0) (Joerg Ott)
>
>
> ---------- Forwarded message ----------
> From: Joerg Ott <jo@netlab.tkk.fi>
> To: Shyam B <shyambs85@gmail.com>om>, dtn-interest@irtf.org
> Cc: kfall@kfall.com
> Date: Tue, 10 May 2016 07:19:16 +0200
> Subject: Re: [dtn-interest] Bad Clock Vs. Clock rating (0)
> I wo¨ld ask the IBR-DTN folks...
>
> On 10.05.16 01:37, Shyam B wrote:
>
>> Hello All,
>>
>> Thanks for the evolving community of DTN. I hope someone can help me
>> with the questions below:
>>
>> How to remove time synchronization between nodes on later versions of
>> IBRDTN:
>> We are using the latest version(s) of IBRDTN on OpenWRT. I read from the
>> change log "Version 1.0.1 (2015-02-24)" that BAD CLOCK has been replaced
>> by something called clock rating (set to 0).
>>
>> 1) I would like to know where and how can I set this clock rating to 0
>> on a node? Is it to be set in the "ibrdtn.conf" file or somewhere else -
>> any specifics will be helpful.
>>
>> 2) I believe this will need to be set "on each node" and the dtnd daemon
>> would read this during its initiation at run-time to bypass any clock
>> synchronization needed to receive bundles/ as well as dtnping, am I right?
>>
>> NOTE: We do not require clock synchronization to keeping our scenarios
>> simple. Just need a way to pass bundles between nodes "under any
>> circumstance".
>>
>> Reference:
>> https://trac.ibr.cs.tu-bs.de/project-cm-2012-ibrdtn/wiki/changelog
>>
>> Thanks for your time. Hope someone can help us soon!
>>
>> --
>> Regards,
>> Shyam, B
>>
>>
>
>
> _______________________________________________
> dtn-interest mailing list
> dtn-interest@irtf.org
> https://www.irtf.org/mailman/listinfo/dtn-interest
>
>