January 2019 - tz - lists.iana.org

Re: [tz] Bulletin C number 57
by Hal Murray Jan. 20, 2019

Jan. 20, 2019

eggert(a)cs.ucla.edu said: > but I worry that the format change will also mess up downstream programs too > (notably NTP-related) Worked OK for ntpsec. There is a checksum in the file, but it only covers the non-comment digits in the file. (so white space changes are OK) The payload lines must start on column 1 - no leading white space. -- These are my opinions. I hate spam.

3 2

Conrad Maldives Rangali Island resort
by Deborah Goldsmith Jan. 20, 2019

Jan. 20, 2019

Apparently, this resort in the Maldives has its own time zone and observes GMT+06 year round, unlike Male at GMT+05. It looks like we’d need a new zone for this. Source: Internal reports and: http://conradglobalmediacenter.com/assets/CNRD/docs/FactSheets/ConradMaldiv… (search for “Local Time”) I wasn’t able to find any source contradicting this information. Apparently it’s a known issue that Maldives resort islands have their own (unofficial) time zones: https://www.timeanddate.com/time/zone/maldives At the moment, users need to find a time zone that has the same GMT offset (in this case Indian/Chagos works) and use that instead. Thanks, Debbie

11 15

Some rules in tz specification files seem to be applied (by zic) outside of their declared period of applicability
by Parsifal Herzog Jan. 19, 2019

Jan. 19, 2019

In the example shown below, copied from from tzdata2018i Africa file, the last Zone line, referencing the Namibia rule, should start at 1990 March 21 2:00 am. There are no Namibia transitions defined from that start, until 1994. However zic does create a transition using the second Namibia rule at the start time, as shown in the zdump output below. There are many other cases like this, where an UNTIL specification ends well before the next applicable rule of the following zone line. I am trying to read the zic manual page as a specification, and I do not understand why zic inserts that transition. It seems to me that either the last Zone line (SAST) would remain in effect until 1994, as there is no other transition defined, or that period is in an undefined state, as the SAST transition is not in effect after1990 March 21. Can someone correct my understanding? ------- Specification extract # RULE NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Vanguard section, for zic and other parsers that support negative DST. Rule Namibia 1994 only - Mar 21 0:00 -1:00 WAT Rule Namibia 1994 2017 - Sep Sun>=1 2:00 0 CAT Rule Namibia 1995 2017 - Apr Sun>=1 2:00 -1:00 WAT # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 1:30 - +0130 1903 Mar 2:00 - SAST 1942 Sep 20 2:00 2:00 1:00 SAST 1943 Mar 21 2:00 2:00 - SAST 1990 Mar 21 # independence # Vanguard section, for zic and other parsers that support negative DST. 2:00 Namibia %s ------ Zicdump output: $ zdump -v -c 1892,1996 Africa/Windhoek Africa/Windhoek -9223372036854775808 = NULL Africa/Windhoek -9223372036854689408 = NULL Africa/Windhoek Sun Feb 7 22:51:35 1892 UT = Sun Feb 7 23:59:59 1892 LMT isdst=0 gmtoff=4104 Africa/Windhoek Sun Feb 7 22:51:36 1892 UT = Mon Feb 8 00:21:36 1892 +0130 isdst=0 gmtoff=5400 Africa/Windhoek Sat Feb 28 22:29:59 1903 UT = Sat Feb 28 23:59:59 1903 +0130 isdst=0 gmtoff=5400 Africa/Windhoek Sat Feb 28 22:30:00 1903 UT = Sun Mar 1 00:30:00 1903 SAST isdst=0 gmtoff=7200 Africa/Windhoek Sat Sep 19 23:59:59 1942 UT = Sun Sep 20 01:59:59 1942 SAST isdst=0 gmtoff=7200 Africa/Windhoek Sun Sep 20 00:00:00 1942 UT = Sun Sep 20 03:00:00 1942 SAST isdst=1 gmtoff=10800 Africa/Windhoek Sat Mar 20 22:59:59 1943 UT = Sun Mar 21 01:59:59 1943 SAST isdst=1 gmtoff=10800 Africa/Windhoek Sat Mar 20 23:00:00 1943 UT = Sun Mar 21 01:00:00 1943 SAST isdst=0 gmtoff=7200 Africa/Windhoek Tue Mar 20 21:59:59 1990 UT = Tue Mar 20 23:59:59 1990 SAST isdst=0 gmtoff=7200 Africa/Windhoek Tue Mar 20 22:00:00 1990 UT = Wed Mar 21 00:00:00 1990 CAT isdst=0 gmtoff=7200 <------ zic inserted the 1994 "CAT" transition. How was this chosen? Africa/Windhoek Sun Mar 20 21:59:59 1994 UT = Sun Mar 20 23:59:59 1994 CAT isdst=0 gmtoff=7200 Africa/Windhoek Sun Mar 20 22:00:00 1994 UT = Sun Mar 20 23:00:00 1994 WAT isdst=1 gmtoff=3600 <----- first applicable rule in 1994. Africa/Windhoek Sun Sep 4 00:59:59 1994 UT = Sun Sep 4 01:59:59 1994 WAT isdst=1 gmtoff=3600 Africa/Windhoek Sun Sep 4 01:00:00 1994 UT = Sun Sep 4 03:00:00 1994 CAT isdst=0 gmtoff=7200 Africa/Windhoek Sat Apr 1 23:59:59 1995 UT = Sun Apr 2 01:59:59 1995 CAT isdst=0 gmtoff=7200 Africa/Windhoek Sun Apr 2 00:00:00 1995 UT = Sun Apr 2 01:00:00 1995 WAT isdst=1 gmtoff=3600 Africa/Windhoek Sun Sep 3 00:59:59 1995 UT = Sun Sep 3 01:59:59 1995 WAT isdst=1 gmtoff=3600 Africa/Windhoek Sun Sep 3 01:00:00 1995 UT = Sun Sep 3 03:00:00 1995 CAT isdst=0 gmtoff=7200 Africa/Windhoek 9223372036854689407 = NULL Africa/Windhoek 9223372036854775807 = NULL -------

