Re: [111attendees] timing

Toerless Eckert <> Thu, 29 July 2021 14:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 32BCE3A24C9 for <>; Thu, 29 Jul 2021 07:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=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
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jUWN28NhDhwD for <>; Thu, 29 Jul 2021 07:37:52 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1340D3A24CC for <>; Thu, 29 Jul 2021 07:37:51 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 0B060548015; Thu, 29 Jul 2021 16:37:44 +0200 (CEST)
Received: by (Postfix, from userid 10463) id 01A1F4E7BA3; Thu, 29 Jul 2021 16:37:43 +0200 (CEST)
Date: Thu, 29 Jul 2021 16:37:43 +0200
From: Toerless Eckert <>
To: Alexandre Petrescu <>
Message-ID: <>
References: <> <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <>
Subject: Re: [111attendees] timing
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 29 Jul 2021 14:37:57 -0000

AFAIK, it is quite the opposite of what you say, see also:

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).


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