<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks Steve, I was doing markup on the redline version, but
apparently the changes dont show clearly. I have copy pasted it
below, but you have captured the sense of it.</p>
<p>Stephanie<br>
</p>
<p>
<style id="dynCom" type="text/css"></style>
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-469750017 -1073732485 9 0 511 0;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-priority:99;
mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin:0cm;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-ansi-language:EN-US;}p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
{mso-style-noshow:yes;
mso-style-priority:99;
mso-style-link:"Comment Text Char";
margin:0cm;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-ansi-language:EN-US;}span.MsoCommentReference
{mso-style-noshow:yes;
mso-style-priority:99;
mso-ansi-font-size:8.0pt;
mso-bidi-font-size:8.0pt;}span.CommentTextChar
{mso-style-name:"Comment Text Char";
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-unhide:no;
mso-style-locked:yes;
mso-style-link:"Comment Text";
mso-ansi-font-size:10.0pt;
mso-bidi-font-size:10.0pt;}.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-ansi-language:EN-US;}div.WordSection1
{page:WordSection1;}</style>
<p class="MsoNormal" style="background:white"><span
style="mso-fareast-font-family:
"Times New
Roman";mso-bidi-font-family:Calibri;mso-bidi-theme-font:minor-latin;color:#333333"
lang="EN-US">The NomCom is seeking accomplished persons of
integrity,
objectivity, and intelligence with <b>e</b><b><a
style="mso-comment-reference:SP_1;
mso-comment-date:20211117T1239">xperience</a></b></span><span
class="MsoCommentReference"><span
style="font-size:8.0pt;color:black;
mso-color-alt:windowtext" lang="EN-US"><a
class="msocomanchor" id="_anchor_1" href="#_msocom_1"
name="_msoanchor_1">[SP1]</a><span
style="mso-special-character:comment"> </span></span></span><span
style="mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family:
Calibri;mso-bidi-theme-font:minor-latin;color:#333333"
lang="EN-US"> in the multistakeholder
policymaking process and within the GNSO community. While GNSO
Council members
should have a deep understanding of the GNSO structure,
existing ICANN consensus policies, and contracts
between ICANN and registries and registrars, preference will
be given
to candidates with a demonstrable ability to manage the policy
development
process towards the best interests of the entire GNSO
community rather than
solely for a specific GNSO Stakeholder Group or Constituency.
NomCom appointed members
are expected to act with integrity and independently. Voting
NomCom appointed
members are encouraged to engage with the Council
representatives of their
appointed House and all NomCom appointed member are encouraged
to engage with
the GNSO community more broadly, </span><span
class="MsoCommentReference"><span
style="font-size:8.0pt;color:black;mso-color-alt:windowtext"
lang="EN-US"><a class="msocomanchor" id="_anchor_2"
href="#_msocom_2" name="_msoanchor_2">[SP2]</a><span
style="mso-special-character:comment"> </span></span></span><span
style="mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family:
Calibri;mso-bidi-theme-font:minor-latin;color:#333333"
lang="EN-US">to understand their
concerns and views, so that the NomCom appointee may be an
informed and
effective councilor.</span></p>
<p class="MsoNormal" style="background:white"><span
style="mso-fareast-font-family:
"Times New
Roman";mso-bidi-font-family:Calibri;mso-bidi-theme-font:minor-latin;color:#333333"
lang="EN-US"> </span></p>
<p class="MsoNormal" style="background:white"><span
style="mso-fareast-font-family:
"Times New
Roman";mso-bidi-font-family:Calibri;mso-bidi-theme-font:minor-latin;color:#333333"
lang="EN-US">NomCom appointed members who are affiliated with
an ICANN
community group at the time of application are not meant to
represent their
current or previously affiliated group and are expected to
observe the
principles and intent of the ICANN’s Conflicts of Interest
Policy.</span></p>
<div style="mso-element:comment-list">
<hr class="msocomoff" width="33%" size="1" align="left">
<div style="mso-element:comment">
<div id="_com_1" class="msocomtxt"><span
style="mso-comment-author:
"Stephanie
Perrin";mso-comment-providerid:"Windows
Live";mso-comment-userid:
84ca7457d663a8dc"><a name="_msocom_1"></a></span>
<p class="MsoCommentText"><span class="MsoCommentReference"><span
style="font-size:8.0pt" lang="EN-US"><span
style="mso-special-character:comment"> <a
href="#_msoanchor_1" class="msocomoff">[SP1]</a></span></span></span><span
lang="EN-US">NCSG rejects the word “ experience” and
“within the GNSO community.”<span
style="mso-spacerun:yes"> </span>Already we have an
issue with burnout of
existing members, and a “revolving door” of the same
people running for office,
year after year.<span style="mso-spacerun:yes"> </span>We
need fresh eyes on
our work, to ensure that there is no capture by a small
group of
stakeholders.<span style="mso-spacerun:yes"> </span>Please
revert to previous
language.</span></p>
</div>
</div>
<div style="mso-element:comment">
<div id="_com_2" class="msocomtxt"><span
style="mso-comment-author:
"Stephanie
Perrin";mso-comment-providerid:"Windows
Live";mso-comment-userid:
84ca7457d663a8dc"><a name="_msocom_2"></a></span>
<p class="MsoCommentText"><span class="MsoCommentReference"><span
style="font-size:8.0pt" lang="EN-US"><span
style="mso-special-character:comment"> <a
href="#_msoanchor_2" class="msocomoff">[SP2]</a></span></span></span><span
lang="EN-US">With respect to the language that has been
deleted here, starting
with “balance the interests” and ending with their
appointed House”, please revert
and return this important language.<span
style="mso-spacerun:yes"> </span>WE
want neutrality on the part of Nomcom appointees, and
fresh eyes…in the event
that Nomcom selects members who have been active in the
stakeholder community
at ICANN already, we absolutely need to emphasis the
need for neutrality and
non-representation on the part of their previous or
current constituency.<span style="mso-spacerun:yes"> </span>Repetition
in the new paragraph below is
fine, we cannot over-emphasize the importance of this
aspect of the role.</span></p>
<p class="MsoCommentText"><span lang="EN-US"> </span></p>
</div>
</div>
</div>
</p>
<div class="moz-cite-prefix">On 2021-11-17 4:45 p.m., Steve Chan
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CD568BBF-EF4F-4EE8-A8E3-B276AB55944A@icann.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0in;}ul
{margin-bottom:0in;}</style>
<div class="WordSection1">
<p class="MsoNormal">Dear Stephanie, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It took me a moment to see what you were
suggesting, as I saw no redlines. I’ve since seen your comment
in the Word doc and thought it might be helpful to make clear
what specific change you are suggesting. For the first
sentence under Job Description:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph"
style="margin-left:0in;mso-list:l0 level1 lfo1"><i>As
currently shared</i>:
<span style="color:#333333">The NomCom is seeking
accomplished persons of integrity, objectivity, and
intelligence
<b>with experience</b> in the multistakeholder
policymaking process <b>and within the GNSO community</b>.</span>
<o:p></o:p></li>
</ul>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph"
style="margin-left:0in;mso-list:l0 level1 lfo1"><i>Suggested
change, which reverts to previous language</i>:
<span style="color:#333333">The NomCom is seeking
accomplished persons of integrity, objectivity, and
intelligence with
<b>an interest</b> in the multistakeholder policymaking
process.</span><o:p></o:p></li>
</ul>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoNormal">I have tried to highlight the difference
between the two versions by bolding the relevant elements, and
hope Councilors find this helpful.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Steve<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span
style="color:black">council
<a class="moz-txt-link-rfc2396E" href="mailto:council-bounces@gnso.icann.org"><council-bounces@gnso.icann.org></a> on behalf of
Stephanie E Perrin via council
<a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a><br>
<b>Reply-To: </b>Stephanie E Perrin
<a class="moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@mail.utoronto.ca"><stephanie.perrin@mail.utoronto.ca></a><br>
<b>Date: </b>Wednesday, November 17, 2021 at 10:02 AM<br>
<b>To: </b><a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org">"council@gnso.icann.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a><br>
<b>Cc: </b>NCSG PC <a class="moz-txt-link-rfc2396E" href="mailto:ncsg-pc@lists.ncsg.is"><ncsg-pc@lists.ncsg.is></a><br>
<b>Subject: </b>Re: [council] Supporting Document for
November Council Meeting Agenda Item 4: Revised GNSO
Councilor Job Description for the Nominating Committee<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p>Thanks for your hard work on this job description. NCSG has
had a brief discussion on this topic, and believes that we
have taken a slight wrong turn in some of the revisions. We
believe that it is important for Nomcom to seek fresh eyes and
talent for the Nomcom representatives on Council. The job
description should therefore not insist, as this new version
does, on the importance of experience. Understanding of the
role of the GNSO, certainly, but experience in the ICANN MS
model and its structures is certainly NOT necessary or even
desireable. WE want fresh eyes, different experience and
ideas that can help us improve.
<o:p></o:p></p>
<p>There is obviously an issue if former Councillors start to
apply for a Nomcom seat on Council when their terms are up, in
terms of upsetting the balance of stakeholder
group/constituency representation. We are not looking for a
prohibition of Councillors coming back as Nomcom, just to
remove the emphasis on previous GNSO/ICANN experience.<o:p></o:p></p>
<p>I hope that I have expressed the views of my SG adequately in
these comments and the attached markup, and suggest we have a
thorough discussion of this topic in our meeting this week.<o:p></o:p></p>
<p>Stephanie Perrin<o:p></o:p></p>
<div>
<p class="MsoNormal">On 2021-11-15 8:00 p.m., Steve Chan via
council wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear
Councilors,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">On behalf
of the small team (Flip Petillion, Mark Datysgeld, Maxim
Alzoba, Olga Cavalli, and Tomslin Samme-Nlar) that worked
on the revised NomCom job description, please find their
proposed final draft attached in both redline and clean.
This version attempts to take into account the initial
edits proposed initially by the previous Council
leadership team, discussion both on list and during the
previous Council call, as well as subsequent email
dialogue amongst the small team. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Steve</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Steven
Chan</span></b><b><span
style="font-size:11.0pt;font-family:"MS
Gothic"">
</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Senior
Director, GNSO Support</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:black">Internet Corporation
for Assigned Names and Numbers (ICANN) </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">12025
Waterfront Drive, Suite 300</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Los
Angeles, CA 90094-2536</span><span
style="font-size:11.0pt;font-family:"MS Gothic"">
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Email: <a
href="mailto:steve.chan@icann.org"
moz-do-not-send="true">
<span style="color:#0563C1">steve.chan@icann.org</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Skype:
steve.chan55</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Mobile:
+1.310.339.4410</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:black">Find out more about
the GNSO by visiting: <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e="
title="https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4Mxf"
moz-do-not-send="true"><span style="color:#0563C1">https://learn.icann.org/</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:black">Follow @GNSO on
Twitter: <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e="
title="https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjE"
moz-do-not-send="true"><span style="color:#0563C1">https://twitter.com/ICANN_GNSO</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:black">Transcripts and
recordings of GNSO Working Group and Council events are
located on the <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e="
moz-do-not-send="true"><span style="color:#0563C1">GNSO
Master Calendar</span><span style="color:#954F72"> </span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>council mailing list<o:p></o:p></pre>
<pre><a href="mailto:council@gnso.icann.org" moz-do-not-send="true" class="moz-txt-link-freetext">council@gnso.icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/council" moz-do-not-send="true" class="moz-txt-link-freetext">https://mm.icann.org/mailman/listinfo/council</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" moz-do-not-send="true" class="moz-txt-link-freetext">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" moz-do-not-send="true" class="moz-txt-link-freetext">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.<o:p></o:p></pre>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
</body>
</html>