<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">All,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">The first issue raised in this thread is a fact question with regard to what Annex 6 and Annex 12 actually say. I've gone back and looked at the Final Report and Annexes, dated February 23. Unfortunately, based on this review, there appear to be some errors in the email. It appears that an earlier version of CCWG Final Report and Annexes might have been used to grab the text quoted in the email. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">In Annex 6, <u>Paragraph 28</u> (not <u>Paragraph 14</u>) contains the operative language. It is almost, but not quite, the same as the language quoted in the email. In either case, the paragraph does not contain the "if any" identified by Brett Schaeffer. This paragraph is part of a section entitled "Detailed Explanation of Recommendations," in a subsection entitled "Operationalizing the Commitment to Respect Human Rights." However, this paragraph is probably not the right one to quote from Annex 6, as there is another similar paragraph (<u>Paragraph 7</u>) in Annex 6, but it's in the section entitled "CCWG-Accountability Recommendations," which would seem to make it more authoritative than Paragraph 28. Paragraph 7 <u>does</u> contain the "if any" identified by Brett.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Paragraph 7 reads as follows:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><p class="gmail-MsoListParagraphCxSpFirst" style="margin:8.6pt 0in 0.0001pt 1in;line-height:12.6pt;vertical-align:baseline"><font color="#0000ff"><span style="font-size:16.5pt;font-family:"courier new";letter-spacing:-0.05pt">o<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif;letter-spacing:-0.05pt">Include the following in Work Stream 2
activities:</span><span style="font-size:16.5pt;font-family:"segoe ui symbol",sans-serif;letter-spacing:-0.05pt"><span></span></span></font></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:2.2pt 0in 0.0001pt 1.5in;line-height:12.6pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:wingdings">§<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif">Develop an FOI-HR for the Human Rights Bylaw.<span></span></span></font></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:4.05pt 0.25in 0.0001pt 1.5in;line-height:12.6pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:wingdings;letter-spacing:-0.1pt">§<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman""> </span></span><span style="font-family:arial,sans-serif;letter-spacing:-0.1pt">Consider
which specific Human Rights conventions or other instruments, if any, should be
used by ICANN in interpreting and implementing the Human Rights Bylaw.<span></span></span></font></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:4.1pt 0.7in 0.0001pt 1.5in;line-height:12.6pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:wingdings">§<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif">Consider the policies and frameworks, if any, that ICANN needs to
develop or enhance in order to fulfill its commitment to respect Human Rights.<span></span></span></font></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:4.2pt 0.3in 0.0001pt 1.5in;line-height:12.6pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:wingdings">§<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif">Consistent with ICANN’s existing processes and protocols, consider
how these new frameworks should be discussed and drafted to ensure broad
multistakeholder involvement in the process.<span></span></span></font></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:4.05pt 0.25in 0.0001pt 1.5in;text-align:justify;line-height:12.6pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:wingdings">§<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman""> </span></span><span style="font-family:arial,sans-serif">Consider what effect, if
any, this Bylaw will have on ICANN’s consideration of advice given by the
Governmental Advisory Committee (GAC).<span></span></span></font></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:4.2pt 0in 0.0001pt 1.5in;text-align:justify;line-height:12.6pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:wingdings">§<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman""> </span></span><span style="font-family:arial,sans-serif">Consider how, if at all,
this Bylaw will affect how ICANN’s operations are carried out.<span></span></span></font></p>
<p class="gmail-MsoListParagraphCxSpLast" style="margin:4.1pt 0.45in 6pt 1.5in;text-align:justify;line-height:12.6pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:wingdings">§<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif">Consider how the interpretation and implementation of this Bylaw
will interact with existing and future ICANN policies and procedures.</span></font></p><p class="gmail-MsoListParagraphCxSpLast" style="margin:4.1pt 0.45in 6pt 1.5in;text-align:justify;line-height:12.6pt;vertical-align:baseline"><br></p></div><div class="gmail_default" style="font-family:verdana,sans-serif">Paragraph 28 reads as follows: </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default"><p class="MsoNormal" style="font-family:verdana,sans-serif;margin:0.1pt 0in 0.0001pt 0.05in;line-height:12.6pt;vertical-align:baseline"><font color="#0000ff"><span style="font-size:8pt;font-family:arial,sans-serif">28 </span><span style="font-family:arial,sans-serif">The Human Rights-related activities to be addressed in Work Stream
2 are:</span><span style="font-size:8pt;font-family:arial,sans-serif"><span></span></span></font></p>
<p class="MsoNormal" style="margin:6.85pt 0in 0.0001pt 0.85in;line-height:12.6pt;vertical-align:baseline"></p><ul><ul><li><font face="arial, helvetica, sans-serif" color="#0000ff">Developing an FOI-HR for the Bylaw.</font></li><li><font face="arial, helvetica, sans-serif" color="#0000ff">Considering which specific Human Rights conventions or other
instruments should be used by ICANN in interpreting and implementing the Bylaw.</font></li><li><font face="arial, helvetica, sans-serif" color="#0000ff">Considering the policies and frameworks, if any, that ICANN needs
to develop or enhance in order to fulfill its commitment to respect Human
Rights.</font></li><li><font face="arial, helvetica, sans-serif" color="#0000ff">Considering how these new frameworks should be discussed and
drafted to ensure broad multistakeholder involvement in the process, consistent
with ICANN’s existing processes and protocols.</font></li><li><font face="arial, helvetica, sans-serif" color="#0000ff">Considering what effect, if any, this Bylaw will have on ICANN’s
consideration of advice given by the GAC.</font></li><li><font face="arial, helvetica, sans-serif" color="#0000ff">Considering how, if at all, this Bylaw will affect how ICANN’s
operations are carried out once an FOI-HR is developed by the
CCWG-Accountability as a consensus recommendation in Work Stream 2 (including
Chartering Organizations’ approval) and the FOI-HR is approved by the ICANN
Board using the same process and criteria it has committed to use to consider
the Work Stream 1 recommendations</font></li><li><font face="arial, helvetica, sans-serif" color="#0000ff">Considering how the
interpretation and implementation of this Bylaw will interact with existing and
future ICANN policies and procedures.</font></li></ul></ul><p></p></div><div class="gmail_default" style="font-family:verdana,sans-serif">It appears that the "if any" was added to Paragraph 7 in the CCWG draft of February 17, but the conforming change to paragraph 28 was never made.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Annex 12 is also not accurately quoted. In the final version, <u>Paragraph 24</u> (not <u>Paragraph 18</u>) <u>does</u> contain the "if any" identified by Brett. Paragraph 24 differs slightly from the quoted Paragraph 18 in other ways as well. It reads:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><p class="MsoNormal" style="margin:16.9pt 0.1in 0.0001pt 0.35in;line-height:12.65pt;vertical-align:baseline"><font color="#0000ff"><span style="font-size:8pt;font-family:arial,sans-serif">24 </span><span style="font-family:arial,sans-serif">To ensure that adding the proposed Human Rights Bylaw provision
into the ICANN Bylaws does not lead to an expansion of ICANN’s Mission or
scope, the CCWG -Accountability will develop a Framework of Interpretation for
Human Rights (FOI-HR) as a consensus recommendation in Work Stream 2 to be
approved by the ICANN Board using the same process and criteria as for Work
Stream 1 recommendations, and the Bylaw provision will not enter into force
before the FOI-HR is in place. The CCWG-Accountability will consider the
following as it develops the FOI-HR:</span><span style="font-size:8pt;font-family:arial,sans-serif"><span></span></span></font></p>
<p class="MsoNormal" style="margin:6.6pt 0.1in 0.0001pt 0.85in;line-height:12.65pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:symbol">·<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif">Consider which specific Human Rights conventions or other
instruments, if any, should be used by ICANN in interpreting and implementing
the Human Rights Bylaw.<span></span></span></font></p>
<p class="MsoNormal" style="margin:6.9pt 0.15in 0.0001pt 0.85in;line-height:12.65pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:symbol">·<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif">Consider the policies and frameworks, if any, that ICANN needs to
develop or enhance in order to fulfill its commitment to respect Human Rights.<span></span></span></font></p>
<p class="MsoNormal" style="margin:6.65pt 0.5in 0.0001pt 0.85in;line-height:12.65pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:symbol">·<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif">Consistent with ICANN’s existing processes and protocols, consider
how these new frameworks should be discussed and drafted to ensure broad
multistakeholder involvement in the process.<span></span></span></font></p>
<p class="MsoNormal" style="margin:6.65pt 0.3in 0.0001pt 0.85in;line-height:12.65pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:symbol">·<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif">Consider what effect, if any, this Bylaw would have on ICANN’s
consideration of advice given by the Governmental Advisory Committee (GAC).<span></span></span></font></p>
<p class="MsoNormal" style="margin:6.8pt 0in 0.0001pt 0.85in;line-height:12.65pt;vertical-align:baseline"><font color="#0000ff"><span style="font-family:symbol">·<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></span><span style="font-family:arial,sans-serif">Consider how, if at all, this Bylaw will affect how ICANN’s
operations are carried out.<span></span></span></font></p>
<p class="MsoNormal" style="margin:6.85pt 0.1in 0.0001pt 0.85in;line-height:12.65pt;vertical-align:baseline"><span style="font-family:symbol"><font color="#0000ff">·<span style="font-variant-numeric:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"times new roman"">
</span></font></span><span style="font-family:arial,sans-serif"><font color="#0000ff">Consider how the interpretation and implementation of this Bylaw
will interact with existing and future ICANN policies and procedures.</font><font color="#000000"><span></span></font></span></p></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">It probably makes sense to send a revised letter with accurate quotations to the CCWG-Plenary, which doesn't meet for another week. I'm happy to prepare one and circulate it to the group.<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Apologies for the length of this email, but it's mostly quotes.</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">On Wed, Jan 4, 2017 at 3:17 PM, Nigel Roberts <span dir="ltr"><<a href="mailto:nigel@channelisles.net" target="_blank">nigel@channelisles.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just because you insist on something doesn't make you right.<br>
</blockquote></blockquote>
<br></span>
There's a saying in panto, which is traditional in this country at this time of year: "OH YES, IT DOES!"<br>
<br>
Actually, however, indeed, no, it doesn't.<br>
<br>
------------------------------<wbr>------------------------------<wbr>------------<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Man (Michael Palin): An argument isn't just contradiction.<br>
<br>
Mr. Vibrating (John Cleese): It can be.<br>
<br>
Man: No it can't. An argument is a connected series of statements intended to establish a proposition.<br>
<br>
Mr. Vibrating: No it isn't.<br>
<br>
Man: Yes it is! It's not just contradiction.<br>
<br>
Mr. Vibrating: Look, if I argue with you, I must take up a contrary position.<br>
<br>
Man: Yes, but that's not just saying 'No it isn't.'<br>
<br>
Mr. Vibrating: Yes it is!<br>
<br>
Man: No it isn't!<br>
<br>
Man: Argument is an intellectual process. Contradiction is just the automatic gainsaying of any statement the other person makes.<br>
<br>
(short pause)<br>
<br>
Mr. Vibrating: No it isn't.<br>
<br>
Man: It is.<br>
<br>
Mr. Vibrating: Not at all.<br>
<br>
Man: Now look!. (MONTY PYTHON: THE ARGUMENT CLINIC)<br>
</blockquote><div class="HOEnZb"><div class="h5">
______________________________<wbr>_________________<br>
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></blockquote></div><br></div>