<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Consolas;
panose-1:2 11 6 9 2 2 4 3 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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.m734694327057617771gmail-
{mso-style-name:m_734694327057617771gmail-;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regarding the items listed by Greg, I do think it would be helpful to talk through these but I think it would
<u>unproductive to do so without putting the FOI itself out for public comment</u>. I strongly suggest we ask the plenary to put the draft FOI out for public comment and note in the public comment that we are asking for input in relation to certain of the
bullet points that Greg has outlined. (I copy the Chairs since I do not know whether there is any procedural barrier to such an approach and we want to do this in a way to complete work by May 2017.)<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">We are familiar with our own work and the reasoning and compromise behind it but we need a “check” on that work before we proceed with addressing suggestions
for items listed in Greg’s bullet points. <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">So I think we should ask the plenary to put the FOI out for interim public comment in the following manner:<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:11.0pt;font-family:"Calibri","sans-serif"">The CCWG-ACCT WS2 Human Rights subteam is soliciting public comment with respect to its draft Human Rights Framework of Interpretation. Input from public comment will
be considered by the subteam and will influence further work to be completed by the subteam no later than May 2017, including possible changes to the existing draft FOI. Such further work will primarily address suggestions for how the HR FOI should be interpreted
in relation to the following bullet points:<o:p></o:p></span></b></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"><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"><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>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#AF272F">Anne E. Aikman-Scalese</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">Of Counsel</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">520.629.4428 office</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt"></td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">520.879.4725 fax</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"><a href="mailto:AAikman@lrrc.com" target="_new" title="Email User"><span style="color:#323232">AAikman@lrrc.com</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">_____________________________</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"><img border="0" width="115" height="46" id="Picture_x0020_1" src="cid:image002.png@01D27AE8.CC46F790"></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">Lewis Roca Rothgerber Christie LLP</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">One South Church Avenue, Suite 700</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#323232">Tucson, Arizona 85701-1611</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"><a href="http://lrrc.com/" target="_new" title="Lewis Roca Rothgerber Christie Webpage"><span style="color:#323232">lrrc.com</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt"></td>
</tr>
</tbody>
</table>
<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 1:54 PM<br>
<b>To:</b> matthew shears; <ws2-hr@icann.org><br>
<b>Subject:</b> Re: [Ws2-hr] [Ws2-jurisdiction] [CCWG-ACCT] Scope of mandate on HR FOI<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Matthew,<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"">Thanks for your response, and I'm glad to see we are converging in our thinking. I'm replying primarily to redirect this to the Human Rights mailing list -- you replied to the one I sent
in error to the Jurisdiction list. Clearly a Freudian slip on my part.<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"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Jan 27, 2017 at 3:49 PM, matthew shears <<a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a>> wrote:<o:p></o:p></p>
<div>
<p>Hi Greg - yes, see inline<o:p></o:p></p>
<p class="MsoNormal">On 27/01/2017 19:42, Greg Shatan wrote:<br>
<br>
<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="color:black"> </span><span style="font-family:Symbol;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="color:black"> </span><span style="font-family:Symbol;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="color:black"> </span><span style="font-family:Symbol;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="color:black"> </span><span style="font-family:Symbol;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="color:black"> </span><span style="font-family:Symbol;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="color:black"> </span><span style="font-family:Symbol;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>
</div>
</div>
<p class="MsoNormal">I agree we need to have this discussion.<br>
<br>
<o:p></o:p></p>
<div>
<div>
<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">Agree. As I suggested in my e-mail.<br>
<br>
<o:p></o:p></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>
</div>
<p class="MsoNormal">Preferably one time - anything else will be confusing.<br>
<br>
<o:p></o:p></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">If it is appropriately considered and necessary, yes.<br>
<br>
<o:p></o:p></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.
<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Some of those bullets are clearly related to implementation - which is, while important to consider for the FoI, beyond our mandate. Now, if we wished to go down that route
that would be separate to the FoI.</span><br>
<br>
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">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-size:10.0pt;font-family:"Verdana","sans-serif"">A delicate balance for sure, but one we can address.<span style="color:#888888"><br>
<br>
<span class="hoenzb">Matthew</span></span></span><span style="font-family:"Verdana","sans-serif""><br>
<br>
</span><o:p></o:p></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""><o:p> </o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Greg<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""><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="m734694327057617771gmail-"> <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>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Ws2-jurisdiction mailing list<o:p></o:p></pre>
<pre><a href="mailto:Ws2-jurisdiction@icann.org" target="_blank">Ws2-jurisdiction@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" target="_blank">https://mm.icann.org/mailman/listinfo/ws2-jurisdiction</a><o:p></o:p></pre>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>------------<o:p></o:p></pre>
<pre>Matthew Shears<o:p></o:p></pre>
<pre>Global Internet Policy and Human Rights<o:p></o:p></pre>
<pre>Center for Democracy & Technology (CDT)<o:p></o:p></pre>
<pre><a href="tel:+44%207712%20472987" target="_blank">+ 44 771 2472987</a><o:p></o:p></pre>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Ws2-jurisdiction mailing list<br>
<a href="mailto:Ws2-jurisdiction@icann.org">Ws2-jurisdiction@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" target="_blank">https://mm.icann.org/mailman/listinfo/ws2-jurisdiction</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
<br>
</font>
</body>
</html>