<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote
cite="mid:CACLR7wL8GzrtqMtX_UhiWfrO8VH+DBx5HLa3dhtQ=W-m2w5ccw@mail.gmail.com"
type="cite">
<div dir="ltr">Scott, when I say fake email for WHOIS, most people
generally understand it to mean a junk email address, a
"mailinator" or "yopmail" address, or a newly created email
address that will never be used again. The "verification"
process is straightforward and quickly learned by anyone that
doesn't understand, and no part of the process forces people to
use an e-mail address that they actively use. At this point in
time most Internet users understand the concept of a junk email
address.</div>
</blockquote>
That is a completely different issue as the whois is essentially
correct and the address fulfills all policy requirements. The
availability and use of such addresses may also have legitimate
purposes. <br>
<blockquote
cite="mid:CACLR7wL8GzrtqMtX_UhiWfrO8VH+DBx5HLa3dhtQ=W-m2w5ccw@mail.gmail.com"
type="cite">
<div dir="ltr">The fact that it happened twice, three, and ten
years ago does not change the daily reality that this
information is not verified, even when reported through a
registrar's abuse channels. I'm going to continue stating that
this policy is a joke until the reality of the bad state of
WHOIS data changes, and then I will change my mind based on the
evidence.</div>
</blockquote>
Verification may be impossible. Validation on the other hand is
possible. If you do not like the policy as it stands, propose an
alternative solution. Ideally also tell us who will pay for it.<br>
<br>
Best,<br>
Volker<br>
<blockquote
cite="mid:CACLR7wL8GzrtqMtX_UhiWfrO8VH+DBx5HLa3dhtQ=W-m2w5ccw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Feb 14, 2017 at 1:56 PM,
Hollenbeck, Scott <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:shollenbeck@verisign.com" target="_blank">shollenbeck@verisign.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div class="m_-5281647379422882632WordSection1">
<div style="border:none;border-left:solid blue
1.5pt;padding:0in 0in 0in 4.0pt">
<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">
allison nixon [mailto:<a
moz-do-not-send="true"
href="mailto:elsakoo@gmail.com"
target="_blank">elsakoo@gmail.com</a>]
<br>
<b>Sent:</b> Tuesday, February 14, 2017 1:35
PM<br>
<b>To:</b> Hollenbeck, Scott <<a
moz-do-not-send="true"
href="mailto:shollenbeck@verisign.com"
target="_blank">shollenbeck@verisign.com</a>><br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a>;
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><span
class=""><br>
<b>Subject:</b> [EXTERNAL] Re:
[gnso-rds-pdp-wg] Dangers of public whois</span></span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">>>[SAH] Actually, there
*are* requirements to provide valid data and for
registrars to perform validation processing:</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div><span class="">
<p class="MsoNormal">How do you expect toothless
policy to work *on the Internet*? Seriously?</p>
<p class="MsoNormal"><b><i><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></i></b></p>
</span>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:#1f497d">Yes,
seriously. Registrars who do not implement the
policy are subject to having their
accreditation revoked. ICANN has, in fact,
revoked or suspended accreditations. Here are
two examples:</span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:#1f497d"><a
moz-do-not-send="true"
href="https://www.icann.org/news/announcement-2-2007-03-16-en"
target="_blank">https://www.icann.org/news/<wbr>announcement-2-2007-03-16-en</a></span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:#1f497d"><a
moz-do-not-send="true"
href="https://www.icann.org/en/system/files/correspondence/serad-to-patel-2-18jul14-en.pdf"
target="_blank">https://www.icann.org/en/<wbr>system/files/correspondence/<wbr>serad-to-patel-2-18jul14-en.<wbr>pdf</a></span></p>
</div>
<span class="">
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">worst that can happen when
you put in fake whois data is that your domain
gets reported, you change "123 fake st" to
"124 fake st", and your registrar is satisfied
because what more can they possibly do. I know
this because I went through this with an old
sinkhole domain. It's a total joke. Let's not
pretend it's anything more than that.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
</span></div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:#1f497d">Not
true. A fake email address, for example, can
be detected easily when email sent to it (one
of the registrar’s validation requirements)
gets bounced back. The worst that can happen
is that your domain gets put into some
non-operational state (“suspend the
registration” per the RAA).<span
class="HOEnZb"></span></span></p>
<span class="HOEnZb"><font color="#888888">
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:#1f497d">Scott</span></p>
</font></span></div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">_________________________________<br>
Note to self: Pillage BEFORE burning.</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
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.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
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.
</pre>
</body>
</html>