Re: [hrpc] I-D Action: draft-irtf-hrpc-political-05.txt

Eliot Lear <lear@cisco.com> Mon, 23 September 2019 11:49 UTC

Return-Path: <lear@cisco.com>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7166E120073 for <hrpc@ietfa.amsl.com>; Mon, 23 Sep 2019 04:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 qksk3Xi6rrGN for <hrpc@ietfa.amsl.com>; Mon, 23 Sep 2019 04:49:45 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E3A612008C for <hrpc@irtf.org>; Mon, 23 Sep 2019 04:49:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13629; q=dns/txt; s=iport; t=1569239384; x=1570448984; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=XXRd1PL8s/886DYpkc5hlXdrEta3Ki7fyPPY14KNOjc=; b=hAjupDtTHpvBzd5nX5rrx/SpGGUzhYEF7/J/94qwKHMVHNgSzjaAVNnv h2FY1Nfiledgy3Im2FELt0hquUGcNBcoMFi+TMPZkeEESpWm/b4McahrE jH3zfFsJhjf/+S3xH0jb55nfeHpB7uth9puOn8Roa1NmLVhVi8PVsVHyy A=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CPAADrsIhd/xbLJq1lGQEBAQEBAQEBAQEBAQwBAQEBAQGBZ4EcgW9TIBIqhCKIfId6JYdEi1OIBgIHAQEBCQMBASMMAQGEPwKDOTgTAgMJAQEEAQEBAgEFBG2FLQyFSgEBAQECASNWBQsLGCoCAlcGExUEgwkBgXsPD6s6c4EyhDcBgRSEaQoGgTSBUYpQgX+BECgME4JMPoJhAQIBgT8BAYMpMoImBIpRgX1SiGKXCoIsgi6BE4I0hiSIcRuNf4Z6hCykHoMRAgQGBQIVgWkhRIEUMxoIGxVlAYJBPhIQFIN6jBs+AzABjCeCRQEB
X-IronPort-AV: E=Sophos;i="5.64,539,1559520000"; d="asc'?scan'208,217";a="17170105"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Sep 2019 11:49:42 +0000
Received: from [10.61.212.69] ([10.61.212.69]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x8NBnfFJ014422 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 Sep 2019 11:49:42 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <B9D8A232-AF49-4809-A249-686E3A8DD309@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6A5CD394-C969-4291-83A3-523E38A8352F"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 23 Sep 2019 13:49:40 +0200
In-Reply-To: <c278a20f-7a3c-9853-8701-285cabaf8215@nielstenoever.net>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, hrpc@irtf.org
To: Niels ten Oever <mail@nielstenoever.net>
References: <156882005427.4606.6393818361687491816@ietfa.amsl.com> <a5361cda-994c-27ad-adf7-0aa06d61a8a2@nielstenoever.net> <20190920183918.d7mpxb4jyulfqqwj@anvilwalrusden.com> <CABcZeBPK8h8Bn-vhr6vq9_K9jUAE-ry5iZhLLiwjd15gpEuwHQ@mail.gmail.com> <28d4faab-cb89-34bd-d8bc-525aab96ab66@nielstenoever.net> <CABcZeBPCEiAxksRz6HnErN=eJDho+WYGg28No1YzOZEL1GjYMA@mail.gmail.com> <4aff9b71-b645-903f-bef8-ca86d048c183@cs.tcd.ie> <c278a20f-7a3c-9853-8701-285cabaf8215@nielstenoever.net>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.212.69, [10.61.212.69]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/XpuhboOkizW9BYFuHWGGcbQBBk8>
Subject: Re: [hrpc] I-D Action: draft-irtf-hrpc-political-05.txt
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "mail@nielstenoever.net" <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2019 11:49:48 -0000

Hi!

This is mostly geeky entertainment.

[Ted, I saw your note after putting most of this together.  Time has been explored… ad infinitum :-), but see below for some entertainment.]

> On 23 Sep 2019, at 11:44, Niels ten Oever <mail@nielstenoever.net> wrote:
> 
> Time, and its standardization, is a very political project. Going back to Aristotle (Physics iv 10-14) there is the difference between Chronos and Kairos, where Chronos became the number to measure motion (kinesis). There have been many other perceptions and measurements of time, that were able to exist next to each other, but as part of the colonial project, the European concept of what time was, was made the universal standard. That is why Greenwich Mean Time (in Great Britain) is used as a standard for the whole world.


But interestingly enough the initial reason for standardization of time in Britain was not political, but a simple matter of practicality; and it wasn’t the government who standardized time per-se, but rather the railways in 1847, in order to manage train schedules, and this was known as Railway Time.  It wasn’t until 1880 that GMT was officially standardized across the island of Great Britain.  GMT was set as an international standard in 1925 as a practical way for astronomers to agree on when the day began.

This gives you some idea as to just how recent in our history there was any sort of standardization of what the time is at any given moment.  However, the much of the actual units of time that we use today date back to at least 1500 BC and the Egyptians.

As Ted points out, NTP and the TZ database are based on the Gregorian calendar scale.  This does indeed prove troublesome for some countries and cultures who are on a lunar calendar.  This was noted in the development of the calendaring standard, where a “calscale” can be specified, but to my knowledge nobody has ever used anything other than Gregorian.*  The folks Calconnect could correct me, tho.

> 
> There are also many stories about the development of timezones, and their consequences, the way in which time helped shape labor, life, and how it altered complete societies.


Time?  Sure, but what part of standardization?  Time zones?  Not as much.

The first official time zone difference was used by New Zealand in 1868 as a convenience to know what time it was in the home office, as it were.  This before there was a legal standard on Great Britain.

And then there are DST transitions.  These were introduced by Germany in 1916.  With Europe about to make a remarkable leap  (so to speak) into the unknown, nobody can possibly say that there isn’t a political influence on time zones.**  The political impact?  People debate them, so I suppose there must be some.

There are some interesting stories.  One involves a contract with a satellite operator with the Holy See in which the contract was written in local time in Brazil.  Apparently they booked the wrong hour, and so a law was passed to change time.  This is actually documented in the TZ file for South America.

> 
> I am not making a value judgment about this re-odering, but I am trying to show that NTP, which helps synchronize to a specific time regime, on which a lot of computing depends, helps promulgate a specific, and political, ordering.


Let us be precise:  NTP requires only two protocol invariants: the length of a second itself and a particular epoch.  The one field that has any real political aspect at this point is the leap second indicator.  There have been some, dare I say, highly entertaining debates in the ITU-R over leap seconds.  Indeed it’s those pesky astronomers who are once again concerned about dinking with leap seconds.[1]  And let’s not even get into whether Pluto is a planet!  Still, the protocol itself is neutral as to how and when the leap second bit is set, or who has the authority to set it.

Eliot

[*]  I gave at tictoc circa 2010 on a Brief History of Time(Zones) that shows Israel spiking; that’s because of a combination of time scale, and issues relating to the High Holidays.  This has mostly been kinked out, but not entirely.  If a transition would occur on Rosh Hashanah, it is moved to the 1st of October.  This cannot be accurately reflected in the TZ database in a programmatic fashion.
[**]. No, this is not an invitation to debate Europe’s decision.  Take it to facebook! ;-)
[***] If you would like references for the above, I highly recommend A Brief History of Time, and Wikipedia now does a very decent job of it.


[1] https://www.abc.net.au/science/articles/2005/09/23/1466849.htm