[client com] Vacancies on CSC, IFRT and SCWG

Mon Apr 18 08:33:18 UTC 2016

All,

Lise and I have discussed and we are OK with the deletion. Diversity is
important but should be an overarching principle in all areas of ICANN.

We will send this and other recently identified issues to the CWG for
ratification / confirmation at 12h00 UTC today.

Jonathan

From: Maarten Simon [mailto:maarten.simon at sidn.nl] 
Sent: 18 April 2016 09:22
To: Flanagan, Sharon <sflanagan at sidley.com>; Client Committee
<cwg-client at icann.org>
Subject: Re: [client com] Vacancies on CSC, IFRT and SCWG

My first take:

The CSC will be governed by the bylaws and its charter. The current draft
version of the charter is part of the CWG proposal and is, I presume, used
as a basis to draft the bylaws. The charter requires ccNSO and the GNSO (or
RySG) in par 1336 and 1337 to strive for a composition of the CWG that has
'to the extend possible, diversity in terms of geography and skill set'. 

The question is if 'to the extend possible, diversity in terms of geography
and skill set' should be part of the bylaws or part of the charter only. If
it should be in the bylaws, than I think it should be in the appointment
part as well as in the part that describes the filling of vacancies.

I have no personal preference here.

Best,

Maarten

From: <cwg-client-bounces at icann.org <mailto:cwg-client-bounces at icann.org> >
on behalf of Sharon Flanagan <sflanagan at sidley.com
<mailto:sflanagan at sidley.com> >
Date: Monday 18 April 2016 at 04:25
To: "cwg-client at icann.org <mailto:cwg-client at icann.org> "
<cwg-client at icann.org <mailto:cwg-client at icann.org> >
Subject: [client com] Vacancies on CSC, IFRT and SCWG

Dear All,

ICANN Legal suggested deletion of the new language below regarding the
filling of vacancies.  Vacancies are not described in the CWG proposal, so
this deletion is not inconsistent with the proposal.  Please confirm the
deletion is acceptable.  It also applies to IFRTs and SCWGs.  

"A vacancy on the CSC shall be deemed to exist in the event of the death,
resignation or removal of any CSC member or liaison.  Vacancies shall be
filled by the organization that appointed such CSC member or liaison.  The
appointing organization shall provide written notice to the Secretary of its
appointment to fill a vacancy, with a notification copy to the Chair of the
CSC.  The organization responsible for filling such vacancy shall use its
reasonable efforts to fill such vacancy within one month after the
occurrence of such vacancy with an individual with a similar skill set and
diversity, to the extent practicable."

ICANN Note: There are not diversity or skill requirements for CSC members
(the experience requirement of 17.2(a) applies to all selections).
Additionally, requiring the new individual to have similar skill set and
diversity as the prior person could lead to unnecessary restrictions on
filling vacancies (i.e., if a Japanese engineer is being replaced, does the
vacancy have to be filled by another Japanese engineer?).

Given time constraints, we are sending these issues as they are identified.
At this point we have:  

- mission/purpose/role issue 

- budget line edits 

- vacancies

Thanks

SHARON R. FLANAGAN

SIDLEY AUSTIN LLP
555 California Street
Suite 2000
San Francisco, CA 94104
+1 415 772 1271
 <mailto:sflanagan at sidley.com> sflanagan at sidley.com
 <http://www.sidley.com> www.sidley.com

  <http://www2.sidley.com/files/upload/signatures/SIDLEY_150-AUTOSIG.png> 

****************************************************************************
************************
This e-mail is sent by a law firm and may contain information that is
privileged or confidential.
If you are not the intended recipient, please delete the e-mail and any
attachments and notify us
immediately.

****************************************************************************
************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cwg-client/attachments/20160418/ce4fa7a2/attachment.html>