Many systems have less than ideal separation of collection, storage, viewing, export, etc. timezones. I prefer to view in local time. I may wish to export in another. Storage in UTC to facilitate all of this makes sense. Normalizing input timezones would be nice.
A boy can only dream...
From: "Christopher Morrow" <morrowc.lists@gmail.com>
To: "nanog list" <nanog@nanog.org>
Sent: Thursday, May 9, 2019 2:16:59 PM
Subject: Re: NTP for ASBRs?
On Thu, May 9, 2019 at 3:12 PM Andy Smith <andy@strugglers.net> wrote:
>
> Hello,
>
> On Wed, May 08, 2019 at 10:27:30PM -0400, Christopher Morrow wrote:
> > UTC is nice
> > EST is nice
> > PDT is nice..
> >
> > pick one, deal with the eccentricities of that decision without
> > foisting your religion on the rest of me. :)
>
> Yes and no. Anything non-UTC can cause issues when working with
> other organisations.
"deal with the eccentricities of that decision without
foisting your religion on the rest of me"
I clearly mistyped: "me" at the end there with "us"... Your point is
squarely on: Hey, you do you... when you talk to me be prepared to
normalize my TZ and yours.
(which may mean;: send in UTC store in ElboniaStandardTime"
> More than once I've received logs or incident notifications from
> suppliers without a time zone stated at all. I've then asked the
> time zone only to be told "It's PST" when in fact the real answer
> was PDT as the supplier was currently in DST. Others shouldn't have
> to work this hard, epseically with DST dates being a matter of local
> legislation, and one way of helping that to happen from the first
> line support up is to use UTC.
>
> Cheers,
> Andy