ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [council] GAC Liaison - Update

  • To: Phil Corwin <psc@xxxxxxxxxxx>, Paul McGrady <policy@xxxxxxxxxxxxxxx>, "'GNSO Council List'" <council@xxxxxxxxxxxxxx>
  • Subject: Re: [council] GAC Liaison - Update
  • From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Date: Tue, 7 Jun 2016 16:11:14 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=jbladel@xxxxxxxxxxx;
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secureservernet.onmicrosoft.com; s=selector1-godaddy-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Ec3L0ifVL793GnObAV/XJ/x7zEtT/GzQUgG6k/VPr0Y=; b=EG8edlorsqmm76FOh/dzhpVreuiIcS1uhtwt8msdHFG+t097NonzRCO/6e6g0y/a4Wsm7lSPERX0hQ1GF6RMIcMtvOnV1SJ+5jCRmM6aXVfEhOzUtcDrHx8jbCycMrSMDTC2RgJLJzQ28LdXkAoX6laKgzNuPeS2omdILQpz8E4=
  • In-reply-to: <8E84A14FB84B8141B0E4713BAFF5B84E20F6D6B8@Exchange.sierracorporation.com>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <D37B8F8F.C44A0%jbladel@godaddy.com> <03d201d1c0ae$d37b9830$7a72c890$@paulmcgrady.com> <8E84A14FB84B8141B0E4713BAFF5B84E20F6D6B8@Exchange.sierracorporation.com>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
  • Thread-index: AQHRwF0uJSCZl9m+JUarTSSVBRdGv5/d3OoAgAAudoD//85qgA==
  • Thread-topic: [council] GAC Liaison - Update
  • User-agent: Microsoft-MacOutlook/14.5.6.150930

Hi Phil & Paul -

We did receive some interest in the role, but significantly less so than when 
the Liaison was created two years ago.

Also, none of the applicants had any previous experience with the GNSO Council 
or with PDP working groups (chair or participant), which were key 
considerations in the selection process.  Additionally, we received some verbal 
indications of interested candidates, but these were withdrawn prior to the 
deadline. (Most likely due to the irregular term, but I also note Phil's point 
about the time commitment during ICANN meetings.)

Apologies if this sounds like I'm being coy, but I am attempting to address 
your questions without divulging too many details about the applicants, should 
they wish to resubmit in the fall.

Hope this helps.

Thanks-

J.



From: Phil Corwin <psc@xxxxxxxxxxx<mailto:psc@xxxxxxxxxxx>>
Date: Tuesday, June 7, 2016 at 9:08
To: Paul McGrady <policy@xxxxxxxxxxxxxxx<mailto:policy@xxxxxxxxxxxxxxx>>, James 
Bladel <jbladel@xxxxxxxxxxx<mailto:jbladel@xxxxxxxxxxx>>, GNSO Council List 
<council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>>
Subject: RE: [council] GAC Liaison - Update

I'm inclined to agree with the proposed timetable, but like Paul would like a 
bit more data. In particular, does the term "underwhelming" denote no 
applications?

Also, it may not just be a timing issue, but the fact that the Liaison has to 
commit to spend so much time in GAC meetings when attending an ICANN meeting in 
which their primary interest may be in other discussions going on 
simultaneously.

Best to all, Philip

Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/Cell

Twitter: @VlawDC

"Luck is the residue of design" -- Branch Rickey

From: owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx> 
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Paul McGrady
Sent: Tuesday, June 07, 2016 7:22 AM
To: 'James M. Bladel'; 'GNSO Council List'
Subject: RE: [council] GAC Liaison - Update

Hi James,

Before opining, can we have the full data set?  Please let us know who 
expressed interest.  Thanks!

Best,
Paul



From:owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx> 
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of James M. Bladel
Sent: Monday, June 06, 2016 8:38 PM
To: GNSO Council List
Subject: [council] GAC Liaison - Update

Dear Council Colleagues -

Recently we closed the nomination period for candidates interested in being 
considered for the role of GNSO Liaison to the GAC.  Unfortunately, the 
response from the GNSO community was underwhelming.  The Vice Chairs and I 
believe that this may be at least partly attributable to the timing of the 
announcement, as more candidates could be interested in the role if it 
coincided with the terms of other elected and appointed positions, which is the 
conclusion of the AGM in Hyderabad.

Therefore, with this in mind, I'd like to propose that we postpone the 
selection of a new GNSO - GAC Liaison until later in the fall, with the (rough) 
timeline listed below.  It is expected that the additional time will generate 
renewed attention to the role, additional expressions of interest from 
prospective candidates, and permanently align the term of this position with 
that of other terms, including most Councilors.

Please let me know if you have any concerns or objections to this approach.  On 
a related note, Mason Cole has graciously agreed to stay on a few extra months 
to ensure continuity.  Thank you, Mason.

Thanks-

J.

________________________________

Nominations Accepted for Candidates:  1 OCT 2016
Council Chairs consider candidates and notify first choice  20 OCT
Chairs submit motion to Council by 29 OCT for consideration during Council 
meeting on 8 NOV
GAC Leadership notified of new Liaison by 9 NOV
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7497 / Virus Database: 4568/12262 - Release Date: 05/19/16
Internal Virus Database is out of date.


<<< Chronological Index >>>    <<< Thread Index >>>