<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Arial","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Arial","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>All,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Please see below for input to our meeting on Thursday.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thank-you.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Jonathan<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Ron Andruff [mailto:randruff@rnapartners.com] <br><b>Sent:</b> 02 September 2013 08:44<br><b>To:</b> jrobinson@afilias.info; gnso-improvem-impl-sc@icann.org<br><b>Subject:</b> SCI Charter Revisions<br><b>Importance:</b> High<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>Dear Jonathan,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>I understand that the GNSO Council will be discussing the SCI Charter revisions on its next call scheduled for September 5<sup>th</sup>, 2013. At its meeting on August 6th, 2013, the SCI members discussed the outcomes from the GNSO Sessions in Durban on this matter and decided that it would be helpful to more formally seek guidance from the Council with respect to the next steps for the SCI Charter. One aspect, in particular, based on the discussion in Durban, seems clear, i.e. that the GNSO Council would like the SCI to continue as a 'standing committee'. We would like the Charter to reflect that, should that indeed be the case. (I refer you to the email on this topic that I sent you on 08 July 2013, just prior to Durban.)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>At the Wrap-Up Session the GNSO Council also discussed the SCI process for decision-making (‘full consensus’ versus Standard Methodology for Making Decisions). The SCI understands that the Council agreed to consider this issue further on its mailing list and Council members were encouraged to share their views in support of one or the other option. We now understand that Jeff Neuman will provide background information as to why the SCI was initially required to operate under full consensus. At the SCI’s August 6<sup>th</sup> meeting and since then on our mailing list, members expressed an interest in helping guide the discussion for the Council as to why SCI members feel there should or should not be full consensus. <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>The impetus behind the recommendation to reconsider using “full or unanimous consensus” or “rough or near consensus” came from my request, as in-coming SCI Chair, to review and update the SCI Charter, as well as the SCI Wiki since the Committee now had over two years of experience behind it and the language in both the document and on the Wiki was outdated. I also noted at the time, and do so here again for Council’s edification, the SCI Charter is further governed by the GNSO Working Group Guidelines. The response within the SCI came in two forms: Those that feel that being forced to come to unanimous consensus “improves our product” because it ensures that the Committee dedicates the time to explore all points of view and works to find stronger outcomes; the arguments against full consensus included concerns about potentially using the SCI in a way that would drive substantive outcomes in the GNSO, whether intentionally or not, by pushing through decisions on procedure/process to meet an immediate need, or that any member choosing to remain steadfast in opposition could capture the SCI process. All SCI members however respect that balanced discussions result in consensus – in some form – leading to better appreciation of each member’s contributions, more confidence in the Committee itself and in the process. <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>The SCI has the luxury of not having to work under any time constraints on procedural and process issues (rather than substantive issues). Within the Standard Methodology for Making Decisions and the five forms of consent defined in the Guidelines, ‘rough or near consent’ (defined as “<i>a position where only a small minority disagrees, but most agree</i>”) immediately follows ‘full or unanimous consent’. We are all aware of the ramifications of full consensus, having worked under this standard since ICANN’s inception. ‘Near consensus’, provides the basis for Committee members to argue for their respective stakeholder group’s position, while it also provides for written rationale entered into the public record for any and all dissenting opinion(s), thus providing more context to the GNSO Council to assist it in coming to its own determinations. Notably, the SCI does not make any determinations other than to propose recommendations to the GNSO Council, which it, in turn, discusses, accepts, modifies or rejects, as Council deems appropriate. <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>On behalf of the SCI, we hope that this background information will inform your discussions, however the SCI would be happy to further brief the Council on the Charter and consensus issues, if so requested. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>We would also be grateful to know as soon as possible if the Council, as the Chartering organization, would prefer to take on the task of revising the SCI Charter or pass that responsibility to the SCI once it has made its determination on the consensus issue. The SCI stands ready to assist in this task in whichever way the Council deems appropriate.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>We await your guidance.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>Kind regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>Ron Andruff<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'>SCI Chair<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Ron Andruff<o:p></o:p></span></b></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>RNA Partners<o:p></o:p></span></b></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'><a href="http://www.rnapartners.com">www.rnapartners.com</a> <o:p></o:p></span></b></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div></body></html>