[council] FW: GNSO letter arising from GNSO Council requesting a change to Module 2 of the Draft Applicant Guidebook
Glen de Saint Géry
Glen at icann.org
Tue Jul 20 16:20:35 UTC 2010
Forwarded From: Diane Schroeder
Dear Glen - I will forward this but please note for future transmissions, items to be sent to the board should be sent to secretary at icann.org<mailto:secretary at icann.org> - that way they dont get lost in my inbox. Thanks Diane
On Jul 16, 2010, at 12:08 PM, Glen de Saint Géry wrote:
Dear Diane,
Please transmit the email below to the Board for information. No action is needed.
Please acknowledge receipt so that the Council can be informed that the Board has been copied as requested.
Thank you very much.
Kind regards
Glen de Saint Géry
GNSO Secretariat
gnso.secretariat at gnso.icann.org<mailto:gnso.secretariat at gnso.icann.org>
http://gnso.icann.org
From: Glen de Saint Géry
Sent: vendredi 16 juillet 2010 21:03
To: Kurt Pritz
To: Kurt Pritz and members of the ICANN New GTLD Implementation Team,
CC: ICANN Board
The GNSO Council requests a change to Module 2 of the Draft Applicant Guidebook. Specifically, we request that the section on "Outcomes of the String Similarity Review" be amended to allow applicants to request an Extended Review under applicable terms similar to those provided for other issues such as "DNS Stability: String Review Procedure". We further request that a section be added on ³String Similarity - Extended Review² that parallels other such sections in Module 2.
This request is seen as urgent because there are conditions under which it may be justified for applicants for a string which has been denied further processing based on confusing similarity by the Initial Evaluation to request an extended evaluation. This Extended Review would evaluate extenuating circumstances in the application which may be such that the similarity is not actually detrimental. This may occur, inter alia, in cases such as:
. The same Registry Operator (for an existing gTLD or a proposed new gTLD) could apply for a string that is similar to an existing or applied for string in a manner that is not detrimentally similar from a user point of view. For example, it is possible that an applicant could apply for both a gTLD with a conventional ASCII label and a corresponding internationalized gTLD (IDN gTLD) that could be deemed to be similar but not cause the detrimental confusion that the GNSO recommendation was trying to avoid.
. A situation where there is an agreement between a new applicant Registry Operator and the Registry Operator of an existing gTLD that allows for better service for the users in the geographical area where the new gTLD will be offered. For example, MuseDoma, the Registry Operator for .museum could enter into an agreement with a new gTLD applicant to offer an IDN version of .museum for a specific language community. The two strings might be judged to be similar but their delegation would not cause detrimental confusion.
We thank you for your prompt attention to this GNSO Council request.
Respectfully submitted on behalf of the GNSO Council Chair Chuck Gomes
Glen de Saint Géry
GNSO Secretariat
gnso.secretariat at gnso.icann.org<mailto:gnso.secretariat at gnso.icann.org>
http://gnso.icann.org
Diane Schroeder
Director of Board Support
ICANN
4676 Admiralty Way, Ste. 330
Marina del Rey, CA 90292
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20100720/46c0c4e6/attachment.html>
More information about the council
mailing list