RE: [council] Proposed letter to the Drafting Team

[Phil Corwin <psc@xxxxxxxxxxx>]

I took over an hour this afternoon to open and scan through all the comments 
filed on the draft Bylaws.

While a few were readily dismissible, most had enough substance to require at 
least some thought. I concur with Paul that no group could assimilate, 
consider, and make decisions upon all of them in less than a week.

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] On 
Behalf Of Paul McGrady
Sent: Monday, May 23, 2016 7:25 AM
To: 'WUKnoben'; 'James M. Bladel'; council@xxxxxxxxxxxxxx
Subject: RE: [council] Proposed letter to the Drafting Team

Thanks WU.  Respectfully, with only 6 days from the close of public comment to 
the Board vote, there is no “process” to bypass.

Best,
Paul






From: owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx> 
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of WUKnoben
Sent: Monday, May 23, 2016 5:51 AM
To: James M. Bladel; Paul McGrady; 
council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>
Subject: Re: [council] Proposed letter to the Drafting Team

I’m fine with this procedure as well as the text proposed by Paul (with the 
links to be inserted).
I’m a bit hesitant whether we should cc the board. This seems to bypass the 
process.

Best regards

Wolf-Ulrich

From: James M. Bladel<mailto:jbladel@xxxxxxxxxxx>
Sent: Sunday, May 22, 2016 7:35 PM
To: Paul McGrady<mailto:policy@xxxxxxxxxxxxxxx> ; 
council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>
Subject: Re: [council] Proposed letter to the Drafting Team

Hi Paul -

Thanks for kicking this off.  Generally, I’m good with this letter.  A few 
questions/comments:

  *   Given the compressed timeline, can we ask Staff to confirm whether or not 
the Drafting Team will have an opportunity to amend the proposed bylaws before 
submitting to the Board?  I’m assuming they will, but…
  *   Should we also cc: the Board and/or CCWG Co-Chairs? (hedge)
  *   With the Comment Period now closed, could we task someone from Policy 
Staff to assist Paul in gathering links to GNSO comments?
  *   The Board is meeting this week to consider the draft bylaws.  It is 
therefore imperative that we move quickly to get this sent.  Councilors, please 
send edits/comments/concerns by EOD (Pacific) Monday to ensure that this is 
posted overnight Tuesday.
Thanks again—

J.

From: <owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>> on 
behalf of Paul McGrady <policy@xxxxxxxxxxxxxxx<mailto:policy@xxxxxxxxxxxxxxx>>
Date: Saturday, May 21, 2016 at 6:01
To: GNSO Council List <council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>>
Subject: [council] Proposed letter to the Drafting Team

Hi all,

On our last call, I volunteered t draft a short letter from James to the Bylaws 
Drafting Team.  Here is the proposed body of that letter to be kicked around 
the Council list:

________

Dear Bylaws Drafting Team:

The GNSO Council thanks you for your efforts in attempting to distill the 
instructions found in the CCWG-Accountability Report into a revised version of 
ICANN’s Bylaws.  We note that the draft Bylaws have generated significant 
public comment from members of the GNSO community.  These include:


[Paul McGrady to pull these links out of the public comment after it closes]

We ask you to carefully review each of these comments and give them serious 
consideration.  It is important that the revised Bylaws remain faithful to the 
CCWG-Accountability Report on which we, as a Council, were called upon to vote 
in Marrakech.  We are fully at your disposal should you wish to consult us on 
any issue raised in the comments generated by the GNSO community.

Kind regards,
James Bladel



Best,
Paul
policy@xxxxxxxxxxxxxxx<mailto:policy@xxxxxxxxxxxxxxx>


________________________________
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