Thanks Mary.

Then it appears that the likely course is to defer a vote until Hyderabad if the report is not delivered until just before our October meeting, in order to give us a chance to fully review it and consult with those we represent on this important matter.

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: Mary Wong [mailto:mary.wong@icann.org]
Sent: Monday, October 03, 2016 7:47 PM
To: James M. Bladel; Phil Corwin; GNSO Council List
Subject: Re: [council] Re: Motion - To Approve the Report from the GNSO Bylaws Implementation Drafting Team

Hello everyone – basically, what James said J

It looks like the DT is on track to complete its work in time for the 13 October Council call, and they certainly intend to do so. This will allow the Council a chance to begin its deliberations on the DT’s recommendations and the placeholder motion on 13 October, with a view toward actual adoption in Hyderabad.

Thanks and cheers

Mary

Mary Wong

Senior Policy Director

Internet Corporation for Assigned Names and Numbers (ICANN)

Email: mary.wong@icann.org

Telephone: +1-603-5744889

From: <owner-council@gnso.icann.org> on behalf of "James M. Bladel" <jbladel@godaddy.com>
Date: Monday, October 3, 2016 at 19:17
To: Phil Corwin <psc@vlaw-dc.com>, GNSO Council List <council@gnso.icann.org>
Subject: [council] Re: Motion - To Approve the Report from the GNSO Bylaws Implementation Drafting Team

Hi Phil –

Let’s confirm with Marika/Mary, but we allowed this team an additional two weeks to complete their work, as requested by Steve. Naturally, we would prefer to have as much time as possible between delivery of the report and consideration / vote by Council. Also, with the transition behind us and an interim EC rep in place, I don’t think we are at risk of missing any external deadlines if we consider this item in Hyderabad, particularly if folks need more time to consider the recommendations. Note that I’m not advocating for this route, but it is an option.

Thanks—

From: Phil Corwin <psc@vlaw-dc.com>
Date: Monday, October 3, 2016 at 16:56
To: "James M. Bladel" <jbladel@godaddy.com>, GNSO Council List <council@gnso.icann.org>
Subject: RE: Motion - To Approve the Report from the GNSO Bylaws Implementation Drafting Team

Can you remind us what the expected date of delivery is? I would hope we’d have at least several days to review and consult with those we represent prior to being asked to vote on approving the report’s recommendations. We only get one chance to implement the new Bylaws, so we should make sure we’re getting it right and not missing anything important.

Thanks and best regards

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@gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of James M. Bladel
Sent: Monday, October 03, 2016 5:40 PM
To: GNSO Council List
Subject: [council] Motion - To Approve the Report from the GNSO Bylaws Implementation Drafting Team

Councilors -

Attached and copied below, please find a placeholder motion to approve the report & recommendations of the Bylaws Implementation Drafting Team. As discussed during our last call, we have extended the expected delivery of this report before our next call on 13 OCT.

Thank you,

MOTION TO APPROVE THE REPORT FROM THE GNSO BYLAWS IMPLEMENTATION DRAFTING TEAM

WHEREAS:

On 30 June 2016 the GNSO Council approved[gnso.icann.org] the creation of a Drafting Team (DT) that was to work with ICANN staff to “fully identify all the new or additional rights and responsibilities that the GNSO has under the revised Bylaws, including but not limited to participation of the GNSO within the Empowered Community, and to develop new or modified structures and procedures (as necessary) to fully implement these new or additional rights and responsibilities”;
In creating the DT, the GNSO Council requested that the DT provide the GNSO Council with an implementation plan “which will have the consensus of the Drafting Team, including any recommendations for needed further changes to ICANN Bylaws and/or GNSO Operating Procedures to enable effective GNSO participation in ICANN activities under the revised ICANN Bylaws, not later than 30 September 2016”;
The DT submitted its report to the GNSO Council on [DATE] (also insert link to report when available);
The GNSO Council has reviewed the DT’s report;

RESOLVED:

The GNSO Council approves the consensus recommendations in DT’s report as submitted.
The GNSO Council directs ICANN staff to draft proposed language for any necessary modifications or additions to the GNSO Operating Procedures and, if applicable, those parts of the ICANN Bylaws pertaining to the GNSO, for the Council’s consideration by no later than [the end of February 2017].
The GNSO Council directs ICANN staff to post all recommended modifications to or proposed new procedures or structures for public comment prior to the Council’s consideration of the proposals. As resolved previously, the GNSO Council intends to intends to adopt new, or proposed modifications to existing procedures and structures to implement the revised Bylaws for the GNSO by a GNSO supermajority vote.
In drafting the proposed language, ICANN staff may wish to consult the DT as needed. The GNSO Council therefore requests that members of the DT make themselves available for consultation by ICANN staff for this purpose.
The GNSO Council thanks the DT for its hard work on the report, especially in view of the nature of the limited time frame available to the DT.

No virus found in this message.
Checked by AVG - www.avg.com[avg.com]
Version: 2016.0.7797 / Virus Database: 4656/13076 - Release Date: 09/24/16
Internal Virus Database is out of date.

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7797 / Virus Database: 4656/13076 - Release Date: 09/24/16
Internal Virus Database is out of date.