<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">I will repeat what I
have said before. Discussing "requirements" before purpose
sets up business requirements before we have defined the
business. DIscussing accuracy and access before we have
determined requirements merely throws the cement hardener into
the mix. Why on earth discuss accuracy requirements for data
elements that are on someone's wish list unless the costing
(and who will pay) is also defined? Part of discussing original
purpose of the collection, use and disclosure of registration
data is to determine, in 2016 and for the foreseeable future,
why we collect information, what is legally permissible to
collect, and who will pay for that collection (in one form or
another).</font></font></p>
<p><font size="+1"><font face="Lucida Grande">as I have said before,
I fully understand that tackling this problem is difficult,
and I understand the rationale for going with all the
"requirements" first. I do think getting further refinement
will sway all of us in certain directions....towards accepting
the assumptions that all this data collection is necessary and
desirable. It will also tire out those of us who have another
life, but perhaps that is a desired outcome of the majority.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Apologies for missing
the call yesterday, I was travelling and unable to accept the
callout. Comments will be coming shortly.<br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">SP</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2016-06-16 5:59, Victoria Sheckler
wrote:<br>
</div>
<blockquote
cite="mid:BN3PR0701MB1637852D09B48E49F3663C62D5560@BN3PR0701MB1637.namprd07.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        font-family:"Calibri",sans-serif;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        font-family:"Calibri",sans-serif;
        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:"Times New Roman",serif;}
