<html>
<body>
Stephanie, yes, that public memo is in the Privacy small team's input
list, as it was identified as an input to this PDP's question on Privacy
in the process framework and thus charter.<br><br>
You can find it posted here in the EWG's public wiki:<br><br>
<a href="https://community.icann.org/download/attachments/43982771/Memo%20to%20EWG%20re%20gTLD%20Registration%20Data%20and%20International%20Data%20Privacy%20Considerations.docx" eudora="autourl">
https://community.icann.org/download/attachments/43982771/Memo%20to%20EWG%20re%20gTLD%20Registration%20Data%20and%20International%20Data%20Privacy%20Considerations.docx<br>
<br>
</a>It's also on this PDP WG's wiki in a couple of places, where you will
find it entitled:<br><br>
EWG
Research:<a href="https://community.icann.org/download/attachments/43982771/Memo%20to%20EWG%20re%20gTLD%20Registration%20Data%20and%20International%20Data%20Privacy%20Considerations.docx">
Data Protection Considerations Applicable to Collection of gTLD Reg Data
Memo</a> <br><br>
<br>
Steve, the Thick to Think memo is also on this PDP WG's wiki, but
highlighted under a different question (system model). I'll add to the
privacy inputs list now, but in the meantime, the two wiki links
associated with that input are:<br><br>
<a href="http://gnso.icann.org/en/issues/whois/thick-final-21oct13-en.pdf">
Thick WHOIS PDP Final Report</a> (2011-2013) and
<a href="https://community.icann.org/download/attachments/52889541/ICANN%20Memorandum%20to%20the%20IRT%20-%20Thin%20to%20Thick%20WHOIS%20Transition_Final_2015-06-08.pdf">
IRT Legal Review</a> <br><br>
Best, Lisa<br><br>
<br>
At 12:56 PM 4/4/2016, Stephanie Perrin wrote:<br>
<blockquote type=cite class=cite cite="">It might be useful to supplement
that with the report presented to the EWG on legal considerations, dated
August 2013. Before attaching that report, as it was supplied in
confidence to the EWG, and I cannot figure out whether it is on the
public part of the EWG website or not, I would ask Lisa if it is ok to
circulate that email. Nothing earth shattering in there in my view,
and it not marked solicitor-client privilege, so I would think we could
distribute it but I am not the boss.<br>
cheers Stephanie<br><br>
On 2016-04-04 14:43, Metalitz, Steven via Gnso-rds-pdp-privacy
wrote:<br>
<blockquote type=cite class=cite cite="">This is indeed an impressive
compendium of documents, which Kathy has subsequently supplemented
further. One of our challenges will be to maintain a focus on those
resources most directly relevant to our tasks (as distinguished from
privacy/data protection topics more generally). <br>
<br>
In that regard, I’ll suggest one additional document which is focused on
an aspect of RDS: the legal review memorandum prepared by ICANN
(with outside counsel assistance) pursuant to the Board resolution
adopting thick Whois architecture as a consensus policy applicable to all
gTLD registries. It can be found at Legal Review Memorandum (8 June
2015):
<a href="https://community.icann.org/download/attachments/52889541/ICANN%20Memorandum%20to%20the%20IRT%20-%20Thin%20to%20Thick%20WHOIS%20Transition_Final_2015-06-08.pdf?version=1&modificationDate=1434138098000&api=v2">
ICANN Memorandum to the IRT - Thin to Thick WHOIS
Transition_Final_2015-06-08.pdf</a>. <br>
<br>
<img src="cid:6.2.3.4.2.20160404130821.11eba3e8@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 & KnuppLLP</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>
<a href="mailto:gnso-rds-pdp-privacy-bounces@icann.org">
gnso-rds-pdp-privacy-bounces@icann.org</a>
[<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>David Cake via Gnso-rds-pdp-privacy<br>
<b>Sent:</b> Wednesday, March 30, 2016 11:28 AM<br>
<b>To:</b>
<a href="mailto:gnso-rds-pdp-privacy@icann.org">
gnso-rds-pdp-privacy@icann.org</a><br>
<b>Subject:</b> [Gnso-rds-pdp-privacy] Template for Privacy team
output<br>
<br>
To coordinate our work, staff have created a Template that suggests the
form our output should take, and that includes a list of the many
documents already suggested as relevant to this teams work. It is
attached to this message.<br><br>
Please note that the list of documents is quite extensive already - which
certainly doesn’t mean we can’t add more. <br><br>
I’d like volunteers to start looking at documents added and summarising
some of their contents. Summaries should focus on describing its
relevance to our work, and the questions it addresses, rather than
opinions about the substantive issues it covers. <br><br>
Regards<br><br>
David<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://protect-us.mimecast.com/s/NV8XBVh95doTx" eudora="autourl">
https://protect-us.mimecast.com/s/NV8XBVh95doTx</a><br><br>
<br><br>
<pre>_______________________________________________
Gnso-rds-pdp-privacy mailing list
<a href="mailto:Gnso-rds-pdp-privacy@icann.org">
Gnso-rds-pdp-privacy@icann.org</a>
<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></pre>
</blockquote><br><br>
</blockquote></body>
</html>