ICANN/GNSO GNSO Email List Archives

[council]


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

[council] Motion - To Approve the Report from the GNSO Bylaws Implementation Drafting Team

  • To: GNSO Council List <council@xxxxxxxxxxxxxx>
  • Subject: [council] Motion - To Approve the Report from the GNSO Bylaws Implementation Drafting Team
  • From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Date: Mon, 3 Oct 2016 21:39:48 +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=+ORrckQpvsGRCaGo4vKQVGmzfpk57rT8+XJ3lBKKmVA=; b=DXCPh2scGzITSJiYeGphvM4NB5wKBlZPrNpIMfSyjOT17EcWVVfHvhB1tJgjmJQSLuNNLOqYYEXG/vyusNrTd2xSQGSv1lEwfBZxw6nGT6Wrk1yNtYQmBEGXqtqCDNgTBUxSyXXLiOoc3U0erirfTeEC6R/bSz6RB7cbiYhVMIU=
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
  • Thread-index: AQHSHb6pFrDzxvlj7kCx7Mi1yTwjnQ==
  • Thread-topic: Motion - To Approve the Report from the GNSO Bylaws Implementation Drafting Team
  • User-agent: Microsoft-MacOutlook/f.1a.0.160910

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,

J.



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

WHEREAS:


  1.  On 30 June 2016 the GNSO Council 
approved<https://gnso.icann.org/en/council/resolutions#20160630-2> 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”;
  2.  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”;
  3.  The DT submitted its report to the GNSO Council on [DATE] (also insert 
link to report when available);
  4.  The GNSO Council has reviewed the DT’s report;

RESOLVED:


  1.  The GNSO Council approves the consensus recommendations in DT’s report as 
submitted.
  2.  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].
  3.  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.
  4.  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.
  5.  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.

Attachment: Motion to Adopt GNSO Bylaws DT report.docx
Description: Motion to Adopt GNSO Bylaws DT report.docx



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