<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} @font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
.MsoChpDefault
{font-family:"Calibri","sans-serif"}
.MsoPapDefault
{margin-bottom:10.0pt;
line-height:115%}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}table.MsoNormalTable
{line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Stefania,</p>
<p><br>
</p>
<p>One alternative would be to resign from the EC? I am not trying to be funny. Yet, this would be the way to avoid a conflict.</p>
<p>Just a thought.</p>
<p><br>
</p>
<div style="color: rgb(33, 33, 33);" dir="auto">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> ncuc-ec-bounces@lists.ncuc.org <ncuc-ec-bounces@lists.ncuc.org> on behalf of Milan, Stefania <Stefania.Milan@EUI.eu><br>
<b>Sent:</b> Saturday, September 20, 2014 8:26 AM<br>
<b>To:</b> William Drake<br>
<b>Cc:</b> Exec. Comm<br>
<b>Subject:</b> Re: [NCUC-EC] CFP: NCUC reps to the NCSG PC</font>
<div> </div>
</div>
<div>
<div>That's why i asked you first. The readon for joining would simply be the way i function: need clear tasks and commitments to which to be linked by a sense of guilt! Otherwise regular work (which is a lot) takes over... :) <br>
<br>
Sent from my iPhone</div>
<div><br>
On 20/set/2014, at 12:55, "William Drake" <<a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a>> wrote:<br>
<br>
</div>
<div></div>
<blockquote type="cite">
<div>You’re on the EC that selects the reps. Don’t you think that’d look weird, especially if there are competing nominees?
<div><br>
</div>
<div>Why don’t we see what we get before thinking about this?<br>
<div><br>
</div>
<div>BTW one doesn’t have to be on the PC to do policy work.</div>
<div><br>
</div>
<div>B<br>
<div><br>
<div>
<div>On Sep 20, 2014, at 12:43 PM, Milan, Stefania <<a href="mailto:Stefania.Milan@EUI.eu">Stefania.Milan@EUI.eu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="auto" style="font-family:Verdana; font-size:18px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<div>Dear Bill</div>
<div>I would be interested in joining the PC. After a year of learning (and much more to go of course), i think it is time to dedicate some energies to policy more directly. What do you think?</div>
<div>Stefania</div>
<div><br>
Sent from my iPhone</div>
<div><br>
On 20/set/2014, at 10:58, "William Drake" <<a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">Hello
<div><br>
</div>
<div>Early in the year, after consultation with members, the NCUC PC appointed Stephanie Perrin and Marilia Maciel to serve as our representatives on the NCSG PC. As you will know, both of these successful reps have recently been elected to the GNSO Council,
so we will need to replace them. This message is to solicit expressions of interest in filling these roles. It is hoped that we can make a final selection and have new people in place by the Annual Meeting in Los Angeles; the NCSG PC meets on Sunday 12 October.</div>
<div><br>
</div>
<div>These are two of the very most important positions we have in NCUC. According to the NCSG charter, </div>
<div><br>
</div>
<div>----------------------------------------------------------------------------------------------------------------------</div>
<div><i><br>
</i></div>
<div><i>2.5 The Policy Committee<br>
</i></div>
<div><i><br>
</i></div>
<div><i>The NCSG Policy Committee is responsible for:<br>
<br>
</i>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• Discussion and development of substantive policies and statements issued in the name of the NCSG. This activity will require coordination with the membership and the Constituencies;<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• Organize policy initiatives on behalf of NCSG membership, including PDP initiatives from the membership;<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• Provide policy research and guidance to NCSG representatives on the GNSO Council;<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• Keep membership informed of GNSO Council activities;<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• Organize, appoint where appropriate, and track NCSG participation in GNSO and other pertinent Working Groups.<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• Organization and oversight of NCSG participation in any GNSO Council- related tasks, whether mandated by Bylaws, Council Procedures or Council decisions.<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• Document methods and procedures used for decision-making. Such documentation is subject to review by the NCSG-EC.<br>
<br>
2.5.1. NCSG-PC Composition.<br>
<br>
The NCSG–PC shall be comprised of two representatives from each Recognized Constituency and one observer from each Candidate Constituency. The NCSG Representatives on the GNSO Council shall also serve as full members of the NCSG- PC. The NCSG Chair will participate
as an ex-officio member of the NCSG-PC and will be included in determining consensus process and votes. Past GNSO Council Representatives may be included as observers in the NCSG-PC. The membership of the NCSG-PC may invite others to participate as observers.<br>
<br>
2.5.2. NCSG-PC Decision making<br>
<br>
</i></div>
<i>• By default NCSG-PC decisions are made by rough consensus of full NCSG-PC members. Rough consensus means that while all members do not need to agree and that no single member can veto a decision, all views must be heard and considered. Any minority views
must be recorded along with the rough consensus position.<br>
<page15image17520.png> <page15image17680.png> <page15image17840.png><br>
2.5.3. NCSG-PC Leadership<br>
<br>
</i>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• A Chair will be elected or replaced from among the members of the NCSG-PC by a 2/3 vote of the NCSG-PC membership on a yearly basis.<br>
<br>
§ The NCSG Chair may not serve in this role.<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• One or more Vice-Chairs may be chosen by the NCSG-PC on a yearly basis. 2.5.4. NCSG-PC Work Process<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• As much as possible, all work will be done using Internet tools, including, inter alia,<br>
<br>
</i>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• § email;<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• § wiki usage (Note: such a wiki will be publicly viewable though editing may be restricted to members of the NCSG-PC);<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• § online document collaboration tools as well as available network cloud based tools.<br>
<br>
</i></div>
</div>
</div>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px"><i>• When necessary, teleconferences will be scheduled. A scheduling tool will be used to attempt to find a time when all members can attend. Unless all members can attend the teleconference,
any decisions made at a teleconference will be provisional until full consensus is determined.</i></blockquote>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px"><i><br>
</i></blockquote>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px"><i>• When possible, as enabled for example by an ICANN meeting, a face-to-face meeting of the NCSG-PC will be held. As with teleconferences, if all members cannot attend, any decisions made
will need to be verified before being considered final.</i></blockquote>
</blockquote>
</blockquote>
<div>
<div><i><br>
2.5.5. NCSG-PC Mailing List<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• All NCSG-PC full members and observers will be subscribed to the NCSG-PC mailing list.<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• The NCSG-PC list will maintain an open archive.<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• For non-subscribers the list will be moderated. Comments from NCSG members relevant to ongoing discussions will be forwarded to the NCSG-PC list by the list moderator.<br>
<br>
2.5.6. NCSG-PC Observers<br>
<br>
</i></div>
<i>• Any observer to the NCSG-PC will have full participation rights except will not be counted in any consensus process or vote.<br>
<page16image17216.png> <page16image17376.png> <page16image17536.png> <page16image17696.png><br>
</i>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• One elected or appointed representative from each Candidate Constituency will be given observer status.<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• Past NCSG Representatives to the GNSO Council may be permitted observer status at discretion of NCSG-PC full members.<br>
<br>
</i></div>
<div><i><span class="Apple-tab-span" style="white-space:pre"></span>• The NCSG-PC may invite other policy experts to participate as observers.</i></div>
</div>
<div><br>
</div>
<div>----------------------------------------------------------------------------------------------------------------------</div>
<div><br>
</div>
<div>
<div><br>
</div>
<div>Basic info on the current PC’s composition is at <a href="https://community.icann.org/display/gnsononcomstake/Committees-Current">https://community.icann.org/display/gnsononcomstake/Committees-Current</a></div>
<div><br>
</div>
<div>The public archive for the PC’s discussions is at <a href="http://mailman.ipjustice.org/listinfo/pc-ncsg">http://mailman.ipjustice.org/listinfo/pc-ncsg</a>. Perusing this would give one a clearer idea of the actual workload and responsibilities.</div>
<div><br>
</div>
<div>It is really really important that we put people into these slots who are fully in tune with the views and traditions of NCUC and NCSG; well appraised (or able to become so) of the substantive issues being discussed in GNSO and related processes; fully
committed to doing the work (including attending monthly NCSG policy calls, collaborative document drafting, timely voting on proposed outputs, and the like); and able to work well with their colleagues on the PC and to coordinate with the NCUC EC and wider
membership as necessary. In short, we need top notch, fully committed candidates.</div>
<div><br>
</div>
<div>We welcome nominations and self-nominations to fill these two slots. Nominees who wish to be considered should send a few paragraphs to the members’ list outlining their interests and engagement in constituency/stakeholder group work, their qualifications
for and ability to perform these particular functions, and any other relevant information. </div>
<div><br>
</div>
<div><b>The time frame unfortunately will need to be tight. The NCUC EC will begin to evaluate the candidate pool on 29 September, with an eye toward announcing selections a few days thereafter. It would be ideal if the selectees are able to attend the Los
Angeles meeting; if necessary, NCUC may be able to defray part of their costs as part of the new travel policy that will be announced shortly.</b></div>
<div><br>
</div>
<div>Any questions, let me know.</div>
<div><br>
</div>
<div>Best</div>
<div><br>
</div>
<div>Bill</div>
<div><br>
<div>***********************************************<br>
William J. Drake<br>
International Fellow & Lecturer<br>
Media Change & Innovation Division, IPMZ<br>
University of Zurich, Switzerland<br>
Chair, Noncommercial Users Constituency, <br>
ICANN,<span class="Apple-converted-space"> </span><a href="http://www.ncuc.org/">www.ncuc.org</a><br>
<a href="mailto:william.drake@uzh.ch">william.drake@uzh.ch</a> (direct), <a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a><span class="Apple-converted-space"> </span>(lists),<br>
<span class="Apple-converted-space"> </span><a href="http://www.williamdrake.org/">www.williamdrake.org</a><br>
***********************************************</div>
</div>
</div>
</blockquote>
<blockquote type="cite"><span>_______________________________________________</span><br>
<span>NCUC-EC mailing list</span><br>
<span><a href="mailto:NCUC-EC@lists.ncuc.org">NCUC-EC@lists.ncuc.org</a></span><br>
<span><a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a></span><br>
</blockquote>
<div class="WordSection1" style="">
<div style="margin:0in 0in 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:8pt; color:rgb(89,89,89)"> </span></div>
<div style="margin:0in 0in 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:8pt; color:rgb(89,89,89)">The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination, distribution,
forwarding, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited without the express permission of the sender. If you received this communication in error, please
contact the sender and delete the material from any computer.</span></div>
</div>
<span><page16image17536.png></span><span><page15image17520.png></span><span><page16image17216.png></span><span><page16image17376.png></span><span><page15image17680.png></span><span><page16image17696.png></span><span><page15image17840.png></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 14">
<meta name="Originator" content="Microsoft Word 14">
<link rel="File-List" href="eui%20footer_files/filelist.xml"><link rel="themeData" href="eui%20footer_files/themedata.thmx"><link rel="colorSchemeMapping" href="eui%20footer_files/colorschememapping.xml"><style>
<!--
@font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
.MsoChpDefault
{font-family:"Calibri","sans-serif"}
.MsoPapDefault
{margin-bottom:10.0pt;
line-height:115%}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
-->
</style><style>
<!--
table.MsoNormalTable
{line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
-->
</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:8.0pt; color:#595959"> </span></p>
<p class="MsoNormal"><span style="font-size:8.0pt; color:#595959">The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination,
distribution, forwarding, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited without the express permission of the sender. If you received this communication in
error, please contact the sender and delete the material from any computer. </span>
</p>
</div>
</div>
</div>
</body>
</html>