<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [gnso-cc-idn-tld-rg] RE: Reminder & Meeting Suggestion
- To: "Adrian Kinderis" <adrian@xxxxxxxxxxxxxxxxxx>
- Subject: Re: [gnso-cc-idn-tld-rg] RE: Reminder & Meeting Suggestion
- From: stefanie lai <steflai@xxxxxxxxxxxxx>
- Date: Sat, 8 Dec 2007 10:16:45 +0800
Hi Chuck,
I am available on both the 17th and 18th
Thanks
Stefanie
On 8 Dec 2007, at 4:04 AM, Adrian Kinderis wrote:
Chuck,
I will be in the air on a flight home on Monday 17th at the
specified time.
I will be available and perhaps jetlagged on Tuesday 18th.
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: adrian@xxxxxxxxxxxxxxx
Web: 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 Olga Cavalli
Sent: Friday, 7 December 2007 11:26 PM
To: Gomes, Chuck; cc-IDN Rework Group
Subject: Re: [gnso-cc-idn-tld-rg] RE: Reminder & Meeting Suggestion
Chuck,
no problem for me on Monday 17th or Tuesday 18th, at the same time.
Regards
Olga
----- Original Message -----
From: Gomes, Chuck
To: Gomes, Chuck ; cc-IDN Rework Group
Sent: Friday, December 07, 2007 11:57 AM
Subject: [gnso-cc-idn-tld-rg] RE: Reminder & Meeting Suggestion
Regarding the suggested meeting on 11 Dec, please cancel that
request. I just realized that I will not have arrived in Prague at
that time and will be in flight. We will have to wait until the
following week.
Please communicate your availability on Monday, 17 Dec. or Tuesday,
18 Dec at the same time:
13:00 UTC [00:00 Midnight (Melbourne); 21:00 (HK); 15:00 (Jordan);
14:00 (Brussels); 10:00 (Buenos Aires); 8:00 (NY); 5:00 (Calif.)]
In the meantime let's continue discussion in Google Docs.
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."
From: Gomes, Chuck
Sent: Friday, December 07, 2007 9:52 AM
To: cc-IDN Rework Group
Subject: Reminder & Meeting Suggestion
Reminder: Everyone committed to reviewing and commenting on the
document in Google Docs NLT than this coming Monday. As of this
point in time, the following have done so: Adrian, Avri, Olga and
myself.
I am thinking that we should have a conference call next week.
Unfortunately, my schedule is very busy next week because I will be
in Prague for ICANN Registry/Registrar meetings. One day I could
do a meeting would be on Tuesday, 11 Dec at our agreed-to time:
13:00 UTC [00:00 Midnight (Melbourne); 21:00 (HK); 15:00 (Jordan);
14:00 (Brussels); 10:00 (Buenos Aires); 8:00 (NY); 5:00 (Calif.)]
Please communicate on this list NLT Monday, 13:00 UTC if this time
will NOT work for you. Otherwise, I request that Glen schedule a
call for two hours if possible. If this time is okay with you,
please reserve it on your calendar.
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."
__________ Información de NOD32, revisión 2709 (20071207) __________
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|