<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
For sure, if I were an IDN registrant and experienced rejection of my domain name (or email address) by some application because all of a sudden it becomes a “forbidden” variant, I would be seriously annoyed.
<div class="">It is true that the affected domain names are probably a rounding error compared to the hundreds of millions domain names, but it would nevertheless (further) reduce confidence in IDNs - and this is something that we really do not need.</div>
<div class="">Cheers,</div>
<div class="">Roberto</div>
<div class=""><br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 13.05.2019, at 07:25, Jothan Frakes <<a href="mailto:jothan@jothan.com" class="">jothan@jothan.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">[speaking entirely in a personal capacity here]</div>
<div class=""><br class="">
</div>
<div class="">I strongly recommend that attention needs to be put towards how the registrants, as well as the provider channel are impacted, especially with respect to the impact on second level (or deeper) registration policies, and this not be trivialized. </div>
<div class=""><br class="">
</div>
<div class="">Confidence and Trust are a large component of attracting better adoption and driving forward UA projects.</div>
<div class=""><br class="">
</div>
<div class="">The user journey of a registrant needs a lot of consideration here. Also, commercially interested parties like registrars get to have very uncomfortable interaction with registrants who suddenly may have a domain that is hobbled or invalidated.
Software developers are looking at this as well, determining how (and if) to support IDN and UA.</div>
<div class=""><br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'm not sure how much of a problem this is in practice. When I went<br class="">
through and looked at all of the IDNs in gTLDs including all the old<br class="">
ones, the number that were grandfathered was quite small, well under<br class="">
1% of the total. </blockquote>
<div class=""> <br class="">
</div>
That was some helpful measurement. Building upon this, the grandfathered registrant-folk were probably a mix of innovators and entrepreneurs (or both). But the fact that they invested time and money, and have renewed these registrations over the span of time
indicates that they are interested in the stuff we're hoping to grow adoption and acceptance of.
<div class=""><br class="">
</div>
<div class="">Hopefully, if we can get more universal acceptance/awareness in communities that could benefit from them, the total sum of all IDN registrations we currently have will be 1% of some future number. <br class="">
</div>
<div class=""><br class="">
</div>
<div class="">My hope is that some future standard update at that point in time not break that statistically insignificant user pool, and this is what developers, IT management, and those who control product cycles where UA can be introduced are considering
when choosing what to have teams focus on in their road-maps.
<div class=""><br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Anytime you change the registration policies for an existing registry, <br class="">
you will have to figure out how to grandfather existing, delegated <br class="">
labels (if any).</blockquote>
The LGRs for several existing TLDS have changed, and .com and .net<br class="">
have some IDNs that predate any LGRs. The rule seems to be that you<br class="">
can renew whatever you have forever, but if it expires and it's not<br class="">
valid under the new rule, nobody can reregister it.</blockquote>
<div class=""><br class="">
</div>
<div class="">Grand-fathering the registrations is one aspect of addressing these things. This means a registrant has the option to continue to pay for the domain and keep using it, which is good. The challenge comes with standards updates that gradually
(or suddenly) diminish the ability to use that name to the level of benefit that was present at the time of registration.</div>
<div class=""><br class="">
</div>
<div class="">A better way to preserve confidence might be to buy them back or offer a path to updated standards for those registrants in a way that is reasonable and acceptable to them.</div>
<div class=""><br class="">
</div>
<div class="">Developers and development leaders will look closely at how this is addressed, as UA projects are harder, with more testing and QA, as well as other specializations which introduce greater scope than other projects that might have clearer profit/benefit
or prioritization.</div>
<div class=""><br class="">
</div>
<div class="">The manner in which we address legacy registrations will have an impact on the success of the UA </div>
<div class=""><br class="">
</div>
<div class="">-Jothan</div>
<div class=""><br class="">
</div>
<div class="">
<div class=""><br class="">
</div>
</div>
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, May 11, 2019 at 7:32 PM John Levine <<a href="mailto:john.levine@standcore.com" target="_blank" class="">john.levine@standcore.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
In article <<a href="mailto:54666ffb-2773-97e9-10d0-f6c0d4afa8aa@ix.netcom.com" target="_blank" class="">54666ffb-2773-97e9-10d0-f6c0d4afa8aa@ix.netcom.com</a>> you write:<br class="">
>Anytime you change the registration policies for an existing registry, <br class="">
>you will have to figure out how to grandfather existing, delegated <br class="">
>labels (if any).<br class="">
<br class="">
The LGRs for several existing TLDS have changed, and .com and .net<br class="">
have some IDNs that predate any LGRs. The rule seems to be that you<br class="">
can renew whatever you have forever, but if it expires and it's not<br class="">
valid under the new rule, nobody can reregister it.<br class="">
<br class="">
I'm not sure how much of a problem this is in practice. When I went<br class="">
through and looked at all of the IDNs in gTLDs including all the old<br class="">
ones, the number that were grandfathered was quite small, well under<br class="">
1% of the total. By percentages it seemed to be more of a problem<br class="">
that some new TLDs aren't following their own existing rules.<br class="">
<br class="">
R's,<br class="">
John<br class="">
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>