<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">The CCWG Charter contains the following definitions:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="color:rgb(51,51,51)"><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><b><span style="color:rgb(51,51,51)">a) Full Consensus - a position where no minority disagrees; identified by an absence of objection</span><br></b></div><div class="gmail_default"><p style="margin:10px 0px 0px;padding:0px;color:rgb(51,51,51)"><font face="verdana, sans-serif"><b>b) Consensus – a position where a small minority disagrees, but most agree</b></font></p><p style="margin:10px 0px 0px;padding:0px;color:rgb(51,51,51)"><font face="verdana, sans-serif">It would be helpful to use these terms, to reflect the Charter and to avoid miscommunication. "Agreement" is not a defined term, and should be avoided. Using the terms above, the proper course of action should read:</font></p><p style="margin:10px 0px 0px;padding:0px"><font color="#333333" face="verdana, sans-serif">1.The subgroup should conduct the primary discussion and interpretation of its mandate.</font></p><p style="margin:10px 0px 0px;padding:0px"><font color="#333333" face="verdana, sans-serif">2. Should Consensus (NOT simple Majority/Minority and NOT Full Consensus) be reached the subgroup should then bring the matter (i.e., the Consensus conclusion of the subgroup) to the attention of Plenary for approval.</font></p><p style="margin:10px 0px 0px;padding:0px"><font color="#333333" face="verdana, sans-serif">3. Should Consensus (NOT simple Majority/Minority and NOT Full Consensus) not be reached the subgroup should then bring the matter (i.e., the alternative conclusions under consideration in the subgroup) to the attention of Plenary for advice, which may include a Consensus conclusion by the Plenary regarding the mandate of the subgroup.</font></p><p style="margin:10px 0px 0px;padding:0px"><font face="verdana, sans-serif">4. The subgroup should proceed accordingly (i.e., follow the mandate approved or decided by the Plenary, or follow the advice of the Plenary if the Plenary only offers advice).</font></p><p style="margin:10px 0px 0px;padding:0px"><br></p><p style="margin:10px 0px 0px;padding:0px">Greg<br></p><p style="margin:10px 0px 0px;padding:0px"><br></p><p style="font-family:arial,sans-serif;margin:10px 0px 0px;padding:0px;color:rgb(51,51,51);font-size:14px"> </p></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 8, 2017 at 1:30 AM, Kavouss Arasteh <span dir="ltr"><<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Dear All,</div><div>With respect to Niels message:</div><div>My understanding was that Niels asked the subgroup to discuss the interpretation of its mandate .</div><div>You understood Niels message was addressed to the Plenary for which I fully agree</div><div>However, if Niels want to discuss the matter at the level of subgroup the following course of action is necessary:</div><div>1.The subgroup could start the primary discussion and interpretation of its mandate.</div><div>2. Should Agreement or Consensus ( NOT Majority / Minority and NOT Soft or Rough Consensus) is reached the subgroup should then bring the matter to the attention of Plenary <font color="#ff0000">for approval</font></div><div>3. Should Agreement or Consensus ( NOT Majority / Minority and NOT Soft or Rough Consensus) is not reached the subgroup should then bring the matter to the attention of Plenary <font color="#ff0000">for advice.</font></div><div><font color="#ff0000"></font><span>If the above course of action is consented,then the sub group should proceed accordingly</span></div><div><span>Regards</span></div><span class="HOEnZb"><font color="#888888"><div><span>Kavouss </span></div><div><span> </span></div><div><br></div><div><span><br></span></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2017-01-08 1:46 GMT+01:00 Greg Shatan <span dir="ltr"><<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Niels's email is addressed to the CCWG-Plenary.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">With regard to discussions at the subgroup level, the subgroup is the proper place for the primary discussion and interpretation of the subgroup's mandate. The conclusions of the subgroup should then be brought back to the Plenary for approval. If the subgroup cannot agree on an interpretation of the mandate, or if (as here) the subgroup perceived a need for clarification from the Plenary, then (as here), the subgroup should go back to the Plenary for advice. Which is exactly what Niels has done.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Best regards,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_-4732409171871985664h5">On Sat, Jan 7, 2017 at 12:53 PM, Kavouss Arasteh <span dir="ltr"><<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div><div class="m_-4732409171871985664h5"><div dir="ltr"><div>Dear Niels,</div><div>Dear Neils,</div><div>Thank you for your message and updates</div><div>Pls kindly note that the subgroup is not eligible to interprète its mandater .The mandate was established by the higher level in other words and any interprétation requires the advice from that higher level</div><div>Homewear, you may start to discuss the issue on preliminary basis but you need to report to CCWG Plenary ,including advice from its CO- CHAIR.</div><div>Please kindly take such action to avoid another series of complex discussion pros and cones on the issue .</div><div>Regards</div><span class="m_-4732409171871985664m_6013500822549031577HOEnZb"><font color="#888888"><div>Kavouss </div></font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_-4732409171871985664m_6013500822549031577h5">2017-01-07 18:30 GMT+01:00 Niels ten Oever <span dir="ltr"><<a href="mailto:lists@nielstenoever.net" target="_blank">lists@nielstenoever.net</a>></span>:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div><div class="m_-4732409171871985664m_6013500822549031577h5">Dear all,<br>
<br>
Please refer to this version of the email instead. The prior version<br>
<span>inadvertently quoted from a draft version of the WS1 report.<br>
<br>
<br>
</span><span>We hope this email finds you all very well. As you all know we shared<br>
with you the Framework of Interpretation of the Human Rights bylaw.<br>
After this the Human Rights Subgroup worked on next steps, which led us<br>
to taking a close look at our mandate and finding that there are<br>
different ways of interpreting this. This difference stems, in part,<br>
from the different constructions of our mandate in Annex 6 and in Annex 12.<br>
<br>
That is why we come to you for guidance to see where we are, and where<br>
we should go next.<br>
<br>
In a bit more detail:<br>
<br>
</span>Paragraph 7 of Annex 6 of the CCWG reads:<br>
<span><br>
Include the following in Work Stream 2 activities:<br>
Develop an FOI-HR for the Human Rights Bylaw.<br>
</span>Consider which specific Human Rights conventions or other instruments,<br>
if any, should be used by ICANN in interpreting and implementing the<br>
<span>Human Rights Bylaw.<br>
Consider the policies and frameworks, if any, that ICANN needs to<br>
</span>develop or enhance in order to fulfill its commitment to respect Human<br>
<span>Rights.<br>
Consistent with ICANN’s existing processes and protocols, consider how<br>
these new frameworks should be discussed and drafted to ensure broad<br>
multistakeholder involvement in the process.<br>
</span>Consider what effect, if any, this Bylaw will have on ICANN’s<br>
<span>consideration of advice given by the Governmental Advisory Committee (GAC).<br>
Consider how, if at all, this Bylaw will affect how ICANN’s operations<br>
are carried out.<br>
Consider how the interpretation and implementation of this Bylaw will<br>
interact with existing and future ICANN policies and procedures.<br>
<br>
</span>Whereas Paragraph 24 of Annex 12 of the CCWG report reads:<br>
<br>
.24 To ensure that adding the proposed Human Rights Bylaw provision<br>
<span>into the ICANN Bylaws does not lead to an expansion of ICANN’s Mission<br>
</span>or scope, the CCWG -Accountability will develop a Framework of<br>
<span>Interpretation for Human Rights (FOI-HR) as a consensus recommendation<br>
in Work Stream 2 to be approved by the ICANN Board using the same<br>
process and criteria as for Work Stream 1 recommendations, and the Bylaw<br>
provision will not enter into force before the FOI-HR is in place. The<br>
</span>CCWG-Accountability will consider the following as it develops the FOI-HR:<br>
Consider which specific Human Rights conventions or other instruments,<br>
if any, should be used by ICANN in interpreting and implementing the<br>
<span>Human Rights Bylaw.<br>
Consider the policies and frameworks, if any, that ICANN needs to<br>
</span>develop or enhance in order to fulfill its commitment to respect Human<br>
<span>Rights.<br>
Consistent with ICANN’s existing processes and protocols, consider how<br>
these new frameworks should be discussed and drafted to ensure broad<br>
multistakeholder involvement in the process.<br>
</span>Consider what effect, if any, this Bylaw would have on ICANN’s<br>
<div><div class="m_-4732409171871985664m_6013500822549031577m_3104645358718055431h5">consideration of advice given by the Governmental Advisory Committee (GAC).<br>
Consider how, if at all, this Bylaw will affect how ICANN’s operations<br>
are carried out.<br>
Consider how the interpretation and implementation of this Bylaw will<br>
interact with existing and future ICANN policies and procedures.<br>
<br>
Annex 6 makes it seem like each of the “bullet points” is a separate<br>
task, starting with the Framework of Interpretation. On the other hand,<br>
Annex 12 makes it seem like the “bullet points” are not really separate<br>
tasks, but only items to be considered as we prepare the Framework of<br>
Interpretation. This makes a significant difference in how we determine<br>
what work lies before us, and also how we look at the Framework of<br>
Interpretation we have completed.<br>
<br>
In our initial work we focused on providing a Framework of<br>
Interpretation of the Bylaw, clearly stating how it should be<br>
interpreted, and we did not focus on how the Bylaw could be<br>
“operationalized”, even though of course we considered the potential<br>
consequences this might have.<br>
<br>
The question is now, what are the next steps? We see different options:<br>
<br>
1. We're done. The FoI is developed, and under consideration by the plenary.<br>
2. We need to have a second look at the FoI and make potential<br>
amendments to the FoI to give more guidance based on the considerations<br>
listed in Annex 6.<br>
3. We need to produce a new document that responds directly to each of<br>
the “bullet points,” which could include examples and recommendations on<br>
what potential next steps could be<br>
4. We need to test specific cases on a hypothetical basis to see<br>
whether the FoI suffices. (in this regard, hypothetical cases suggested<br>
by the plenary would be helpful.)<br>
<br>
We've have made first steps into the direction of step 3, but this led<br>
us into quite detailed discussions on recommending the use of Human<br>
Rights Impact Assessments and how and where these could be integrated in<br>
PDPs and ICANN operations. In these discussions, it felt as though we<br>
were going into too much detail, and stepping outside of the mandate of<br>
our Subgroup.<br>
<br>
5. A fifth option could be (and this might be a mix between option 1<br>
and 3) to issue high-level recommendations on how ICANN and the SO’s and<br>
AC’s could best operationalize the core value contained in the Human<br>
Rights Bylaw. These recommendations could include (a) chartering a GNSO<br>
Working Group on Human Rights to consider and recommend how the Bylaw<br>
should be taken into account in gTLD policy development and<br>
implementation, and/or (b) chartering Working Groups in each of the<br>
other SO’s and AC’s for purposes relevant to their remit, and/or (c)<br>
chartering a new CCWG on Human Rights to specifically consider the steps<br>
needed to make the Bylaw operational, and provide guidance to each of<br>
the SO's and AC's on how they could incorporate the CCWG’s output in<br>
their processes, as well as discussing measures that could be adopted by<br>
ICANN, the corporation, with respect to its own internal human<br>
resources, employment, and contracting practices based on the Bylaw.<br>
<br>
We would like to bring these five options in front of the plenary, and<br>
we would greatly appreciate your thoughts on these and potentially other<br>
options.<br>
<br>
The Human Rights Subgroup wishes you a revitalizing festive season and<br>
we're greatly looking forward to completing our work in Workstream 2<br>
with you all in 2017.<br>
<br>
All the best,<br>
<br>
The CCWG Accountability Human Rights Subgroup<br>
<br>
</div></div>PS Thanks Greg and Brett for finding this error and for helping to<br>
correct it.<br>
<span class="m_-4732409171871985664m_6013500822549031577m_3104645358718055431im m_-4732409171871985664m_6013500822549031577m_3104645358718055431HOEnZb">--<br>
Niels ten Oever<br>
Head of Digital<br>
<br>
Article 19<br>
<a href="http://www.article19.org" rel="noreferrer" target="_blank">www.article19.org</a><br>
<br>
PGP fingerprint 8D9F C567 BEE4 A431 56C4<br>
678B 08B5 A0F2 636D 68E9<br>
______________________________<wbr>_________________<br>
</span></div></div><span><div class="m_-4732409171871985664m_6013500822549031577m_3104645358718055431HOEnZb"><div class="m_-4732409171871985664m_6013500822549031577m_3104645358718055431h5">Ws2-hr mailing list<br>
<a href="mailto:Ws2-hr@icann.org" target="_blank">Ws2-hr@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-hr" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ws2-hr</a><br>
</div></div></span></blockquote></div><br></div>
<br></div></div><span>______________________________<wbr>_________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community<wbr>@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/accountability-cross-c<wbr>ommunity</a><br>
<br></span></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>