Proposal: UTC and only UTC, please
Can I propose strongly that we please use UTC, and only UTC, consistently for all timing purposes in the IGC. If UTC is used, then all members can be clear on what this means for them, and there is no need for timezone translations to be provided. (In my experiences, translations do not help, but only risk introducing errors and confusion.) The one exception is for physical meetings where local time should be used of course, along with UTC equivalent for info of remote participants. Thanks. ________________________________________________________________________ Paul Wilson, Director-General, APNIC <dg@apnic.net> http://www.apnic.net +61 7 3858 3100 See you at APNIC 38! http://conference.apnic.net/38
I support Paul's "time use proposal" - Russ On Jul 23, 2014, at 6:00 PM, Paul Wilson <pwilson@apnic.net> wrote:
Can I propose strongly that we please use UTC, and only UTC, consistently for all timing purposes in the IGC.
If UTC is used, then all members can be clear on what this means for them, and there is no need for timezone translations to be provided. (In my experiences, translations do not help, but only risk introducing errors and confusion.)
The one exception is for physical meetings where local time should be used of course, along with UTC equivalent for info of remote participants.
Thanks.
________________________________________________________________________ Paul Wilson, Director-General, APNIC <dg@apnic.net> http://www.apnic.net +61 7 3858 3100
See you at APNIC 38! http://conference.apnic.net/38
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
I do also - to be honest I automatically assumed that the 'last call for comments by XX CET' was some US time zone that I had no idea about, so looked it up on timeanddate.com and found that it was Central European Time, ie UTC+1. So only use local time for F2F meetings (as well as UTC), with the local time always expressed in full, ie US CDT, or AEST etc so there really is no room for confusion. Regards Narelle -----Original Message----- From: internal-cg-bounces@icann.org [mailto:internal-cg-bounces@icann.org] On Behalf Of Russ Mundy Sent: Thursday, 24 July 2014 8:43 AM To: Paul Wilson Cc: ICG Internal Subject: Re: [Internal-cg] Proposal: UTC and only UTC, please I support Paul's "time use proposal" - Russ On Jul 23, 2014, at 6:00 PM, Paul Wilson <pwilson@apnic.net> wrote:
Can I propose strongly that we please use UTC, and only UTC, consistently for all timing purposes in the IGC.
If UTC is used, then all members can be clear on what this means for them, and there is no need for timezone translations to be provided. (In my experiences, translations do not help, but only risk introducing errors and confusion.)
The one exception is for physical meetings where local time should be used of course, along with UTC equivalent for info of remote participants.
Thanks.
________________________________________________________________________ Paul Wilson, Director-General, APNIC <dg@apnic.net> http://www.apnic.net +61 7 3858 3100
See you at APNIC 38! http://conference.apnic.net/38
On 24 jul 2014, at 04:51, Narelle Clark <narelle.clark@accan.org.au> wrote:
So only use local time for F2F meetings (as well as UTC), with the local time always expressed in full, ie US CDT, or AEST etc so there really is no room for confusion.
I actually think expressing local time in full this way is a bad idea, and the reason is that not many individuals that arrange a meeting say in Stockholm, Sweden, but do not live there, know what timezone Stockholm is in at the time of the meeting (think of changes in daylight savings in the middle of the meeting). Because of this I first of all strongly encourage time in UTC. That I agree with. Secondly, for local meetings, say in Stockholm, the time is to be given as "local time in Stockholm", i.e. very explicit when everyone know where the meeting is. For example for the schedule for the day if the meeting is there. No guessing on what timezone it is please! Patrik
Oh yeah! And in particular no EDT, PDT, CET, CEST... Wolf-Ulrich Sent from my personal phone
Am 24.07.2014 um 00:00 schrieb Paul Wilson <pwilson@apnic.net>:
Can I propose strongly that we please use UTC, and only UTC, consistently for all timing purposes in the IGC.
If UTC is used, then all members can be clear on what this means for them, and there is no need for timezone translations to be provided. (In my experiences, translations do not help, but only risk introducing errors and confusion.)
The one exception is for physical meetings where local time should be used of course, along with UTC equivalent for info of remote participants.
Thanks.
________________________________________________________________________ Paul Wilson, Director-General, APNIC <dg@apnic.net> http://www.apnic.net +61 7 3858 3100
See you at APNIC 38! http://conference.apnic.net/38
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
Paul+1. UTC only. Kuo Wu Paul Wilson <pwilson@apnic.net> 於 2014/7/24 6:00 寫道：
Can I propose strongly that we please use UTC, and only UTC, consistently for all timing purposes in the IGC.
If UTC is used, then all members can be clear on what this means for them, and there is no need for timezone translations to be provided. (In my experiences, translations do not help, but only risk introducing errors and confusion.)
The one exception is for physical meetings where local time should be used of course, along with UTC equivalent for info of remote participants.
Thanks.
________________________________________________________________________ Paul Wilson, Director-General, APNIC <dg@apnic.net> http://www.apnic.net +61 7 3858 3100
See you at APNIC 38! http://conference.apnic.net/38
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
Yes please! Cheers Keith On 24/07/2014 10:00 a.m., Paul Wilson wrote:
Can I propose strongly that we please use UTC, and only UTC, consistently for all timing purposes in the IGC.
If UTC is used, then all members can be clear on what this means for them, and there is no need for timezone translations to be provided. (In my experiences, translations do not help, but only risk introducing errors and confusion.)
The one exception is for physical meetings where local time should be used of course, along with UTC equivalent for info of remote participants.
Thanks.
________________________________________________________________________ Paul Wilson, Director-General, APNIC <dg@apnic.net> http://www.apnic.net +61 7 3858 3100
See you at APNIC 38! http://conference.apnic.net/38
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
participants (7)
-
Keith Davidson -
Narelle Clark -
Patrik Fältström -
Paul Wilson -
Russ Mundy -
Wolf-Ulrich.Knoben＠t-online.de -
Wu Kuo-Wei