<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Full agreement on this point<br>
</p>
<br>
<div class="moz-cite-prefix">On 11/28/2017 01:30 PM, Kris Seeburn
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:C8185C87-9D92-43E1-9C83-BD9976FBAF2E@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
As we move on …one way or the other the GDPR and other aligned
privacy laws will catch up eventually. We will need to find levels
and technical ways and reasons to get things to work. We move to
RDAPis fine as we look ahead but we should be able to not only
look at the laws that we need to respect but also to find
technical ways to get and make sure things still continue towork.
As this stage personally both are as important.<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Nov 28, 2017, at 23:15, allison nixon <<a
href="mailto:elsakoo@gmail.com" class=""
moz-do-not-send="true">elsakoo@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Most systems operators are not
afraid to block entire TLDs. While there are no scientific
studies out on this matter AFAIK, the help forums are
littered with people asking how to block entire TLDs, and
also registrants on those TLDs asking why everyone is
blocking them. It's enough to conclusively say this is
already an issue, and we can thank abuse for this.
<div class=""><br class="">
</div>
<div class="">In this Reddit post, a user learns the hard
truth about his brand new XYZ domain:</div>
<div class=""><a
href="https://www.reddit.com/r/webdev/comments/6jq6f5/getting_blocked_should_i_abandon_my_xyz_domain/"
class="" moz-do-not-send="true">https://www.reddit.com/r/webdev/comments/6jq6f5/getting_blocked_should_i_abandon_my_xyz_domain/</a><br
class="">
</div>
<div class=""><br class="">
</div>
<div class="">This article discusses Facebook's block of
all XYZ domains:</div>
<div class=""><a
href="http://adamyamada.com/facebook-blocks-xyz-domains-new-domains-pages/"
class="" moz-do-not-send="true">http://adamyamada.com/facebook-blocks-xyz-domains-new-domains-pages/</a><br
class="">
</div>
<div class=""><br class="">
</div>
<div class="">This Malwarebytes staff member explains to a
legitimate registrant that all .SCIENCE TLDs are blocked
and he gets no exception: </div>
<div class=""><a
href="https://forums.malwarebytes.com/topic/173535-all-my-science-domains-blocked/"
class="" moz-do-not-send="true">https://forums.malwarebytes.com/topic/173535-all-my-science-domains-blocked/</a><br
class="">
</div>
<div class=""><br class="">
</div>
<div class="">In fact, the Malwarebytes "false positive"
forum is littered with owners of hacked domains that
discovered their problem because of a block, not because
of a notification:</div>
<div class=""><a
href="https://forums.malwarebytes.com/forum/123-website-blocking/"
class="" moz-do-not-send="true">https://forums.malwarebytes.com/forum/123-website-blocking/</a><br
class="">
</div>
<div class=""><br class="">
</div>
<div class="">This user asks for an 'Existing list of
garbage "new" TLDs' to block</div>
<div class=""><a
href="https://vamsoft.com/forum/topic/597/existing-list-of-garbage-new-tlds"
class="" moz-do-not-send="true">https://vamsoft.com/forum/topic/597/existing-list-of-garbage-new-tlds</a><br
class="">
</div>
<div class=""><br class="">
</div>
<div class="">There are 179 Google search results for
people asking Microsoft's help service for ways to block
entire TLDs:</div>
<div class=""><a
href="https://www.google.com/search?q=how+do+i+block+TLD+site:answers.microsoft.com"
class="" moz-do-not-send="true">https://www.google.com/search?q=how+do+i+block+TLD+site:answers.microsoft.com</a><br
class="">
</div>
<div class=""><br class="">
</div>
<div class="">There are 72,500 Google search results
for "how to block" "tld":<br class="">
<a
href="https://www.google.com/search?q=%22how+to+block%22+%22tld%22"
class="" moz-do-not-send="true">https://www.google.com/search?q=%22how+to+block%22+%22tld%22</a></div>
<div class=""><br class="">
</div>
<div class="">The Internet is effectively "broken" for any
legitimate registrants on these TLDs. </div>
<div class=""><br class="">
</div>
<div class="">As a seller of some of those same TLDs,
should you be concerned if your customers purchase
domains rendered useless due to blocking? </div>
<div class="">Would you actually refund a customer if they
told you they couldn't use the domain for e-mail due to
the TLD?</div>
<div class="">Would you warn your prospective .XYZ,
.STUDY, .PRESS, .PARTY, etc, customers that they should
not use the domains for e-mail?</div>
<div class="">When ICANN releases new gTLDs in the future,
do you think that those domains will ever be able to
send e-mail?</div>
<div class=""><br class="">
</div>
<div class="">Truly, the rest of the world will be fine.
The more that ICANN has the "not my problem" attitude,
the more the rest of the world is going to push back.
ICANN seems to have lost the ability to release new
gTLDs without severe connectivity issues, so we also
need to ask the question: "why are these guys selling
the digital equivalent of the scarlet letter and not
warning their customers beforehand?"</div>
<div class=""><br class="">
</div>
<div class="">I think the question of selling defective
products is one that needs to be addressed more
seriously by regulators and outside parties. </div>
<div class=""><br class="">
</div>
<div class="">I can also tell you that security vendors
are already looking into other anti-abuse techniques for
domains post-WHOIS, and I can also tell you that they
will result in an increase in the percentage of
legitimate domains that are blocked. This is your
problem now. </div>
<div class=""><br class="">
</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Tue, Nov 28, 2017 at 12:43 PM,
Volker Greimann <span dir="ltr" class=""><<a
href="mailto:vgreimann@key-systems.net"
target="_blank" class="" moz-do-not-send="true">vgreimann@key-systems.net</a>></span>
wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Andrew,<br class="">
<br class="">
re:hotbed I was rather intending to ask whether there
is a direct correllation between TLDs with redacted
whois and issues that go unresolved. So do you have
more unresolved issues in .<a href="http://co.uk/"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">co.uk</a> than in .com (if
numbers are normalized for registered domain names).<br
class="">
<br class="">
I am sure no one would consider blocking the entire
mail traffic originating from the United Kingdom Top
Level Domain just because you cannot resolve some
issues in a few domains, correct?<br class="">
<br class="">
So if everyone followed their (or a similar) model,
the internet would not break. Some issues would get
harder to solve (or take longer). I am asking because
that is what most likely will happen on May 25 or
sooner.<br class="">
<br class="">
Volker
<div class="">
<div class="h5"><br class="">
<br class="">
<br class="">
Am 28.11.2017 um 18:27 schrieb Andrew Sullivan:<br
class="">
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
On Tue, Nov 28, 2017 at 04:31:56PM +0100, Volker
Greimann wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
case of internet operability issues. While I
appreciate that there can be<br class="">
issues that would necessitate the ability to
quickly contact whoever can fix<br class="">
the issue, I wonder how this problem is solved
in TLDs where whois is<br class="">
already redacted.<br class="">
</blockquote>
It's not. In that case, if I am the one who has
this experience and I<br class="">
can't reach the target, then the problem goes
unresolved. In mail<br class="">
cases, as John suggests elsewhere in this
thread, the answer is very<br class="">
likely that mail is blocked. People seem
surprised these days that<br class="">
mail is so fragile, but this sort of thing is
part of the reason.<br class="">
<br class="">
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
So how does it work there? Are these TLDs
hotbeds of DNS issues and<br class="">
unresolved problems?<br class="">
</blockquote>
I don't know what you mean by "hotbed", or
whether that is intended to<br class="">
be dismissive. Some TLDs defintely have more
DNS problems than<br class="">
others. Given how hard the DNS works to make
connections happen even<br class="">
when things are badly misconfigured, lots of
stuff will work to some<br class="">
extent even when it is badly configured. But
DNS operations people<br class="">
trade stories about problems amongst themselves,
after giving up on<br class="">
sites because whois can't help and the mname in
the SOA record is<br class="">
broken. I find this happens more often than you
might expect.<br class="">
<br class="">
But yes, there are broken domains on the
Internet. I find it hard to<br class="">
believe that would be even slightly remarkable.<br
class="">
<br class="">
Best regards,<br class="">
<br class="">
A<br class="">
<br class="">
</blockquote>
<br class="">
-- <br class="">
</div>
</div>
Bei weiteren Fragen stehen wir Ihnen gerne zur
Verfügung.<br class="">
<br class="">
Mit freundlichen Grüßen,<br class="">
<br class="">
Volker A. Greimann<br class="">
- Rechtsabteilung -<br class="">
<br class="">
Key-Systems GmbH<br class="">
Im Oberen Werk 1<br class="">
66386 St. Ingbert<br class="">
Tel.: <a
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
value="+4968949396901" target="_blank" class=""
moz-do-not-send="true">+49 (0) 6894 - 9396 901</a><br
class="">
Fax.: <a
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
value="+4968949396851" target="_blank" class=""
moz-do-not-send="true">+49 (0) 6894 - 9396 851</a><br
class="">
Email: <a href="mailto:vgreimann@key-systems.net"
target="_blank" class="" moz-do-not-send="true">vgreimann@key-systems.net</a><br
class="">
<br class="">
Web: <a href="http://www.key-systems.net/"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.key-systems.net</a> / <a
href="http://www.rrpproxy.net/" rel="noreferrer"
target="_blank" class="" moz-do-not-send="true">www.RRPproxy.net</a><br
class="">
<a href="http://www.domaindiscount24.com/"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.domaindiscount24.com</a>
/ <a href="http://www.brandshelter.com/"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.BrandShelter.com</a><br
class="">
<br class="">
Folgen Sie uns bei Twitter oder werden Sie unser Fan
bei Facebook:<br class="">
<a href="http://www.facebook.com/KeySystems"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.facebook.com/KeySystems</a><br
class="">
<a href="http://www.twitter.com/key_systems"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.twitter.com/key_systems</a><br
class="">
<br class="">
Geschäftsführer: Alexander Siffrin<br class="">
Handelsregister Nr.: HR B 18835 - Saarbruecken<br
class="">
Umsatzsteuer ID.: DE211006534<br class="">
<br class="">
Member of the KEYDRIVE GROUP<br class="">
<a href="http://www.keydrive.lu/" rel="noreferrer"
target="_blank" class="" moz-do-not-send="true">www.keydrive.lu</a><br
class="">
<br class="">
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 class="">
<br class="">
------------------------------<wbr class="">--------------<br
class="">
<br class="">
Should you have any further questions, please do not
hesitate to contact us.<span class=""><br class="">
<br class="">
Best regards,<br class="">
<br class="">
Volker A. Greimann<br class="">
</span>
- legal department -<br class="">
<br class="">
Key-Systems GmbH<br class="">
Im Oberen Werk 1<br class="">
66386 St. Ingbert<br class="">
Tel.: <a
href="tel:%2B49%20%280%29%206894%20-%209396%20901"
value="+4968949396901" target="_blank" class=""
moz-do-not-send="true">+49 (0) 6894 - 9396 901</a><br
class="">
Fax.: <a
href="tel:%2B49%20%280%29%206894%20-%209396%20851"
value="+4968949396851" target="_blank" class=""
moz-do-not-send="true">+49 (0) 6894 - 9396 851</a><br
class="">
Email: <a href="mailto:vgreimann@key-systems.net"
target="_blank" class="" moz-do-not-send="true">vgreimann@key-systems.net</a><br
class="">
<br class="">
Web: <a href="http://www.key-systems.net/"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.key-systems.net</a> / <a
href="http://www.rrpproxy.net/" rel="noreferrer"
target="_blank" class="" moz-do-not-send="true">www.RRPproxy.net</a><br
class="">
<a href="http://www.domaindiscount24.com/"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.domaindiscount24.com</a>
/ <a href="http://www.brandshelter.com/"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.BrandShelter.com</a><br
class="">
<br class="">
Follow us on Twitter or join our fan community on
Facebook and stay updated:<br class="">
<a href="http://www.facebook.com/KeySystems"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.facebook.com/KeySystems</a><br
class="">
<a href="http://www.twitter.com/key_systems"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">www.twitter.com/key_systems</a><br
class="">
<br class="">
CEO: Alexander Siffrin<br class="">
Registration No.: HR B 18835 - Saarbruecken<br
class="">
V.A.T. ID.: DE211006534<br class="">
<br class="">
Member of the KEYDRIVE GROUP<br class="">
<a href="http://www.keydrive.lu/" rel="noreferrer"
target="_blank" class="" moz-do-not-send="true">www.keydrive.lu</a><br
class="">
<br class="">
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.
<div class="HOEnZb">
<div class="h5"><br class="">
<br class="">
<br class="">
<br class="">
______________________________<wbr class="">_________________<br
class="">
gnso-rds-pdp-wg mailing list<br class="">
<a href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" class="" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br
class="">
<a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">https://mm.icann.org/mailman/l<wbr
class="">istinfo/gnso-rds-pdp-wg</a></div>
</div>
</blockquote>
</div>
<br class="">
<br class="" clear="all">
<div class=""><br class="">
</div>
-- <br class="">
<div class="gmail_signature"
data-smartmail="gmail_signature">_________________________________<br
class="">
Note to self: Pillage BEFORE burning.</div>
</div>
_______________________________________________<br class="">
gnso-rds-pdp-wg mailing list<br class="">
<a href="mailto:gnso-rds-pdp-wg@icann.org" class=""
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br
class="">
<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></div>
</blockquote>
</div>
<br class="">
<div class="">
<div dir="auto" style="color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; orphans: auto; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px; -webkit-text-size-adjust:
auto; -webkit-text-stroke-width: 0px; word-wrap: break-word;
-webkit-nbsp-mode: space; line-break: after-white-space;"
class="">
<div dir="auto" style="color: rgb(0, 0, 0); letter-spacing:
normal; text-align: start; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; word-wrap: break-word;
-webkit-nbsp-mode: space; line-break: after-white-space;"
class="">
<div dir="auto" style="color: rgb(0, 0, 0); letter-spacing:
normal; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; word-spacing:
0px; -webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space; line-break:
after-white-space;" class="">
<div dir="auto" style="color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; -webkit-text-stroke-width:
0px; word-wrap: break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing:
normal; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;" class=""><br
class="Apple-interchange-newline">
<br class="">
</div>
<div style="color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;" class=""><br
class="Apple-interchange-newline">
<br class="">
</div>
<div style="color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;" class="">Kris
Seeburn</div>
<div style="color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;" class=""><a
href="mailto:seeburn.k@gmail.com" class=""
moz-do-not-send="true">seeburn.k@gmail.com</a></div>
<div style="color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;" class="">
<ul style="margin: 0px; padding: 0px 0px 8px;
border: 0px; outline: 0px; font-family:
Helvetica, Arial, sans-serif; vertical-align:
baseline; list-style: none; line-height: 17px;
display: table-cell; width: 504px; color:
rgb(51, 51, 51);" class="">
<li style="margin: 0px; padding: 8px 12px 2px
0px; border: 0px; outline: 0px; font-style:
inherit; font-size: 11px; font-family:
inherit; vertical-align: baseline;
font-variant-ligatures: inherit;
font-variant-position: inherit;
font-variant-caps: inherit;
font-variant-numeric: inherit;
font-variant-alternates: inherit;
font-variant-east-asian: inherit; line-height:
1.2em;" class="">
<dl class="public-profile" style="margin: 0px;
padding: 0px; border: 0px; outline: 0px;
font-style: inherit; font-family: inherit;
vertical-align: baseline;
font-variant-ligatures: inherit;
font-variant-position: inherit;
font-variant-caps: inherit;
font-variant-numeric: inherit;
font-variant-alternates: inherit;
font-variant-east-asian: inherit;
line-height: inherit; word-wrap:
break-word;">
<dd style="margin: 0px; padding: 2px 9px 1px
0px; border: 0px; outline: 0px;
font-style: inherit; font-family: inherit;
vertical-align: top;
font-variant-ligatures: inherit;
font-variant-position: inherit;
font-variant-caps: inherit;
font-variant-numeric: inherit;
font-variant-alternates: inherit;
font-variant-east-asian: inherit;
line-height: inherit; display:
inline-block; zoom: 1;" class=""><a
href="http://www.linkedin.com/in/kseeburn/"
title="View public profile"
name="webProfileURL" style="margin: 0px
10px 0px 0px; padding: 0px 0px 0px 19px;
border: 0px; outline: 0px; font-style:
inherit; font-family: inherit;
vertical-align: middle; text-decoration:
none; color: rgb(102, 102, 102);
font-variant-ligatures: inherit;
font-variant-position: inherit;
font-variant-caps: inherit;
font-variant-numeric: inherit;
font-variant-alternates: inherit;
font-variant-east-asian: inherit;
line-height: inherit; display:
inline-block; zoom: 1; background-image:
url(http://s.c.lnkd.licdn.com/scds/common/u/images/apps/profile/sprite/sprite_profile_top_card_v8.png);
background-position: 0px -249px;
background-repeat: no-repeat no-repeat;"
class="" moz-do-not-send="true">www.linkedin.com/in/kseeburn/</a></dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<span style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px; text-transform:
none; white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px;"><span><span><br class="Apple-interchange-newline">
<span><img apple-inline="yes"
id="FD046824-DB19-4986-967A-4FE4353AED1A"
src="cid:part36.BFB71D0B.38A45781@bambenekconsulting.com"
class=""></span>
</span></span></span></div>
<br class="">
<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>