<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 9/7/2015 7:35 AM, William Drake wrote:<br>
<blockquote
cite="mid:1C00EAC8-07C6-4F47-8FA3-3B0EF67BA7A4@gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=us-ascii">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Sep 7, 2015, at 11:22 AM, Tapani Tarvainen
<<a moz-do-not-send="true"
href="mailto:ncuc@TAPANI.TARVAINEN.INFO" class="">ncuc@TAPANI.TARVAINEN.INFO</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span class="">compromise phrasing like "...
human rights, in particular</span><br class="">
<span class="">freedom of expression and privacy" might
work.</span></div>
</blockquote>
</div>
<br class="">
<div class="">
<div class="">
<div class="">Works for me, per the F2F discussions with other
stakeholders since summer 2014.</div>
</div>
</div>
</blockquote>
This makes sense and is advisable. <br>
<br>
I'm not sure it brings us to consensus, but I think it's worth doing
anyways. It avoids a fractured ICANN-specific HR framework, while
emphasizing the importance of the two rights that are most often
threatened in the ICANN context. I'd add due process.<br>
<br>
Best,<br>
Tamir
<blockquote
cite="mid:1C00EAC8-07C6-4F47-8FA3-3B0EF67BA7A4@gmail.com"
type="cite">
<div class="">
<div class="">
<div class=""><br class="">
</div>
<div class="">Bill</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>