RE: [council] Update on planning for Helsinki

["Paul McGrady" <policy@xxxxxxxxxxxxxxx>]

Thanks James.

 

IPC Leadership has asked for time for C's and SG's to meet, so hopefully,
that can be worked into the calendar.

 

As far as dinner goes, either are fine with me.

 

Best,

Paul

 

 

 

From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On
Behalf Of James M. Bladel
Sent: Monday, April 25, 2016 08:20 PM
To: Austin, Donna; council@xxxxxxxxxxxxxx
Subject: Re: [council] Update on planning for Helsinki

 

Donna -

Thank you for taking the lead on this.  In the last few weeks, planning for
Meeting B has become almost as controversial as most policy topics.  You've
outlined a solid foundation for the GNSO to focus on Policy Work in
Helsinki, and please keep us updated as the afternoon cross-community topics
are finalized.

 

Council Colleagues-

It would be good to know if any SGs/Cs are planning break-out sessions of
their own, like an abbreviated Constituency Day. If you like we can ask that
these be included in the general calendar.    

 

Also, Ed has volunteered (thanks!) to work with Glen on planning a dinner
for our group in Helsinki, with the most likely candidates being Sunday (26
JUN) or Monday (27 JUN). My personal preference would be to gather on Sunday
evening, but not if it means we are missing several Councilors.  Therefore,
could everyone please indicate whether your travel schedules will allow
dinner on Sunday, or wether we should try for Monday?

 

Thanks-

 

J.

 

 

From: <owner-council@xxxxxxxxxxxxxx> on behalf of "Austin, Donna"
<Donna.Austin@xxxxxxxxxxx>
Date: Monday, April 25, 2016 at 10:55 
To: GNSO Council List <council@xxxxxxxxxxxxxx>
Subject: [council] Update on planning for Helsinki

 

All

 

A quick update on planning for Helsinki. A Planning Committee has been
established to primarily develop the schedule for the meeting in Helsinki
27-30 June 2016. Attached is the current draft schedule including for the
GNSO. Given Meeting B is intended to be an opportunity to progress policy
development efforts, most of the GNSO schedule has been carved out for four
policy efforts, namely:

.       Next Generation gTLD Registration Directory Service (4 hours); 

.       New gTLDs Subsequent Procedures (3.25 hours); 

.       Review of all Rights Protection Mechanisms in New gTLDs (2 hours);
and

.       IGO-INGO Access to Curative Rights Protection Mechanisms (2 hours).

 

You'll also see that time has been allocated for a Council Meeting, a
Council Prep Session, Council Bilateral Meeting Requests, and a Council Wrap
Up session. There is also time set aside for the discussion of other topics
on Monday-once the full agenda is locked down we can review to understand
what topics will require attention. It may also be possible/necessary to
schedule some of these topics in parallel; however, they would not conflict
with PDP or Council sessions. The topics are consistent with those
previously identified by the Council.

 

The Planning Committee is in the process of trying to decide what topics
should be Cross-Community Discussions, and I provided input on behalf of the
GNSO Council on a number of topics that Councilors had identified. There
were 12 topics identified in total and it is not clear at this time what
topics will be selected. It is hoped that some of the PDP efforts will
become topics identified for Cross Community Discussion and in that event
the GNSO Schedule will be adjusted accordingly.

 

This is a work in progress with still a ways to go. 

 

Let me know if you have any questions.

 

Thanks

 

Donna

 

Donna Austin:Neustar, Inc.
Policy and Industry Affairs Manager

Cell:+1.310.890.9655 Email:  <mailto:donna.austin@xxxxxxxxxxx>
donna.austin@xxxxxxxxxxx

 

  _____  

The information contained in this e-mail message is intended only for the
use of the recipient(s) named above and may contain confidential and/or
privileged information. If you are not the intended recipient you have
received this e-mail message in error and any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you have
received this communication in error, please notify me immediately and
delete the original message.

Follow Neustar:   cid:image001.png@01CC3CD3.5F595DC0
<http://www.facebook.com/neustarinc> Facebook
cid:image002.png@01CC3CD3.5F595DC0  <http://www.linkedin.com/company/5349>
LinkedIn   cid:image003.png@01CC3CD3.5F595DC0
<http://www.twitter.com/neustar> Twitter

P Please consider the environment before printing this e-mail.