ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [council] Regarding confusion amongst two letter codes


Hi Chuck

The first was designed to stimulate discussion through a set of questions which were shared between the two groups. There are certainly no definitive positions yet although some progress was made through the IDN session later in the week.

Kind regards.

Liz
.....................................................

Liz Williams
Senior Policy Counselor
ICANN - Brussels
+32 2 234 7874 tel
+32 2 234 7848 fax
+32 497 07 4243 mob




On 06 Apr 2007, at 16:43, Gomes, Chuck wrote:

Thanks much Liz. Is the first presentation an official position of the
ccNSO or of the ccNSO GAC/IDN working group?

Chuck Gomes

"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."


-----Original Message-----
From: Liz Williams [mailto:liz.williams@xxxxxxxxx]
Sent: Friday, April 06, 2007 4:02 AM
To: Gomes, Chuck
Cc: Mike Rodenbaugh; GNSO Council
Subject: Re: [council] Regarding confusion amongst two letter codes

Hello everyone

You may find this information helpful from the ccNSO meeting
in Lisbon.

http://www.icann.org/meetings/lisbon/presentation-ccnso-idn-28
mar07.pdf

Here is the presentation by  Elisabeth Portenueve --  http://
www.icann.org/meetings/lisbon/presentation-ccnso-gac-idns-26mar07.pdf

Here is the other presentation by Debbie Garside -- http://
www.icann.org/meetings/lisbon/presentation-garside-26mar07.pdf

Happy Easter.

Liz


.....................................................

Liz Williams
Senior Policy Counselor
ICANN - Brussels
+32 2 234 7874 tel
+32 2 234 7848 fax
+32 497 07 4243 mob




On 05 Apr 2007, at 21:21, Gomes, Chuck wrote:

Elisabeth Portenueve is now working for the ISO Maintenance
Agency and
might be a useful resource in this regard.

Chuck Gomes

"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."


-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Mike Rodenbaugh
Sent: Thursday, April 05, 2007 3:07 PM
To: GNSO Council
Subject: RE: [council] Regarding confusion amongst two letter codes

Thanks Bruce, so can we ask both the GAC and the ISO Maintenance
Agency?


Also would love to see that research if you have or can recall any
other identifying info so I can find?

Mike Rodenbaugh
Sr. Legal Director
Yahoo! Inc.

-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx
[mailto:owner-council@xxxxxxxxxxxxxx]
On Behalf Of Bruce Tonkin
Sent: Sunday, April 01, 2007 6:43 PM
To: GNSO Council
Subject: [council] Regarding confusion amongst two letter codes

Hello Mike,


Furthermore, we note close similarity among many
longstanding ccTLDs
(such as .ai/.al, .am/.an, .bi/.bj, .ch/.cn, .gg/.gq,
.ni/.nl, .to/.tp
and others).  Is the GAC aware of any confusion amongst
users of these
ccTLDs?



Actually this could be a good question to ask about the ISO list in
general.   Ie did the ISO consider the potential for confusion when
selecting the two letter codes?

Actually I have read some research to indicate that humans
are better
able to distinguish differences in short strings rather than long
strings.

E.g humans can spot the difference between "to" and "tom"
relatively easily, but not necessarily between "licence" and
"license" .



Regards,
Bruce Tonkin










<<< Chronological Index >>>    <<< Thread Index >>>