<html>
<body>
Steve, thanks for volunterring for those docs for the privacy team; I
will update the checklist to reflect that now.<br><br>
And thanks for catching my error in the status column for the IWG docs
that Sana Ali volunteered to review. You are correct, those should have
been "A" not "S" as summaries for those have not yet
been submitted to this list. I will correct that status column right now
as well.<br><br>
Note that, when summaries are submitted, the "Reviewed by / Link
to" column will be hyperlinked to the email message containing the
summary. For this team, the only summary submitted as of the time that
I'm writing this is Kathy's summary of the obligations of data
controllers - follow the link to
<a href="http://mm.icann.org/pipermail/gnso-rds-pdp-privacy/2016-March/000018.html" eudora="autourl">
http://mm.icann.org/pipermail/gnso-rds-pdp-privacy/2016-March/000018.html</a>
You can also view summaries produced by the other two teams by
following links in their checklists, found at
<a href="https://community.icann.org/x/p4xlAw">
https://community.icann.org/x/p4xlAw</a><br><br>
Best, Lisa<br><br>
<br>
At 03:17 PM 4/6/2016, Metalitz, Steven wrote:<br>
<blockquote type=cite class=cite cite="">I will summarize the
following:<br>
<br>
<b>
<a href="https://www.icann.org/resources/pages/whois-privacy-conflicts-procedure-2008-01-17-en">
ICANN Procedure For Handling WHOIS Conflicts with Privacy Law</a>
(2008)<br>
and
<a href="http://gnso.icann.org/en/issues/whois-privacy/council-rpt-18jan06.htm">
GNSO Policy underlying current procedure</a><br>
<u>Review of the ICANN Procedure for Handling WHOIS Conflicts with
Privacy Law (2014)<br>
</u>Privacy & Proxy Services Accreditation PDP Final Report
(2015)<br>
Thick WHOIS PDP Final Report (2011-2013) and IRT Legal Review<br>
</b>I will do my best to have these summaries prepared prior to the next
WG call. <br>
I see that on this checklist, eight summaries are listed as “S”
meaning they have been submitted to the e-mail list. I seem to have
missed this distribution, although I have seen other e-mails to
this list from the assigned summarizers (Ali and Kleiman). Lisa,
would you mind re-sending or pointing us to these summaries so we can
consider using them as a template? Thanks. <br>
<br>
Steve Metalitz <br>
<b><u> <br>
</u> <br>
</b> <br>
I <br>
<br>
<img src="cid:6.2.3.4.2.20160406182540.130a4168@mail.corecom.com.1" width=124 height=41 alt="image001">
<br>
<b>Steven J. Metalitz </b>|<b> Partner, through his professional
corporation<br>
</b>T: 202.355.7902 | <a href="mailto:met@msk.com">met@msk.com</a><br>
<b>Mitchell Silberberg & Knupp</b> <b>LLP</b> |
<a href="http://www.msk.com/"><b>www.msk.com</a><br>
</b>1818 N Street NW, 8th Floor, Washington, DC 20036<br>
<br>
<b><u>THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY
FOR THE PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS.</u>
THIS MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS SUCH IS
PRIVILEGED AND CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT AN
INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REVIEW, USE,
DISSEMINATION, FORWARDING OR COPYING OF THIS MESSAGE IS STRICTLY
PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE,
AND DELETE THE ORIGINAL MESSAGE AND ALL ATTACHMENTS FROM YOUR SYSTEM.
THANK YOU.<br>
</b> <br>
<b>From:</b> gnso-rds-pdp-privacy-bounces@icann.org
[<a href="mailto:gnso-rds-pdp-privacy-bounces@icann.org" eudora="autourl">
mailto:gnso-rds-pdp-privacy-bounces@icann.org</a>] <b>On Behalf Of
</b>Lisa Phifer via Gnso-rds-pdp-privacy<br>
<b>Sent:</b> Wednesday, April 06, 2016 10:40 AM<br>
<b>To:</b> Gnso-rds-pdp-privacy<br>
<b>Subject:</b> [Gnso-rds-pdp-privacy] Privacy Team Checklist - 6
April<br>
<br>
Hello all,<br><br>
Today's updated privacy team checklist (attached) <br>
was just posted to the wiki at:<br>
<a href="https://community.icann.org/x/p4xlAw">
https://community.icann.org/x/p4xlAw</a><br><br>
Just follow the link above if you're looking for <br>
the latest daily update of any team's checklist.<br><br>
In today's checklist update, to make it clearer <br>
which docs are not yet assigned, I have removed <br>
the ? names from the "Reviewed by" column. As you <br>
can see, there are still plenty of docs <br>
identified by this team over the past week or so <br>
that could still use volunteers to review them. <br>
For those not certain how much work is involved: <br>
summaries should be concise - for example, <br>
"executive summaries" that point the WG to the <br>
portions of the document most relevant to RDS privacy and why.<br><br>
Best, Lisa<br><br>
<br>
At 11:49 AM 4/5/2016, David Cake via Gnso-rds-pdp-privacy wrote:<br><br>
<br>
>Please find attached a summary of the proposed <br>
>plan to finish the sub-teams input summarising <br>
>work as presented on todays call. Weâd like to >get this
document summarising work done (of <br>
>course, we know other relevant documents may be <br>
>published from here on, but we can handle those <br>
>as the come) so we can get back to full WG mode <br>
>and start proceeding with the rest of the work plan.<br>
><br>
>So what we are asking of you now is:<br>
><br>
>Please look at the input checklist provided, <br>
>choose at least one input (ideally one that has <br>
>not been looked at yet) that you are wiling to <br>
>summarise, and email the whole group to let them <br>
>know that you are working on it. Aim to have these summaries done by
Monday.<br>
>Please try to do this by the end of Wednesday.<br>
><br>
>This doesnât mean that we are necessarily done ne <br>
>with identification of new inputs - if you have <br>
>someone else valuable to add, feel free to <br>
>continue to do so. But the focus should now be on summarising what we
have.<br>
><br>
><br>
>David<br>
><br>
><br>
><br>
><br>
>_______________________________________________<br>
>Gnso-rds-pdp-privacy mailing list<br>
><a href="mailto:Gnso-rds-pdp-privacy@icann.org">
Gnso-rds-pdp-privacy@icann.org</a><br>
><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-privacy" eudora="autourl">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-privacy</a><br><br>
</blockquote></body>
</html>