Re: [dtn] [Last-Call] [EXTERNAL] Re: Genart last call review of draft-ietf-dtn-bpbis-17

William Ivancic <> Tue, 12 November 2019 15:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F331C12006E for <>; Tue, 12 Nov 2019 07:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.332
X-Spam-Status: No, score=-1.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6dqrnUwaW5gk for <>; Tue, 12 Nov 2019 07:53:09 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3BBC812007C for <>; Tue, 12 Nov 2019 07:53:07 -0800 (PST)
X-Sender-Id: a2hosting|x-authuser|
Received: from (localhost []) by (Postfix) with ESMTP id 52B862C066C; Tue, 12 Nov 2019 15:53:03 +0000 (UTC)
Received: from (100-96-92-150.trex.outbound.svc.cluster.local []) (Authenticated sender: a2hosting) by (Postfix) with ESMTPA id 009592C1D4F; Tue, 12 Nov 2019 15:53:01 +0000 (UTC)
X-Sender-Id: a2hosting|x-authuser|
Received: from ([TEMPUNAVAIL]. []) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by (trex/5.18.5); Tue, 12 Nov 2019 15:53:03 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: a2hosting|x-authuser|
X-MailChannels-Auth-Id: a2hosting
X-Hysterical-Snatch: 1da7f995236805d8_1573573983070_2691866328
X-MC-Loop-Signature: 1573573983070:3529068484
X-MC-Ingress-Time: 1573573983070
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=default; h=Content-transfer-encoding:Content-type: Mime-version:In-Reply-To:References:Message-ID:To:From:Subject:Date:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=S6Pjxvsv7KHWmmTuqNizPajD4UxFspHxQydwfFvSrcU=; b=mRiaJlpW8OmA86yiCToOxpvxmj vCooBWeittxH8cQadxTf8FG0qdvDTL6mSZG0sRWhZrqkzXrs3D6XGum0jfC9gkWtVyrFhcIPdvEH4 zEZoLSqRZgL9a7JG19LWhXpo/DXUp58/P/MDOE6GM8diOfI4eTKxIKUQ0mm27MJ5giP7rE3MiAfnN Z5VjbN4SENlSxBNjBYgLhGsCHrechZE7kdP1wZvTdk2J2t7BPSl8y2nnN84LTe1J9poK1TKc0D4Tp SbvvM1vtxUyg7BIJSWzWLC4Hj8znbmCab7oLX58uOF/TGjA409ivbLI+PQBSeX1L58Dt0+Rkhfs8x d+O14PrQ==;
Received: from ([]:55018 helo=[]) by with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <>) id 1iUYTP-0034LZ-R7; Tue, 12 Nov 2019 10:52:55 -0500
User-Agent: Microsoft-MacOutlook/10.1d.0.190908
Date: Tue, 12 Nov 2019 10:52:54 -0500
From: William Ivancic <>
To: "Burleigh, Scott C (US 312B)" <>, "" <>
Message-ID: <>
Thread-Topic: [dtn] [Last-Call] [EXTERNAL] Re: Genart last call review of draft-ietf-dtn-bpbis-17
References: <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
Subject: Re: [dtn] [Last-Call] [EXTERNAL] Re: Genart last call review of draft-ietf-dtn-bpbis-17
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 12 Nov 2019 15:53:11 -0000

Scott,  In the EPOXI experiment, what were the time-to-live settings on the bundles.  I thought all bundle lifetimes were set to the duration of the mission/experiment to ensure bundles would not expire.



