[Gnso-newgtld-wg] Meeting schedule was Re: Proposal to Extend CC2 Deadline

Michele Neylon - Blacknight michele at blacknight.com
Tue May 2 02:49:25 UTC 2017 

Jeff

Thanks for the detailed outline of the times and their impacts. I think you're being very generous and possibly ignoring people who want to achieve a reasonable work / life balance ;-)
Regards
Michele

Mr Michele Neylon
Blacknight Hosting & Domains
http://www.blacknight.host/
http://www.mneylon.social
Sent from mobile so typos and brevity are normal

On 1 May 2017, at 22:37, Jeff Neuman <jeff.neuman at comlaude.com<mailto:jeff.neuman at comlaude.com>> wrote:

Kavouss,

I want to assure you that in our scheduling calls, there is absolutely no mal-intent or any desire to drive away participation of the GAC.  In fact, we are trying to do the opposite.  As you know, scheduling calls where everyone can attend has been one of our biggest issues and one for which there just is no really good solution.  We also have to schedule calls out a number of weeks in advance so that everyone can plan their schedules accordingly.

ICANN has given us three time slots which do not conflict with other working groups, CCWGs, WS2 and other calls that regularly take place.  The three times we have been given are:  15:00 UTC, 20:00 UTC and 3:00 UTC.   We can again explore whether there are other time slots available, but we have already tried on numerous occasions.

That said, on a personal note, I kindly request that you please not take this out on the PDP leadership team and you have some patience with us.  Like you, we are all volunteering our time and resources to try and do the best possible work that we can.  We are all trying to do the right thing and Avri, the Work Team Leaders and ICANN staff are doing the best that we can to accommodate everyone.  But that is not always possible and we are all having to make sacrifices.

Below, I provide a sample of how certain cities (in which I believe we have participants), are impacted by the rotating time schedules.

At 15:00 UTC currently, it is the following times in the following cities:

1.  New York, USA – 11:00 am
2.  Los Angeles, USA –8:00 am
3.  London, UK – 4:00 pm
4.  Geneva, Switzerland – 5:00 pm
5.  Moscow, Russia – 6:00 pm
6.  Beijing, China – 11:00pm
7.  Tokyo, Japan –12:00 am (midnight)
8.  Melbourne, Australia – 1:00 am
9.  Rio, Brazil – 10:00 am
10.  Buenos Aires, Argentina  : -- 12:00 pm (noon)
11.  Tehran, Iran – 7:30 pm

At 20:00 UTC, the following

1.  New York, USA – 4:00 pm
2.  Los Angeles, USA – 1:00 pm
3.  London, UK – 9:00 pm
4.  Geneva, Switzerland – 10:00 pm
5.  Moscow, Russia – 11:00 pm
6.  Beijing, China – 4:00 am
7.  Tokyo, Japan – 5:00 am
8.  Melbourne, Australia – 6:00 am
9.  Rio, Brazil – 3:00 pm
10.  Buenos Aires, Argentina  : -- 5:00 pm
11.  Tehran, Iran – 12:30 am

And 03:00 UTC

1.  New York, USA – 11:00 pm
2.  Los Angeles, USA – 8:00 pm
3.  London, UK – 4:00 am
4.  Geneva, Switzerland – 5:00 am
5.  Moscow, Russia – 6:00 am
6.  Beijing, China – 11:00 am
7.  Tokyo, Japan –12:00 pm (noon)
8.  Melbourne, Australia – 1:00 pm
9.  Rio, Brazil – 10:00 pm
10.  Buenos Aires, Argentina  : 12:00 am (midnight)
11.  Tehran, Iran – 7:30 am

If you look at the highlighted areas and you assume that 11:00 pm – 6:00 am has pain in attending, then you can see almost everyone has some pain.   Those in Russia, China, Japan and Australia feeling the pain 2 out of every 3 calls.

Moving this to 04:00 UTC, in addition to the time conflict with WS2, would be worse for those on the East Coast of the US, would move Moscow out of the pain zone, but would put those in Rio in the pain zone.

