<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:"Helvetica Neue";
panose-1:2 0 5 3 0 0 0 2 0 4;}
@font-face
{font-family:HelveticaNeue;
panose-1:2 0 5 3 0 0 0 2 0 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Dear all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I want first to finish what is expected from Latin GP. After that people who want to work on this issue could continue. I am sure I do not have any more power to carry on .
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards Mirjana<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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">From: </span></b><span style="font-size:12.0pt;color:black">Bill Jouris <bill.jouris@insidethestack.com><br>
<b>Reply-To: </b>Bill Jouris <bill.jouris@insidethestack.com><br>
<b>Date: </b>Monday, July 9, 2018 at 19:11<br>
<b>To: </b>Mirjana Tasić <Mirjana.Tasic@rnids.rs>, Michael Bauland <Michael.Bauland@knipp.de>, Latin GP <latingp@icann.org><br>
<b>Subject: </b>Re: [Latingp] ODG: ODG: Variants -- Case for Considering Upper Case<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div id="yui_3_16_0_ym19_1_1530911355477_21370">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">The problem is that what is written (as opposed to what is registered) can be in mixed case. So what the *user* sees -- in an email or a document
or on a website -- may be in any mix of cases. No matter what the mix of cases, the link will always go to the same place.
<br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_21523">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black"><br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_21644">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">The "crime" is not by the user, but by the person writing the link -- and doing it in a way that they have done it for decades. I have seen
ICANN's website done as both icann.org and ICANN.org. I see companies, especially those with multi-word names, capitalize the first letter in each word: USBank.com for example. It may be regretible that this has become a common practice, but that's the long-standing
reality out there.<br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_22499">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black"><br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_22358">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">And there is no "punishment" available. The user, after all, is typically not the one who created the link in the document. What the variant
rules can do is keep someone who does not own the original domain from creating something that the user will see as the same. Thus allowing him to scam users.
<br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_21647">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black"><br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_21649">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">For example, suppose we decide that a Cyrillic Small Letter Em (
</span><span style="font-size:14.0pt;color:black">м</span><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black"> codepoint 043C) is NOT a variant of a Latin Small Letter M (m codepoint 006D). Then it is possible to create a (Cyrillic) TLD
of </span><span style="font-size:14.0pt;color:black">.</span><span style="font-size:14.0pt;color:black">сом</span><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">, because the last letter is visibly "different" from that in .com. Which,
in turn, means that the owner of every .com domain in the world will be faced with a choice:
<br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_21991">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">- register his domain name again, in the new TLD
<br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_22061">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">- let someone else register his domain name there, and live with the possibility that his customers will find themselves going somewhere else.
<br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_22081">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">The first option doubles his expense -- great for the companies which sell domain name registrations, but not for the user community. Not
to mention the possibility that the company simply doesn't realize the problem exists until it is too late -- most companies do not routinely keep track of new TLDs being created. And security problems involved in the latter situation are obvious.
<br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_22147">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black"><br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_22146">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">It isn't particularly hard to write variant rules which will stop that happening. There are a handful of Cyrillic letters, and a couple of
Greek letters, where the lower case looks like a Latin upper case letter. We just include them in our list of variants, and the problem doesn't arise. It's not something that will take us any significant amount of time to do as we go thru our process . .
. once we determine that it is appropriate to do so.<br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_22225">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black"><br>
<br>
<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_21371">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black"> <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_21517">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black">Bill Jouris<br>
Inside Products<br>
bill.jouris@insidethestack.com<br>
831-659-8360<br>
925-855-9512 (direct)<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_21518">
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-size:12.0pt;font-family:"Helvetica Neue";color:black"><o:p> </o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1530911355477_21653">
<div id="yui_3_16_0_ym19_1_1530911355477_21652">
<div id="yui_3_16_0_ym19_1_1530911355477_21651">
<div id="yui_3_16_0_ym19_1_1530911355477_21650">
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">
<hr size="0" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> Mirjana Tasić <Mirjana.Tasic@rnids.rs><br>
<b>To:</b> Michael Bauland <Michael.Bauland@knipp.de>; "latingp@icann.org" <latingp@icann.org>
<br>
<b>Sent:</b> Monday, July 9, 2018 6:16 AM<br>
<b>Subject:</b> [Latingp] ODG: ODG: Variants -- Case for Considering Upper Case</span><span style="font-size:12.0pt;font-family:HelveticaNeue;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:HelveticaNeue;color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:HelveticaNeue;color:black">Dear all,
<br>
<br>
Now I understand the point. My opinion that such cases cannot be prevented by developing any variants rules. This is the crime and should be punished accordingly.<br>
<br>
Regrds Mirjana<br>
<br>
-----Originalna poruka-----<br>
Od: Latingp <<a href="mailto:latingp-bounces@icann.org">latingp-bounces@icann.org</a>> U ime Michael Bauland<br>
Poslato: Monday, July 9, 2018 15:02<br>
Za: <a href="mailto:latingp@icann.org">latingp@icann.org</a><br>
Tema: Re: [Latingp] ODG: Variants -- Case for Considering Upper Case<br>
<br>
Dear Mirjana,<br>
<br>
<br>
On 09.07.2018 14:22, Mirjana Tasić wrote:<br>
<br>
> Dear Bill,<br>
> <br>
> <br>
> <br>
> I am a little bit confused with this discussion. I cannot remember <br>
> that I have ever seen the domain name written in uppercase. May be it <br>
> is the result of not paying attention to such cases. Could you <br>
> please give me some examples of ASCII domains written and registered in uppercase?<br>
<br>
you do not *register* domains in upper or lower case. The domain name is always case insensitive. You can simply try this out yourself.<br>
If you go to<br>
<a href="http://icann.org/" target="_blank">http://icann.org</a><br>
or<br>
<a href="http://icann.org/" target="_blank">http://Icann.oRg</a><br>
<br>
It's all the same. Therefore you don't know, if some company simply always publishes its internet address in capital letters. Or mixed if they want to be very cool/hip/modern, whatever. ;-)<br>
<br>
Therefore domain names can look the same, although they are different.<br>
<br>
Cheers,<br>
<br>
Michael<br>
<br>
--<br>
____________________________________________________________________<br>
| |<br>
| knipp | Knipp Medien und Kommunikation GmbH<br>
------- Technologiepark<br>
Martin-Schmeisser-Weg 9<br>
44227 Dortmund<br>
Germany<br>
<br>
Dipl.-Informatiker Fon: +49 231 9703-0<br>
Fax: +49 231 9703-200<br>
Dr. Michael Bauland SIP: <a href="mailto:Michael.Bauland@knipp.de">
Michael.Bauland@knipp.de</a><br>
Software Development E-mail: <a href="mailto:Michael.Bauland@knipp.de">
Michael.Bauland@knipp.de</a><br>
<br>
Register Court:<br>
Amtsgericht Dortmund, HRB 13728<br>
<br>
Chief Executive Officers:<br>
Dietmar Knipp, Elmar Knipp _______________________________________________<br>
Latingp mailing list<br>
<a href="mailto:Latingp@icann.org">Latingp@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/latingp" target="_blank">https://mm.icann.org/mailman/listinfo/latingp</a>
<o:p></o:p></span></p>
<div id="yqtfd42824">
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:HelveticaNeue;color:black"><br>
_______________________________________________<br>
Latingp mailing list<br>
<a href="mailto:Latingp@icann.org">Latingp@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/latingp" target="_blank">https://mm.icann.org/mailman/listinfo/latingp</a><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-size:12.0pt;font-family:HelveticaNeue;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>