<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19190">
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: CG Times;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-compose
}
.MsoChpDefault {
mso-style-type: export-only
}
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><FONT color=#0000ff><SPAN class=334043619-06032012>Dear
IAG:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff><SPAN
class=334043619-06032012></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff>ICANN IAG: N5: Matching Rules</FONT></DIV>
<DIV> </DIV>
<DIV><BR><FONT color=#0000ff>Issue 1: Applying the Identical Match
rules</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT color=#0000ff>1. Regarding rule "B" of matching rules:</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT color=#0000ff>I suggest that the transcription of the special
characters "@" and "&" be based on the language of the trademark itself,
rather than the intended language for the domain name or national language of
the jurisdiction.</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT color=#0000ff>I furthermore suggest that the language of the
trademark be collected from the trademark owner during the initial application
to the clearinghouse. <SPAN
class=334043619-06032012> </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff><SPAN
class=334043619-06032012> </SPAN><BR>Trademark owners <SPAN
class=334043619-06032012>could also </SPAN>indicate at the time of
submission to the clearinghouse what their intended spelling should be for the
special characters "@" and "&".</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT color=#0000ff>I find it unusual that these <SPAN
class=334043619-06032012> are the only </SPAN>two special
characters <SPAN class=334043619-06032012> that </SPAN>are
afforded the special treatment for trademark owners. There are other
special characters, such as "+" <SPAN class=334043619-06032012> and
"*" </SPAN>that also deserve such treatment.<SPAN
class=334043619-06032012> </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff><SPAN
class=334043619-06032012></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff><SPAN class=334043619-06032012>Are Registries allowed
to augment this rule if they wish by allowing additional special
characters to be spelled out? </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><BR><FONT color=#0000ff>Issue 2: Registry Character Mappings</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT color=#0000ff>I <SPAN
class=334043619-06032012> recommend </SPAN>the approach where the
clearinghouse is responsible for providing the mapping rules <SPAN
class=334043619-06032012> for </SPAN>each TLD. This will help
ensure consistency across TLDs for matching during sunrise and claims
periods.</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT color=#0000ff>Allowing registries to perform this step may require
distribution of data, which has previously been considered as
undesirable.</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT color=#0000ff>I also recommend that where variant characters exist
for certain languages, that ICANN encourage Registries follow a universal
standard rather than develop their own unique approach.</FONT></DIV>
<DIV><SPAN class=334043619-06032012><FONT
color=#0000ff> </FONT></SPAN></DIV>
<DIV><SPAN class=334043619-06032012><FONT color=#0000ff>Is the issue of variants
for IDN's only? Or can Registries develop
additional transcription rules for "variants" including special characters,
numbers, etc.</FONT></SPAN></DIV>
<DIV><SPAN class=334043619-06032012> </SPAN><BR><SPAN
class=334043619-06032012><FONT color=#0000ff>Best regards,</FONT></SPAN></DIV>
<DIV><SPAN class=334043619-06032012><FONT
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=334043619-06032012><FONT color=#0000ff>Tom
Barrett</FONT></SPAN></DIV>
<DIV><SPAN class=334043619-06032012><FONT
color=#0000ff>President</FONT></SPAN></DIV>
<DIV><SPAN class=334043619-06032012><FONT
color=#0000ff>EnCirca</FONT></SPAN></DIV></BODY></HTML>