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

Kevin Fall <kfall@kfall.com> Tue, 17 May 2016 01:09 UTC

Return-Path: <kfall@kfall.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 EE65D12DB25 for <dtn-interest@ietfa.amsl.com>; Mon, 16 May 2016 18:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kfall-com.20150623.gappssmtp.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 FoDOwKDvARba for <dtn-interest@ietfa.amsl.com>; Mon, 16 May 2016 18:09:30 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 CE21212D568 for <dtn-interest@irtf.org>; Mon, 16 May 2016 18:09:29 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id k142so2113310oib.1 for <dtn-interest@irtf.org>; Mon, 16 May 2016 18:09:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kfall-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=EuczP6UFJBqfqpYn3ihnalVbs7amT8TYBtUPII41t14=; b=rOcpRM05w5CVLQSmUbnBnGtIYLQGBMYr5KOP5viquChroQNXurrPs4ua7SuVVT5Ynd j0Wwt3y/a4/rlXmMSLZXURw4ATFcaYXEwBrBYOOMTUadB+AAj0s/fX70X7+up9Wmq24R 32sqwgaGVOeKHzrXSehN3ze6GNmCH/fslEGTjtYzRqY0bOKuj/yzOhMpGVj80FQ5ho0U iGX9ww3h8R4pLUlYQ3GG5Hndhi/Oar4lO5pv6vfyfty1P0F4GjD/PzAR9A2Yfayn9AzQ eBOwUuIEHZiQUekfvTjqOCaiGJ3ik8v/Ox2GHRzbW1jg54M6qb9HnMdGgCHhp3ntx52a iVdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=EuczP6UFJBqfqpYn3ihnalVbs7amT8TYBtUPII41t14=; b=eLeZB7WA2pKrrZ6zfuZvFpU74mVdaK19lOef1evuk+qlVKqH2lImeryRar98oqu4wc ZlQ6ShxqA8jjfdYobUWmIpH9aLbFb/6zL1fGAgr2haXEhpnkopkyHbUccXzmZ+dpOTc0 oDAcXp+VcmFkAiNXw+mGl4Mq91/Jh4dOW1V4Ph5WRydgiWujMTK+GulwLsizRg6sr18K D3JEUm6BUrCtvYgj7TUGxEVYNtg3vgMCyNuRIpu2Cyih+RtGN6jXRG6VuMX0fcGVDYu0 z+Hdifk5G3Y50n2LNv4VcUMPS8oQeaYTXSQRXUr/InAWV44qQy4d5D9+JxRkWT+7LE3O 9/og==
X-Gm-Message-State: AOPr4FUv+/jMCY8/UT1oTHZaAchtN3mU6QnJhdUYE/LYMtqCaDwYU2bXcw+9W7LNjQUxcZ/gBhh/SfY7PFHQJQ==
MIME-Version: 1.0
X-Received: by 10.157.7.66 with SMTP id 60mr17610360ote.187.1463447369034; Mon, 16 May 2016 18:09:29 -0700 (PDT)
Received: by 10.202.244.131 with HTTP; Mon, 16 May 2016 18:09:28 -0700 (PDT)
X-Originating-IP: [100.6.119.36]
In-Reply-To: <DB4PR06MB457C7292519F7C0BBFD3C51AD480@DB4PR06MB457.eurprd06.prod.outlook.com>
References: <CAKLzrV9rkQqAzLqARmjqecTwYTKDN3RYO3dpq9ga-pgv9R4gtw@mail.gmail.com> <DB4PR06MB457D1863ABA5661AE4435FDAD770@DB4PR06MB457.eurprd06.prod.outlook.com> <DB4PR06MB457C7292519F7C0BBFD3C51AD480@DB4PR06MB457.eurprd06.prod.outlook.com>
Date: Mon, 16 May 2016 21:09:28 -0400
Message-ID: <CALhyZY-bf-X=tDKWNa2ikqnjJFA6L-sYzybeMYoETziqaQWyxg@mail.gmail.com>
From: Kevin Fall <kfall@kfall.com>
To: l.wood@surrey.ac.uk
Content-Type: multipart/alternative; boundary="001a113de4929477c10532ff645f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtn-interest/ao-WigQptL30AkmGeJK-i_6cm8Y>
Cc: nikansell00@gmail.com, shyambs85@gmail.com, DTN interest <dtn-interest@irtf.org>
Subject: Re: [dtn-interest] Bad Clock Vs. Clock rating (0)
X-BeenThere: dtn-interest@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Tue, 17 May 2016 01:09:33 -0000

Ah, rehashing old arguments.  A real blast from the past.

The particular paper referenced below indeed points out operational cases
in which the authors had difficulty in establishing synchronized clocks.
While there are cases in which establishing time synch may be challenging,
it isn't really fundamental to the design, and there are a number of other
options people have implemented since then if you are faced with that
problem.  (or, the more realistic/interesting case in which some nodes have
a correct notion of time and others do not).  Of course, not having
synchronized time causes certain features to be difficult or impossible to
implement (e.g., expiring/deleting bundles that have been stored on passive
media lacking actual time stamps).

The reasons for the design decision of using time synchronization was given
in, for example: (
http://web.cs.ucla.edu/classes/cs217/2008DTN_Perspective.pdf), a paper from
2008.

- Kevin

On Mon, May 16, 2016 at 8:24 PM, <l.wood@surrey.ac.uk> wrote:

> I was wrong, and I'd like to take this opportunity to apologise to the
> list for being wrong and to correct my mistake.
>
>
> It was SEVEN years ago that we pointed out the fundamental problems with
> the bundle protocol's reliance on clocks and synchronization in our 'A
> Bundle of Problems' paper....
>
>
> http://personal.ee.surrey.ac.uk/Personal/L.Wood/dtn/bundle.html
>
> http://dx.doi.org/10.1109/AERO.2009.4839384
>
>
> Lloyd Wood
> http://about.me/lloydwood
>
>
> ------------------------------
> *From:* dtn-interest <dtn-interest-bounces@irtf.org> on behalf of
> l.wood@surrey.ac.uk <l.wood@surrey.ac.uk>
> *Sent:* Monday, 16 May 2016 11:25 AM
> *To:* dtn-interest@irtf.org; nikansell00@gmail.com; shyambs85@gmail.com
>
> *Subject:* Re: [dtn-interest] Bad Clock Vs. Clock rating (0)
>
>
> Five years ago we pointed out the fundamental problems with the bundle
> protocol's reliance on clocks and synchronization in our 'A Bundle of
> Problems' paper.
>
>
> http://personal.ee.surrey.ac.uk/Personal/L.Wood/dtn/bundle.html
>
> http://dx.doi.org/10.1109/AERO.2009.4839384
>
>
> People are still trying to use it and work around its clocking? As
> Australians say: so tragic.
> <http://dx.doi.org/10.1109/AERO.2009.4839384>
>
>
> Lloyd Wood
> http://about.me/lloydwood
> ------------------------------
> *From:* dtn-interest <dtn-interest-bounces@irtf.org> on behalf of Nik
> Ansell <nikansell00@gmail.com>
> *Sent:* Wednesday, 11 May 2016 2:07:49 PM
> *To:* dtn-interest@irtf.org
> *Subject:* Re: [dtn-interest] Bad Clock Vs. Clock rating (0)
>
> 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>, 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
>>
>>
>
> _______________________________________________
> dtn-interest mailing list
> dtn-interest@irtf.org
> https://www.irtf.org/mailman/listinfo/dtn-interest
>
>