<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font size="+1"><font face="Lucida Grande">Thanks Chuck, for this
reminder. One of the key reasons I keep pounding away on the
need to go back to basics and discuss the purpose of ICANN
governing, through the RAA and other instruments, the
collection, use and disclosure of registrant data, is to get
to the bottom of how it sets policy for information
governance. This is because we need to be sure that all
aspects of information governance are within its mandate. IF
it has strayed into serving the information desires (I will
not accept the use of the term "needs") of a growing host of
information users, this indeed mirrors what has happened in
the online world (how fondly we privacy advocates look back on
the first cookies scandals back in 1996-2000, as compared with
the network advertising initiative and its members' activities
after the Doubleclick debacle, let alone what goes on today).
It does not make it right, from a perspective of fundamental
rights. Certainly, the horse has long since left the barn,
but the unhappy job of regulators (and the civil society who
fight alongside them but often wish they would do a better job
of it) is always to go and find the horse and get it back to
the barn, an often thankless task.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">I have had the
opportunity lately of trying to explain to both academics and
data commissioners exactly how information is managed at
ICANN, now that I appear to have a better handle on it. It is
crystal clear that getting a grip on this, if one is not
immersed in ICANN or the domain name management business, is
not that easy. For instance, I suspect (but have nothing but
apocryphal data collected to support) that data commissioners
have spent more time discussing whois policy with their cctld
managers, failing to understand that ICANN has less influence
on these matters. They have focused less on the RAA. It
might be useful for this team to either get a briefing, or get
the documentation arising from, Nigel Hickson's trip to
Germany to discuss the correspondence/impasse between ICANN
and the article 29 group with respect to waivers and the RAA
more generally. If we have a report on that in our document
list, I have somehow missed it. </font></font><br>
</p>
Kind regards, <br>
Stephanie<br>
<div class="moz-cite-prefix">On 2016-04-27 0:58, Gomes, Chuck wrote:<br>
</div>
<blockquote
cite="mid:6DCFB66DEEF3CF4D98FA55BCC43F152E4AEE2F00@BRN1WNEXMBX01.vcorp.ad.vrsn.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Gulim;
        panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
        {font-family:Gulim;
        panose-1:2 11 6 0 0 1 1 1 1 1;}
@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:"\@Gulim";
        panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
        {font-family:GulimChe;
        panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
        {font-family:"\@GulimChe";
        panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
        {font-family:"Comic Sans MS";
        panose-1:3 15 7 2 3 3 2 2 2 4;}
@font-face
        {font-family:"Lucida Grande";
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Gulim","sans-serif";
        mso-fareast-language:KO;}
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:"Gulim","sans-serif";
        mso-fareast-language:KO;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:GulimChe;
        mso-fareast-language:KO;}
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";
        mso-fareast-language:KO;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        mso-fareast-language:KO;}
