<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="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:blue;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:595.3pt 841.9pt;
        margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
        {page:Section1;}
-->
</style>
</head>
<body lang=EL link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Hi Vladimir and all,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>I have been discussing
for quite a long period with the DNSEXT group of the IETF because (in my
opinion) an xNAME solution is necessary in many cases for a good user
experience of the IDN Variants. That discussion has not finished but it hasn’t
progressed significantly since the SF Icann meeting. I fully support your
proposal about the presentation, since many are unaware of the difficulties of
administering multiple TLDs (when they should perform as one) while trying to
help the user minimize his costs and troubles.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>I believe Andrew could
tell us what the present situation of the xNAME discussion is. I had to take
some unavoidable time of absence lately and I am a little uninformed since so
please forgive me for not giving you a clear picture of the current status of
this issue.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Kind Regards,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Vaggelis Segredakis<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span lang=EN-US
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span lang=EN-US style='font-size:10.0pt;font-family:Tahoma'>
vip-bounces@icann.org [mailto:vip-bounces@icann.org] <b><span style='font-weight:
bold'>On Behalf Of </span></b>Vladimir Shadrunov<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 05, 2011 12:07
PM<br>
<b><span style='font-weight:bold'>To:</span></b> vip@icann.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [vip] Educational
session on existing variant practices</span></font><span lang=EN-US><o:p></o:p></span></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Hi Andrew and thanks for
your comment. <br>
<br>
I perfectly understand your points. However, I heard a number of times that
DNAME or some other xNAME may be part of the solution for the problem we are
trying to define. There may be members of this group who do not know well what
DNAME is and I think a 5-10 minute presentation may fill this gap. <br>
<br>
With regards to the work of IETF there are RFCs that consider variants and string
similarity, at least for Chinese and Cyrillic scripts. I believe this is very
relevant to the work of this group and as these are finished work products I
believe it may be useful for the group to learn if the variant issues were
defined and dealt with in these RFCs. <br>
<br>
Best regards,<br>
Vladimir Shadrunov<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On 4 July 2011 22:03, Andrew Sullivan <<a
href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>> wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Dear colleagues,<br>
<br>
I think this is an excellent suggestion worthy of pursuit. I have one<br>
remark, however.<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><br>
On Mon, Jul 04, 2011 at 11:04:07AM +0100, Vladimir Shadrunov wrote:<br>
<br>
> If someone active in the IETF community would be willing to give a<br>
> presentation on how existing DNS standards and related RFC handle string<br>
> similarity that would also be great. Additionally some feedback from the
IP<br>
> lawyers would be appreciated as to whether the variant problem exists in
the<br>
> IP realm.<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I can certainly provide an overview of how various DNS technologies<br>
can be used to help with label-string similarity issues. There are<br>
some tricks one can use in the DNS that make some of these issues in<br>
some ways easier, and in some ways trickier, to deal with.<br>
<br>
But the short answer to the question as phrased above is much more<br>
blunt, and I want to put it here on the list so that it is not lost.<br>
The existing DNS standards and related RFCs do nothing at all about<br>
string similarity. DNS is an exact-match technology. You send a<br>
query for a QNAME, QCLASS, and QTYPE. If there is an entry in the<br>
authoritative name server you happen to talk to, or some in<br>
intermediate cache, that matches _exactly_ your requested combination,<br>
you get back an answer. If there is the same name but something else<br>
doesn't match, you get back an empty answer with no error (or,<br>
sometimes, a redirection). And if there is no such name in the<br>
authoritative servers, you get back "NXDOMAIN" (that is, RCODE=3 Name<br>
Error).<br>
<br>
This is a deep and fundamental part of the DNS, and it is important we<br>
not lose sight of it; it is not something we can change without<br>
effectively replacing the DNS itself. Anything that we cannot<br>
ultimately simulate by adding to the number of exact matches in the<br>
global DNS -- that is, making the DNS bigger -- is just not a policy<br>
that can ever be deployed.<br>
<br>
Best regards,<br>
<br>
A<br>
<font color="#888888"><span style='color:#888888'><br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a></span></font><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>