<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font size="+1"><font face="Lucida Grande">I was merely registering
the fact that in general, the NCSG has become concerned when
contracted parties, either in consultation with ICANN's
compliance department, or on their own, develop best practices
outside the regular PDP process. I think Ayden responded with
a good example, and while I appreciate the detail into which
Greg went in taking apart Ayden's argument, I think it is a wee
bit misplaced at the moment. This is getting off topic.<br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Simply put, <br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">1. John Horton asked
if it was within our remit to establish the chain of authority
in cases of abuse, and whether we should develop a best practice
guide in how to pursue a complaint. (given that ICANN has no
authority over hosting providers, I would suggest that the
answer to that is no)</font></font></p>
<p><font size="+1"><font face="Lucida Grande">2, You responded that
we could make recommendations about how to pursue a complaint,
for use on a voluntary basis.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">3. While I don't
question the relatively innocuous nature of the suggestion,
and the fact that such a guide would doubtless be useful and
helpful given the complexity of the chain of responsibiilty
described below, I am merely giving early warning that the
NCSG is concerned about "voluntary best practices". <br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie Perrin<br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande"></font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-02-25 07:43, Gomes, Chuck
wrote:<br>
</div>
<blockquote
cite="mid:6DCFB66DEEF3CF4D98FA55BCC43F152E57B5FE2A@BRN1WNEXMBX02.vcorp.ad.vrsn.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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:"Times New Roman",serif;
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:870071105;
mso-list-template-ids:-314556882;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:958487450;
mso-list-template-ids:-841984490;}
@list l1:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:991757157;
mso-list-template-ids:-613261524;}
@list l3
{mso-list-id:1929460117;
mso-list-template-ids:-1569159406;}
@list l4
{mso-list-id:2032146847;
mso-list-template-ids:1147556552;}
@list l4:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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:windowtext">Stephanie.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">I
am not at all clear about what you are concerned about
here. I was simply responding to a question John asked
about WG scope. ICANN org nor ICANN community has not asked
or suggested that various contracted parties do anything in
this regard. Various WG members have simply been sharing
some ideas about education of users that might be helpful. I
personally think it is pretty early to get concerned and
that it would be better to wait until we see if this
discussion goes anywhere. In the meantime I think it is
important for WG members to float ideas for possible future
consideration or not. We will filter them to make sure they
are in scope; some will be pursued further and some not and
the ones we pursue further will be vetted by the full WG so
there will be plenty of opportunity to everyone to
contribute. In particular, if and when the WG decides to
consider any possible best practices, we will have to
evaluate whether there might be risk of coercion.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<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;color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">
<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>Stephanie Perrin<br>
<b>Sent:</b> Friday, February 24, 2017 10:23 PM<br>
<b>To:</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> [EXTERNAL] Re: [gnso-rds-pdp-wg] Dangers
of public whois<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida
Grande",serif">I have not consulted my SG yet, but I
think I can safely say that we are getting quite concerned
about what ICANN is asking/suggesting its various contracted
parties do on a voluntary basis. Best practice,
particularly in an unregulated environment, becomes
coercive.</span><o:p></o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida
Grande",serif">Stephanie Perrin</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 2017-02-24 18:09, Gomes, Chuck wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks
for explaining John. Below is my opinion on ‘</span><span
style="font-family:"Arial",sans-serif;color:#222222">on
whether it's appropriate for this group to make a
determination about this "chain of responsibility" as part
of our work.</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">’</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">As
someone else has already pointed out, ICANN has no
relationship with hosting providers so it would be out of
scope for consensus policy. But I don’t think that that
would prevent the WG from making some recommendations
along the lines that are being discussed that could be
implemented on a voluntary basis.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">I
ask staff and others to correct me if they think I am
wrong on this.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Chuck</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<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">
John Horton [<a moz-do-not-send="true"
href="mailto:john.horton@legitscript.com">mailto:john.horton@legitscript.com</a>]
<br>
<b>Sent:</b> Friday, February 24, 2017 11:12 AM<br>
<b>To:</b> Gomes, Chuck <a moz-do-not-send="true"
href="mailto:cgomes@verisign.com"><cgomes@verisign.com></a><br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>;
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Dangers
of public whois</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#444444">Hi
Chuck,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#444444"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#444444">Sure. </span><span
style="font-family:"Arial",sans-serif;color:#222222">What I'm
asking you to determine is whether it is within the
ambit of this group's mission to do, or come to a
consensus on, the following:</span><o:p></o:p></p>
</div>
<ol start="1" type="1">
<li class="MsoNormal"
style="color:#222222;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4
level1 lfo3">
<span
style="font-family:"Arial",sans-serif;color:#444444">"</span><span
style="font-family:"Arial",sans-serif">Establish(ing)
chains of responsibility in the data," in the
context of submitting complaints or resolving issues
with a website or domain name</span><o:p></o:p></li>
</ol>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in"><span
style="font-family:"Arial",sans-serif;color:#444444">, and
determining "registrar obligations" in response to
those abuse complaints. </span><o:p></o:p></p>
</div>
<ol start="2" type="1">
<li class="MsoNormal"
style="color:#222222;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4
level1 lfo3">
<span style="font-family:"Arial",sans-serif">Either
alternatively or simultaneously, developing or
providing a "how to guide" or "guidance" "for going
forward with a complaint." </span><o:p></o:p></li>
</ol>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#222222">Concretely,
I think the point is to formalize the notion that
"registrars" shouldn't have to do the "hosting
provider's job" and to "direct a lot of traffic
away from the registrar." For example, one "chain
of responsibility" that this group might seek to
establish would be to direct, suggest or advise
that a registrant should be contacted first, then
the hosting provider, and only then the
registrar. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#222222"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#222222">What
I'm asking for is a determination on whether it's
appropriate for this group to make a determination
about this "chain of responsibility" as part of
our work. From my perspective, it is outside the
scope of our mission, so trying to discuss it,
persuade each other or come to a consensus on it
in this group isn't <i>apropos.</i> If this is
something that is requested by the ICANN board as
part of the RDS's group and any report we issue,
or if it's appropriately within the ambit, it
would be helpful to clarify that and also the
scope. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#222222"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#222222">Let
me know if I'm not clearly summarizing what I'm
asking you to rule on. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#222222"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#222222">Thanks,</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#073763">John
Horton<br>
President and
CEO,
LegitScript</span><o:p></o:p></p>
<div>
<p
class="MsoNormal"><img
moz-do-not-send="true" style="width:1.0in;height:.375in"
id="_x0000_i1025"
src="https://docs.google.com/uc?export=download&id=0B13GfLt8zwZJRXE5UTAtclVxdTg&revid=0B13GfLt8zwZJSG9zOUVwN1lFKzFrRVlnaWU0NGZ4RmdkUjg4PQ"
height="36"
border="0"
width="96"><o:p></o:p></p>
<div>
<div>
<p
style="margin:0in;margin-bottom:.0001pt"><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif"> </span><o:p></o:p></p>
<p
style="margin:0in;margin-bottom:.0001pt"><b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#444444">Follow</span></b><b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#0B5394">
</span></b><b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif">Legit</span></b><b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#0B5394">Script</span></b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif">:
<a
moz-do-not-send="true"
href="http://www.linkedin.com/company/legitscript-com" target="_blank"><span
style="color:#CC0000">LinkedIn</span></a> | <a moz-do-not-send="true"
href="https://www.facebook.com/LegitScript" target="_blank"><span
style="color:#6AA84F">Facebook</span></a>
| <a
moz-do-not-send="true"
href="https://twitter.com/legitscript" target="_blank"><span
style="color:#674EA7">Twitter</span></a>
| </span><u><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#FF9900"><a
moz-do-not-send="true" href="http://blog.legitscript.com"
target="_blank">Blog</a></span></u><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif"> |</span><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#FF9900">
<a
moz-do-not-send="true"
href="https://plus.google.com/112436813474708014933/posts"
target="_blank">Google+</a></span><o:p></o:p></p>
<p
style="margin:0in;margin-bottom:.0001pt"><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif"> </span><o:p></o:p></p>
<p
style="margin:0in;margin-bottom:.0001pt"><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#FF9900"><img
moz-do-not-send="true" style="width:.4833in;height:1.0in"
id="_x0000_i1026"
src="https://www.legitscript.com/wp-content/uploads/2015/09/LegitScript-Workplace.png"
height="96"
border="0"
width="46"><img
moz-do-not-send="true" style="width:.4916in;height:1.0166in"
id="_x0000_i1027"
src="https://docs.google.com/uc?export=download&id=0B13GfLt8zwZJTmNWbmcwOTVJMXc&revid=0B13GfLt8zwZJQlZWOXVGbG9acC9nRGhzdEkxclFJVytCWVNjPQ"
height="98"
border="0"
width="47"></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">On Fri, Feb 24, 2017 at 6:53 AM,
Gomes, Chuck <<a moz-do-not-send="true"
href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>>
wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">John,</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Can
you clarify what you want a ruling on?</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Chuck</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a
moz-do-not-send="true"
name="m_-5557364173733076281__MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></a><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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 moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>
[mailto:<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>John Horton<br>
<b>Sent:</b> Friday, February 24, 2017 8:41 AM<br>
<b>To:</b> Volker Greimann <<a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a>><br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg]
Dangers of public whois</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Arial",sans-serif;color:#444444">Let me
provide a few comments on that. </span><o:p></o:p></p>
</div>
<div>
<ol start="1" type="1">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo7">
<span
style="font-family:"Arial",sans-serif;color:#444444">I
like Volker's idea of including
hosting details in the ultimate RDS.
It's additional information, which may
be useful to the viewer. From a
concrete use-case perspective, when I
or one of my analysts is evaluating
whether a merchant should be boarded
with a bank or rejected based on risk,
it's certainly one of the details we
look it. (I'm not sure it's
technically "registration data," but
not sure if that matters.)</span><o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo7">
<span
style="font-family:"Arial",sans-serif;color:#444444">I
object to using the RDS (or this
group) to establish chains or a
hierarchy of responsibility as being
outside of our scope and mandate.
(Chuck, maybe we can get a ruling on
that?) I realize that there are
members of this group who believe that
a complainant should always go to the
registrant first, then the host, and
only the registrar as a last resort
(some believe never). But that's not
how everyone feels. Others believe it
should be the payment processor first.
Still others believe the registrar
should be the first point of contact
for a complaint. Still others believe
there is no hierarchy and it's a
case-by-case solution and all
facilitators are equally valid points
of contact. My point is not to get
into an argument about who is right
there (I and I'm sure many others
don't have the time, and many of us
have discussed this elsewhere); I
simply don't think we should be using
this group to try and resolve that
particular issue, or impose some sort
of a structure on internet users,
because I think it's probably outside
the scope of our mandate (and I will
strongly note that I don't think
there's consensus on that issue).</span><o:p></o:p></li>
</ol>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Arial",sans-serif;color:#444444">Chuck, if
I'm wrong and it's inside the scope of
our mandate to use the RDS to
establish a structure about who a
complainant should approach first,
second, third, fourth, etc. let us
know, but if it's in scope, that's
going to be a somewhat different
discussion. Again, my objective here
isn't to launch another 100-email
debate about who is right or wrong; my
objective is to argue that a) the idea
of including hosting information in
the RDS seems like a pretty reasonable
one, but b) doing that in order to
impose rules on internet users on what
complaint hierarchy they should follow
is out of scope for our mandate. </span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br
clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Arial",sans-serif;color:#073763">John
Horton<br>
President and
CEO,
LegitScript</span><o:p></o:p></p>
<div>
<p
class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><img
moz-do-not-send="true"
style="width:1.0in;height:.375in" id="_x0000_i1028"
src="https://docs.google.com/uc?export=download&id=0B13GfLt8zwZJRXE5UTAtclVxdTg&revid=0B13GfLt8zwZJSG9zOUVwN1lFKzFrRVlnaWU0NGZ4RmdkUjg4PQ"
height="36"
border="0"
width="96"><o:p></o:p></p>
<div>
<div>
<p
style="margin:0in;margin-bottom:.0001pt"><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif"> </span><o:p></o:p></p>
<p
style="margin:0in;margin-bottom:.0001pt"><b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#444444">Follow</span></b><b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#0B5394">
</span></b><b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif">Legit</span></b><b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#0B5394">Script</span></b><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif">:
<a
moz-do-not-send="true"
href="http://www.linkedin.com/company/legitscript-com" target="_blank"><span
style="color:#CC0000">LinkedIn</span></a> | <a moz-do-not-send="true"
href="https://www.facebook.com/LegitScript" target="_blank"><span
style="color:#6AA84F">Facebook</span></a>
| <a
moz-do-not-send="true"
href="https://twitter.com/legitscript" target="_blank"><span
style="color:#674EA7">Twitter</span></a>
| </span><u><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#FF9900"><a
moz-do-not-send="true" href="http://blog.legitscript.com"
target="_blank">Blog</a></span></u><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif"> |</span><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#FF9900">
<a
moz-do-not-send="true"
href="https://plus.google.com/112436813474708014933/posts"
target="_blank">Google+</a></span><o:p></o:p></p>
<p
style="margin:0in;margin-bottom:.0001pt"><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif"> </span><o:p></o:p></p>
<p
style="margin:0in;margin-bottom:.0001pt"><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#FF9900"><img
moz-do-not-send="true" style="width:.4833in;height:1.0in"
id="_x0000_i1029"
src="https://www.legitscript.com/wp-content/uploads/2015/09/LegitScript-Workplace.png"
height="96"
border="0"
width="46"><img
moz-do-not-send="true" style="width:.4916in;height:1.025in"
id="_x0000_i1030"
src="https://docs.google.com/uc?export=download&id=0B13GfLt8zwZJTmNWbmcwOTVJMXc&revid=0B13GfLt8zwZJQlZWOXVGbG9acC9nRGhzdEkxclFJVytCWVNjPQ"
height="98"
border="0"
width="47"></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On
Fri, Feb 24, 2017 at 4:35 AM, Volker
Greimann <<a moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a>>
wrote:<o:p></o:p></p>
<blockquote
style="border:none;border-left:solid
#CCCCCC 1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">So
should we maybe include hosting
details in the ultimate RDS? These
would have to be supplied differently,
but it would make sense if we want to
establish chains of responsibility in
the data.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
<br>
<br>
Am 20.02.2017 um 14:20 schrieb
theo geurts:<o:p></o:p></p>
<blockquote
style="border:none;border-left:solid
#CCCCCC 1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Good
point Michele,<br>
<br>
RDS should be a facilitating
here in the sense that reports
end up at the correct party and
yet give the reporter a logical
natural flow in creating the
report without creating
confusion with different set of
contacts.<br>
<br>
Theo<br>
<br>
<br>
On 20-2-2017 12:24, Michele
Neylon - Blacknight wrote:<o:p></o:p></p>
<blockquote
style="border:none;border-left:solid
#CCCCCC 1.0pt;padding:0in 0in
0in
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Volker<br>
<br>
From our perspective the
frustration is when the client
(registrant) has their details
in whois and / or on the
website and the complainant
makes zero attempt to contact
them. The first we hear about
the alleged issues is when I
get a 100 page takedown notice
on my desk.<br>
So if they can at least
attempt to contact the website
operator then it makes our
lives a lot easier.<br>
As the hosting provider we
*should* have details of how
to reach the site owner, but
not always, as we also offer
dedicated servers, colo etc.,
but we’ll know who the IPs are
assigned to<br>
<br>
Regards<br>
<br>
Michele<br>
<br>
<br>
-- <br>
Mr Michele Neylon<br>
Blacknight Solutions<br>
Hosting, Colocation &
Domains<br>
<a moz-do-not-send="true"
href="https://www.blacknight.com/"
target="_blank">https://www.blacknight.com/</a><br>
<a moz-do-not-send="true"
href="http://blacknight.blog/"
target="_blank">http://blacknight.blog/</a><br>
Intl. <a
moz-do-not-send="true"
href="tel:%2B353%20%280%29%2059%20%209183072"
target="_blank">+353 (0) 59
9183072</a><br>
Direct Dial: <a
moz-do-not-send="true"
href="tel:%2B353%20%280%2959%209183090"
target="_blank">+353 (0)59
9183090</a><br>
Personal blog: <a
moz-do-not-send="true"
href="https://michele.blog/"
target="_blank">https://michele.blog/</a><br>
Some thoughts: <a
moz-do-not-send="true"
href="https://ceo.hosting/"
target="_blank">https://ceo.hosting/</a><br>
-------------------------------<br>
Blacknight Internet Solutions
Ltd, Unit 12A,Barrowside
Business Park,Sleaty<br>
Road,Graiguecullen,Carlow,R93
X265,Ireland Company No.:
370845<br>
<br>
On 20/02/2017, 11:21, "Volker
Greimann" <<a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a>>
wrote:<br>
<br>
Agreed. The question is
who is next if the details are
not available. If<br>
it is content, the next
port of call should be the
host as the host has<br>
the ability to remove
said content and also bears
certain legal<br>
obligations in case of
obvious violations while the
registrar does not.<br>
As the registrar may
not even know the actual
registrant, for example<br>
for registrations under
third party privacy services,
it does not even<br>
make sense to contact the
registrar.<br>
Best,<br>
Volker<br>
Am
20.02.2017 um 12:08 schrieb
Michele Neylon - Blacknight:<br>
> Volker<br>
><br>
> The key thing is the
sequence.<br>
> If the contact’s
details are available either
via whois OR on the website
then they’re the first port of
call.<br>
><br>
> Regards<br>
><br>
> Michele<br>
><br>
><br>
> --<br>
> Mr Michele Neylon<br>
> Blacknight Solutions<br>
> Hosting, Colocation
& Domains<br>
> <a
moz-do-not-send="true"
href="https://www.blacknight.com/"
target="_blank">https://www.blacknight.com/</a><br>
> <a
moz-do-not-send="true"
href="http://blacknight.blog/"
target="_blank">http://blacknight.blog/</a><br>
> Intl. <a
moz-do-not-send="true"
href="tel:%2B353%20%280%29%2059%20%209183072"
target="_blank">+353 (0) 59
9183072</a><br>
> Direct Dial: <a
moz-do-not-send="true"
href="tel:%2B353%20%280%2959%209183090"
target="_blank">+353 (0)59
9183090</a><br>
> Personal blog: <a
moz-do-not-send="true"
href="https://michele.blog/"
target="_blank">https://michele.blog/</a><br>
> Some thoughts: <a
moz-do-not-send="true"
href="https://ceo.hosting/"
target="_blank">https://ceo.hosting/</a><br>
>
-------------------------------<br>
> Blacknight Internet
Solutions Ltd, Unit
12A,Barrowside Business
Park,Sleaty<br>
>
Road,Graiguecullen,Carlow,R93
X265,Ireland Company No.:
370845<br>
><br>
> On 20/02/2017,
10:46, "Volker Greimann" <<a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a>>
wrote:<br>
><br>
> Well, the
registrant may not be the
right contact in all cases,<br>
> especially if
it comes down to subdomains.
But yes, if the registrant is<br>
> known, then he
should probably be contacted
right after a known website<br>
> operator. But
if the registrant is unknown,
the next contact should be<br>
> the host as he
is closer to the alleged
violation than the registrar.<br>
><br>
> Best,<br>
><br>
> Volker<br>
><br>
><br>
><br>
><br>
> Am 20.02.2017
um 11:28 schrieb Michele
Neylon - Blacknight:<br>
> > Volker<br>
> ><br>
> > Really?<br>
> > As a
hosting provider I’d strongly
disagree.<br>
> ><br>
> > If you’ve
got a problem with content on
a website you should contact
the registrant first.<br>
> ><br>
> > Regards<br>
> ><br>
> > Michele<br>
> ><br>
> ><br>
> > --<br>
> > Mr Michele
Neylon<br>
> > Blacknight
Solutions<br>
> > Hosting,
Colocation & Domains<br>
> > <a
moz-do-not-send="true"
href="https://www.blacknight.com/"
target="_blank">https://www.blacknight.com/</a><br>
> > <a
moz-do-not-send="true"
href="http://blacknight.blog/"
target="_blank">http://blacknight.blog/</a><br>
> > Intl. <a
moz-do-not-send="true"
href="tel:%2B353%20%280%29%2059%20%209183072"
target="_blank">
+353 (0) 59 9183072</a><br>
> > Direct
Dial: <a
moz-do-not-send="true"
href="tel:%2B353%20%280%2959%209183090"
target="_blank">
+353 (0)59 9183090</a><br>
> > Personal
blog: <a
moz-do-not-send="true"
href="https://michele.blog/"
target="_blank">https://michele.blog/</a><br>
> > Some
thoughts: <a
moz-do-not-send="true"
href="https://ceo.hosting/"
target="_blank">https://ceo.hosting/</a><br>
> >
-------------------------------<br>
> > Blacknight
Internet Solutions Ltd, Unit
12A,Barrowside Business
Park,Sleaty<br>
> >
Road,Graiguecullen,Carlow,R93
X265,Ireland Company No.:
370845<br>
> ><br>
> > On
20/02/2017, 09:54, "<a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>
on behalf of Volker Greimann"
<<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>
on behalf of <a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a>>
wrote:<br>
> ><br>
> > When
you say web site, it should be
taken up with the web host not
the<br>
> >
registrar as the registrant is
not necessarily the correct
content.<br>
> ><br>
> >
Problems with domain ->
registrant<br>
> ><br>
> >
Problems with content ->
Web host<br>
> ><br>
> > Best,<br>
> ><br>
> >
Volker<br>
> ><br>
> ><br>
> > Am
17.02.2017 um 20:49 schrieb
Mark Svancarek via
gnso-rds-pdp-wg:<br>
> > >
Counter example<br>
> > >
"Joe" has a web site which is
used to abuse my trademark. I
can't contact Joe because his
thin data is incorrect or
hidden (I don't know that Joe
is actually Joe.). I then
contact the registrar. They
follow up with the privacy
proxy service if needed.
Hopefully all this happens
quickly and the cease and
desist message is actually
delivered.<br>
> > ><br>
> > >
In actual practice, there is a
noteworthy difference in
effectiveness if we have to go
through the registrar,
compared to us contacting
directly. If the registrar
isn't responsive, then I may
have to pressure ICANN to
enforce the registrar
contract, which has its own
issues.<br>
> > ><br>
> > >
In either case, your abuse of
my trademark is probably a
civil issue, so starting with
law enforcement isn't a great
option, even if they had the
inclination and bandwidth to
help out in a timely fashion.<br>
> > ><br>
> > >
-----Original Message-----<br>
> > >
From: <a
moz-do-not-send="true"
href="mailto:benny@nordreg.se"
target="_blank">benny@nordreg.se</a>
[mailto:<a
moz-do-not-send="true"
href="mailto:benny@nordreg.se"
target="_blank">benny@nordreg.se</a>]<br>
> > >
Sent: Friday, February 17,
2017 9:41 AM<br>
> > >
To: Mark Svancarek <<a
moz-do-not-send="true"
href="mailto:marksv@microsoft.com"
target="_blank">marksv@microsoft.com</a>><br>
> > >
Cc: RDS PDP WG <<a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
> > >
Subject: Re: [gnso-rds-pdp-wg]
Dangers of public whois<br>
> > ><br>
> > >
Let us take a simple example<br>
> > ><br>
> > >
A phone number can you as the
one it's registered on choose
by yourself if it shall be
published in the phone book,
if you give the number to
someone it's your choice as an
individual! If the police want
your number they will get
without to much effort.<br>
> > ><br>
> > >
So why on earth are we forcing
registrants to give up this
right to choose to whom they
share that info?<br>
> > ><br>
> > >
Forget what Whois are as we
know it and come up with ideas
how we can make a new system
which takes reasonable
interest of all sides here.<br>
> > ><br>
> > >
The Status Quo hammering are
not productive at all.<br>
> > ><br>
> > >
RDS are meant to make change
to the better!<br>
> > ><br>
> > ><br>
> > >
Sent from my iPhone<br>
> > ><br>
> >
>> On 17 Feb 2017, at
18:28, Mark Svancarek <<a
moz-do-not-send="true"
href="mailto:marksv@microsoft.com"
target="_blank">marksv@microsoft.com</a>>
wrote:<br>
> >
>><br>
> >
>> Spam and DDOS will
always be with us, and the
need to mitigate them does not
eliminate the need to have
public data. It seems
orthogonal to me.<br>
> >
>><br>
> >
>><br>
> >
>><br>
> >
>> -----Original
Message-----<br>
> >
>> From: <a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank">
gnso-rds-pdp-wg-bounces@icann.org</a><br>
> >
>> [mailto:<a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>]
On Behalf Of<br>
> >
>> <a
moz-do-not-send="true"
href="mailto:benny@nordreg.se"
target="_blank">benny@nordreg.se</a><br>
> >
>> Sent: Friday,
February 17, 2017 8:25 AM<br>
> >
>> To: RDS PDP WG <<a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
> >
>> Subject: Re:
[gnso-rds-pdp-wg] Dangers of
public whois<br>
> >
>><br>
> >
>> Another post about
the problems with public whois<br>
> >
>><br>
> >
>> How anyone here can
still defend this abuse of
info as a the best system I
have serious problems
understanding.<br>
> >
>><br>
> >
>> <a
moz-do-not-send="true"
href="http://domainnamewire.com/2017/02/16/control-block-sms-spam-robocallin"
target="_blank">
http://domainnamewire.com/2017/02/16/control-block-sms-spam-robocallin</a><br>
> >
>> g-based-whois-info/<br>
> >
>><br>
> >
>><br>
> >
>> --<br>
> >
>> Med vänliga
hälsningar / Kind Regards /
Med vennlig hilsen<br>
> >
>><br>
> >
>> Benny Samuelsen<br>
> >
>> Registry Manager -
Domainexpert<br>
> >
>><br>
> >
>> Nordreg AB - ICANN
accredited registrar<br>
> >
>> IANA-ID: 638<br>
> >
>> Phone: <a
moz-do-not-send="true"
href="tel:%2B46.42197080"
target="_blank">+46.42197080</a><br>
> >
>> Direct: <a
moz-do-not-send="true"
href="tel:%2B47.32260201"
target="_blank">+47.32260201</a><br>
> >
>> Mobile: <a
moz-do-not-send="true"
href="tel:%2B47.40410200"
target="_blank">+47.40410200</a><br>
> >
>><br>
> >
>>> On 17 Feb 2017,
at 14:55, Michele Neylon -
Blacknight <<a
moz-do-not-send="true"
href="mailto:michele@blacknight.com"
target="_blank">michele@blacknight.com</a>>
wrote:<br>
> >
>>><br>
> >
>>> Allison<br>
> >
>>><br>
> >
>>> As others have
said, if you have an issue
please report it to ICANN,<br>
> >
>>> law enforcement,
consumer protection etc., Some
of us take our obligations
very seriously and lumping all
registrars and providers into
one big bucket isn't very
helpful for constructive
dialogue.<br>
> >
>>> We get a number
of whois complaints from ICANN
every year and we investigate
each and every one of them. In
some cases it's very obvious
that the details provided are
bogus, but in others it's not
and we have to spend time
energy and effort going back
and forth with our client and
ICANN to resolve it. Sometimes
this leads to domains being
suspended or deleted,
sometimes the whois gets
updated, sometimes the
complaint is denied. But each
complaint is handled on its
merits.<br>
> >
>>><br>
> >
>>> We also have a
whois privacy service. It is
NOT a fake address. You can
check it in the Irish company
office:<br>
> >
>>> <a
moz-do-not-send="true"
href="https://search.cro.ie/company/CompanyDetails.aspx?id=480317&type=C"
target="_blank">
https://search.cro.ie/company/CompanyDetails.aspx?id=480317&type=C</a><br>
> >
>>><br>
> >
>>> Now you may not
like that people and
organisations choose to
obfuscate their contact
details via services like that
one, but that's a different
issue entirely. I also
personally have correspondence
addresses in the US, mainland
UK and a couple in Northern
Ireland. I don't live at any
of them, but you can send me
physical mail and I will get
it. You could argue that the
address is "fake", but as I
can get mail to it I'd suspect
that in many cases it'd be
considered valid.<br>
> >
>>><br>
> >
>>> Regards<br>
> >
>>><br>
> >
>>> Michele<br>
> >
>>><br>
> >
>>> --<br>
> >
>>> Mr Michele Neylon<br>
> >
>>> Blacknight
Solutions<br>
> >
>>> Hosting,
Colocation & Domains<br>
> >
>>> <a
moz-do-not-send="true"
href="https://www.blacknight.com/"
target="_blank">https://www.blacknight.com/</a><br>
> >
>>> <a
moz-do-not-send="true"
href="http://blacknight.blog/"
target="_blank">http://blacknight.blog/</a><br>
> >
>>> Intl. <a
moz-do-not-send="true"
href="tel:%2B353%20%280%29%2059%20%209183072"
target="_blank">
+353 (0) 59 9183072</a><br>
> >
>>> Direct Dial: <a
moz-do-not-send="true"
href="tel:%2B353%20%280%2959%209183090"
target="_blank">
+353 (0)59 9183090</a><br>
> >
>>> Personal blog: <a
moz-do-not-send="true"
href="https://michele.blog/"
target="_blank">
https://michele.blog/</a><br>
> >
>>> Some thoughts: <a
moz-do-not-send="true"
href="https://ceo.hosting/"
target="_blank">
https://ceo.hosting/</a><br>
> >
>>>
-------------------------------<br>
> >
>>> Blacknight
Internet Solutions Ltd, Unit
12A,Barrowside Business<br>
> >
>>> Park,Sleaty<br>
> >
>>>
Road,Graiguecullen,Carlow,R93
X265,Ireland Company No.:
370845<br>
> >
>>>
_______________________________________________<br>
> >
>>> gnso-rds-pdp-wg
mailing list<br>
> >
>>> <a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">
gnso-rds-pdp-wg@icann.org</a><br>
> >
>>> <a
moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
> >
>>
_______________________________________________<br>
> >
>> gnso-rds-pdp-wg
mailing list<br>
> >
>> <a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">
gnso-rds-pdp-wg@icann.org</a><br>
> >
>> <a
moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
> > >
_______________________________________________<br>
> > >
gnso-rds-pdp-wg mailing list<br>
> > >
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
> > >
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
> ><br>
> > --<br>
> > Bei
weiteren Fragen stehen wir
Ihnen gerne zur Verfügung.<br>
> ><br>
> > Mit
freundlichen Grüßen,<br>
> ><br>
> >
Volker A. Greimann<br>
> > -
Rechtsabteilung -<br>
> ><br>
> >
Key-Systems GmbH<br>
> > Im
Oberen Werk 1<br>
> > 66386
St. Ingbert<br>
> > Tel.:
<a moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
target="_blank">
+49 (0) 6894 - 9396 901</a><br>
> > Fax.:
<a moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
target="_blank">
+49 (0) 6894 - 9396 851</a><br>
> >
Email: <a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">
vgreimann@key-systems.net</a><br>
> ><br>
> > Web:
<a moz-do-not-send="true"
href="http://www.key-systems.net"
target="_blank">www.key-systems.net</a>
/
<a moz-do-not-send="true"
href="http://www.RRPproxy.net"
target="_blank">www.RRPproxy.net</a><br>
> > <a
moz-do-not-send="true"
href="http://www.domaindiscount24.com"
target="_blank">www.domaindiscount24.com</a>
/
<a moz-do-not-send="true"
href="http://www.BrandShelter.com"
target="_blank">www.BrandShelter.com</a><br>
> ><br>
> >
Folgen Sie uns bei Twitter
oder werden Sie unser Fan bei
Facebook:<br>
> > <a
moz-do-not-send="true"
href="http://www.facebook.com/KeySystems"
target="_blank">www.facebook.com/KeySystems</a><br>
> > <a
moz-do-not-send="true"
href="http://www.twitter.com/key_systems"
target="_blank">www.twitter.com/key_systems</a><br>
> ><br>
> >
Geschäftsführer: Alexander
Siffrin<br>
> >
Handelsregister Nr.: HR B
18835 - Saarbruecken<br>
> >
Umsatzsteuer ID.: DE211006534<br>
> ><br>
> >
Member of the KEYDRIVE GROUP<br>
> > <a
moz-do-not-send="true"
href="http://www.keydrive.lu"
target="_blank">www.keydrive.lu</a><br>
> ><br>
> > Der
Inhalt dieser Nachricht ist
vertraulich und nur für den
angegebenen Empfänger
bestimmt. Jede Form der
Kenntnisgabe, Veröffentlichung
oder Weitergabe an Dritte
durch den Empfänger ist
unzulässig. Sollte diese
Nachricht nicht für Sie
bestimmt sein, so bitten wir
Sie, sich mit uns per E-Mail
oder telefonisch in Verbindung
zu setzen.<br>
> ><br>
> >
--------------------------------------------<br>
> ><br>
> >
Should you have any further
questions, please do not
hesitate to contact us.<br>
> ><br>
> > Best
regards,<br>
> ><br>
> >
Volker A. Greimann<br>
> > -
legal department -<br>
> ><br>
> >
Key-Systems GmbH<br>
> > Im
Oberen Werk 1<br>
> > 66386
St. Ingbert<br>
> > Tel.:
<a moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
target="_blank">
+49 (0) 6894 - 9396 901</a><br>
> > Fax.:
<a moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
target="_blank">
+49 (0) 6894 - 9396 851</a><br>
> >
Email: <a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">
vgreimann@key-systems.net</a><br>
> ><br>
> > Web:
<a moz-do-not-send="true"
href="http://www.key-systems.net"
target="_blank">www.key-systems.net</a>
/
<a moz-do-not-send="true"
href="http://www.RRPproxy.net"
target="_blank">www.RRPproxy.net</a><br>
> > <a
moz-do-not-send="true"
href="http://www.domaindiscount24.com"
target="_blank">www.domaindiscount24.com</a>
/
<a moz-do-not-send="true"
href="http://www.BrandShelter.com"
target="_blank">www.BrandShelter.com</a><br>
> ><br>
> >
Follow us on Twitter or join
our fan community on Facebook
and stay updated:<br>
> > <a
moz-do-not-send="true"
href="http://www.facebook.com/KeySystems"
target="_blank">www.facebook.com/KeySystems</a><br>
> > <a
moz-do-not-send="true"
href="http://www.twitter.com/key_systems"
target="_blank">www.twitter.com/key_systems</a><br>
> ><br>
> > CEO:
Alexander Siffrin<br>
> >
Registration No.: HR B 18835 -
Saarbruecken<br>
> >
V.A.T. ID.: DE211006534<br>
> ><br>
> >
Member of the KEYDRIVE GROUP<br>
> > <a
moz-do-not-send="true"
href="http://www.keydrive.lu"
target="_blank">www.keydrive.lu</a><br>
> ><br>
> > This
e-mail and its attachments is
intended only for the person
to whom it is addressed.
Furthermore it is not
permitted to publish any
content of this email. You
must not use, disclose, copy,
print or rely on this e-mail.
If an addressing or
transmission error has
misdirected this e-mail,
kindly notify the author by
replying to this e-mail or
contacting us by telephone.<br>
> ><br>
> ><br>
> ><br>
> >
_______________________________________________<br>
> >
gnso-rds-pdp-wg mailing list<br>
> > <a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
> > <a
moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
> ><br>
> ><br>
><br>
> --<br>
> Bei weiteren
Fragen stehen wir Ihnen gerne
zur Verfügung.<br>
><br>
> Mit
freundlichen Grüßen,<br>
><br>
> Volker A.
Greimann<br>
> -
Rechtsabteilung -<br>
><br>
> Key-Systems
GmbH<br>
> Im Oberen Werk
1<br>
> 66386 St.
Ingbert<br>
> Tel.: <a
moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
target="_blank">
+49 (0) 6894 - 9396 901</a><br>
> Fax.: <a
moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
target="_blank">
+49 (0) 6894 - 9396 851</a><br>
> Email: <a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a><br>
><br>
> Web: <a
moz-do-not-send="true"
href="http://www.key-systems.net"
target="_blank">www.key-systems.net</a>
/
<a moz-do-not-send="true"
href="http://www.RRPproxy.net"
target="_blank">www.RRPproxy.net</a><br>
> <a
moz-do-not-send="true"
href="http://www.domaindiscount24.com"
target="_blank">www.domaindiscount24.com</a>
/
<a moz-do-not-send="true"
href="http://www.BrandShelter.com"
target="_blank">www.BrandShelter.com</a><br>
><br>
> Folgen Sie uns
bei Twitter oder werden Sie
unser Fan bei Facebook:<br>
> <a
moz-do-not-send="true"
href="http://www.facebook.com/KeySystems"
target="_blank">www.facebook.com/KeySystems</a><br>
> <a
moz-do-not-send="true"
href="http://www.twitter.com/key_systems"
target="_blank">www.twitter.com/key_systems</a><br>
><br>
>
Geschäftsführer: Alexander
Siffrin<br>
> Handelsregister
Nr.: HR B 18835 - Saarbruecken<br>
> Umsatzsteuer
ID.: DE211006534<br>
><br>
> Member of the
KEYDRIVE GROUP<br>
> <a
moz-do-not-send="true"
href="http://www.keydrive.lu"
target="_blank">www.keydrive.lu</a><br>
><br>
> Der Inhalt
dieser Nachricht ist
vertraulich und nur für den
angegebenen Empfänger
bestimmt. Jede Form der
Kenntnisgabe, Veröffentlichung
oder Weitergabe an Dritte
durch den Empfänger ist
unzulässig. Sollte diese
Nachricht nicht für Sie
bestimmt sein, so bitten wir
Sie, sich mit uns per E-Mail
oder telefonisch in Verbindung
zu setzen.<br>
><br>
>
--------------------------------------------<br>
><br>
> Should you have
any further questions, please
do not hesitate to contact us.<br>
><br>
> Best regards,<br>
><br>
> Volker A.
Greimann<br>
> - legal
department -<br>
><br>
> Key-Systems
GmbH<br>
> Im Oberen Werk
1<br>
> 66386 St.
Ingbert<br>
> Tel.: <a
moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
target="_blank">
+49 (0) 6894 - 9396 901</a><br>
> Fax.: <a
moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
target="_blank">
+49 (0) 6894 - 9396 851</a><br>
> Email: <a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a><br>
><br>
> Web: <a
moz-do-not-send="true"
href="http://www.key-systems.net"
target="_blank">www.key-systems.net</a>
/
<a moz-do-not-send="true"
href="http://www.RRPproxy.net"
target="_blank">www.RRPproxy.net</a><br>
> <a
moz-do-not-send="true"
href="http://www.domaindiscount24.com"
target="_blank">www.domaindiscount24.com</a>
/
<a moz-do-not-send="true"
href="http://www.BrandShelter.com"
target="_blank">www.BrandShelter.com</a><br>
><br>
> Follow us on
Twitter or join our fan
community on Facebook and stay
updated:<br>
> <a
moz-do-not-send="true"
href="http://www.facebook.com/KeySystems"
target="_blank">www.facebook.com/KeySystems</a><br>
> <a
moz-do-not-send="true"
href="http://www.twitter.com/key_systems"
target="_blank">www.twitter.com/key_systems</a><br>
><br>
> CEO: Alexander
Siffrin<br>
> Registration
No.: HR B 18835 - Saarbruecken<br>
> V.A.T. ID.:
DE211006534<br>
><br>
> Member of the
KEYDRIVE GROUP<br>
> <a
moz-do-not-send="true"
href="http://www.keydrive.lu"
target="_blank">www.keydrive.lu</a><br>
><br>
> This e-mail and
its attachments is intended
only for the person to whom it
is addressed. Furthermore it
is not permitted to publish
any content of this email. You
must not use, disclose, copy,
print or rely on this e-mail.
If an addressing or
transmission error has
misdirected this e-mail,
kindly notify the author by
replying to this e-mail or
contacting us by telephone.<br>
><br>
><br>
><br>
><br>
><br>
--<br>
Bei weiteren Fragen
stehen wir Ihnen gerne zur
Verfügung.<br>
Mit freundlichen
Grüßen,<br>
Volker A. Greimann<br>
- Rechtsabteilung -<br>
Key-Systems GmbH<br>
Im Oberen Werk 1<br>
66386 St. Ingbert<br>
Tel.: <a
moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
target="_blank">
+49 (0) 6894 - 9396 901</a><br>
Fax.: <a
moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
target="_blank">
+49 (0) 6894 - 9396 851</a><br>
Email: <a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a><br>
Web: <a
moz-do-not-send="true"
href="http://www.key-systems.net"
target="_blank">www.key-systems.net</a>
/
<a moz-do-not-send="true"
href="http://www.RRPproxy.net"
target="_blank">www.RRPproxy.net</a><br>
<a moz-do-not-send="true"
href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a>
/
<a moz-do-not-send="true"
href="http://www.BrandShelter.com"
target="_blank">www.BrandShelter.com</a><br>
Folgen Sie uns bei
Twitter oder werden Sie unser
Fan bei Facebook:<br>
<a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><br>
<a moz-do-not-send="true"
href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><br>
Geschäftsführer:
Alexander Siffrin<br>
Handelsregister Nr.: HR B
18835 - Saarbruecken<br>
Umsatzsteuer ID.:
DE211006534<br>
Member of the
KEYDRIVE GROUP<br>
<a moz-do-not-send="true"
href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a><br>
Der Inhalt dieser
Nachricht ist vertraulich und
nur für den angegebenen
Empfänger bestimmt. Jede Form
der Kenntnisgabe,
Veröffentlichung oder
Weitergabe an Dritte durch den
Empfänger ist unzulässig.
Sollte diese Nachricht nicht
für Sie bestimmt sein, so
bitten wir Sie, sich mit uns
per E-Mail oder telefonisch in
Verbindung zu setzen.<br>
--------------------------------------------<br>
Should you have any
further questions, please do
not hesitate to contact us.<br>
Best regards,<br>
Volker A. Greimann<br>
- legal department -<br>
Key-Systems GmbH<br>
Im Oberen Werk 1<br>
66386 St. Ingbert<br>
Tel.: <a
moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
target="_blank">
+49 (0) 6894 - 9396 901</a><br>
Fax.: <a
moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
target="_blank">
+49 (0) 6894 - 9396 851</a><br>
Email: <a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a><br>
Web: <a
moz-do-not-send="true"
href="http://www.key-systems.net"
target="_blank">www.key-systems.net</a>
/
<a moz-do-not-send="true"
href="http://www.RRPproxy.net"
target="_blank">www.RRPproxy.net</a><br>
<a moz-do-not-send="true"
href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a>
/
<a moz-do-not-send="true"
href="http://www.BrandShelter.com"
target="_blank">www.BrandShelter.com</a><br>
Follow us on Twitter
or join our fan community on
Facebook and stay updated:<br>
<a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><br>
<a moz-do-not-send="true"
href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><br>
CEO: Alexander
Siffrin<br>
Registration No.: HR B
18835 - Saarbruecken<br>
V.A.T. ID.: DE211006534<br>
Member of the
KEYDRIVE GROUP<br>
<a moz-do-not-send="true"
href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a><br>
This e-mail and its
attachments is intended only
for the person to whom it is
addressed. Furthermore it is
not permitted to publish any
content of this email. You
must not use, disclose, copy,
print or rely on this e-mail.
If an addressing or
transmission error has
misdirected this e-mail,
kindly notify the author by
replying to this e-mail or
contacting us by telephone.<br>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</blockquote>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</blockquote>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
-- <br>
Bei weiteren Fragen stehen wir
Ihnen gerne zur Verfügung.<br>
<br>
Mit freundlichen Grüßen,<br>
<br>
Volker A. Greimann<br>
- Rechtsabteilung -<br>
<br>
Key-Systems GmbH<br>
Im Oberen Werk 1<br>
66386 St. Ingbert<br>
Tel.: <a moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
target="_blank">+49 (0) 6894 -
9396 901</a><br>
Fax.: <a moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
target="_blank">+49 (0) 6894 -
9396 851</a><br>
Email: <a moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><br>
<br>
Web: <a moz-do-not-send="true"
href="http://www.key-systems.net"
target="_blank">www.key-systems.net</a>
/
<a moz-do-not-send="true"
href="http://www.RRPproxy.net"
target="_blank">www.RRPproxy.net</a><br>
<a moz-do-not-send="true"
href="http://www.domaindiscount24.com"
target="_blank">www.domaindiscount24.com</a>
/
<a moz-do-not-send="true"
href="http://www.BrandShelter.com"
target="_blank">www.BrandShelter.com</a><br>
<br>
Folgen Sie uns bei Twitter oder
werden Sie unser Fan bei Facebook:<br>
<a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems"
target="_blank">www.facebook.com/KeySystems</a><br>
<a moz-do-not-send="true"
href="http://www.twitter.com/key_systems"
target="_blank">www.twitter.com/key_systems</a><br>
<br>
Geschäftsführer: Alexander Siffrin<br>
Handelsregister Nr.: HR B 18835 -
Saarbruecken<br>
Umsatzsteuer ID.: DE211006534<br>
<br>
Member of the KEYDRIVE GROUP<br>
<a moz-do-not-send="true"
href="http://www.keydrive.lu"
target="_blank">www.keydrive.lu</a><br>
<br>
Der Inhalt dieser Nachricht ist
vertraulich und nur für den
angegebenen Empfänger bestimmt.
Jede Form der Kenntnisgabe,
Veröffentlichung oder Weitergabe
an Dritte durch den Empfänger ist
unzulässig. Sollte diese Nachricht
nicht für Sie bestimmt sein, so
bitten wir Sie, sich mit uns per
E-Mail oder telefonisch in
Verbindung zu setzen.<br>
<br>
--------------------------------------------<br>
<br>
Should you have any further
questions, please do not hesitate
to contact us.<br>
<br>
Best regards,<br>
<br>
Volker A. Greimann<br>
- legal department -<br>
<br>
Key-Systems GmbH<br>
Im Oberen Werk 1<br>
66386 St. Ingbert<br>
Tel.: <a moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
target="_blank">+49 (0) 6894 -
9396 901</a><br>
Fax.: <a moz-do-not-send="true"
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
target="_blank">+49 (0) 6894 -
9396 851</a><br>
Email: <a moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><br>
<br>
Web: <a moz-do-not-send="true"
href="http://www.key-systems.net"
target="_blank">www.key-systems.net</a>
/
<a moz-do-not-send="true"
href="http://www.RRPproxy.net"
target="_blank">www.RRPproxy.net</a><br>
<a moz-do-not-send="true"
href="http://www.domaindiscount24.com"
target="_blank">www.domaindiscount24.com</a>
/
<a moz-do-not-send="true"
href="http://www.BrandShelter.com"
target="_blank">www.BrandShelter.com</a><br>
<br>
Follow us on Twitter or join our
fan community on Facebook and stay
updated:<br>
<a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems"
target="_blank">www.facebook.com/KeySystems</a><br>
<a moz-do-not-send="true"
href="http://www.twitter.com/key_systems"
target="_blank">www.twitter.com/key_systems</a><br>
<br>
CEO: Alexander Siffrin<br>
Registration No.: HR B 18835 -
Saarbruecken<br>
V.A.T. ID.: DE211006534<br>
<br>
Member of the KEYDRIVE GROUP<br>
<a moz-do-not-send="true"
href="http://www.keydrive.lu"
target="_blank">www.keydrive.lu</a><br>
<br>
This e-mail and its attachments is
intended only for the person to
whom it is addressed. Furthermore
it is not permitted to publish any
content of this email. You must
not use, disclose, copy, print or
rely on this e-mail. If an
addressing or transmission error
has misdirected this e-mail,
kindly notify the author by
replying to this e-mail or
contacting us by telephone.<br>
<br>
<br>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
</body>
</html>