span.EmailStyle20
        {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";
        mso-fareast-language:KO;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">With
regard to the RAA as well as registry agreements with gTLD
registries, one of the possible outcomes of this WG is the
recommendation of consensus policies. As I think many of you
know, gTLD registries and registrars are required in their
agreements to implement consensus policies approved by the
Board so the consensus policies would become a requirement
in the applicable agreements.<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">Chuck<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>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<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"">
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-purpose-bounces@icann.org">gnso-rds-pdp-purpose-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-rds-pdp-purpose-bounces@icann.org">mailto:gnso-rds-pdp-purpose-bounces@icann.org</a>]
<b>On Behalf Of </b>Susan Kawaguchi<br>
<b>Sent:</b> Tuesday, April 26, 2016 4:01 PM<br>
<b>To:</b> Stephanie Perrin;
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-purpose@icann.org">gnso-rds-pdp-purpose@icann.org</a><br>
<b>Subject:</b> Re: [gnso-rds-pdp-purpose] Additional
Information/question<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Hi
Stephanie, <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">I
disagree that we accepted the RAA as fait accompli. I
think the whole EWG team spent many hours discussing
any view point in reference to registration data
purpose, collection and display. We also reviewed any
document that was brought to our attention from DPA’s
or Article 29 WP. We may not have agreed on the
interpretation and meaning of those documents but we
discussed data collection and privacy more than any
other topic since it was so crucial to our work. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Best, <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Susan
Kawaguchi<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Domain
Name Manager <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Facebook
Legal Dept. <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:
</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><<a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-purpose-bounces@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-purpose-bounces@icann.org">gnso-rds-pdp-purpose-bounces@icann.org</a></a>>
on behalf of Stephanie Perrin <<a
moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca"><a class="moz-txt-link-abbreviated" href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a></a>><br>
<b>Date: </b>Monday, April 25, 2016 at 9:11 AM<br>
<b>To: </b>"<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-purpose@icann.org">gnso-rds-pdp-purpose@icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-purpose@icann.org">gnso-rds-pdp-purpose@icann.org</a>><br>
<b>Subject: </b>Re: [gnso-rds-pdp-purpose] Additional
Information/question<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p><span style="font-size:18.0pt;font-family:"Lucida
Grande","serif";color:black">I would
actually disagree. We discussed the use cases for data,
accepting those current uses as by and large
legitimate. From a data protection perspective, it has
been clear from the very beginning that many of the new
purposes that registrant data were being put to, would
not be permissible by law under the original purpose of
WHOIS. We never looked at the collection instrument,
(RAA) it was accepted as fait accompli. We did not go
over the extensive collection of documents that we had
received from the DPAs. So a thorough, tabula rasa
discussion of the purpose of collection of registrant
data is in order, in my view. And SAC 055 agrees with
that view.</span><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p><span style="font-size:18.0pt;font-family:"Lucida
Grande","serif";color:black">Stephanie
Perrin</span><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">On
2016-04-25 17:34, Carlton Samuels wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black">...and FWIW, the Review
Team's final report was a very important substrate
upon which the EWG's work was advanced.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black">The EWG spent an inordinate
amount of time resolving the question as to
whether there was a purposeful need for
registration data and if so, what should be
collected, the standards for collection, how it
should be curated and the safeguards, why and how
it should be published and the mechanisms for
publication.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black">I say again, it would be a
sign of malignancy to embrace any attempt to
bounce the rubble here. If there is new and
original insight of value to the end game, let it
be heard. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black">Otherwise, enough good minds
and treasure are exhausted answering those
questions. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black">Lets get on with it.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Comic Sans
MS";color:black">-Carlton<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><br
clear="all">
<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><br>
==============================<br>
Carlton A Samuels<br>
Mobile: 876-818-1799<br>
</span><i><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#33CC00">Strategy,
Planning, Governance, Assessment &
Turnaround</span></i><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><br>
=============================<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">On
Mon, Apr 25, 2016 at 8:08 AM, Kathy Kleiman <<a
moz-do-not-send="true"
href="mailto:kathy@kathykleiman.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:kathy@kathykleiman.com">kathy@kathykleiman.com</a></a>>
wrote:<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Hi
Marika and All,
<br>
I think my concerns run to (iii) and (v) below
as the limitations of certain documents
(especially ones people refer to often) have
definitely been a part of the discussion of this
subgroup. I would note that certain document in
the summaries already contain some red
highlighted notes, and I would like to request
that similar notes be added *within our summary*
of the Whois Review Team Final Report and within
our subgroup report to the full WG. Here are the
bullet points you requested (tx for asking!):<br>
<br>
- The Whois Review Team was<i> expressly barred
from looking at the purpose of the Whois
system</i>. It was allowed to look only at
ICANN's "existing policy relating to WHOIS" per
the Affirmation of Commitments signed between US
Department of Commerce and ICANN in 2009. <br>
<br>
- Even within that scope, the Whois Review Team
Final Report expressly recommended protection of
privacy for commercial companies, noncommercial
organizations and individuals (finding that each
shared with us legal and legitimate reasons for
privacy including as-yet-unannounced mergers,
new movie names, unpopular religious, ethnic and
policy views, etc).
<br>
<br>
- The Whois Review Team Final Report advised
ICANN to work towards a standard of
"contactability"
<i>- reaching the registrant by some means
rather than all means </i>- which we wrote
as: "ICANN should take appropriate measures to
reduce the number of WHOIS registrations that
fall into the accuracy groups Substantial
Failure and Full Failure (as defined by the NORC
Data Accuracy Study, 2009/10..." p. 87.<br>
<br>
We were tasked with conveying to the full WG our
understanding of "purpose" as guided by these
documents - and these notes add key insights and
understandings to it (as we shared many times in
presenting this Final Report to ICANN in 2012).
<br>
<br>
Best,<br>
Kathy <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><br>
<br>
On 4/24/2016 8:35 PM, Marika Konings wrote:<br>
<br>
<o:p></o:p></span></p>
<pre><span style="color:black">Kathy, all, as a reminder, each sub-team is expected to answer the<o:p></o:p></span></pre>
<pre><span style="color:black">following questions in relation to the work it has undertaken:<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">(i) Did this input inventory produce any insights to inform the WG¹s work<o:p></o:p></span></pre>
<pre><span style="color:black">plan? <o:p></o:p></span></pre>
<pre><span style="color:black">(ii) Which inputs are likely to be the most important [relevant] during WG<o:p></o:p></span></pre>
<pre><span style="color:black">deliberations and why?<o:p></o:p></span></pre>
<pre><span style="color:black">(iii) Which inputs, if any, generated the most discussion within the small<o:p></o:p></span></pre>
<pre><span style="color:black">team? <o:p></o:p></span></pre>
<pre><span style="color:black">(iv) Which inputs may be obsolete or super-ceded by subsequent work?<o:p></o:p></span></pre>
<pre><span style="color:black">(v) What input gaps, if any, may need to be addressed later?<o:p></o:p></span></pre>
<pre><span style="color:black">(vi) Other key takeaways from this input inventory the team wishes to<o:p></o:p></span></pre>
<pre><span style="color:black">share with the WG <o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Your concern appears to fall under item v? If you would like to summarise<o:p></o:p></span></pre>
<pre><span style="color:black">your concerns in a few bullets, the sub-team can maybe use these to start<o:p></o:p></span></pre>
<pre><span style="color:black">building out the responses to the questions?<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Best regards,<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Marika<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">On 22/04/16 15:13, <a moz-do-not-send="true" href="mailto:gnso-rds-pdp-purpose-bounces@icann.orgonbehalfofKathyKleiman" target="_blank">"gnso-rds-pdp-purpose-bounces@icann.org on behalf of<o:p></o:p></a></span></pre>
<pre><span class="MsoHyperlink"><a moz-do-not-send="true" href="mailto:gnso-rds-pdp-purpose-bounces@icann.orgonbehalfofKathyKleiman" target="_blank">Kathy Kleiman"</a></span><span style="color:black"> <a moz-do-not-send="true" href="mailto:gnso-rds-pdp-purpose-bounces@icann.orgonbehalfofkathy@kathykleiman.com" target="_blank"><gnso-rds-pdp-purpose-bounces@icann.org on behalf of<o:p></o:p></a></span></pre>
<pre><span class="MsoHyperlink"><a moz-do-not-send="true" href="mailto:gnso-rds-pdp-purpose-bounces@icann.orgonbehalfofkathy@kathykleiman.com" target="_blank">kathy@kathykleiman.com></a></span><span style="color:black"> wrote:<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style="color:black">Hi Susan and Lisa,<o:p></o:p></span></pre>
<pre><span style="color:black">I have a question (which certainly does not have to be answered on a<o:p></o:p></span></pre>
<pre><span style="color:black">Friday afternoon), but some deep concerns have been raised on this list<o:p></o:p></span></pre>
<pre><span style="color:black">by people who helped created various documents and reports that we are<o:p></o:p></span></pre>
<pre><span style="color:black">now evaluating. For example, I raised the fact that it was completely<o:p></o:p></span></pre>
<pre><span style="color:black">out of scope for the Whois Review Team to evaluate the data collected in<o:p></o:p></span></pre>
<pre><span style="color:black">Whois and the primary purpose for which it was created. By the<o:p></o:p></span></pre>
<pre><span style="color:black">Affirmation of Commitments, we had to deal with the Whois system as it<o:p></o:p></span></pre>
<pre><span style="color:black">existed (and had been passed to ICANN from the National Science<o:p></o:p></span></pre>
<pre><span style="color:black">Foundation).<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">We could not and did not address or deal with primary purpose. I think<o:p></o:p></span></pre>
<pre><span style="color:black">this limitation and fact is critical to the understanding and evaluation<o:p></o:p></span></pre>
<pre><span style="color:black">of the Whois Review Team report, especially as it applies to our<o:p></o:p></span></pre>
<pre><span style="color:black">question of "purpose."<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">How can this point be added to Whois Review Team Final Report summary -<o:p></o:p></span></pre>
<pre><span style="color:black">perhaps in Additional Information? -- and to our discussion?<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Tx,<o:p></o:p></span></pre>
<pre><span style="color:black">Kathy<o:p></o:p></span></pre>
<pre><span style="color:black">_______________________________________________<o:p></o:p></span></pre>
<pre><span style="color:black">gnso-rds-pdp-purpose mailing list<o:p></o:p></span></pre>
<pre><span style="color:black"><a moz-do-not-send="true" href="mailto:gnso-rds-pdp-purpose@icann.org" target="_blank">gnso-rds-pdp-purpose@icann.org</a><a moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dpurpose&d=CwMD-g&c=5VD0RTtNlTh3ycd41b3MUw&r=gvEx8xF7ynrYQ7wShqEr-w&m=gYsnbc0nP-KLQYZYH7zwJoTq_v1XlnuWoZeUWEVTbZE&s=O2AG5wV0Zo2LJ7ZQZ1TVhCFBXTd7bx3GcUYvajgOc9k&e=" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-purpose</a><o:p></o:p></span></pre>
</blockquote>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><br>
_______________________________________________<br>
gnso-rds-pdp-purpose mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-purpose@icann.org">gnso-rds-pdp-purpose@icann.org</a><br>
<a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dpurpose&d=CwMD-g&c=5VD0RTtNlTh3ycd41b3MUw&r=gvEx8xF7ynrYQ7wShqEr-w&m=gYsnbc0nP-KLQYZYH7zwJoTq_v1XlnuWoZeUWEVTbZE&s=O2AG5wV0Zo2LJ7ZQZ1TVhCFBXTd7bx3GcUYvajgOc9k&e="
target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-purpose</a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre><span style="color:black">_______________________________________________<o:p></o:p></span></pre>
<pre><span style="color:black">gnso-rds-pdp-purpose mailing list<o:p></o:p></span></pre>
<pre><span style="color:black"><a moz-do-not-send="true" href="mailto:gnso-rds-pdp-purpose@icann.org">gnso-rds-pdp-purpose@icann.org</a><a moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dpurpose&d=CwMD-g&c=5VD0RTtNlTh3ycd41b3MUw&r=gvEx8xF7ynrYQ7wShqEr-w&m=gYsnbc0nP-KLQYZYH7zwJoTq_v1XlnuWoZeUWEVTbZE&s=O2AG5wV0Zo2LJ7ZQZ1TVhCFBXTd7bx3GcUYvajgOc9k&e=">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-purpose</a><o:p></o:p></span></pre>
</blockquote>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>