"I wouldn't have thought that Frontier was able to offer dark fiber loops to
end user customers at any kind of reasonable product-scale".
Sorry; didn't know I had to show my work here. :-)
Cheers,
-- jra
- Original Message -
> From: "Eric Kuhnke"
> To: "nanog@nanog.org list"
> Sent: W
Personally I'd like to see the UTC timescale be fixed to the TAI timescale
with a fixed offset determined by whatever the offset is when they make the
change.
Or stated as a different solution with the same result: quit
adding/removing seconds from the TAI to UTC offset.
At the same time, those
Hey, This is not an advertisement but an attempt to help folks to better understand networking HW. Some of you might know (and love 😊) “between 0x2 nerds” podcast Jeff Doyle and I have been hosting for a couple of years. Following up the discussion we have decided to dedicate a number of upcoming p
Any regional ILEC spanning at least a few counties in size will have some
amount of inter-CO dark fiber, whether they want to sell it to any 3rd
parties is entirely another question.
On Wed, 3 Aug 2022 at 08:17, Jay Ashworth wrote:
> I wouldn't have thought that Frontier was able to offer dark
talk at
https://www.youtube.com/watch?v=beuy9QbQ5lg
(higher quality) slides at
https://archive.nanog.org/meetings/nanog49/presentations/Monday/gill-keynote.pdf
> On Aug 3, 2022, at 12:45 PM, Mel Beckman wrote:
>
> Besides his many contributions to Nanog, I knew Vij from Twilio. He was very
>
- Original Message -
> From: "Brandon Martin"
> On 8/3/22 11:16, Jay Ashworth wrote:
>> I wouldn't have thought that Frontier was able to offer dark fiber,
>> since air distribution fan out is all GPON, is it not?
>>
>> If their fanout was active ethernet it might be a different story bu
On 8/3/22 11:16, Jay Ashworth wrote:
I wouldn't have thought that Frontier was able to offer dark fiber,
since air distribution fan out is all GPON, is it not?
If their fanout was active ethernet it might be a different story but...
They have access to/control of a large amount of mid-mile an
Besides his many contributions to Nanog, I knew Vij from Twilio. He was very
willing to share his time at one of the Twillio conferences, where I had been
hired to stand up the conference WiFi network on a leased gigabit pipe on very
short notice. I became a Twilio user as a result of his enthus
- Original Message -
> From: "Peter Beckman"
> On Wed, 3 Aug 2022, Matthew Huff wrote:
> This shouldn't cause huge issues, as most systems will not freak out and
> die if the system clocks goes from 23:59:58 to 00:00:00. But things that
> were supposed to happen at 23:59:59 on that day
This is why we've internally standardized on Leap smearing, an added benefit is
that it keeps us in sync with Google and AWS who also smear time in the same
way.
Daniel Marks
d...@nielmarks.com
--- Original Message ---
On Wednesday, August 3rd, 2022 at 11:33 AM, Matthew Huff wrote:
> Begin forwarded message:
>
> From: Herb L via CAGeeks
> Subject: [CA Geeks] Vijay Gill
> Date: August 2, 2022 at 20:47:13 EDT
> To: CA Geeks
> Reply-To: Herb L
>
> All,
> I was told that Vijay passed on from a heart attack while at work. I am
> deeply saddened by the news and wish to con
On Wed, 3 Aug 2022, Matthew Huff wrote:
But it's hard enough to get developers to understand the need to code for
61 seconds in a minute, and now they would need to code for 59 seconds as
well.
If time systems simply skewed the time so that 60 seconds actually just
took 61 seconds or 59 seconds
Just to set the standard.
There is no "during" a negative leap second.
A positive leap second proceeds as
23:59:59
23:59:60 <--- second added here
00:00:00
A negative leap second proceeds as
23:59:58
00:00:00 <--- whoops! second 59 is gone!!!
Those systems that "smear" leap seconds over a 24 ho
Sure.
ALL of this has been gamed out, and I had believed, handled, by the 8601 nerds,
and we ignore that investment of work at our peril.
On August 3, 2022 11:33:09 AM EDT, Matthew Huff wrote:
>True,
>
>But it's hard enough to get developers to understand the need to code for 61
>seconds in a
True,
But it's hard enough to get developers to understand the need to code for 61
seconds in a minute, and now they would need to code for 59 seconds as well.
If time systems simply skewed the time so that 60 seconds actually just took 61
seconds or 59 seconds, there would be other issues, bu
On Wed, Aug 03, 2022 at 11:09:25AM -0400,
Jay Ashworth wrote
a message of 32 lines which said:
> General press loses its *mind*:
Indeed, they seem not to know what they write about. "atomic time –
the universal way time is measured on Earth – may have to change" They
don't even know the diffe
I wouldn't have thought that Frontier was able to offer dark fiber, since air
distribution fan out is all GPON, is it not?
If their fanout was active ethernet it might be a different story but...
Cheers,
-- jra
On July 13, 2022 7:40:47 AM EDT, Mike Hammett wrote:
>I'm looking for a contact at
General press loses its *mind*:
https://www.cbsnews.com/news/earth-spinning-faster-than-usual-shortest-day-ever/#app
Have you tested leap second handling, especially in reverse? How do you
simulate it? Are there existing test harnesses for simulating it?
Cheers,
-- jra
--
Sent from my Androi
When working with ILECs it is important to differentiate what must be offered
via ICAs and what is offered commercially. We for example sell a ton
commercially but effectively none through our interconnection agreements
anymore.
(we being Ziply Fiber in WA/OR/ID/MT)
From: NANOG On Behalf Of
19 matches
Mail list logo