6 6

Bulletin C number 57
by Chris Woodbury Jan. 19, 2019

Jan. 19, 2019

On Tue Jan 8 01:32:04 UTC 2019, Paul Eggert wrote:> In the meantime perhaps we could forge the NIST leap-seconds.list file > (including a comment that it's a forgery and why we're doing the > forgery), and then substitute the real thing whenever it shows up. I'd > rather have a script to do that than do it by hand, though. We'd need > that script anyway if we start basing our distribution on the IERS file, > as so many users now grab the NIST file from us rather than from the NIST.Your wish is my command.... # -=*( This file is in the public domain )*=- # This NTP leap-second file was created with data obtained from # the United States Naval Observatory (USNO) MAIA FTP server. # # Find it at: <ftp://maia.usno.navy.mil/ser7/leapsec.dat> # Updated using information from IERS Bulletin C 57 (7 Jan 2019) # Found at <ftp://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat> # # This file is not a forgery, per se, but it is created # by some one/thing other than a national metrology lab. # It is necessitated by a current US government shutdown # and the resulting lack of an NIST generated file. # # UTC is a time scale based upon standard international (SI) # seconds and derived from Temps Atomique International (TAI). # # Leap seconds are an official correction to UTC to keep it # within 0.9 seconds of UT1; yet another time standard # based upon the orientation of the earth in space. # # These data, kept in "leap-seconds.list", are used by the # Network Time Protocol daemon (NTPd) to determine when to # apply leap seconds to Coordinated Universal Time (UTC). # "leap-seconds.list" is a symbolic link to the actual # file name, leap-seconds.xxxxxxxxxx, where xxxxxxxxxx # is derived from the NTP update timestamp (below). # # Theoretically, a leap second may be positive or negative. # Realistically, negative leap seconds are unlikely to occur. # # All timestamps in this leap seconds file are encoded using the # NTP epoch. These timestamps represent the number of seconds # since 1 Jan 1900 0:00:00. This is Modified Julian Date (MJD) # 15020 and Julian Date 2415020.5. There will be an unsigned # 32-bit overflow to the second NTP era in 2036 (07 Feb 2036 # 06:28:16 UTC to be precise). # # A leap second datum consists of an NTP timestamp and the # number of seconds difference between TAI and UTC (e.g. # currently TAI-UTC is 37). UTC was established at midnight on # 1 Jan 1972 with TAI-UTC started at 10. There was no mechanism # prior to that time defining when to apply leap seconds. # # Note: the first datum in the leap-seconds.list file is *not* # a leap-second; it denotes the definition of the UTC timescale. # # Leap-seconds rules are establish in: # # International Telecommunications Union-Regulation (ITU-R) # 460-6, Annex 1, Section 2. # # <http://www.itu.int/rec/R-REC-TF.460-6-200202-I/> # # NTP Leap second files have an update time (#$). This is often # the UTC zero (0) hour time of the day when the leap second file # is built. It should be updated whenever a new IERS Bulletin C # is issued. # #$ 3755808000 # # Leap second data have a lifetime. Traditionally, this ends on # the twenty-eighth (28) day of the month six months after the # period of time described in the latest IERS Bulletin C. This # is the expiry time (#@). # #@ 3786480000 # # Leap second files have a hash, as define in NIST's FIPS 180 # Secure Hash Standard (SHS), current revision 4 (FIPS 180-4). # # FIPS Publications: <http://csrc.nist.gov/publications/fips/> # Direct Link: <http://dx.doi.org/10.6028/NIST.FIPS.180-4> # # It is based on an SHA[1] digest, created using the data # portions of the file including leap second data and the update # and expiry timestamps. All "white space" and comments are # excluded in the computation thereof. The 160-bit SHA[1] # digest polynomial are encoded in five hexadecimal grouping at # the end of the file (#h). The hash itself is NOT included in # the SHA[1]. It can also be calculated using GNU sha1sum which # generates the same 160-bit digest, given the same data, in # forty hexadecimal characters. # # NTP delta #timestamp T sign Date of Change 2272060800 10 # + : 1 Jan 1972 (MJD 41317) 2287785600 11 # + : 1 Jul 1972 (MJD 41499) 2303683200 12 # + : 1 Jan 1973 (MJD 41683) 2335219200 13 # + : 1 Jan 1974 (MJD 42048) 2366755200 14 # + : 1 Jan 1975 (MJD 42413) 2398291200 15 # + : 1 Jan 1976 (MJD 42778) 2429913600 16 # + : 1 Jan 1977 (MJD 43144) 2461449600 17 # + : 1 Jan 1978 (MJD 43509) 2492985600 18 # + : 1 Jan 1979 (MJD 43874) 2524521600 19 # + : 1 Jan 1980 (MJD 44239) 2571782400 20 # + : 1 Jul 1981 (MJD 44786) 2603318400 21 # + : 1 Jul 1982 (MJD 45151) 2634854400 22 # + : 1 Jul 1983 (MJD 45516) 2698012800 23 # + : 1 Jul 1985 (MJD 46247) 2776982400 24 # + : 1 Jan 1988 (MJD 47161) 2840140800 25 # + : 1 Jan 1990 (MJD 47892) 2871676800 26 # + : 1 Jan 1991 (MJD 48257) 2918937600 27 # + : 1 Jul 1992 (MJD 48804) 2950473600 28 # + : 1 Jul 1993 (MJD 49169) 2982009600 29 # + : 1 Jul 1994 (MJD 49534) 3029443200 30 # + : 1 Jan 1996 (MJD 50083) 3076704000 31 # + : 1 Jul 1997 (MJD 50630) 3124137600 32 # + : 1 Jan 1999 (MJD 51179) 3345062400 33 # + : 1 Jan 2006 (MJD 53736) 3439756800 34 # + : 1 Jan 2009 (MJD 54832) 3550089600 35 # + : 1 Jul 2012 (MJD 56109) 3644697600 36 # + : 1 Jul 2015 (MJD 57204) 3692217600 37 # + : 1 Jan 2017 (MJD 57754) # #h ffee5390 2e3cf253 e15b646e 01768a18 e83785c3

