[Gnso-newgtld-wg] [Gnso-newgtld-lead] - Time Shift Analysis

Fri Oct 28 05:07:51 UTC 2016

Well, it was bound to happen – with so many different email list available for this WG, someone was going to send a message to the wrong address. Unfortunately, it was me! However, I think it’s beneficial to get responses from so many different voices, so perhaps it’s a good mistake. For those considering weighing in, I’ll provide a bit of additional context. The default is to adjust all GNSO working group schedules when daylight savings adjustments having taken place in the majority of places where it’s observed, which for this year, will be 6 November. The change results in the UTC times being adjusted +1 hour (e.g., 0300 UTC becomes 0400 UTC, 1500UTC becomes 1600 UTC, etc.). If the region you’re in observes daylight savings, this would mean the local time for the meeting would remain unchanged (e.g., a meeting at 12:00 pm would continue to be at 12:00 pm). Of course, not all countries or regions observe daylight savings, which is why this debate was taking place within the leadership team.

The main concern with this WG being an outlier to following this practice is that we increase the risk of conflicts with other GNSO meetings (including Stakeholder and Constituency meetings potentially). As a result, the staff recommendation has been, and remains, to follow the practice that other WGs are following. However, it is ultimately up to WG and its leadership to make the decision.

Please feel free to give me a hard time for my inadequate email skills in Hyderabad L

Best,

Steve

From: <gnso-newgtld-wg-bounces at icann.org> on behalf of Cecilia Smith <Cecilia.Smith at fox.com>
Date: Thursday, October 27, 2016 at 8:12 PM
To: Karen Day <Karen.Day at sas.com>, Cheryl Langdon-Orr <langdonorr at gmail.com>
Cc: "gnso-newgtld-wg at icann.org" <gnso-newgtld-wg at icann.org>
Subject: Re: [Gnso-newgtld-wg] [Gnso-newgtld-lead] - Time Shift Analysis

+1

From: <gnso-newgtld-wg-bounces at icann.org> on behalf of Karen Day <Karen.Day at sas.com>
Date: Thursday, October 27, 2016 at 7:09 PM
To: Cheryl Langdon-Orr <langdonorr at gmail.com>
Cc: "gnso-newgtld-wg at icann.org" <gnso-newgtld-wg at icann.org>
Subject: Re: [Gnso-newgtld-wg] [Gnso-newgtld-lead] - Time Shift Analysis

I will add my voice to the "do not adjust UTC" chorus here.

Best,

Karen

Sent from my iPad

On Oct 27, 2016, at 9:58 PM, Cheryl Langdon-Orr <langdonorr at gmail.com> wrote:

No Surprise  I support Avri as well *after all* Like Avri I have been also saying exactly this for years now ;-) 

Anyway  I am building my movement  getting more support today from other participants in other meetings So if you keep hearing  "just stick to UTC" a lot more in the near future  this is why...

Cheryl Langdon-Orr ...  (CLO)

about.me/cheryl.LangdonOrr

On 28 October 2016 at 07:06, theo geurts <gtheo at xs4all.nl> wrote:

100% with Avri on this.

UTC is a time saver ;)

Theo 

On 27-10-2016 21:30, avri doria wrote:

Hi,

I am in favor of just sticking with UTC and not bothering with the
complexities of who is going in or out of DST at any time.  I suggest
that for all WGs. and will suggest it for any group I am in.

avri

On 27-Oct-16 15:07, Steve Chan wrote:

Hello All,

I did some basic analysis to try and understand the impact of staying
on the same UTC time versus moving 1 hour forward on UTC (e.g., the
1500 UTC would be 1600 UTC). I’d say it’s inconclusive and at least to
me, not terribly surprising – it helps in some cases and hurts in
others. When there are early meetings, adding an hour to the UTC helps
and when it’s evening or middle of the night, it generally makes
things worse. Unfortunately, I don’t think this gives us a clear path
forward, but it at least lets us see how it affects this particular WG
in certain regions of the world. I’ve highlighted the most difficult
meetings times in red.

Note, this analysis would be as of 7 November, so to the extent that
timeanddate.com accurately captures what regions observe daylight
savings, that factor should be taken into account.

Best,

Steve

*Steven Chan*

Sr. Policy Manager

*ICANN*

12025 Waterfront Drive, Suite 300

Los Angeles, CA 90094-2536

steve.chan at icann.org <mailto:steve.chan at icann.org>

direct: +1.310.301.3886

mobile: +1.310.339.4410

tel: +1.310.301.5800

fax: +1.310.823.8649

Find out more about the GNSO by taking our interactive courses
<applewebdata://310CAD3E-E244-4690-A938-C2655DD44BDE/learn.icann.org/courses/gnso> and
visiting the GNSO Newcomer pages
<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers>.

Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO

Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/

http://gnso.icann.org/en/

_______________________________________________
Gnso-newgtld-wg mailing list
Gnso-newgtld-wg at icann.org
https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

_______________________________________________
Gnso-newgtld-wg mailing list
Gnso-newgtld-wg at icann.org
https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg

_______________________________________________
Gnso-newgtld-wg mailing list
Gnso-newgtld-wg at icann.org
https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg

_______________________________________________
Gnso-newgtld-wg mailing list
Gnso-newgtld-wg at icann.org
https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20161028/349c5d6d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2018 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20161028/349c5d6d/smime-0001.p7s>