Chris Adams :
> Leap seconds are inserted to keep the atomic clocks synced with an
> arbitrary time base (that is guaranteed to vary forever). There's
> nothing magic about having noon UTC meaning the Sun is directly over 0°
> longitude; if we didn't insert leap seconds, it would have drifted
> sl
On 9 July 2016 at 04:39, Patrick W. Gilmore wrote:
Hey,
> But time _DOES_ flow. The seconds count
> 58, 59, 60, 00, 01, …
> If you can’t keep up, that’s not UTC’s fault.
Check the implementation on your PC. This is why code is broken and
people don't even know it's broken. You have to u
On 8/Jul/16 04:43, Manuel Marín wrote:
> Dear Nanog community
>
> We are currently experimenting TCP degradation issues in some metro markets
> where there are multiple POPs and the IP packets have to pass multiple L3
> access devices (routers) before reaching the core router. The more L3 hops
>
At about 16:46 UTC block 420001 showed up on the Bitcoin blockchain,
so the mining reward per block dropped from 25 to 12.5 btc.
Depending on whom you believe, nothing will change, or most of the
miners will go offline, or something else. My blockchain client saw
420002 was over 25 minutes after
This is pretty O/T for this list, isn't it?
On Jul 9, 2016 12:15 PM, "John Levine" wrote:
> At about 16:46 UTC block 420001 showed up on the Bitcoin blockchain,
> so the mining reward per block dropped from 25 to 12.5 btc.
>
> Depending on whom you believe, nothing will change, or most of the
> m
Hi,
> This is pretty O/T for this list, isn't it?
not if he's using his routers ASICs to do it! ;-)
(or maybe its related to the bitcoin network traffic volumes...but
thats too logical...)
alan
Hi,
> Leap second handling code is not well-tested and is an ultimate corner
> case. There's been debate about abolishing leap seconds; with all the
well, we've gone through a few of these now...so if it was all okay before
its likely to be again... exception: any NEW code that
you are running s
On Sat, Jul 9, 2016 at 2:04 PM, wrote:
> Hi,
Blockchain-based replacement for RPKI involving encoding of
IP address registry registrations assigned to a Network operator's
specified Org ID wallet, And LOAs for propagating the announcement
of a prefix by using Colored coins automatically
On 9 July 2016 at 22:09, wrote:
> well, we've gone through a few of these now...so if it was all okay before
> its likely to be again... exception: any NEW code that
> you are running since last time - THAT hasnt been tested ;-)
In most cases the bugs are not pathological if the elapsed time is
On Sat, 09 Jul 2016 12:14:03 +0300, Saku Ytti said:
> Check the implementation on your PC. This is why code is broken and
> people don't even know it's broken. You have to use monotonic time to
> measure passage of time, which is not particularly easy to do
> portable, in some languages.
It doesn
POSIX (Unix) (normal) time does not have leap seconds.
Every POSIX (Unix) (normal) minute has exactly 60 seconds.
Every POSIX (Unix) (normal) hour has exactly 60 minutes.
Every POSIX (Unix) (normal) day has exactly 24 hours.
Every POSIX (Unix) (normal) year has 365 days, unless it is a leap year,
On Sat, Jul 9, 2016 at 3:10 PM, Jimmy Hess wrote:
> On Sat, Jul 9, 2016 at 2:04 PM, wrote:
> > Hi,
>
> Blockchain-based replacement for RPKI involving encoding of
> IP address registry registrations assigned to a Network operator's
> specified Org ID wallet, And LOAs for propagating the an
How'd namecoin work out? .bit taking over the internet?
/kc
On Sat, Jul 09, 2016 at 05:39:17PM -0400, Christopher Morrow said:
>On Sat, Jul 9, 2016 at 3:10 PM, Jimmy Hess wrote:
>
>> On Sat, Jul 9, 2016 at 2:04 PM, wrote:
>> > Hi,
>>
>> Blockchain-based replacement for RPKI involvi
On Saturday, July 9, 2016, Christopher Morrow
wrote:
> On Sat, Jul 9, 2016 at 3:10 PM, Jimmy Hess > wrote:
>
> > On Sat, Jul 9, 2016 at 2:04 PM, >
> wrote:
> > > Hi,
> >
> > Blockchain-based replacement for RPKI involving encoding of
> > IP address registry registrations assigned to a Networ
14 matches
Mail list logo
