<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] RE: Tim's response regarding the third amendment
- To: "Gomes,Chuck" <cgomes@xxxxxxxxxxxx>
- Subject: RE: [council] RE: Tim's response regarding the third amendment
- From: Tim Ruiz <tim@xxxxxxxxxxx>
- Date: Wed, 13 Feb 2008 06:51:59 -0700
- Cc: Council GNSO <council@xxxxxxxxxxxxxx>, Edmon Chung <edmon@xxxxxxxxxxx>
- List-id: council@xxxxxxxxxxxxxx
- Reply-to: Tim Ruiz <tim@xxxxxxxxxxx>
- Sender: owner-council@xxxxxxxxxxxxxx
- User-agent: Web-Based Email 4.12.22
<html><body>Correct. And my comment about one per 3166-1 entry was intended for
the fast track. Sorry for the confusion.<BR><BR>Tim <BR><BR>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px
solid" webmail="1">-------- Original Message --------<BR>Subject: RE: [council]
RE: Tim's response regarding the third amendment<BR>From: "Gomes, Chuck"
<cgomes@xxxxxxxxxxxx><BR>Date: Wed, February 13, 2008 2:15 am<BR>To: "Tim
Ruiz" <tim@xxxxxxxxxxx><BR>Cc: "Council GNSO"
<council@xxxxxxxxxxxxxx>, "Edmon
Chung"<BR><edmon@xxxxxxxxxxx><BR><BR>So if I understand you correctly,
you are okay with saying, "Yes, the<BR>GNSO believes that there should be only
one string per ISO 3166-1 entry<BR>per relevant script." Is that correct? If
so, then I understood Edmon<BR>to say that he could live with that.<BR><BR>I
thought you were suggesting that we change it to "Yes, the GNSO<BR>believes
that there should be only one string per ISO<BR>3166-1 entry." In other words,
in a country like Singapore where they<BR>have four official languages using
four different scripts, they would<BR>have to!
pick just one of those. The current response as quoted in my<BR>first
paragraph above says that we would support them having one string<BR>for each
of the four scripts. Of course that doesn't mean the ccNSO<BR>would decide
that.<BR><BR>Chuck<BR><BR>-----Original Message-----<BR>From: Tim Ruiz
[mailto:<a
onclick="Popup.composeWindow('pcompose.php?sendto=tim%40godaddy.com'); return
false;"
href="https://email.secureserver.net/pcompose.php?aEmlPart=0&type=replyall&folder=INBOX&uid=128148#Compose";>tim<B></B>@godaddy.com</A>]
<BR>Sent: Wednesday, February 13, 2008 1:28 AM<BR>To: Gomes, Chuck<BR>Cc:
Council GNSO; Edmon Chung<BR>Subject: RE: [council] RE: Tim's response
regarding the third amendment<BR><BR>If I finally understand this correctly,
the question is:<BR><BR>a) Should there similarly be only a single IDN ccTLD
for a given script<BR>for each territory or can there be multiple IDN ccTLD
strings? For<BR>example, should there be only one equivalent of .cn in Ch!
inese script<BR>for China or .ru in Cyrillic for Russia?<BR><BR>And th
e current response is:<BR><BR>Yes, the GNSO believes that there should be only
one string per ISO<BR>3166-1 entry per relevant script.<BR><BR>And the
suggested change to the proposed response is:<BR><BR>Yes, the GNSO believes
that there should be only one string per ISO<BR>3166-1 entry per relevant
script., except in those cases where one<BR>script is used for multiple
languages and governmental policy makes<BR>selecting a single string
inappropriate. Measures must be taken to limit<BR>confusion and collisions due
to variants.<BR><BR>I am not suggesting we don't answer the question. I am
suggesting that<BR>we stick with the current response. <BR><BR><BR>Tim
<BR><BR>-------- Original Message --------<BR>Subject: RE: [council] RE: Tim's
response regarding the third amendment<BR>From: "Gomes, Chuck" <<A
onclick="Popup.composeWindow('pcompose.php?sendto=cgomes%40verisign.com');
return false;"
href="https://email.secureserver.net/pcompose.php?aEmlPart=0&type=replyall&f!
older=INBOX&uid=128148#Compose">cgomes<B></B>@verisign.com</A>><BR>Date:
Wed, February 13, 2008 12:03 am<BR>To: "Tim Ruiz" <<A
onclick="Popup.composeWindow('pcompose.php?sendto=tim%40godaddy.com'); return
false;"
href="https://email.secureserver.net/pcompose.php?aEmlPart=0&type=replyall&folder=INBOX&uid=128148#Compose";>tim<B></B>@godaddy.com</A>>,
"Edmon Chung" <<A
onclick="Popup.composeWindow('pcompose.php?sendto=edmon%40dotasia.org'); return
false;"
href="https://email.secureserver.net/pcompose.php?aEmlPart=0&type=replyall&folder=INBOX&uid=128148#Compose";>edmon<B></B>@dotasia.org</A>><BR>Cc:
"Council GNSO" <<A
onclick="Popup.composeWindow('pcompose.php?sendto=council%40gnso.icann.org');
return false;"
href="https://email.secureserver.net/pcompose.php?aEmlPart=0&type=replyall&folder=INBOX&uid=128148#Compose";>council<B></B>@gnso.icann.org</A>><BR><BR>Tim,<BR><BR>The
issues report asks a specific question regarding!
this issue. Are<BR>you suggesting that we do not answer the question?
<BR><BR>Chuck<BR><BR>From: owner-<A
onclick="Popup.composeWindow('pcompose.php?sendto=council%40gnso.icann.org');
return false;"
href="https://email.secureserver.net/pcompose.php?aEmlPart=0&type=replyall&folder=INBOX&uid=128148#Compose";>council<B></B>@gnso.icann.org</A>
[mailto:owner-<A
onclick="Popup.composeWindow('pcompose.php?sendto=council%40gnso.icann.org');
return false;"
href="https://email.secureserver.net/pcompose.php?aEmlPart=0&type=replyall&folder=INBOX&uid=128148#Compose";>council<B></B>@gnso.icann.org</a>]<BR>On
Behalf Of Tim Ruiz<BR>Sent: Tuesday, February 12, 2008 11:32 PM<BR>To: Edmon
Chung<BR>Cc: 'Council GNSO'<BR>Subject: RE: [council] RE: Tim's response
regarding the third amendment<BR><BR><BR><BR>Yes, if we can stick with the
original language in this document and let<BR>whatever PDP goes forward deal
with the gov't policy issue. I don't<BR>think we need to go there in this
document.<BR><BR><BR>Tim Ruiz<BR><BR><BR></BLOCKQUOTE></bod!
y></html>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|