<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=utf-8">
<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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.m-8339779776176025409hoenzb
{mso-style-name:m_-8339779776176025409hoenzb;}
span.m-8339779776176025409m4906796040590542517gmail-
{mso-style-name:m_-8339779776176025409m_4906796040590542517gmail-;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Good point Greg about choosing one list or the other rather than both – agree with your conclusion.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">David McAuley<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">International Policy Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Verisign Inc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">703-948-4154<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> ws2-hr-bounces@icann.org [mailto:ws2-hr-bounces@icann.org]
<b>On Behalf Of </b>Greg Shatan<br>
<b>Sent:</b> Friday, January 27, 2017 2:54 PM<br>
<b>To:</b> <ws2-hr@icann.org><br>
<b>Cc:</b> Tatiana Tropina<br>
<b>Subject:</b> [EXTERNAL] Re: [Ws2-hr] [CCWG-ACCT] Scope of mandate on HR FOI<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I was about to revise my email so it was more free-standing, and then post it to the Plenary list. But I stopped myself. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">We can respond to the Co-Chairs' email in one of two ways:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">1. We can take our discussion to the Plenary list and work it out there; or<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">2. We can work it out here and then come back to the Plenary ASAP with a consensus response. It doesn't have to be our Final Answer, but it should be something to reflect that we are considering
the advice and request from the Co-Chairs (and not rubber stamping "confirmed"). Eventually (and sooner than later), we will need our Final Answer, and then we'll need to do whatever we decide that dictates, if anything.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">What I don't think we should do is have some of us take this over to the Plenary list, and some of us stay over here. That won't really be productive, and may be counter-productive. So
I will not post my thoughts to the Plenary list, in favor of having us work out our position over here on the Human Rights list. (And not the Jurisdiction list either... Apologies for the mush-headed error...)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Greg<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""> <o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Jan 27, 2017 at 2:49 PM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">All,<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I tend to agree for the most part with Tatiana. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">We have been asked to "confirm that [the Human Rights subgroup] it has completed developing the Human Rights FOI per Annex 12." This can't be a rubber stamp.</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-family:"Verdana","sans-serif"">We
need to satisfy ourselves that this FoI really reflects <i>how</i> and <i>that </i>we have considered each of the following:</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.6pt;margin-right:.1in;margin-bottom:0in;margin-left:.9in;margin-bottom:.0001pt;line-height:12.65pt;vertical-align:baseline">
<span style="font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;color:black">
</span><span style="font-family:"Arial","sans-serif";color:black">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><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:6.9pt;margin-right:.15in;margin-bottom:0in;margin-left:.9in;margin-bottom:.0001pt;line-height:12.65pt;vertical-align:baseline">
<span style="font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;color:black">
</span><span style="font-family:"Arial","sans-serif";color:black">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><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:6.65pt;margin-right:.5in;margin-bottom:0in;margin-left:.9in;margin-bottom:.0001pt;line-height:12.65pt;vertical-align:baseline">
<span style="font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;color:black">
</span><span style="font-family:"Arial","sans-serif";color:black">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><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:6.65pt;margin-right:.3in;margin-bottom:0in;margin-left:.9in;margin-bottom:.0001pt;line-height:12.65pt;vertical-align:baseline">
<span style="font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;color:black">
</span><span style="font-family:"Arial","sans-serif";color:black">Consider what effect, if any, this Bylaw would have on ICANN’s consideration of advice given by the Governmental Advisory Committee (GAC).</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:6.8pt;margin-right:0in;margin-bottom:0in;margin-left:.9in;margin-bottom:.0001pt;line-height:12.65pt;vertical-align:baseline">
<span style="font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;color:black">
</span><span style="font-family:"Arial","sans-serif";color:black">Consider how, if at all, this Bylaw will affect how ICANN’s operations are carried out.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:6.85pt;margin-right:.1in;margin-bottom:0in;margin-left:.9in;margin-bottom:.0001pt;line-height:12.65pt;vertical-align:baseline">
<span style="font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;color:black">
</span><span style="font-family:"Arial","sans-serif";color:black">Consider how the interpretation and implementation of this Bylaw will interact with existing and future ICANN policies and procedures.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:6.85pt;margin-right:.1in;margin-bottom:0in;margin-left:.9in;margin-bottom:.0001pt;line-height:12.65pt;vertical-align:baseline">
<o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Do we want "consider" to be synonymous with "duly take into account" which can be satisfied by reviewing and considering an element (say, a public comment) and then
</span><span style="font-family:"Arial","sans-serif""></span><span style="font-family:"Verdana","sans-serif"">deciding that nothing will be as a result of that review? At the very least, we need to make sure we did the "review and consider" part. If no changes
need to be made in the FoI on a given point, then we should be able to say why we came to that conclusion.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Verdana","sans-serif"">We need to have a substantial discussion to determine whether the FoI reflects that we have considered each of these elements, and reflects the outcome of that consideration.</span></b><span style="font-family:"Verdana","sans-serif""><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Verdana","sans-serif"">Until we do this, I strongly question whether the Framework of Interpretation document is ready for Public Comment.</span></b><span style="font-family:"Verdana","sans-serif""> If we decided
that separate documents/annexes/etc. were needed, then perhaps this could be put out for comment. But I question that as well. Those really are parts of the FoI package, and would also need to be put out for Public Comment before the Bylaw graduates from
"dormant" status. Wouldn't it be better to have the whole package out there at once? As an alternative, we could put the FoI out for a second set of comments while putting the added pieces out for first comments (and possibly only comments).<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""></span><span style="font-family:"Verdana","sans-serif"">Also, the determination of the Co-Chairs</span><span style="font-family:"Arial","sans-serif""></span><span style="font-family:"Verdana","sans-serif"">
was that we follow Annex 12, rather than Annex 6. Annex 12 calls for a single integrated document reflecting all considerations. Annex 6 calls for follow-on documents. Since we are going with Annex 12 any additional material needed to reflect our "consideration"
<b>must be in the FoI itself.</b><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">One last point. I think that the open-ended invitation to "<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">develop suggestions for ICANN implementing the HR FOI<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""></span><span style="font-family:"Verdana","sans-serif"">"<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""> goes beyond our mandate. The only implementation advice we should be giving would be as a result of "considering" the 6 bullet points above. One could say there is an express or implied
element of implementation (or more accuerately "implementation guidance," which is not quite the same thing)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""></span><span style="font-family:"Verdana","sans-serif""> in each of these bullet points. A textual analysis of the Bylaw, no matter how excellent it is, does not satisfy any of these points.
And going beyond these points into an unfettered discussion of suggestions for Implementation would be going too far.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">So, I'm sorry to say, we're not there yet.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#888888"><o:p> </o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#888888">Greg<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""></span><span style="font-family:"Verdana","sans-serif""><o:p></o:p></span></p>
</div>
<p class="MsoNormal">On Fri, Jan 27, 2017 at 1:15 PM, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">Thanks, do find inline:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On Jan 26, 2017 2:11 PM, "León Felipe Sánchez Ambía" <<a href="mailto:leonfelipe@sanchez.mx" target="_blank">leonfelipe@sanchez.mx</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">Dear all,<span class="m-8339779776176025409m4906796040590542517gmail-"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Considering these and other factors the Co-Chairs would recommend that the Human Rights sub-group confirm that it has completed developing the Human Rights FOI per Annex 12 of the CCWG-Accountability WS1 Recommendations.<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">SO: Exact question that I have been asking as well, which also implies that it's not helpful to put the draft FoI to public comment without getting clear response on the point above!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Should the sub-group feel that it should develop suggestions for ICANN implementing the HR FOI based on its work to date the Co-Chairs would be amenable to this and would invite the HR sub-group to submit any such suggestions to the plenary
for consideration by early May 2017, if there was no objection from the plenary.<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">SO: May I ask the Co-Chairs to clarify what part of the WS1 report mandates the HR subgroup to carry out the task above or is this WS2 assigning a new task to the subgroup?. Like I have said, it seem to me that all HR needed to produce
was the FoI and they just need to confirm if the draft they sent was done is consideration of Annex 12 period!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thomas, Mathieu and León<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>