<<<
Chronological Index
>>> <<<
Thread Index
>>>
Comments in Support of GAC Advice on Safeguards
- To: "'comments-gac-safeguard-advice-23apr13@xxxxxxxxx'" <comments-gac-safeguard-advice-23apr13@xxxxxxxxx>
- Subject: Comments in Support of GAC Advice on Safeguards
- From: "Aikman-Scalese, Anne" <AAikman@xxxxxxxxx>
- Date: Tue, 4 Jun 2013 18:33:06 +0000
Comments are made in my individual capacity as a private practice attorney with
a diverse client base ranging from individual artists interested primarily in
free expression (but who also have trademark and copyright interests to
protect), to a state university, to a federally recognized Indian tribe, to a
mass market retailer concerned about counterfeit goods, to a Fortune 150 global
defense industry concern, among others.
The GAC Safeguards should be implemented by ICANN. The best prescription for a
free, open, and innovative Internet is a well-considered self-regulatory
approach by the ICANN Community. The Community should follow the GAC Advice as
to Safeguards and avoid forcing individual governments to enact regulatory
schemes to address their legitimate concerns. Following the GAC Advice as to
Safeguards will also ensure consumer trust and confidence in the Internet as
the new gTLDs launch.
With respect to applications for generic strings that provide for "exclusive
access", the Community should undertake an expedited Policy Development Process
in the GNSO with respect to the GAC Advice regarding operating such strings "in
the public interest". The PDP should include an analysis of the process and
timing of posting Public Interest Commitments as well as enforcing those
commitments via the draft Public Interest Commitment Dispute Resolution
Procedure ("PICDRP"). In terms of organizational effectiveness, there is an
urgent need for the ICANN Board, in cooperation with the Community, to develop
a method for real time participation by the GAC in the Policy Development
Process. There is apparently a Working Group dedicated to this task but an
interim solution is needed.
Thank you for the opportunity to comment.
Respectfully submitted,
Anne Aikman-Scalese
[cid:550201318@04062013-010A]Anne E. Aikman-Scalese
Of Counsel
Lewis and Roca LLP • Suite 700
One South Church Avenue • Tucson, Arizona 85701-1611
Tel (520) 629-4428 • Fax (520) 879-4725
AAikman@xxxxxxxxx<mailto:AAikman@xxxxxxxxx> •
www.LewisandRoca.com/Aikman<http://www.lewisandroca.com/Aikman>
P Please consider the environment before printing this e-mail.
This e-mail contains legally privileged and confidential information
intended only for the individual or entity named within the message.
If the reader of this message is not the intended recipient, or the
agent responsible to deliver it to the intended recipient, you are
hereby notified that any review, dissemination, distribution or
copying of this communication is prohibited. If this communication
was received in error, please notify us by reply e-mail and delete the original
message.
________________________________
For more information about Lewis and Roca LLP, please go to
www.lewisandroca.com<http://www.lewisandroca.com/>.
Phoenix (602)262-5311 Reno (775)823-2900
Tucson (520)622-2090 Albuquerque (505)764-5400
Las Vegas (702)949-8200 Silicon Valley (650)391-1380
This message is intended only for the use of the individual or entity to
which it is addressed. If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering the message to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this message is strictly prohibited. If you have
received this communication in error, please notify us immediately by replying
to the sender of this E-Mail by return E-Mail or by telephone.
In accordance with Internal Revenue Service Circular 230, we advise you that
if this email contains any tax advice, such tax advice was not intended or
written to be used, and it cannot be used, by any taxpayer for the purpose of
avoiding penalties that may be imposed on the taxpayer.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|