Dear GNSO Councilors,

Please see the following Call for Volunteers.

Kind regards,

Nathalie

--

Call for Volunteers: GNSO Drafting Team to Further Develop Recommendations to 
Implement the GNSO's New Roles and Obligations Under the Revised ICANN Bylaws

In Brief

Per the motion adopted on 30 June 2016, the Generic Names Supporting 
Organization (GNSO) Council seeks volunteers for a Drafting Team to further 
develop recommendations to implement the GNSO's new roles and obligations under 
the post-transition ICANN Bylaws.

What This Team Will Do

The Drafting Team will work with ICANN staff to fully identify all the new or 
additional rights and responsibilities that the GNSO has under the 
post-transition 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.

The Drafting Team shall 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.

As part of the process of its consideration of the implementation plan, 
intended to be approved by a GNSO supermajority vote, the Council may further 
request that the Drafting Team work with ICANN staff to develop new, or propose 
modifications to existing, procedures and structures to implement the revised 
Bylaws for the GNSO. Any such new, or proposed modifications to existing 
procedures and structures to implement the revised Bylaws for the GNSO are also 
intended to be approved by a GNSO supermajority vote.

How to Join
Volunteers for the Drafting Team will be identified by GNSO Council members. 
Volunteers should express interests and can demonstrate reasonable knowledge of 
or experience with the process of revising the ICANN Bylaws or GNSO Operating 
Procedures. The Drafting Team shall reflect the current composition of the GNSO 
and as such, the GNSO Council may review the number of volunteers identified by 
the GNSO Council members. GNSO Councilors are requested to identify volunteers 
by email to gnso-secs@icann.org by 22 July 2016.

Next Steps

As noted above, the GNSO Council directed that this call for volunteers be 
circulated to the GNSO Council and that the volunteers should be identified by 
GNSO Council members. It is anticipated that the Drafting Team will convene 
online for the first time in early August 2016. Following that, regular online 
meetings will be scheduled in accordance with the Drafting Team's work plan, 
which it is expected to develop as one of its first tasks.

Further Information and Preparation

For those interested in volunteering for this effort, you are encouraged to 
review the  table at: 
http://gnso.icann.org/en/drafts/revised-bylaws-notes-comments-procedures-14jun16-en.pdf.

Background

On 27 May 2016 the ICANN Board adopted a set of new ICANN Bylaws, as revised on 
26 May 2016, that aim to reflect changes needed to implement the IANA 
Stewardship Transition Proposal and such adoption is contingent on the proposed 
transition away of remaining United States Government oversight of ICANN.  The 
Generic Names Supporting Organization (GNSO) Council is aware that changes that 
may need to be made to the GNSO's current Operating Procedures and related 
mechanisms and to the ICANN Bylaws in order to give effect to new roles and 
obligations of the GNSO under the new Bylaws, such as those in this table 
(http://gnso.icann.org/en/drafts/revised-bylaws-notes-comments-procedures-14jun16-en.pdf),
 including but not limited to the GNSO's participation in the Empowered 
Community.  Per the motion adopted on 30 June 2016, the Generic Names 
Supporting Organization (GNSO) Council seeks volunteers for a Drafting Team to 
further develop recommendations to implement the GNSO's new roles and 
obligations under the revised ICANN Bylaws.