- tz - lists.iana.org

About time
by Arthur David Olson Feb. 2, 2019

Feb. 2, 2019

Having stumbled across a copy of the educational film "About Time," I can correct the quotations that kick off the README file; the diffs should be attached. @dashdashado

4 3

Europe/Budapest timezone
by Lev Feb. 2, 2019

Feb. 2, 2019

Dear all, I've downloaded the current time zone data from this link: https://data.iana.org/time-zones/releases/tzdata2018i.tar.gz , and compiled the time zone files with zic. For Europe/Budapest, I got this tz string: CET-1CEST,M3.5.0,M10.5.0/3 I think IMHO it should be: CET-1CEST,M3.5.0/2,M10.5.0/3 Best regards, Levente -- Levente Kovacs Senior Electronic Engineer W: http://levente.logonex.eu

4 5

Fwd: Bulletin C number 57
by Tim Parenti Feb. 1, 2019

Feb. 1, 2019

FYI, per IERS Bulletin C57, there will be no leap second on 2019-06-30. Unfortunately, NIST is affected by the partial shutdown of the US government <https://www.commerce.gov/news/blog/2018/12/shutdown-due-lapse-congressional…> which has been ongoing since 2018-12-22 00:00 -05, so most of their website is unavailable, meaning it will likely be some time before they publish an updated leap-seconds.list. But since the current NIST file doesn't expire until 2019-06-28, we've got some time before we have to deal with that. Last we had left the problem of being able to take the equivalent file directly from the IERS at https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list, some lines had been added to https://hpiers.obspm.fr/iers/bul/bulc/README on 2017-04-11, but the exact text did not make any assertions about surrounding files, and we would prefer the notice be added to leap-seconds.list itself. (There are a few other typos therein which I spotted as well.) See: https://mm.icann.org/pipermail/tz/2017-April/024990.html https://mm.icann.org/pipermail/tz/2017-April/024988.html In light of the current US/NIST situation, it would be helpful to re-energize these efforts. Happy to help Christian and others come up with something workable. -- Tim Parenti ---------- Forwarded message --------- From: IERS EOP Product Center <iers.eoppc(a)obspm.fr> Date: Mon, 7 Jan 2019 at 10:56 Subject: Bulletin C number 57 To: <bulc.iers(a)obspm.fr> INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE SERVICE DE LA ROTATION TERRESTRE DE L'IERS OBSERVATOIRE DE PARIS 61, Av. de l'Observatoire 75014 PARIS (France) Tel. : +33 1 40 51 23 35 e-mail : services.iers(a)obspm.fr http://hpiers.obspm.fr/eop-pc Paris, 07 January 2019 Bulletin C 57 To authorities responsible for the measurement and distribution of time INFORMATION ON UTC - TAI 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 Leap seconds can be introduced in UTC at the end of the months of December or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every six months, either to announce a time step in UTC, or to confirm that there will be no time step at the next possible date. Christian BIZOUARD Director Earth Orientation Center of IERS Observatoire de Paris, France

8 19

[calsify] Streaming info for CalConnect Public Time Zone Workshop on February 5 in Zurich, Switzerland
by David Thewlis Jan. 31, 2019

Jan. 31, 2019

The CalConnect Public Time Zone Workshop will be next Tuesday, 5 February 2019, between 1400 and 1730 Central European Time. We have made arrangements with our host, Google, to stream the CalConnect Public Time Zone Workshop <https://www.calconnect.org/events/calconnect-public-time-zone-worksjop> for any interested parties who cannot be present. (The workshop was announced in November and we did get a few queries as to streaming.) The streaming will be done using Google Hangouts; the URL to join the stream is https://meet.google.com/qjb-zbip-cpf <https://meet.google.com/qjb-zbip-cpf>. You do have to have a google id of some sort (gmail is fine) to join the streaming. When you access the stream, your request to join will be authorized. Please do not attempt to join before 1345 CET. The workshop itself will take place between 1400-1730 CET. The inbound audio and video stream will be disabled, so this will be a one-way outbound feed. However, there is a chat function so you can ask questions via the chat. Our plan is to take periodic pauses so the chat questions can be brought up and answered. If that proves impractical we will answer the chat questions after the workshop is over, so you’ll want to include an e-mail address for a response. Dave Thewlis Here’s the original post: Please note that this is NOT an IETF event. CalConnect <http://www.calconnect.org/> will host a Public Time Zone Workshop on Tuesday afternoon, February 5th, during its conference at Google in Zürich, Switzerland <http://www.calconnect.org/events/calconnect-xliv-february-4-8-2019>. The Time Zone Workshop will be Tuesday February 5th from 13:30 to 17:30 at the Google facility <http://www.calconnect.org/events/calconnect-xliv-february-4-8-2019#location>. This workshop will be focussed on the potential impact of EU Summer Time changes and how the changes might be mitigated; please see our news release <http://www.calconnect.org/news/2018/10/30/calconnect-calls-eu-reconsider-ti…>. The workshop is open to the public but you must register in advance. There is no fee to attend the workshop. Attendees are invited to stay for a Welcome Reception following the workshop. More information will be provided as planning continues. The workshop is intended for anyone who needs to plan and prepare for this and other TZ/DST changes, in particular representatives from governments, industries affected by tz changes (travel, financial, health, device manufacturers, etc.), organizations deploying tz data, and organizations maintaining and updating tz data. Please register for this event at https://www.eventbrite.com/e/eu-dst-timezone-change-public-workshop-tickets… <https://www.eventbrite.com/e/eu-dst-timezone-change-public-workshop-tickets…>. We invite anyone who is interested in or concerned by the pending changes and how time zone change information might better be distributed and implemented to attend. Dave Thewlis -- Dave Thewlis, Executive Director CalConnect - The Calendaring and Scheduling Consortium +1 707 840 9391 voice | +1 707 498 2238 mobile | +1 415 946 3454 fax http://www.calconnect.org <http://www.calconnect.org/> | Dave.Thewlis(a)calconnect.org <mailto:Dave.Thewlis@calconnect.org> _______________________________________________ calsify mailing list calsify(a)ietf.org https://www.ietf.org/mailman/listinfo/calsify

