Re: [111attendees] timing

Diego Dujovne <diego.dujovne@gmail.com> Thu, 29 July 2021 14:46 UTC

Return-Path: <diego.dujovne@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F06B3A24FC for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 07:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 A8XjmlmDykAW for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 07:46:28 -0700 (PDT)
Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (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 5F4733A24FA for <111attendees@ietf.org>; Thu, 29 Jul 2021 07:46:28 -0700 (PDT)
Received: by mail-oi1-x236.google.com with SMTP id o185so8682127oih.13 for <111attendees@ietf.org>; Thu, 29 Jul 2021 07:46:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=L8BBpW8YMBvNT/lVztODIrg/OD+pAk4QUScmm0Ty5ds=; b=E72SgVytpO6EE+HmmDpeabC4jTAKwxp8dYb6tx2QT2KKD5RpBqCrkv8/VO7XEafun8 6+lWuVq72tyGoGMu0cxmX6mzR9U3fbJGiBJTsmiy4nGduWXrvzmp0j+A+gqb9hgzq+6L wBnHGkVkPrN6MUI1rUQPZpGSbGh3bWP/ref0ykX7wZ/rJdOCVqKTSmsIgOipXCoXQRWZ niwdVnTZd1eyJe06z0XU8m1A/lVSBZh05Rp7K0RiD7SRSqxd+yslW0H86S/ghU2vGIhE dUD0gVKt7GDbotclTQ/2rh5VjxsHAQR9A4nR23LMpIrk5hU2k3Wk3s+MiNm8fO0W2k+n i67g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=L8BBpW8YMBvNT/lVztODIrg/OD+pAk4QUScmm0Ty5ds=; b=HIlac/3K5mgLa1NegKGY3CMQr5ilMKuIIJcVKqemBbTLVQBQSS6hzzP7qhWI/BUmNK gjPIIsSA3sV1Mj41gzNRVS3ShAY+5QyynrHuGEb8KoyUqBuRiyrxrN27F/0HnMudkZm7 RsDVab5dp52WFLuVjYwloB8cPNgoaKe4p4VMGtw/88Vo6ZCOF9aWkO4NS8f5wkl1ZX8U 9Ov6DAZN6bVpAKcPGbAZrHlMAgQMaysoCdqXGGsZkqEoKdFSPmQerwN5U5XEF2mXMhiX +SO2OC2Uvc4gEkHfnF00ErvxZaU2ceXL1ffwNa8AoEzFX7FpX5K1XV5JljTxD+phCIil U4iw==
X-Gm-Message-State: AOAM530ECk6RR4qnLScQA8/nq3z9XY69RKTEK8GovLv4YpKPz1p+6GMa kMELw7iHYtGgErb9Mh4Gqbha2+D2YtukpI7QmC4=
X-Google-Smtp-Source: ABdhPJw1uvh6v7nV53UAI5G7ZX14s3w4t5IXkT0KBBBzEbYlED2Rjs2dswzTxT9CXXz6/jm50aOfYd/wMo96JgWg23c=
X-Received: by 2002:aca:c005:: with SMTP id q5mr1226909oif.153.1627569986614; Thu, 29 Jul 2021 07:46:26 -0700 (PDT)
MIME-Version: 1.0
References: <m2k0lao9uk.wl-randy@psg.com> <686590804.2522.1627479080183@appsuite-gw1.open-xchange.com> <E38F5121-EB45-45E6-B632-4ADFC9FA67A8@tzi.org> <4bd9097e-bd30-3a96-79b6-4043ccc6b8af@gmail.com> <20210729143743.GD57091@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <20210729143743.GD57091@faui48e.informatik.uni-erlangen.de>
From: Diego Dujovne <diego.dujovne@gmail.com>
Date: Thu, 29 Jul 2021 11:46:14 -0300
Message-ID: <CA+VeKNh8CowSj_QK3K=bFD4gp-5L15SkghnDygs=hFAovThkZA@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 111attendees@ietf.org
Content-Type: multipart/related; boundary="000000000000e65cc105c8442a00"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/TwwEWNv2jDiHSzJncXhLc-Zr4GA>
Subject: Re: [111attendees] timing
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2021 14:46:33 -0000

What I generally do is to ask Google: what time is UTC?

[image: image.png]
(no interest in good writing when Google understands anyway)
Then I calculate the difference myself.
Regards,

                        Diego

On Thu, Jul 29, 2021 at 11:38 AM Toerless Eckert <tte@cs.fau.de> wrote:

> AFAIK, it is quite the opposite of what you say, see also:
> https://en.wikipedia.org/wiki/Coordinated_Universal_Time
>
> UTC does minimize the amount of errors and conversion steps you need
> to do when collaborating internationally. If your reference time is
> some TZ, you need to understand not only your own local TZ offset and
> DST rules, but also that of the reference TZ offset and DST rules.
> And you effectively translate from one to the other going through UTC.
> When UTC is your reference you only need to understand your local TZ
> offset and DST rules.
>
> As to whether or not UTC exists, thats a matter of "exists" wrt to
> TZ. I guess your "exist" is that only those TZ exist that are adopted
> by some territorial entity. And while Ghana and Iceland adopt UTC+0, no
> DST,
> i would agree that recommending some countries whose TZ rules nobody
> knows is but a hack for the normal user.
>
> Nevertheless, adoption of TZ by territorial governments is but one
> type of adoption/existance. UTC is the universal standard in aviation and
> militaries as
> well as i think a lot ofthernationally coordinated organizations are
> adopting UTC directly without a need to declare themselves to be
> in Ghana or Iceland. The same is logical for IETF.
>
> Of course, we may not need to call it UTC. NATO for example
> calls UTC ZULU time. If we wanted to confuse the heck out of
> participants to make a good joke & pun (which is always a good
> reason to confuse people IMHO), we could call it iTime (Internet Time,
> IETF time).
>
> Cheers
>     Toerless
>
> On Wed, Jul 28, 2021 at 06:48:59PM +0200, Alexandre Petrescu wrote:
> > There is a difference in opposing noon start times and opposing UTC
> > references.  I oppose the latter.
> >
> > Using UTC is a big source of errors: artificial two-step conversion and
> > and an ambiguity of a third step which is the daylight savings (UTC does
> > not respect daylight savings, and UTC is the same as London times some
> > times).
> >
> > Time should be talked about in terms of geography (cities, oceans, what
> > have you) but not in absolute terms like 'Unviersal'.  There is no
> > Universal time however one might turn it.
> >
> > UTC is an anchor to go to when one does not have where to go to.  But it
> > does not really exist.
> >
> > Alex
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>