<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I'm not aware. I wonder if IDN EPDP members could clarify.<br>
</p>
<div class="moz-cite-prefix">On 22 Oct 2023 10:37, Thomas Rickert |
rickert.law wrote:<br>
</div>
<blockquote type="cite"
cite="mid:C16FCE9F-FC36-4C28-BE9F-E79F7C09BA00@rickert.law">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator"
content="Microsoft Word 15 (filtered medium)">
<style>@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;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}span.E-MailFormatvorlage19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}div.WordSection1
{page:WordSection1;}</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Thanks for your analysis, Mark.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">I may have missed this, but has there been any
discussion around grandfathering or bundles of SLDs under
both TLDs that would help avoid confusion of an identical
second level domain under both TLDs?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Thomas<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<div
style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:12.0pt;color:black">Von: </span></b><span
style="font-size:12.0pt;color:black">council
<a class="moz-txt-link-rfc2396E" href="mailto:council-bounces@gnso.icann.org"><council-bounces@gnso.icann.org></a> im Auftrag von Mark
Datysgeld via council <a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a><br>
<b>Antworten an: </b>Mark Datysgeld
<a class="moz-txt-link-rfc2396E" href="mailto:mark@governanceprimer.com"><mark@governanceprimer.com></a><br>
<b>Datum: </b>Sonntag, 22. Oktober 2023 um 10:17<br>
<b>An: </b><a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org">"council@gnso.icann.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a><br>
<b>Betreff: </b>[council] Further on dot québec<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>I have been studying the Latin Script Root Zone Label
Generation Rules [<a
href="https://www.icann.org/sites/default/files/lgr/proposal-japanese-lgr-20dec21-en.xml"
moz-do-not-send="true">here</a>] and, for practical
purposes, (U+0065) vs. é (U+00E9) are not variants. The
variants for lower case Latin letter "e" are listed under
"Variant Set 3" and consist of one homoglyph (forward and
reverse mapping) and one out-of-repertoire (reflexive)
instance, both which do not apply here. Also, é (U+00E9) is
recognized as part of the French language in the document, so
linguistic relevance is recognized there.<o:p></o:p></p>
<p>Potential for malice also does not come up as a significant
concern in the LGR, as opposed to something like dotted i
(U+0069) vs. dotless i (U+0131), for example.<o:p></o:p></p>
<p>That said, considering that we are dealing with a geoTLD,
linguistic and cultural relevance are important aspects, and
looking into the writing of the word "Québec" on the Web, both
the the "e" and "é" cases seem to be widely employed, in such
a way that they are interchangeable in a way. If these TLDs
were to be managed independently, that would almost certainly
lead to confusion.<o:p></o:p></p>
<p>However, the requestor of the accented TLD is the same as
that of the ASCII TLD, which is PointQuébec, so we are looking
into a "same entity" situation. If PointQuébec were to run
both TLDs as if they were the same (as if they were variants),
meaning that domain names would resolve consistently instead
of being operated independently, this would allow the people
of Québec the linguistic freedom to utilize their language
while at the same time avoiding confusion.<o:p></o:p></p>
<p>Since, as Seb pointed out, this is the only applicant from
the first round reaching out to have this issue resolved, it
does not seem to be out of scope to simply recognize their
request, and allow them to operate the TLDs in this way, more
than anything because there seems to be no good reason not to.
We would just need to be very clear about the necessity of
both TLDs operating in this consistent manner.<o:p></o:p></p>
<p>Best,<o:p></o:p></p>
<div>
<p class="MsoNormal">-- <br>
Mark W. Datysgeld [<a href="https://markwd.website"
moz-do-not-send="true">markwd.website</a>]<br>
Director at Governance Primer [<a
href="https://governanceprimer.com" moz-do-not-send="true">governanceprimer.com</a>]<br>
ICANN GNSO Councilor<o:p></o:p></p>
</div>
</div>
</blockquote>
<div class="moz-signature">-- <br>
Mark W. Datysgeld [<a href="https://markwd.website">markwd.website</a>]<br>
Director at Governance Primer [<a
href="https://governanceprimer.com">governanceprimer.com</a>]<br>
ICANN GNSO Councilor</div>
</body>
</html>