On 11/11/19, 10:24 PM, "dtn on behalf of Burleigh, Scott C (US 312B)" < on behalf of> wrote:

    I just now realize that what I wrote here may have been confusing: I didn't make it clear that we used BP to upload the clock corrections to EPOXI.  In some contexts that would go without saying, but perhaps not this one.
    Specifically, the clock corrections were "utcdelta" commands in "ionrc" files that were encapsulated in bundles; the files were ingested by an on-board instance of the ionadmin utility program.
    That is, we uploaded files via BP in order to correct for clock drift, rather than the other way around, and we found it easy to correct a misaligned clock on a bundle node by using the bundle protocol itself.
    The mechanism we used for this purpose back in 2008 was relatively clumsy; the new Asynchronous Management protocol will make this process somewhat more graceful.  But the basic principles were demonstrated a long time ago.
    -----Original Message-----
    From: Burleigh, Scott C (US 312B) <> 
    Sent: Monday, November 11, 2019 7:25 AM
    To:; Carsten Bormann <>rg>; Burleigh, Scott C (US 312B) <>
    Subject: RE: [dtn] [Last-Call] [EXTERNAL] Re: Genart last call review of draft-ietf-dtn-bpbis-17
    Hi, Lloyd.  I don't recall the EPOXI clock drifting that quickly, but certainly it did drift and we did upload clock corrections.  The flow of bundles was not dependent on those corrections; it is not hard to add margin in the time-to-live when bundles are sourced.  But improving the accuracy of the clocks did improve network utilization by enabling the spacecraft to start and stop communication at the beginning and end of each contact rather than a few seconds early or late.
    -----Original Message-----
    From: dtn <> On Behalf Of
    Sent: Monday, November 11, 2019 3:05 AM
    To: Carsten Bormann <>rg>; Burleigh, Scott C (US 312B) <>
    Subject: Re: [dtn] [Last-Call] [EXTERNAL] Re: Genart last call review of draft-ietf-dtn-bpbis-17
     (That wikipedia page thinks POSIX *is* unix time, and the cited reference
     doesn't seem to support that claim. Anyone want a wikipedia edit war?)
     Scott, when you did the Deep Impact/Epoxi DTN experiments, the
     spacecraft clock was drifting by over a second a day, and clock
     corrections were uploaded before you could do image uploads.
     Yes, notoriously unreliable -- in a harsh environment.
     But this is now going to be addressed with atomic clocks?
     So this is fixing software design problems in hardware?
     I don't have a solution to what I think are difficult problems.
     But I'd rather not see the protocol problems be glossed over.
     Lloyd Wood
    On Sunday, 10 November 2019, 08:54:36 GMT+11, Burleigh, Scott C (US 312B) <> wrote: 
    Thank you, Carsten.  Some notes in-line below.
    -----Original Message-----
    From: Carsten Bormann <> 
    Sent: Saturday, November 9, 2019 12:31 AM
    To: Burleigh, Scott C (US 312B) <>
    Subject: Re: [dtn] [EXTERNAL] Re: [Last-Call] Genart last call review of draft-ietf-dtn-bpbis-17
    On Nov 8, 2019, at 16:34, Burleigh, Scott C (US 312B) <> wrote:
    > I disagree.  From Wikipedia:
    > Unix time (also known as Epoch time, POSIX time,[1] seconds since the Epoch,[2] or UNIX Epoch time[3]) is a system for describing a point in time. It is the number of seconds that have elapsed since the Unix epoch, that is the time 00:00:00 UTC on 1 January 1970, minus leap seconds. Leap seconds are ignored,[4] 
    There is a problem with this phrase.
    You cannot “ignore” leap seconds if you want Posix time.
    To the contrary, you need to subtract every single one of them from the number of seconds you count from the Epoch.
        -->  I see your point: Epoch time is simply the number of seconds that have elapsed since the Unix epoch, period.  The "minus" is confusing; "omitting" would have been a little better.
        -->  If you don't have Epoch time, and instead only have UTC, then in order to convert from UTC to the equivalent Epoch time you have to add to your UTC value the applicable number of leap seconds; UTC runs slightly behind Epoch time because it counts more seconds (the leap seconds), which Epoch time does not count.  (At the moment of leap second insertion it takes 2 seconds for UTC to advance from 23:59:59 to 00:00:00 [because the advance from 23:59:59 to 23:59:60 is additionally counted], while over that same 2-second interval the Epoch time will have advanced from 23:59:59 to 00:00:01.)  If you have Epoch time, then in order to convert from Epoch time to the equivalent UTC you have to subtract from your Epoch time value the applicable number of leap seconds, thus retroactively "counting" them.
    Leap seconds are actively *not counted*, not “ignored”.
    Of course, if you think “ignore” means “not count”, you will think the sentence makes sense.
        -->  Yes.  The sentence could have been written more clearly.
    There are time scales that don’t know about leap seconds, such as TAI or GPS (*).
    Posix time does know about leap seconds, it needs them to be mostly compatible with civil time (UTC).
    (*) The GPS signal indicates the accumulated number of leap seconds since GPS epoch *along with* the monotonic time in GPS time scale (that “ignores” the fact that there are leap seconds).
    Sorry for overstressing the semantics here, but from teaching I know that half of the people understand “ignore” as “do not take any notice of”, as TAI does, and only the other half understands that you mean “do not count” as an explicit act of “ignoring”, as in Posix time.
        -->  You're right, an important clarification.
    > For example, “The Open Group Base Specifications Issue 7, Rationale: Base Definitions”, section A.4 (General Concepts) says “Coordinated Universal Time (UTC) includes leap seconds. However, in POSIX time (seconds since the Epoch), leap seconds are ignored (not applied) to provide an easy and compatible method of computing time differences.”
    “Not applied” has the same problem, maybe slightly less so.
    You “apply” leap seconds to Posix time by *not counting* them.
    > I am happy to agree that an operating system’s implementation of the time() function may typically obtain accurate UTC time (from GPS or NTP) and subtract the leap seconds out of that value to obtain Epoch time, and in this sense the implementation of the time() function is typically dependent on information about leap seconds.
    > But that is an implementation expedient, which BP does not care about.  What BP cares about is expressing time as a number of seconds that have elapsed since the Epoch (minus an offset, the number of seconds elapsed from the Epoch to midnight 1 January 2000 UTC).  The manner in which that value is generated doesn’t matter to the protocol.
    That is correct, but it means you can’t have a BP node that doesn’t know about leap seconds (either explicitly or by periodically resetting its clock to the Posix representation of civil time, which in many cases you do anyway because of clock drift).
        -->  Not quite true.  You *can* have a BP node that doesn't know about leap seconds, though I admit that this may not be common.  If the only way to implement the function that returns the current DTN time is to consult UTC time and back the leap seconds out then yes, you need to know about leap seconds.  But if the function that returns the current DTN time does so by consulting an accurate local clock that monotonically increases the count of seconds since the Epoch -- which is, for example, what all deep-space spacecraft clocks effectively do -- then no knowledge of leap seconds is needed.
        -->  Spacecraft clocks have been notoriously unstable in the past, but that is changing.  Radiation-hardened on-board electronics are increasingly reliable.  At the outer edge of what we might contemplate in the near term is the deep-space atomic clock, the first instance of which launched in June (  It may fairly be argued that an atomic clock the size of a toaster oven, massing 16 kg, is far too large and expensive to deploy on a Cubesat.  I think we find, though, that useful devices like these tend to become smaller and less costly as markets for them emerge.
    Grüße, Carsten
    last-call mailing list
    dtn mailing list
    dtn mailing list