p.mso-border-outer, li.mso-border-outer, div.mso-border-outer
        {mso-style-name:mso-border-outer;
        mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        background:#F5FFFF;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
p.mso-border-middle, li.mso-border-middle, div.mso-border-middle
        {mso-style-name:mso-border-middle;
        mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        background:#DFF6FF;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
p.mso-border-inner, li.mso-border-inner, div.mso-border-inner
        {mso-style-name:mso-border-inner;
        mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        background:#99B0E1;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
p.outlook-com-only, li.outlook-com-only, div.outlook-com-only
        {mso-style-name:outlook-com-only;
        mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:1.0pt;
        font-family:"Times New Roman",serif;
        display:none;}
p.border-outer, li.border-outer, div.border-outer
        {mso-style-name:border-outer;
        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:"Times New Roman",serif;}
p.border-middle, li.border-middle, div.border-middle
        {mso-style-name:border-middle;
        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:"Times New Roman",serif;}
p.border-inner, li.border-inner, div.border-inner
        {mso-style-name:border-inner;
        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:"Times New Roman",serif;}
span.EmailStyle25
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle26
        {mso-style-type:personal;
        font-family:"Arial",sans-serif;
        color:#1F497D;
        font-weight:normal;
        font-style:normal;}
span.EmailStyle27
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.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="1027" />
</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">+1<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 #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Vayra, Fabricio (Perkins Coie)<br>
<b>Sent:</b> Wednesday, June 15, 2016 10:50 AM<br>
<b>To:</b> Gomes, Chuck <a class="moz-txt-link-rfc2396E" href="mailto:cgomes@verisign.com"><cgomes@verisign.com></a>;
Ayden Férdeline <a class="moz-txt-link-rfc2396E" href="mailto:icann@ferdeline.com"><icann@ferdeline.com></a>; Susan
Kawaguchi <a class="moz-txt-link-rfc2396E" href="mailto:susank@fb.com"><susank@fb.com></a><br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] RDS 5 Charter
questions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">I
agree with Susan. There’s a reason the charter was written
as is and to change it unwinds the charter without the
benefit of the thoughtful work and deliberations that went
into it. Moreover, leaving access and accuracy out of the
discussion until the end has us making decisions in a
vacuum. And, finally, I’m not sure how you divorce
Users/Purposes, Privacy, and Data elements from Access and
Accuracy, as the latter two are a constant and vital
reference within all documents I’ve reviewed on the former
three … so to separate these two topics out until later just
sets us up for unnecessary grid-lock when we have to revisit
the first three topics through the interrelated latter two
topics of Access and Accuracy. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Fabricio
Vayra</span></b><b><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#D6001C"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#75787B">PARTNER<o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#75787B">700
Thirteenth Street, N.W. Suite 600<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#75787B">Washington,
DC 20005-3960<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#75787B">D.
+1.202.654.6255<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#75787B">F.
+1.202.654.9678<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#75787B">E.
<a moz-do-not-send="true"
href="mailto:FVayra@perkinscoie.com"><span
style="font-family:"Calibri",sans-serif">FVayra@perkinscoie.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#75787B"><img
id="Picture_x0020_1"
src="cid:part2.CA39CCE0.569968F8@mail.utoronto.ca"
alt="cid:image001.jpg@01D054C5.01001EE0" height="19"
border="0" width="130"></span><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:10.0pt;font-family:"Arial",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-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Gomes, Chuck<br>
<b>Sent:</b> Wednesday, June 15, 2016 9:21 AM<br>
<b>To:</b> Ayden Férdeline; Susan Kawaguchi<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] RDS 5 Charter
questions<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks
for continuing the discussion on the approach to reaching
consensus. I strongly encourage others to express your
opinion on that along with your rationale: 1) Should we
leave our work plan as is or 2) should we change it from two
issue reports to three issue reports with the first one
following deliberation on the user/purpose, privacy/data
protection and data element questions?<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">I
appreciate the time you took to explain your position but
note that much of what you said gets into what we will
discuss in our future deliberations so I ask everyone to not
go there yet but instead focus on commenting on the approach
to reaching consensus. Our goal is to finalize that
approach in our meeting next week.<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">
Ayden Férdeline [<a moz-do-not-send="true"
href="mailto:icann@ferdeline.com"><span
style="font-family:"Calibri",sans-serif">mailto:icann@ferdeline.com</span></a>]
<br>
<b>Sent:</b> Wednesday, June 15, 2016 6:54 AM<br>
<b>To:</b> Susan Kawaguchi<br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"><span
style="font-family:"Calibri",sans-serif">gnso-rds-pdp-wg@icann.org</span></a>;
Gomes, Chuck<br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] RDS 5 Charter
questions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" style="width:100.0%" border="0"
cellpadding="0" cellspacing="0" width="100%">
<tbody>
<tr>
<td style="padding:0in 0in 0in 0in" valign="top">
<table class="MsoNormalTable" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<td style="padding:0in 0in 0in 0in" valign="top">
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Hi
Susan,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Thanks
for sharing these reflections. I
understand the desire not to complicate
this task. As someone who is new to the
ICANN community and its approach to
policy-making – and, also, someone who is
an advocate of privacy – it would seem to
me that all the costs and burdens
associated with rallying against an
open-access Registration Directory Service
have been put on some stakeholders, while
proponents of the status quo profit from
the lack of consensus or inertia on a
different path forward. I say this not to
demonise any views, but to clarify that I
do indeed share your perspective that we
don’t want to be permanently gridlocked
here.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">This
is actually why my preference would be to
go down the path that was suggested on our
call yesterday – from what I recall, it
would mean three opportunities for public
comment, and a mandate to focus our
energies on understanding Users/Purposes,
Privacy, and Data Elements before we
consider whether or not gated access is
necessary or whether or not records should
be accurate. It seems a little premature
to me to consider the latter points when
we have not yet established if there is a
basis for collecting registration data in
the first place. I share your point,
though, that we should be distinguishing
between individuals and commercial
entities – which is not to presuppose that
there ultimately will be a need for
variations in treatment if the RDS is
warranted.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">We
can make our work easier, however. If we
decide upon a standard by which to assess
whether or not the RDS complies with, say,
data privacy laws, we might have a more
straightforward exercise ahead. And on
that point I would like to note that just
because the Internet originated in the US
and its governance framework has been
historically dominated by US-based actors
does not mean we should by default turn to
US law for contextual protections or
principles. I would like to respectfully
suggest that European instruments such as
the European Convention on Human Rights,
standards set by the European Union Data
Protection Directive, and Convention 108
of the Council of Europe might be helpful
starting points. These are not obscure
laws or conventions which apply to no one:
the EU population is over 500 million
people, far greater than that of the US.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">I
am not a lawyer and I do not come at this
topic with the same institutional
knowledge that others do have. I do not
know all the details or decisions that
have led us to this point where, it would
seem, the (political) cost to move away
from the current default is so very high.
I say this to be clear, from the onset,
that I might well be misinformed or wrong
about how we move forward in this working
group. However, it is my view that just
because the Internet is by nature
cross-border does not mean that it should
be treated as a self-governing realm
beyond the reach of national laws. WHOIS
today, to me, seems to subvert and/or
undermine domestic norms and institutions
in many territories worldwide. I don’t
want to get into the question of
sovereignty online, but it would be
helpful to at least establish whether or
not we believe ICANN should mandate
through its contracts with registrars that
they comply with local legal regulations,
or whether we instead believe that market
forces should be driving fundamental
decisions about the nature of the
Internet.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">You
can probably guess my position here, but
I’d like to think we can reach some common
ground. What are we more concerned about –
the rights of the data subject and
controller, or the rights of those who
wish to monetise it? To come up with, like
we have, a list of something like 780
possible requirements for the RDS strikes
me as a recipe for disaster. It seems
inevitable that we will accidentally
impose huge costs on some stakeholder
groups – the unintended consequence of
trying to achieve some short-term policy
goal not to do with any functional
imperative of the Internet itself, but to
meet someone’s obscure interest. That’s
why I want to hammer down on what data is
being collected, why it is being used, and
what are the implications for privacy
before we proceed any further.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Just
my $0.02.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">-
Ayden<o:p></o:p></span></p>
</div>
<div>
<p><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<p><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">On
Tue, Jun 14, 2016 10:51 PM, Susan
Kawaguchi
<a moz-do-not-send="true"
href="mailto:susank@fb.com"
target="_blank">susank@fb.com</a>
wrote:<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Hello
All, <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">I
have been thinking about the RDS
discussion from this morning’s
meeting and wanted to clarify my
personal position (not as a vice
chair of the WG) I think we will
complicate our task if we initially
limit the discussion to three of
the charter questions relating to
users/purposes, privacy and data
elements. Much thought went into
drafting the charter and
brainstorming how a WG should
approach deliberations. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Users/Purposes<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Privacy<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Data
elements<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Access<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Accuracy<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">All
of the above are very interrelated
and I can’t imagine that we can
sufficiently discuss one or two
without the others. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">One
other issue that comes to mind is
that we must keep in mind PII data
but we also have to be wary of
creating requirements that convey
data protection rights of
individuals to commercial entities.
For each of the topics above we
need to address how it would affect
an individual or a commercial
entity. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">I
think we should move forward with
the original plan according to the
Charter and discuss all 5 issues in
the first pass. <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Susan
Kawaguchi<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Domain
Name Manager <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Facebook
Legal Dept. <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif">Ayden
Férdeline<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"><a
moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_gnsosoi_Ayden-26-2343-3BF-25C3-25A9rdeline-26-2343-3BSOI&d=CwMGaQ&c=XRWvQHnpdBDRh-yzrHjqLpXuHNC_9nanQc6pPG_SpT0&r=6lUxzkhJPN5qts-Nve5TYqxoGjP81z1kCvXgsmw-MiQ&m=fLy_j2dJidfz8cbOpf5vyO1JREPzgsOw2KKOvpqP3eI&s=kkHizDWFLQRbNkD1e9Kt9tnqA6BmHLWlIte1Qy8Q500&e="><span
style="background:white">Statement
of Interest</span></a><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">
<v:stroke joinstyle="miter" />
<v:formulas>
<v:f eqn="if lineDrawn pixelLineWidth 0" />
<v:f eqn="sum @0 1 0" />
<v:f eqn="sum 0 0 @1" />
<v:f eqn="prod @2 1 2" />
<v:f eqn="prod @3 21600 pixelWidth" />
<v:f eqn="prod @3 21600 pixelHeight" />
<v:f eqn="sum @0 0 1" />
<v:f eqn="prod @6 1 2" />
<v:f eqn="prod @7 21600 pixelWidth" />
<v:f eqn="sum @8 21600 0" />
<v:f eqn="prod @7 21600 pixelHeight" />
<v:f eqn="sum @10 21600 0" />
</v:formulas>
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />
<o:lock v:ext="edit" aspectratio="t" />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" alt="" style='position:absolute;margin-left:0;margin-top:0;width:.75pt;height:.75pt;z-index:251658240;mso-wrap-distance-left:0;mso-wrap-distance-top:0;mso-wrap-distance-right:0;mso-wrap-distance-bottom:0;mso-position-horizontal:left;mso-position-horizontal-relative:text;mso-position-vertical-relative:line' o:allowoverlap="f">
<v:imagedata src="https://app.mixmax.com/api/track/v2/1vsyCGVzYh9OioWpK/i02bj5SZulGblRmclZGQu5WYjlmI/i02bj5ibnl2cpJXZ2B0cl12bnNmI/IyajVHaDBCLzVWbvdkI?sc=false" />
<w:wrap type="square"/>
</v:shape><![endif]--><!--[if !vml]--><img moz-do-not-send="true"
src="https://app.mixmax.com/api/track/v2/1vsyCGVzYh9OioWpK/i02bj5SZulGblRmclZGQu5WYjlmI/i02bj5ibnl2cpJXZ2B0cl12bnNmI/IyajVHaDBCLzVWbvdkI?sc=false"
v:shapes="_x0000_s1026" height="1"
align="left" width="1"><!--[endif]--><span
style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" style="text-align:center" align="center">
<hr align="center" size="2" width="100%">
</div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
NOTICE: This communication may contain privileged or other
confidential information. If you have received it in error,
please advise the sender by reply email and immediately
delete the message and any attachments without copying or
disclosing the contents. Thank you.</span><o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</body>
</html>