1.  New York, USA – 12:00 am (midnight)
2.  Los Angeles, USA – 8:00 pm
3.  London, UK – 5:00 am
4.  Geneva, Switzerland – 6:00 am
5.  Moscow, Russia – 7:00 am
6.  Beijing, China – 12:00 pm
7.  Tokyo, Japan –1:00 pm
8.  Melbourne, Australia – 1:00 pm
9.  Rio, Brazil – 11:00 pm
10.  Buenos Aires, Argentina  : 1:00 am (midnight)
11.  Tehran,  Iran – 8:30 am

As you know, calls are recorded and transcripts are provided for any calls that have to be missed.  Therefore, hopefully everyone can be caught up on the materials.  We also strongly encourage participation on the e-mail lists.

I hope this e-mail, these examples, and my explanation help you understand a little better our thought processes behind the schedule.  Thank you for your participation in the SubPro PDP and we truly hope you continue to stay involved.  Our success is due in large part to those, like you, who consistently contribute to our work and show such dedication and passion for these issues.

Best regards,


Jeffrey J. Neuman
Senior Vice President |Valideus USA | Com Laude USA
1751 Pinnacle Drive, Suite 600
Mclean, VA 22102, United States
E: jeff.neuman at valideus.com<mailto:jeff.neuman at valideus.com> or jeff.neuman at comlaude.com<mailto:jeff.neuman at comlaude.com>
T: +1.703.635.7514
M: +1.202.549.5079
@Jintlaw


From: gnso-newgtld-wg-bounces at icann.org<mailto:gnso-newgtld-wg-bounces at icann.org> [mailto:gnso-newgtld-wg-bounces at icann.org] On Behalf Of Kavouss Arasteh
Sent: Monday, May 1, 2017 8:41 PM
To: avri doria <avri at apc.org<mailto:avri at apc.org>>; Steve Chan <steve.chan at icann.org<mailto:steve.chan at icann.org>>; James M. Bladel <jbladel at godaddy.com<mailto:jbladel at godaddy.com>>; Thomas.Schneider at bakom.admin.ch<mailto:Thomas.Schneider at bakom.admin.ch>; mark.carvell at culture.gov.uk<mailto:mark.carvell at culture.gov.uk>; fin.pet at erst.dk<mailto:fin.pet at erst.dk>; Olga Cavalli <olgacavalli at gmail.com<mailto:olgacavalli at gmail.com>>; <Jorge.Cancio at bakom.admin.ch<mailto:Jorge.Cancio at bakom.admin.ch>> <jorge.cancio at bakom.admin.ch<mailto:jorge.cancio at bakom.admin.ch>>; gac at gac.icann.org<mailto:gac at gac.icann.org>; gnso-newgtld-wg at icann.org<mailto:gnso-newgtld-wg at icann.org>
Subject: Re: [Gnso-newgtld-wg] Meeting schedule was Re: Proposal to Extend CC2 Deadline

Avri,
I  check the schedule of CCWG Accountability for the month of May and found that one Tuesday 16 May , they have Jurisdiction meeting at 05,00 UTC thus other Tuesday they do niot have any meeting at that time.
I therefore request to be collaborative and change the timing of your General Meeting to 04,00 UTC and ask CCWG Jurisdiction to shift their meeting by Half an hour to start at 05,30 not to have any clash with your meeting .As they meet for only 60 minutes still they end by 06,30 UTC at that only one meeting per night.
If you insist , I interpret that this is an effort to EXCLUDE GAC TO ATTEND THE PDP.
I will formally announce that to the responsible group.
You and staff need to kindly work it out in consultation with Bernie.
I insist on that.
Regards
Kavouss

2017-05-01 20:59 GMT+02:00 avri doria <avri at apc.org<mailto:avri at apc.org>>:
Dear Kavouss,

I have received heard your requests and seen your complaint to the
chairs of the GNSO and the GAC.

Staff reviewed our meeting time and found that 4 UTC was not possible,
especially for our full meeting as that is a 90 minute meeting that
would interfere with the WS2 meetings that are scheduled in the 5 UTC
time frame. We have been very careful to keep our scheduling out of the
WS2 time tracks as that was one of the original concerns that people had
in establishing our rotating scheduling. The other goal we had was
consistency in the rotating times at which we held meetings as much as
possible.  Finally the point was the sharing of discomfort among the
residents of various time frames which was accepted by the WG at the
beginning of this process.

