ICANN ICANN Email List Archives

[gnso-cc-idn-tld-rg]


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

Re: [gnso-cc-idn-tld-rg] Recap of Final cc Rework Group Meeting

  • To: <adrian@xxxxxxxxxxxxxxxxxx>, <gnso-cc-idn-tld-rg@xxxxxxxxx>, <liz.gasster@xxxxxxxxx>, <cgomes@xxxxxxxxxxxx>
  • Subject: Re: [gnso-cc-idn-tld-rg] Recap of Final cc Rework Group Meeting
  • From: "Liz Gasster" <Liz.Gasster@xxxxxxxxx>
  • Date: Wed, 30 Jan 2008 08:42:46 -0800

Also pls use track changes for all edits and post to the list. Thanks, Liz  
-----Original Message----- 
From: "liz.gasster" <liz.gasster@xxxxxxxxx> 
To: Adrian Kinderis <adrian@xxxxxxxxxxxxxxxxxx> 
To:  <gnso-cc-idn-tld-rg@xxxxxxxxx> 
To:  <liz.gasster@xxxxxxxxx> 
To: Chuck' 'Gomes <cgomes@xxxxxxxxxxxx> 
 
Sent: 1/30/2008 8:27:25 AM 
Subject: RE: [gnso-cc-idn-tld-rg] Recap of Final cc Rework Group Meeting 
 
Doc attached 
 
  
 
  _____   
 
From: owner-gnso-cc-idn-tld-rg@xxxxxxxxx 
[mailto:owner-gnso-cc-idn-tld-rg@xxxxxxxxx] On Behalf Of Adrian Kinderis 
Sent: Tuesday, January 29, 2008 7:21 PM 
To: Gomes, Chuck; gnso-cc-idn-tld-rg@xxxxxxxxx 
Subject: RE: [gnso-cc-idn-tld-rg] Recap of Final cc Rework Group Meeting 
 
  
 
Thanks Chuck. 
 
  
 
I think you just need to be careful to not open the Document up for 
discussion on the GNSO Council call. People will react to the Executive 
Summary without reading the body  of the text which will only lead to 
circular conversation. 
 
  
 
I think that you should introduce the document as you have suggested and ask 
that responses be considered between the meeting and Delhi where we can 
discuss the topics thoroughly. 
 
  
 
My two cents (plus ICANN domain tasting fee). 
 
  
 
P.S. Great job everyone! 
 
  
 
Adrian Kinderis 
Managing Director 
 
AusRegistry Group Pty Ltd 
Level 8, 10 Queens Road 
Melbourne. Victoria Australia. 3004 
Ph: +61 3 9866 3710 
Fax: +61 3 9866 1970 
Email:  <mailto:adrian@xxxxxxxxxxxxxxx> adrian@xxxxxxxxxxxxxxx 
Web:  <http://www.ausregistryinternational.com/> www.ausregistrygroup.com 
 
  
 
The information contained in this communication is intended for the named 
recipients only. It is subject to copyright and may contain legally 
privileged and confidential information and if you are not an intended 
recipient you must not use, copy, distribute or take any action in reliance 
on it. If you have received this communication in error, please delete all 
copies from your system and notify us immediately. 
 
  
 
  
 
From: owner-gnso-cc-idn-tld-rg@xxxxxxxxx 
[mailto:owner-gnso-cc-idn-tld-rg@xxxxxxxxx] On Behalf Of Gomes, Chuck 
Sent: Wednesday, 30 January 2008 11:32 AM 
To: gnso-cc-idn-tld-rg@xxxxxxxxx 
Subject: [gnso-cc-idn-tld-rg] Recap of Final cc Rework Group Meeting 
Importance: High 
 
  
 
For those unable to participate in our final call, we finished our final 
edits today.  Liz will be incorporating those edits into the final document 
and distributing the final draft document for group review within a few 
hours.  Within 24 hours of the time it hits your email box please review it 
and provide any suggested edits you have to this list.  First thing on 
Thursday morning (California time), Liz and I will incorporate those edits 
as we judge appropriate into a final version that will be sent to the GNSO 
Council before the Council meeting on Thursday, 31 January.  Chuck will 
provide a brief overview of the document during that meeting (probably the 
Executive Summary), will entertain general questions without getting into 
content discussion and will encourage all Councilors to thoroughly 
familiarize themselves with the full document before our New Delhi weekend 
working sessions. 
 
  
 
Thanks again for all the great work.  It was a pleasure leading this 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."  
 
  
 




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

Privacy Policy | Terms of Service | Cookies Policy