2 1

Bulletin C number 57
by Chris Woodbury Jan. 17, 2019

Jan. 17, 2019

On Tue Jan 8 01:32:04 UTC 2019 Paul Eggert <eggert(a)cs.ucla.edu> wrote: > In the meantime perhaps we could forge the NIST leap-seconds.list file > (including a comment that it's a forgery and why we're doing the > forgery), and then substitute the real thing whenever it shows up. I'd > rather have a script to do that than do it by hand, though. We'd need > that script anyway if we start basing our distribution on the IERS file, > as so many users now grab the NIST file from us rather than from the NIST. Your wish is my command. See attachment.

1 0

Brasil DST changes
by Dedeco Balaco Jan. 15, 2019

Jan. 15, 2019

Hello, last year, the DST automatic adjust for my recently installed system was wrong. It is a Debian 9 install. I adjusted it manually in the start and end or the period. It was not done according to what was defined by our State sometime before. Please note that it was not something done close to the change date. My friends and I looked around a bit, and we found that this change should have passed here somehow. Next year, I do not know how it will be. Who is responsible for this kind of information or update?

3 3

Notice Lead Time Tracking
by Brian Inglis Jan. 13, 2019

Jan. 13, 2019

Given some recent last minute end of year announcements, could I please suggest creating a new document to formally track metadata about every time change notice's lead time from 2019, as a basis for stats, info, distributor/vendor additions and enhancements, walls of shame, etc. as this has never yet been suggested AFAIR. I could see vendors like Apple, Google, Microsoft, Oracle dev groups adding columns to local copies to track their own responses, and using those to prod government officials to do better. The document could be a text file containing an HTML document with a table tracking: CC, announcement date[/time], effective date[/time], lead time in years-months-days [hours:minutes:seconds], tzdb release date[/time], tzdb release lead time +/- in years-months-days [hours:minutes:seconds], whether change affects STD, whether change affects DST, number of zones impacted, list of zones impacted, comments about missing details etc.; with dates[/times] in ISO formats (and perhaps also Unix format metadata attributes, allowing for JS HTML text display customization and sorting by third party users); times only specified when useful or notice is days, and times are available and accurate. If anyone has been doing this already, perhaps they could contribute their data; and anyone with interest and time could backfill data from mailing list posts. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised.