At this point you are the only one with this specific request.  Should
there be a consensus in the group that we need to review and possibly
redo the rotating schedule of meetings, I will ask the staff to help us
find a new solution that is acceptable to a consensus of the
participants in the WG.  I will ask that the issue be added as AOB to
our full meeting to find out whether there is consensus on the need to
reschedule our meetings.

Thank you

Avri


On 01-May-17 13:21, Arasteh wrote:
> Avri
> Once again, I reiterate-my position which was supported by many European residents that the window of 03,00 UTC is a painful window for meeting .
> I sincerely and respectfully request you to move it to 04,00 UTC which does not make a big change for Asia Pacific people. Failure to do that is a clear sign to exclude People from Europe to attend
> Regards
> Kavouss
>
> Sent from my iPhone
>
>> On 20 Apr 2017, at 00:18, avri doria <avri at apc.org<mailto:avri at apc.org>> wrote:
>>
>> Hi,
>>
>> I want to append a comment to this.  While I fully support the
>> extension, I want to encourage people to submit their comments as soon
>> as they can.  As most of you know the sub teams are currently working on
>> all these issues and the sooner they get input, the better.  Everyone in
>> the leadership group is waiting with bated breath and is eager to see
>> the answers that are ready.  Also want to note, that there are many
>> questions, and there is no barrier to submitting multiple responses
>> dealing the variety of questions.  Also those who submit early will have
>> the opportunity for making further comments should they think of new
>> elements to add to their answers.
>>
>> So please, though we are recommending an extension, please feel free to
>> submit the work that is already ready.
>>
>> Thanks
>>
>> avri
>>
>>
>>
>>> On 18-Apr-17 05:11, Jeff Neuman wrote:
>>>
>>> All,
>>>
>>>
>>>
>>> Last week the Avri and I received a formal request from the
>>> Governmental Advisory Committee to “consider an extension of the
>>> deadline for public comments to the Community Comment 2 (CC2)
>>> questionnaire.”  In light of the extensive nature of the questionnaire
>>> as well as the desire to get as many responses as possible, Avri and I
>>> are inclined to agree to this request.  In order to be fair, we
>>> believe the extension should be applied to everyone, not just the GAC.
>>>
>>>
>>>
>>> Working backwards, it is our desire to have a summary of all of the
>>> public comments to discuss at ICANN59 at the end of June.  The
>>> document deadline for that meeting is 15 business days prior to the
>>> meeting (beginning of June).  In order to give staff some time to
>>> compile the summary in time for the document deadline, we are
>>> proposing *May 22, 2017* as the new date for comments to be due.  This
>>> would be a 3 week extension for the entire community.
>>>
>>>
>>>
>>> I know this is asking for quick turnaround, but please let us know by
>>> no later than *April 20^th *if you have any strong objections to this
>>> proposal.  Otherwise, we will let the community know about the
>>> extension on April 21^st .
>>>
>>>
>>>
>>> Best regards,
>>>
>>>
>>>
>>> *Jeffrey J. Neuman*
>>>
>>> *Senior Vice President *|*Valideus USA***| *Com Laude USA*
>>>
>>> 1751 Pinnacle Drive, Suite 600
>>>
>>> Mclean, VA 22102, United States
>>>
>>> E: _jeff.neuman at valideus.com<mailto:jeff.neuman at valideus.com> <mailto:jeff.neuman at valideus.com<mailto:jeff.neuman at valideus.com>>_or
>>> _jeff.neuman at comlaude.com<mailto:jeff.neuman at comlaude.com> <mailto:jeff.neuman at comlaude.com<mailto:jeff.neuman at comlaude.com>>_
>>>
>>> T: +1.703.635.7514<tel:%2B1.703.635.7514>
>>>
>>> M: +1.202.549.5079<tel:%2B1.202.549.5079>
>>>
>>> @Jintlaw
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Gnso-newgtld-wg mailing list
>>> Gnso-newgtld-wg at icann.org<mailto: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<mailto: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<mailto: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/20170502/a45f3d99/attachment-0001.html>

More information about the Gnso-newgtld-wg mailing list