ICANN ICANN Email List Archives

[gnso-iocrc-dt]


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

RE: [gnso-iocrc-dt] Revised Redline of Motion

  • To: "Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx>, <gnso-iocrc-dt@xxxxxxxxx>
  • Subject: RE: [gnso-iocrc-dt] Revised Redline of Motion
  • From: "Shatan, Gregory S." <GShatan@xxxxxxxxxxxxx>
  • Date: Tue, 13 Mar 2012 18:01:01 -0400

A few small proposed changes, and a point of clarification:
 
In the last new "Whereas" clause, I think the word "of" after "policy
impact" should be "on".
 
With the change to Recommendation 2, I would suggest that the title of
Recommendation 2 be changed to "In the Initial Round, Protect the
IOC/RCRC Terms in the Languages Provided in Section 2.2.1.2.3 of the
Applicant Guidebook"  (It now still reads "Protect the IOC/RCRC Terms in
as many Languages as Feasible")
 
In recommendation 3 I would insert the word "names" after "RCRC" in the
newly-added language.
 
The point of clarification:
 
Recommendation 2 now refers to "the list of languages ... in Section
2.2.1.2.3" of the AGB.  This Section does not in fact list "languages."
What it does list are specific names/strings in a number of languages.
However, it does not list all of the same strings in all of the
languages.  For instance, REDLIONANDSUN is listed in English only (at
least among languages using the Roman alphabet; perhaps it is there in
Farsi as well).  MOGENDAVIDADOM is there in English, Hebrew and
transliterated Hebrew only.  Some languages are used only for the IOC
names and some only for the RCRC names.
 
My question is:  Are we recommending that the specific names/strings
listed in the AGB be used at the top level in the first round?  Or are
we recommending that all the languages used in Section 2.2.1.2.3 of the
AGB be applied to all of the strings listed in Section 2.2.1.2.3 of the
AGB (thus expanding the total number of names/strings beyond those
specifically on the list, e.g., REDLIONANDSUN would now be "protected"
in Chinese)?  
 
Greg
 
Gregory S. Shatan 
Deputy Chair| Tech Transactions Group 
IP | Technology | Media 
ReedSmithLLP 
The business of relationships
599 Lexington Avenue
New York, NY 10022
212.549.0275 | Phone
917.816.6428 | Mobile
212.521.5450 | Fax
gshatan@xxxxxxxxxxxxx
www.reedsmith.com 

 

________________________________

From: owner-gnso-iocrc-dt@xxxxxxxxx
[mailto:owner-gnso-iocrc-dt@xxxxxxxxx] On Behalf Of Neuman, Jeff
Sent: Tuesday, March 13, 2012 5:22 PM
To: gnso-iocrc-dt@xxxxxxxxx
Subject: [gnso-iocrc-dt] Revised Redline of Motion



All,

 

Based on the e-mails of the Drafting Team, please find enclosed the
revised version of the motion.  Once we are all ok, we will need someone
at the council to make these friendly amendments (after someone seconds
the motion).  Have you had discussions with your groups.

 

Best regards,

 

Jeffrey J. Neuman 
Neustar, Inc. / Vice President, Business Affairs
21575 Ridgetop Circle, Sterling, VA 20166
Office: +1.571.434.5772  Mobile: +1.202.549.5079  Fax: +1.703.738.7965 /
jeff.neuman@xxxxxxxxxxx <mailto:jeff.neuman@xxxxxxxxxxx>   /
www.neustar.biz <http://www.neustar.biz/>  

________________________________

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. 
 
* * *
 
This E-mail, along with any attachments, is considered confidential and may 
well be legally privileged. If you have received it in error, you are on notice 
of its status. Please notify us immediately by reply e-mail and then delete 
this message from your system. Please do not copy it or use it for any 
purposes, or disclose its contents to any other person. Thank you for your 
cooperation.
* * *
To ensure compliance with Treasury Department regulations, we inform you that, 
unless otherwise indicated in writing, any U.S. Federal tax advice contained in 
this communication  (including any attachments) is not intended or written to 
be used, and cannot be used, for the purpose of (1) avoiding penalties under 
the Internal Revenue Code or applicable state and local provisions or (2) 
promoting, marketing or recommending to another party any tax-related matters 
addressed herein.
Disclaimer Version RS.US.1.01.03
pdc1


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

Privacy Policy | Terms of Service | Cookies Policy