First, I note the same issue as George.  Going back to Mary's original email, the instructions are ambiguous.  I abstained from participating in the poll as I'm not in the APAC region, based on Mary's original note "In particular, we invite members based in Singapore, India, Japan, Hong Kong, China, Australia and other areas in the APAC region to weigh in."  I suppose that "In particular" can be interpreted in a number of different ways.  If it was intended that everyone should participate, but that extra outreach or encouragement was being directed at APAC participants, then it is open to all, and everyone should be encouraged to participate.  If it was intended to be only for APAC participants, then that should be made clear, and the poll should be restarted with only APAC participants weighing in.  The invitation was surely well-intentioned, but we've ended up with something that's neither limited nor comprehensive.

Second, I've attached a "Time and Date" website printout showing the hourly clock, which can be found (in easier-to-interpret color) at https://www.timeanddate.com/worldclock/meetingtime.html?iso=20180328&p1=137&p2=179&p3=136&p4=87&p5=2&p6=44&p7=236&p8=248&p9=240&p10=264.  This reveals the dilemma.

If we want a time that is not too painful for the entirety of APAC, the only decent hours are 0600 to 0900 UTC (when it's 8 am to 11 am in Amman and 7 am to 10 pm in Wellington).  This is tolerable for London (one hour behind Amman), decent for the rest of Europe, but really bad for North and South America (where this span is 11 pm to 2 am in LA, 2 am to 5 am in DC and 3 am to 6 am in BA).

Georges suggested 10 am NYC time (1400 UTC).  This is decent for Western and Central Asia but it's 10 pm in Singapore, and worse from there -- 11 pm in Tokyo, 1 am in Sydney and 3 am in Wellington.

The current time of 0300 UTC is deadly for Europe, Africa and the Middle East, getting tolerable around Abu Dhabi and then falling basically into the work day from Mumbai to Wellington.

The staff-suggested alternatives of 2200 and 2300 UTC are good for most of Australia and for New Zealand, and also for North and South America.  They are deadly for Europe, Africa the Middle East and any part of Asia up to and including Singapore/Hong Kong.

Long story short, we can accommodate APAC and Europe at the expense of the Americas (e.g, with 0800 UTC), or we can accommodate the Eastern part of APAC (between 2200 and 0300 and possibly some of the Americas at the earlier end) at the expense of Europe and the Western parts of APAC.

One last point -- rather than generically looking at time zones, it would be preferable to look at the participants' time zones.  While this might not change the result, it might identify a few time zones that don't need to be considered.

Greg



On Sun, Mar 25, 2018 at 8:37 AM, George Kirikos <icann@leap.com> wrote:
Many of the folks who've already voted in the Doodle poll don't appear
to be in Singapore, India, Japan, Hong Kong, China, Australia or other
areas in the APAC region:

https://doodle.com/poll/zwpqnnz45yw74x3m

Is the poll intended to be open to everyone?

Ultimately, attendance at calls is meaningful only to those who
actually intend to actively participate (i.e. speak, type in the
chatroom, ask questions or otherwise communicate in some other manner
during the call itself). If one doesn't actively participate,
listening to the recording or reading the transcript later is
essentially the same as being an observer of the live call (and might
actually be more time efficient, as one can use software to playback
MP3 audio at double speed, or read even faster).

Sincerely,

George Kirikos
416-588-0269
http://www.leap.com/



On Thu, Mar 22, 2018 at 2:34 PM, Mary Wong <mary.wong@icann.org> wrote:
> Dear Working Group members,
>
>
>
> As we restart the meetings cycle following ICANN61, the Working Group
> co-chairs would like to seek your feedback concerning an appropriate time
> for the 4th rotational Working Group call (i.e. generally the last meeting
> of the month). As you know, our practice has been to try to hold this call
> at a time that will allow our Asia-Pacific (APAC) based members to attend,
> and that time to date has been 0300 UTC on the last Thursday of each month.
>
>
>
> Having used this rotation for some time, the Working Group co-chairs wish to
> find out if an alternative time that will still allow APAC member
> participation may be more suitable. Based on the geographical distribution
> of our current membership, staff has suggested that a workable alternative
> time might be either 2200 UTC or 2300 UTC on Wednesdays.
>
>
>
> We have created a Doodle poll where you may indicate your belief as to which
> of these times (including the current arrangement) will work best. In
> particular, we invite members based in Singapore, India, Japan, Hong Kong,
> China, Australia and other areas in the APAC region to weigh in as the aim
> of this poll is to facilitate your continued participation in Working Group
> calls: https://doodle.com/poll/zwpqnnz45yw74x3m.
>
>
>
> Finally, please note that as some of our Sub Teams will be continuing to
> meet for the next two weeks or so, our expectation is that the first
> post-ICANN61 APAC time zone-friendly call will not take place before 25
> April 2018.
>
>
>
> Thanks and cheers
>
> Mary, Julie, Ariel & Berry
>
>
> _______________________________________________
> gnso-rpm-wg mailing list
> gnso-rpm-wg@icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rpm-wg
_______________________________________________
gnso-rpm-wg mailing list
gnso-rpm-wg@icann.org
https://mm.icann.org/mailman/listinfo/gnso-rpm-wg