ICANN ICANN Email List Archives

[gnso-iocrc-dt]


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

[gnso-iocrc-dt] RE: Languge Issue Solution

  • To: "Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx>, Kiran Malancharuvil <kmalancharuvil@xxxxxxxxx>, "gnso-iocrc-dt@xxxxxxxxx" <gnso-iocrc-dt@xxxxxxxxx>
  • Subject: [gnso-iocrc-dt] RE: Languge Issue Solution
  • From: "Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx>
  • Date: Tue, 13 Mar 2012 13:58:36 -0400

Never mind...it was sent.  All, please make sure this point is discussed with 
your relevant groups.

Jeffrey J. Neuman
Neustar, Inc. / Vice President, Business Affairs

________________________________
The information contained in this e-mail message is intended only for the use 
of the recipient(s) named above and may contain confidential and/or privileged 
information. If you are not the intended recipient you have received this 
e-mail message in error and any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately and delete the original message.


From: owner-gnso-iocrc-dt@xxxxxxxxx [mailto:owner-gnso-iocrc-dt@xxxxxxxxx] On 
Behalf Of Neuman, Jeff
Sent: Tuesday, March 13, 2012 11:55 AM
To: Kiran Malancharuvil; gnso-iocrc-dt@xxxxxxxxx
Cc: Jim Bikoff; debra.hughes@xxxxxxxxxxxx; shankins@xxxxxxxx; 
christophe.lanord@xxxxxxxx
Subject: [gnso-iocrc-dt] RE: Languge Issue Solution

Thanks for this.  Can I ask that you please send this to the full drafting team 
list so we can amend the motion?

Jeffrey J. Neuman
Neustar, Inc. / Vice President, Business Affairs

________________________________
The information contained in this e-mail message is intended only for the use 
of the recipient(s) named above and may contain confidential and/or privileged 
information. If you are not the intended recipient you have received this 
e-mail message in error and any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately and delete the original message.


From: Kiran Malancharuvil [mailto:kmalancharuvil@xxxxxxxxx]
Sent: Monday, March 12, 2012 4:12 PM
To: gnso-iocrc-dt@xxxxxxxxx<mailto:gnso-iocrc-dt@xxxxxxxxx>
Cc: Neuman, Jeff; Jim Bikoff; 
debra.hughes@xxxxxxxxxxxx<mailto:debra.hughes@xxxxxxxxxxxx>; 
shankins@xxxxxxxx<mailto:shankins@xxxxxxxx>; 
christophe.lanord@xxxxxxxx<mailto:christophe.lanord@xxxxxxxx>
Subject: Languge Issue Solution
Importance: High

Dear Jeff and all:

The RCRC and IOC representatives met this afternoon as requested, to discuss 
the languages to be included for the String Similarity Review on the top-level 
and for the first round only.

The RCRC and IOC have agreed to limit the languages submitted for String 
Similarity Review on the top-level and for the first round to those set forth 
in the Applicant Guidebook in Section 2.2.1.2.3.  The parties have decided to 
proceed this way in the spirit of cooperation and for purposes of expediency, 
understanding that the parties both assert that the list of languages as set 
forth in the Applicant Guidebook in Section 2.2.1.2.3 is only illustrative and 
the denominations have broader protections in other languages that may be 
asserted in future rounds and at the second level.  We hope that this spirit of 
cooperation will resolve the discussions that have been held on the languages 
issue and will help move this proposal forward to consensus.

Accordingly, as this list has been previously verified, we recommend that the 
last sentence of Recommendation 2 relating to vetting of the list be deleted.

Respectfully submitted,

Christophe Lanord, Debra Hughes, Jim Bikoff, Kiran Malancharuvil and Stephane 
Hankins



Kiran J. Malancharuvil

Silverberg, Goldman & Bikoff, L.L.P.

Georgetown Place, Suite 120

1101 30th Street NW

Washington, DC 20016

(202) 944-3307 - Office

(619) 972-7810 - Mobile

kmalancharuvil@xxxxxxxxx<mailto:kmalancharuvil@xxxxxxxxx>





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

Privacy Policy | Terms of Service | Cookies Policy