<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 9/12/2019 6:40 PM, Andrew Sullivan
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20190913014056.2zvfeizoc47jl2es@mx4.yitter.info">
<pre class="moz-quote-pre" wrap="">On Thu, Sep 12, 2019 at 06:27:49PM -0700, Asmus Freytag wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Which would be a proper concern, but not if EURID applied for both.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Why? The mere fact that the same operator operates two TLDs does not
imply that they are actually or reasonably related in any way. For
instance, com and net are both operated by Verisign, but they have
nothing to do with each other and there is no reason to suppose that a
given label in .com has anything to do with the identical label in
.net. The fact that two strings are merely visually similar to one
another similarly does not give us reason to suppose the policies in
one will be affected by decisions in the other (nor, for that matter,
that they should be). And it's quite clear that "bundling" of names
has been roundly rejected by the market except maybe in a couple quite
specific cases.</pre>
</blockquote>
<p>Well, if that's the case we categorically shouldn't allow any
allocatable variants <br>
for TLDs, but the procedure you authored contemplates precisely
that.</p>
<p>Confused !?!<br>
</p>
<p>A./<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:20190913014056.2zvfeizoc47jl2es@mx4.yitter.info">
<pre class="moz-quote-pre" wrap="">
Best regards,
A
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>