5 6

Bulletin C 57: No leap second
by Kurt Roeckx Jan. 7, 2019

Jan. 7, 2019

Bulletin C 57 was sent today, and contained: NO leap second will be introduced at the end of June 2019. The difference between Coordinated Universal Time UTC and the International Atomic Time TAI is : from 2017 January 1, 0h UTC, until further notice : UTC-TAI = -37 s Kurt

1 0

[tz-announce] 2018i release of tz code and data available
by Paul Eggert Jan. 5, 2019

Jan. 5, 2019

The 2018i release of the tz code and data is available. It reflects the following change, which was circulated on the tz mailing list: Briefly: São Tomé and Príncipe switches from +01 to +00 on 2019-01-01. Changes to future timestamps Due to a change in government, São Tomé and Príncipe switches back from +01 to +00 on 2019-01-01 at 02:00. (Thanks to Vadim Nasardinov and Michael Deckers.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2018i.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2018i.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2018i.tar.lz As usual, links to the latest release files are here: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 388b0a55116099360a99cc9973d75ae6ec63d939 dated 2018-12-30 11:05:43 -0800 and tagged '2018i' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 1a3d53043f20b8252f7598f547d78e7294d9e0cf1fcdd2159354d9769f824c8c8a03cef9cbb7fa579345fdb41372335117d2ef782ecd9c107dd0526e59492d9d tzcode2018i.tar.gz 6afcacb377842190648ed26f01abcf3db37aa2e7c63d8c509c29b4bc0078b7ff2d4e5375291b9f53498215b9e2f04936bc6145e2f651ae0be6d8166d8d336f6a tzdata2018i.tar.gz 1bdab8ce6a2fc17e9b9d88baa7423b44254811255c82ccce0031725cd316b0ac14a696451f98c72559186270de54e8f467afdb788b2b501427f72fb4ea49d145 tzdb-2018i.tar.lz Here are the GPG checksums for the release files::n -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwpGB4ACgkQ7ZfpDmKq fjTyAw/9EA6VzQop7iRV9GA3UQa6w4Rm/P6gJwF3gkz7hlAf39A6Tueulzzwk6F8 K2oIJQ/MlVGNw5yzkGHR2NTY1W3yhSJTKR5X4k2E5f/7vGnTf3USJx2Fs2Itolyn UoGSIRHWesr3tmbNUCT4LImfNyeW2MrW4q8yw1ZS7uZ34TMxDmJ+DTbomSPVhiMu yn3Y9KEqId6z3SsV8yjcDDd4J8B0zuh2WWrhSkPLXjCtGfHdiT9YaTo8y8Ayinwr xzofREicLEj1YX+3Hx0ErUCiWbtEzByOlkSX7CXfABI6EcaNaJzUsiHvrw7TTFoy u1rrJgarkrNj7YXX8Dj4PoAp4cIH4++AwNbZKfZp5PNRlzydKYX0APpuYUwmS5Qv yXqcvsOGHau/wkDb6ZPQwUwu5g7BmZQ42Yvp8tisoeGeCNnm3zu5cKyCMy2LRKyy dELRyxKEpOSOzjYqIl06yPGtQf4xgXh4r/zKCSS1bEBEpzTIV4BvoxB1R9x26hc1 IJwcuYEeU9NAq17Njcs5jyts4SnNfryxX8+RvwtJnxnmoTc1whaMHR8CMka11XI2 bJ1FlJCQr5dBA5M5cstLJZVkreoMp1bNLiVwCL+8cdAHWGXQ6SPUDuQYyUj+wKBp EX6dfVjrX/CYQVe65HnXiqxYJpDamGk2J4suSc4SG6EF8TVtQCw= =eLXg -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIyBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwpGB8ACgkQ7ZfpDmKq fjTMog/3YJT5eFuwlijuTDxlt+VMTaAEaDaSUfzmQhaTDuHPKVDXxCaWq+tcO4J8 gzzecRj40Xc/jZId7MREq2S3uyUu7D6tJR7kRMw8BeTYVkhf+wX4Xmfh+6bVB9bO 34GNTSK9BXoieio68AkaCziVhBy6KynKhzUS4d1sqEDUxhS7r3ir6jTiU4UGAf54 PKWh2YKYITuYww4XnseG9rQsKbVKK4GUm/e7OmV3zf5pI9lhf/TQh1XZXKFbKK70 gDmFPUDAyuiFBCxkA7YsGolAnkscVmuF301brsNg+VKPy1qgMbxY/vF0lo/f7xRw dzi8+ek6/pKCIUmVRWCsg68wUDh1j3pAh9MLT8zhMtxOc42Kh+4b1BNq0x45zVbQ 693ufcf056654Y27bCexy1JbGBNEd6UUGUv/Ou9EGrl6nfrfMSmUneqmBEnl8NY+ 6/cge/JOr+rVbmEku+nuC9kLZx63lSy4BXJ8+vv4DgzE6/3906V30+w/oJUGaImx PjE9tjm6biIWdRi6bZRdFcg0mktBEyzJuAuurX0ZRgcaNkrhNd4zw2Q3yuKDcD67 aM5wUA4JVLX5v6P+s5j5Y+B+OY4sVk8fFzev8BJX+wRulqEmchVertypir17PUSr oqRUAww6oaYwenZNE+6dN0OWtpLDdBUv7+pesiYcaJRrXDCLAA== =ttI4 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwpGCEACgkQ7ZfpDmKq fjRrfA//ZeU5yiKc9WOW9kco9zXoBvlHgqpxO3qI3ESgUxslFAIpeVA/26JRbEc8 AJaEEEfmKFNFtO0Wev8WAhRT6qayaxlR30qWlhQl73F+F4xVmTuCojf02HlzUS5B QpReCDZecEMXp3SmEHrog3gMtGtT6dbofUbFjXoJtwm8OpjXzlY1LdAwO33eiOKH SKr7r7q4dm/3ZVhdFP2b/OPqiF/ezhywAoYqxIUdglroGyCGtlHECEDyYIHAHlwT /hwRk96a3/ghQiEyVbqREzwBMWydTbeo+MptCtgpA1p1vmVLxLhY/3SUaOdEBIqC mYhDuLMy9SKIVtkLBc537RnUBWyCfX3p9XZ90q2YqcpqzxX47+55IKmZ8MeWEvgU OvPUV6kYVtWCO/7bNVz4I0XaJdK/tA1vhNyk8jXaMW4duCgZZsCDn5uD3oQCKJE4 O+QZqf7k5pGWT3NWFln4vv6/mahAeoV0OxpHpn1qdA6+CAa/DVdU5ZTcaleNsTSy lAd0Zt2UBCb/rycnckgT87RrAtvjUUVq4onHSaTmtOdBYfMLr5BKtD+UClAcudvd jb15tHpErlXpZ/02Bn1yfynd5xFndGA1Rj3xIRCV31/EY+pxYl4i8ZNc9lWvtLa8 PV9bGewU6EsFohzm5/1CnJbT/gKYoFVoYkdQ7/Bc+mtNjYIAYxM= =ehq4 -----END PGP SIGNATURE----- PS. If your tzdata parser does not yet support negative DST offsets, this particular release's data entries are also available in a rearguard-format tarball and signature that does not contain such offsets. This is intended to be a temporary transition aid for these parsers. The URLs are: https://web.cs.ucla.edu/~eggert/tz/release/2018i/tzdata2018i-rearguard.tar.… https://web.cs.ucla.edu/~eggert/tz/release/2018i/tzdata2018i-rearguard.tar.… with the following SHA-512 and GPG checksums: 55ec0bc2504eddc72187c80c24c80ac7a2ec4c9e5b5a4cee583dcd2f97a648b35674e1eb2e390151e689f9d4eb237615d2f0f3c64b2209672e762f0bc4c580e2 tzdata2018i-rearguard.tar.gz -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwpGB8ACgkQ7ZfpDmKq fjT/yw/9HUQnV+LGYkiQRE840qJ02XqH5K0l2R7n9OiUKsZnI+PEg5y23bUGd4+A gWwNAvC7629m+La8yiIRMO9fdNX3qHCHAXn7eUBH9nfJLcPML4t5i8kFT+NYvXwT JuauEAHDRqVQw6s0Sjeh3wsz/4Iq0c6AOuPqYC5Nnh8OgXZUsG8sNlJfB6x2Hbfe 85UimkXX+xSizN6gMxrP4Y5adoQaJRcCkvjZLm4TwGvMOTFQLNsERtl9KeiJOD3Z qEnt03Wx+kpOK2nIepe+ZgS2TtgK1uRntiu+L7MmRPmNriegCE+SCQVZhl5Kbm4a HHORTs/97B9ec6tiNreL0lg35Z/0vKA4KUdcpBGCaylGNvXNmz4TnHWHpdOWgueD 3O8E87edCTAUvQ8rAoEcqmg6CPrr2p/gfn+96w1EBfBqVJCjsZ/6KaDhbb6/LBAr oHd3TVtHMxpxrkxGXCyZwwpHEQtdnKeWPAyyc5kKd9LqUM1YQLQhQ44aN0SBeO8n spAFJLQm03GA+1aw1ETVrid474PMLTGKQj4iOg0XY/91E/L5p+Pf15ztMBo8asie lo07vW+o0ED3N0p60EXIdZxnokm/hPLo9yqbrCGpXE6wHcSFOgiK/Q5wOahrA/y0 LVI5yJt9Bc+hHLcQnwIPQei2P50ixVVDq8k2hTiM+2PN3iIcoGY= =fOhE -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

5 10

Timezone change for Asia/Qyzylorda
by Zhanbolat Raimbekov Jan. 3, 2019

Jan. 3, 2019

Hi, Starting 21 December 2018 00:00, Qyzylorda oblast, Kazakhstan (Asia/Qyzylorda) has moved back from +6 to +5. Link: http://adilet.zan.kz/rus/docs/P1800000817 -- Zhanbolat Raimbekov, Rochester Institute of Technology '12

9 15