<!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:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D = "DAV:" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3132" name=GENERATOR>
<STYLE>@font-face {
font-family: Wingdings;
}
@font-face {
font-family: Century;
}
@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.0pt; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","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
}
P.MsoListParagraph {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
LI.MsoListParagraph {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
SPAN.EmailStyle17 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
OL {
MARGIN-BOTTOM: 0cm
}
UL {
MARGIN-BOTTOM: 0cm
}
</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-AU vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2>Adrian,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2>Please accept my apologies for taking so long to respond to
this. Besides being spread really thin while I was on jury duty for three
weeks, I also needed to consult with RyC members to ensure that any response I
gave was consistent with constituency views. I did the latter yesterday in
our regular biweekly meeting.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2>First of all it is important to emphasize that the main
thrust of the RyC statement regarding the 'confusingly similar' new gTLD
recommendation is that user confusion should be avoided. Also, it is
critical to recognize that the statement is a constituency statement, not a
VeriSign statement. I certainly participated in the development of the
statement but it was truly written and ultimately approved by the full
constituency. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2>Regarding 'confusing strings' (using the latest term used
by ICANN staff in their implementation work), if you read all of the
information in the New gTLD Recommendations submitted to the Board, it is
clear that confusion of strings could come from anyone of the three types
of similarity that you cited ('looks like', 'sounds like' or 'the same as')
and maybe other types as well. I think we have to be very careful to
over-generalize in that regard because each script is different and each ASCII
gTLD is different; there are many variables that come into play. If
it was as simple as establishing precise rules, we might not even need a dispute
process. The fundamental question that will have to be asked and answered
in each case is whether or not a string creates confusion, regardless of what
type of confusion is involved.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2>The RyC is not taking a position that we should be
automatically granted all string variations of our gTLDs. To be honest, we
would love that, and if the community wants to go that route, the RyC will
support it, but we suspect that that is unrealistic. We accept the fact
that we will have to apply for any IDN versions that we want. And we also
expect to be able to challenge any applications for strings that we believe are
confusing with strings we already have. I firmly believe that this is
fully consistent with the New gTLD recommendations.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2>May others apply for ASCII or IDN versions that are
similar to the gTLD strings we currently support or support in the future?
Yes, but, if we believe it creates confusion, they should anticipate a
dispute. At that point it will be up to the dispute panel to decide whether
there is string confusion based on whatever criteria is finally established in
that regard.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2>Regarding your request for examples, we gave at least one
example in our paper. I am going to leave it at that.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=734373523-17042008><FONT face=Arial
color=#0000ff size=2>Chuck</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Adrian Kinderis
[mailto:adrian@ausregistry.com.au] <BR><B>Sent:</B> Thursday, April 10, 2008
11:53 AM<BR><B>To:</B> Gomes, Chuck; Council GNSO<BR><B>Cc:</B> Maher,
David<BR><B>Subject:</B> RE: [council] RyC Confusingly Similar
Statement<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Chuck,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Thanks
for posting this.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Just
so I am clear.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal>“RyC believes that a key means of avoiding this problem is to
allow all manifestations of a given top level domain to be managed by a single
entity. This simple solution will also address the second issue: ensure
that each TLD name always means the same thing.”<o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Which
one(s) of the following is therefore true in the further explanation you (the
RyC) have provided;<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><![if !supportLists]><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">a.<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">No
one, other than Verisign, could have a TLD (ascii or IDN) that <I>looks like</I>
.com<o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><![if !supportLists]><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">b.<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">No
one , other than Verisign, could have a TLD (ascii or IDN) that <I>sounds
like</I> .com<o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><![if !supportLists]><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">c.<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">No
one, other than Versign, could have a TLD (ascii ot IDN) that <I>means the same
as</I> .com<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
think examples will help explain the RyC paper.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Thanks
and see you later today (?)<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">Adrian
Kinderis</SPAN></B><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><BR>Managing
Director</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">AusRegistry
Group Pty Ltd<BR>Level 8, 10 Queens Road<BR>Melbourne. Victoria Australia.
3004<BR>Ph: +61 3 9866 3710<BR>Fax: +61 3 9866 1970<BR>Email: </SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><A
title=mailto:adrian@ausregistry.com.au
href="mailto:adrian@ausregistry.com"><SPAN
style="COLOR: black">adrian@ausregistry.com</SPAN></A><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">Web:
</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><A
href="http://www.ausregistryinternational.com/"><SPAN
style="COLOR: black">www.ausregistrygroup.com</SPAN></A></SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">The
information contained in this communication is intended for the named recipients
only. It is subject to copyright and may contain legally privileged and
confidential information and if you are not an intended recipient you must not
use, copy, distribute or take any action in reliance on it. If you have received
this communication in error, please delete all copies from your system and
notify us immediately.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN lang=EN-US
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
lang=EN-US style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] <B>On Behalf
Of </B>Gomes, Chuck<BR><B>Sent:</B> Thursday, 10 April 2008 7:31
AM<BR><B>To:</B> Council GNSO<BR><B>Cc:</B> David W. Maher<BR><B>Subject:</B>
[council] RyC Confusingly Similar Statement<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Century','serif'">Here's a statement
developed by the RyC regarding New gTLD Recommendation 2, hopefully
providing some new thoughts in that regard.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Century','serif'">Chuck</SPAN><o:p></o:p></P></DIV></BODY></HTML>