<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="">
Hi all.
<div class="">I would like to comment on the proposal to remove the limitation about two character strings. The text reads:</div>
<blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div class="">
<div class="page" title="Page 29">
<div class="section">
<div class="layoutArea">
<div class="column">
<p class=""><i class=""><span class="" style="font-size: 11pt; font-family: TimesNewRomanPSMT;">2.7.1.c.3: The Work Track is also considering a proposal to remove the reservation of two-character strings at the top level that consist of one ASCII letter and
one number (e.g., .O2 or .3M), but acknowledges that technical considerations may need to be taken into account on whether to lift the reservation requirements for those strings. In addition, some have expressed concern over two characters consisting of a
number and an ASCII letter where the number closely resembles a letter </span><span class="" style="font-size: 11pt; font-family: TimesNewRomanPSMT;">(e.g., a “zero” looking like the letter “O” or the letter “L” in lowercase looking like the number “one”). </span></i></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div class="">Personally, I believe that besides the issue about confusing similarity there is a more fundamental problem. Two characters string are used for ccTLDs following inclusion in the ISO 3166-1 Alpha-2 list.</div>
<div class="">While the list is clearly identified as “Alpha-2” I am not sure that, in case of a future shortage of combinations, ISO could not instruct ISO 3166-MA to use also two-characters alphanumeric strings. We have seen that already with IATA and the
airline codes, initially limited to two characters alphabetic strings, but later extended to two characters alphanumeric.</div>
<div class="">I personally believe that, considering that we have billions of possibilities with alphanumeric character strings of length >2 we are unnecessarily taking collision risks for little benefit. May I also remind that ICANN has already in the previous
round ignored collision warnings and had to take emergency action afterwards. I hope that we have learned from the experience.</div>
<div class="">Should ICANN decide do disregard the warning and proceed anyway, it should at least protect itself asking ISO for a commitment not to use mixed alphanumeric 2-character strings in the future as part of the ISO-3166 code system.</div>
<div class="">This comment applies also as answer to the related question quoted below:</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">
<div class="">
<div class="gmail_default" style="font-size: small;"><span id="m_-6320552768509264848m_-222030257553634043gmail-docs-internal-guid-b8351502-7fff-4518-2866-40b3741d2434" class="">
<p dir="ltr" style="line-height: 1.2; margin-top: 0pt; margin-bottom: 6pt;" class="">
<span style="font-size: 11pt; font-family: Calibri; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;" class=""><i class="">Q 2.7.1.e.2 -
</i></span><i style="font-family: Calibri; font-size: 11pt; white-space: pre-wrap;" class="">If there are no technical obstacles to the use of 2-character strings at the top level consisting of one letter and one digit (or digits more generally), should the
reservation of those strings be removed? Why or why not? Do you believe that any additional analysis is needed to ensure that these types of strings will not pose harm or risk to security and stability? Please explain.</i></p>
</span></div>
</div>
</blockquote>
<div class="">Best regards,</div>
<div class="">Roberto</div>
</body>
</html>