<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] Proposed letter to the Drafting Team
- To: "'WUKnoben'" <wolf-ulrich.knoben@xxxxxxxxxxx>, "'James M. Bladel'" <jbladel@xxxxxxxxxxx>, <council@xxxxxxxxxxxxxx>
- Subject: RE: [council] Proposed letter to the Drafting Team
- From: "Paul McGrady" <policy@xxxxxxxxxxxxxxx>
- Date: Mon, 23 May 2016 06:24:43 -0500
- In-reply-to: <23EF2E0E84C3446B8A2F633B3E250429@WUKPC>
- List-id: council@xxxxxxxxxxxxxx
- References: <000501d1b350$1ad2e740$5078b5c0$@paulmcgrady.com> <D36756B8.C1AA3%jbladel@godaddy.com> <23EF2E0E84C3446B8A2F633B3E250429@WUKPC>
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AQI/z0sBcLMDxyxyzv4akTjwronlDwJXwi3lAoEEIeOew2XcMA==
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] On
Behalf Of WUKnoben
Sent: Monday, May 23, 2016 5:51 AM
To: James M. Bladel; Paul McGrady; 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
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> on behalf of Paul McGrady
<policy@xxxxxxxxxxxxxxx>
Date: Saturday, May 21, 2016 at 6:01
To: GNSO Council List <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
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|