1 0

DST ends 2040 in Oracle database
by Joachim Damm Jan. 31, 2019

Jan. 31, 2019

Hello, we found one issue in the Oracle database that DST calculation is wrong from 2040 and beyond. I create a SR at Oracle and the Oracle support told me, that this behavior is from the IANA tzdata file and not from Oracle. My question is, if this is the case, where can I find the required information? If this is not the case, please let me also know to give the information to the Oracle support. I will appreciate your feedback regarding the information from the Oracle SR team! Mit freundlichen Grüßen / Kind Regards i.A. Joachim Damm Senior Database Consultant Systems Integration [cid:image001.jpg@01CF7F53.FD0881C0] Werum IT Solutions GmbH Wulf-Werum-Str. 3, 21337 Lüneburg, Germany T +49 4131 8900-515 F +49 4131 8900-20 Joachim.Damm(a)Werum.com<mailto:Joachim.Damm@Werum.com> www.werum.com<http://www.werum.com/> Geschäftsführer / Managing Directors: Rüdiger Schlierenkämper, Richard Nagorny, Hans-Peter Subel RG Lüneburg / Court of Jurisdiction: Lüneburg, Germany Handelsregisternummer / Commercial Register: HRB 204984 USt.-IdNr. / VAT No.: DE 116 083 850 Connect with us: [cid:image006.jpg@01D4B3D4.B9323120] <https://www.linkedin.com/company/werum> [cid:image007.jpg@01D4B3D4.B9323120] <https://twitter.com/werum> [cid:image008.jpg@01D4B3D4.B9323120] <http://www.vimeo.com/werum> [cid:image009.jpg@01D4B3D4.B9323120] <https://www.youtube.com/werum>

12 23

Re: [tz] DST ends 2040 in Oracle database
by Brian Inglis Jan. 31, 2019

Jan. 31, 2019

On 2019-01-31 15:25, Scott Nelson wrote: >> On Jan 31, 2019, at 4:17 PM, Brian Inglis wrote: >> Device expiration date is specified as ISO: >> https://www.ecfr.gov/cgi-bin/retrieveECFR?n=se21.8.801_118 >> "Title 21 → Chapter I → Subchapter H → Part 801 → Subpart A → §801.18 >> Title 21: Food and Drugs >> PART 801—LABELING >> Subpart A—General Labeling Provisions >> §801.18 Format of dates provided on a medical device label. >> ... >> (a) In general. Whenever the label of a medical device includes a printed >> expiration date, date of manufacture, or any other date intended to be brought >> to the attention of the user of the device, the date must be presented in the >> following format: The year, using four digits; followed by the month, using two >> digits; followed by the day, using two digits; each separated by hyphens. For >> example, January 2, 2014, must be presented as 2014-01-02. >> ... >> [78 FR 58818, Sept. 24, 2013]” > Yeah, but the exception is rather large: > (b) Exceptions. (1) A combination product that properly bears a National Drug > Code (NDC) number is not subject to the requirements of paragraph (a) of this > section. Why I restricted my statement to "Device expiration date" -- 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.

1 0

new NIST leap-seconds.list
by Chris Woodbury Jan. 31, 2019

Jan. 31, 2019

Thanks to Dr. Levine, NIST has a newer version of leap-seconds.list with an expiry of 28 Dec 2019. Hurrah!! (Note: I re-named it so I could see the different versions.) $ FIPS180 -f NIST_leap-seconds.3676924800.2019-01-31 -v -h Generated SHA digest matches file digest File name: NIST_leap-seconds.3676924800.2019-01-3 Original file name: leap-seconds.3676924800 Last modified: 31 Jan 2019 08:02:47 UTC Updated: 08 Jul 2016 00:00:00 UTC Expires: 28 Dec 2019 00:00:00 UTC #h 83c68138 d3650221 07dbbbcd 11fcc859 ced1106a $

1 0

Time Zone Standards
by Samah Kareem Jan. 31, 2019

Jan. 31, 2019

Hello All I want to ask about references, countries can change their time zone depending on, I want name of standards, guidelines if any. Regards Samah Kareem

3 2

Daylight saving in 2372
by Arthur David Olson Jan. 30, 2019

Jan. 30, 2019

In the "Star Trek: Deep Space Nine" episode "Paradise Lost," Captain Sisko, at Starfleet's San Francisco headquarters, mentions "19 hundred 47 hours P. S. T." Per one source*, theepisode is set in June 2372. Seems there's no daylight saving in San Francisco in 2372, but the "standard" "S" is still used. @dashdashado _ *http://www.johnstonsarchive.net/startrek/st-episodes-1.html

5 5

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

Jan. 30, 2019

Something else, as it may not be obvious. The comments and white space do not contribute to the FIPS 180 digest and they may all be edited with impunity. This is the primary reason that using the date in the comments as data is such a bad idea. There's absolutely is no way to detect any changes or tampering. So, if someone doesn't like the fact that I put in the sign of the TAI-UTC delta T (or the MJD) as comments, edit it out. (Or any line starting with # (except the timestamps) for that matter.) Paul, your "corrected" leap-seconds.list file is an attachment.

1 0