<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [gnso-rn-wg] IDN WG Recommendations for Single/2-Character Subgroup
- To: "Gomes,Chuck" <cgomes@xxxxxxxxxxxx>
- Subject: RE: [gnso-rn-wg] IDN WG Recommendations for Single/2-Character Subgroup
- From: Tim Ruiz <tim@xxxxxxxxxxx>
- Date: Thu, 26 Apr 2007 03:25:14 -0700
<div>
4.1.1 basically ensures that no new gTLD round could be started unless
it includes IDN gTLDs. I suppose that is the IDN-WG's goal.</div>
<div> </div>
<div>
With the dozens or even hundreds of languages based on roman/cyrillic
scripts who is going to examine every ASCII gTLD string applied for to see if
it could possibly mean something in another language? And even if it does, to
assume that the intent is ASCII-squatting is overstepping, IMHO. I think that's
what the dispute processes should be for instead of making blanket assumptions
and overly restrictive, difficult to enforce policy.</div>
<div><BR><BR>Tim <BR></div>
<div name="wmMessageComp"><BR><BR>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px
solid" webmail="1">-------- Original Message --------<BR>Subject: [gnso-rn-wg]
IDN WG Recommendations for Single/2-Character<BR>Subgroup<BR>From: "Gomes,
Chuck" <cgomes@xxxxxxxxxxxx><BR>Date: Wed, April 25, 2007 6:06 pm<BR>To:
<gnso-rn-wg@xxxxxxxxx><BR><BR>
<DIV><FONT face=Arial size=2><SPAN class=298554620-25042007>
Here are the IDN-WG recommendations that I promised to send in todays
meeting for reference by the Single/2-Character Subgroup. Note the last
one I included below does not relate to the point I made in our call today but
does relate to symbols so I included it as well.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=298554620-25042007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=298554620-25042007>
These recommendations, with the exception of the last one, could also be
useful for consideration by other subgroups as you consider ASCII and IDN
recommendations for reserved names. Any recommendations that would give
an advantage to ASCII gTLD applicants over IDN gTLD applicants might relate to
the recommendations below.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=298554620-25042007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial><SPAN class=298554620-25042007><STRONG><U>Areas of
Agreement by the IDN-WG</U></STRONG> (Strong Support)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=298554620-25042007></SPAN></FONT> </DIV>
<DIV><FONT size=2><SPAN class=298554620-25042007>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><B
style="mso-bidi-font-weight: normal"><SPAN style="mso-bidi-font-family:
Arial"><FONT size=3><FONT face=Arial>4.1.1 Avoidance of ASCII-Squatting:
<o:p></o:p></FONT></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
size=3><FONT face=Arial><B style="mso-bidi-font-weight: normal"><SPAN
style="mso-bidi-font-family: Arial">Agreement </SPAN></B><SPAN
style="mso-bidi-font-family: Arial">
to avoid “ASCII-squatting” situations where applications for
new non-IDN gTLD strings, if accepted for insertion in the root at an earlier
stage than IDN gTLDs, could pre-empt later applications for IDN gTLDs.
<o:p></o:p></SPAN></FONT></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><SPAN
style="FONT-SIZE: 10pt; LINE-HEIGHT: 150%; mso-bidi-font-family: Arial"><FONT
face=Arial>
E.g. a new non-IDN gTLD “.caxap”, if accepted, would
prohibit the acceptance of a later application for an IDN gTLD
“.caxap” (in Cyrillic script and meaning “sugar” in
Russian). </FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><SPAN
style="FONT-SIZE: 10pt; LINE-HEIGHT: 150%; mso-bidi-font-family: Arial"><FONT
face=Arial></FONT></SPAN> </P><SPAN style="FONT-SIZE: 10pt; LINE-HEIGHT:
150%; mso-bidi-font-family: Arial">
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><B
style="mso-bidi-font-weight: normal"><SPAN style="mso-bidi-font-family:
Arial"><FONT size=3><FONT face=Arial>4.1.6. Limit Confusingly Similar Strings:
<o:p></o:p></FONT></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
size=3><FONT face=Arial><B style="mso-bidi-font-weight: normal"><SPAN
style="mso-bidi-font-family: Arial">Agreement </SPAN></B><SPAN
style="mso-bidi-font-family: Arial">
that measures be taken to ensure that an IDN gTLD string with
v<st1:PersonName w:st="on">ari</st1:PersonName>
ants (see 4.1.4 and 4.1.5 above) be treated in analogy with current
practice for IDN SLD labels, i.e. strings that only differ from an IDN gTLD
string by v<st1:PersonName w:st="on">ari</st1:PersonName>
ants (see above) are not available for registration by others.
<o:p></o:p></SPAN></FONT></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><SPAN
style="FONT-SIZE: 10pt; LINE-HEIGHT: 150%; mso-bidi-font-family: Arial"><FONT
face=Arial>
Note: This is equivalent in effect to the provisions against
“confusingly similar” strings foreseen in the New gTLD
recommendations.<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><o:p><FONT
face=Arial></FONT></o:p> </P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><o:p><SPAN
class=298554620-25042007><FONT face=Arial size=3><STRONG><U>Areas of Support by
the IDN-WG</U></STRONG> (Some Support)</FONT></SPAN></o:p></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><o:p><SPAN
class=298554620-25042007><FONT face=Arial
size=3></FONT></SPAN></o:p> </P><o:p><SPAN class=298554620-25042007><FONT
size=3>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><B
style="mso-bidi-font-weight: normal"><SPAN style="mso-bidi-font-family:
Arial"><FONT face=Arial>4.2.1<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
face=Arial><B style="mso-bidi-font-weight: normal"><SPAN
style="mso-bidi-font-family: Arial">Support</SPAN></B><SPAN
style="mso-bidi-font-family: Arial">
for a first application round open to both non-IDN gTLDs and IDN gTLDs,
if possible. <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><B
style="mso-bidi-font-weight: normal"><SPAN style="mso-bidi-font-family:
Arial"><o:p><FONT face=Arial> </FONT></o:p></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><B
style="mso-bidi-font-weight: normal"><SPAN style="mso-bidi-font-family:
Arial"><FONT face=Arial>4.2.2<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
face=Arial><B style="mso-bidi-font-weight: normal"><SPAN
style="mso-bidi-font-family: Arial">Support</SPAN></B><SPAN
style="mso-bidi-font-family: Arial">
for avoiding “hostage” situations in planning a new non-IDN
gTLD application round; neither non-IDN gTLDs nor IDN gTLDs should be delayed
due to the other. <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
face=Arial size=2></FONT> </P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><B
style="mso-bidi-font-weight: normal"><SPAN style="mso-bidi-font-family:
Arial"><FONT face=Arial>4.2.6<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
face=Arial><B style="mso-bidi-font-weight: normal"><SPAN
style="mso-bidi-font-family: Arial">Support</SPAN></B><SPAN
style="mso-bidi-font-family: Arial">
for resolving IDN policy issues before launch of application round.
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT:
150%"><FONT face=Arial><B style="mso-bidi-font-weight: normal"><SPAN
style="mso-bidi-font-family: Arial">Alternative view</SPAN></B><SPAN
style="mso-bidi-font-family: Arial">; prioritize launch of IDN gTLD over
non-IDN gTLDs. <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; LINE-HEIGHT: 150%"><FONT
face=Arial><B style="mso-bidi-font-weight: normal"><SPAN
style="mso-bidi-font-family: Arial">Alternative view</SPAN></B><SPAN
style="mso-bidi-font-family: Arial">
; provide opportunities to reserve IDN gTLD strings in case the first
application round can only address non-IDN gTLD applications fully.
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><SPAN
style="FONT-SIZE: 10pt; LINE-HEIGHT: 150%; mso-bidi-font-family: Arial"><FONT
face=Arial>
Note: Whether there will be a timing issue or not depends on the
progress of the new gTLD policy, including IDN policy aspects, as well as on
the progress of the protocol revisions and technical tests regarding IDN at the
top-level. They all need to have advanced sufficiently before a decision can be
made to go ahead with IDN TLD deployment.<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
face=Arial size=2></FONT> </P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><SPAN
style="mso-bidi-font-family: Arial"><o:p><FONT
face=Arial> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><SPAN
style="mso-bidi-font-family: Arial"><FONT
face=Arial><STRONG>4.2.21</STRONG><SPAN class=298554620-25042007><STRONG>
</STRONG>
(Note: this one does not relate to the point I made in today's call but
is relevant to symbols.)</SPAN></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
face=Arial><B style="mso-bidi-font-weight: normal"><SPAN
style="mso-bidi-font-family: Arial">Support</SPAN></B><SPAN
style="mso-bidi-font-family: Arial">
for elimination of non-language characters, as foreseen in the IDN
protocol revision. <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><SPAN
style="mso-bidi-font-family: Arial"><FONT face=Arial><SPAN
style="mso-tab-count: 1">
</SPAN><B style="mso-bidi-font-weight: normal">Alternative view</B>: to signal
concerns about symbols that may be <o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><SPAN
style="mso-bidi-font-family: Arial"><FONT face=Arial><SPAN
style="mso-tab-count: 1">
</SPAN>eliminated but would potentially be needed for human
communications.<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
face=Arial size=2></FONT> </P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 150%"><FONT
face=Arial
size=2></FONT></FONT></SPAN></o:p></SPAN> </P></SPAN></FONT></DIV>
<DIV> </DIV>
<DIV align=left><FONT face=Tahoma size=2>Chuck Gomes</FONT></DIV>
<DIV align=left><FONT face=Tahoma size=2></FONT> </DIV>
<DIV align=left><FONT face=Tahoma size=2>
"This message is intended for the use of the individual or entity to
which it is addressed, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. Any unauthorized
use, distribution, or disclosure is strictly prohibited. If you have received
this message in error, please notify sender immediately and destroy/delete the
original transmission." </FONT></DIV>
<DIV> </DIV></BLOCKQUOTE></DIV>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|