<div dir="ltr">I'd be happy to help on this as appropriate. I have experience in analyzing, evaluating, and critiquing privacy policies of large multinationals with aims to improving their usefulness to end-users.<div>
<br></div><div>Cheers,</div><div>Chris</div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div>-- </div><div>*************************************************</div><div>Christopher Parsons</div><div>
Postdoctoral Fellow</div>
<div>Citizen Lab, Munk School of Global Affairs</div><div><a href="http://www.christopher-parsons.com" target="_blank">http://www.christopher-parsons.com</a></div><div>*************************************************</div>
</div></div>
<br><br><div class="gmail_quote">On 28 March 2014 10:30, Balleste, Roy <span dir="ltr"><<a href="mailto:rballeste@stu.edu" target="_blank">rballeste@stu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I agree with Avri. Will this be a new list for members interested in the subject? Or a list for members drafting policy positions on behalf of the membership? In the past, it was worked well when NPOC and NCUC worked together in policy positions.<br>
<br>
Roy Balleste<br>
Law Library Director &<br>
Professor of Law<br>
St. Thomas University Law Library<br>
16401 NW 37th Avenue<br>
Miami Gardens, FL 33054<br>
<a href="tel:305-623-2341" value="+13056232341">305-623-2341</a><br>
<div class=""><br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ncuc-discuss-bounces@lists.ncuc.org">ncuc-discuss-bounces@lists.ncuc.org</a> [mailto:<a href="mailto:ncuc-discuss-bounces@lists.ncuc.org">ncuc-discuss-bounces@lists.ncuc.org</a>] On Behalf Of Avri Doria<br>
Sent: Friday, March 28, 2014 5:30 AM<br>
To: <a href="mailto:ncuc-discuss@lists.ncuc.org">ncuc-discuss@lists.ncuc.org</a><br>
Subject: Re: [NCUC-DISCUSS] ICANN privacy policy<br>
<br>
</div><div><div class="h5">Hi,<br>
<br>
I am confused.<br>
<br>
<<a href="mailto:privacy@ipjustice.org">privacy@ipjustice.org</a>> is a relatively small list. Of course it looks like it could get bigger if everyone wants to join, but I don't see that as a problem as long as it does not get as big as NCUc or the NCSG<br>
<br>
I think that doing the work in a smaller open and archived group that focuses on just one subject is a good idea. I also think that we don't need separate privacy etc list for bot NCUC and NCSG. But I am one of the people that is less than excited about the competing constituency model and prefer the unified NCSG model.<br>
<br>
avri<br>
<br>
<br>
<br>
On 28-Mar-14 15:35, Stephanie Perrin wrote:<br>
> I understand why you want to do this. This is a working group, to<br>
> draft something. I hear rumours there are 350 people on the NCSG<br>
> discussion list. I have worked all year trying to get basic, basic<br>
> concepts of data protection law understood. I am not sure drafting<br>
> this thing in such a big group is efficient. i have no objections<br>
> sending the small group's concensus draft from the working group to<br>
> the larger list, but I am mindful of Bill's admonition to keep the<br>
> traffic low. if we start discussing definitions, frameworks,<br>
> jurisdiction, related constitutional protections (remembering there<br>
> are at least 50 jurisdictions out there with data protection law,) we<br>
> will never get this thing done. It is supposed to be a short gap<br>
> analysis of their privacy policy, that is all, not a draft of a new<br>
> privacy policy. If that were what we are doing, then maybe we would<br>
> have to do it in the bigger group. Just saying. EPIC and PI found it<br>
> a total nightmare in recent years trying to update the Privacy and<br>
> Human RIghts Law Handbook, it is just too big now (see link<br>
> <a href="http://www.worldlii.org/int/journals/EPICPrivHR/2006/PHR2006-Defining" target="_blank">http://www.worldlii.org/int/journals/EPICPrivHR/2006/PHR2006-Defining</a>.<br>
</div></div>> html) I will abide by the decision of this group, but I will also feed<br>
<div class="HOEnZb"><div class="h5">> my draft in to the EWG if we bog down and cannot reach agreement. we<br>
> have a major admission that they need advice, STeve is happy to get<br>
> it, we gotta move. Cheers SP PS Here is the link to the framework I<br>
> intend to reference (mostly because it is dated 2002 and I want to<br>
> underscore just how late ICANN is in recognizing its<br>
> responsibilities), referring of course to recent updates in EU law,<br>
> proposed regulation, and the guidance on binding corporate rules from<br>
> the Art 29 group.<br>
> <a href="http://danskprivacynet.files.wordpress.com/2008/06/ipse_finalreport1.pdf" target="_blank">http://danskprivacynet.files.wordpress.com/2008/06/ipse_finalreport1.pdf</a>.<br>
> If anyone can think of a decent US document to cite, I am all ears,<br>
> but I am not aware of one. ________________________________________<br>
> From: <a href="mailto:ncuc-discuss-bounces@lists.ncuc.org">ncuc-discuss-bounces@lists.ncuc.org</a><br>
> <<a href="mailto:ncuc-discuss-bounces@lists.ncuc.org">ncuc-discuss-bounces@lists.ncuc.org</a>> on behalf of Avri Doria<br>
> <<a href="mailto:avri@acm.org">avri@acm.org</a>> Sent: March 27, 2014 10:11 PM Cc:<br>
> <a href="mailto:ncuc-discuss@lists.ncuc.org">ncuc-discuss@lists.ncuc.org</a> Subject: Re: [NCUC-DISCUSS] ICANN privacy<br>
> policy<br>
><br>
> On 27-Mar-14 13:13, Amr Elsadr wrote:<br>
>> I think it is important to decide early on wether we are going to<br>
>> have separate discussions regarding ICANN's privacy and data<br>
>> protection policies within their own corporate practices and within<br>
>> the policies developed through the GNSO impacting obligations imposed<br>
>> on contracted parties, or not.<br>
><br>
> I suggest we stick to one NCSG wide discussion space for all of this.<br>
><br>
> avri _______________________________________________ Ncuc-discuss<br>
> mailing list <a href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a><br>
> <a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><br>
><br>
><br>
_______________________________________________<br>
Ncuc-discuss mailing list<br>
<a href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><br>
_______________________________________________<br>
Ncuc-discuss mailing list<br>
<a href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><br>
</div></div></blockquote></div><br></div>