<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [bc-gnso] Announcement: Change in June meeting location: Middle East Developments Cause Cancellation of ICANN Jordan Meeting
- To: Marilyn Cade <marilynscade@xxxxxxxxxxx>
- Subject: Re: [bc-gnso] Announcement: Change in June meeting location: Middle East Developments Cause Cancellation of ICANN Jordan Meeting
- From: "Mike O'Connor" <mike@xxxxxxxxxx>
- Date: Sun, 20 Feb 2011 07:25:21 -0600
a couple of thoughts…
i know that most of you already know this, but "non-refundable" tickets are
often refundable -- there's just a rebooking charge. when i cancelled my trip
to Nairobi, i think i got all but $150 back from Expedia in the form of a
credit that i had to use up within a year.
speaking of Nairobi. i participated remotely in that meeting and i have to say
that the experience was great. looking at the $2100 ticket cost to Singapore
(the leading candidate in the rumor mill at the moment) i'd like to lobby for a
US-based remote-participation option. i love you folks, but 48 hours of plane
rides and $2100 to see your faces is pretty steep.
mikey
On Feb 20, 2011, at 7:00 AM, Marilyn Cade wrote:
> Dear BC Members:
>
>
> http://blog.icann.org/2011/02/middle-east-developments-interfere-with-icann-41-jordan-meeting/
>
> ICANN announced that the June meeting will not take place in Jordan. A formal
> announcement of location
> will be made soon. I am aware that at least two BC members have already
> purchased tickets to Jordan. That is
> regrettable, and I do hope that they are refundable tickets.
>
> Please stay tuned for the formal announcement of the new location of the June
> meeting.
>
> I realize that travel to Asia is challenging as well to many BC members, due
> to cost and time to travel.
> I am told that it is likely that the meeting will be in Asia.
>
>
>
> Marilyn Cade
> BC Chair
- - - - - - - - -
phone 651-647-6109
fax 866-280-2356
web http://www.haven2.com
handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|